Electronic device and method for wireless communication, and computer readable storage medium

Abstract

The present disclosure provides an electronic device and method for wireless communication, and a computer readable storage medium, the electronic device comprising: a processing circuit configured to send service information of a service that a first terminal device can provide to one or more second terminal devices, the service information comprising service type information and service characteristic information; and providing a data flow of the corresponding service to at least one terminal device in the one or more second terminal devices based on the service information.

Description

Electronic device and method for wireless communication, and computer-readable storage medium

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on June 10, 2022, with application number 202210654415.5 and invention name “Electronic device and method for wireless communication, computer-readable storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] Embodiments of the present disclosure generally relate to the field of wireless communications, and more particularly, to enhancement of short-range communication networks. More particularly, they relate to electronic devices and methods, and computer-readable storage media for wireless communications. Background Art

[0003] The enhancements to Proximity Services (ProSe)-based communications in 3GPP Rel-17 (TS 23.304) are currently limited to UE-to-Network Relay and do not involve UE-to-UE Relay, and are all PC5 connections based on unicast links.

[0004] In scenarios such as the Internet of Vehicles (V2X), intelligent robots, and drones, PC5-based broadcast and multicast have become the main communication methods to support business, such as message push for safety and efficiency applications, especially applications related to vehicle-road collaboration. However, the scope of broadcast and multicast communication services that a single terminal device can provide is limited, and it is necessary to enhance communication modes such as broadcast and multicast.

[0005] The current broadcast is a mapping relationship between a single service and a destination Layer-2 ID. The data packet sent to the UE broadcast carries the destination Layer-2 ID and is broadcast. There is no forwarding mechanism, nor is there any satisfaction of customized requirements under this service, nor the application of HARQ and beam.

[0006] Multicast can be divided into two types: broadcast-like multicast, which uses broadcast format but carries multicast services, and multicast with upper-layer group management. Upper-layer group management can deliver information such as the number of group members, group ID, and communication range to the non-access stratum (NAS), facilitating additional functions such as group member management, generation of destination Layer-2 IDs for specific group communications, and HARQ feedback at the NAS layer.

[0007] Summary of the Invention

[0008] A brief overview of the present disclosure is provided below to provide a basic understanding of certain aspects of the present disclosure. It should be understood that this overview is not an exhaustive overview of the present disclosure. It is not intended to identify key or important aspects of the present disclosure, nor is it intended to limit the scope of the present disclosure. Its purpose is simply to present certain concepts in a simplified form as a prelude to the more detailed description discussed later.

[0009] According to one aspect of the present application, an electronic device for wireless communication is provided, comprising: a processing circuit configured to: send service information of a service that can be provided by a first terminal device to one or more second terminal devices, wherein the service information includes service type information and service characteristic information; and provide a data stream of the corresponding service to at least one terminal device among the one or more second terminal devices based on the service information.

[0010] According to another aspect of the present application, a method for wireless communication is provided, comprising: sending service information of a service that can be provided by a first terminal device to one or more second terminal devices, wherein the service information includes service type information and service characteristic information; and providing a data stream of the corresponding service to at least one terminal device among the one or more second terminal devices based on the service information.

[0011] The electronic device and method according to the above aspects of the present application can provide business data with finer granularity to better meet customized needs.

[0012] According to one aspect of the present application, an electronic device for wireless communication is provided, comprising: a processing circuit configured to: receive service information of a service that can be provided by the second terminal device from a second terminal device, wherein the service information includes service type information and service characteristic information; and include the service information in provision information of a data service that can be provided by the first terminal device and multicast it to one or more third terminal devices.

[0013] According to another aspect of the present application, a method for wireless communication is provided, comprising: receiving service information of a service that can be provided by the second terminal device from a second terminal device, wherein the service information includes service type information and service characteristic information; and including the service information in provision information of a data service that can be provided by the first terminal device and multicasting it to one or more third terminal devices.

[0014] The electronic device and method according to the above aspects of the present application can realize the relay transmission of business data with finer granularity to better adapt to customized needs and enhance the coverage of the multicast communication mode.

[0015] According to one aspect of the present application, an electronic device for wireless communication is provided, comprising: a processing circuit configured to: receive provision information of a data service that can be provided by the second terminal device and sent by the second terminal device via multicast, the provision information including service information of the services that can be provided, the service information including service type information and service characteristic information; and send a service trigger request of the first terminal device to the second terminal device, the service trigger request including demand information of the service characteristics of the first terminal device.

[0016] According to another aspect of the present application, a method for wireless communication is provided, including: receiving provision information of a data service that can be provided by the second terminal device sent by the second terminal device via multicast from the second terminal device, the provision information including service information of the services that can be provided, and the service information including service type information and service characteristic information; and sending a service trigger request of the first terminal device to the second terminal device, the service trigger request including demand information of the service characteristics of the first terminal device.

[0017] The electronic device and method according to the above aspects of the present application can obtain service data with finer granularity to better adapt to customized needs and enhance the coverage of the multicast communication mode.

[0018] According to one aspect of the present application, an electronic device for wireless communication is provided, comprising: a processing circuit configured to: perform beam matching for one or more second terminal devices to select a beam to be used for communication; and perform communication between a first terminal device and one or more second terminal devices using the selected beam.

[0019] According to another aspect of the present application, a method for wireless communication is provided, comprising: performing beam matching for one or more second terminal devices to select a beam to be used for communication; and performing communication between a first terminal device and one or more second terminal devices using the selected beam.

[0020] The electronic device and method according to the above aspects of the present application implement directional data transmission and improve communication efficiency by performing beam matching.

[0021] According to other aspects of the present disclosure, a computer program code and a computer program product for implementing the above-mentioned method for wireless communication, as well as a computer-readable storage medium having the computer program code for implementing the above-mentioned method for wireless communication recorded thereon, are also provided.

[0022] The above and other advantages of the present disclosure will become more apparent through the following detailed description of the preferred embodiments of the present disclosure in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to further illustrate the above and other advantages and features of the present disclosure, the following is a further detailed description of the specific embodiments of the present disclosure in conjunction with the accompanying drawings. The drawings, together with the detailed description below, are included in this specification and form a part of this specification. Elements with the same function and structure are represented by the same reference numerals. It should be understood that these drawings only depict typical examples of the present disclosure and should not be regarded as limiting the scope of the present disclosure. In the drawings:

[0024] FIG1 shows a functional module block diagram of an electronic device for wireless communication according to an embodiment of the present application;

[0025] FIG2 shows a functional module block diagram of an electronic device for wireless communication according to another embodiment of the present application;

[0026] Figure 3 shows an example of phase matching in a connected vehicle scenario;

[0027] FIG4 shows an example of the related information flow between the serving UE, the relay UE and the remote UE;

[0028] FIG5 shows an example of an information flow of a fourth terminal device joining an existing network;

[0029] FIG6 shows an example of matching of a new relay UE joining the network in a vehicle networking scenario;

[0030] FIG7 shows an example of matching of a new service UE joining the network in a vehicle networking scenario;

[0031] FIG8 shows a schematic example of beam direction limitation;

[0032] FIG9 shows a schematic example of the interaction of keep-alive signaling;

[0033] FIG10 shows another schematic example of the interaction of keep-alive signaling;

[0034] FIG11 shows a functional module block diagram of an electronic device for wireless communication according to another embodiment of the present application;

[0035] FIG12 shows a functional module block diagram of an electronic device for wireless communication according to another embodiment of the present application;

[0036] FIG13 shows an example of the beam matching process;

[0037] FIG14 shows another example of the beam matching process;

[0038] FIG15 shows another example of the beam matching process;

[0039] FIG16 shows a flowchart of a method for wireless communication according to an embodiment of the present application;

[0040] FIG17 shows a flowchart of a method for wireless communication according to another embodiment of the present application;

[0041] FIG18 shows a flowchart of a method for wireless communication according to another embodiment of the present application;

[0042] FIG19 shows a flowchart of a method for wireless communication according to another embodiment of the present application;

[0043] FIG20 is a block diagram showing an example of a schematic configuration of a smartphone to which the technology of the present disclosure can be applied;

[0044] FIG21 is a block diagram showing an example of a schematic configuration of a car navigation device to which the technology of the present disclosure can be applied; and

[0045] 22 is a block diagram of an exemplary structure of a general-purpose personal computer in which the method and / or apparatus and / or system according to the embodiments of the present disclosure may be implemented. DETAILED DESCRIPTION

[0046] Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings. For the sake of clarity and conciseness, not all features of an actual implementation are described in this specification. However, it should be understood that in the process of developing any such actual implementation, many implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with system and business-related constraints, which may vary from implementation to implementation. In addition, it should be understood that although the development work may be very complex and time-consuming, it is a routine task for those skilled in the art who benefit from the contents of this disclosure.

[0047] It should also be noted here that in order to avoid obscuring the present disclosure due to unnecessary details, the drawings only show the device structures and / or processing steps closely related to the solutions according to the present disclosure, while other details that are not closely related to the present disclosure are omitted.

[0048] As mentioned above, it is expected to provide enhanced technologies for short-range communication between terminal devices, especially enhanced technologies for multicast or broadcast communication modes. In the following, multicast and broadcast can be collectively referred to as multicast. In addition, in some of the following descriptions, the Internet of Vehicles scenario will be used as an example, but it should be understood that this is not restrictive and is only for the convenience of description. The terms first, second, third, fourth, etc. in this article are only for the purpose of distinction and do not have any order, priority or other meaning.

[0049] <First embodiment>

[0050] Figure 1 shows a functional module block diagram of an electronic device 100 for wireless communication according to an embodiment of the present application. As shown in Figure 1, the electronic device 100 includes: a transceiver unit 101, configured to send service information of a service that can be provided by a first terminal device to one or more second terminal devices, wherein the service information includes service type information and service characteristic information; and a providing unit 102, configured to provide a data stream of the corresponding service to at least one terminal device among the one or more second terminal devices based on the service information.

[0051] The transceiver unit 101 and the providing unit 102 may be implemented by one or more processing circuits, which may be implemented as chips or processors, for example. Furthermore, it should be understood that the various functional units in the electronic device shown in FIG1 are merely logical modules divided according to the specific functions they implement, and are not intended to limit specific implementation methods.

