Device coordination for device-centric sidelink resource allocation

Abstract

A first device (103, 115, 301, 401) and a second device (303, 401), both operating in a communication network (101), communicate with each other via a sidelink communication (105), a sidelink communication resource (111) being allocated by the communication network (102) and being communicated to at least one of the first device (103, 115, 301, 401) and the second device (303, 402). The first device (103, 115, 301, 401) transmits (205, 315, 501) sidelink context information to the application server (113, 305), where the sidelink context information is related to the sidelink communication (105). A first device (103, 115, 301, 401) receives (317, 503) a communication from an application server (113, 305), the communication comprising information identifying one or more communication resources within at least one set of communication resources (111) allocated by a network to be used during a sidelink communication (105) with a second device (303, 401). The first device (103, 115, 301, 401) performs one or both of a first action (505) and a second action (507), where the first action (505) comprises: configuring (509) a transceiver of the first device (103, 115, 301, 401) to use a communication resource identified by a communication received from an application server (113, 305); and using (511) the configured transceiver when communicating with the second device (303, 401) via the sidelink. The second action (507) comprises transmitting (513) information about the identified communication resource to the second device (303, 401) for use in performing the sidelink communication (105) between the first device (103, 115, 301, 401) and the second device (303, 401).

Description

Background Technology

[0001] The present invention relates to secondary link communication between devices such as user equipment in a communication network, and more specifically, to allocating spectrum resources for secondary link communication between devices in a communication network.

[0002] The following abbreviations are used in part or in whole in this specification: abbreviation illustrate 3GPP Third Generation Partnership Project AR Augmented Reality D2D device to device DNS Domain Name Server FR1 Frequency range 1 FR2 frequency range 2 HW Hardware IUC UE Inter-coordination ID identifier NR New Radio NW Network OTT over-the-top RRC Radio Resource Control SL-U Sublink Unlicensed Carrier SW software TXR transceiver UE User Equipment VR Virtual Reality XR Extended Reality

[0003] Work has been done in 3GPP to specify a device-to-device communication protocol, known as secondary link communication, or sometimes referred to in 3GPP references as the PC5 interface for UEs. For an overall description, see Section 16.9 of TS 38.300.

[0004] For wireless communications such as sublink communication to be performed, a network needs available frequency resources. In many cases, such resource indications for the network are static (e.g., based on operator spectrum allocations from regional spectrum regulators). Dynamic spectrum allocation methods based on databases also exist, where wireless network nodes receive information about available spectrum from a database. Several solutions exist in the literature and practice where various external database methods are used to derive spectrum limits, i.e., which portions of spectrum a network node is allowed to allocate to one or more wireless devices for sublink transmissions. See, for example, WO2019 / 081001 A1; WO2021 / 134775 A1; and RP-221798 3GPPNR Sublink Evolution Rel 18 WID.

[0005] In some solutions, such a database interacts only with network nodes. In other solutions, such a database can also receive information directly from wireless devices that guides the selection of communication resources, such as the level of congestion or interference experienced.

[0006] After a network node has been configured with the spectrum it is permitted to use for its communication, it can allocate a portion of that spectrum to a specific device for transmission. Within the concept of secondary link communication, there are two main types of resource allocation modes for providing communication resources (time and frequency) (also referred to herein as “transmission resources”) to devices using secondary links. One of these modes (scheduled resource allocation) is the network scheduling mode, where each transmission is scheduled by the network base station. This approach is sometimes referred to as “Mode 1”. The other mode (UE-autonomous resource selection (sometimes referred to as “Mode 2” or “UE-centric”)) is the UE scheduling mode, where the network base station (e.g., a gNB in ​​NR technology) allocates one or more resource pools for secondary link communication. The UE communicating on the secondary link selects secondary link communication resources from the resource pools. Information about the resource pools can be provided to the UE in system information or along with dedicated control signaling.

[0007] When the UE is not in an RRC-connected state with the network, such as when they are out of coverage, the UE autonomous resource selection operation can be used. However, this mode can also be used when the network determines that resource scheduling is better handled without direct gNB control.

[0008] An example of reasonable UE-autonomous resource selection is that the gNB allocates resource pools on frequency bands that it rarely uses for direct communication with UEs, because the gNB may consider the benefits of detailed scheduling of resources with low utilization to be minimal. Furthermore, if a group of UEs communicates via secondary links in areas where interference to other UEs in the system can be assumed to be low, then from a network perspective, UE-autonomous resource selection may be reasonable. In the 3GPP Release 18 work item description regarding secondary link enhancements (see RP-221798 3GPP NR Secondary Link Evolution Rel 18 WID mentioned above), high-frequency usage, represented as Frequency Range 2 (FR2) operation, has been added. Additionally, work on defining secondary link operation (SL-U) on unlicensed carriers is defined within the same WID. Given that FR2 resources will not significantly interfere with other frequency resources, networks operating primarily in the low-frequency (FR1) band may find it useful to allocate FR2 resources through UE-autonomous resource selection. Furthermore, networks allocating unlicensed frequency bands (which, in any case, cannot be fully controlled by the network) may also find that UE autonomous resource selection is the most appropriate way to select communication resources for secondary link communication. Other examples of UE autonomous resource selection are also envisioned within the scope of this invention.

[0009] As mentioned above, there are multiple solutions for network-based direct resource scheduling and frequency allocation, which can be performed by network nodes in a self-contained solution, or alternatively by spectrum allocation support provided via an external database.

[0010] However, even after the network has been allocated frequency ranges for communication and a group of UEs have been instructed which portion of the allocated spectrum is permitted for secondary link communication, inter-UE coordination of communication resource utilization is still required. One example is UE-autonomous resource selection based on resource pools, as specified in 3GPP.

[0011] In other words, when multiple UEs participate in secondary link communication based on UE-autonomous resource selection (and thus share a resource pool), and data communication use cases require good secondary link performance in terms of data rate and / or latency, the UEs need to coordinate their use on the resource pool to which they are allocated.

[0012] Consider the following scenario: a group of devices forming a cluster communicates with each other via secondary links. An efficient method will be needed to define beneficial resource allocation within such a cluster and between two or more device clusters.

[0013] To address this, signaling protocols for inter-UE coordination (IUC) have been defined in 3GPP. See, for example, TS 38.300 NR and NG-RAN overall descriptions; and TS 38.331 RRC protocol specification. For instance, this protocol allows a first UE to indicate preferred or non-preferred resources to a second UE via a secondary link. Signaling can be an aperiodic explicit trigger for the transmission of inter-UE coordination messages, a periodic transmission of coordination messages, or an event-triggered event. The specifications in TS 38.300 NR and NG-RAN state that "IUC can be triggered by an explicit request from UE-B or by conditions at UE-A." However, the functionality and methods for utilizing signaling under conditions at the UE are not specified, leaving the decision to the UE implementation. It is unclear how the UE determines what constitutes preferred and non-preferred resources, and what conditions at the UE might lead to such a transmission. Furthermore, in Section 6.3.5 of the TS38.331 RRC protocol specification, the “SL-InterUE-CoordinationScheme1” field includes elements to indicate the conditions in the UE from which the IUC signaling originates, and the resource set is determined by the UE implementation.

