Device and method for cluster
By receiving registration information and requests from service devices, selecting specific service devices and building a group communication strategy, the problems of device selection and communication coordination in multi-device collaboration are solved, and efficient and low-cost task completion is achieved.
Patent Information
- Application Number
- PCT/CN2025/083303
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-03-25
- Filing Date
- 2025-03-19
- Publication Date
- 2025-10-02
AI Technical Summary
In fields such as the Internet of Things, Internet of Vehicles, Industrial Internet, and Extended Reality, when multiple devices collaborate to complete tasks, it is necessary to dynamically select appropriate service devices and coordinate communication behaviors to achieve flexible, robust, efficient, and low-cost collaboration, but existing technologies are difficult to effectively solve this problem.
Provided are an electronic device and method for receiving registration information and service requests of service devices, selecting a specific service device, and building or updating a group communication strategy for a specific cluster to achieve efficient collaboration between devices.
It achieves flexible, robust, efficient and low-cost collaboration between devices, improves the efficiency of task completion and communication quality, and reduces resource waste.
Smart Images

Figure CN2025083303_02102025_PF_FP_ABST
Abstract
Description
Device and method for clustering
[0001] Priority Declaration
[0002] This application claims priority to the Chinese patent application filed on March 25, 2024, with application number 202410340775.7 and invention name “Device and method for clustering”, the entire contents of which are incorporated herein by reference. Technical Field
[0003] The present disclosure relates to the field of communications, and in particular, to an apparatus and method for clustering. Background Art
[0004] Wireless communication technologies are increasingly being used in the Internet of Things (IoT), Vehicle-to-Everything (V2X), Industrial Internet, and Extended Reality (XR). In many scenarios within these areas, multiple devices must collaborate to complete one or more tasks. This requires identifying one or more devices capable of participating in a specific task. Furthermore, the communication behavior of these identified devices must be coordinated to achieve flexible, robust, efficient, and cost-effective collaboration. Summary of the Invention
[0005] The present disclosure provides an apparatus, method, computer-readable storage medium, computer program product, and device for clustering.
[0006] One aspect of the present disclosure relates to an electronic device, which includes at least one processing unit and at least one storage unit, the at least one storage unit including program instructions, wherein the at least one storage unit and the program instructions are configured to enable the electronic device to perform the following operations through the at least one processing unit: receive registration information from each service device in one or more service devices, the registration information including service capability information associated with the service that the service device can provide; receive a service request from a requesting device, the service request being associated with a specific service requested by the requesting device; select a specific service device from the one or more service devices based on a match between the service capability information and the service request; and send configuration information associated with the specific service to the specific service device.
[0007] Another aspect of the present disclosure relates to an electronic device, which includes at least one processing unit and at least one storage unit, the at least one storage unit including program instructions, wherein the at least one storage unit and the program instructions are configured to enable the electronic device to perform the following operations through the at least one processing unit: send registration information to a control device, the registration information including service capability information associated with services that the electronic device can provide; receive configuration information associated with a specific service from the control device, wherein the configuration information specifies that the electronic device forms a specific cluster with a requesting device requesting the specific service; and execute the specific service based at least on the configuration information.
[0008] Another aspect of the present disclosure relates to an electronic device, which includes at least one processing unit and at least one storage unit, the at least one storage unit including program instructions, wherein the at least one storage unit and the program instructions are configured to enable the electronic device to perform the following operations through the at least one processing unit: receive a group session request from a specific cluster including one or more devices, the group session request including at least task information, the task information being associated with one or more tasks to be performed by the one or more devices; and send a group communication policy to the specific cluster, the group communication policy being based at least in part on the task information.
[0009] Another aspect of the present disclosure relates to an electronic device, which includes at least one processing unit and at least one storage unit, the at least one storage unit including program instructions, wherein the at least one storage unit and the program instructions are configured to enable the electronic device to perform the following operations through the at least one processing unit: send a group session request to a control device, the group session request including at least task information, the task information being associated with one or more tasks to be performed by the electronic device; receive a group communication policy associated with a specific cluster from the control device, the group communication policy being based at least in part on the task information; and execute the one or more tasks based on the group communication policy.
[0010] One aspect of the present disclosure relates to a method performed by an electronic device, comprising the following operations: receiving registration information from each of one or more service devices, the registration information including service capability information associated with a service that the service device can provide; receiving a service request from a requesting device, the service request associated with a specific service requested by the requesting device; selecting a specific service device from the one or more service devices based on a match between the service capability information and the service request; and sending configuration information associated with the specific service to the specific service device.
[0011] One aspect of the present disclosure relates to a method performed by an electronic device, comprising the following operations: sending registration information to a control device, the registration information including service capability information associated with services that the electronic device can provide; receiving configuration information associated with a specific service from the control device, wherein the configuration information specifies that the electronic device forms a specific cluster with a requesting device requesting the specific service; and executing the specific service based at least on the configuration information.
[0012] One aspect of the present disclosure relates to a method performed by an electronic device, comprising the following operations: receiving a group session request from a specific cluster including one or more devices, the group session request including at least task information, the task information being associated with one or more tasks to be performed by the one or more devices; and sending a group communication policy to the specific cluster, the group communication policy being based at least in part on the task information.
[0013] One aspect of the present disclosure relates to a method performed by an electronic device, comprising the following operations: sending a group session request to a control device, the group session request including at least task information, the task information being associated with one or more tasks to be performed by the electronic device; receiving a group communication policy associated with a specific cluster from the control device, the group communication policy being based at least in part on the task information; and performing the one or more tasks based on the group communication policy.
[0014] Another aspect of the present disclosure relates to a computer-readable storage medium storing one or more instructions, which, when executed by one or more processing circuits of an electronic device, causes the electronic device to perform any method as described in the present disclosure.
[0015] Another aspect of the present disclosure relates to a computer program product, comprising a computer program, which implements any method as described in the present disclosure when executed by a processor.
[0016] Another aspect of the present disclosure relates to an apparatus comprising means for performing any of the methods described in the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The above and other objects and advantages of the present disclosure will be further described below in conjunction with specific embodiments and with reference to the accompanying drawings. In the accompanying drawings, identical or corresponding technical features or components will be represented by identical or corresponding reference numerals.
[0018] FIG1 shows an exemplary block diagram of an electronic device according to some embodiments of the present disclosure.
[0019] FIG2 shows an exemplary block diagram of an electronic device according to some embodiments of the present disclosure.
[0020] FIG3 shows a flowchart of a method according to some embodiments of the present disclosure.
[0021] FIG4 shows a flowchart of a method according to some embodiments of the present disclosure.
[0022] FIG5 shows a flowchart of a method according to some embodiments of the present disclosure.
[0023] FIG6 shows a flowchart of a method according to some embodiments of the present disclosure.
[0024] FIG7 shows a schematic diagram of a process according to some embodiments of the present disclosure.
[0025] FIG8 shows a schematic diagram of a process according to some embodiments of the present disclosure.
[0026] FIG9 shows a schematic diagram of a process according to some embodiments of the present disclosure.
[0027] FIG10 shows a schematic diagram of a process according to some embodiments of the present disclosure.
[0028] FIG11 shows a schematic diagram of a process according to some embodiments of the present disclosure.
[0029] FIG12 is a block diagram illustrating a first example of an exemplary configuration of a gNB to which the techniques of this disclosure may be applied.
[0030] FIG13 is a block diagram illustrating a second example of an exemplary configuration of a gNB to which the techniques of this disclosure may be applied.
[0031] FIG. 14 is a block diagram illustrating an example of an exemplary configuration of a communication device to which the technology of the present disclosure may be applied.
[0032] FIG. 15 is a block diagram illustrating an example of an exemplary configuration of a car navigation device to which the technology of the present disclosure can be applied.
[0033] Although the embodiments described in this disclosure may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown as examples in the drawings and described in detail in this disclosure. It should be understood that the drawings and detailed description thereof are not intended to limit the embodiments to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the claims. DETAILED DESCRIPTION
[0034] Exemplary embodiments of the present disclosure will be described below with reference to the accompanying drawings. For the sake of clarity and conciseness, not all features of the embodiments are described in the specification. However, it should be understood that many implementation-specific settings must be made in the process of implementing the embodiments in order to achieve the developer's specific goals, such as meeting those restrictions related to equipment and services, and these restrictions may vary depending on the implementation. In addition, it should be understood that although the development work may be very complex and time-consuming, it is only a routine task for those skilled in the art who benefit from the contents of this disclosure.
[0035] It should also be noted here that in order to avoid obscuring the present disclosure due to unnecessary details, only the processing steps and / or equipment structures that are closely related to at least the scheme according to the present disclosure are shown in the accompanying drawings, while other details that are not very relevant to the present disclosure are omitted.
[0036] Wireless communication technology is increasingly being applied in areas such as IoT, V2X, the Industrial Internet, and XR. In many scenarios, multiple devices must collaborate to complete one or more tasks. Each task can be initiated by a requesting device. Completion of each task may require the use of one or more specific services provided by a service device. A service device can be a device that enables one or more specific functions to provide the service corresponding to the requested task.
[0037] As an example, in an XR scenario, multiple service devices can collaborate to complete XR tasks. These service devices may include multiple display devices, audio devices, motion capture devices, and so on. For example, one or more service devices can be dynamically selected from the multiple service devices to perform corresponding services to complete the XR task. These services include, for example, media presentation and user interaction.
[0038] As another example, in a smart factory scenario, production tasks can be completed through the collaboration of multiple service devices. For example, multiple robotic arms can serve as service devices on an assembly line. These service devices can collaboratively perform corresponding services, including but not limited to assembly, welding, corrosion protection, and painting. For another example, multiple cranes and forklifts at a port can serve as service devices. These service devices can collaboratively complete corresponding services, including loading, unloading, sorting, and transferring cargo.
[0039] As another example, in transportation scenarios, tasks such as autonomous driving or assisted driving can be accomplished through the collaboration of multiple service devices. For example, one or more service devices installed on or near a car can perform services such as map updates, sensor fusion, and driving decision-making, thereby jointly achieving autonomous driving or assisted driving for the car.
[0040] Due to the diverse and ever-changing nature of tasks and service devices, it is necessary to dynamically select appropriate service devices to complete specific tasks. For example, in a V2X scenario, a vehicle UE may pass through different road sections (including bridges, tunnels, intersections, etc.) while traveling to its destination. Accordingly, the vehicle UE may initiate different services requiring wireless transmission (such as sensor fusion services related to assisted or autonomous driving, remote control services, computation offload services, and non-driving-related services such as multimedia entertainment). As both the environment and services constantly change, the service devices capable of providing services to the vehicle UE need to adapt adaptively. Advantageously, one or more service devices that are locally relevant and suitable for the current task can be selected from multiple service devices. Furthermore, the services performed by different service devices may need to coordinate with each other. Accordingly, these service devices may need to communicate with each other. Advantageously, the selected one or more service devices can be formed into a specific cluster. A group communication policy can be configured for this specific cluster. This group communication policy can configure one or more aspects of communications associated with the cluster to improve intra-cluster and / or inter-cluster communications while ensuring mission completion, including but not limited to saving communication resources, reducing communication congestion, and improving communication quality. Furthermore, there are one or more other issues that can be improved.
[0041] To this end, the present disclosure provides an apparatus, method, computer-readable storage medium, computer program product, and device for clustering.
[0042] 1. Exemplary Equipment
[0043] Figure 1 shows an exemplary block diagram of an electronic device 100 according to some embodiments of the present disclosure. In some embodiments, the electronic device 100 can be implemented on the control side or the server side. Therefore, the electronic device 100 can be referred to as a control device or a server. The electronic device 100 can be implemented as the control device or server itself, as a part of the control device or server, or as another device for manipulating a server or a control device. For example, the electronic device 100 can be implemented as a chip for manipulating a control device. In some embodiments of the present disclosure, for convenience of description, the electronic device 100 is implemented as the control device itself. In other embodiments, the electronic device 100 can alternatively be implemented as a device other than a control device.
[0044] In the example of a cellular network, the electronic device 100 can be implemented as a network-side device. The network-side device can include, for example, a base station or one or more network elements deployed in the cellular network. In some examples, the electronic device 100 can be implemented as an access and mobility management function (AMF) network element. In other types of networks, the electronic device 100 can include other types of control devices.
[0045] According to some embodiments of the present disclosure, the electronic device 100 may include a communication unit 110 , a storage unit 120 , and a processing circuit 130 .
[0046] The communication unit 110 of the electronic device 100 can be used to receive or send wired or radio transmissions. The communication unit 110 can perform functions such as up-conversion and digital-to-analog conversion on transmitted signals, and / or perform functions such as down-conversion and analog-to-digital conversion on received signals. The communication unit 110 can be implemented using various technologies. For example, the communication unit 110 can be implemented as communication interface components such as an antenna device, radio frequency circuitry, and a portion of baseband processing circuitry. The communication unit 110 is depicted with dashed lines because it can alternatively be located within the processing circuitry 130 or external to the electronic device 100.
[0047] The storage unit 120 of the electronic device 100 can store information generated by the processing circuit 130, information received from other devices via the communication unit 110 or information to be transmitted to other devices, programs, machine code, and data used for the operation of the electronic device 100, etc. The storage unit 120 can be a volatile memory and / or a non-volatile memory. For example, the storage unit 120 can include, but is not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), read-only memory (ROM), and flash memory. The storage unit 120 is drawn with a dotted line because it can alternatively be located within the processing circuit 130 or outside the electronic device 100.
[0048] The processing circuit 130 of the electronic device 100 can be configured to perform one or more operations, thereby providing various functions of the electronic device 100. The functions of the elements disclosed herein can be implemented using a circuit or processing circuit 130, which includes a general-purpose processor, a special-purpose processor, an integrated circuit, an ASIC ("application-specific integrated circuit"), a conventional circuit, and / or a combination thereof that is configured or programmed to perform the disclosed functions. Processors are considered processing circuits or circuits because they include transistors and other circuits therein. In the present disclosure, a circuit, unit, or device is hardware that performs or is programmed to perform the functions described. The hardware can be any hardware disclosed herein or otherwise known that is programmed or configured to perform the functions described. When the hardware is a processor that can be considered a type of circuit, the circuit, device, or unit is a combination of hardware and software, with the software being used to configure the hardware and / or processor. According to some embodiments, in response to the processing circuit 130 executing the computer program code contained in the storage unit 120, the electronic device 100 can be configured to perform one or more steps performed by the control device in the present disclosure.
[0049] According to some aspects of the present disclosure, the electronic device 100 may be configured to perform one or more operations for building or updating a cluster associated with a specific task. Specifically, the electronic device 100 may be configured to receive registration information from each of one or more service devices. The registration information of each service device may include service capability information associated with the services that the service device can provide. The electronic device 100 may also be configured to receive a service request from a requesting device. The service request may be associated with a specific service requested by the requesting device. The requesting device may be a device that initiates or performs a specific task, and the requested specific service may be associated with the specific task. The electronic device 100 may be further configured to select a specific service device from one or more service devices based on a match between the service capability information and the service request. The electronic device 100 may then be configured to send configuration information associated with the specific service to the specific service device.
[0050] According to some embodiments, the processing circuit 130 of the electronic device 100 may include one or more subunits for implementing the aforementioned steps. For example, the processing circuit 130 may include a matching unit, a selection unit, and a configuration unit (not shown in FIG1 ). The matching unit may be configured to obtain the received service capability information and the service request from the communication unit 110 of the electronic device 100 and perform a match between the two. The selection unit may be configured to select a specific service device based on the result of the matching unit. The configuration unit may obtain configuration information for the specific service device associated with the specific service. The obtained configuration information may be sent through the communication unit 110 of the electronic device 100.
[0051] Optionally, the electronic device 100 may also be configured to perform one or more additional steps, including but not limited to steps associated with the example methods or processes described with respect to FIG. 3 or FIG. 7 .
[0052] According to other aspects of the present disclosure, the electronic device 100 may be configured to perform one or more operations for building or updating a group communication policy associated with a specific cluster. Specifically, the electronic device 100 may be configured to receive a group session request from a specific cluster including one or more devices. The group session request may include at least task information, which may be associated with one or more tasks to be performed by the one or more devices. The electronic device 100 may be further configured to send a group communication policy to the specific cluster, where the group communication policy may be based at least in part on the task information.
[0053] According to some embodiments, the processing circuit 130 of the electronic device 100 may include one or more subunits for implementing one or more of the aforementioned steps. For example, the processing circuit 130 may include a policy unit (not shown in FIG1 ). The policy unit may be configured to obtain task information of a specific cluster from the communication unit 110. The policy unit may be further configured to obtain a group communication policy associated with the specific cluster. For example, the policy unit may interact with other network elements in the cellular network to retrieve the group communication policy, or the policy unit may generate the group communication policy locally, or both. The obtained group communication policy may be sent by the communication unit 110 of the electronic device 100.
[0054] Optionally, the electronic device 100 may also be configured to perform one or more additional steps, including but not limited to steps associated with the example methods or processes described with respect to FIG. 5 , FIG. 8 , or FIG. 9 .
[0055] It should be understood that the above-mentioned two aspects of the electronic device 100 can be implemented separately or in combination. For example, the construction and update of the cluster can be performed by a first instance of the electronic device 100, while the construction and update of the group communication policy associated with the cluster can be performed by a second instance of the electronic device 100. In some embodiments, the first instance and the second instance can be the same instance. In other embodiments, the first instance is different from the second instance.
[0056] Figure 2 shows an exemplary block diagram of an electronic device 200 according to some embodiments of the present disclosure. In some embodiments, the electronic device 200 may be implemented on the client side. Therefore, the electronic device 200 may be referred to as a user device (UE). A user may include an individual, an enterprise, or an organization. For example, service equipment deployed by an enterprise that can provide one or more services may be referred to as a user device. In another example, industrial equipment that needs to perform one or more tasks may also be referred to as a user device. The electronic device 200 may be implemented as the user device itself, as a portion of the user device, or as a controller for controlling the user device. For example, the electronic device 200 may be implemented as a chip for controlling the user device. In some examples of cellular networks, the electronic device 200 may include a user equipment (UE), which may refer to various user devices that access a cellular network to communicate. In some embodiments of the present disclosure, for ease of description, the electronic device 200 is implemented as a UE itself. In other embodiments, the electronic device 200 may alternatively be implemented as a device other than a UE. For example, in some examples, a network element of a cellular network acts as a service device to provide specific services to a UE for completing specific tasks. Accordingly, the electronic device 200 may also include a network element or base station to which the UE accesses.
[0057] According to some embodiments of the present disclosure, electronic device 200 may include a communication unit 210, a storage unit 220, and a processing circuit 230. The specific implementations of communication unit 210, storage unit 220, and processing circuit 230 may be similar to the communication unit 110, storage unit 120, and processing circuit 130 described above with respect to electronic device 100, and are not further described herein. According to some embodiments, in response to processing circuit 230 executing computer program code contained in storage unit 220, electronic device 200 may be configured to perform one or more steps performed by a user device in implementing various methods according to some embodiments of the present disclosure.
[0058] According to some aspects of the present disclosure, the electronic device 200 may be configured to perform one or more operations for building or updating a cluster associated with a specific task. Specifically, the electronic device 200 may be configured to send registration information to a control device, and the registration information may include service capability information associated with the services that the electronic device 200 can provide. The electronic device 200 may be further configured to receive configuration information associated with a specific service from the control device. The configuration information may specify that the electronic device 200 forms a specific cluster with a requesting device requesting the specific service. The electronic device 200 may then be further configured to perform the specific service based at least on the configuration information.
[0059] According to some embodiments, the processing circuit 230 of the electronic device 200 may include one or more subunits for implementing the aforementioned steps. For example, the processing circuit 230 may include a registration unit, a configuration unit, and a service unit (not shown in FIG2 ). The registration unit may be configured to send registration information via the communication unit 210 of the electronic device 200. The registration information (particularly, service capability information) may be generated by the registration unit. The configuration unit may receive the configuration information via the communication unit 210 of the electronic device 200. The configuration unit may configure the electronic device 200 based on the received configuration information. The service unit may be configured to perform a specific service based on the configuration information.
[0060] Optionally, the electronic device 200 may also be configured to perform one or more additional steps, including but not limited to steps associated with the example methods and processes described with respect to FIG. 4 or FIG. 7 .
[0061] According to other aspects of the present disclosure, the electronic device 200 may be configured to perform one or more operations for building or updating a group communication policy associated with a specific cluster. Specifically, the electronic device 200 may be configured to send a group session request to a control device, where the group session request may include at least task information. The task information may be associated with one or more tasks to be performed by the electronic device 200. The electronic device 200 may be further configured to receive a group communication policy associated with a specific cluster from the control device. The specific cluster may include multiple devices, including the electronic device 200. The group communication policy may be based at least in part on the task information. The electronic device 200 may then be further configured to perform the one or more tasks based on the group communication policy.
[0062] According to some embodiments, the processing circuit 230 of the electronic device 200 may include one or more subunits for implementing the aforementioned steps. For example, the processing circuit 230 may include a request unit, a configuration unit, and a service unit (not shown in FIG. 2 ). The request unit may be configured to send a group session request via the communication unit 210. The group session request (particularly, the task information) may be generated by the request unit. The configuration unit may receive a group communication policy via the communication unit 210 of the electronic device 200. The configuration unit may configure the electronic device 200 based on the received group communication policy. The service unit may be configured to perform one or more tasks based on the group communication policy.
[0063] Optionally, the electronic device 200 may also be configured to perform one or more additional steps, including but not limited to steps associated with the example methods and processes described with respect to FIG. 6 , FIG. 8 , or FIG. 9 .
[0064] It should be understood that the above two aspects of the electronic device 200 can be implemented separately or in combination. For example, the construction and update of the cluster can be performed by the first instance of the electronic device 200, while the construction and update of the group communication policy associated with the cluster can be performed by the second instance of the electronic device 200. The first instance and the second instance can be the same instance or different.
[0065] 2. Exemplary Methods
[0066] FIG3 shows a flow chart of a method 300 according to some embodiments of the present disclosure. According to some embodiments, the method 300 may be performed at a control device. The control device may be implemented by the aforementioned electronic device 100. Accordingly, the method 300 may be performed by the processing circuit 130 of the electronic device 100.
[0067] Method 300 may begin at step 310. In step 310, the control device may be configured to receive registration information from each of one or more service devices. The registration information may include service capability information associated with services that the service device can provide. The registration information may be used to register the service device with the control device.
[0068] According to some embodiments, the services of a service device may include services required to complete specific tasks. By way of example and not limitation, such specific tasks may include, but are not limited to, sensing tasks, industrial production tasks, device movement tasks, media presentation tasks, and the like. According to some embodiments, the service device may include, but is not limited to, sensor devices, industrial production equipment, vehicle-mounted devices, multimedia devices, aircraft devices, or access points, and the like.
[0069] According to some embodiments, the service capability information of each service device may include, but is not limited to, supported service types and supported service parameter ranges associated with the service device. For example, supported service types may describe services associated with functions that the service device can enable. Supported service parameter ranges may describe the ranges of parameters for these functions.
[0070] Preferably, the service capability information of each service device may also include a communication capacity requirement corresponding to each unit of service capability. The communication capacity requirement may indicate the communication resource requirement of the service device when providing the unit of service capability. For example, the requirement may specify the communication bandwidth, communication throughput, number of communication time slots, or other aspects required by the service device when providing the unit of service capability.
[0071] Preferably, the service capability information of each service device may also include mobility information of the service device. For a fixed service device, the mobility information may include the location or orientation of the service device. For a mobile service device, the mobility information may include the location, orientation, speed, acceleration, etc. of the service device.
[0072] The method 300 may continue to step 320. In step 320, the control device may be configured to receive a service request from a requesting device. The service request is associated with a specific service requested by the requesting device.
[0073] The requesting device may include a device that requests a specific service in order to complete a specific task. According to some embodiments, the requesting device itself may be a service device. For example, the requesting device may be one of the one or more service devices. According to other embodiments, the requesting device may be another device other than the one or more service devices.
[0074] According to some embodiments, the service request from the requesting device may include, but is not limited to, the requesting device's subscription information, service type requirements, or service parameter requirements. Preferably, the service request may also include the requesting device's mobility information. The requesting device's mobility information may include the user device's location, speed, acceleration, etc.
[0075] The method 300 may continue to step 330. In step 330, the control device may be configured to select a specific service device from the one or more service devices based on a match between the service capability information and the service request.
[0076] According to some embodiments, the control device may perform a match based on one or more criteria to determine the specific service device from multiple candidate service devices. For example, the control device may determine that the specific service device matches the subscription information of the requesting device. Additionally or alternatively, the control device may determine that the service types supported by the specific service device match the service type requirements of the requesting device. Additionally or alternatively, the control device may determine that the service parameter ranges supported by the specific service device match the service parameter requirements of the requesting device. Additionally or alternatively, the control device may determine that the spatial relationship between the specific service device and the requesting device satisfies a predetermined condition. The spatial relationship may be determined based on the mobility information of the service device and the mobility information of the requesting device.
[0077] The method 300 may continue to step 340. In step 340, the control device may be configured to send configuration information associated with the specific service to the selected specific service device. The configuration information may be determined to meet the specific service required by the requesting device.
[0078] According to some embodiments, the configuration information may wake up the specific service device. For example, each service device may remain in a low-power state after registering with the control device and be awakened upon receiving configuration information associated with a specific service. Additionally, the configuration information may specify the activated function or service of the specific service device. Other functions or services (if any) of the specific service device may remain inactive. Additionally or alternatively, the configuration information may specify the set service parameter values of the specific service device.
[0079] According to some embodiments, the configuration information may specify that a specific service device and the requesting device form a specific cluster. For example, to complete a specific task, the requesting device may request multiple services (including the aforementioned specific service). The control device may determine multiple service devices (including the aforementioned specific service device), each of which provides a corresponding service from the multiple services. In this case, the configuration information may specify that the multiple service devices form a specific cluster with the requesting device that issued the service request.
[0080] Because the specific cluster may include multiple service devices, the configuration information may additionally specify a communication configuration associated with the specific cluster. For example, the communication configuration may specify one or more of a cluster identifier for the specific cluster, an interface type used for communication between devices in the specific cluster, communication resources allocated for the specific cluster, a key used for communication between devices in the specific cluster, or a multicast address or L2 identifier for the specific cluster. Other configurations are also possible.
[0081] According to some embodiments, the control device may be further configured to send an indication to the requesting device that the requested specific service is supported. The indication may, for example, include identification information associated with the selected specific service device. Optionally, the indication may also include a set service parameter value for the specific service device.
[0082] It should be understood that the above description is merely an exemplary embodiment of the method 300. Details of each step of the method 300 as well as additional or optional steps will be further described below.
[0083] FIG4 shows a flow chart of a method 400 according to some embodiments of the present disclosure. According to some embodiments, the method 400 may be performed at a service device. The service device may be implemented by the aforementioned electronic device 200. Accordingly, the method 400 may be performed by the processing circuit 230 of the electronic device 200.
[0084] Method 400 may begin at step 410. In step 410, the service device may be configured to send registration information to the control device. The registration information may include service capability information associated with services that the service device can provide. For example, the service capability information may include, but is not limited to, supported service types, supported service parameter ranges, communication capacity requirements per unit of service capability, or mobility information associated with the service device.
[0085] Method 400 may continue to step 420. In step 420, the service device may be configured to receive configuration information associated with a specific service from the control device. In some embodiments, the configuration information may specify that the service device forms a specific cluster with a requesting device requesting the specific service.
[0086] According to some embodiments, the service device receives the configuration information only if the service capability information of the service device matches the specific service requested by the user equipment.
[0087] According to some embodiments, the service device is awakened to provide the service after receiving the configuration information. The service device may remain in a low-power state when the configuration information is not received. According to some embodiments, the configuration information also specifies the activated functions or services of the service device. Additionally, the configuration information also specifies the service parameter values to be set for the service device.
[0088] According to some embodiments, the configuration information may further specify a communication configuration associated with the particular cluster. The communication configuration may include, but is not limited to, a cluster identifier for the particular cluster, an interface type used for communication between devices in the particular cluster, communication resources allocated for the particular cluster, a key used for communication between devices in the particular cluster, or a multicast address or L2 identifier for the particular cluster.
[0089] Method 400 may continue to step 430. In step 430, the service device may be configured to perform the specific service based at least on the configuration information. According to some embodiments, the service device may activate corresponding functions or services based on the configuration information to enable the specific service. Additionally, the activated functions or services of the service device may be executed based on service parameter values in the configuration information. Preferably, the service device may communicate based on the communication configuration in the configuration information, including but not limited to inter-device communication with other devices in the specific cluster.
[0090] It should be understood that the above description is merely an exemplary embodiment of the method 400. Details of each step of the method 400 as well as additional or optional steps will be further described below.
[0091] FIG5 shows a flow chart of a method 500 according to some embodiments of the present disclosure. According to some embodiments, the method 500 may be performed at a control device. The control device may be implemented by the aforementioned electronic device 100. Accordingly, the method 500 may be performed by the processing circuit 130 of the electronic device 100.
[0092] Method 500 may begin at step 510. In step 510, a control device may be configured to receive a group session request from a specific cluster including one or more devices. The group session request may include at least task information. The task information may be associated with one or more tasks to be performed by the one or more devices.
[0093] According to some embodiments, the task information may include a task list, which may specify the one or more tasks. As an example, the one or more tasks may include at least one of the following: a sensing task, an industrial production task, a device movement task, or a media presentation task.
[0094] Additionally or alternatively, the task information may include a communication time requirement that specifies timing information for completing one or more transmissions associated with the one or more tasks. For example, the timing information may include a specified time period for completing each of the one or more transmissions.
[0095] Additionally or alternatively, the task information may include communication quality of service (QoS) associated with the one or more tasks. For example, the QoS may be associated with at least one of communication priority, bandwidth, latency, packet loss rate, and redundancy.
[0096] According to some embodiments, the group session request may include identification information associated with the specific cluster. The identification information may include, but is not limited to, a cluster identifier of the specific cluster, a device identifier of at least one device in the specific cluster, or authentication information associated with the specific cluster.
[0097] According to some embodiments, the group session request may include a group session establishment request for establishing a session associated with the specific cluster. According to other embodiments, the group session request may include a group session update request for modifying a current group session associated with the specific cluster.
[0098] The method 500 may continue to step 520 . In step 520 , the control device is configured to send a group communication policy to the specific cluster. The group communication policy may be based at least in part on the task information obtained in step 510 .
[0099] In some embodiments, the group communication policy may be applied to communications between devices in the particular cluster and external devices outside the particular cluster. Such communications may be referred to as external communications associated with the particular cluster. External devices of the particular cluster may include, for example, a control device or other devices or networks external to the cluster. In other words, the group communication policy (or at least a portion thereof) may not be directed to communications between multiple members within the particular cluster (or, in other words, internal communications).
[0100] According to some embodiments, the group communication strategy may include a communication plan for the particular cluster. In some examples, the communication plan may include a time domain communication schedule for one or more transmissions performed by one or more devices in the particular cluster to complete the one or more tasks. Additionally or alternatively, the communication plan may include a communication path configuration for the one or more transmissions. Preferably, the communication plan is based at least in part on the communication time requirements and / or the communication quality of service (QoS) in the task information.
[0101] According to some embodiments, the one or more devices may include a specific device that can operate as a relay device. For example, the specific device may have a relatively fixed location. For another example, the specific device may be located at or near the center of the cluster. For another example, the specific device can communicate with other devices in the one or more devices in the cluster via a wired connection, or can communicate with external devices of the cluster via a wired connection. Therefore, the specific device has the potential to operate as a relay device. Accordingly, the communication path configuration in the group communication policy may include a relay configuration, which can specify the specific device as a relay device in the specific cluster. The relay device can at least be used to route external communications associated with the specific cluster.
[0102] Additionally, the communication path configuration may also include a transmission configuration, which specifies which data in external communications associated with the specific cluster should be transmitted via the relay device. For example, the transmission configuration may specify different communication paths for a first data transmission and a second data transmission. For example, the first data transmission may be transmitted to or received from an external device of the specific cluster via at least the relay device. The second data transmission may be transmitted to or received from an external device of the specific cluster without passing through the relay device.
[0103] According to some embodiments, the designation of a communication path may be based on the priority of the data. For example, the first priority of a first data transmission may be different from the second priority of a second data transmission. Therefore, the first data transmission and the second data transmission may be assigned different communication paths. For example, in response to the first priority being higher than the second priority, the first data transmission may be transmitted through a more reliable connection (e.g., a wired connection), while the second data transmission may be transmitted through other means (e.g., a wireless connection). Specifically, when the first data transmission has a higher priority than the second data transmission, the first data transmission may be transmitted to an external device of a specific cluster through the PC5 interface of the relay device and at least one wired connection, while the second data transmission may be transmitted to an external device of a specific cluster through the Uu interface. The priority of the data may be determined based on one or more of the data itself, the task associated with the data, the data source, or the data destination.
[0104] For the specific device that may operate as a relay device, the control device may receive communication capability information associated with the specific device. The relay configuration and / or communication path configuration in the group communication strategy may be based on the communication capability information. For example, the communication capability information may include the communication capability (e.g., latency or bandwidth) of at least one wired connection of the specific device. Additionally, the communication capability information may include the wireless communication capability of the specific device. For example, the specific device may have a PC5 interface for side link communication. The wireless communication capability may include the QoS range supported by the PC5 interface, such as the maximum rate on the interface, the supported frequency range, etc. When the lower of the communication capability of the PC5 interface and the at least one wired connection meets the threshold communication condition, the first data transmission may be routed through the combination of the PC5 interface and the at least one wired connection. For example, the specific device may receive a first data transmission from other devices via the PC5 interface, and then send the first data transmission to the outside of the cluster via the at least one wired connection.
[0105] According to some embodiments, stability information of a particular cluster may be determined. The stability information may be associated with the stability of the cluster. Specifically, the stability information may indicate the length of time that a particular cluster can remain stable. The stability information may be determined at least in part based on the task of the cluster. For example, tasks of the factory assembly line processing type may have stronger cluster stability than tasks of internal factory transportation. For example, a first cluster associated with a first task may be more stable than a second cluster associated with a second task. The group communication strategy determined for the cluster may be based at least in part on the stability information. The control device may send the stability information. The stability information may be sent together with or separately from the group communication strategy.
[0106] According to some embodiments, a control device may be associated with multiple clusters. The control device may configure a group communication strategy for each cluster across the clusters. The configured one or more group communication strategies may take into account interference between clusters, thereby minimizing the interference. For example, the aforementioned specific cluster may be the first cluster among the multiple clusters, and the aforementioned communication plan may be a first group communication strategy for the first cluster. The control device may be configured to optimize the first group communication strategy for the first cluster based at least in part on a second group communication strategy for a second cluster among the multiple clusters, so that interference between the first group communication strategy and the second group communication strategy can be minimized. For example, by adjusting the task content of the first group and the task content of the second group, the communication peak of the first communication strategy in the first group communication strategy may be staggered in the time domain or frequency domain with the communication peak of the second communication strategy in the second group communication strategy. For another example, the first communication strategy and the second communication strategy may reuse certain communication resources. If the first cluster has lower stability than the second cluster (for example, stability information indicates that the first cluster has a shorter stabilization time), communication resources may be preferentially allocated to the first cluster. In some embodiments, the optimization may be performed in response to the first cluster and the second cluster being spatially close (for example, the distance is less than a threshold). Additionally or alternatively, the optimization can be performed in response to the first cluster and the second cluster containing shared service devices (e.g., containing more than a specified number or percentage of common service devices). For example, the shared service devices can be scheduled to prioritize completing tasks corresponding to the first cluster with lower stability.
[0107] It should be understood that the above description is merely an exemplary embodiment of the method 500. Details of each step of the method 500 as well as additional or optional steps will be further described below.
[0108] FIG6 shows a flow chart of a method 600 according to some embodiments of the present disclosure. According to some embodiments, the method 600 may be performed at a user device. The user device may be implemented by the aforementioned electronic device 200. Accordingly, the method 600 may be performed by the processing circuit 230 of the electronic device 200.
[0109] Method 600 may begin at step 610. In step 610, a user device may be configured to send a group session request to a control device. The group session request may include at least task information. The task information may be associated with one or more tasks to be performed by the user device.
[0110] As previously described, the task information may include a task list specifying the one or more tasks. The task information may also include a communication time requirement, which specifies timing information for the user equipment to complete one or more transmissions associated with the one or more tasks. Additionally, the task information may also include a communication quality of service (QoS) associated with the one or more transmissions.
[0111] Method 600 may continue to step 620. In step 620, the user device may be configured to receive a group communication policy associated with a particular cluster from the control device. The particular cluster may include multiple user devices, which may include the user device executing method 600. The group communication policy is based at least in part on the task information of the user device.
[0112] According to some embodiments, the group communication strategy may include a communication plan for the user equipment. Specifically, for example, the communication plan may include a time domain communication schedule for one or more transmissions of the user equipment. Additionally or alternatively, the communication plan may include a communication path configuration for one or more transmissions of the user equipment.
[0113] According to some embodiments, the specific cluster may include a specific device that is capable of communicating with other devices in the one or more devices via at least one wired connection. In this case, the communication path configuration in the group communication policy may include a relay configuration and a transmission configuration. The relay configuration may designate the specific device as a relay device in the specific cluster. The transmission configuration may designate that a first data transmission is transmitted through the relay device and that a second data transmission is not transmitted through the relay device, wherein the first data transmission has a higher priority than the second data transmission.
[0114] According to some embodiments, the user device performing method 600 may have the potential to act as a relay device in a particular cluster. For example, the user device may have at least one wireless connection to one or more other devices in the cluster (e.g., via a PC5 interface) and at least one wired connection to a device outside the cluster. In this case, the user device may be configured to send communication capability information associated with the user device to the control device. The communication capability information may include the communication capability (e.g., latency or bandwidth) of the at least one wired connection of the user device. The communication capability may also include the communication capability (e.g., maximum rate on the PC5 interface, supported frequency range, etc.) of the at least one wireless connection of the user device. The communication capability information may be included in the group session request or may be sent separately to the control device.
[0115] Method 600 may continue to step 630. In step 630, the user device may be configured to perform one or more tasks of the user device based on the group communication strategy. For example, the user device may perform one or more transmissions associated with the one or more tasks based on the time domain communication schedule in the group communication strategy, so that the transmission associated with each task occurs according to the time domain communication schedule. Additionally or alternatively, the user device may transmit or receive the transmission associated with each task based on the communication path configuration in the group communication strategy. When the user device is designated as a relay device, the device may receive data transmissions (e.g., first data transmissions) from other devices via the PC5 interface and route the received transmissions to the outside of the cluster via a wired connection. When the user device is not designated as a relay device, the device may send the first data transmission to the designated relay device via the PC5 interface for forwarding to the external device, and may send the second data transmission to the external device via its own Uu interface. The combined path of the PC5 interface and the wired connection may have higher reliability than the Uu interface and may therefore be used to send transmissions with higher priority.
[0116] It should be understood that the above description is merely an exemplary embodiment of the method 600. Details of each step of the method 600 as well as additional or optional steps will be further described below.
[0117] 3. Example Process
[0118] Figure 7 shows a schematic diagram of a process 700 according to some embodiments of the present disclosure. Process 700 can be used to build or update a cluster. The cluster can be built or updated around a service or task. Process 700 can be performed by a control device and one or more user devices. The control device can be implemented by electronic device 100. The user devices can be implemented by electronic device 200.
[0119] In some embodiments, process 700 can be performed in a cellular communication scenario. In some embodiments, the control device may include a network element residing on the network side of the cellular network. For example, the control device may include an access and mobility management function (AMF) network element. For another example, the control device may include a base station. Alternatively, the control device may include other network elements or be implemented across multiple network elements. Each user equipment may include a UE in a cellular network. One or more UEs may be numbered from 1 to X. It should be understood that the cellular communication scenario shown in Figure 7 is merely exemplary. In other embodiments, the technology of the present disclosure may be implemented in other scenarios without limitation.
[0120] Process 700 may start at step 710. In step 710, one or more UEs (eg, UE#2 to UE#X) may send registration information to a control device. The registration information may include service capability information associated with services that each UE can provide.
[0121] A UE capable of providing services may be referred to as a service device. Services provided by a service device may include services required to complete specific tasks. These specific tasks may include, but are not limited to, sensing tasks, industrial production tasks, device mobility tasks, media presentation tasks, and the like. Service devices may include, but are not limited to, sensor devices, industrial production equipment, vehicle-mounted devices, multimedia devices, aircraft devices, or access points.
[0122] As an example, a sensor device may provide a measurement service, and the measured results may be provided to complete a specific task. As another example, an industrial production device may provide a processing service, which may include one or more processes of an industrial production task. As yet another example, an on-board device or a flight device may provide one or more services associated with device movement (e.g., driving or flying), such as map updates, sensor fusion, driving decisions, user interaction, automatic formation, etc., and the one or more services may be used to automatically or semi-automatically control the driving or flying of the device. As yet another example, a multimedia device may provide a media rendering service (e.g., presenting audio, video, tactile output, etc.), which may be used to complete XR tasks. As yet another example, an access point device may provide a network access service, which may be used to complete communication tasks. Examples of access point devices may include wireless access points, such as Wi-Fi access points or cellular base stations.
[0123] According to some embodiments, the service capability information of each service device may include the service type and the supported service parameter range supported by the device.
[0124] For sensor devices, the supported service types can indicate which specific physical or chemical properties the device can measure. The supported service parameter ranges can indicate the range, accuracy, and measurement environment requirements for each specific property that the sensor device can measure. Other natural properties and associated parameters are also possible.
[0125] For industrial production equipment, the supported service types can indicate the processes that the equipment can complete, such as actions such as gripping, moving, assembling, disassembling, painting, and inspecting products. The supported service parameter ranges can indicate the parameter ranges associated with the process, such as the range of motion, duration, and processing accuracy of each action. Other processes and associated parameters are also possible.
[0126] For in-vehicle or aircraft devices, the supported service types may indicate the functions that the device can perform, such as positioning, identifying environmental conditions, identifying obstacles, path planning, identifying traffic conditions, providing entertainment information, providing reminders, etc. The supported service parameter ranges may indicate the parameter ranges associated with each function, such as positioning accuracy, positioning frequency, identification range, identification resolution, etc. Other functions and associated parameters are also possible.
[0127] For multimedia devices, supported service types may indicate the media types that the device can output, such as visual media content, auditory media content, tactile media content, olfactory media content, etc. Supported service parameter ranges may include parameter ranges associated with media content output, such as resolution, duration, media format, output intensity, etc. Other media types and associated parameters are also possible.
[0128] For an access point device, the supported service type may indicate the communication protocol type, device type, etc. that the device can support. The supported service parameter range may include frequency bands, bandwidths, delays, etc. associated with communication. Other associated parameters are also possible.
[0129] Preferably, the service capability information of each service device may include mobility information of the service device. The mobility information may include the location of the service device. Additionally, the mobility information may include the speed, acceleration, and orientation of the service device. The mobility information of the service device may be used to determine the spatial relationship between the device and other devices and to select an appropriate service device, as further described below.
[0130] The control device may store the received registration information. For example, the control device may store the registration information locally on the control device or in another location accessible to the control device.
[0131] In step 720, UE#1 may send a service request to the control device. The service request may be associated with a specific service requested by UE#1. For example, when UE#1 requires a specific service to complete a specific task, UE#1 may send a service request to the control device.
[0132] UE#1 that sends the service request can be referred to as the requesting device. It should be understood that the requesting device may or may not be a serving device. For example, UE#1 may be a vehicle controller that does not itself provide a specific service but instead controls vehicle operation based on the services of other serving devices. Alternatively, UE#1 may be an in-vehicle head unit that controls vehicle operation based on the services of the serving device and may also provide one or more services, such as multimedia services.
[0133] In a V2X scenario, UE#1 may be a vehicle controller (or vehicle UE). Serving devices UE#2 through UE#X may be UEs providing services to the vehicle UE. Serving devices UE#2 through UE#X may include, but are not limited to, RSU UEs, edge server UEs, traffic management equipment UEs, and even base stations. In some cases, UE#2 through UE#X may include another vehicle UE providing services to the vehicle UE. These serving devices may be capable of communicating via a Uu interface (data network communication) or via a PC5 interface (short-range direct communication) with the vehicle UE. In step 710, the serving device may register the type and specific specifications of the services it can provide with the control device. For example, in a sensor fusion scenario associated with a vehicle UE, serving devices UE#2 through UE#X may provide the control device with information such as sensor specifications, sensor coverage, and fusion perception method parameters in step 710. The serving device may also provide the control device with its location. Under the V2X concept (e.g., the China Communications Standards Association (CCSA) / 5G Automotive Alliance (5GAA)), the control device may comprise a central subsystem or be part of such a central subsystem. Under the 3rd Generation Partnership Project 3GPP concept, the control device may be part of a core network.
[0134] In the smart factory scenario, service devices UE#2 to UE#X may be one or more factory devices (referred to as manufacturing UEs) with processing capabilities. These UEs may expose their capabilities to a control device (e.g., located in the core network) in step 710, including a capability identifier, a maximum capability capacity (which may indicate a capability quantification parameter), and a conversion relationship between capability value and communication volume (e.g., a communication capacity requirement corresponding to each unit of service capability, which may be represented as an X-value capability corresponding to a Y-bit data transmission requirement). Example capabilities of service devices may include sensing capabilities (e.g., perception of various modalities), production capabilities (associated with processing processes such as grasping, machining, welding, and painting), and measurement and inspection capabilities (e.g., quality inspection of products).
[0135] In other scenarios, example capabilities of the service device may include drone flight parameters (e.g., cruising speed, control distance, payload) or vehicle driving capabilities (e.g., vehicle control mode, cruising speed), etc.
[0136] According to some embodiments, the service request from UE#1 may include but is not limited to the UE's subscription information, service type requirements, or service parameter requirements.
[0137] In some embodiments, the subscription information of UE#1 may include identification information or authentication information of UE#1, which may be used to identify the service type or service device set to which UE#1 has subscribed.
[0138] In some embodiments, the service type requirement may include a list of one or more services required to complete a specific task of UE#1.
[0139] In some embodiments, the service parameter requirements may include parameter ranges of one or more services required to complete a specific task of UE#1.
[0140] In some embodiments, UE#1 may send a service request based on a trigger condition. In other embodiments, UE#1 may periodically send a service request. For example, in response to the initiation of a specific task, UE#1 may begin sending a service request. Additionally, UE#1 may periodically send the service request during the duration of the specific task. UE#1 may stop sending the service request after completing the specific task.
[0141] As an example, in a V2X scenario, a vehicle UE (as UE#1) can request service support from the network upon vehicle startup. This service support may include service requests for one or more services. In some cases, the vehicle UE may send service requests at predetermined time intervals or distance intervals. Additionally or alternatively, the vehicle UE may send updated service requests in response to an increase or change in available service types. For example, when a vehicle travels in a mountainous area, the vehicle UE may require roadside equipment capable of providing high-precision positioning to provide assisted positioning. Alternatively, when the vehicle travels on different road sections (e.g., highways and urban roads), the sensor fusion services required by the vehicle UE (e.g., sensor type, sensor accuracy, etc.) may change. Additionally or alternatively, the vehicle UE may send service requests in response to user operations. The service request sent by the vehicle UE may include the vehicle UE's subscription information. This subscription information may include the vehicle UE's GPSI (or other identifier) and authentication information. Additionally or alternatively, the service request may also include the services required by the vehicle UE, which may include an identifier for the service application (indicating the service type), service parameters, and / or service level. The service request of the vehicle UE may also include mobility information of the vehicle UE, such as the vehicle's location, speed, acceleration, driving direction, etc.
[0142] In step 730, in response to receiving the service request from UE#1, the control device may select a specific UE from the one or more serving devices (e.g., UE#2 to UE#X) based on a match between the service capability information and the service request. This matching may be performed based on one or more criteria.
[0143] Based on the first example criterion, the control device may determine that a specific service device matches the subscription information of the user device. For example, the control device may determine that the specific service device can provide the service type to which the user device has subscribed. Additionally or alternatively, the control device may determine that the specific service device is within a set of service devices to which the user device has subscribed. Specifically, the identification information and authentication information in the user device's subscription information may be used to determine whether the user device is authorized to obtain the specific service type or the services of the specific service device.
[0144] According to the second example criterion, the control device may determine that the service types supported by the specific service device match the service type requirements of the user device. For example, in response to at least one service type supported by the specific service device being the same as at least one service type requirement of the user device, the match may be considered successful.
[0145] According to the third example criterion, the control device may determine that the service parameter range supported by the specific service device matches the service parameter requirement of the user equipment. For example, in response to the service parameter range supported by the specific service device meeting the service parameter requirement of the user equipment, the match may be considered successful.
[0146] According to the fourth example standard, the control device can determine whether the spatial relationship between the specific service device and the user device meets a predetermined condition. The spatial relationship can be determined based on the mobility information of the service device and the mobility information of the user device. In some examples, the specific service device and the user device may be required to have a specified positional relationship. For example, the distance between the specific service device and the user device needs to be less than a threshold, within a specified threshold interval, or greater than a threshold. In other examples, the specific service device and the user device may be required to have a specified motion relationship. For example, the relative speed or relative acceleration between the specific service device and the user device needs to be less than a threshold, within a specified threshold interval, or greater than a threshold. For example, when UE#1 is a moving vehicle-mounted device, a specific service device within a threshold distance of the vehicle-mounted device can be selected. The selected specific service device can change as UE#1 moves, so that UE#1 can obtain service uninterruptedly.
[0147] It will be understood that the above example standards are merely examples and not limitations, and one or more of these example standards may be applied individually or in combination.
[0148] In FIG7 , by way of example and not limitation, the selected specific service device is UE#2. Accordingly, in step 740A, the control device may send first configuration information to the selected UE#2. The first configuration information may be associated with the specific service requested by UE#1.
[0149] According to some embodiments, the configuration information may specify that a particular service device be awakened or activated. In many scenarios, service devices may not have access to a continuous power supply. Therefore, it is desirable to minimize the energy consumption of service devices. After registering with the control device, the service device may remain in a low-power state. The service device may be awakened only after receiving the configuration information.
[0150] Additionally, the configuration information may also specify the activated functions or services of the specific service device. For example, the configuration information may specify the specific type of sensor, specific fusion algorithm, specific recognition algorithm, computing capacity, etc. of the specific service device. As an example, UE#2 may be a multimedia device, and the first configuration information may at least specify which types of video media content, audio media content, and tactile media content the multimedia device outputs. For another example, UE#2 may be a sensor device, and the first configuration information may specify the physical or chemical properties that UE#2 should measure and activate the corresponding sensing functions accordingly.
[0151] Additionally, the first configuration information may also specify a set service parameter value for UE#2. For example, if UE#2 is a multimedia device, the first configuration information may specify the time or intensity at which UE#2 outputs media content. For another example, if UE#2 is a sensor device, the first configuration information may specify a sampling frequency for measurements performed by UE#2.
[0152] Additionally, the first configuration information may also specify a communication configuration for the specific service device, as further described below.
[0153] The control device may also send second configuration information to UE#1 that issued the service request in step 740B. The second configuration information may include an indication that the specific service requested by UE#1 is supported. The indication may, for example, include identification information associated with the selected specific service device (e.g., UE#2). Optionally, the indication may also include a set service parameter value for UE#2. In response to receiving the second configuration information, UE#1 may anticipate which device will satisfy the requested specific service and to what extent. UE#1 may adjust its own operation based on the expectation. Additionally, the second configuration information may also specify the communication configuration of the user equipment, as further described below.
[0154] According to some embodiments, the service request issued by UE#1 may be associated with multiple services. For example, the service request of UE#1 may include multiple services associated with one or more tasks. Accordingly, the control device may select a specific service device for each service in step 730. The control device may send first configuration information for each specific service device to the device in step 740A. Each first configuration information may include at least a portion specific to that service. The second configuration information sent by the control device in step 740B may include an indication of each supported service. The indication may include identification information of the corresponding service device and a service parameter value.
[0155] According to some embodiments, the multiple service devices providing the multiple services for UE#1 may be organized into a cluster. The cluster may include UE#1 and may additionally include multiple service devices selected from UE#2 to UE#X. Accordingly, the first configuration information and the second configuration information sent in steps 740A-740B may specify that UE#1 forms a cluster with the selected multiple service devices. Additionally, the first configuration information and the second configuration information may include a communication configuration associated with the cluster.
[0156] As an example, the communication configuration may include a cluster identifier for identifying the cluster. The cluster identifier may be used to notify the device (including the requesting device and the serving device) that has received the communication configuration of the specific cluster to which the device belongs. In some examples, each device may belong to one or more clusters. For example, UE#1 may send multiple service requests for multiple tasks, each task being associated with a corresponding cluster. For another example, serving device UE#2 may serve multiple requesting UEs, each requesting UE corresponding to a corresponding cluster. Different clusters may be assigned different identifiers. The cluster identifier may identify each specific cluster in intra-cluster communication, inter-cluster communication, and communication between a cluster and a control device, for example, for authentication and authorization.
[0157] Additionally or alternatively, the communication configuration may specify the type of interface used for communication between devices in the particular cluster. For multiple devices in a particular cluster, it may be specified that at least a portion of the communication between the devices no longer passes through the core network (e.g., data network), but instead passes through an inter-device link. An inter-device link may include, but is not limited to, a side link or a wired link. The communication configuration may specify whether the communication between two devices in the cluster is through a side link, through a wired link, or through a core network or data network, and specify the interface used for each type of communication (e.g., a PC5 interface, a Uu interface, or a wired interface). For example, the communication configuration may specify whether each service device serves the requesting device through a PC5 interface, or serves the requesting device through a combination of a Uu interface and a data network.
[0158] Additionally or alternatively, the communication configuration may specify a key for communication between devices in a particular cluster. For example, the specified key may be used for authentication between multiple devices in the particular cluster. Additionally, the communication configuration may specify a multicast address for the particular cluster. Additionally, the communication configuration may specify an L2 identifier for the particular cluster.
[0159] Additionally or alternatively, the communication configuration may specify the communication resources allocated to the particular cluster. The communication resources may include resources allocated for side link communication or cellular communication through the core network. For example, the communication configuration may specify the frequency band and time slot used for communication between two devices in the cluster. In the scenario of a smart factory, the control device may determine the service devices involved in the processing task based on the service capability information of the service devices (UE#2 to UE#X) and the service request of the user device (UE#1). Based on the communication capacity requirements corresponding to the per-unit service capability of the determined service device, the control device may also collaborate with network-side devices such as SMF and RAN to formulate a communication configuration for the determined service device. The communication configuration may include, for example, a multicast strategy, etc.
[0160] In step 750, the specific service device UE#2 selected in step 730 can interact with UE#1 that initiated the service request to perform a specific task. Specifically, UE#2 can operate in accordance with the first configuration information to provide a specific service. UE#1 can operate in accordance with the second configuration information to complete the specific task with the help of the specific service provided by UE#2. UE#1 and UE#2 can communicate with each other. For example, UE#1 or UE#2 can perform a discovery process broadcast message to trigger unicast establishment. Each UE can also send and receive data packets to a specific IP. In some embodiments, the communication can be performed based on the aforementioned communication configuration. For example, UE#1 and UE#2 can first authenticate each other using a cluster-specific key. In response to successful authentication, UE#1 and UE#2 can continue to communicate. For another example, according to some communication configurations, UE#2 can provide services through a specified PC5 interface. Alternatively, according to other communication configurations, UE#2 can provide services through a combination of a Uu interface and a data network.
[0161] Figure 8 shows a schematic diagram of a process 800 according to some embodiments of the present disclosure. Process 800 can be used to establish or update a group session associated with a cluster. Process 800 can be performed by a control device and one or more user devices. The control device can be implemented by electronic device 100. Each user device can be implemented by electronic device 200.
[0162] In some embodiments, process 800 can be performed in a cellular communication scenario. In some embodiments, the control device may include a network element residing on the network side of the cellular network. For example, the control device may include an access and mobility management function (AMF) network element. For another example, the control device may include a base station. Alternatively, the control device may include other network elements or be implemented across multiple network elements. Each user equipment may include a UE in a cellular network. One or more UEs in Figure 8 may be numbered 1 to X. Other numbers of UEs are also possible. It should be understood that the cellular communication scenario shown in Figure 8 is merely exemplary. In other embodiments, the technology of the present disclosure may be implemented in other scenarios without limitation.
[0163] In some embodiments, the one or more user equipments UE#1 to UE#X have formed a specific cluster. In some examples, the specific cluster can be formed by the process described in Figure 7. In other examples, the specific cluster can be formed by any other suitable process.
[0164] In some scenarios, UE#1 to UE#X may include manufacturing UEs in a factory, which are controlled by a control device (e.g., a remote server) to collaboratively process a product. In some scenarios, UE#1 to UE#X may include cranes or unmanned trucks at a port, which are controlled by a control device to load, unload, organize, or transfer goods. In some scenarios, UE#1 to UE#X may include vehicle UEs, which are controlled by a control device to collaboratively form a platoon. In some scenarios, UE#1 to UE#X may include multiple XR devices, which are controlled by a control device to collaboratively render a scene. Other types of UEs are also possible.
[0165] In step 810, one or more UEs in the cluster may send a group session request to the control device. According to some embodiments, the group session request may include a group session establishment request. The group session establishment request may be used to initially establish a session associated with the specific cluster. According to other embodiments, the group session request may include a group session update request. The group session update request may be used to modify the group session associated with the specific cluster. For example, after the group session has been established, the group session update request may be triggered in response to an environmental change or a task change.
[0166] According to some embodiments, the group session request may include identification information associated with the specific cluster. The identification information may include a cluster identifier for the specific cluster. The cluster identifier may be assigned when the cluster is established. The identification information may also include a device identifier (e.g., GPSI, GUTI, SUPI) of at least one device among the one or more devices in the cluster. Preferably, the identification information may also include authentication information associated with the specific cluster.
[0167] According to some embodiments, the group session request may include at least task information. The task information may be associated with one or more tasks to be performed by UE#1 to UE#X. As previously described, the one or more tasks may include a sensing task, an industrial production task, a device movement task, a media presentation task, and the like.
[0168] According to some embodiments, the task information may include a task list for each UE among UE#1 to UE#X, where the task list may include the one or more tasks to be performed by each UE. For example, the task list may include an identifier for each task. In some examples, the task list may also include corresponding resource parameters for each task.
[0169] According to some embodiments, the task information may further include a communication time requirement. The communication time requirement may specify the timing information of one or more transmissions performed by each UE in order to complete the one or more tasks. As an example, the timing information associated with each task may include a specified time period for completing the data transmission associated with the task. For example, for a transmission associated with a one-time task (for example, a single processing task in a smart factory scenario, or a single task in a V2X scenario), the timing information may specify the time period (for example, t1 to t2) in which the one-time transmission should occur. For another example, for a transmission associated with a periodic task (for example, a processing task performed repeatedly on an assembly line), the timing information may specify the time period in which the periodic transmission occurs in each cycle. For example, when the cycle is T, the time period may be t1 to t2 within each cycle T.
[0170] According to some embodiments, the task information may further include a communication quality of service (QoS) associated with the one or more tasks. For example, the QoS may be associated with at least one of communication priority, bandwidth, latency, packet loss rate, and redundancy. Each task may have a different QoS.
[0171] Process 800 may continue to step 820. In step 820, the control device may be configured to obtain a group communication policy. The group communication policy may be based at least in part on the task information obtained in step 810. For example, the control device may generate the group communication policy based at least in part on the task information. When the control device is a network element (e.g., an AMF), the control device may collaborate with one or more other network elements to obtain the group communication policy, as described further below.
[0172] In some embodiments, the group communication policy may be applied to communications between devices in the cluster (e.g., UE#1 to UE#X) and external devices outside the cluster. Such communications may be referred to as external communications associated with the cluster. External devices of the cluster may include, for example, a control device or other devices outside the cluster (e.g., other devices in a core network or a data network). External communications may, for example, include communications that require access to a data network or a core network. In contrast, internal communications within a cluster may not require passing through a data network or a core network, but may be performed between devices in the cluster via inter-device links.
[0173] According to some embodiments, the group communication strategy includes a communication plan for the specific cluster. In some examples, the communication plan may include a time domain communication schedule for one or more devices in the specific cluster. For example, the time domain communication schedule may indicate the distribution of the communication behavior of each device in the time domain. Additionally, the time domain communication schedule may indicate the distribution of the communication rate of the cluster as a whole in the time domain. In some examples, the distribution of the communication rate may be a uniform distribution. In some examples, the distribution of the communication rate may be a non-uniform distribution. The non-uniform distribution may have a distribution shape specified by the time domain communication schedule. The distribution shape may, for example, include one or more specified peaks and / or one or more valleys. The time domain communication schedule may be determined at least in part based on the communication time requirements in the task information.
[0174] In some examples, the communication plan may also include a communication path configuration for one or more devices in the particular cluster. The communication path configuration may specify a communication path for connecting to the outside of the cluster. The communication path may include multiple types. For example, a first type of path may include a relay. The path may include a combination of a wireless connection (e.g., a PC5 interface) and a wired connection. For another example, a second type of path may not include a relay and may include only a wireless connection (e.g., a Uu interface). The communication path configuration may specify different communication paths for different types of data.
[0175] Specifically, the communication path configuration may include a relay configuration. The relay configuration may designate a specific device in a cluster as a relay device in the specific cluster. For example, the specific device may have a relatively fixed location. Additionally or alternatively, the specific device may be located at or near the center of the cluster. Additionally or alternatively, the specific device may be able to communicate with devices external to the cluster via at least one wired connection and with at least one other device in the cluster via at least one wireless connection.
[0176] The specific device may indicate in the group session request sent in step 810 that it has the ability to operate as a relay device. Optionally, the specific device may report communication capability information to the control device. The communication capability information may include the communication capability (e.g., latency or bandwidth) of at least one wired connection of the specific device. Additionally, the communication capability information may include the wireless communication capability of the specific device. For example, the specific device may have a PC5 interface. The PC5 interface may be used, for example, for sidelink communication. Accordingly, the wireless communication capability of the specific device may include the QoS range supported by the PC5 interface, such as the maximum rate on the interface, the supported frequency range, etc. The control device may specify a relay device based at least in part on the communication capability information. For example, the control device may determine whether to designate the specific device as a relay device to receive transmissions from other UEs via the PC5 interface based at least in part on the QoS range supported by the PC5 interface. For a specific cluster, the control device may designate any suitable number of relay devices, such as zero, one, or more.
[0177] Additionally, the communication path configuration may further include a transmission configuration for specifying which data in the external communication associated with the particular cluster should be transmitted via the relay device. Optionally, the transmission configuration is used to specify how to transmit via the relay device. For example, the transmission configuration may specify that the first data transmission is transmitted via a combination of a wired connection and a wireless connection, while the second data transmission is transmitted only via wireless communication. Accordingly, the first data transmission may be transmitted by the UE to the relay device (e.g., via a PC5 interface), and then routed by the relay device to a device outside the cluster. In contrast, the second data transmission may be transmitted directly by the UE via wireless transmission (e.g., via a Uu interface) to a device outside the cluster.
[0178] According to some embodiments, the designation of a communication path may be based on data priority. For example, the first priority of a first data transmission may be higher than the second priority of a second data transmission. Therefore, the first data transmission may be transmitted via a more reliable communication path. Wired connections are generally considered to have higher reliability. Therefore, the first data transmission may be transmitted via a combination of wired and wireless connections. The second data transmission may be transmitted solely via wireless communication.
[0179] The process 800 may continue to step 830. In step 830, the control device may send the group communication policy to UE#1 to UE#X in the cluster.
[0180] Then, in step 840, UE#1 to UE#X may perform tasks based on the group communication policy. Specifically, UE#1 to UE#X may perform one or more transmissions associated with one or more tasks specified in the task list based at least on the group communication policy.
[0181] As an example, each UE can perform data transmissions associated with each task based on the time domain communication schedule in the group communication policy. These data transmissions can be performed at the specified time, thereby matching the timing information associated with the task. Additionally, the overall distribution of data transmissions from all UEs in the time domain can meet the distribution specified by the time domain communication schedule.
[0182] As another example, each UE can perform communication with devices outside the cluster based on the communication path configuration in the group communication policy. In the example of Figure 8, UE#X is a fixed UE. Therefore, UE#X is designated as a relay device by the group communication policy. In step 840, the relay device UE#X can route transmissions of other UEs to devices outside the cluster. For example, UE#X can receive transmissions from other UEs in the cluster through a PC5 interface or a wired interface. UE#X can route the received transmissions to the outside of the cluster, for example, to a control device, through a wired connection or a wireless connection. It can be understood that UE#1 to UE#X can include multiple designated relay devices, and each relay device can serve one or more UEs, thereby achieving load balancing.
[0183] According to an embodiment of the present disclosure, a control device may generate, adjust and optimize another group of communication policies associated with another cluster based at least in part on a group communication policy associated with one cluster. According to some embodiments, such cross-cluster coordination may be performed in response to the establishment or update of a group session. In some examples, due to the establishment of a service within the first cluster, the first cluster sends a group session establishment request, resulting in the control device needing to adjust the second group of communication policies of the second cluster to support the first group of communication policies of the first cluster. In other examples, due to changes in the service within the first cluster, the first cluster sends a group session update request, resulting in the second group of communication policies of the second cluster also being adjusted accordingly. In some other examples, the control device may proactively configure new services and associated group communication policies for the first cluster, which may also trigger the adjustment of the second group of communication policies of the second cluster.
[0184] FIG9 illustrates a schematic diagram of a process 900 according to some embodiments of the present disclosure. Process 900 describes cross-cluster coordination between a first cluster and a second cluster. As an example, the first cluster may include UE#1-1 through UE#1-X (which may correspond to UE#1 through UE#X in FIG8 ), while the second cluster may include UE#2-1 through UE#2-N. In the example of FIG9 , the first and second clusters are shown as non-overlapping. In other examples, the first and second clusters may include one or more shared UEs.
[0185] In step 910, UE#1-1 to UE#1-X in the first cluster may send a group session request to the control device. The group session request may include, for example, task information associated with UE#1-1 to UE#1-X.
[0186] In step 920, the control device may obtain a group communication policy based on cross-cluster coordination. For example, if the control device has not yet configured a second group communication policy for the second cluster, the control device may configure respective group communication policies for the first cluster and the second cluster based on task information associated with the first cluster and task information associated with the second cluster. Alternatively, if the control device has already configured a second group communication policy for the second cluster, the control device may configure a first group communication policy for the first cluster based on the task information associated with the first cluster and the second group communication policy associated with the second cluster. The control device may additionally modify the second group communication policy associated with the second cluster to generate an updated second group communication policy.
[0187] According to some embodiments, cross-cluster coordination may include coordination of communication plans. For example, the control device may optimize the first communication plan for the first cluster based at least in part on the second communication plan for the second cluster. As an example, the first time domain communication schedule specified by the first communication plan may be coordinated with the second time domain communication schedule specified by the second communication plan. For example, the communication peak of the first communication plan may be staggered with the communication peak of the second communication plan in the time domain or frequency domain. Additionally or alternatively, if feasible, the first communication plan and the second communication plan may reuse certain communication resources.
[0188] According to some embodiments, cross-cluster coordination may be performed in response to a specific relationship between the first cluster and the second cluster. For example, the control device may perform cross-cluster coordination in response to the first cluster and the second cluster being spatially close (e.g., an average distance less than a threshold). Additionally or alternatively, the control device may perform cross-cluster coordination in response to the first cluster and the second cluster containing shared service devices (e.g., containing more than a specified number or percentage of shared service devices). Cross-cluster coordination may reduce contention for resources among different clusters, such as reducing contention for shared devices among different clusters. Cross-cluster coordination may also reduce congestion at the control device.
[0189] In step 930A, the control device may send a first set of communication policies associated with the first cluster to UE #1-1 to UE #1-X in the first cluster. In step 930B, the control device may send a second set of communication policies associated with the second cluster (e.g., an updated second set of communication policies) to UE #2-1 to UE #2-N in the second cluster.
[0190] In step 940A, UE#1-1 to UE#1-X may perform tasks based on a first set of communication policies. In step 940B, UE#2-1 to UE#2-N may perform tasks based on a second set of communication policies.
[0191] Figure 10 shows a schematic diagram of a process 1000 according to some embodiments of the present disclosure. Process 1000 describes a process in which an application function (AF) network element provides parameters to a unified data management (UDM) network element via a network exposure function (NEF) network element in a 5G network, so that a policy control function (PCF) network element can obtain policy parameters to be applied to a specific UE.
[0192] In step 1010, the NF may send a Nudm_SDM_Subscribe request to the UDM. Additionally, steps 1010a and 1010b may be optionally performed by the AF and NEF. In step 1010a, the AF may subscribe to and receive UE mobility analysis and / or communication analysis from the Network Data Analysis Function (NWDAF). In step 1010b, the AF may analyze the received data and derive expected UE behavior parameters.
[0193] In step 1020, the AF may send a Nnef_ParameterProvision_Create / Update / Delete request to the NEF. The Nnef_ParameterProvision_Create / Update / Delete request sent by the AF to the NEF in step 1020 may include one or more parameters for the cluster associated with the task.
[0194] The one or more parameters of the cluster associated with the task may include task cluster configuration parameters. The task cluster configuration parameters may include DNN, S-NSSAI, PDU session type, application descriptor, authentication / authorization information, group communication indication, maximum group rate, etc.
[0195] The one or more parameters of the cluster associated with the task may also include membership management parameters. For example, a cluster identifier may be used to uniquely identify the cluster within a certain network or operator. In addition, a GPSI list may be used to identify all UEs within the cluster, where each GPSI may be used to uniquely identify a corresponding UE within the cluster.
[0196] According to some embodiments of the present disclosure, the task cluster configuration parameter may also include one or more new parameters.
[0197] As an example, the one or more new parameters may include a group communication mode. The group communication mode may specify at least one of the following optional communication modes: Uu, PC5, a combination of PC5 and Uu (including broadcast, including PC5 broadcast and Uu broadcast, Uu unicast to a relay node and then PC5 broadcast by the relay node, etc.), a combination of PC5 and wired, etc.
[0198] Additionally or optionally, the one or more new parameters may include group communication service characteristics. The group communication service characteristics may include stability information describing the stability of a cluster consisting of multiple UEs. The stability information may be described in a certain time granularity (e.g., days, hours, minutes, etc.). The stability information may indicate the expected length of time that the cluster can remain stable. For example, a cluster of multiple robotic arms in a smart factory scenario may remain stable for a long time. Therefore, the stability information associated with the cluster may have a time granularity of hours or even days. In a V2X scenario, the multiple RSU devices or sensor devices serving a certain vehicle UE may change rapidly as the vehicle UE moves. Therefore, the composition or configuration of the cluster may be updated in real time for the vehicle UE by the control device / central network. Accordingly, the stability information associated with the cluster may have a smaller time granularity (e.g., minutes). Optionally, the group communication service characteristics may also include the type of service involved in the communication, such as V2X sensor fusion, remote driving, green wave traffic, seamless switching in home / work scenarios, joint processing / manufacturing, etc. In addition, the group communication service characteristics may also include an indication of whether the control device / central sub-network / group management network needs to form a cluster.
[0199] Additionally or optionally, the one or more new parameters may also include a group communication handover requirement. For service flow handover requirements between multiple UEs within a cluster, the group communication handover requirement may include an indication of whether interruption is permitted. If interruption is permitted, the group communication handover requirement may additionally include an upper limit on the permitted interruption time (e.g., 300ms, 500ms, 2s). If interruption is not permitted, the group communication handover requirement may include an indication of whether redundancy is required for the handover.
[0200] In step 1030, the NEF may send one or more parameters of the cluster associated with the task (along with other parameters defined in the standard protocol) to the UDM. For example, the NEF may send a Nudm_ParameterProvision_Create / Update / Delete request to the UDM.
[0201] Then, through interaction between the UDM and the unified data repository (UDR), operations such as saving, updating, or deleting one or more parameters of the cluster associated with the task can be performed. For example, in step 1040, the UDM can send a Nudr_DM_Query message to the UDR. In step 1050, the UDR can send a Nudr_DM_Update message to the UDM.
[0202] Then, in step 1060, the UDM may send a Nudm_ParameterProvision_Create / Update / Delete response to the NEF. In step 1070, the NEF may send a Nnef_ParameterProvision_Create / Update / Delete response to the AF.
[0203] Figure 11 shows a schematic diagram of a process 1100 according to some embodiments of the present disclosure. At step 1101, the AMF may decide to establish a UE policy association. At step 1102, the AMF may send an Npcf_UEPolicyControl_Create request to the visiting PCF (V-PCF). At step 1103, the V-PCF may send an Npcf_UEPolicyControl_Create request to the home PCF (H-PCF). At step 1104, the H-PCF may send an Npcf_UEPolicyControl_Create response to the V-PCF. At step 1105, the V-PCF may send an Npcf_UEPolicyControl_Create response to the AMF. At step 1106, the H-PCF may send an Npcf_UEPolicyControl_UpdateNotify request to the V-PCF. At step 1107, the V-PCF may send an Npcf_UEPolicyControl_UpdateNotify response to the H-PCF. At step 1108, the AMF and the V-PCF may perform a UE configuration update procedure together. At step 1108, the V-PCF may send an Npcf_UEPolicyControl_Update request to the H-PCF. At step 1109, the H-PCF may send an Npcf_UEPolicyControl_Update response to the V-PCF. It should be understood that process 1100 in FIG11 is merely an example and not a limitation. For example, in an alternative embodiment, both the V-PCF and the H-PCF may not exist, but rather a single PCF may exist.
[0204] Process 1100 describes the acquisition and determination of the actual configuration policy of the UE between the AMF and the PCF in the 5G network based on the core network storage functional unit such as the UDM or UDR. One or more parameters of the cluster associated with the task can be proactively obtained by the PCF from the UDR in 1106. Then, the confirmed group management policy and group communication policy can be sent to the AMF in 1108.
[0205] The present disclosure provides devices, methods, computer-readable storage media, computer program products and apparatuses for clustering. The technology disclosed in the present disclosure is particularly suitable for cluster communications in business scenarios such as V2X, factories, XR, etc. that may involve data networks. Additionally, the technology disclosed in the present disclosure can reduce the energy consumption of service equipment (especially shared service equipment) and improve service efficiency. Additionally, the technology disclosed in the present disclosure can improve the utilization of wireless resources in places with high density of UEs. In addition, by using the technology disclosed in the present disclosure, devices participating in the cluster can have a higher degree of freedom of movement without requiring all devices in the cluster to be connected by wire. In addition, the technology disclosed in the present disclosure allows dynamic resource sharing between devices to obtain improved performance.
[0206] 4. Sample application products
[0207] The technology disclosed herein can be applied to various products.
[0208] For example, the control device / base station mentioned in this disclosure can be implemented as any type of base station, such as an eNB, such as a macro eNB and a small eNB. A small eNB can be an eNB that covers a cell smaller than a macro cell, such as a pico eNB, a micro eNB, and a home (femto) eNB. For another example, it can be implemented as a gNB, such as a macro gNB and a small gNB. A small gNB can be a gNB that covers a cell smaller than a macro cell, such as a pico gNB, a micro gNB, and a home (femto) gNB. Alternatively, the base station can be implemented as any other type of base station, such as a NodeB and a base transceiver station (BTS). A base station can include: a main body (also called a base station device) configured to control wireless communications; and one or more remote radio heads (RRHs) located at a location different from the main body. In addition, the various types of terminals described below can all operate as a base station by temporarily or semi-permanently performing base station functions. For example, the terminal devices mentioned in the present disclosure may be implemented as mobile terminals (such as smart phones, tablet personal computers (PCs), notebook PCs, portable game terminals, portable / dongle-type mobile routers, and digital camera devices) or vehicle-mounted terminals (such as car navigation devices) in some embodiments. The terminal device may also be implemented as a terminal that performs machine-to-machine (M2M) communication (also known as a machine-type communication (MTC) terminal). In addition, the terminal device may be a wireless communication module (such as an integrated circuit module comprising a single chip) installed on each of the above-mentioned terminals.
[0209] Application examples according to the present disclosure will be described below with reference to the accompanying drawings.
[0210] [Example about base stations]
[0211] It should be understood that the term "base station" in the present disclosure has the full breadth of its usual meaning and includes at least a wireless communication station used as part of a wireless communication system or radio system to facilitate communication. Examples of base stations may include, but are not limited to, the following: a base station may be one or both of a base transceiver station (BTS) and a base station controller (BSC) in a GSM system, one or both of a radio network controller (RNC) and a Node B in a WCDMA system, an eNB in an LTE and LTE-Advanced system, or a corresponding network node in a future communication system (such as a gNB, eLTE eNB, etc. that may appear in a 5G communication system). Some of the functions in the base station of the present disclosure may also be implemented as an entity that has a control function for communication in D2D, M2M, and V2V communication scenarios, or as an entity that plays a spectrum coordination role in a cognitive radio communication scenario.
[0212] First example
[0213] FIG12 is a block diagram illustrating a first exemplary configuration of a gNB to which the techniques of this disclosure may be applied. The gNB 2100 includes multiple antennas 2110 and a base station device 2120. The base station device 2120 and each antenna 2110 may be connected to each other via an RF cable. In one implementation, the gNB 2100 (or base station device 2120) herein may correspond to the control-side electronic device described above.
[0214] Each antenna 2110 includes a single or multiple antenna elements (such as multiple antenna elements included in a multiple-input multiple-output (MIMO) antenna) and is used for base station device 2120 to transmit and receive wireless signals. As shown in Figure 12, gNB 2100 may include multiple antennas 2110. For example, multiple antennas 2110 may be compatible with multiple frequency bands used by gNB 2100.
[0215] The base station device 2120 includes a controller 2121 , a memory 2122 , a network interface 2123 , and a wireless communication interface 2125 .
[0216] The controller 2121 may be, for example, a CPU or a DSP, and operates various functions of the higher layers of the base station device 2120. For example, the controller 2121 determines the location information of a target terminal device in at least one terminal device based on the positioning information of at least one terminal device on the terminal side in the wireless communication system acquired by the wireless communication interface 2125 and the specific location configuration information of at least one terminal device. The controller 2121 may have a logical function of performing the following controls: the control may be, for example, radio resource control, radio bearer control, mobility management, access control, and scheduling. The control may be performed in conjunction with a nearby gNB or core network node. The memory 2122 includes RAM and ROM, and stores programs executed by the controller 2121 and various types of control data (such as a terminal list, transmission power data, and scheduling data).
[0217] The network interface 2123 is a communication interface for connecting the base station device 2120 to the core network 2124. The controller 2121 can communicate with the core network node or another gNB via the network interface 2123. In this case, the gNB 2100 and the core network node or other gNB can be connected to each other via a logical interface (such as an S1 interface and an X2 interface). The network interface 2123 can also be a wired communication interface or a wireless communication interface for wireless backhaul. If the network interface 2123 is a wireless communication interface, the network interface 2123 can use a higher frequency band for wireless communication than the frequency band used by the wireless communication interface 2125.
[0218] The wireless communication interface 2125 supports any cellular communication scheme, such as Long Term Evolution (LTE) and LTE-Advanced, and provides wireless connectivity to terminals located in the gNB 2100 cell via the antenna 2110. The wireless communication interface 2125 may typically include, for example, a baseband (BB) processor 2126 and RF circuitry 2127. The BB processor 2126 can perform various signal processing functions, such as encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and performs various signal processing for layers such as Layer 1 (L1), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP). In place of the controller 2121, the BB processor 2126 may perform some or all of the aforementioned logical functions. The BB processor 2126 may be a memory storing communication control programs, or a module including a processor configured to execute programs and associated circuitry. Program updates can modify the functionality of the BB processor 2126. This module may be a card or blade inserted into a slot in the base station device 2120. Alternatively, it may be a chip mounted on the card or blade. Meanwhile, the RF circuit 2127 may include, for example, a mixer, a filter, and an amplifier, and transmits and receives wireless signals via the antenna 2110. Although FIG12 shows an example in which one RF circuit 2127 is connected to one antenna 2110, the present disclosure is not limited to this illustration, and one RF circuit 2127 may be connected to multiple antennas 2110 at the same time.
[0219] As shown in Figure 12 , the wireless communication interface 2125 may include multiple BB processors 2126. For example, multiple BB processors 2126 may be compatible with multiple frequency bands used by the gNB 2100. As shown in Figure 12 , the wireless communication interface 2125 may include multiple RF circuits 2127. For example, multiple RF circuits 2127 may be compatible with multiple antenna elements. While Figure 12 illustrates an example in which the wireless communication interface 2125 includes multiple BB processors 2126 and multiple RF circuits 2127, the wireless communication interface 2125 may also include a single BB processor 2126 or a single RF circuit 2127.
[0220] Second example
[0221] FIG13 is a block diagram illustrating a second exemplary configuration of a gNB to which the techniques of this disclosure can be applied. gNB 2200 includes multiple antennas 2210, RRHs 2220, and base station equipment 2230. RRHs 2220 and each antenna 2210 can be connected to each other via an RF cable. Base station equipment 2230 and RRHs 2220 can be connected to each other via a high-speed line such as an optical fiber cable. In one implementation, gNB 2200 (or base station equipment 2230) herein may correspond to the control-side electronic device described above.
[0222] Each antenna 2210 includes a single or multiple antenna elements (such as multiple antenna elements included in a MIMO antenna) and is used for transmitting and receiving wireless signals by the RRH 2220. As shown in Figure 13, the gNB 2200 may include multiple antennas 2210. For example, the multiple antennas 2210 may be compatible with multiple frequency bands used by the gNB 2200.
[0223] Base station device 2230 includes a controller 2231, a memory 2232, a network interface 2233, a wireless communication interface 2234, and a connection interface 2236. Controller 2231, memory 2232, and network interface 2233 are the same as controller 2121, memory 2122, and network interface 2123 described with reference to FIG.
[0224] The wireless communication interface 2234 supports any cellular communication scheme (such as LTE and LTE-Advanced) and provides wireless communication to terminals located in the sector corresponding to the RRH 2220 via the RRH 2220 and the antenna 2210. The wireless communication interface 2234 may generally include, for example, a BB processor 2235. The BB processor 2235 is identical to the BB processor 2126 described with reference to FIG. 12 , except that the BB processor 2235 is connected to the RF circuit 2222 of the RRH 2220 via the connection interface 2236. As shown in FIG. 13 , the wireless communication interface 2234 may include multiple BB processors 2235. For example, the multiple BB processors 2235 may be compatible with multiple frequency bands used by the gNB 2200. Although FIG. 13 illustrates an example in which the wireless communication interface 2234 includes multiple BB processors 2235, the wireless communication interface 2234 may also include a single BB processor 2235.
[0225] The connection interface 2236 is an interface for connecting the base station device 2230 (wireless communication interface 2234) to the RRH 2220. The connection interface 2236 may also be a communication module for connecting the base station device 2230 (wireless communication interface 2234) to the RRH 2220 for communication in the high-speed line.
[0226] The RRH 2220 includes a connection interface 2223 and a wireless communication interface 2221 .
[0227] The connection interface 2223 is an interface for connecting the RRH 2220 (wireless communication interface 2221) to the base station device 2230. The connection interface 2223 may also be a communication module for communication in the above-mentioned high-speed line.
[0228] The wireless communication interface 2221 transmits and receives wireless signals via the antenna 2210. The wireless communication interface 2221 may generally include, for example, an RF circuit 2222. The RF circuit 2222 may include, for example, a mixer, a filter, and an amplifier, and transmits and receives wireless signals via the antenna 2210. Although FIG13 illustrates an example in which one RF circuit 2222 is connected to one antenna 2210, the present disclosure is not limited to this illustration, and one RF circuit 2222 may be connected to multiple antennas 2210 simultaneously.
[0229] As shown in FIG13 , the wireless communication interface 2221 may include multiple RF circuits 2222. For example, the multiple RF circuits 2222 may support multiple antenna elements. Although FIG13 shows an example in which the wireless communication interface 2221 includes multiple RF circuits 2222, the wireless communication interface 2221 may also include a single RF circuit 2222.
[0230] [Example of User Equipment / Terminal Equipment]
[0231] First example
[0232] 14 is a block diagram illustrating an example of an exemplary configuration of a communication device 2300 (e.g., a smart phone, a contact, etc.) to which the technology of the present disclosure may be applied. The communication device 2300 includes a processor 2301, a memory 2302, a storage device 2303, an external connection interface 2304, a camera 2306, a sensor 2307, a microphone 2308, an input device 2309, a display device 2310, a speaker 2311, a wireless communication interface 2312, one or more antenna switches 2315, one or more antennas 2316, a bus 2317, a battery 2318, and an auxiliary controller 2319. In one implementation, the communication device 2300 (or processor 2301) herein may correspond to the aforementioned transmitting device or terminal-side electronic device.
[0233] The processor 2301 may be, for example, a CPU or a system on a chip (SoC), and controls the functions of the application layer and other layers of the communication device 2300. The memory 2302 includes RAM and ROM, and stores data and programs executed by the processor 2301. The storage device 2303 may include storage media such as semiconductor memories and hard disks. The external connection interface 2304 is an interface for connecting an external device (such as a memory card and a universal serial bus (USB) device) to the communication device 2300.
[0234] The camera 2306 includes an image sensor (such as a charge coupled device (CCD) and a complementary metal oxide semiconductor (CMOS)) and generates a captured image. The sensor 2307 may include a group of sensors such as a measurement sensor, a gyroscope sensor, a geomagnetic sensor, and an acceleration sensor. The microphone 2308 converts the sound input to the communication device 2300 into an audio signal. The input device 2309 includes, for example, a touch sensor, a keypad, a keyboard, a button, or a switch configured to detect a touch on the screen of the display device 2310, and receives an operation or information input from the user. The display device 2310 includes a screen (such as a liquid crystal display (LCD) and an organic light emitting diode (OLED) display) and displays the output image of the communication device 2300. The speaker 2311 converts the audio signal output from the communication device 2300 into sound.
[0235] The wireless communication interface 2312 supports any cellular communication scheme (such as LTE and LTE-Advanced) and performs wireless communication. The wireless communication interface 2312 may generally include, for example, a BB processor 2313 and an RF circuit 2314. The BB processor 2313 may perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and perform various types of signal processing for wireless communication. Meanwhile, the RF circuit 2314 may include, for example, a mixer, a filter, and an amplifier, and transmit and receive wireless signals via an antenna 2316. The wireless communication interface 2312 may be a chip module on which the BB processor 2313 and the RF circuit 2314 are integrated. As shown in FIG14 , the wireless communication interface 2312 may include multiple BB processors 2313 and multiple RF circuits 2314. Although FIG14 shows an example in which the wireless communication interface 2312 includes multiple BB processors 2313 and multiple RF circuits 2314, the wireless communication interface 2312 may also include a single BB processor 2313 or a single RF circuit 2314.
[0236] In addition, in addition to the cellular communication scheme, the wireless communication interface 2312 can support other types of wireless communication schemes, such as a short-range wireless communication scheme, a near-field communication scheme, and a wireless local area network (LAN) scheme. In this case, the wireless communication interface 2312 can include a BB processor 2313 and an RF circuit 2314 for each wireless communication scheme.
[0237] Each of the antenna switches 2315 switches the connection destination of the antenna 2316 between a plurality of circuits (eg, circuits for different wireless communication schemes) included in the wireless communication interface 2312 .
[0238] Each of the antennas 2316 includes a single or multiple antenna elements (such as multiple antenna elements included in a MIMO antenna) and is used for transmitting and receiving wireless signals via the wireless communication interface 2312. As shown in FIG14, the communication device 2300 may include multiple antennas 2316. Although FIG14 shows an example in which the communication device 2300 includes multiple antennas 2316, the communication device 2300 may also include a single antenna 2316.
[0239] In addition, the communication device 2300 may include an antenna 2316 for each wireless communication scheme. In this case, the antenna switch 2315 may be omitted from the configuration of the communication device 2300.
[0240] The bus 2317 connects the processor 2301, the memory 2302, the storage device 2303, the external connection interface 2304, the camera 2306, the sensor 2307, the microphone 2308, the input device 2309, the display device 2310, the speaker 2311, the wireless communication interface 2312, and the auxiliary controller 2319. The battery 2318 supplies power to the various blocks of the communication device 2300 shown in FIG14 via a feeder line, which is partially shown as a dotted line in the figure. The auxiliary controller 2319 operates the minimum necessary functions of the communication device 2300, for example, in sleep mode.
[0241] Second example
[0242] Figure 15 is a block diagram showing an example of an exemplary configuration of a car navigation device 2400 to which the technology of the present disclosure can be applied. The car navigation device 2400 includes a processor 2401, a memory 2402, a global positioning system (GPS) module 2404, a sensor 2405, a data interface 2406, a content player 2407, a storage medium interface 2408, an input device 2409, a display device 2510, a speaker 2411, a wireless communication interface 2413, one or more antenna switches 2416, one or more antennas 2417, and a battery 2418. In one implementation, the car navigation device 2400 (or processor 2401) herein may correspond to a transmitting device or a terminal-side electronic device.
[0243] The processor 2401 may be, for example, a CPU or an SoC, and controls a navigation function and other functions of the car navigation apparatus 2400. The memory 2402 includes a RAM and a ROM, and stores data and programs executed by the processor 2401.
[0244] The GPS module 2404 uses GPS signals received from GPS satellites to measure the position (such as latitude, longitude, and altitude) of the car navigation device 2400. The sensor 2405 may include a group of sensors such as a gyroscope sensor, a geomagnetic sensor, and an air pressure sensor. The data interface 2406 is connected to, for example, the vehicle network 2421 via a terminal not shown, and acquires data generated by the vehicle (such as vehicle speed data).
[0245] The content player 2407 reproduces content stored in a storage medium (such as a CD or DVD) inserted into the storage medium interface 2408. The input device 2409 includes, for example, a touch sensor, button, or switch configured to detect a touch on the screen of the display device 2510, and receives an operation or information input from the user. The display device 2510 includes a screen such as an LCD or OLED display and displays an image of a navigation function or reproduced content. The speaker 2411 outputs the sound of the navigation function or the reproduced content.
[0246] The wireless communication interface 2413 supports any cellular communication scheme (such as LTE and LTE-Advanced) and performs wireless communication. The wireless communication interface 2413 may generally include, for example, a BB processor 2414 and an RF circuit 2415. The BB processor 2414 may perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and perform various types of signal processing for wireless communication. Meanwhile, the RF circuit 2415 may include, for example, a mixer, a filter, and an amplifier, and transmit and receive wireless signals via an antenna 2417. The wireless communication interface 2413 may also be a chip module on which the BB processor 2414 and the RF circuit 2415 are integrated. As shown in FIG15 , the wireless communication interface 2413 may include multiple BB processors 2414 and multiple RF circuits 2415. Although FIG15 shows an example in which the wireless communication interface 2413 includes multiple BB processors 2414 and multiple RF circuits 2415, the wireless communication interface 2413 may also include a single BB processor 2414 or a single RF circuit 2415.
[0247] In addition, in addition to the cellular communication scheme, the wireless communication interface 2413 can support other types of wireless communication schemes, such as short-range wireless communication schemes, near field communication schemes, and wireless LAN schemes. In this case, for each wireless communication scheme, the wireless communication interface 2413 can include a BB processor 2414 and an RF circuit 2415.
[0248] Each of the antenna switches 2416 switches the connection destination of the antenna 2417 between a plurality of circuits included in the wireless communication interface 2413 , such as circuits for different wireless communication schemes.
[0249] Each of the antennas 2417 includes a single or multiple antenna elements (such as multiple antenna elements included in a MIMO antenna) and is used for transmitting and receiving wireless signals with the wireless communication interface 2413. As shown in Figure 15, the car navigation device 2400 may include multiple antennas 2417. Although Figure 15 shows an example in which the car navigation device 2400 includes multiple antennas 2417, the car navigation device 2400 may also include a single antenna 2417.
[0250] In addition, the car navigation device 2400 may include an antenna 2417 for each wireless communication scheme. In this case, the antenna switch 2416 may be omitted from the configuration of the car navigation device 2400.
[0251] The battery 2418 supplies power to the respective blocks of the car navigation device 2400 shown in Fig. 15 via a feeder line, which is partially shown as a dotted line in the figure. The battery 2418 accumulates the power supplied from the vehicle.
[0252] The technology of the present disclosure can also be implemented as an in-vehicle system (or vehicle) 2420 including a car navigation device 2400, an in-vehicle network 2421, and one or more blocks of a vehicle module 2422. The vehicle module 2422 generates vehicle data (such as vehicle speed, engine speed, and fault information) and outputs the generated data to the in-vehicle network 2421.
[0253] The exemplary embodiments of the present disclosure are described above with reference to the accompanying drawings, but the present disclosure is certainly not limited to the above examples. Those skilled in the art may obtain various changes and modifications within the scope of the appended claims, and it should be understood that these changes and modifications will naturally fall within the technical scope of the present disclosure.
[0254] It should be understood that the machine-executable instructions in the machine-readable storage medium or program product according to the embodiments of the present disclosure can be configured to perform operations corresponding to the above-mentioned device and method embodiments. When referring to the above-mentioned device and method embodiments, the embodiments of the machine-readable storage medium or program product are clear to those skilled in the art and are therefore not described again. Machine-readable storage media and program products for carrying or including the above-mentioned machine-executable instructions also fall within the scope of the present disclosure. Such storage media may include, but are not limited to, floppy disks, optical disks, magneto-optical disks, memory cards, memory sticks, and the like.
[0255] In addition, it should be understood that the above series of processes and devices can also be implemented by software and / or firmware. In the case of implementation by software and / or firmware, the storage medium of the relevant device stores the corresponding program constituting the corresponding software, and when the program is executed, various functions can be performed.
[0256] For example, a plurality of functions included in one unit in the above embodiments may be implemented by separate devices. Alternatively, a plurality of functions implemented by a plurality of units in the above embodiments may be implemented by separate devices, respectively. In addition, one of the above functions may be implemented by a plurality of units. Needless to say, such a configuration is included in the technical scope of the present disclosure.
[0257] In this specification, the steps described in the flowchart include not only processing that is performed in order in time series, but also processing that is performed in parallel or individually rather than necessarily in time series. In addition, even in the steps processed in time series, it goes without saying that the order can be appropriately changed.
[0258] 5. Example Embodiments
[0259] By way of example and not limitation, the present disclosure may include the following embodiments.
[0260] 1. An electronic device, comprising: at least one processing unit; and at least one storage unit, the at least one storage unit comprising program instructions, wherein the at least one storage unit and the program instructions are configured to cause the electronic device to perform the following operations through the at least one processing unit: receive registration information from each of one or more service devices, the registration information comprising service capability information associated with services that the service device can provide; receive a service request from a requesting device, the service request being associated with a specific service requested by the requesting device; select a specific service device from the one or more service devices based on a match between the service capability information and the service request; and send configuration information associated with the specific service to the specific service device.
[0261] 2. The electronic device as described in Example 1, wherein the service capability information includes at least one of the following: supported service types; supported service parameter ranges; communication capacity requirements corresponding to each unit of service capability; or mobility information of the service device.
[0262] 3. The electronic device as described in embodiment 2, wherein the service request includes at least one of the following: subscription information of the requesting device; service type requirement; service parameter requirement; or mobility information of the requesting device.
[0263] 4. An electronic device as described in Example 3, wherein the matching includes at least one of the following: determining that the specific service device matches the subscription information; determining that the supported service type matches the service type requirement; determining that the supported service parameter range matches the service parameter requirement; or determining that the specific service device and the requesting device satisfy a predetermined spatial relationship.
[0264] 5. The electronic device according to embodiment 1, wherein the configuration information specifies: the specific service device to be awakened; the function or service to be activated for the specific service device; or the set service parameter value for the specific service device.
[0265] 6. The electronic device of embodiment 1, wherein the configuration information specifies that the specific service device and the requesting device form a specific cluster.
[0266] 7. An electronic device as described in Example 6, wherein the specific cluster includes multiple service devices, the configuration information specifies a communication configuration associated with the specific cluster, and the communication configuration includes at least one of the following: a cluster identifier of the specific cluster; an interface type used for communication between devices in the specific cluster; communication resources allocated to the specific cluster; a key used for communication between devices in the specific cluster; or a multicast address or L2 identifier for the specific cluster.
[0267] 8. The electronic device of embodiment 1, wherein the operation further comprises: sending an indication to the requesting device that the specific service is supported.
[0268] 9. The electronic device according to embodiment 1, wherein the specific service is associated with at least one of the following: a sensing task, an industrial production task, a device movement task, and a media presentation task.
[0269] 10. The electronic device according to embodiment 1, wherein the one or more service devices include at least one of the following: a sensor device, an industrial production device, an in-vehicle device, an aircraft device, a multimedia device, or an access point.
[0270] 11. An electronic device, comprising: at least one processing unit; and at least one storage unit, the at least one storage unit comprising program instructions, wherein the at least one storage unit and the program instructions are configured to enable the electronic device to perform the following operations through the at least one processing unit: send registration information to a control device, the registration information comprising service capability information associated with services that the electronic device can provide; receive configuration information associated with a specific service from the control device, wherein the configuration information specifies that the electronic device forms a specific cluster with a requesting device requesting the specific service; and execute the specific service based at least on the configuration information.
[0271] 12. An electronic device as described in Example 11, wherein the service capability information includes at least one of the following: supported service types; supported service parameter ranges; communication capacity requirements corresponding to each unit of service capability; or mobility information of the electronic device.
[0272] 13. The electronic device according to embodiment 11, wherein the service capability information of the electronic device matches the specific service requested by the requesting device.
[0273] 14. The electronic device according to embodiment 11, wherein the configuration information further specifies: the electronic device being awakened; the function or service being activated of the electronic device; or the set service parameter value of the electronic device.
[0274] 15. An electronic device as described in Example 11, wherein the configuration information specifies a communication configuration associated with the specific cluster, and the communication configuration includes at least one of the following: a cluster identifier of the specific cluster; an interface type used for communication between devices in the specific cluster; communication resources allocated to the specific cluster; a key used for communication between devices in the specific cluster; or a multicast address or L2 identifier for the specific cluster.
[0275] 16. An electronic device as described in Example 11, wherein the specific service is associated with at least one of the following: a sensing task, an industrial production task, a device movement task, a media presentation task; and the electronic device includes at least one of the following: a sensor device, an industrial production device, a vehicle-mounted device, an aircraft device, a multimedia device, or an access point.
[0276] 17. An electronic device, comprising: at least one processing unit; and at least one storage unit, the at least one storage unit comprising program instructions, wherein the at least one storage unit and the program instructions are configured to enable the electronic device to perform the following operations through the at least one processing unit: receive a group session request from a specific cluster comprising one or more devices, the group session request comprising at least task information, the task information being associated with one or more tasks to be performed by the one or more devices; and send a group communication policy to the specific cluster, the group communication policy being based at least in part on the task information.
[0277] 18. An electronic device as described in Example 17, wherein the task information includes: a task list specifying the one or more tasks; a communication time requirement specifying timing information for completing one or more transmissions associated with the one or more tasks; and / or a communication service quality QoS associated with the one or more transmissions.
[0278] 19. An electronic device as described in Example 18, wherein the group communication strategy includes a communication plan for the specific cluster, and the communication plan includes at least: time domain communication scheduling of the one or more transmissions; and / or communication path configuration of the one or more transmissions.
[0279] 20. An electronic device as described in Example 19, wherein the communication path configuration includes: a relay configuration, which specifies a specific device in the specific cluster as a relay device; and a transmission configuration, which specifies that a first data transmission is transmitted through the relay device and a second data transmission is not transmitted through the relay device, wherein the first data transmission has a higher priority than the second data transmission.
[0280] 21. The electronic device of embodiment 20, wherein the operation further comprises: receiving communication capability information associated with the specific device, the communication capability information comprising at least the communication capability of at least one wired connection associated with the first data transmission.
[0281] 22. An electronic device as described in Example 21, wherein the first data transmission is transmitted to the external device of the specific cluster through the PC5 interface of the specific device and the at least one wired connection, and the second data transmission is transmitted to the external device of the specific cluster through the Uu interface.
[0282] 23. The electronic device of embodiment 19, wherein the particular cluster is a first cluster, the group communication policy is a first group communication policy for the first cluster, and wherein the operation further comprises optimizing the first group communication policy based at least in part on a second group communication policy for a second cluster.
[0283] 24. The electronic device as described in Example 18, wherein the QoS is associated with at least one of communication priority, bandwidth, latency, packet loss rate, and redundancy.
[0284] 25. An electronic device as described in Example 17, wherein the group session request also includes identification information associated with the specific cluster, and the identification information includes at least one of the following items: a cluster identifier of the specific cluster; a device identifier of at least one device in the specific cluster; and authentication information associated with the specific cluster.
[0285] 26. The electronic device of embodiment 17, wherein the group session request comprises: a group session establishment request for establishing a session associated with the specific cluster; or a group session update request for modifying a current group session associated with the specific cluster.
[0286] 27. The electronic device as described in Example 18, wherein the one or more tasks include at least one of the following: a sensing task, an industrial production task, a device movement task, and a media presentation task.
[0287] 28. The electronic device of embodiment 17, wherein the operation further comprises: sending stability information to the specific cluster, the stability information indicating a length of time that the specific cluster can remain stable.
[0288] 29. An electronic device, comprising: at least one processing unit; and at least one storage unit, the at least one storage unit comprising program instructions, wherein the at least one storage unit and the program instructions are configured to enable the electronic device to perform the following operations through the at least one processing unit: send a group session request to a control device, the group session request comprising at least task information, the task information being associated with one or more tasks to be performed by the electronic device; receive a group communication strategy associated with a specific cluster from the control device, the group communication strategy being based at least in part on the task information; and perform the one or more tasks based on the group communication strategy.
[0289] 30. An electronic device as described in Example 29, wherein the task information includes: a task list specifying the one or more tasks; a communication time requirement specifying timing information for the electronic device to complete one or more transmissions associated with the one or more tasks; and / or a communication service quality QoS associated with the one or more transmissions.
[0290] 31. An electronic device as described in Example 29, wherein the group communication strategy includes a communication plan for the specific cluster, and the communication plan includes: time domain communication scheduling of the one or more transmissions; and / or communication path configuration of the one or more transmissions.
[0291] 32. An electronic device as described in Example 31, wherein the communication path configuration includes: a relay configuration, which specifies a specific device in the specific cluster as a relay device; and a transmission configuration, which specifies that a first data transmission is transmitted through the relay device and a second data transmission is not transmitted through the relay device, wherein the first data transmission has a higher priority than the second data transmission.
[0292] 33. An electronic device as described in Example 32, wherein the electronic device is the specific device, and the operation further includes: sending communication capability information associated with the electronic device to the control device, the communication capability information at least including the communication capability of at least one wired connection associated with the first data transmission.
[0293] 34. The electronic device of embodiment 30, wherein the first data transmission is transmitted to the external device of the specific cluster via the PC5 interface of the electronic device and the at least one wired connection.
[0294] 35. An electronic device as described in Example 30, wherein the QoS is associated with at least one of communication priority, bandwidth, latency, packet loss rate, and redundancy.
[0295] 36. The electronic device of embodiment 29, wherein the one or more tasks include at least one of the following: a sensing task, an industrial production task, a device movement task, and a media presentation task.
[0296] 37. A method performed by an electronic device, comprising the following operations: receiving registration information from each service device in one or more service devices, the registration information including service capability information associated with the service that the service device can provide; receiving a service request from a requesting device, the service request associated with a specific service requested by the requesting device; selecting a specific service device from the one or more service devices based on a match between the service capability information and the service request; and sending configuration information associated with the specific service to the specific service device.
[0297] 38. A method performed by an electronic device, comprising the following operations: sending registration information to a control device, the registration information including service capability information associated with services that the electronic device can provide; receiving configuration information associated with a specific service from the control device, wherein the configuration information specifies that the electronic device forms a specific cluster with a requesting device that requests the specific service; and executing the specific service based at least on the configuration information.
[0298] 39. A method performed by an electronic device, comprising the following operations: receiving a group session request from a specific cluster including one or more devices, the group session request including at least task information, the task information being associated with one or more tasks to be performed by the one or more devices; and sending a group communication policy to the specific cluster, the group communication policy being based at least in part on the task information.
[0299] 40. A method performed by an electronic device, comprising the following operations: sending a group session request to a control device, the group session request including at least task information, the task information being associated with one or more tasks to be performed by the electronic device; receiving a group communication policy associated with a specific cluster from the control device, the group communication policy being based at least in part on the task information; and performing the one or more tasks based on the group communication policy.
[0300] 41. A computer-readable storage medium storing one or more instructions, which, when executed by one or more processing circuits of an electronic device, cause the electronic device to perform the method of any one of embodiments 37-40.
[0301] 42. A computer program product comprising a computer program, which, when executed by a processor, performs the method of any one of embodiments 37-40.
[0302] 43. An apparatus comprising means for performing the method of any one of embodiments 37-40.
Claims
1. An electronic device, comprising: at least one processing unit; and At least one storage unit, the at least one storage unit including program instructions, wherein the at least one storage unit and the program instructions are configured to cause the electronic device to perform the following operations through the at least one processing unit: receiving registration information from each of the one or more service devices, the registration information including service capability information associated with a service that the service device can provide; receiving a service request from a requesting device, the service request being associated with a specific service requested by the requesting device; selecting a specific service device from the one or more service devices based on a match between the service capability information and the service request; as well as Configuration information associated with the specific service is sent to the specific service device.
2. The electronic device according to claim 1, wherein The service capability information includes at least one of the following: Types of services supported; The range of supported service parameters; Communication capacity requirements per unit of service capability; or Mobility information of the serving device.
3. The electronic device according to claim 2, wherein: The service request includes at least one of the following: Subscription information of the requesting device; Service type requirements; Service parameter requirements; or The requesting device's mobility information.
4. The electronic device according to claim 3, wherein: The matching includes at least one of the following: Determining that the specific service device matches the subscription information; Determining that the supported service type matches the service type requirement; Determining that the supported service parameter range matches the service parameter requirement; or It is determined that the specific service device and the requesting device satisfy a predetermined spatial relationship.
5. The electronic device according to claim 1, wherein The configuration information specifies: The specific service device is awakened; The activated function or service of the specific service device; or The set service parameter value of the specific service device.
6. The electronic device according to claim 1, wherein The configuration information specifies that the specific service device and the requesting device form a specific cluster.
7. The electronic device according to claim 6, wherein: The specific cluster includes a plurality of service devices, and the configuration information specifies a communication configuration associated with the specific cluster, wherein the communication configuration includes at least one of the following: a cluster identifier of the particular cluster; the type of interface used for communication between devices in the particular cluster; communication resources allocated to the specific cluster; a key for communication between devices in the particular cluster; or The multicast address or L2 identifier for the specific cluster.
8. The electronic device according to claim 1, wherein The operations also include sending an indication to the requesting device that the particular service is supported.
9. The electronic device according to claim 1, wherein The specific service is associated with at least one of the following: a sensing task, an industrial production task, a device movement task, and a media presentation task. 10 . The electronic device of claim 1 , wherein the one or more service devices include at least one of the following: a sensor device, an industrial production device, a vehicle-mounted device, an aircraft device, a multimedia device, or an access point.
11. An electronic device, comprising: at least one processing unit; and At least one storage unit, the at least one storage unit including program instructions, wherein the at least one storage unit and the program instructions are configured to cause the electronic device to perform the following operations through the at least one processing unit: Sending registration information to a control device, the registration information including service capability information associated with services that the electronic device can provide; receiving configuration information associated with a specific service from the control device, wherein the configuration information specifies that the electronic device forms a specific cluster with a requesting device requesting the specific service; as well as Based at least on the configuration information, the specific service is performed.
12. The electronic device according to claim 11, wherein The service capability information includes at least one of the following: Types of services supported; The range of supported service parameters; Communication capacity requirements per unit of service capability; or Mobility information of the electronic device.
13. The electronic device according to claim 11, wherein The service capability information of the electronic device matches the specific service requested by the requesting device.
14. The electronic device according to claim 11, wherein The configuration information also specifies: The electronic device is awakened; The activated function or service of the electronic device; or The set service parameter value of the electronic device.
15. The electronic device according to claim 11, wherein The configuration information specifies a communication configuration associated with the particular cluster, the communication configuration including at least one of the following: a cluster identifier of the particular cluster; the type of interface used for communication between devices in the particular cluster; communication resources allocated to the specific cluster; a key for communication between devices in the particular cluster; or The multicast address or L2 identifier for the specific cluster.
16. The electronic device according to claim 11, wherein The specific service is associated with at least one of the following: a sensing task, an industrial production task, a device movement task, and a media presentation task; and The electronic device includes at least one of the following: a sensor device, an industrial production device, a vehicle-mounted device, an aircraft device, a multimedia device, or an access point.
17. An electronic device, comprising: at least one processing unit; and At least one storage unit, the at least one storage unit including program instructions, wherein the at least one storage unit and the program instructions are configured to cause the electronic device to perform the following operations through the at least one processing unit: receiving a group session request from a particular cluster comprising one or more devices, the group session request comprising at least task information associated with one or more tasks to be performed by the one or more devices; as well as A group communication policy is sent to the particular cluster, the group communication policy being based at least in part on the task information.
18. The electronic device according to claim 17, wherein: The task information includes: a task list specifying the one or more tasks; communication time requirements specifying timing information for completing one or more transmissions associated with the one or more tasks; and / or A communication quality of service (QoS) associated with the one or more transmissions.
19. The electronic device according to claim 18, wherein The group communication strategy includes a communication plan for the specific cluster, and the communication plan includes at least: a time domain communication schedule for the one or more transmissions; and / or A communication path configuration for the one or more transmissions.
20. The electronic device according to claim 19, wherein The communication path configuration includes: a relay configuration that designates a specific device in the specific cluster as a relay device; and A transmission configuration specifies that a first data transmission is transmitted through the relay device and a second data transmission is not transmitted through the relay device, wherein the first data transmission has a higher priority than the second data transmission.
21. The electronic device according to claim 20, wherein: The operations further include: Communication capability information associated with the specific device is received, the communication capability information including at least a communication capability of at least one wired connection associated with a first data transmission.
22. The electronic device according to claim 21, wherein The first data transmission is transmitted to the external device of the specific cluster via the PC5 interface of the specific device and the at least one wired connection, and the second data transmission is transmitted to the external device of the specific cluster via the Uu interface.
23. The electronic device according to claim 19, wherein The particular cluster is a first cluster, the group communication policies are a first group communication policies for the first cluster, wherein the operations further comprise optimizing the first group communication policies based at least in part on a second group communication policies for a second cluster.
24. The electronic device according to claim 18, wherein The QoS is associated with at least one of communication priority, bandwidth, delay, packet loss rate, and redundancy.
25. The electronic device according to claim 17, wherein The group session request further includes identification information associated with the specific cluster, where the identification information includes at least one of the following: a cluster identifier of the particular cluster; a device identifier of at least one device in the particular cluster; Authentication information associated with the particular cluster.
26. The electronic device according to claim 17, wherein The group session request includes: A group session establishment request for establishing a session associated with the specific cluster; or The group session update request is used to modify the current group session associated with the specific cluster.
27. The electronic device according to claim 18, wherein The one or more tasks include at least one of the following: a sensing task, an industrial production task, a device movement task, and a media presentation task.
28. The electronic device according to claim 17, wherein The operations further include: Stability information is sent to the specific cluster, where the stability information indicates a length of time that the specific cluster can remain stable.
29. An electronic device, comprising: at least one processing unit; and At least one storage unit, the at least one storage unit including program instructions, wherein the at least one storage unit and the program instructions are configured to cause the electronic device to perform the following operations through the at least one processing unit: sending a group session request to a control device, the group session request including at least task information associated with one or more tasks to be performed by the electronic device; receiving, from the control device, a group communication policy associated with a particular cluster, the group communication policy being based at least in part on the task information; as well as Based on the group communication policy, the one or more tasks are performed.
30. The electronic device according to claim 29, wherein The task information includes: a task list specifying the one or more tasks; Communication time requirements specifying timing information for the electronic device to complete one or more transmissions associated with the one or more tasks; and / or A communication quality of service (QoS) associated with the one or more transmissions.
31. The electronic device according to claim 29, wherein The group communication strategy includes a communication plan for the specific cluster, the communication plan including: a time domain communication schedule for the one or more transmissions; and / or A communication path configuration for the one or more transmissions.
32. The electronic device according to claim 31, wherein The communication path configuration includes: a relay configuration that designates a specific device in the specific cluster as a relay device; and A transmission configuration specifies that a first data transmission is transmitted through the relay device and a second data transmission is not transmitted through the relay device, wherein the first data transmission has a higher priority than the second data transmission.
33. The electronic device according to claim 32, wherein: The electronic device is the specific device, and the operation further includes: sending communication capability information associated with the electronic device to the control device, the communication capability information including at least a communication capability of at least one wired connection associated with the first data transmission.
34. The electronic device according to claim 30, wherein: The first data transmission is transmitted to the external device of the specific cluster through the PC5 interface of the electronic device and the at least one wired connection.
35. The electronic device according to claim 30, wherein The QoS is associated with at least one of communication priority, bandwidth, delay, packet loss rate, and redundancy.
36. The electronic device according to claim 29, wherein The one or more tasks include at least one of the following: a sensing task, an industrial production task, a device movement task, and a media presentation task.
37. A method performed by an electronic device, comprising the following operations: receiving registration information from each of the one or more service devices, the registration information including service capability information associated with a service that the service device can provide; receiving a service request from a requesting device, the service request being associated with a specific service requested by the requesting device; selecting a specific service device from the one or more service devices based on a match between the service capability information and the service request; and Configuration information associated with the specific service is sent to the specific service device.
38. A method performed by an electronic device, comprising the following operations: Sending registration information to the control device, the registration information including service capability information associated with services that the electronic device can provide; receiving configuration information associated with a specific service from the control device, wherein the configuration information specifies that the electronic device forms a specific cluster with a requesting device requesting the specific service; and Based at least on the configuration information, the specific service is performed.
39. A method performed by an electronic device, comprising the following operations: receiving a group session request from a particular cluster comprising one or more devices, the group session request comprising at least task information associated with one or more tasks to be performed by the one or more devices; and A group communication policy is sent to the particular cluster, the group communication policy being based at least in part on the task information.
40. A method performed by an electronic device, comprising the following operations: sending a group session request to a control device, the group session request including at least task information associated with one or more tasks to be performed by the electronic device; receiving, from the control device, a group communication policy associated with a particular cluster, the group communication policy being based at least in part on the task information; as well as Based on the group communication policy, the one or more tasks are performed.
41. A computer-readable storage medium storing one or more instructions, which, when executed by one or more processing circuits of an electronic device, cause the electronic device to perform the method according to any one of claims 37 to 40.
42. A computer program product comprising a computer program which, when executed by a processor, performs the method of any one of claims 37 to 40.
43. An apparatus comprising means for performing the method of any one of claims 37-40.
Citation Information
Patent Citations
Service co-processing method, device and equipment for Internet of Things equipment cluster
CN114006925A
Device scheduling method, server, device cluster, collaboration system and storage medium
CN117376111A
Method of supporting a collaborative session
EP2043330A1
Service-based internet protocol multimedia subsystem (IMS) architecture
WO2023192292A1