[0052] The electronic device 100 can be, for example, provided on a first terminal device, or can be communicatively connected to the first terminal device. The terminal device described herein can be, for example, various user equipment, and the terminal device will also be represented by UE hereinafter. For example, the terminal device can be implemented as a mobile terminal (such as a smart phone, a tablet personal computer (PC), a notebook PC, a portable game terminal, a portable / dongle-type mobile router, and a digital camera) or a vehicle-mounted terminal (such as a car navigation device). The terminal device can also be implemented as a terminal that performs machine-to-machine (M2M) communication (also referred to as a machine type communication (MTC) terminal). In addition, the terminal device can be a wireless communication module (such as an integrated circuit module including a single chip) installed on each of the above-mentioned terminals.

[0053] Here, it should also be noted that the electronic device 100 can be implemented at the chip level, or it can also be implemented at the device level. For example, the electronic device 100 can work as the first terminal device itself, and can also include external devices such as memory, transceiver (not shown in the figure), etc. The memory can be used to store programs and related data information that need to be executed by the electronic device to implement various functions. The transceiver may include one or more communication interfaces to support communication with different devices (for example, other terminal devices, base stations, etc.), and the implementation form of the transceiver is not specifically limited here.

[0054] In this embodiment, the first terminal device can provide a data stream of a certain service type to other terminal devices, and is therefore also referred to as a service UE or information source hereinafter. For example, the first terminal device can provide: perception capabilities of a specific area, such as various sensor data, sensors including, for example, Lidar, radar, camera devices, meteorological sensors, etc.; target information within a specific area, such as the location and movement speed of vehicles, pedestrians, and aircraft; map information services, such as the construction of 2D or 3D maps; task information publishing services, such as the release of demand tasks for automated guided vehicles (AGVs) to transport goods; parameter updates during the deployment or training of artificial intelligence / machine learning (AI / ML) models, such as reporting of training iteration results and model parameter updates involved in distributed learning and federated learning.

[0055] To inform other terminal devices of the types of services that the first terminal device can provide, the first terminal device can include service type information in the service information. For example, the service type information can indicate, but is not limited to, one or more of the above types. The service type information can be indicated by a service identifier (ID), and the service identifier can be standardized. Alternatively, the service type information can be in the form of textual description information, which is not restrictive.

[0056] Furthermore, the service information may also include service characteristic information, which is used to indicate the characteristics of one or more granular services under the corresponding service type. Exemplarily, the service characteristic information may include: service characteristic identification (ID), service characteristic differentiation information, directional or regional transmission requirements, and relay transmission related information. The service characteristic ID is used to uniquely represent a finer-grained service characteristic under the corresponding service type, such as indicating the type of a specific sensor when the service type is the perception capability of a specific area. In addition, the service characteristic ID can also be unique within the local mesh network.

[0057] The service characteristic differentiation information is used to differentiate between the different characteristics of the service content of the corresponding service type. Exemplarily, the service characteristic differentiation information includes one or more of the following: the geographical scope involved in the service data, service source information / sensor information, and map resolution. Among them, the sensor information includes, for example, the type of sensor, location such as source coordinates, direction, field of view (FOV), etc. In this way, the sharing of sensor data or other source data can be achieved, which is beneficial to the fusion requirement matching and alignment correction in the data fusion perception process of sensors or other sources.

[0058] Directional or regional transmission requirements are used to further limit service content. These can include transmission requirements for a specific direction or a specific area. For example, if there are two lanes leaving an intersection, the vehicle information in one lane may not be meaningful to the other lane. In this case, only the vehicle information in one lane needs to be provided.

[0059] Relay transmission-related information may include, for example, one or more of the following: the transmission range of service data, whether relay transmission is possible, the directional or regional transmission requirements of relay transmission, the hop limit of relay transmission, and service reliability requirements. Service reliability requirements may include, for example, the need for alternative communication paths and the QoS of relay transmission.

[0060] In addition, the service information may also include the transmission mode of the data stream carrying the service, which includes broadcast, multicast, or unicast.

[0061] By sending service information that can be provided by the first terminal device to one or more second terminal devices, terminal devices with relevant service needs can obtain the corresponding service content from the first terminal device at the desired granularity. The second terminal device can determine whether to save the received service information and maintain connection confirmation with the serving UE based on its own capabilities, such as whether it has service forwarding capabilities, that is, act as a relay UE.

[0062] The transceiver unit 101 may send the service information via the PC5 port in at least one transmission mode of broadcast, multicast, and unicast.

[0063] Accordingly, the providing unit 102 may, for example, provide a data stream of a corresponding service to at least one second terminal device based on the service information in response to a demand of the second terminal device. The second terminal device may be a relay UE or a remote UE that is not a relay UE.

[0064] Furthermore, providing unit 102 may be configured to mark data packets in the data stream of the corresponding service based on the service characteristic information before transmission. Providing unit 102 may perform marking in one of the following ways: marking a specific field within the header of the data packet at a specific transport protocol layer included in the transport protocol stack; modulating the data within the data packet using a modulation method corresponding to the service characteristic information before transmission; or transmitting the data packet within a time period corresponding to the service characteristic information. In this way, the second terminal device can identify data packets corresponding to the service characteristics.

[0065] In addition, the transceiver unit 101 may also be configured to provide the affinity information of the first terminal device to the second terminal device, where the affinity information is one or more of the geographic location information, mobility information, and path planning information of the first terminal device.

[0066] Because both the first and second terminal devices may be in a mobile state, the actual link between them may be constantly changing. To provide stable data services, it is desirable that the first and second terminal devices have similar motion characteristics. For example, the similarity of their motion characteristics can be assessed by the degree of matching of their phase information.

[0067] Exemplarily, the matching of the phase information between two terminal devices can be performed as follows: D = w1×d1+w2×d2+w3×d3 (1)

[0068] Where d1 represents the Euclidean distance between the two terminal devices, d2 represents the speed difference between the two terminal devices, d3 represents the percentage of overlap of the planned or expected paths of the two terminal devices, and w1, w2, and w3 represent the weight coefficients of each item.

[0069] The matching of the affinity information can be performed by the second terminal device or the first terminal device, and this is not restrictive. For example, when the second terminal device determines that the degree of matching between its affinity information and the first terminal device is above a predetermined threshold, it requests the first terminal device to transmit data for a specific service.

[0070] In addition to the above-mentioned phase information, the matching process can also consider the transmission and reception capabilities of the second terminal device, which can be indicated by a numerical value. For example, large vehicles use distributed antennas, that is, transceiver antennas are set at different heights and in all directions of the vehicle body. Compared with small vehicles that use single antennas / centralized antennas, they have stronger data transmission and reception capabilities and the spatial angle range for establishing short-distance communication links. Therefore, as a relay node, they can have stronger data transmission and reception capabilities and the continuity of short-distance communication links.

[0071] In one example, the second terminal device is a relay device and is used to send a data stream to one or more third terminal devices (also called remote terminal devices or remote UEs). The relay device here can be a single relay device or a local D2D network formed by multiple relay devices. The transceiver unit 101 is also configured to send a networking request to the second terminal device in response to the service content demand information from the second terminal device. The networking request may include service information and affinity information of the first terminal device. The service content demand information, for example, includes a description of a specific service type and service characteristics, or a description of coverage requirements in a certain direction, in order to request surrounding terminal devices that have not joined the network to join the network to provide corresponding services or expand the coverage area of ​​existing services. For example, when the affinity information of the first terminal device can match the relay device and / or the remote terminal device, the first terminal device can join the network and provide services.

[0072] In addition, the transceiver unit 101 may also send a networking request in response to an application layer request. In some cases, there may not be an existing local mesh network, that is, the first terminal device initiates the establishment of a local mesh network. These are not restrictive.

[0073] The electronic device 100 according to this embodiment can provide finer granularity service data to better meet customized needs. In addition, the electronic device 100 can also enable the first terminal device to join an existing local mesh network or initially initiate a networking request to expand the service coverage area.

[0074] <Second embodiment>

[0075] Figure 2 shows a functional module block diagram of an electronic device 200 according to another embodiment of the present application. As shown in Figure 2, the electronic device 200 includes: a receiving unit 201, configured to receive service information of a service that can be provided by the second terminal device from the second terminal device, wherein the service information includes service type information and service characteristic information; and a sending unit 202, configured to include the service information in the provision information of the data service that can be provided by the first terminal device and multicast it to one or more third terminal devices.

[0076] The receiving unit 201 and the sending unit 202 may be implemented by one or more processing circuits, which may be implemented as chips or processors, for example. Furthermore, it should be understood that the various functional units in the electronic device shown in FIG2 are merely logical modules divided according to the specific functions they implement, and are not intended to limit specific implementation methods.

[0077] The electronic device 200 may be provided on the first terminal device, or may be communicatively connected to the first terminal device, for example.

[0078] Here, it should also be noted that the electronic device 200 can be implemented at the chip level, or it can also be implemented at the device level. For example, the electronic device 200 can work as the first terminal device itself, and can also include external devices such as memory, transceiver (not shown in the figure), etc. The memory can be used to store programs and related data information that need to be executed by the electronic device to implement various functions. The transceiver may include one or more communication interfaces to support communication with different devices (for example, other terminal devices, base stations, etc.), and the implementation form of the transceiver is not specifically limited here.

[0079] For example, the receiving unit 201 may receive the service information via the PC5 port in at least one transmission mode of broadcast, multicast, and unicast.

[0080] The service information in this embodiment has the same meaning as the service information in the first embodiment. For example, the service type information indicates the type of service provided by the second terminal device, and the service characteristic information indicates information about the characteristics of the service at one or more granular levels within the service type. Service types include, for example, awareness of a specific area, provision of target information within a specific area, map information services, task information publishing services, and parameter updates during the deployment or training of artificial intelligence / machine learning models. The service characteristic information may include one or more of the following: a service characteristic ID, service characteristic differentiation information, directional or regional transmission requirements, and relay transmission-related information. The service characteristic differentiation information may include one or more of the following: the geographic scope of the service data, service source information / sensor information, and map resolution. For example, directional or regional transmission requirements include transmission requirements for a specific direction or for a specific area. Relay transmission-related information may include one or more of the following: the transmission range of the service data, whether relay transmission is possible, directional or regional transmission requirements for relay transmission, hop limit for relay transmission, and service reliability requirements. Furthermore, the service information may also include the transmission mode of the data stream carrying the corresponding service. For details, refer to the first embodiment and are not repeated here.