[0014] These methods are specifically designed for scenarios where the network does not participate in the scheduling of resources for each wireless device. The network only allocates resource pools, and any coordination within the pool depends on the device implementation, meaning it is independent of network nodes and signaling within the network.

[0015] Given at least the above, a technique is needed that allows the UE to effectively determine which resources within a resource pool should be indicated in such IUC signaling in order to ensure proper use of available resources in secondary link communications. A technique is also needed that addresses the issues associated with determining resources for such secondary link communications. Summary of the Invention

[0016] It should be emphasized that, when used in this specification, the term "comprising" is considered to specify the presence of a declared feature, integer, step, or component, but the use of these terms does not exclude the presence or addition of one or more other features, integers, steps, components, or combinations thereof.

[0017] Furthermore, in some cases (e.g., in the claims and the summary of the invention), reference letters may be provided to facilitate the identification of various steps and / or units. However, the use of reference letters is not intended to imply or suggest that the steps and / or units so referenced will be performed or operated in any particular order.

[0018] According to one aspect of the invention, techniques (e.g., methods, apparatus, non-transitory computer-readable storage media, program apparatus) for performing multi-device radar sensing are employed to achieve the above and other objectives.

[0019] Some aspects of this invention relate to actions performed by a first device in connection with secondary link communication between the first device and a second device, both operating in a communication network, wherein at least one set of resources to be used for the secondary link communication is allocated by the communication network and transmitted to at least one of the first device and the second device. Actions performed by the first device include: transmitting secondary link context information to an application server, wherein the secondary link context information is related to the secondary link communication. The first device receives communication from the application server, the communication including information identifying one or more communication resources within the at least one set of communication resources allocated by the network to be used during the secondary link communication with the second device. The first device performs one or both of a first action and a second action, wherein the first action includes: configuring the first device's transceiver to use the communication resources identified by the communication received from the application server; and using the configured transceiver when communicating with the second device via the secondary link. The second action includes: transmitting information about the identified communication resources to the second device for use when performing the secondary link communication between the first device and the second device.

[0020] In another aspect consistent with some, but not necessarily all, embodiments of the present invention, the context information includes one or more of the following:

[0021] The latency requirements for the secondary link communication;

[0022] The bandwidth requirements for the secondary link communication;

[0023] Quality of Service (QoS) requirements for applications using the secondary link for communication;

[0024] Device identifier used for communication via the secondary link;

[0025] The service type of the application using the secondary link communication; and

[0026] Application identifier used for communication via the secondary link.

[0027] In yet another aspect consistent with some, but not necessarily all, embodiments of the invention, the second action is performed.

[0028] In another aspect consistent with some, but not necessarily all, embodiments of the invention, the information regarding the identified communication resources is transmitted to the second device using a first beamforming signal.

[0029] In another aspect consistent with some, but not necessarily all, embodiments of the invention, the first device initiates a secondary link communication session with the second device before transmitting the secondary link context information to the application server.

[0030] In another aspect consistent with some, but not necessarily all, embodiments of the invention, the first device transmits information to the application server regarding the at least one set of communication resources to be used for the secondary link communication.

[0031] In another aspect of some, but not necessarily all, embodiments consistent with the present invention, the first device receives from a node in the communication network information regarding the at least one set of communication resources to be used for the secondary link communication. In some, but not necessarily all, embodiments, the first device sends a request for secondary link communication resources to the node in the communication network, wherein the information regarding the communication resource pool is received from the node in response to the sent request for secondary link communication resources.

[0032] In another aspect consistent with some, but not necessarily all, embodiments of the invention, the first device sends information identifying spatial characteristics of the secondary link communication to the application server.

[0033] In another aspect consistent with some, but not necessarily all, embodiments of the invention, communication between the first device and the application server is conducted via the communication network.

[0034] In another aspect consistent with some, but not necessarily all, embodiments of the invention, communication between the first device and the application is conducted via a local area network.

[0035] In another aspect consistent with some, but not necessarily all, embodiments of the invention, the first device transmits spatial domain information to the second device for use by the second device when communicating with the first device via a secondary link.

[0036] In another aspect of some, but not necessarily all, embodiments consistent with the present invention, the first device sends information to devices other than the second device regarding communication resources to be avoided when the first device communicates with the second device via a secondary link. In some, but not necessarily all, embodiments, the information regarding communication resources to be avoided when the first device communicates with the second device via a secondary link is transmitted to the devices other than the second device via a second beamforming signal.

[0037] In another aspect of some, but not necessarily all, embodiments consistent with the present invention, the first device responds to a triggering event by reporting changes affecting ongoing secondary link communication to the application server; and in response to the report, receives updated resource allocations from the application server. In yet another aspect of some, but not necessarily all, such embodiments, the triggering event is a change to the cluster of devices involved in the secondary link communication with the first device.

[0038] In another aspect consistent with some, but not necessarily all, embodiments of the invention, the first device identifies the application server by using an Internet Protocol-based domain name server lookup function.

[0039] Some aspects of this invention relate to actions performed by an application server for coordinating secondary link communication resources used by multiple communication devices, including a first device and a second device both operating in a communication network. In one aspect consistent with some, but not necessarily all, embodiments of this invention, the application server establishes a connection with the first device and receives information from the first device regarding a pool of communication resources available when performing secondary link communication with the second device. The application server also receives secondary link context information from the first device, wherein the secondary link context information relates to secondary link communication between the first device and the second device. The application server selects one or more communication resources from the communication resource pool received from the first device to be used by the first device and the second device during the secondary link communication between the first device and the second device, wherein the selection is based at least in part on the received secondary link context information. The application server notifies the first device of the selected one or more communication resources.

[0040] In another aspect consistent with some, but not necessarily all, embodiments of the invention, the selection of the one or more communication resources is further based at least in part on avoiding the selection of one or more communication resources that the application server has allocated for use by the third device and the fourth device during secondary link communication between the third device and the fourth device, wherein the plurality of communication devices includes the third device and the fourth device.

[0041] In another aspect of some, but not necessarily all, embodiments consistent with the present invention, the secondary link communication between the first device and the second device is a first secondary link communication activity, and the secondary link communication between the third device and the fourth device is a second secondary link activity. Furthermore, avoiding the selection of one or more communication resources allocated by the application server for use by the third device and the fourth device during the secondary link communication between the third device and the fourth device is performed based on an assessment of potential interference between the first secondary link activity and the second secondary link activity. In another aspect of some, but not necessarily all, such embodiments, the application server receives: a first location of the first device; a second location of the second device; a third location of the third device; and a fourth location of the fourth device. The application server generates the assessment of potential interference between the first secondary link activity and the second secondary link activity based at least in part on the first location, the second location, the third location, and the fourth location.

[0042] In another aspect of some, but not necessarily all, embodiments consistent with the present invention, the application server receives from the first device a report regarding changes affecting ongoing secondary link communication involving the first device; in response to the report, determines an updated resource allocation; and transmits the updated resource allocation to the first device. In another aspect of some, but not necessarily all, such embodiments, the changes affecting the ongoing secondary link communication involving the first device are changes to the cluster of devices involved in the secondary link communication with the first device.

[0043] In another aspect consistent with some, but not necessarily all, embodiments of the invention, the application server sends information to devices other than the first and second devices regarding communication resources to be avoided when the first device communicates with the second device via a secondary link.

