BR112016028298B1 - OPERATING METHOD ON A REQUESTING DEVICE AND REQUESTING DEVICE, AND OPERATING METHOD ON A LOCAL DEVICE AND LOCAL DEVICE - Google Patents

Abstract

DISCOVERY OF MULTI-HOP CAPABILITY AND ROUTING ON A PER-LINK BASIS. It is a device and a method for sending a resource discovery query to a local device to request resource information per link for a wireless link between a requesting device and the local device to receive the resource information per link requested from the local device that indicates the resources that the local device has available to allocate to the wireless link, and to establish the wireless link with the local device based on the resource information received. The wireless link may be a point-to-point link. Disclosed are a device and a method for allocating resources, from a pool of resources available to the local device, on a per-link basis, to receive a resource discovery query from a requesting device that seeks per-link resource information, and to send resource information per link to the requesting device that indicates the resources that the local device has available to allocate to the wireless link.

Description

CROSS REFERENCE TO RELATED ORDERS

[0001] This application claims the priority and benefit of provisional patent application No. 62/006,877 filed with the United States Patent and Trademark Office on June 2, 2014, and non-provisional patent application No. US 14/ 664,575 filed with the United States Patent and Trademark Office on March 20, 2015, the entire contents of which are incorporated herein by reference.

BACKGROUND FIELD

[0002] Various characteristics relate to devices and communication methods for discovering device resources in multi-hop systems and routing traffic through surrounding devices on a per-link basis.

BACKGROUND

[0003] In current wireless cellular communication systems, such as those commonly referred to as 3G, 4G and/or long term evolution (LTE) systems, wireless devices maintain a paradigm in which communication between devices passes through a access node (e.g. base station, NodeB or eNodeB). Under this paradigm, a wireless device establishes a single link with its access node (where the link includes uplink and downlink components).

[0004] In current wireless cellular communication systems, a device advertises its radio access capability in terms of a “category”. Devices advertise their capabilities to other devices to facilitate communication between devices. Separate categories are defined by uplink and downlink.

[0005] Due to the fact that the device establishes a link with its access node, the category of a given device is effectively provided on a per-device basis. The category advertised by a device, for uplink and downlink, represents only a partial list of that device's total capabilities. An example of a standard that establishes capability parameters on a per-device basis can be found in 3GPP Technical Specification (TS) 36.306, which defines, on a per-device basis (i.e., a per user equipment (UE) basis) , eleven categories for uplink capacity and eleven separate categories for downlink capacity. See 3 GPP TS 36.306 version 12.2.0, Tables 4.1-1 and 4.1-2. The present approach provides advertising on a per-device basis, but not on a per-link basis. Please note that the word “capabilities” as used herein is not intended to be limited to the capabilities identified in 3 GPP TS 36.306 version 12.2.0, Tables 4.1-1 and 4.1-2.

[0006] Consequently, there is a need for a solution (or solutions) that allows devices to allocate and advertise capabilities and/or resources on a per-link basis. For example, it would be desirable to provide a mechanism for devices to advertise capabilities for more than one link (for example, in the case of a device having the ability to establish a first link with an access node and a second link with another device). As another example, it would be desirable to provide a mechanism for advertising the resources that a given device has available to be used to establish a link with a device. As yet another example, it would be desirable to provide a mechanism for determining how the resources of a given device would be allocated between two or more links on a per-link basis. These resources may be, but are not limited to, memory resources, processing power resources, transmitter bandwidth resources, receiver bandwidth resources, number of transmit/receive antennas, and/or a combination of sets. of resources.

SUMMARY

[0007] The following presents a simplified summary of one or more aspects of the present disclosure in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated features of the revelation, and is not intended to identify key or critical elements of all aspects of the revelation nor to delineate the scope of any or all aspects of the revelation. Its sole purpose is to present some concepts of one or more aspects of revelation in a simplified form as a prelude to the more detailed description that is presented later.

[0008] A system of one or more computers, machines and/or devices may be configured to perform specific operations or actions by virtue of having software, firmware, hardware or a combination thereof installed in a system that in operation causes the system performs the actions in this document, and the actions are described in an exemplary or non-limiting manner. One or more computer programs may be configured to perform specific operations or actions by virtue of including instructions that, when executed by the data processing apparatus, cause the apparatus to perform the actions. A general aspect may include a method of operating on a requesting device, which includes: sending a resource discovery query to a local device that requests link resource information available for a wireless link between the requesting device and the local device. The method may also include receiving resource information per link from the local device that indicates resources that the local device has allocated, or has available to allocate, to the wireless link. The method may also include establishing the wireless link with the local device based on the received resource information. Other examples of this aspect may include computer systems, apparatus, and corresponding computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.

[0009] A general aspect may include a requesting device, which includes: a wireless network interface configured to communicate with one or more local devices; a processing circuit coupled to the wireless network interface, the processing circuit is configured to: send a resource discovery query to a first local device that requests available link resource information for a wireless link between the requesting device and the first local device. The requesting device may also receive link resource information from the first local device that indicates the resources that the first local device has allocated, or has available to allocate, to the wireless link; and establishing the wireless link with the first local device based on the received resource information. Other examples of this aspect may include computer systems, apparatus, and corresponding computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.

[0010] A general aspect may include an operating method on a local device, which includes: allocating resources, from a pool of resources available to the local device, on a per-link basis. The method may also include receiving a resource discovery query from a requesting device that searches for available link resource information for a wireless link between the requesting device and the local device; and sending resource information per link to the requesting device that indicates the resources that the local device has allocated, or has available to allocate, to the wireless link. Other examples of this aspect may include computer systems, apparatus, and corresponding computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.

[0011] A general aspect may include a local device, which includes a wireless network interface configured to communicate data traffic with one or more local devices; a processing circuit coupled to the wireless network interface, the processing circuit is configured to: receive a resource discovery query from a requesting device that seeks per-link resource information available for a wireless link between the requesting device and the local device; allocate resources from a pool of resources available to the local device on a per-link basis; and sending resource information per link to the requesting device that indicates the resources that the local device has allocated, or has available to allocate, to the wireless link. Other examples of this aspect may include computer systems, apparatus, and corresponding computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.

[0012] These and other aspects of the revelation will be more fully understood upon review of the detailed description that follows. Other aspects, features and embodiments of the present disclosure will become apparent to those skilled in the art upon review of the following description of specific exemplary embodiments of the present disclosure in conjunction with the attached Figures. Although the features of the present disclosure may be discussed in relation to certain embodiments and Figures below, all embodiments of the present disclosure may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with the various embodiments discussed herein. Similarly, although exemplary embodiments may be discussed below as device, system, or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a block diagram illustrating different ways in which categories (e.g., a set of resources) can be defined. Figure 2 illustrates an exemplary discovery procedure in which category information can be submitted. Figure 3 illustrates an exemplary category update procedure in which a device can update other devices as its category changes. Figure 4 illustrates routing in a multi-hop mode in which there is a single route that is available between an originating device and a terminating device. Figure 5 illustrates routing in a multi-hop mode where there is an aggregated route between the originating device and the terminating device. Figure 6 illustrates an exemplary route discovery procedure in which a device may seek to find a destination (terminating) and/or content device. Figure 7 illustrates another alternative in which an aggregated route category can be recursively determined. Figure 8 illustrates an exemplary device configured for per-link category discovery and per-link route discovery. Figure 9 illustrates another exemplary device configured for per-link category discovery and per-link route discovery. Figure 10 is a flow diagram illustrating a method operating by a originating device to obtain resource information from other devices on a per-link basis. Figure 11 is a flow diagram illustrating a method of operating through a local device to provide resource information to an originating device on a per-link basis. Figure 12 is a flow diagram illustrating a method operating via a local device to provide route discovery to an originating device on a per-link basis.