[0081] The sending unit 202 may be configured to include the service information in the provision information and multicast it to one or more third terminal devices, for example, when the relay transmission related information indicates that relay transmission is possible. Of course, it may also be assumed that the multicast can be performed.

[0082] In this way, the first terminal device works as a relay UE, the second terminal device works as a service UE (information source), and the third terminal device works as a remote UE (also called an initiating UE). The service UE, relay UE, and remote UE constitute a local mesh network. The data services that the first terminal device can provide include data services that are currently being provided and available data services, such as data services forwarded to the first terminal device through other online nodes (including service UE and other relay UEs). By including information on the data services that the first terminal device can provide in the provision information and providing it to multiple third terminal devices, third terminal devices with corresponding data needs can obtain data services via relays.

[0083] In addition to the information about the data services that the first terminal device can provide, the provided information may also include the affinity information of the first terminal device. As mentioned above, the affinity information includes one or more of the geographical location information, mobility information, and path planning information of the terminal device.

[0084] Since the mobility of the relay UE will cause the actual link between it and the remote UE to change continuously, specifically, the received signal strength changes, affecting the continuity of the service after the remote UE accesses the network, the relay UE can provide phase information, so that the phase matching between the relay UE and the remote UE can be performed. The specific example of phase matching is as described in the first embodiment and will not be repeated here. Phase matching can be performed at the relay UE or at the remote UE, which is not restrictive. For example, in the case of phase matching between the relay UE and the remote UE, a connection between the relay UE and the remote UE is established.

[0085] For ease of understanding, Figure 3 shows an example of affinity matching in a connected vehicle scenario. UE1 through UE4 are relay UEs, interconnected to form a PC5 mesh network. UE x, UE y, UE z, and UE r are remote UEs. UE r's movement direction is opposite to that of the relay UEs, so UE r's affinity does not match that of relay UE 3, and it cannot establish a connection with UE 3.

[0086] The receiving unit 201 is further configured to receive a service triggering request from a third terminal device and match the service triggering request with data services that can be provided by the first terminal device, wherein the service triggering request includes information about service characteristics required by the third terminal device. The sending unit 202 is configured to provide the data service to the third terminal device if the requirement information matches the data service that can be provided by the first terminal device.

[0087] The demand information of business characteristics includes, for example, the geographical scope involved in the required business data, service source information / sensor information, map resolution, etc. In fact, the perfect match between the demand information and the data service that the first terminal device can provide is a low-probability event, so the demand information can be set as a representation of some points, and the data service that the first terminal device can provide is a representation of the range, as long as the former can fall within the range of the latter. For example, when the business characteristics indicate the geographical range, the business characteristic information in the demand information can be the geographical location of some target points, and the first terminal device provides the regional range, as long as the geographical location of the target point is within the provided regional range. Similarly, in other business types, similar comparison methods can be applied, such as the first terminal device can provide the parameter update range of a specific layer in the AI / ML model, the working area range corresponding to the robot or drone work task, etc.

[0088] In addition, the service trigger request may also include one or more of the following: QoS requirements for service data transmission (such as multi-hop number restrictions, service continuity requirements, etc.), transmission mode type requirements (whether the transmission between the first terminal device and the third terminal device is broadcast, multicast or unicast), and the relevance information of the third terminal device. The receiving unit 201 is also configured to perform matching of these requirements or information to comprehensively determine whether the first terminal device can provide data services for the third terminal device. For example, the receiving unit 201 can perform matching of relevance information as above, and not provide data services to the third terminal device if the relevance information does not match. Similarly, the receiving unit 201 can also consider the QoS requirements and transmission mode type requirements of the third terminal device when matching data services.

[0089] The sending unit 202 can, for example, provide data services to the third terminal device in one of the following ways: adding the third terminal device to the subscription group of the data service whose content completely matches the content being provided by the first terminal device; adding a new data service that meets the needs of the third terminal device and adding the third terminal device to the subscription group of the newly added data service; and establishing a unicast data service from the first terminal device to the third terminal device.

[0090] Specifically, if the first terminal device already provides a broadcast or multicast data service with identical service characteristics to other terminal devices, the first terminal device only needs to add the third terminal device as a new subscribing remote UE for the data service. In this case, there is basically no need to modify the QoS rules and corresponding packet filters. In the case of multicast, the number of group members and range parameters may need to be updated.

[0091] In the case that the first terminal device has not yet provided the data service that meets the requirements (including the two situations that the required service characteristics do not exist at all and do not fully correspond), the first terminal device first needs to add the configuration of the corresponding data service from other relay UEs or service UEs, such as data transmission that determines the relevant service characteristics on the data plane and modification of its own data plane QoS rules and forwarding packet filters, etc., and add the third interrupt device to the subscription group of the newly added data service.

[0092] In addition, the first terminal device can also establish a unicast bearer service data stream for the third terminal device, that is, provide unicast data services. In the unicast establishment / modification process, the first terminal device and the third terminal device mutually confirm the modification of QoS rules and packet filters. Note that although the first terminal device and the third terminal device are unicast in this case, the data forwarded by the first terminal device can be in multicast form, that is, the service data generated by the information source does not only serve one remote UE.

[0093] After ensuring that the data plane process is ready, the first terminal device sends confirmation information to the third terminal device, for example, including QoS rules / packet filters / destination addresses (L2 or L3 destination / source ID) information for sending and receiving the data stream. The confirmation information can also include the ID of a newly added service feature under a certain service type of the third terminal device. For example, the service data stream originally relayed and broadcast by the first terminal device itself contains some sensor shared data / target identification information, and at this time the third terminal device suddenly adds a service feature requirement that does not belong to the existing data stream but belongs to the information set that the service UE can provide (such as information about the lane to be turned into). In this case, the ID of the newly added corresponding service feature needs to be included.

[0094] If the first terminal device provides the corresponding data service in the form of broadcast or multicast, there is no need for the third terminal device to feedback and the data plane can be updated directly. If the first terminal device provides the corresponding data service in the form of unicast, the first terminal device needs to wait for the feedback of the third terminal device before initiating data plane transmission.

[0095] Subsequently, the first terminal device sends the negotiated data stream to the third terminal device.

[0096] For ease of understanding, Figure 4 shows an example of the relevant information flow between the service UE (second terminal device), the relay UE (first terminal device) and the remote UE (third terminal device). Among them, the relay UE can represent a single relay UE, or it can represent a local network formed by multiple relay UEs. In step 1, the service UE sends its service information to the relay UE, for example, by broadcasting or multicasting. It should be noted that although only one service UE is shown here, this is only representative, and there can be multiple service UEs. In step 2, the relay UE includes the service information in the service availability notification, such as the provision information described above, and broadcasts or multicasts it to the remote UE. In step 3, the remote UE with specific service requirements receives the service availability notification and sends a service trigger request to the relay UE if the compatibility of the remote UE and the relay UE matches. The service trigger request includes the service characteristic requirement information of the relay UE, and may also include the compatibility information of the relay UE, QoS requirements, etc. In step 4, the relay UE prepares the data plane in response to the service trigger request and sends a service configuration notification, i.e., confirmation information. In the case of multicast, the service configuration notification only notifies the data service to be provided. In the case of unicast, the service configuration notification also includes a unicast link establishment request. In step 5, the remote UE provides feedback to the relay UE on whether it accepts the unicast link establishment request. In step 6, the relay UE sends the required service data to the remote UE.

[0097] In addition, in step 3, the remote UE may also send a service trigger request to multiple relay UEs, obtain service availability notifications from multiple relay UEs, and select the most appropriate relay UE for access. Note that these information flows are only examples and are not restrictive.

[0098] In one example, assuming that the first terminal device is in the first mesh network, that is, the first terminal device is a relay UE in the first mesh network, the sending unit 202 is also configured to send service content requirement information to one or more fourth terminal devices outside the first mesh network, and the receiving unit 201 receives the networking request sent by the fourth terminal device in response to the service content requirement information.

[0099] The service content requirement information may include, for example, a description of a specific service type and characteristics, or a description of coverage requirements in a particular direction, thereby requesting that nearby terminal devices not yet connected to the network (herein referred to as fourth terminal devices) join the network to provide the corresponding service or expand the coverage area of ​​an existing service. The service content requirement information may be sent via multicast along with the provisioning information described above, or separately, without limitation.

[0100] After receiving the service content requirement information, the fourth terminal device that is not currently in the network can issue a network request if it determines that it can meet the relevant requirements. The network request can be received and processed by any relay UE in the first mesh network, not limited to the first terminal device.

[0101] For example, when a fourth terminal device is to access the first mesh network as a relay UE, the networking request may include the fourth terminal device's phase information, the coverage type provided by the fourth terminal device, and the corresponding transmit power or expected transmission distance of each coverage type, thereby notifying the first mesh network of the service range it can provide. In addition, in the case of initial networking, that is, when the fourth terminal device serves as the initial UE to establish the network, such as due to application layer requirements, the fourth terminal device may also send such a networking request to the first terminal device.

[0102] When a fourth terminal device wishes to access the first mesh network as a serving UE, the networking request may include service information for the fourth terminal device. The networking request may also include the first terminal device's affinity information. Furthermore, in the case of initial networking, where the fourth terminal device serves as the initial UE in network establishment, such as due to application layer requirements, the fourth terminal device may also send such a networking request to the first terminal device.

[0103] For example, the first terminal device reviews the above networking request or forwards the received networking request to the central node of the first mesh network for review. In the latter case, the first mesh network adopts a centralized control method. Specifically, the network control logic can be deployed in a central node or multiple central nodes. The central node can be a UE, a base station, or a core network functional unit. Each central node has the function of deciding network configuration and whether to add a new service UE or relay UE. The central node also has the function of publishing update information. If it is a UE type central node, the UE needs to have authorization information from the core network.