[0044] In another aspect consistent with some, but not necessarily all, embodiments of the invention, the first device and the second device are two of at least two devices operating in the communication network; and the application server is one of the at least two devices operating in the communication network. Attached Figure Description

[0045] The objectives and advantages of the present invention will be understood by reading the following detailed description in conjunction with the accompanying drawings, wherein:

[0046] Figure 1 A wireless communication system with a wireless network supporting telecommunications services for the device is shown;

[0047] Figure 2One aspect is a flowchart of the actions performed by a system for coordinating secondary link communication resources between communication devices configured to operate in a wireless communication system and also communicate directly with themselves via secondary links.

[0048] Figure 3 This is a signaling diagram of an exemplary arrangement in which the first device and the second device perform D2D communication;

[0049] Figure 4 This is a block diagram of an exemplary wireless device configured to operate according to at least some aspects of the present invention;

[0050] Figure 5 One aspect is a flowchart of actions performed by the first device according to some, but not necessarily all, embodiments of the present invention;

[0051] Figure 6 One aspect is a flowchart of actions performed by an application server according to some, but not necessarily all, embodiments of the present invention;

[0052] Figure 7 An exemplary controller is shown that can be included in a wireless device or application server to cause any and / or all actions described and illustrated herein associated with that device to be performed. Detailed Implementation

[0053] Various features of the invention will now be described with reference to the accompanying drawings, wherein the same reference numerals are used to identify the same parts.

[0054] Various aspects of the invention will now be described in more detail with reference to several exemplary embodiments. To facilitate understanding of the invention, many aspects are described according to a sequence of actions to be performed by elements of a computer system or other hardware capable of executing programmed instructions. It will be appreciated that in each of these embodiments, various actions can be performed by dedicated circuitry (e.g., analog and / or discrete logic gates interconnected to perform dedicated functions), by using one or more processors programmed with a suitable instruction set, or by a combination of both. The term “circuit configured to perform one or more of the said actions” is used herein to refer to any such embodiment (i.e., one or more dedicated circuits alone, one or more programmed processors, or any combination thereof). Furthermore, the invention can also be considered to be entirely embodied in any form of non-transitory computer-readable carrier, such as a solid-state memory, disk, or optical disk containing a suitable computer instruction set that would cause a processor to perform the techniques described herein. Therefore, various aspects of the invention can be embodied in many different forms, and all such forms are contemplated to be within the scope of the invention. For each aspect of the invention, any embodiment of any such form as described above may be referred to herein as “logic configured to perform the said actions”, or alternatively as “logic performing the said actions.”

[0055] Embodiments consistent with the present invention address the problem of effectively determining, by one or more UEs, which resources within a resource pool should be used for secondary link communication and / or indicated in IUC signaling to UEs participating in secondary link communication, so as to achieve good use of available resources in secondary link communication.

[0056] In one aspect of some embodiments of the invention, the first device performs secondary link communication with the second device, both devices being configured to operate within a communication network. At least one set of resources to be used for the secondary link communication is allocated by the communication network and transmitted to at least one of the first and second devices.

[0057] One aspect of an embodiment consistent with the present invention relates to inter-device resource coordination signaling in a secondary link protocol.

[0058] Another aspect of some embodiments consistent with this invention relates to a device that, when activated for secondary link communication, is granted one or more pools of communication resources by a network for use in secondary link communication. The device sends information to an application server instructing the device to utilize context (e.g., application identifier, secondary link quality of service (QoS), device type / capabilities, mobility, and location).

[0059] In another aspect of some embodiments consistent with the present invention, the application server also receives information about the communication resource pool from the device or from another source (e.g., another device participating in secondary link communication).

[0060] In another aspect of some embodiments consistent with the present invention, the application server may also receive additional information about resources licensed by the network. In one or more examples, such information may be sent as a metric indicating the total amount of available resources.

[0061] In another aspect of some embodiments consistent with the present invention, the application server can process information received from multiple wireless devices participating in a secondary link and send resource coordination information to one or more of these wireless devices.

[0062] In another aspect of some embodiments consistent with the present invention, the wireless device subsequently uses resource coordination information as a trigger to send inter-UE coordination signaling to at least one of a plurality of devices via secondary link communication based on the coordination information received from the application server.

[0063] It can be noted that the device is capable of communicating with the application server with or without explicit network resources available to it. In some examples, the device can participate in secondary link communication even without explicit network resources available, and can benefit from interacting with the application server by providing information to the application server and possibly also receiving information about resource coordination with nearby devices. In other words, such a device can also be triggered to send IUC signaling for coordination between secondary link UEs.

[0064] As an exemplary overview of the system, Figure 1 A wireless communication system with a wireless network 101 supporting telecommunications services for devices (e.g., UE 103) is illustrated. In this example, multiple devices communicate with each other on a secondary link (e.g., secondary link 105). In this example, it is assumed that network 101 uses a UE-autonomous scheduling method for secondary link communication, which means that communication will be scheduled by the device 103 itself communicating on the secondary link.

[0065] Wireless network 101 has its own communication resources (including frequency resources and time resources) available for its use, and wireless network 101 selects a pool of secondary link communication resources from these resources that can be used to support secondary link communication between multiple devices. Wireless network 101 notifies one or more of these devices of the communication resource pool 111.

[0066] The secondary link communication protocol allows for standardized signaling for coordination between devices using allocated communication resource pools. The benefit of this standardized control signaling is that all compatible devices can decode such signals. In one aspect of the invention, the technology provides a method for obtaining relevant information to be sent over the coordination control signaling and for enabling multiple devices to coordinate with each other. Any number of devices can be included in the coordination. Examples of practical scenarios include coordination between devices running the same operating system, devices running applications from the same application provider, devices from the same device manufacturer, etc.

[0067] Now refer to Figure 2 Describing at least some other aspects of embodiments of the present invention, Figure 2 One aspect is a flowchart of the actions performed by a system for coordinating secondary link communication resources between communication devices configured to operate in a wireless communication system and also communicate directly with themselves via secondary links. In other aspects, Figure 2 The boxes shown can also be considered as representing devices 200 (e.g., hardwired or programmable circuits or other processing devices) for performing the described actions.

[0068] At a higher level, aspects of secondary link communication resource coordination include:

[0069] - A set of initialization steps, including initializing secondary link connections using device-autonomous resource allocation. Furthermore, the application server is determined to be advantageously executed within the initialization steps.

[0070] - Server communication includes information provision steps and configuration reception steps. Here, resource coordination information related to secondary link communication resources is provided to at least one of these devices.

[0071] - Inter-device coordination steps, wherein a device transmits resource coordination information with one or more other devices via a secondary link protocol.

[0072] These actions will now be described in more detail below:

[0073] Initialization steps

[0074] The initialization steps include establishing secondary link communication between a group of devices in a wireless network (step 201). To illustrate this, referring to a 3GPP-compliant system, this may include a 3GPP network and UEs communicating via a Uu interface, with the secondary link connection activated where the network signals to the UEs the use of autonomous resource allocation. In an alternative exemplary embodiment, a group of UEs initiates the secondary link connection when in idle mode or out-of-coverage mode (from a 3GPP perspective). In the latter case, UE autonomous resource allocation is used by default for the secondary link. It can be noted that the wireless devices may be out of coverage or in idle mode relative to the 3GPP network and still be connected to the Internet via a non-3GPP connection.