DETAILED DESCRIPTION

[0013] In the following description, specific details are given to provide a more complete understanding of the embodiments. However, it will be understood by one of those of ordinary skill in the art that the modalities can be practiced without these specific details. For example, circuits may be shown in block diagrams in order to avoid obscuring the embodiments in unnecessary detail. In other instances, well-known circuits, structures, and techniques may not be shown in detail so as not to obscure the embodiments.

[0014] The word “exemplary” is used herein to mean “serve as an example, occurrence or illustration”. Any implementation or modality described herein as "exemplary" should not necessarily be construed as preferential or advantageous over other modalities. Likewise, the term “modalities” does not require that all embodiments include the feature, advantage or mode of operation discussed.

OVERVIEW

[0015] In a wireless communication system in which a wireless mobile device (referred to herein as a “device” or “UE device” for exemplary and non-limiting purposes) can support different wireless links with different endpoints simultaneously or almost simultaneously, the notion of “category” can be dissociated from the device’s capacity. The same or all capabilities and/or resources of a device, including but not limited to parameters associated with the device, may be identified by revealing the device category. However, rather than having a single “category” describe each device on a per-device level, each wireless link supported by the device can be associated with its own category, thereby allowing the use of categories to describe each link. wireless on a per-link level. This also allows for dynamically changing resource allocation/reallocation for wireless links supported by the device. Each category can represent a different combination or allocation of available resources, on a per-link basis, on the device. A wireless link (also referred to herein as a link) may refer to a wireless connection between a transmitter and a receiver. The wireless link may be a point-to-point link. Data traffic through an intermediate access node (e.g. eNodeB) may not be necessary.

[0016] In an example, for a direct link (e.g., a UE device that serves as a hopping device in a multi-hop network), a category for the direct link (associated with the receiving and transmitting entities) can represent the amount of resources that the UE device has available to allocate to this direct link. Another link (for example, a link terminating at the UE device) may have a different category depending on the service and subscription for the UE device. Consequently, the notion of “category” becomes an attribute of each wireless link rather than a single attribute of the UE device.

[0017] Two features disclosed herein include category partitioning and route discovery in the context of device categories per wireless link (i.e., per link).

[0018] In category partitioning, a device (e.g., a UE device) can partition its resources into categories (i.e., sets of resources). In one example, the UE device may partition its resources into: (A) the amount of resources dedicated to its own traffic, and (B) the amount of resources dedicated to forwarding traffic, all on a per-link basis. Categories may not only be determined through physical capabilities and/or features of the UE device on a per-link basis, but may also be determined by other factors such as: (A) Subscription data plan (e.g., in the case of of “sponsored connectivity”), and/or (B) user preference data.

[0019] In route discovery, resources for all devices (e.g., including intermediate devices) via a multi-hop route, on a per-link basis, can be discovered. Consequently, discovery procedures may determine: (A) the set of devices (e.g., UE devices) to traverse to reach a destination device, (B) the resources available on the traversed devices, on a per-link basis, along the route, which may include supporting guaranteed service data rate types (e.g., voice, mission-critical application), and/or (C) the best route or routes to access the data or content sought. For example, multiple routes can be useful for increased reliability (depending on the application), higher aggregate bandwidth, etc. Additionally, when configuring a multi-hop route, discovery procedures can determine whether specific content is available on surrounding devices, thereby avoiding the need to obtain content from a more distant device or location.

EXAMPLE CATEGORY PARTITION

[0020] Figure 1 is a block diagram illustrating a difference between how a device category 102 is traditionally defined in existing systems on a per-device basis versus how categories may be defined using a more sophisticated approach. flexible on a per-link basis 106, 108. In a traditional approach, a device category 102 can be understood to represent a set of resources. In the traditional approach, the device category 102 may be defined to represent a set of resources 104a, 104b, 104c, wherein the set of resources 104a, 104b, and 104c are specified or defined for the device (i.e., resources with a per device basis). In contrast, category partitioning may be done on a per-link basis so that a partition of each resource 110a, 110b, and 110c may be allocated to each link 106 and 108. The pool of resources allocated to a link may be specified or defined for each link established by the device (that is, resources on a per-link basis). Resources can be allocated equally or unequally. In the example of Figure 1, a larger allocation of Resource A 110a is provided to Link 1106 than to Link 2108. A smaller allocation of Resource B 110b is provided to Link 1106 than to Link 2108. An equal allocation of Resource C 110c is provided for Link 1106 and Link 2108. Consequently, the category becomes an attribute of the link rather than the UE device. Note that a link can be a channel and/or a connection at the lowest layer of a protocol stack (e.g., the physical layer) between two devices or nodes (e.g., two UE devices).

[0021] The category for each link on an active wireless link may be updated when other links are created/modified/deleted, thereby removing/adding available resources for each active link. For example, in the case where a new link is to be added (e.g., Link 3, not shown), the resources that are available for such a new link can be obtained from the resources (e.g., Resources A, B, and C ) used to support the operation of pre-existing links (for example, Link 1, Link 2). In this case, by way of example, Resource A may be reallocated in any proportion among Link 1, Link 2, and, to be established, Link 3. A similar reallocation may occur for Resources B and C. An initial allocation of, or a reallocation (e.g., an upgrade) of resources for a given link category 106, 108 may be accomplished by allowing the UE device to advertise its resources, and/or an amount of each resource available for allocation, on wireless links . The initial allocation or reallocation of resources may also be accomplished by allowing the UE device to initiate updates of resource allocations on a per-link basis. Various reporting schemes can be applied such as: (A) control plane (CP) level update/ACK procedure (i.e., a radio resource control (RRC) level procedure), (B) medium access control (MAC) level update (with or without ACK acknowledgment), and/or (C) all resources constituting the category may be reported or only a subset of resources may be reported.

[0022] The amount of resources allocated to each link may not only be dictated by the extent of a UE device's capabilities but also by user preferences (e.g., how much of a UE device's resources a user is willing to devote to forwarding packets from other users/devices on a multi-hop network) or subscription preferences (for example, an operator could bring in a “sponsored connectivity” aspect if the UE device devotes some of its resources to forwarding data on a network multiple hops). In an example, resource allocation may be accomplished by enabling a control plane level configuration of the categories for the UE device links.