[0104] For ease of understanding, Figure 5 shows an example of the information flow of a fourth terminal device joining an existing first mesh network. Relay UE 1 to Relay UE X are relay nodes in the existing first mesh network. Periodic updates can be performed between Relay UE 1 and Relay UE X (shown as step 0 in the figure). For example, the following content can be updated: the types of services currently included in the network and the service characteristics information corresponding to each service type; the current node information of the network. For example, when the service UE exits the network or passively disconnects from the local network, the service UE needs to send notification information in a timely manner or the relay UE directly connected to the service UE needs to update it in a timely manner. The node information of the network can include the phase information and coverage information of each node, such as the configuration of directional transmission, the service types and service characteristics information subscribed by each node, etc. In a centrally controlled network, the node information can also include the number of multi-hops from the central node to the end node and the number limit.

[0105] In step 1, taking relay UE 1 as an example, the relay UE sends a service availability notification. Here, the service availability notification not only includes information about the data services that the relay UE can provide, but also includes service content requirement information. The service content requirement information includes, for example, a description of a specific service type and service characteristics, or a description of coverage requirements in a certain direction. After receiving the service content requirement information, the new UE responds. Here, the new UE can respond as a relay UE or as a serving UE to send a networking request to relay UE 1 (step 2). As previously mentioned, the information included in the networking request may differ depending on whether it is acting as a relay UE or a serving UE.

[0106] Relay UE 1 reviews the networking request, checking for compatibility, service content, and coverage type. In a centrally controlled network, if relay UE 1 is not a central node, it forwards the networking request to the central node for review. If the review passes, a notification of acceptance of the networking request is sent to the new UE in step 4. The new UE then joins the first mesh network as both a new relay UE and a new serving UE, thereby expanding the coverage of the first mesh network.

[0107] Figure 6 shows an example of the matching of a new relay UE joining a mesh network in a vehicle networking scenario. The roadside unit (RSU) at the intersection sends its sensing information to surrounding UEs (vehicle UEs, VRU UEs) in the form of omnidirectional broadcasts, such as sensing information or identification information of vehicles, pedestrians, and other objects in all directions of the intersection. Based on its own service coverage, the RSU has requested local networking to forward its broadcast data services through relay UEs 1 to 4 on the first layer that can communicate directly with the RSU. To further expand the coverage of the RSU service, relay UE1, for example, after negotiation / after being instructed by the RSU UE, can use the information flow of Figure 5 to select a new relay UE that matches it as a new relay node. In this example, there may also be differences in the forwarding processing of RSU original service data by different relay UEs on the data plane. For example, the data forwarded by relay UE 1 may include information on the four directions of the intersection. This is because the relevant vehicles may need to turn or pass the intersection immediately, while the newly added relay UE may only include information corresponding to part of the forward direction, because the relevant vehicles may only need to obtain information about surrounding vehicles.

[0108] Figure 7 illustrates an example of matching new service UEs joining a mesh network in a connected vehicle scenario. UEs z, w, and y, acting as remote UEs on the road, indirectly obtain road information broadcast by the RSUs through two relay nodes, UE x and UE x+2. These two relay nodes can filter RSU broadcasts based on their characteristics to match the needs of their respective remote UEs. At this point, UE z gradually moves out of the RSU's sensing range and has greater requirements for road conditions in its forward direction. UE x-2, stopped at a location in its forward direction and equipped with sensors capable of providing data services, can now join the mesh network by executing the information flow shown in Figure 5, thereby indirectly or directly providing data services to UE z.

[0109] In addition, when the fourth terminal device is approved to join the mesh network as a new service UE, the sending unit 202 is also configured to send network extension confirmation information to the fourth terminal device. The network extension confirmation information, for example, includes confirmation of the service type and service characteristics that need to be transmitted after the service UE accesses the network.

[0110] When the fourth terminal device is approved to join the mesh network as a new relay UE, the sending unit 202 is further configured to send network extension confirmation information to the fourth terminal device, where the network extension confirmation information includes a beam direction restriction or recommendation indication. In addition, the network extension confirmation information may also include the coverage type of the previous relay UE (e.g., the second terminal device) of the corresponding service flow, such as omnidirectional coverage or specific direction coverage.

[0111] Beam direction restriction or recommendation indication is used to restrict or recommend the transmission direction of broadcasts or multicasts for newly joined relay UEs to prevent remote UEs in the same area from simultaneously receiving the broadcasts / multicasts of the same or similar service data streams from two relay UEs. Figure 8 shows a schematic example of beam direction restriction. UE 1 and UE 2 are relay UEs, UE 3 and UE 4 are remote UEs, and UE 2 is a newly joined relay UE. To avoid co-covering UE 4 with UE 1, UE 2's beam direction is restricted to cover only UE 3.

[0112] The beam direction restriction or recommendation mentioned here can be achieved, for example, by beamforming. Alternatively, the data streams broadcast or multicast by different relay UEs can be distinguished by different modulation and demodulation modes, different time domains for sending data packets, and indicating such differences in signaling.

[0113] In addition, when beamforming is supported, the first terminal device may perform beam matching to determine a beam to be used before providing data services. The beam matching process may include, for example, selecting a beam that covers the terminal device to be served and avoids covering terminal devices already served by other terminal devices.

[0114] If the first terminal device is provided with network extension confirmation information including a beam direction restriction or recommendation indication before joining the mesh network as a new relay UE, the first terminal device may perform beam matching within the beam range indicated by the beam direction restriction or recommendation indication, or use the beam indicated by the beam direction restriction or recommendation indication for data transmission. The processing of beam matching between UEs will be described in detail in the fourth embodiment.

[0115] It should be noted that, considering the interests of operators, core network management may be required before forming and joining a local mesh network based on PC5. Typically, fully independent PC5 port service models (out-of-coverage) are limited to scenarios such as emergency services (such as field search and rescue), while most commercial scenarios are limited to in-coverage scenarios.

[0116] Specifically, there are three scenarios. First, all participating UEs (including relay UEs, serving UEs, and remote UEs) must be online and request permission or policy issuance for related services (local networking and localized services) from relevant core network units (AMF, SMF, PCF) through registration processes (UE registration request) and UE policy update processes. Second, any one of the participating UEs or a UE with a specific role (relay UE, serving UE, or remote UE) must be online and request permission or policy issuance for related services (local networking and localized services) from relevant core network units (AMF, SMF, PCF) through registration processes (UE registration request) and UE policy update processes. Third, a UE does not need to be online to initiate local networking or provide or receive services. It only needs to obtain relevant service permissions in advance, such as part of the UE policy, such as the factory UE configuration, USIM card configuration, and a non-expired policy issued by the PCF during network access, which includes the current policy for local networking and services.

[0117] In addition to carrying specific information elements in the UE policy to authorize networking requests, the management unit of the core network can also specifically issue some networking identifiers, restrictions on the types of services that can be carried by the short-range local network, corresponding operational frequency bands of the short-range local network, geographical area restrictions / scale restrictions of the network and other parameters. The networking identifier is used to uniquely identify the short-range local network within the PLMN or a specific area, such as a city or a county.

[0118] In addition, when the coverage capability provided by a relay UE in a mesh network, such as a newly joined relay UE, is not what the mesh network currently requires, or when the relay UE that has joined the network does not need to carry data transmission for any remote UE within a specific time period, the relay UE or the corresponding relay UE chain may enter a connection waiting (pending) state during the time period. In this case, the relay UE (such as the first terminal device, specifically, the sending unit 202 of the first terminal device) may continuously send keep alive signaling to mutually confirm the availability of connection wakeup.

[0119] For example, if only the end relay UE is in the connection waiting state, the end relay UE (relay UE 1) needs to periodically send keepalive signaling to its previous relay node (relay UE 2) and receive keepalive ack (keep alive confirmation) signaling from it, as shown in Figure 9. If relay UE 1 does not receive keepalive ack signaling within a predetermined time after sending the keepalive signaling, it can be determined that it is not reachable and has left the mesh network. If relay UE 2 does not receive keepalive signaling from relay UE 1 for more than a certain period of time, it is considered that relay UE 1 is not reachable. For example, relay UE 1 can send keepalive signaling every 10 seconds.

[0120] Alternatively, relay UE 2 may periodically send keep alive signaling to relay UE 1 and receive keep alive ack signaling from relay UE 1. In this case, if relay UE 2 does not receive keep alive ack signaling within a predetermined time after sending the keep alive signaling, it may be determined that relay UE 1 is not reachable. If relay UE 1 does not receive keep alive signaling from relay UE 2 for more than a certain period of time, it may be determined that it is not reachable. For example, relay UE 2 may send keep alive signaling every 10 seconds.

[0121] In the case where there is a chain of waiting relay UEs, the end relay UE of the chain (intermediate UE 1) can send keep alive signaling to the upper relay UE of the chain, and feedback can be sent upward step by step in this way. In the feedback process of each level, the ID of itself and the known lower relay UEs as well as coverage information, mobility information, etc. can be carried; in the feedback process, the keep alive ack signaling should also be sent down step by step after confirmation by the top relay UE x that is not in the waiting state, as shown in Figure 10.

[0122] If a relay UE does not receive a keep-alive ack signaling within a predetermined time after sending a keep-alive signaling, it is considered unreachable. If the top-level relay UE x, which is not in a waiting state, does not receive a keep-alive signaling for a certain period of time, the relay UE chain is considered unreachable. If only some relay UEs have feedback information, the remaining relay UEs in the chain are considered unreachable.

[0123] In summary, the electronic device 200 according to this embodiment can provide relay transmission of service data with finer granularity to better adapt to customized needs, and enhance the coverage of the multicast communication mode through an extensible networking form.

[0124] <Third embodiment>

[0125] Figure 11 shows a functional module block diagram of an electronic device 300 according to another embodiment of the present application. As shown in Figure 11, the electronic device 300 includes: a receiving unit 301, configured to receive provision information of a data service that can be provided by the second terminal device sent by the second terminal device via multicast from the second terminal device, the provision information including service information of the service that can be provided, and the service information including service type information and service characteristic information; and a sending unit 302, configured to send a service trigger request of the first terminal device to the second terminal device, the service trigger request including demand information of the service characteristics of the first terminal device.