[0075] In addition to the secondary link initiation, a connection to the application server for potential future resource coordination support is initiated (step 203). Several alternative methods are possible for identifying the appropriate application server. In one example, an IP-based DNS lookup function can be used, where the device requesting resource coordination uses a known domain name for secondary link coordination. To illustrate this, a domain name in the form of "www.[domain name for secondary link coordination].com" can be used. Of course, any other domain known to the device application can be used. In one such embodiment, the wireless communication network directs requests for such domains to an internal function and thereby hosts an addressable server. In an alternative embodiment, an external server outside the wireless communication network can be utilized. Figure 1 The diagram illustrates this second alternative, showing a cloud-based application server 113 independent of wireless network 101. In this way, any coordination provider can host the coordination function, and any device can access it.

[0076] In another alternative, a more application-specific server is provided, where IP addresses or similar connection information are provided to the wireless device via over-the-top application communication. In such an embodiment, the wireless device can receive the appropriate IP address for secondary link resource coordination via information provided by an application or operating system running on the device, wherein the application / operating system entity is connected to one or more control servers on the Internet. This arrangement allows the relevant coordination server addresses for their respective services to be provided to all devices running the same application or the same operating system.

[0077] Server communication

[0078] Following the initialization step, the device communicates with the application server. Server communication may include one or more authentication and authorization steps, whereby the wireless device may provide information such as a UE identifier and / or application identifier to be authorized for secondary link coordination. Furthermore, server communication includes providing the application server with context information related to the secondary link communication (step 205). The application server processes the indicated context information and uses it as a basis for determining an appropriate resource allocation strategy. In a non-limiting example, the secondary link usage context includes one or more of the following: application identifier and device identifier, device type, mobility and / or location information. Providing secondary link information (e.g., available resources for the secondary link) is advantageous. Additionally, in some embodiments, secondary link information such as secondary link clustering information may be provided, meaning the device is connected to one or more nearby devices. For illustration and reference... Figure 1 Device 103 may have multiple other devices in its vicinity, enabling these devices to form a first cluster 107. Similarly, as shown in the figure, other devices (such as devices near the second device 115) may form a second cluster 109.

[0079] In some other non-limiting embodiments, the secondary link information may also include secondary link radio quality information.

[0080] One principle involved in the illustrated example is that, as described above, application server 113 receives information from multiple devices 103, 115, and therefore can more efficiently coordinate resources between devices compared to in-device evaluation that would otherwise be required without server functionality. Thus, in the illustrated embodiment, application server 113 processes information received from multiple connected devices 103, 115 and responds to one or more connected devices 103, 115 to provide recommendations regarding secondary link communication resource coordination. The secondary link communication resource coordination information sent from application server 113 to wireless devices 103, 115 may include time and frequency information to be used by devices 103, 115, or may include communication resources (e.g., time and / or frequency) not used by devices 103, 115 (i.e., such that the device will not cause disruptive interference to secondary link communication between other nearby devices).

[0081] Communication to and from the application server 117, 119 (by...) Figure 1(As shown by the dashed line in the diagram) This can be done at the IP level (e.g., HTTP protocol data communication based on the IP address given in the initialization step). Signaling to devices 103 and 115 can be provided repeatedly, meaning that, as a non-limiting example, updated resource coordination information can be repeatedly provided to the devices until the device indicates the end of the secondary link communication. Such information can be used in the wireless device to perform periodic inter-device coordination signaling, and the period of IUC signaling on the secondary link can be coordinated with the update frequency of device-server communication.

[0082] In some non-limiting embodiments, event-based or trigger-based reporting on the interface to server 113 is also provided. Different triggers can be defined within device-server communications 117, 119 to determine, for example, when wireless devices 103, 115 update their information to server 113, or when server 113 will provide updated resource allocation recommendations. For example, when one or more conditions of the secondary link cluster 107, 109 change (e.g., when a new device is activated and joins the secondary link cluster, or when a device connected to the secondary link is deactivated / removed from the secondary link cluster), the cluster head device (e.g., device 103 or device 115) reports the change to server 113. In response, server 113 provides updated resource allocation recommendations accordingly. Such communications can be used in wireless devices 103, 115 to perform condition-based inter-device coordination signaling, where coordination information received by devices 103, 115 from server 113 is a condition triggering IUC signaling.

[0083] Equipment Coordination

[0084] As one aspect, following the resource proposal from application server 113, an exemplary embodiment includes the step of providing inter-device coordination to one or more devices near wireless devices 103, 115 (e.g., devices forming a first cluster 107 with device 103; and / or devices forming a second cluster 109 with device 115). As a non-limiting example, this can be provided using UE-to-UE coordination signaling as defined in 3GPP, as described in the 3GPP specification. As previously stated, the 3GPP specification teaches that UE-to-UE coordination may include information about preferred or non-preferred resources to be used by a second UE, and one reason for such transmission may be a condition determined in the UE. According to some exemplary embodiments consistent with the present invention, one such condition in the UE is that the aforementioned server communication is being performed, and the UE thus receives information about suitable resources indicated as preferred or non-preferred by other UEs. Therefore, as Figure 2As shown, the device monitors to detect whether communication resource coordination information has been received from application server 113 (decision box 207), and if it has been received (the "yes" path in the decision box), the information indicating resource allocation is sent to one or more other devices on the secondary link via UE-to-UE coordination signaling specified by 3GPP in some non-limiting embodiments (step 209).

[0085] It can be noted that, in addition to the suggested inter-UE coordination signaling, other methods for sending information to nearby devices are also envisioned in the alternative embodiments. For example, the information could be signaled via different communication protocols and technologies (such as Bluetooth or WiFi).

[0086] Devices 103 and 115 also monitor to detect whether the secondary link session has ended (Decision Box 211). If it has not ended (No path in Decision Box 211), resource coordination steps 207 and 209 are repeated. Otherwise (Yes path in Decision Box 211), no further steps are taken.

[0087] Now refer to Figure 3 Other aspects of embodiments consistent with the present invention are described. Figure 3 This is a signaling diagram illustrating an exemplary arrangement in which the first device 301 and the second device 303 perform D2D communication. In one aspect of this embodiment, the application server 305 provides support for coordinating communication resources used for D2D communication.

[0088] In this non-limiting exemplary embodiment, D2D signaling is assumed to use the traditional 3GPP "PC5" secondary link protocol. The PC5 interface is a low-level radio access protocol control signaling.

[0089] Figure 3 The device-to-application server signaling shown is assumed to use IP-based application communication, such as the HTTP protocol using the IP address provided to the application server. In this assumed protocol, IP-based application / payload data is exchanged via a logical connection established between the device and the application server.

[0090] It should be emphasized that these assumptions (i.e., using PC5 and HTTP protocols) are for illustrative purposes only, and other protocols may be used in alternative embodiments.

[0091] Figure 3 The signaling diagram illustrates the main principles of the signaling flow. The diagram begins with the first device 301 and the second device 303 initiating secondary link communication with each other at 307.

[0092] Then, one of these devices (in this non-limiting example, first device 301) sends a connection request 309 to application server 305. In return, application server 305 sends a connection response 311 to first device 301.