[0023] Figure 2 illustrates an exemplary discovery procedure in which category information can be sent from one device to another. A first device A 202 (e.g., user equipment, wireless communication device, subscriber device, mobile device, sensor, connected machine, cordless telephone) may employ a mechanism whereby various attributes of surrounding devices. In a first example, the first device A 202 may send a discovery query 206 to a second device B 204. For example, one such requested attribute may be the forwarding category of the second device B 204, which represents the quantity and/or the types of resources that the second device B 204 has available to forward traffic (i.e., the traffic that the second device B 204 may be willing/able to forward from device A to other devices (not shown)). The category may be a list, or set, of specific resources that may be shared with the requesting device (e.g., first device A 202). In some examples, each category in the list of categories, or set of categories, represents a plurality of resources that can be used, or that may be needed, to establish a link, and can define a quantity of each resource represented by the category. The link can be a point-to-point link. For example, such resources may include, but are not limited to, one or more of memory resources, processing power resources, transmitter bandwidth resources, receiver bandwidth resources, number of transmit/receive antennas, and/or a combination of specific feature sets.

[0024] In another example, the first device A 202 may simply indicate a type of service that it requires (e.g., more effort, time sensitivity, etc.) from the second device B 204.

[0025] In connection with any example (discovery query 206 or service type request), the second B device 204 may respond 208 by indicating its forwarding category and/or whether the service request can be granted.

[0026] Figure 3 illustrates an exemplary category update procedure in which a device can update other devices that its category has changed. For example, a first device A 302 may send a category update 306 to surrounding devices (e.g., second device B 304) that its forwarding category has changed. These category changes and updates may occur, for example, as the first device A 302 adds or removes links. Reasons for a category update by the first A device 302 may include: (A) the first A device 302 has become part of a multi-hop route, (B) another route has changed in strength, (C) changes in resources devoted to the first device A 302's own terminating traffic, and/or (D) changes in resources devoted to the first device A 302's own originating traffic. This list is exemplary and not limiting, as other reasons for an update of category are within the scope of the disclosure.

[0027] To avoid generating too much signaling traffic, in one example, the first device A 302 may send only such category updates to surrounding devices with which the first device A 302 currently has an active link.

[0028] A second B device 304 that receives the category update 306 may then respond with an acknowledgment 308.

EXAMPLE ROUTE DISCOVERY

[0029] Routing discovery may refer to establishing a path through a network from an originating device and a terminating device. Often, such routing involves intermediate hopping devices that forward communications between the originating and terminating devices. According to one example, the originating, terminating, and intermediate hopping devices may each be UE devices. In Figure 4, the UE devices are illustrated as identical devices; however, this was for ease of illustration - nothing described herein limits any set of devices to be identical. In order to determine proper routing for a desired service on an originating device, the resource partition (for each active wireless link) on each device on the route needs to be communicated.

[0030] Figure 4 illustrates routing in a multi-hop mode in which there is a single route that is available between an originating device 402 and a terminating device 404. The route may include one or more intermediate hop devices 406 and 408 between the originating device 402 and the terminating device 404. Links between two devices (e.g., Link A between devices 402 and 406) may be referred to as a link. The overall link from the originating device 402 to the terminating device 404 may be referred to as an end-to-end link. An end-to-end link may include one or more links. A link can originate at the requesting device (which can alternatively be referred to as an originating device in this scenario) and terminate at the local device, or it can originate at the local device and terminate at the originating device. In this way, data traffic can be transmitted to and/or received from an access node network. Links may include point-to-point links.

[0031] In the example of Figure 4, where a single route is available, the “weakest link” principle may be applicable whereby the resources for the weakest (i.e., least available or least capable) link between any two devices on the route determines the end-to-end link capabilities or performance between the originating device 402 and the terminating device 404.

[0032] Figure 5 illustrates routing in a multi-hop mode in which there is an aggregated route between an originating device 502 and the terminating device 504. In this example, a first route may be available through A-B-C links using of intermediate devices 506, 508, while a second route may be available via D-E links using another intermediate device 510. Thus, the first route (through a first set of intermediate devices 506 and 508) and the second route (through a second intermediate device 510) may be aggregated to enable communications between the originating device 502 and the terminating device 504. Communication may occur via the first route, the second route, or both the first and second routes. routes.

[0033] Figure 6 illustrates an exemplary route discovery procedure in which a device may seek to find a terminating device (i.e., a destination device and/or a device that has the desired content (referred to herein as a content device)). For example, a first device A 602 may send a discovery query 606 to a second device B 604, wherein the discovery query 606 seeks to discover a route to a third device (C) (not shown) and/or content. The second device B 604 may be a nearby or surrounding device (also referred to herein as a local device). For example, the second device B 604 may be a specific device on which the communication (e.g., voice, message and/or video) terminates (i.e., the destination device or a terminating device, in which case the third device C and the second device B are the same device). As another example, the second device B 604 may be an intermediate device that can be connected to a broader network (e.g., a gateway device for the Internet). As yet another example, the second device B 604 may be a category of device that may host specific content (e.g., the content may include system information content, any type of control plane content, user plane content and/or any combination thereof).

[0034] Second device B 604 may respond to discovery query 606 with a discovery response 608, which may indicate a known route to the terminating device (i.e., third device C and/or the device having the desired content ), or may indicate that the request has been additionally forwarded.

[0035] Upon receipt of the discovery response 608 from the second B device 604, the first A device 602 may query each device identified in the discovery response 608 (i.e., each device indicated as being on a known route to the terminating device). for its category (e.g. resource pool and/or resource allocations) and can synthesize an aggregated route category and/or metric. The aggregated route category can be synthesized, for example, according to the “weakest link” principle described in conjunction with Figure 4, above, or it can be synthesized using different metrics or combination of metrics such as route reliability. link, aggregate bandwidth, aggregate delay and/or other modes known to those skilled in the art. By way of example, not limitation, the aggregated route metric may reflect a sum total of route categories, an average of the sum total of route categories, numerous hops on a given route, different metrics, or combination of metrics such as reliability link capacity, aggregate bandwidth, aggregate delay and/or a combination of these and/or other metrics. In one example, such a query for the category of each device along the discovered route may be performed by the first device A 602 and each device along the route. Alternatively, this query may be performed by a device other than the first device A 602.

[0036] Figure 7 illustrates an alternative in which an aggregate route category can be recursively determined. According to Figure 7, a first device A 702 may send a discovery query 706 to a second device B 704. The discovery query 706 may seek to query each device identified in a discovery response (e.g., 608, Figure 6 ) (e.g., each device indicated as being on a known route from device A 702 to destination device N 707) for its category (e.g., resource set and/or resource allocations). Alternatively or additionally, discovery request 706 may include a service request. The second device B 704 may be a nearby or surrounding device (also referred to herein as a local device). In the example of Figure 7, the second device B 704 (i.e., the local device B 704) may send one or more discovery queries 710 forward to facilitate the recursive determination of the aggregated route category. For ease of illustration, sending the one or more discovery queries 710 forward is depicted as an action from local device B 704 to destination device N 707. It is understood that discovery query 710 may represent multiple discovery queries that flow forward through multiple links between multiple intermediate devices (not shown) between the local device B 704 and the destination device N 707. The links may include point-to-point links.