[0126] The receiving unit 301 and the sending unit 302 may be implemented by one or more processing circuits, which may be implemented as chips or processors, for example. Furthermore, it should be understood that the various functional units in the electronic device shown in FIG11 are merely logical modules divided according to the specific functions they implement, and are not intended to limit specific implementation methods.

[0127] The electronic device 300 may be provided on the first terminal device, or may be communicatively connected to the first terminal device, for example.

[0128] Here, it should also be noted that the electronic device 300 can be implemented at the chip level, or it can also be implemented at the device level. For example, the electronic device 300 can work as the first terminal device itself, and can also include external devices such as memory, transceiver (not shown in the figure), etc. The memory can be used to store programs and related data information that need to be executed by the electronic device to implement various functions. The transceiver may include one or more communication interfaces to support communication with different devices (for example, other terminal devices, base stations, etc.), and the implementation form of the transceiver is not specifically limited here.

[0129] The service information in this embodiment has the same meaning as the service information in the first and second embodiments. The relevant descriptions in the first and second embodiments are also applicable and will not be repeated here.

[0130] In this embodiment, the first terminal device is a remote UE, and the second terminal device can be a relay UE or a serving UE.

[0131] The service trigger request may also include one or more of the following: QoS requirements for service data transmission, transmission mode type requirements, and affinity information of the first terminal device. The affinity information may include one or more of the first terminal device's geographic location information, mobility information, and path planning information. The relevant details are provided in the second embodiment and are not repeated here.

[0132] When the first terminal device has a specific service requirement, a comparison can be made based on the received provision information, and the above-mentioned service trigger request can be sent to the corresponding relay UE or service UE if the requirement is met. The matching of the phase information can be performed at the first terminal device or at the second terminal device. In addition, the receiving unit 301 is also configured to receive confirmation information from the second terminal device to confirm that the second terminal device will provide the requested data service. When the transmission mode is unicast, the sending unit 302 is also configured to send feedback to the second terminal device to indicate acceptance of the establishment of the unicast link. Subsequently, the second terminal device can provide data services to the first terminal device.

[0133] In addition, when there is a specific service requirement, the first terminal device can send a service trigger request to multiple relay UEs and / or service UEs, obtain the provided information of multiple relay UEs and / or service information of multiple service UEs, and select the most appropriate relay UE / or service UE for access.

[0134] The relevant information flow has been described in detail in the first embodiment and the second embodiment, which is also applicable to this embodiment and will not be repeated here.

[0135] In addition, the first terminal device may perform a beam matching process with the second terminal device before performing data transmission to determine the beam to be used. The process of beam matching between UEs will be described in detail in the fourth embodiment.

[0136] The electronic device 300 according to this embodiment can obtain service data with finer granularity to better meet customized needs and enhance the coverage of the multicast communication mode.

[0137] <Fourth embodiment>

[0138] Figure 12 shows a functional module block diagram of an electronic device 400 according to another embodiment of the present application. As shown in Figure 12, the electronic device 400 includes: a matching unit 401, configured to perform beam matching for one or more second terminal devices to select a beam to be used for communication; and an execution unit 402, configured to use the selected beam to perform the communication between the first terminal device and the one or more second terminal devices.

[0139] The matching unit 401 and the execution unit 402 may be implemented by one or more processing circuits, which may be implemented as chips or processors, for example. Furthermore, it should be understood that the various functional units in the electronic device shown in FIG12 are merely logical modules divided according to the specific functions they implement, and are not intended to limit specific implementation methods.

[0140] The electronic device 400 may be provided on the first terminal device, or may be communicatively connected to the first terminal device, for example.

[0141] It should also be noted here that the electronic device 400 can be implemented at the chip level or at the device level. For example, the electronic device 400 can operate as the first terminal device itself and may also include external devices such as a memory and a transceiver (not shown in the figure). The memory can be used to store programs and related data information that the electronic device needs to execute to implement various functions. The transceiver may include one or more communication interfaces to support communication with different devices (e.g., other terminal devices, base stations, etc.), and the implementation form of the transceiver is not specifically limited here.

[0142] The electronic device 400 of this embodiment can achieve directional transmission of beams between UEs through beam matching, making communication more targeted while avoiding interference and improving communication efficiency.

[0143] For example, the matching unit 401 may perform beam matching as follows: sending multiple beams to one or more second terminal devices; receiving beam quality reports generated by the one or more second terminal devices based on reception of the multiple beams; and selecting one or more beams with the best communication quality based on the beam quality reports. For example, the communication quality may be indicated by reference signal received power (RSRP) or reference signal received quality (RSRQ).

[0144] Among them, the first terminal device can be referred to as a transmitting UE, and the second terminal device can be referred to as a receiving UE. During the matching process, the transmitting UE can indicate the indexes of multiple transmitting beams. After receiving, the receiving UE feeds back to the transmitting UE the indexes corresponding to one or more beams whose RSRP / RSRQ is higher than a predetermined threshold, and the transmitting UE selects the optimal beam from them. For example, the transmitting UE can select the transmitting beam that all receiving UEs feed back or the transmitting beam that the largest number of receiving UEs feed back. After the beam matching is completed, the receiving UE can also determine which receiving beam to use to receive data from the transmitting UE.

[0145] When a first terminal device performs broadcast or multicast with multiple second terminal devices, the matching unit 401 may, for example, first try a wide beam, then try a combination of a wide beam and a narrow beam, or a combination of a narrow beam, when performing beam matching. Of course, it may also try only a narrow beam. Figure 13 shows an example of a beam matching process. The sending UE x wants to perform broadcast or multicast to the receiving UEs r1 to r3. Since the azimuth angles of UEs r1 to r3 differ greatly, it may be considered to use a wide beam to cover them. As shown in Figure 13, candidate beams 1 to 3 are sent respectively. The receiving UEs within the coverage range of the candidate beams will feedback their indexes. For example, UE x may select candidate beam 2 that can cover UEs r1 to r3.

[0146] Figure 14 shows another example of the beam matching process. In this example, each wide beam cannot fully cover UEs r1 to r3. The transmitting UE x attempts to use a combination of narrow beams to cover the receiving UEs. For example, the combination of two narrow beams shown in Figure 14 can be used for broadcast or multicast. Furthermore, a combination of wide and narrow beams can also be used for broadcast or multicast, depending on the situation.

[0147] In addition, the matching unit 401 is further configured to avoid interference with existing communications when selecting a beam. For example, when the first terminal device is a relay terminal device (relay UE), the matching unit 401 is configured to select a beam whose communication quality for terminal devices served by other terminal devices is lower than a predetermined threshold. In other words, when selecting a beam, the matching unit 401 selects a transmission beam whose communication quality for the remote UE to be served by the first terminal device is higher than the predetermined threshold, but whose communication quality for the remote UE served by other relay UEs or serving UEs is lower than the predetermined threshold.

[0148] For example, other relay UE services or serving UEs may instruct the receiving UEs they are serving to perform beam avoidance matching. Specifically, for example, when the RSRP / RSRQ of the beam received by the receiving UE from the first terminal device is higher than a predetermined threshold, an indication of interference is sent to the other relay UE services or serving UEs or directly to the first terminal device, so that the first terminal device can avoid the corresponding beam when selecting a beam.

[0149] It can be understood that in this situation, the first terminal device acting as a relay UE needs to select multiple remote UEs to be served (group 1), and the base station or other relay UE or service UE instructs the first terminal device to avoid repeated coverage of remote UEs (group 2), and the remote UE performs beam quality reporting such as beam index feedback.

[0150] Figure 15 shows an example of the matching process in this scenario. Relay UE 1 is an existing UE in the mesh network and is currently serving remote UE 3. Note that while shown as a relay UE, it could also be a serving UE. Relay UE 2 is a newly added relay UE. Before executing a broadcast or multicast, Relay UE 2 performs beam selection, taking into account the impact on UE 3 already served by Relay UE 1.

[0151] The upper diagram in Figure 15 shows that relay UE 2 and remote UE 3 are both within the coverage of relay UE 1. Relay UE 2 needs to select an appropriate beam to cover remote UE 1 and remote UE 2 while avoiding covering remote UE 3. The lower left diagram in Figure 15 shows a scenario where relay UE 2 transmits candidate beam 1. This candidate beam can cover remote UE 1 to remote UE 3 simultaneously, causing remote UE 3 to be within the coverage of both relay UE 1 and relay UE 2, resulting in duplicate reception or interference with existing data transmission by relay UE 2. The lower right diagram in Figure 15 shows a scenario where relay UE 2 transmits candidate beam 2. This candidate beam meets the requirements and can cover remote UE 1 and remote UE 2 simultaneously, but does not cover UE 3.

[0152] In addition, as described in the second embodiment, when the first terminal device newly joins the mesh network (as a serving UE or as a relay UE), it can receive network extension confirmation information from the existing relay UE, and the network extension confirmation information may include a beam direction restriction or a recommendation indication. Thus, the first terminal device can perform beam matching processing based on the beam direction restriction or recommendation indication or use the beam indicated by the beam direction restriction or recommendation indication for data transmission.

[0153] After beam matching is completed, the execution unit 402 uses the selected beam to perform communication between the first terminal device and one or more second terminal devices, which can be one of unicast, broadcast or multicast. That is, the execution unit 402 performs data transmission based on beamforming.

[0154] The electronic device 400 according to this embodiment can implement directional data transmission and improve communication efficiency by performing beam matching.

[0155] <Fifth embodiment>

[0156] In the process of describing the electronic device for wireless communication in the above embodiments, it is obvious that some processes or methods are also disclosed. Below, an overview of these methods is given without repeating some of the details discussed above, but it should be noted that although these methods are disclosed in the process of describing the electronic device for wireless communication, these methods do not necessarily use the components described or are not necessarily performed by those components. For example, the embodiments of the electronic device for wireless communication can be partially or completely implemented using hardware and / or firmware, and the methods for wireless communication discussed below can be completely implemented by computer-executable programs, although these methods can also use the hardware and / or firmware of the electronic device for wireless communication.