[0093] Once the device-application connection is established, the first device 301 sends secondary link context information 315 to the application server 305. The application server 305 evaluates the context information 315 individually, or possibly in combination with other secondary link context information 313 that the application server 305 may have received from other devices in the same or different device clusters. In this respect, the application server has a high-level view of the secondary link communication occurring between multiple devices and is able to make recommendations and / or decisions on how best to coordinate the use of secondary link communication resources (e.g., time and frequency resources) among the various devices. Based on this evaluation, the application server 305 sends resource coordination information 317 to the first device 301. The first device 301 then shares 319 this information with the second device 303, and both devices use the coordination information to make decisions regarding the utilization of secondary link communication resources.

[0094] As mentioned above, it is shown at a high level Figure 3 The actions described herein. In practice, each such action may require the execution of multiple sub-steps, with multiple signaling messages being transmitted in different directions. Furthermore, communication with other nodes and functions is also likely to occur, such as communication between the device and the network base station for a secondary link initiation process, and communication between the device and a DNS server, which may be necessary to identify the IP address of the application server 305.

[0095] Now refer to Figure 4 Other aspects consistent with, but not necessarily all, of this invention are described. Figure 4 This is a block diagram of a wireless device 401 configured to operate according to the present invention. Exemplary embodiments are non-limiting and for illustrative purposes only, as the functionality described herein can be implemented within the device in various ways, depending largely on the device architecture implementation. Figure 4 In the example, wireless device 401 includes application entity 403 and at least one modem entity 405. Application entity 403 includes processing capabilities (e.g., hardware and / or software) for running an operating system for the application entity's software architecture, wherein one or more applications 407, 409 may be active. Applications 407, 409 may perform functions such as processing input and output from sensors and displays, or processing application data. Modem entity 405 performs communication via wireless communication protocols (e.g., Bluetooth, Wi-Fi, and 3GPP protocols).

[0096] In one exemplary embodiment, information typically available in modem entity 405 is shared with the application server. This means that information sent from a communication network node (e.g., a gNB) and received by modem entity 405 in device 401 (e.g., secondary link resource pool information) will be further forwarded to the application server. In this type of example, communication resource coordination functionality can be implemented in modem entity 405 of wireless device 401, wherein modem entity 405 may include secondary link resource coordination functionality responsible for connecting to a designated application server.

[0097] In an alternative exemplary embodiment, information typically available in both the modem entity 405 and the application entity 403 of the wireless device 401 is shared with each other. This allows the functionality described herein to be implemented in either the modem entity 405 or the application entity 403. The wireless device 401 typically includes a set of interfaces 411 for exchanging information and / or signals between the application entity 403 and the modem entity 405, wherein both payload data and control information relating to the management of interaction between the two entities are transmitted. As an example in which device coordination functionality is implemented in the application entity 403, information about the radio resources allocated for use in secondary link communication is transmitted from the modem entity 405 to the application entity 403 after secondary link activation. Thereafter, the application entity (e.g., a function within one of running applications 407, 409) can combine such information with context information available in the application entity 403 and transmit the information to the application server for secondary link resource coordination. In addition, information about the coordination information received from the application server can be sent from the application entity 403 to the modem entity 405 so that the modem 405 can send the relevant inter-device coordination on the secondary link.

[0098] In some examples, secondary link communication can be performed on frequencies where the wireless device 401 is capable of performing beamforming or other spatial domain control on the transmitted signals. As an example, this can be enabled for so-called millimeter-wave communication (e.g., in the 3GPP frequency range 2 spectrum, meaning carrier frequencies above 6 GHz). This can be used in combination with other aspects of the embodiments of the invention disclosed herein, where inter-device coordination signaling is transmitted in the spatial domain with specific characteristics. The wireless device can determine (e.g., based on the spatial characteristics of the secondary link data communication) the appropriate spatial domain for the IUC coordination signaling to be used. In one example, a first inter-device coordination signal is transmitted using beamforming intended for communication with a first device, thereby informing the first device of appropriate resource usage. Furthermore, for this example, a second inter-device coordination signal is transmitted using beamforming intended for communication with devices other than the first device, thereby informing them of resources they should avoid using. In another exemplary embodiment, an application server can assist in determining the beamforming to be applied by the device for inter-device coordination, wherein the wireless device reports the spatial characteristics of the secondary link communication as part of a report to the application server. The application server can use this information and provide suggestions in the server response regarding spatial domain handling for device transfers coordinated between devices.

[0099] Other aspects of embodiments of the invention will now be described with reference to exemplary use cases, namely, device groups used for gaming. In particular, consider outdoor online multiplayer games involving wireless devices, where, as part of the gaming process, the wireless devices interact with the environment and require significant data transmission due to, for example, XR-based (e.g., AR-based or VR-based) user interfaces.

[0100] In a standard setup, and assuming a 3GPP-compliant communication system, each player's device will be connected to the mobile network via the Uu air interface, meaning from each UE to the network base station (gNB). Local data reflecting the environment from the first player's camera and sensors will be uploaded to the game server via OTT data transmission. The processed data (taking into account game actions and other modifications by the game server) will then be downloaded to the second player's device again via Uu.

[0101] By applying aspects of the invention described herein, the arrangement just described can be significantly improved. For example, the amount of data transmitted via the Uu interface can be significantly reduced, and data transmission from the first player to the second player can be performed locally via a secondary link connection (as described below), which enables a high-performance game mode.

[0102] In one embodiment, the first player's mobile device (which can act as a cluster head) is connected to the cellular network via an FR1 connection. It requests and is thus granted secondary link resources from the cellular network, such as FR2 resources with a minimum bandwidth of 100 MHz. The decision to participate in the game and the availability of secondary link resources can be considered triggering conditions for cooperative management of secondary links via the application server. Therefore, the first player registers with the application server (which may be associated with or implemented within the game server), including game parameters and its approximate location (e.g., physical location or cell ID fingerprint). The first player's device also provides the application server with information about its granted secondary link resources (i.e., those granted by the network). This can be done via FR1 in an OTT manner.

[0103] A second player's device participating in the same game also registers with the application server, similarly providing its game context and location. Based on the received information, the application server can identify that devices may be within the secondary link range, and that at least one of these devices has already acquired secondary link resources. The application server can also verify whether the resources (low latency, high bandwidth, if within FR2) are sufficient for the required data transmission based on specific (e.g., high-performance) operating modes, and it can determine whether there are more devices nearby (e.g., other game clusters) also using overlapping resource allocations from the network. Based on this, the application server can identify which of the available secondary link communication resources should be used by the first and second devices, in order to coordinate resource usage not only between these two devices but also potentially considering the needs of other devices.

[0104] The application server then signals one or more of the first and second player devices which available secondary link communication resources are recommended for use by both devices. In this way, the use of secondary link resources provided by the network can be shared among multiple devices. This signaling includes information that ensures both players use sufficient allocated resources for their communication needs and also ensures they avoid interfering with other nearby devices. In other words, the application server's coordination helps ensure the use of secondary link resources within the cluster and among two or more device clusters (e.g., Figure 1 The appropriate resource allocation between the first and second clusters (107, 109) shown in the diagram. Once the secondary link connection is coordinated using inter-device coordination signaling, data that does not need to be processed in the game server (e.g., VR / AR / XR scene data) can be directly transmitted between the first and second player devices using the regular secondary link protocol. The two players can play the game at a high-quality level supported by the FR2 secondary link resources.