[0037] Upon receipt of discovery query 710, target device N 707 may respond with a discovery response 712. Discovery response 712 may include an indication of a target device category N 707 for use in recursively determining the aggregate route category. For ease of illustration, sending the one or more discovery responses 712 in a return direction is depicted as an action from device N 707 to device N 704. It is understood that discovery response 712 may represent multiple discovery responses which flow in the return direction through the multiple links between the multiple intermediate devices (not shown) between the destination device N 707 and the local device B 704. The links may include point-to-point links. By way of example, an aggregate route category may be recursively determined by receiving, at each intermediate device along the route from destination device N 707 to local device B 704, the category of a subsequent device. The subsequent device category can be expressed as a recursively determined aggregated route category of all subsequent devices including destination device N 707. At the intermediate device, the received category (or aggregated route category of all subsequent devices including the destination device destination N 707) can be combined with the intermediate device category to determine a new aggregate route category. The new aggregated route category may then be forwarded to a preceding device for a further iteration in determining the aggregated route category, until the result reaches the local device B 704. The requesting device A 702 may then receive a discovery response 708 from local device B 704. The discovery response 708 may include the aggregated route category for devices B 704 to N 707, inclusive. The aggregate route category for devices B 704 to N 707 inclusive may be determined by combining the aggregate route category received at the local device B 704 with the category of the local device B 704 in a recursive manner.

EXAMPLE WIRELESS DEVICES, GENERALLY

[0038] In a wireless multi-hop system, one or more wireless devices (hereinafter device or devices) may be dispersed throughout the geographic area. Wireless communication between two adjacent devices in a wireless multi-hop system can be implemented as communication at the lowest level of a protocol stack (for example, the Layer 1, physical layer in the Interconnection Model protocol stack). Open Systems (OSI), the Layer 1, physical layer (PHY) in the Long Term Evolution (LTE) protocol stack and/or in general, the lowest layer related to over-the-air radio transmissions in a given stack. protocols). Communication can be point-to-point communication. In some examples, wireless communication in a wireless multi-hop system may be directed to cellular wireless systems that deploy devices configured for wireless multi-hop operation.

[0039] Devices in a wireless multi-hop system may use wireless signals to communicate with one or more other wireless devices in the multi-hop system. Wireless signals can be in the form of radio waves. Other wireless signals, such as those in the form of infrared waves, are within the scope of this disclosure. Two devices in each other's range can establish a physical layer wireless link between them. The link can be a point-to-point link. The physical layer wireless link may be limited to the lowest layer of a protocol stack. A physical layer wireless link that joins two adjacent devices may be referred to herein as a wireless link, or a link. Two devices that are within each other's range (e.g., the link cannot be established or have less than desired quality due to, for example, distance or interference) can nevertheless communicate by establishing links with a or more intermediate devices.

[0040] For example, if a first wireless device is required to transfer or obtain data from a second wireless device, or otherwise communicate with the same, but the first and second wireless devices cannot establish a link directly between them, the first wireless device (e.g., the originating device) can communicate with the second wireless device (e.g., the terminating device) through one or more intermediate wireless devices (e.g. example, intermediate devices). In a case where a single intermediate device is in range of the originating and terminating devices, but the originating and terminating devices are not in range of each other, the originating device may establish a first link with the single intermediate device and the single intermediate device can establish a second link with the terminating device.

[0041] According to the wireless multi-hop system examples described herein, a route for communication between two devices, regardless of the need for any intermediate devices, does not require the route to pass through a central connection or bus. As explained above, according to the examples described herein, the discovery and selection of communication routes on a per-link basis can be performed dynamically at the device level.

[0042] Devices (i.e., wireless devices) may be referred to by those skilled in the art by various names, including, for example, and without limitation, a wireless device, mobile device, a device, a user equipment ( UE), a UE device, a device, a station, a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a wireless communications device , a remote device, a mobile subscriber station, a terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or other suitable terminology.

[0043] Examples of mobile wireless devices may include a mobile telephone, a pager, a personal digital assistant (PDA), a personal information manager (PIM), a personal media player, a palmtop computer, a laptop type, a tablet type computer, an e-reader and/or other mobile computing/communication devices that communicate over a wireless or cellular network.

[0044] Examples of typically non-mobile devices that may include wireless communication circuits may include a wireless modem, a wireless access point (AP), a television, an appliance, a digital video recorder (DVR) , any device included in an Internet of Things (IOT) network.

[0045] For exemplary purposes, the examples of multi-hop systems described in this document depict multi-hop systems that include mobile devices; however, multi-hop systems may include one or more non-mobile devices in addition to mobile devices without departing from the scope of the disclosure.

EXEMPLIFICATION ORIGINAL DEVICE (REQUEST)

[0046] Figure 8 illustrates an exemplary wireless device 802 configured for per-link category discovery and per-link route discovery. The wireless device 802 may be operative as a device that originates discovery queries for a first wireless link. It should be noted that the wireless device 802, while operating on a first wireless link with a second device (not shown) as an originating device, may additionally operate on a second wireless link with a third device (not shown) as an originating device. an intermediate or terminating device in conjunction with a wireless link to the third device.

[0047] As used herein, an originating device may be referred to as a requesting device. An intermediate or terminating device may be referred to as a local device.

[0048] The exemplary wireless device 802 of Figure 8 may include a wireless network communication interface/circuit 804, one or more processing circuits 806, and a memory/storage device 808 that are operatively coupled between yes. In the exemplary illustration of Figure 8, the wireless network communication interface/circuitry 804, processing circuit(s) 806, and memory/storage device 808 are operatively coupled via at least one wireless communication bus. two-way 830 that can be accessed by all modules, circuits and/or functions, such as communication buses 830 are well understood and will not be explained in this document. The wireless network communication interface/circuitry 804, one or more processing circuitry 806, and memory/storage device 808 are described below.

EXAMPLE WIRELESS NETWORK COMMUNICATION INTERFACE/CIRCUIT

[0049] The wireless network communication interface/circuit 804 may serve to couple the wireless device 802 to one or more networks, e.g., network A 801 and/or network B 803 with the use of one or more wireless access technologies that facilitate the establishment of a wireless link to other devices. In this manner, the wireless network communication interface/circuitry 804 may be configured to facilitate wireless communications from the wireless device 802. For example, the wireless network communication interface/circuitry 804 may include circuitry and /or adapted programming to facilitate bidirectional information communication with respect to one or more wireless UE devices on Network A 801 and/or Network B 803. Wireless network communication interface/circuitry 804 may include a or more receiver module/circuit/functions 824, one or more transmitter module/circuit/functions 826, and/or one or more antenna module/circuit/functions 828. The receiver (or receivers) 824, transmitter (or transmitters) 826, and antenna (or antennas) 828 may be operatively coupled together. The one or more antennas 828 may facilitate wireless communication with the one or more wireless UE devices in Network A 801 and/or Network B 803.