[0157] Figure 16 shows a flowchart of a method for wireless communication according to an embodiment of the present application. The method includes: sending service information of services that can be provided by a first terminal device to one or more second terminal devices (S11), where the service information includes service type information and service feature information; and providing a data stream of the corresponding service to at least one of the one or more second terminal devices based on the service information (S12). This method can be performed on the first terminal device, for example.

[0158] For example, in step S11, the service information may be sent via the PC5 port in at least one transmission mode of broadcast, multicast, and unicast.

[0159] For example, the service type information indicates the type of service provided by the first terminal device, and the service characteristic information indicates information indicating the characteristics of one or more granular services under the type of service. The types of services may include: perception of a specific area, provision of target information within a specific area, map information services, task information publishing services, and parameter updates during artificial intelligence / machine learning model deployment or training. The service characteristic information may include, for example, one or more of the following: service characteristic identification, service characteristic differentiation information, directional or regional transmission requirements, and relay transmission related information. The service characteristic differentiation information may include one or more of the following: the geographical scope involved in the service data, service source information / sensor information, and map resolution. The directional or regional transmission requirements include transmission requirements for a specific direction or transmission requirements for a specific area, and the relay transmission related information includes one or more of the following: the transmission range of the service data, whether relay transmission is possible, the directional or regional transmission requirements for relay transmission, and the hop limit for relay transmission.

[0160] The service information may also include the transmission mode of the data flow carrying the service.

[0161] Step S12 also includes marking data packets in the data stream of the corresponding service based on the service characteristic information before transmission. For example, marking can be performed in one of the following ways: marking a specific field in the header of the data packet at a specific transport protocol layer included in the transport protocol stack; modulating the data in the data packet using a modulation method corresponding to the service characteristic information before transmission; or transmitting the data packet within a time period corresponding to the service characteristic information.

[0162] Step S11 also includes providing the affinity information of the first terminal device to the second terminal device, where the affinity information is one or more of the geographic location information, mobility information, and path planning information of the first terminal device.

[0163] Exemplarily, the second terminal device may be a relay device configured to transmit the data stream to one or more third terminal devices. Although not shown in the figure, the method may further include: in response to service content demand information from the second terminal device, transmitting a networking request to the second terminal device, the networking request including service information and compatibility information of the first terminal device.

[0164] The above method corresponds to the electronic device 100 in the first embodiment. The specific details can be referred to the first embodiment and will not be repeated here.

[0165] Figure 17 shows a flowchart of a method for wireless communication according to another embodiment of the present application. The method includes: receiving service information of a service that can be provided by a second terminal device from the second terminal device (S21), where the service information includes service type information and service feature information; and including the service information in provision information of data services that can be provided by the first terminal device and multicasting the information to one or more third terminal devices (S22). This method can be performed on the first terminal device, for example.

[0166] For example, in step S21, service information can be received via PC5 port in at least one of broadcast, multicast, and unicast transmission modes. The meaning of service information has been described in detail above and is also applicable to this method, so it will not be repeated here.

[0167] For example, when the relay transmission related information indicates that relay transmission is possible, the service information may be included in the provision information and multicast to one or more third terminal devices in step S22. The provision information may also include the related information of the first terminal device.

[0168] Although not shown in the figure, the above method may further include the following steps: receiving a service trigger request from a third terminal device, the service trigger request including service characteristic requirement information of the third terminal device; matching the service trigger request with data services that can be provided by the first terminal device; and providing the data service to the third terminal device if the requirement information matches the data service that can be provided by the first terminal device. Providing the data service to the third terminal device may include one of the following: adding the third terminal device to a subscription group of a data service whose content completely matches the content currently being provided by the first terminal device; adding a new data service that meets the requirements of the third terminal device and adding the third terminal device to the subscription group of the newly added data service; and establishing a unicast data service from the first terminal device to the third terminal device.

[0169] The service trigger request may also include one or more of the following: QoS requirements for service data transmission, transmission mode type requirements, and related information of the third terminal device.

[0170] In one example, a first terminal device is in a first mesh network, and the method further includes: sending service content requirement information to one or more fourth terminal devices outside the first mesh network, and receiving a networking request sent by the fourth terminal device in response to the service content requirement information. For example, the networking request includes information about the fourth terminal device's characteristics, the coverage type provided by the fourth terminal device, and the transmit power or expected transmission distance corresponding to each coverage type; or, the networking request includes service information of the fourth terminal device. The method further includes reviewing the networking request or forwarding the networking request to a central node of the first mesh network for review.

[0171] The above method also includes: sending network extension confirmation information to the fourth terminal device, where the network extension confirmation information includes beam direction restriction or recommendation indication.

[0172] In addition, a beam matching process may be performed before providing data services to determine a beam to be used. For example, the beam matching process includes selecting a beam that covers the terminal device to be served and avoids covering terminal devices already served by other terminal devices.

[0173] The above method corresponds to the electronic device 200 in the third embodiment. The specific details can be referred to the second embodiment and will not be repeated here.

[0174] Figure 18 shows a flowchart of a method for wireless communication according to another embodiment of the present application. The method includes: receiving provision information of data services that the second terminal device can provide, transmitted by the second terminal device via multicast (S31), the provision information including service information of the available services, including service type information and service feature information; and sending a service trigger request of the first terminal device to the second terminal device (S32), the service trigger request including service feature requirement information of the first terminal device. This method can be performed, for example, on the first terminal device.

[0175] The meaning of the business information has been described in detail above, and is also applicable to this method, so it will not be repeated here.

[0176] For example, the service trigger request may also include one or more of the following: QoS requirements for service data transmission, transmission mode type requirements, and phase information of the first terminal device.

[0177] As shown in the dotted box in Figure 18, the above method may further include step S33: receiving confirmation information from the second terminal device. In addition, when the transmission mode is unicast, the above method may further include step S34: sending feedback to the second terminal device.

[0178] In addition, although not shown in the figure, the above method may further include the following steps: performing beam matching processing with the second terminal device before data transmission to determine the beam to be used.

[0179] The above method corresponds to the electronic device 300 in the third embodiment. For specific details, please refer to the third embodiment and will not be repeated here.

[0180] Figure 19 shows a flowchart of a method for wireless communication according to another embodiment of the present application. The method includes: performing beam matching on one or more second terminal devices to select a beam to be used for communication (S41); and performing communication between a first terminal device and the one or more second terminal devices using the selected beam (S42). This method can be performed, for example, on the first terminal device.

[0181] For example, in step S41, beam matching may be performed as follows: transmitting multiple beams to one or more second terminal devices; receiving beam quality reports generated by the one or more second terminal devices based on reception of the multiple beams; and selecting one or more beams with the best communication quality based on the beam quality reports. Communication quality may be indicated by reference signal received power or reference signal received quality.

[0182] When performing beam matching, a wide beam can be tried first, followed by a combination of a wide beam and a narrow beam, or a combination of narrow beams. Beam selection can also avoid interference with existing communications.

[0183] For example, the first terminal device is a relay terminal device, and in step S41 , a beam whose communication quality for terminal devices served by other terminal devices is lower than a predetermined threshold is selected.

[0184] The above method corresponds to the electronic device 400 in the fourth embodiment. For specific details, please refer to the fourth embodiment and will not be repeated here.

[0185] Note that the above methods can be used in combination or individually.

[0186] The electronic devices 100 to 400 may be implemented as various terminal devices or user devices. Each terminal device or user device may include one or more of the electronic devices 100 to 400 or implement a part or all of their functions.

[0187] The terminal device or user equipment can be implemented as a mobile terminal (such as a smart phone, a tablet personal computer (PC), a notebook PC, a portable game terminal, a portable / dongle-type mobile router, and a digital camera) or an in-vehicle terminal (such as a car navigation device). The terminal device or user equipment can 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 or user equipment can be a wireless communication module (such as an integrated circuit module including a single chip) installed on each of the above terminals.

[0188] [Application examples for terminal devices]

[0189] (First application example)

[0190] 20 is a block diagram showing an example of a schematic configuration of a smartphone 900 to which the technology of the present disclosure can be applied. The smartphone 900 includes a processor 901, a memory 902, a storage device 903, an external connection interface 904, a camera 906, a sensor 907, a microphone 908, an input device 909, a display device 910, a speaker 911, a wireless communication interface 912, one or more antenna switches 915, one or more antennas 916, a bus 917, a battery 918, and an auxiliary controller 919.

[0191] The processor 901 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 smartphone 900. The memory 902 includes RAM and ROM, and stores data and programs executed by the processor 901. The storage device 903 may include storage media such as semiconductor memories and hard disks. The external connection interface 904 is an interface for connecting external devices (such as memory cards and universal serial bus (USB) devices) to the smartphone 900.

[0192] The camera 906 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 907 may include a group of sensors such as a measurement sensor, a gyroscope sensor, a geomagnetic sensor, and an acceleration sensor. The microphone 908 converts the sound input to the smartphone 900 into an audio signal. The input device 909 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 910, and receives an operation or information input from the user. The display device 910 includes a screen such as a liquid crystal display (LCD) and an organic light emitting diode (OLED) display and displays an output image of the smartphone 900. The speaker 911 converts the audio signal output from the smartphone 900 into sound.

[0193] The wireless communication interface 912 supports any cellular communication scheme (such as LTE and LTE-Advanced) and performs wireless communication. The wireless communication interface 912 may generally include, for example, a BB processor 913 and an RF circuit 914. The BB processor 913 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 914 may include, for example, a mixer, a filter, and an amplifier, and transmit and receive wireless signals via an antenna 916. The wireless communication interface 912 may be a chip module on which the BB processor 913 and the RF circuit 914 are integrated. As shown in Figure 20, the wireless communication interface 912 may include multiple BB processors 913 and multiple RF circuits 914. Although Figure 20 shows an example in which the wireless communication interface 912 includes multiple BB processors 913 and multiple RF circuits 914, the wireless communication interface 912 may also include a single BB processor 913 or a single RF circuit 914.

[0194] In addition, in addition to the cellular communication scheme, the wireless communication interface 912 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 912 may include a BB processor 913 and an RF circuit 914 for each wireless communication scheme.

[0195] Each of the antenna switches 915 switches a connection destination of the antenna 916 between a plurality of circuits (eg, circuits for different wireless communication schemes) included in the wireless communication interface 912 .