[0105] Now refer to Figure 5Other aspects of some, but not all, of the embodiments of the present invention are described. Figure 5 In one aspect, there is a flowchart of actions performed by the first device according to some, but not necessarily all, embodiments of the invention. In other aspects, Figure 5 The boxes shown can also be considered as representing devices 500 (e.g., hardwired or programmable circuits or other processing devices) for performing the described actions.

[0106] The first device is located in an arrangement including the first device and the second device, both of which operate in a communication network, wherein at least one set of resources to be used for secondary link communication between the first device and the second device is allocated by the communication network and transmitted to at least one of the first device and the second device.

[0107] like Figure 5 As shown, the process includes: a first device transmitting (step 501) secondary link context information to an application server, wherein the secondary link context information relates to secondary link communication. The first device receives (step 503) communication from the application server, the communication including information identifying one or more communication resources within at least one set of communication resources allocated by the network to be used during secondary link communication with the second device. The first device then performs one or both of a first action (step 505) and a second action (step 507), wherein the first action (step 505) includes: configuring (step 509) the first device's transceiver to use the communication resources identified by the communication received from the application server; and using (step 511) the configured transceiver when communicating with the second device via the secondary link.

[0108] The second action (step 507) includes transmitting (step 513) information about the identified communication resource to the second device for use in performing secondary link communication between the first device and the second device.

[0109] Now refer to Figure 6 Other aspects of some, but not all, of the embodiments of the present invention are described. Figure 6 One aspect is a flowchart of actions performed by an application server according to some, but not necessarily all, embodiments of the invention. In other aspects, Figure 6 The boxes shown can also be considered as representing a device 600 (e.g., a hardwired or programmable circuit or other processing device) for performing the described action.

[0110] An application server is used to coordinate secondary link communication resources used by multiple communication devices, including a first device and a second device, both operating within the communication network. For example... Figure 6As shown, the process includes: establishing a connection with the first device (step 601); receiving (step 603) information from the first device about the pool of communication resources available when performing secondary link communication with the second device; and receiving (step 605) secondary link context information from the first device, wherein the secondary link context information relates to secondary link communication between the first device and the second device.

[0111] The application server selects (step 607) one or more communication resources from the communication resource pool received from the first device to be used by the first device and the second device during secondary link communication between the first device and the second device, wherein the selection is based at least in part on the received secondary link context information. The application server then notifies the first device of the selected one or more communication resources.

[0112] Now refer to Figure 7 Other aspects of embodiments consistent with the present invention are described. Figure 7 An exemplary controller 701 is illustrated. Controller 701 can be included in a sensing device or lighting device to cause any and / or all actions described and illustrated herein associated with that device to be performed. In particular, controller 701 includes circuitry configured to perform any one or any combination of the various functions described herein. For example, such circuitry can be fully hardwired circuitry (e.g., one or more application-specific integrated circuits, "ASICs"). However, in Figure 7 The exemplary embodiment shown is a programmable circuit that includes a processor 703 coupled to one or more storage devices 705 (e.g., random access memory, disk drive, optical disk drive, read-only memory, etc.) and an interface 707 that enables bidirectional communication with other units of the device as described above. A complete list of possible other units is beyond the scope of this specification.

[0113] Storage device 705 stores program means 709 (e.g., processor instruction set), which is configured to cause processor 703 to control other device units to perform any aspects described herein. Storage device 705 may also store data (not shown) representing various constant and variable parameters that processor 703 may need and / or may generate when performing its functions (e.g., functions specified by program means 709).

[0114] Embodiments consistent with aspects of the present invention offer several advantages over conventional techniques. One of these advantages is that even if the network has decided that secondary link resource allocation is based on a resource pool (whose usage is determined by the device (e.g., UE, (mode 2 operation))) without network-specific scheduling, multiple devices can still obtain external server support for coordination and thus improve their resource utilization for high-quality secondary link communication in an efficient manner.

[0115] Another advantage is that this can be achieved even if the devices belong to different sub-link communication device clusters. In other words, compared to exploitation based solely on the transmission intent known only to a single device, the triggering conditions and collected information for initiating inter-device coordination signaling can be based on additional information involving multiple devices.

[0116] Another advantage is that actions related to the technology disclosed herein can be performed without the involvement of an explicit wireless network, which means that signaling from the device described herein to the application server is performed at the application layer.

[0117] The invention has been described with reference to specific embodiments. However, it will be readily apparent to those skilled in the art that the invention may be embodied in specific forms other than those described above.

[0118] For example, the exemplary embodiments described above assume that the application server is an entity completely separate from the wireless devices (e.g., UEs) operating in the communication network. However, in some alternative embodiments, a user equipment (e.g., one of the devices participating in secondary link communication) may assume the role of an application server to perform the functions described herein.

[0119] Therefore, the described embodiments are merely illustrative and should not be construed as limiting in any way. The scope of the invention is further defined by the appended claims, and not merely by the foregoing description, and all variations and equivalents falling within the scope of the claims are intended to be included therein.

Claims

1. A method for secondary link communication (105) between a first device (103, 115, 301, 401) and a second device (303, 401), wherein both the first device (103, 115, 301, 401) and the second device (303, 401) operate in a communication network (101), wherein, At least one set of communication resources (111) to be used for the secondary link communication (105) is allocated by the communication network (101) and transmitted to at least one of the first device (103, 115, 301, 401) and the second device (303, 401), the method being performed by the first device (103, 115, 301, 401) and comprising: Transmit secondary link context information (205, 315, 501) to the application server (113, 305), wherein the secondary link context information is related to the secondary link communication (105); Receive (317, 503) communications from the application server (113, 305), the communications including information identifying one or more communication resources within the at least one set of communication resources (111) allocated by the network to be used during the secondary link communication (105) with the second device (303, 401); and Perform one or both of the first action (505) and the second action (507). The first action (505) includes: Configure (509) the transceiver of the first device (103, 115, 301, 401) to use the communication resources identified by the communication received from the application server (113, 305); and When communicating with the second device (303, 401) via the secondary link, the transceiver configured in (511) is used; and The second action (507) includes: Transmit (513) information about the identified communication resources to the second device (303, 401) for use in performing the sublink communication (105) between the first device (103, 115, 301, 401) and the second device (303, 401).

2. The method according to claim 1, wherein, The context information includes one or more of the following: The delay requirement of the secondary link communication (105); The bandwidth requirements of the secondary link communication (105); Quality of Service (QoS) requirements for applications using the secondary link communication (105); The device identifier used for the secondary link communication (105); The service type of the application using the secondary link communication (105); and The application identifier used in the sublink communication (105) 3. The method according to any one of the preceding claims, comprising the second action (507).

4. The method according to claim 3, wherein, The information regarding the identified communication resources is transmitted to the second device (303, 401) using a first beamforming signal.

5. The method according to any one of the preceding claims, comprising: Before transmitting the secondary link context information to the application server (113, 305), initiate a secondary link communication session between (203, 309) and the second device (303, 401).

6. The method according to any one of the preceding claims, comprising: Information about the at least one set of communication resources (111) to be used in the sublink communication (105) is transmitted to the application server (113, 305).

7. The method of claim 6, comprising: Receive information from a node in the communication network (101) regarding the at least one set of communication resources (111) to be used for the sublink communication (105).