EXAMPLE PROCESSING CIRCUIT (OR CIRCUITS)

[0050] One or more processing circuits 806 may be operatively coupled to the wireless network communication interface/circuit 804. For ease of illustration, a processing circuit 806 is illustrated. The processing circuit 806 may include a link establishment module/circuit/function 810, a category discovery module/circuit/function 814, and/or a route discovery module/circuit/function 812. The processing circuit 806 may be arranged to obtain, process and/or send data, control access and storage of data, issue commands and control other desired operations. Processing circuitry 806 may include circuitry adapted to implement desired programming provided by suitable non-transient media in at least one example. For example, processing circuitry 806 may be deployed as one or more processors, one or more controllers, and/or other structures configured to perform executable programming. Examples of processing circuit 806 may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic component. discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may include a microprocessor as well as any conventional processor, controller, microcontroller, or state machine. Processing circuit 806 may also be implemented as a combination of computing components, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, an ASIC and a microprocessor, or any another number of variant configurations. These examples of processing circuit 806 are for illustration and other suitable configurations within the scope of the present disclosure are also contemplated.

[0051] Processing circuit 806 may be adapted for processing, including executing programming, which may be stored in memory/storage device 808. As used herein, the term “programming” may be interpreted broadly to include , but not limited to, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to software, firmware, middleware, microcode, hardware description language or otherwise.

EXAMPLE MEMORY/STORAGE DEVICE

[0052] The memory/storage device 808 may be operably coupled to the processing circuit (or circuits) 806 and may also be operably coupled to the network communication interface/circuit 804. The memory/device storage instructions 808 may include link establishment instructions 818, route discovery instructions 820 and/or category discovery instructions 822.

[0053] Memory/storage device 808 may include one or more non-transient computer-readable, machine-readable, and/or processor-readable devices for storing programming, such as processor-executable code or instructions (e.g., software, firmware), electronic data, databases or other digital information. The memory/storage device 808 can also be used to store data that can be manipulated by the processing circuit 806 when performing programming. Memory/storage device 808 may be any available non-transient media that can be accessed by a general-purpose processor or special-purpose processor, including portable or fixed storage devices, optical storage devices, and various other adapted non-transient media. to store, contain and/or load programming. By way of example, and not limitation, memory/storage device 808 may include a non-transient computer-readable, machine-readable, and/or processor-readable storage medium such as a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical storage device (e.g., compact disc (CD), digital versatile disc (DVD)), a magnetic card, a flash memory device (e.g., card, stick, pen drive) , random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), a register, a removable disk and/or other media for storage non-transient programming, as well as any combination thereof.

[0054] The memory/storage device 808 may be coupled to the processing circuit 806 so that the processing circuit 806 can read information from the memory/storage device 808 and write information thereto. That is, the memory/storage device 808 may be coupled to the processing circuitry 806 so that the memory/storage device 808 may be at least accessible by the processing circuitry 806, including examples where the memory/storage device Storage 808 may be integral to processing circuitry 806 and/or examples where memory/storage device 808 may be separate from processing circuitry 806.

[0055] Programming stored by memory/storage device 808, when executed by processing circuit 806, may cause processing circuit 806 to perform one or more of the various functions and/or process steps described herein. Thus, in accordance with one or more aspects of the present disclosure, the processing circuit 806 may be adapted to perform (in conjunction with the memory/storage device 808) any or all of the processes, functions, steps and/or the routines associated with the exemplary wireless device 802 described herein. As used herein, the term “adapted” in relation to processing circuit 806 may refer to processing circuit 806 that is one or more of configured, employed, deployed and/or programmed (in conjunction with the memory/device 808) to perform a specific process, function, step and/or routine in accordance with various features described herein.

EXEMPLIFYING TERMINATION DEVICE (LOCAL, INTERMEDIATE, DESTINATION, CONTENT)

[0056] Figure 9 illustrates an exemplary wireless device 902 configured for per-link category discovery and per-link route discovery. The wireless device 902 may be operational as a local device that receives and responds to discovery queries and responses between devices, as an intermediary device and/or as a device that terminates discovery queries, as a target device and/or of content.

[0057] Nothing in this document prevents exemplary wireless device 902 from being operational as an originating (requesting) device.

[0058] The exemplary wireless device 902 of Figure 9 may include a wireless network communication interface/circuit 904, one or more processing circuits 906, and a memory/storage device 908 that are operatively coupled between yes. In the exemplary illustration of Figure 9, wireless network communication interface/circuitry 904, processing circuit(s) 906, and memory/storage device 908 are operatively coupled via at least one communication bus. two-way modules 930 that can be accessed by all modules, circuits and/or functions, such as communication buses 930 are well understood and will not be explained in this document. The wireless network communication interface/circuitry 904, one or more processing circuitry 906, and memory/storage device 908 are described below.

EXAMPLE WIRELESS NETWORK COMMUNICATION INTERFACE/CIRCUIT

[0059] The wireless network communication interface/circuit 904 may serve to couple the wireless device 902 to one or more networks, e.g., network A 901 and/or network B 903 with the use of one or more wireless access technologies that facilitate the establishment of a wireless link to other devices. In this manner, the wireless network communication interface/circuit 904 may be configured to facilitate wireless communications from the wireless device 902. For example, the wireless network communication interface/circuit 904 may include circuitry and /or adapted programming to facilitate bidirectional information communication with respect to one or more wireless UE devices (e.g., devices) on Network A 901 and/or Network B 903. The network communication interface/circuit wireless network 904 may include at least one receiver module/circuit/function 924 and/or at least one transmitter module/circuit/function 926. The wireless network communication interface/circuit 904 may also include one or more modules antenna/circuitry/function 928 operatively coupled to the at least one receiver 924 and/or at least one transmitter 926. The one or more antennas 928 may facilitate wireless communication with the one or more wireless UE devices (e.g. e.g. devices) on Network A 901 and/or Network B 903.

EXAMPLE PROCESSING CIRCUIT (OR CIRCUITS)

[0060] One or more processing circuits 906 may be operatively coupled to the wireless network communication interface/circuit 904. For ease of illustration, a processing circuit 906 is illustrated. The processing circuit 906 may include a resource allocation with a per-link base module/circuit/function 909, a link establishment module/circuit/function 910, a route discovery module/circuit/function 912, and/or a category discovery module/circuit/function 914. Processing circuit 906 may be arranged to obtain, process and/or send data, control data access and storage, issue commands, and control other desired operations. Processing circuitry 906 may include circuitry adapted to implement desired programming provided by suitable non-transient media in at least one example. For example, processing circuitry 906 may be deployed as one or more processors, one or more controllers, and/or other structures configured to perform executable programming. Examples of processing circuit 906 may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic component. discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may include a microprocessor as well as any conventional processor, controller, microcontroller, or state machine. Processing circuit 906 may also be implemented as a combination of computing components, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, an ASIC and a microprocessor, or any another number of variant configurations. These examples of processing circuit 906 are for illustration and other suitable configurations within the scope of the present disclosure are also contemplated.