[0196] Each of the antennas 916 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 912. As shown in FIG20, the smartphone 900 may include multiple antennas 916. Although FIG20 shows an example in which the smartphone 900 includes multiple antennas 916, the smartphone 900 may also include a single antenna 916.

[0197] In addition, the smartphone 900 may include an antenna 916 for each wireless communication scheme. In this case, the antenna switch 915 may be omitted from the configuration of the smartphone 900.

[0198] The bus 917 connects the processor 901, the memory 902, the storage device 903, the external connection interface 904, the camera 906, the sensor 907, the microphone 908, the input device 909, the display device 910, the speaker 911, the wireless communication interface 912, and the auxiliary controller 919. The battery 918 supplies power to the various blocks of the smartphone 900 shown in FIG20 via feeders, which are partially shown as dotted lines in the figure. The auxiliary controller 919 operates the minimum necessary functions of the smartphone 900, for example, in sleep mode.

[0199] In the smartphone 900 shown in FIG20 , the transceiver unit 101, the providing unit 102, and the transceiver of the electronic device 100, the receiving unit 201, the transmitting unit 202, and the transceiver of the electronic device 200, the receiving unit 301, the transmitting unit 302, and the transceiver of the electronic device 300, or the transceiver of the electronic device may be implemented by the wireless communication interface 912. At least a portion of the functions may also be implemented by the processor 901 or the auxiliary controller 919. For example, the processor 901 or the auxiliary controller 919 can implement the provision of service data with finer granularity and the enhancement of mesh network coverage by executing the functions of the transceiver unit 101 and the providing unit 102, can implement the relay transmission of service data with finer granularity and the enhancement of coverage of the multicast communication mode by executing the functions of the receiving unit 201 and the sending unit 202, can implement the acquisition of service data with finer granularity and the enhancement of coverage of the multicast communication mode by executing the functions of the receiving unit 301 and the sending unit 302, and can implement beam matching processing and beamforming-based data transmission between terminal devices by executing the functions of the matching unit 401 and the execution unit 402.

[0200] (Second application example)

[0201] 21 is a block diagram showing an example of a schematic configuration of a car navigation device 920 to which the technology of the present disclosure can be applied. The car navigation device 920 includes a processor 921, a memory 922, a global positioning system (GPS) module 924, a sensor 925, a data interface 926, a content player 927, a storage medium interface 928, an input device 929, a display device 930, a speaker 931, a wireless communication interface 933, one or more antenna switches 936, one or more antennas 937, and a battery 938.

[0202] The processor 921 may be, for example, a CPU or an SoC, and controls a navigation function and other functions of the car navigation apparatus 920. The memory 922 includes a RAM and a ROM, and stores data and programs executed by the processor 921.

[0203] The GPS module 924 measures the position (such as latitude, longitude, and altitude) of the car navigation device 920 using GPS signals received from GPS satellites. The sensor 925 may include a group of sensors such as a gyroscope sensor, a geomagnetic sensor, and an air pressure sensor. The data interface 926 is connected to, for example, the in-vehicle network 941 via an unillustrated terminal and acquires data generated by the vehicle (such as vehicle speed data).

[0204] The content player 927 reproduces content stored in a storage medium (such as a CD or DVD) inserted into the storage medium interface 928. The input device 929 includes, for example, a touch sensor, button, or switch configured to detect a touch on the screen of the display device 930, and receives an operation or information input from the user. The display device 930 includes a screen such as an LCD or OLED display and displays an image of a navigation function or reproduced content. The speaker 931 outputs the sound of the navigation function or the reproduced content.

[0205] The wireless communication interface 933 supports any cellular communication scheme (such as LTE and LTE-Advanced) and performs wireless communication. The wireless communication interface 933 may generally include, for example, a BB processor 934 and an RF circuit 935. The BB processor 934 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 935 may include, for example, a mixer, a filter, and an amplifier, and transmit and receive wireless signals via an antenna 937. The wireless communication interface 933 may also be a chip module on which the BB processor 934 and the RF circuit 935 are integrated. As shown in Figure 21, the wireless communication interface 933 may include multiple BB processors 934 and multiple RF circuits 935. Although Figure 21 shows an example in which the wireless communication interface 933 includes multiple BB processors 934 and multiple RF circuits 935, the wireless communication interface 933 may also include a single BB processor 934 or a single RF circuit 935.

[0206] In addition, in addition to the cellular communication scheme, the wireless communication interface 933 can support other types of wireless communication schemes, such as a short-range wireless communication scheme, a near field communication scheme, and a wireless LAN scheme. In this case, for each wireless communication scheme, the wireless communication interface 933 can include a BB processor 934 and an RF circuit 935.

[0207] Each of the antenna switches 936 switches a connection destination of the antenna 937 between a plurality of circuits included in the wireless communication interface 933 , such as circuits for different wireless communication schemes.

[0208] Each of the antennas 937 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 933. As shown in FIG21, the car navigation device 920 may include multiple antennas 937. Although FIG21 shows an example in which the car navigation device 920 includes multiple antennas 937, the car navigation device 920 may also include a single antenna 937.

[0209] Furthermore, the car navigation device 920 may include an antenna 937 for each wireless communication scheme. In this case, the antenna switch 936 may be omitted from the configuration of the car navigation device 920.

[0210] The battery 938 supplies power to the respective blocks of the car navigation device 920 shown in Fig. 21 via a feeder line, which is partially shown as a dotted line in the figure. The battery 938 accumulates the power supplied from the vehicle.

[0211] In the car navigation device 920 shown in FIG21 , the transceiver unit 101, providing unit 102, and transceiver of the electronic device 100, the receiving unit 201, sending unit 202, and transceiver of the electronic device 200, the receiving unit 301, sending unit 302, and transceiver of the electronic device 300, or the electronic device transceiver can be implemented by the wireless communication interface 933. At least a portion of the functions can also be implemented by the processor 921. For example, the processor 921 can implement the provision of finer-grained service data and enhanced mesh network coverage by executing the functions of the transceiver unit 101 and providing unit 102, the relay transmission of finer-grained service data and enhanced multicast communication mode coverage by executing the functions of the receiving unit 201 and sending unit 202, the acquisition of finer-grained service data and enhanced multicast communication mode coverage by executing the functions of the receiving unit 301 and sending unit 302, and the beam matching processing and beamforming-based data transmission between terminal devices by executing the functions of the matching unit 401 and executing unit 402.

[0212] The technology of the present disclosure can also be implemented as an in-vehicle system (or vehicle) 940 including a car navigation device 920, an in-vehicle network 941, and one or more blocks of a vehicle module 942. The vehicle module 942 generates vehicle data (such as vehicle speed, engine speed, and fault information) and outputs the generated data to the in-vehicle network 941.

[0213] The basic principles of the present invention are described above in conjunction with specific embodiments. However, it should be pointed out that those skilled in the art will understand that all or any steps or components of the methods and devices of the present invention can be implemented in any computing device (including a processor, storage medium, etc.) or a network of computing devices in the form of hardware, firmware, software, or a combination thereof. This can be achieved by those skilled in the art using their basic circuit design knowledge or basic programming skills after reading the description of the present invention.

[0214] Furthermore, the present invention also provides a program product storing machine-readable instruction codes, which, when read and executed by a machine, can execute the method according to the embodiment of the present invention.

[0215] Accordingly, the storage medium for carrying the program product storing the machine-readable instruction code is also included in the disclosure of the present invention, including but not limited to a floppy disk, an optical disk, a magneto-optical disk, a memory card, a memory stick, and the like.

[0216] When the present invention is implemented through software or firmware, the programs constituting the software are installed from a storage medium or a network to a computer with a dedicated hardware structure (such as the general-purpose computer 2200 shown in Figure 22). When various programs are installed on the computer, it can perform various functions, etc.

[0217] 22 , a central processing unit (CPU) 2201 executes various processes according to a program stored in a read-only memory (ROM) 2202 or a program loaded from a storage section 2208 to a random access memory (RAM) 2203. In the RAM 2203, data required when the CPU 2201 executes various processes, etc., is also stored as needed. The CPU 2201, the ROM 2202, and the RAM 2203 are connected to each other via a bus 2204. An input / output interface 2205 is also connected to the bus 2204.

[0218] The following components are connected to the input / output interface 2205: an input section 2206 (including a keyboard, a mouse, etc.), an output section 2207 (including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.), a storage section 2208 (including a hard disk, etc.), and a communication section 2209 (including a network interface card such as a LAN card, a modem, etc.). The communication section 2209 performs communication processing via a network such as the Internet. A drive 2210 may also be connected to the input / output interface 2205 as needed. A removable medium 2211 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is installed in the drive 2210 as needed, so that a computer program read therefrom is installed in the storage section 2208 as needed.

[0219] In the case where the above-described series of processing is realized by software, a program constituting the software is installed from a network such as the Internet or a storage medium such as the removable medium 2211 .

[0220] It should be understood by those skilled in the art that such storage media is not limited to the removable medium 2211 shown in FIG. 22 , which stores the program and is distributed separately from the device to provide the program to the user. Examples of the removable medium 2211 include magnetic disks (including floppy disks (registered trademark)), optical disks (including compact disk read-only memories (CD-ROMs) and digital versatile disks (DVDs)), magneto-optical disks (including minidiscs (MDs) (registered trademark)), and semiconductor memories. Alternatively, the storage medium may be a ROM 2202, a hard disk included in the storage portion 2208, or the like, in which the program is stored and distributed to the user together with the device containing them.

[0221] It should also be noted that in the apparatus, method, and system of the present invention, each component or step can be decomposed and / or recombined. Such decomposition and / or recombination should be considered equivalent solutions of the present invention. Furthermore, the steps of performing the above series of processes can naturally be performed in chronological order according to the order described, but do not necessarily need to be performed in chronological order. Certain steps can be performed in parallel or independently of each other.

[0222] Finally, it should be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. Furthermore, in the absence of further limitations, an element defined by the phrase "comprises a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0223] Although the embodiments of the present invention have been described in detail above with reference to the accompanying drawings, it should be understood that the embodiments described above are merely illustrative of the present invention and are not intended to limit the present invention. It will be apparent to those skilled in the art that various modifications and variations may be made to the embodiments described above without departing from the spirit and scope of the present invention. Therefore, the scope of the present invention is limited solely by the appended claims and their equivalents.