8. The method of claim 7, comprising: Send a request for secondary link communication resources to the node in the communication network (101). The information regarding the at least one set of communication resources (111) is received from the node in response to a sent request for secondary link communication resources.

9. The method according to any one of the preceding claims, comprising: Send information identifying the spatial characteristics of the secondary link communication (105) to the application server (113, 305).

10. The method according to any one of the preceding claims, wherein, Communication (117, 119) between the first device (103, 115, 301, 401) and the application server (113, 305) is conducted via the communication network (101).

11. The method according to any one of claims 1 to 9, wherein, Communication (117, 119) between the first device (103, 115, 301, 401) and the application server (113, 305) is conducted via a local area network.

12. The method according to any one of the preceding claims, comprising: Spatial domain information is transmitted to the second device (303, 401) for use by the second device when communicating with the first device (103, 115, 301, 401) via a secondary link.

13. The method according to any one of the preceding claims, comprising: The first device (103, 115, 301, 401) sends information to devices other than the second device (303, 401) about communication resources to be avoided when the first device (103, 115, 301, 401) communicates with the second device (303, 401) via a secondary link.

14. The method according to claim 13, wherein, The information that the first device (103, 115, 301, 401) should avoid communication resources when communicating with the second device (303, 401) via a secondary link is transmitted to the devices other than the second device (303, 401) via a second beamforming signal.

15. The method according to any one of the preceding claims, comprising: In response to the triggering event, report the changes affecting ongoing secondary link communication (105) to the application server (113, 305); as well as In response to the report, an updated resource allocation is received from the application server (113, 305).

16. The method according to claim 15, wherein, The triggering event is a change to the device cluster (107, 109) involved in the secondary link communication (105) with the first device (103, 115, 301, 401).

17. The method according to any one of the preceding claims, comprising: The application server (113, 305) was identified by using the Internet Protocol-based domain name server lookup function.

18. The method according to any one of the preceding claims, wherein: The first device and the second device are two of at least two devices operating in the communication network; as well as The application server is one of the at least two devices operating in the communication network.

19. A computer program (709) comprising instructions which, when executed by at least one processor (703), cause the at least one processor (703) to perform the method according to any one of the preceding claims.

20. A carrier comprising the computer program (1509) according to claim 19, wherein, The carrier is one of electronic signals, optical signals, radio signals, and non-transitory computer-readable storage media (705).

21. A method executed by an application server (113, 305) for coordinating secondary link communication resources used by a plurality of communication devices, the plurality of communication devices including a first device (103, 115, 301, 401) and a second device (303, 401) both operating in a communication network (101), the method comprising: Establish a connection (311, 601) with the first device (103, 115, 301, 401). Receive (603) information from the first device (103, 115, 301, 401) about the communication resource pool (111) available when performing secondary link communication with the second device (303, 401); Receive secondary link context information (315, 605) from the first device (103, 115, 301, 401), wherein the secondary link context information is related to the secondary link communication (105) between the first device (103, 115, 301, 401) and the second device (303, 401); Select (607) one or more communication resources from the communication resource pool received from the first device (103, 115, 301, 401) to be used by the first device (103, 115, 301, 401) and the second device (303, 401) during the sublink communication (105) between the first device (103, 115, 301, 401) and the second device (303, 401), wherein the selection (607) is based at least in part on the received sublink context information; Notify the first device (103, 115, 301, 401) of the selected one or more communication resources (609).

22. The method according to claim 21, wherein, The selection (607) of the one or more communication resources is further based at least in part on avoiding the selection of one or more communication resources that the application server (113, 305) has allocated for use by the third device and the fourth device during the sublink communication (105) between the third device and the fourth device, wherein the plurality of communication devices includes the third device and the fourth device.

23. The method according to claim 22, wherein: The secondary link communication (105) between the first device (103, 115, 301, 401) and the second device (303, 401) is a first secondary link communication activity, and the secondary link communication (105) between the third device and the fourth device is a second secondary link activity; as well as The avoidance of selecting one or more communication resources that the application server (113, 305) has allocated for use by the third device and the fourth device during the secondary link communication (105) between the third device and the fourth device is performed based on an assessment of potential interference between the first secondary link activity and the second secondary link activity.

24. The method of claim 23, comprising: Receive the first position of the first device (103, 115, 301, 401); Receive the second position of the second device (303, 401); Receive the third position of the third device; Receive the fourth position of the fourth device; as well as The assessment of potential interference between the first sublink activity and the second sublink activity is generated based at least in part on the first position, the second position, the third position, and the fourth position.

25. The method according to any one of claims 21 to 24, comprising: Receive reports from the first device (103, 115, 301, 401) regarding changes affecting ongoing secondary link communication (105) involving the first device (103, 115, 301, 401); In response to the report, determine the updated resource allocation; as well as The updated resource allocation is transmitted to the first device (103, 115, 301, 401).

26. The method of claim 25, wherein, The change affecting the ongoing secondary link communication (105) involving the first device (103, 115, 301, 401) is a change to the device cluster (107, 109) involved in the secondary link communication (105) with the first device (103, 115, 301, 401).

27. The method according to any one of claims 21 to 26, comprising: Send information to devices other than the first device (103, 115, 301, 401) and the second device (303, 401) about communication resources to be avoided when the first device (103, 115, 301, 401) communicates with the second device via a secondary link.

28. The method according to any one of claims 21 to 27, wherein: The first device and the second device are two of at least two devices operating in the communication network; as well as The application server is one of the at least two devices operating in the communication network.

29. A computer program (709) comprising instructions that, when executed by at least one processor (703), cause the at least one processor (703) to perform the method according to any one of claims 21 to 28.

30. A carrier comprising the computer program (1509) according to claim 28, wherein, The carrier is one of electronic signals, optical signals, radio signals, and non-transitory computer-readable storage media (705).

31. An apparatus for secondary link communication (105) between a first device (103, 115, 301, 401) and a second device (303, 401), wherein the first device (103, 115, 301, 401) and the second device (303, 401) both operate in a communication network (101), wherein, At least one set of communication resources (111) to be used for the secondary link communication (105) is allocated by the communication network (101) and transmitted to at least one of the first device (103, 115, 301, 401) and the second device (303, 401), wherein the means is configured to cause the first device (103, 115, 301, 401) to perform: Transmit secondary link context information (205, 315, 501) to the application server (113, 305), wherein the secondary link context information is related to the secondary link communication (105); Receive (317, 503) communications from the application server (113, 305), the communications including information identifying one or more communication resources within the at least one set of communication resources (111) allocated by the network to be used during the secondary link communication (105) with the second device (303, 401); and Perform one or both of the first action (505) and the second action (507). The first action (505) includes: Configure (509) the transceiver of the first device (103, 115, 301, 401) to use the communication resources identified by the communication received from the application server (113, 305); and When communicating with the second device (303, 401) via the secondary link, the transceiver configured in (511) is used; and The second action (507) includes: Transmit (513) information about the identified communication resources to the second device (303, 401) for use in performing the sublink communication (105) between the first device (103, 115, 301, 401) and the second device (303, 401).