[0061] Processing circuit 906 may be adapted for processing, including executing programming, which may be stored in memory/storage device 908. As used herein, the term “programming” may be interpreted broadly to include , but not limited to, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to software, firmware, middleware, microcode, hardware description language or otherwise.

EXAMPLE MEMORY/STORAGE DEVICE

[0062] The memory/storage device 908 may be operably coupled to the processing circuit (or circuits) 906 and may also be operably coupled to the network communication interface/circuit 904. The memory/device storage instructions 908 may include resource allocation in link-based instructions 917, link establishment instructions 918, route discovery instructions 920 and/or category discovery instructions 922.

[0063] Memory/storage device 908 may include one or more non-transient computer-readable, machine-readable, and/or processor-readable devices for storing programming, such as code or processor-executable instructions (e.g., software, firmware), electronic data, databases or other digital information. The memory/storage device 908 can also be used to store data that can be manipulated by the processing circuit 906 when performing programming. Memory/storage device 908 may be any available non-transient media that can be accessed by a general-purpose processor or special-purpose processor, including portable or fixed storage devices, optical storage devices, and various other non-transient media adapted to store, contain and/or load programming. By way of example, and not limitation, memory/storage device 908 may include a non-transient computer-readable, machine-readable, and/or processor-readable storage medium such as a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical storage device (e.g., compact disc (CD), digital versatile disc (DVD)), a magnetic card, a flash memory device (e.g., card, stick, pen drive) , random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), a register, a removable disk and/or other media for storage non-transient programming, as well as any combination thereof.

[0064] The memory/storage device 908 may be coupled to the processing circuit 906 so that the processing circuit 906 can read information from the memory/storage device 908 and write information thereto. That is, the memory/storage device 908 may be coupled to the processing circuitry 906 so that the memory/storage device 908 may be at least accessible by the processing circuitry 906, including examples where the memory/storage device Storage 908 may be integral to processing circuitry 906 and/or examples where memory/storage device 908 may be separate from processing circuitry 906.

[0065] Programming stored by memory/storage device 908, when executed by processing circuit 906, may cause processing circuit 906 to perform one or more of the various functions and/or process steps described herein. Thus, in accordance with one or more aspects of the present disclosure, the processing circuit 906 may be adapted to perform (in conjunction with the memory/storage device 908) any or all of the processes, functions, steps and/or the routines associated with the exemplary device 902 described herein. As used herein, the term “adapted” in relation to processing circuit 906 may refer to processing circuit 906 that is one or more of configured, employed, deployed and/or programmed (in conjunction with the memory/device storage 908) to perform a specific process, function, step and/or routine in accordance with various features described herein.

EXEMPLIFICATION METHODS OF OPERATION

[0066] Three methods of operation are described below with reference to Figures 10, 11 and 12. Each method of operation may be operative on a device utilizing, for example, the exemplary wireless devices of Figures 8 and/or 9. Each method of operation may be operational on an originating, intermediate and/or terminating device. However, for explanatory purposes, the method of Figure 10 is described with respect to an originating device identified as a requesting device and the methods of Figures 11 and 12 are described with respect to an intermediate device or a terminating device collectively identified as a local device.

EXAMPLE METHOD FOR OBTAINING RESOURCE INFORMATION ON A PER-LINK BASIS

[0067] Figure 10 is a flow diagram illustrating a method 1000 operational by a originating device (referred to, for explanatory purposes, as a requesting device) to obtain resource information on a per-link basis from a local device (referred to as a requesting device). for explanatory purposes, as a local device) for a wireless link between the requesting device and the local device. The method may begin at 1002, wherein the requesting device may send, to the local device, a resource discovery query that requests available link resource information for a wireless link between the requesting device and the local device. The request for resource information on a per-link basis may be a request for resources that are available from the local device to the wireless link between the requesting device and the local device. The wireless link can be a new wireless link or an upgraded wireless link.

[0068] At 1004, in response, the requesting device may receive per-link resource information from the local device that indicates the resources that the local device has available to allocate and/or has allocated to the wireless link on a per-link basis before to establish the link. The response may be indicative of the reorganization (e.g., by reallocating resources) by the local device of resources that include resources in use for pre-existing links and resources to be allocated to, for example, the wireless link.

[0069] At 1006, the requesting device may then establish the wireless link with the local device based on the received resource information. The wireless link between the requesting device and the local device may be a point-to-point wireless link. The point-to-point wireless link may be one of a plurality of wireless links established by the requesting device.

EXAMPLE METHOD FOR PROVIDING RESOURCE INFORMATION ON A PER-LINK BASIS

[0070] Figure 11 is a flow diagram illustrating a method 1100 operating via a wireless device in accordance with the disclosure (referred to for explanatory purposes as a local device) for providing resource information on a per-link basis to an originating device (referred to for explanatory purposes as a requesting device) for a wireless link between the requesting device and the local device. The method may begin at 1102, wherein the local device may receive, from the requesting device, a resource discovery query that searches for link resource information on available resources for a wireless link between the requesting device and the local device. The wireless link can be a new wireless link or an upgraded wireless link.

[0071] At 1104, the local device may allocate (e.g., pre-allocate, reserve, or set aside) or reallocate resources to the requesting device on a per-link basis, from a pool of resources available to the local device. Allocation/relocation allows the local device to support the operation of pre-existing links and future operation of the wireless link. The resources available to the requesting device may depend on the amount of each resource in the local device's resource pool that the local device agrees to allocate, and then allocates, to the wireless link associated with the requesting device. The resources available to the requesting device may, additionally or alternatively, depend on the amount of each resource already allocated to n other links, where n > 0, that may be currently active on the local device. The resources available to the requesting device may be impacted by the resources already allocated to the other n links. Additionally or alternatively, the local device may change, or negotiate to change, the amount of resources already allocated to one or more of the n other links that are currently active on the local device. In this way or other ways, the local device may have the ability to obtain a given level of resources for an n+1th link to be established with the requesting device. According to this exemplary method, the local device may determine the resources that it can agree to allocate on a per-link basis with the requesting device and allocate (e.g., pre-allocate, reserve, or set aside) those resources before the link is established. For example, by pre-allocating, reserving, or setting aside resources for a requested wireless link with the requesting device, the local device can ensure an ability to accommodate the requested wireless link. The requested wireless link may be a link in addition to the n links that may be currently active on the local device, if or when the requested link is established. In an alternative example, the local device may allocate resources on a per-link basis (e.g., in anticipation of serving a predetermined number of links) before receiving, from the requesting device, a resource discovery query that seeks per-link resource information. link in resources available for a wireless link between the requesting device and the local device. In the alternative example, the resources available to the requesting device may depend on one or more of the same factors discussed above.