Claims

1. An electronic device for wireless communication, comprising: The processing circuit is configured to: Sending service information of services that can be provided by the first terminal device to one or more second terminal devices, wherein the service information includes service type information and service feature information; and A data stream of a corresponding service is provided to at least one terminal device among the one or more second terminal devices based on the service information.

2. The electronic device according to claim 1, wherein The processing circuit is configured to send the service information via the PC5 port in at least one transmission mode of broadcast, multicast, and unicast.

3. The electronic device according to claim 1, wherein The service type information indicates the type of service provided by the first terminal device, and the service characteristic information indicates information indicating characteristics of one or more granular services under the service type.

4. The electronic device according to claim 3, wherein The types of services include: perception of specific areas, provision of target information within specific areas, map information services, task information release services, and parameter updates during artificial intelligence / machine learning model deployment or training.

5. The electronic device according to claim 3, wherein The service characteristic information includes one or more of the following: service characteristic identification, service characteristic differentiation information, directional or regional transmission requirements, and relay transmission related information. The electronic device according to claim 5 , wherein: The service characteristic differentiation information includes one or more of the following: a geographical range involved in service data, service source information / sensor information, and map resolution.

7. The electronic device according to claim 5, wherein: The directional or regional transmission requirements include transmission requirements for a specific direction or transmission requirements for a specific area, and the relay transmission related information includes one or more of the following: the transmission range of business data, whether relay transmission is possible, the directional or regional transmission requirements of relay transmission, and the hop limit of relay transmission.

8. The electronic device according to claim 1, wherein The service information also includes a transmission mode of the data flow carrying the service.

9. The electronic device according to claim 1, wherein The processing circuit is further configured to mark data packets in the data flow of the corresponding service based on the service characteristic information before transmission.

10. The electronic device according to claim 9, wherein The processing circuit is configured to mark in one of the following ways: marking a specific field in the header of the data packet at a specific transmission protocol layer included in a transmission protocol stack; modulating the data in the data packet using a modulation method corresponding to the service characteristic information and then transmitting the data packet; and transmitting the data packet within a time period corresponding to the service characteristic information.

11. The electronic device according to claim 1, wherein The processing circuit is further configured to provide affinity information of the first terminal device to the second terminal device, where the affinity information is one or more of geographic location information, mobility information, and path planning information of the first terminal device.

12. The electronic device according to claim 11, wherein The second terminal device is a relay device and is configured to send the data stream to one or more third terminal devices.

13. The electronic device according to claim 12, wherein: The processing circuit is further configured to send a networking request to the second terminal device in response to the service content requirement information from the second terminal device, where the networking request includes the service information and the compatibility information of the first terminal device.

14. An electronic device for wireless communication, comprising: The processing circuit is configured to: receiving, from a second terminal device, service information of a service that can be provided by the second terminal device, wherein the service information includes service type information and service characteristic information; and The service information is included in provision information of a data service that can be provided by the first terminal device and multicast to one or more third terminal devices.

15. The electronic device according to claim 14, wherein The processing circuit is configured to receive the service information via the PC5 port in at least one transmission mode of broadcast, multicast, and unicast.

16. The electronic device according to claim 14, wherein The service type information indicates the type of service provided by the second terminal device, and the service characteristic information indicates information indicating characteristics of one or more granular services under the service type.

17. The electronic device according to claim 16, wherein: The types of services include: perception of specific areas, provision of target information within specific areas, map information services, task information release services, and parameter updates during artificial intelligence / machine learning model deployment or training.

18. The electronic device according to claim 16, wherein: The service characteristic information includes one or more of the following: service characteristic identification, service characteristic differentiation information, directional or regional transmission requirements, relay transmission related information, and service reliability requirements.

19. The electronic device according to claim 18, wherein The service characteristic differentiation information includes one or more of the following: a geographical range involved in service data, service source information / sensor information, and map resolution.

20. The electronic device according to claim 18, wherein The directional or regional transmission requirements include transmission requirements for a specific direction or transmission requirements for a specific area, and the relay transmission related information includes one or more of the following: the transmission range of business data, whether relay transmission is possible, the directional or regional transmission requirements of relay transmission, the hop limit of relay transmission, and business reliability requirements.

21. The electronic device according to claim 20, wherein The processing circuit is configured to include the service information in the provision information and multicast the service information to the one or more third terminal devices if the relay transmission related information indicates that relay transmission is possible.

22. The electronic device according to claim 14, wherein The service information also includes a transmission mode of the data flow carrying the service.

23. The electronic device according to claim 14, wherein The provided information also includes the compatibility information of the first terminal device, and the compatibility information is one or more of the geographic location information, mobility information and path planning information of the first terminal device.

24. The electronic device according to claim 14, wherein The processing circuit is further configured to: receiving a service triggering request from a third terminal device, wherein the service triggering request includes demand information of a service characteristic of the third terminal device; matching the service triggering request with a data service that can be provided by the first terminal device; as well as When the demand information matches the data service that the first terminal device can provide, Provide data services to the third terminal device under certain circumstances.

25. The electronic device according to claim 24, wherein Providing data services to the third terminal device includes one of the following: adding the third terminal device to a subscription group of a data service that completely matches the content being provided by the first terminal device; Adding a data service that meets the needs of the third terminal device and adding the third terminal device to a subscription group of the newly added data service; as well as Establish a unicast data service from the first terminal device to the third terminal device.

26. The electronic device according to claim 24, wherein The service trigger request also includes one or more of the following: QoS requirements for service data transmission, transmission mode type requirements, and affinity information of the third terminal device, wherein the affinity information is one or more of the geographic location information, mobility information, and path planning information of the third terminal device.

27. The electronic device according to claim 14, wherein The first terminal device is in a first mesh network, and the processing circuit is further configured to send service content requirement information to one or more fourth terminal devices outside the first mesh network, and receive a networking request sent by the fourth terminal device in response to the service content requirement information.

28. The electronic device according to claim 27, wherein The networking request includes the phase information of the fourth terminal device, the coverage type provided by the fourth terminal device, and the transmission power or expected transmission distance corresponding to each coverage type; or the networking request includes the service information of the fourth terminal device, The processing circuit is configured to review the networking request or forward the networking request to a central node of the first mesh network for review.

29. The electronic device according to claim 28, wherein The processing circuit is further configured to send network extension confirmation information to the fourth terminal device, where the network extension confirmation information includes a beam direction restriction or recommendation indication.

30. The electronic device according to claim 24, wherein The processing circuit is further configured to perform a beam matching process to determine a beam to use before providing data services.

31. The electronic device according to claim 30, wherein The beam matching process includes selecting a beam that covers the terminal device to be served and avoids covering the terminal device already served by other terminal devices.

32. An electronic device for wireless communication, comprising: The processing circuit is configured to: receiving, from a second terminal device, provision information of a data service that can be provided by the second terminal device, which is sent by the second terminal device via multicast, the provision information including service information of available services, the service information including service type information and service feature information; as well as A service triggering request of the first terminal device is sent to the second terminal device, where the service triggering request includes demand information of the service characteristics of the first terminal device.

33. The electronic device according to claim 32, wherein The service trigger request also includes one or more of the following: QoS requirements for service data transmission, transmission mode type requirements, and affinity information of the first terminal device, wherein the affinity information is one or more of the geographic location information, mobility information, and path planning information of the first terminal device.

34. The electronic device according to claim 32, wherein The processing circuit is further configured to receive confirmation information from the second terminal device, and send feedback to the second terminal device if the transmission mode is unicast.

35. The electronic device according to claim 34, wherein The processing circuit is further configured to perform a beam matching process with the second terminal device before data transmission to determine a beam to be used.

36. An electronic device for wireless communication, comprising: The processing circuit is configured to: performing beam matching for the one or more second terminal devices to select a beam to be used for communication; as well as The communication between the first terminal device and the one or more second terminal devices is performed using the selected beam.

37. The electronic device according to claim 36, wherein The processing circuit is configured to perform beam matching as follows: sending a plurality of beams to the one or more second terminal devices; receiving beam quality reports generated by the one or more second terminal devices based on reception of the multiple beams; as well as One or more beams with the best communication quality are selected based on the beam quality report.

38. The electronic device according to claim 37, wherein The processing circuit is configured to try a wide beam first, and then try a combination of a wide beam and a narrow beam, or a combination of narrow beams, when performing the beam matching.

39. The electronic device according to claim 37, wherein The processing circuit is further configured to avoid interference with existing communications when selecting the beam.

40. The electronic device according to claim 39, wherein The first terminal device is a relay terminal device, and the processing circuit is configured to select a beam whose communication quality for terminal devices served by other terminal devices is lower than a predetermined threshold.

41. The electronic device according to claim 37, wherein The communication quality is indicated by a reference signal reception power or a reference signal reception quality.

42. A method for wireless communication, comprising: Sending service information of services that can be provided by the first terminal device to one or more second terminal devices, wherein the service information includes service type information and service feature information; and A data stream of a corresponding service is provided to at least one terminal device among the one or more second terminal devices based on the service information.

43. A method for wireless communication, comprising: receiving, from a second terminal device, service information of a service that can be provided by the second terminal device, wherein the service information includes service type information and service characteristic information; and The service information is included in provision information of a data service that can be provided by the first terminal device and multicast to one or more third terminal devices.

44. A method for wireless communication, comprising: receiving, from a second terminal device, provision information of a data service that can be provided by the second terminal device, which is sent by the second terminal device via multicast, the provision information including service information of available services, the service information including service type information and service feature information; as well as A service triggering request of the first terminal device is sent to the second terminal device, where the service triggering request includes demand information of the service characteristics of the first terminal device.

45. A method for wireless communication, comprising: performing beam matching for the one or more second terminal devices to select a beam to be used for communication; as well as The communication between the first terminal device and the one or more second terminal devices is performed using the selected beam.

46. ​​A computer-readable storage medium having computer-executable instructions stored thereon, which, when executed by a processor, causes the processor to perform the method for wireless communication according to any one of claims 42 to 45.

Images