32. The apparatus according to claim 31, wherein, The context information includes one or more of the following: The delay requirement of the secondary link communication (105); The bandwidth requirements of the secondary link communication (105); Quality of Service (QoS) requirements for applications using the secondary link communication (105); The device identifier used for the secondary link communication (105); The service type of the application using the secondary link communication (105); and The application identifier used in the sublink communication (105) 33. The apparatus according to any one of claims 31 to 32, wherein, The device is configured to cause the first device (103, 115, 301, 401) to perform the second action (507).

34. The apparatus according to claim 33, wherein, The apparatus is configured such that the first device (103, 115, 301, 401) uses a first beamforming signal to transmit the information about the identified communication resource to the second device (303, 401).

35. The apparatus according to any one of claims 31 to 34, wherein, The apparatus is configured to cause the first device (103, 115, 301, 401) to perform: Before transmitting the secondary link context information to the application server (113, 305), initiate a secondary link communication session between (203, 309) and the second device (303, 401).

36. The apparatus according to any one of claims 31 to 35, wherein, The apparatus is configured to cause the first device (103, 115, 301, 401) to perform: Information about the at least one set of communication resources (111) to be used in the sublink communication (105) is transmitted to the application server (113, 305).

37. The apparatus according to claim 36, wherein, The apparatus is configured to cause the first device (103, 115, 301, 401) to perform: Receive information from a node in the communication network (101) regarding the at least one set of communication resources (111) to be used for the sublink communication (105).

38. The apparatus according to claim 37, wherein, The apparatus is configured to cause the first device (103, 115, 301, 401) to perform: Send a request for secondary link communication resources to the node in the communication network (101). The information regarding the at least one set of communication resources (111) is received from the node in response to a sent request for secondary link communication resources.

39. The apparatus according to any one of claims 31 to 38, wherein, The apparatus is configured to cause the first device (103, 115, 301, 401) to perform: Send information identifying the spatial characteristics of the secondary link communication (105) to the application server (113, 305).

40. The apparatus according to any one of claims 31 to 39, wherein, Communication (117, 119) between the first device (103, 115, 301, 401) and the application server (113, 305) is conducted via the communication network (101).

41. The apparatus according to any one of claims 31 to 39, wherein, The apparatus is configured such that the first device (103, 115, 301, 401) communicates with the application server (113, 305) via a local area network.

42. The apparatus according to any one of claims 31 to 41, wherein, The apparatus is configured to cause the first device (103, 115, 301, 401) to perform: Spatial domain information is transmitted to the second device (303, 401) for use by the second device when communicating with the first device (103, 115, 301, 401) via a secondary link.

43. The apparatus according to any one of claims 31 to 42, wherein, The apparatus is configured to cause the first device (103, 115, 301, 401) to perform: The first device (103, 115, 301, 401) sends information to devices other than the second device (303, 401) about communication resources to be avoided when the first device (103, 115, 301, 401) communicates with the second device (303, 401) via a secondary link.

44. The apparatus according to claim 43, wherein, The device is configured such that the first device (103, 115, 301, 401) transmits information via a second beamforming signal to devices other than the second device (303, 401) about communication resources to be avoided when the first device (103, 115, 301, 401) communicates with the second device (303, 401) via a secondary link.

45. The apparatus according to any one of claims 31 to 44, wherein, The apparatus is configured to cause the first device (103, 115, 301, 401) to perform: In response to the triggering event, report the changes affecting ongoing secondary link communication (105) to the application server (113, 305); and In response to the report, an updated resource allocation is received from the application server (113, 305).

46. ​​The apparatus according to claim 45, wherein, The triggering event is a change to the device cluster (107, 109) involved in the secondary link communication (105) with the first device (103, 115, 301, 401).

47. The apparatus according to any one of claims 31 to 46, wherein, The apparatus is configured to cause the first device (103, 115, 301, 401) to perform: The application server (113, 305) was identified by using the Internet Protocol-based domain name server lookup function.

48. The apparatus according to any one of claims 31 to 47, wherein: The first device and the second device are two of at least two devices operating in the communication network; as well as The application server is one of the at least two devices operating in the communication network.

49. An apparatus for enabling an application server (113, 305) to coordinate secondary link communication resources used by a plurality of communication devices, said plurality of communication devices including a first device (103, 115, 301, 401) and a second device (303, 401) both operating in a communication network (101), wherein, The device is configured to cause the application server (113, 305) to perform: Establish a connection (311, 601) with the first device (103, 115, 301, 401). Receive (603) information from the first device (103, 115, 301, 401) about the communication resource pool (111) available when performing secondary link communication with the second device (303, 401); Receive secondary link context information (315, 605) from the first device (103, 115, 301, 401), wherein the secondary link context information is related to the secondary link communication (105) between the first device (103, 115, 301, 401) and the second device (303, 401); Select (607) one or more communication resources from the communication resource pool received from the first device (103, 115, 301, 401) to be used by the first device (103, 115, 301, 401) and the second device (303, 401) during the sublink communication (105) between the first device (103, 115, 301, 401) and the second device (303, 401), wherein the selection (607) is based at least in part on the received sublink context information; Notify the first device (103, 115, 301, 401) of the selected one or more communication resources (609).

50. The apparatus according to claim 49, wherein, The selection (607) of the one or more communication resources is further based at least in part on avoiding the selection of one or more communication resources that the application server (113, 305) has allocated for use by the third device and the fourth device during the sublink communication (105) between the third device and the fourth device, wherein the plurality of communication devices includes the third device and the fourth device.

51. The apparatus according to claim 50, wherein: The secondary link communication (105) between the first device (103, 115, 301, 401) and the second device (303, 401) is a first secondary link communication activity, and the secondary link communication (105) between the third device and the fourth device is a second secondary link activity; as well as The avoidance of selecting one or more communication resources that the application server (113, 305) has allocated for use by the third device and the fourth device during the secondary link communication (105) between the third device and the fourth device is performed based on an assessment of potential interference between the first secondary link activity and the second secondary link activity.

52. The apparatus according to claim 51, wherein, The device is configured to cause the application server (113, 305) to perform: Receive the first position of the first device (103, 115, 301, 401); Receive the second position of the second device (303, 401); Receive the third position of the third device; Receive the fourth position of the fourth device; as well as The assessment of potential interference between the first sublink activity and the second sublink activity is generated based at least in part on the first position, the second position, the third position, and the fourth position.

53. The apparatus according to any one of claims 49 to 52, wherein, The device is configured to cause the application server (113, 305) to perform: Receive reports from the first device (103, 115, 301, 401) regarding changes affecting ongoing secondary link communication (105) involving the first device (103, 115, 301, 401); In response to the report, determine the updated resource allocation; as well as The updated resource allocation is transmitted to the first device (103, 115, 301, 401).

54. The apparatus according to claim 53, wherein, The change affecting the ongoing secondary link communication (105) involving the first device (103, 115, 301, 401) is a change to the device cluster (107, 109) involved in the secondary link communication (105) with the first device (103, 115, 301, 401).

55. The apparatus according to any one of claims 49 to 54, wherein, The device is configured to cause the application server (113, 305) to send information to devices other than the first device (103, 115, 301, 401) and the second device (303, 401) about communication resources to be avoided when the first device (103, 115, 301, 401) communicates with the second device via a secondary link.

56. The apparatus according to any one of claims 49 to 55, wherein: The first device and the second device are two of at least two devices operating in the communication network; as well as The application server is one of the at least two devices operating in the communication network.

Images