[0072] At 1106, the local device may send a message representative of the link resources that it has available to allocate to the wireless link that may be established between the requesting device and the local device. The message may be indicative of the reorganization (e.g., through reallocation) by the local device of resources that include resources in use for pre-existing links and resources to be allocated to, e.g., the requested wireless link. A reallocation may be necessary if, for example, a first allocation of a first resource between links varies with respect to a second allocation of a second resource between links.

[0073] At 1108, the local device may then establish the requested wireless link with the requesting device based on the resource information sent to the requesting device.

[0074] At 1110, the updated resource information may be sent to the requesting device and/or any other of the n devices with which the local device has an active link (e.g., an active wireless link), wherein the Updated resource information may reflect a dynamic change in the division of at least one resource that is used to maintain an active wireless link with the local device. Additionally, updated resource information may be sent to the access node if the local device has an active link (e.g., an active wireless link) with the access node. Each link can be a point-to-point link.

[0075] The wireless link between the requesting device and the local device may be a point-to-point wireless link. The point-to-point wireless link may be one of a plurality of wireless links established by the local device.

EXAMPLE METHOD FOR OBTAINING ROUTE DISCOVERY INFORMATION ON A PER-LINK BASIS

[0076] Figure 12 is a flow diagram illustrating a method 1200 operational by an originating device (referred to, for explanatory purposes, as a requesting device) to obtain route discovery information on a per-link basis from a local device ( referred to, for explanatory purposes, as a local device) for a route to a destination device and/or a content device.

[0077] The method may begin at 1202, wherein a wireless link between a requesting device and a local device may be established. At 1204, the requesting device may send, to the local device, a route discovery query that requests routing information for a destination device and/or a content device. At 1206, in response, the requesting device may receive routing information from the local device that indicates a route to the destination device and/or content device. Such routing information may identify one or more intermediate devices along a route to reach the destination device and/or content device.

[0078] At 1208, the requesting device may send a resource discovery query to each of the one or more intermediate devices identified in the routing information, wherein the information may be sent to the destination device and/or the receiving device. content.

[0079] At 1210, the requesting device may receive a response that includes resource information from each of the one or more intermediate devices identified in the routing information and from the destination device and/or the content device. The resource information may identify the resources allocated (e.g., pre-allocated, reserved, or separated) or reallocated on a per-link basis by each of the one or more intermediate devices, prior to establishing an end-to-end link. Each response may be indicative of a reorganization (e.g., by way of reallocation) of resources, on the respective one or more intermediate devices and the destination device, wherein the reorganization of resources may include the reallocation of resources used for pre-links. existing resources and resources to be allocated for, for example, the wireless link.

[0080] At 1212, the requesting device may establish the end-to-end wireless link from the requesting device, through the first local device and the one or more intermediate devices, to the destination device and/or content device with based on the resource information received for each intermediate device and for the target device and/or content device. The end-to-end link may include multiple links between two or more intermediate devices. The multiple links may include at least one point-to-point link.

[0081] At 1214, the requesting device may aggregate one or more routes between the requesting device and the destination device and/or the content device and transmit or receive information (e.g., data traffic) between the requesting device and the target device and/or content device.

[0082] One or more of the components, steps, characteristics and/or functions illustrated in the Figures may be rearranged and/or combined into a single component, step, resource or function or incorporated into several components, steps or functions. Elements, components, steps and/or functions may also be added without departing from the innovative features disclosed in this document. The apparatus, devices and/or components illustrated in the Figures may be configured to perform one or more of the methods, features or steps described in the Figures. The innovative algorithms described in this document can also be efficiently implemented in software and/or embedded in hardware.

[0083] Also, it is noted that the examples can be described as a process depicted as a flowchart, a flow diagram, a structure diagram or a block diagram. Although a flowchart may describe operations as sequential processing, many of the operations may be performed in parallel or concurrently. Furthermore, the order of operations can be rearranged. A process can be terminated when its operations are complete. A process can correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process matches a function, its termination corresponds to a return from the function to the calling function or the main function.

[0084] Furthermore, a storage medium may represent one or more devices for storing data, including read-only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices and/or other machine-readable media, processor-readable media and/or computer-readable media for storing information. The terms “machine-readable medium,” “computer-readable medium,” and/or “processor-readable medium” may include, but are not limited to, non-transitory media such as portable or fixed storage devices, optical storage devices, and various other media with capacity to store, contain or carry instruction (or instructions) and/or data. Accordingly, the various methods described herein may be fully or partially implemented by instructions and/or data that may be stored on a “machine-readable medium,” “computer-readable medium,” and/or “processor-readable medium.” ” and executed by one or more processors, machines and/or devices.

[0085] Furthermore, examples can be implemented using hardware, software, firmware, middleware, microcode or any combination thereof. When implemented in software, firmware, middleware, or microcode, program code or segments of code to perform necessary tasks may be stored on a machine-readable medium such as a storage medium or other storage (or stores). The processor can perform the necessary tasks. A code segment can represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program definitions. A code segment can be coupled to another code segment or a hardware circuit when passing and/or receiving information, data, arguments, parameters or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded or transmitted through any suitable means which include memory sharing, message passing, token passing, network transmission, etc.

[0086] The various illustrative logic blocks, modules, circuits, elements and/or components described in connection with the examples disclosed herein may be implemented or realized with a general purpose processor, a digital signal processor (DSP), a application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic component, discrete gate or transistor logic, hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be deployed as a combination of computing components (e.g., a combination of a DSP and a microprocessor, numerous microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0087] The methods or algorithms described in connection with the examples disclosed in this document may be incorporated directly into hardware, into a software module executable by a processor, or in a combination of both, in the form of a processing unit, instruction instructions. programming or other directions, and may be contained on a single device or distributed across multiple devices. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to the processor so that the processor can read information from the storage medium and write information thereto. Alternatively, the storage medium may be integral to the processor.

[0088] Those skilled in the art will further note that the various illustrative logic blocks, modules, circuits and algorithm steps described in conjunction with the examples disclosed herein can be implemented as electronic hardware, computer software or combinations thereof. To illustrate this interchangeability of hardware and software, several illustrative components, blocks, models, circuits and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular design and ordering constraints imposed on the overall system.

[0089] The various features of the examples described in this document can be implemented in different systems without departing from the scope of the disclosure. It should be noted that the foregoing examples are merely examples and should not be construed as limiting the invention. The description of the examples is intended to be illustrative, and not to limit the scope of the claims. Thus, the present teachings can be readily applied to other types of apparatus and many alternatives, modifications and variations will be apparent to those skilled in the art.

Claims (14)

1. Operating method on a requesting device (402,502,802), comprising: establishing (1202) a wireless link with a local device (902); characterized by: sending (1204) a route discovery query to a local device (902) that requests routing information to a destination device (404,504) and/or to a content device (404,504); receiving (1206) routing information from the local device (902) indicating a route to a destination device (404,504) and/or to the content device (404,504); and sending (1208) resource discovery queries to each intermediate device (406,408,506,508,510) identified in the routing information and to the destination device and/or to the content device, the resource discovery queries requesting resource information for each device intermediary (406,408,506,508,510) along the route to reach the destination device (404,504) and/or the content device (404,504), and resource information for the destination device (404,504) and/or the content device (404,504) , and resource information for the target device (404,504) and/or the content device (404,504); receive (1210) resource information on a per-link basis for each intermediate device (406,408,506,508,510) and for the destination device (404,504) and/or for the content device (404,504) indicating resources that each device has allocated on the wireless link, prior to establishing an end-to-end wireless link; establish (1212) an end-to-end wireless link, from the requesting device (402,502,802), through the local device (902) and one or more intermediate devices (406,408,506,508,510), to the destination devices (404,504) and/or for the content devices (404,504) based on the resource information received by each intermediate device (406,408,506,508,510) and for each destination device (404,504) and/or for the content devices (404,504), the end-to-end wireless link edge including multiple links between two or more intermediate devices (406,408,506,508,510); and aggregating (1214) one or more routes between the requesting device (402,502,802) and the destination device (404,504) and/or the content device (404,504) to transmit information between the requesting device (402,502,802) and the destination device ( 404,504) and/or the content device (404,504). 2. Method according to claim 1, characterized by the fact that the requesting device and the local device are mobile wireless devices or cellular wireless devices. 3. Method according to claim 1, characterized by the fact that the wireless link either originates at the requesting device and terminates at the local device or originates at the local device and terminates at the requesting device or is at a lower level of a protocol stack. 4. The method of claim 1, further comprising: receiving updated resource information, wherein the updated resource information reflects a dynamic change in an amount of at least one resource used for the wireless link between the requesting device and the local device. 5. Requesting device (402,502,802), comprising: a wireless network interface configured to communicate with one or more local devices; a processing circuit coupled to the wireless network interface, the processing circuit being configured to: establish (1202) a wireless link with a local device (902); characterized in that the processing circuit is further configured to: send (1204) a route discovery query to a local device (902) that requests routing information to a destination device (404,504) and/or to a content device (404,504); receiving (1206) routing information from the local device (902) indicating a route to a destination device (404,504) and/or to the content device (404,504); and sending (1208) resource discovery queries to each intermediate device (406,408,506,508,510) identified in the routing information and to the destination device (404,504) and/or to the content device (404,504), the resource discovery queries requesting resource information for each intermediate device (406,408,506,508,510) along the route to reach the destination device (404,504) and/or the content device (404,504), and resource information for the destination device (404,504) and/or to the content device (404,504), and resource information for the target device (404,504) and/or the content device (404,504); receive (1210) resource information on a per-link basis for each intermediate device (406,408,506,508,510) and for the destination device (404,504) and/or for the content device (404,504) indicating resources that each device has allocated on the wireless link, prior to establishing an end-to-end wireless link; establish (1212) an end-to-end wireless link, from the requesting device (402,502,802), through the local device (902) and one or more intermediate devices (406,408,506,508,510), to the destination devices (404,504) and/or for the content devices (404,504) based on the resource information received by each intermediate device (406,408,506,508,510) and for each destination device (404,504) and/or for the content devices (404,504), the end-to-end wireless link edge including multiple links between two or more intermediate devices (406,408,506,508,510); and aggregating (1214) one or more routes between the requesting device (402,502,802) and the destination device (404,504) and/or the content device (404,504) to transmit information between the requesting device (402,502,802) and the destination device ( 404,504) and/or the content device (404,504). 6. Method of operating on a local device (902), characterized by the fact that it comprises: receiving (1102) a resource discovery query from a requesting device (402,502,802) that seeks per-link resource information available for a wireless link between the requesting device (402,502,802) and the local device (902); reallocating (1104) resources from a pool of resources available to the local device (902), on a per-link basis, to support the operation of pre-existing links and the wireless link; and sending (1106) resource information per link to the requesting device (402,502,802) which indicates the resources allocated by the local device (902) to support the operation of the wireless link before establishing the wireless link; receiving a route discovery query from the requesting device (402,502,802) that requests routing information for a destination device (404,504) and/or for a content device (404,504). sending routing information to the requesting device (402,502,802) that indicates a route to the destination device and/or the content device; recursively determining, at the local device (902), resource information and/or routing information for devices between the local device (902) and the target device (404,504) and/or the content device (404,504); aggregate resource information and/or routing information; send the resource information and/or the aggregated routing information to the requesting device (402,502,802); and establishing the wireless link with the requesting device based on the sent resource information. 7. Method according to claim 1 or 6, characterized in that the wireless link is a new wireless link or an updated wireless link or a point-to-point link. 8. The method of claim 6, wherein relocating resources on a per-link basis includes either dividing each resource that the local device has available between a first link and a second link or allocation between wireless links terminating at the local device and wireless links dedicated to forwarding traffic to other devices. 9. The method of claim 6, wherein the resource information includes both two or more of memory resources, processing power resources, transmitter bandwidth resources and/or bandwidth resources. receiver bandwidth that the local device has available to allocate for the wireless link with the requesting device or is expressed as a category in a set of categories, and each category in the set of categories represents a plurality of resources used to establish the link and define a quantity of each resource represented through the category. 10. The method of claim 6, wherein the local device allocates each resource in the resource pool between at least one first wireless link and a second wireless link, wherein the first wireless link is between the requesting device and the local device and the second wireless link is between the local device and an access node. 11. The method of claim 10, wherein a first allocation of a first resource between the first and second links varies with respect to a second allocation of a second resource between the first and second links. 12. The method of claim 10, wherein the resources in the resource pool are shared between the first and second wireless links or at least two resources in the resource pool are equally shared between the first and the second wireless link. second wireless links. 13. Local device (902), characterized in that it comprises: a wireless network interface configured to communicate traffic data with one or more local devices; a processing circuit coupled to the wireless network interface, the processing circuit being configured to: receive a discovery query from a requesting device (402,502,802) that searches for per-link resource information available for a wireless link between the requesting device ( 402,502,802) and the local device (902); reallocating resources from a pool of resources available to the local device (902), on a per-link basis, to support the operation of pre-existing links and the wireless link; and sending resource information per link to the requesting device (402,502,802) that indicates the resources allocated by the local device (902) to support the operation of the wireless link before establishing the wireless link; receiving a route discovery query from the requesting device (402,502,802) that requests routing information for a destination device (404,504) and/or for a content device (404,504). sending routing information to the requesting device (402,502,802) that indicates a route to the destination device and/or the content device; recursively determining, at the local device (902), resource information and/or routing information for devices between the local device (902) and the target device (404,504) and/or the content device (404,504); aggregate resource information and/or routing information; send the resource information and/or the aggregated routing information to the requesting device (402,502,802); and establishing the wireless link with the requesting device based on the sent resource information. 14. Computer-readable memory, characterized by the fact that it comprises instructions stored therein that, when executed, cause a computer to execute the method, as defined in any one of claims 1 to 4 or 6 to 12.