Network device, terminal device and data transmission method

Abstract

The application provides a network device, a terminal device and a data transmission method. The method is applied to the network device and includes the following steps: obtaining a plurality of bit streams, different bit streams being for different first devices in a first device set, the first device set including a plurality of first devices; splicing the plurality of bit streams into a multiplexed bit stream; mapping the multiplexed bit stream into a continuous vector; performing semantic coding on the continuous vector to obtain a semantic sequence of the first device set; and sending the semantic sequence to the plurality of first devices in the first device set.

Description

Technical Field

[0001] This application relates to, but is not limited to, the field of communication technology, and in particular to a network device, a terminal device, and a data transmission method. Background Technology

[0002] In multi-user downlink service scenarios, when it is necessary to simultaneously provide image, video, text, or other types of service information to multiple terminals within limited time-frequency resources, how to further improve the resource reuse capability while ensuring the recoverability of the receiving end has become a continuous focus. Related technologies, for multi-user downlink scenarios, do not directly address how to achieve downlink transmission with multiple users sharing the same time-frequency resources, nor do they solve the problem of how each user can recover its own bitstream from the common physical layer signal based on a consistent configuration. Summary of the Invention

[0003] This application provides a network device, a terminal device, and a data transmission method.

[0004] The technical solution of this application embodiment is implemented as follows: This application provides a network device, which includes a first transceiver and... A first processor, coupled to a first transceiver; the first processor is configured to: Multiple bitstreams are obtained, with different bitstreams targeting different first devices in a first device set, which includes multiple first devices. Concatenate multiple bitstreams into a multiplexed bitstream; Map the multiplexed bitstream to a continuous vector; Semantic encoding is performed on continuous vectors to obtain a semantic sequence of the first device set; A semantic sequence is sent to multiple first devices in the first device set via a first transceiver.

[0005] This application provides a terminal device, which includes a second transceiver, and A second processor, coupled to a second transceiver; the second processor is configured to: The terminal device receives a semantic sequence of a first set of devices sent by a network device via a second transceiver; the terminal device is one of a plurality of first devices in the first set of devices. Based on boundary indication information, semantic decoding is performed on the semantic sequence to obtain the continuous vector of the terminal device; The continuous vectors of the terminal device are transformed to obtain the bit stream of the terminal device.

[0006] This application provides a data transmission method applied to a network device, including: Multiple bitstreams are obtained, with different bitstreams targeting different first devices in a first device set, which includes multiple first devices. Concatenate multiple bitstreams into a multiplexed bitstream; Map the multiplexed bitstream to a continuous vector; Semantic encoding is performed on continuous vectors to obtain a semantic sequence of the first device set; Send semantic sequences to multiple first devices in the first device set.

[0007] This application provides a data transmission method applied to a terminal device, including: The terminal device receives a semantic sequence of a first set of devices sent by the network device; the terminal device is one of a plurality of first devices in the first set of devices. Based on boundary indication information, semantic decoding is performed on the semantic sequence to obtain the continuous vector of the terminal device; The continuous vectors of the terminal device are transformed to obtain the bit stream of the terminal device.

[0008] In this embodiment, a network device obtains multiple bitstreams, each targeting a different first device in a first device set, which includes multiple first devices. The multiple bitstreams are concatenated into a multiplexed bitstream. The multiplexed bitstream is mapped into a continuous vector. The continuous vector is semantically encoded to obtain a semantic sequence of the first device set. The semantic sequence is sent to the multiple first devices in the first device set. A terminal device receives the semantic sequence of the first device set sent by the network device. The terminal device is one of the multiple first devices in the first device set. Based on boundary indication information, the semantic sequence is semantically decoded to obtain a continuous vector of the terminal device. The continuous vector of the terminal device is then transformed to obtain the bitstream of the terminal device. Thus, by sending semantic sequences to multiple first devices, multi-user multiplexing in the downlink is achieved, improving data transmission efficiency. Attached Figure Description

[0009] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application.

[0010] Figure 1 This is a schematic diagram of an optional data transmission method provided in an embodiment of this application; Figure 2 This is a schematic diagram of an optional data transmission method provided in an embodiment of this application; Figure 3 This is a schematic flowchart of an optional data transmission method provided in an embodiment of this application. Figure 4This is a schematic diagram of a physical layer joint coding modulation multiple access scheme provided in an embodiment of this application; Figure 5 This is a schematic diagram of an algorithm flow for physical layer joint coding and modulation provided in an embodiment of this application; Figure 6 This is a schematic diagram of a signaling interaction process for physical layer joint coding and modulation provided in an embodiment of this application; Figure 7 This is a schematic diagram of a runtime user set maintenance and re-pairing process provided in an embodiment of this application; Figure 8 This is a schematic diagram of simulation results for the solution and related technical solutions provided in the embodiments of this application; Figure 9 This is a schematic diagram of an optional structure of the device provided in the embodiments of this application. Detailed Implementation

[0011] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application are further described in detail below with reference to the accompanying drawings and embodiments. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0012] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0013] It should be noted that the terms "first, second, and third" used in the embodiments of this application are merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, and third" can be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0014] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which the embodiments of this application pertain. It should also be understood that terms such as those defined in general dictionaries should be understood to have a meaning consistent with their meaning in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined as herein.

[0015] This application provides a network device, a terminal device, and a data transmission method.

[0016] Firstly, embodiments of this application provide a data transmission method applied to network devices, such as... Figure 1 As shown, it includes: S101. Obtain multiple bit streams, with different bit streams targeting different first devices in a first device set, the first device set including multiple first devices; S102. Concatenate multiple bitstreams into a multiplexed bitstream; S103. Map the multiplexed bitstream into a continuous vector; S104. Semantically encode the continuous vectors to obtain the semantic sequence of the first device set; S105, Send a semantic sequence to multiple first devices in the first device set.

[0017] Secondly, embodiments of this application provide a data transmission method applied to a terminal device, such as... Figure 2 As shown, it includes: S201, Receive a semantic sequence of a first set of devices sent by a network device; the terminal device is one of a plurality of first devices in the first set of devices; S202. Based on the boundary indication information, perform semantic decoding on the semantic sequence to obtain the continuous vector of the terminal device; S203. Convert the continuous vector of the terminal device to obtain the bit stream of the terminal device.

[0018] Thirdly, embodiments of this application provide a data transmission method applied to a communication system including network devices and terminal devices, such as... Figure 3 As shown, it includes: S301. The network device obtains multiple bit streams, and the different bit streams are for different first devices in the first device set, which includes multiple first devices. S302. Network devices concatenate multiple bitstreams into a multiplexed bitstream; S303. Network devices map multiplexed bitstreams into continuous vectors; S304. The network device performs semantic encoding on the continuous vector to obtain the semantic sequence of the first set of devices; S305. The network device sends a semantic sequence to multiple first devices in the first device set; S306. The terminal device receives a semantic sequence of a first set of devices sent by the network device; the terminal device is one of a plurality of first devices in the first set of devices; S307. The terminal device performs semantic decoding on the semantic sequence based on the boundary indication information to obtain the continuous vector of the terminal device; S308. The terminal device converts the continuous vector of the terminal device to obtain the bit stream of the terminal device.

[0019] Below, on Figure 1 , Figure 2 or Figure 3 The data transmission method shown is described.

[0020] Here, the first device set includes multiple first devices. The first device set includes multiple first devices involved in this downlink transmission, meaning that multiple first devices receive the same semantic sequence. These multiple first devices are multiple user equipment (UE).

[0021] In this embodiment of the application, the network device acquires data for multiple first devices, performs bearer processing on the data of the multiple first devices respectively, and obtains multiple bit streams, with different bit streams for different first devices.

[0022] Data from multiple first devices can be sent to the network device from the same server, or from multiple servers or data sources; this application does not limit this.

[0023] In some embodiments, the network device may be a base station, and the server sends data of multiple first devices to the core network, and forwards the data of multiple first devices to the base station via the user plane of the core network.

[0024] The network device's data transmission processing for multiple first devices includes at least the following: the network device sequentially performs Packet Data Convergence Protocol (PDCP) encryption, Radio Link Control (RLC) segmentation and reassembly, and Medium Access Control (MAC) multiplexing and scheduling processing along the access layer link.

[0025] In this embodiment of the application, the network device concatenates multiple bit streams into a multiplexed bit stream, maps the multiplexed bit stream into a continuous vector, and performs semantic encoding on the continuous vector to obtain a semantic sequence of the first device set.

[0026] Network devices concatenate multiple bit streams into a multiplexed bit stream according to preset concatenation rules, where the concatenation rules indicate the concatenation order of the multiple bit streams. In some embodiments, multiple bit streams are concatenated into a multiplexed bit stream at the MAC layer.

[0027] Network devices perform bit embedding mapping on multiplexed bit streams, mapping discrete multiplexed bit streams to a continuous vector space, resulting in continuous vectors. In one example, the network device may use embedding techniques to achieve the mapping from discrete multiplexed bit streams to continuous vectors.

[0028] Network devices perform semantic encoding on continuous vectors to obtain semantic sequences, which are specific to multiple first devices in the first device set.

[0029] In some embodiments, multiplexed bitstreams are mapped to continuous vectors at the physical layer; semantic encoding is performed on the continuous vectors to obtain a semantic sequence of the first set of devices.

[0030] In this embodiment, a semantic encoder is used to semantically encode a continuous vector to obtain a continuous vector. In one example, the semantic encoder is a Joint Semantic-Channel Coding and Modulation (JSCCM) encoder.

[0031] The semantic sequence is a complex modulation symbol output by the semantic encoder, which is the signal actually transmitted by the network device.

[0032] In this embodiment of the application, the network device sends a semantic sequence to a plurality of first devices in a first device set; the terminal device (one of the plurality of first devices) receives the semantic sequence of the first device set sent by the network device; according to the boundary indication information, the semantic sequence is semantically decoded to obtain the continuous vector of the terminal device; the continuous vector of the terminal device is converted to obtain the bit stream of the terminal device.

[0033] After performing power normalization, layer mapping, precoding, and resource mapping on the semantic sequence, the network device sends the semantic sequence to multiple first devices through the downlink transmission channel.

[0034] In this embodiment, boundary indication information is used to indicate the boundaries of the bitstreams of multiple first devices in the multiplexed bitstream. The terminal device can decode the continuous vector of the current terminal device from the semantic sequence based on the boundary indication information; the terminal device then transforms the continuous vector of the terminal device to obtain the bitstream of the terminal device.

[0035] In some embodiments, boundary indication information includes the start position and length of the bit stream of a plurality of first devices in a multiplexed bit stream.

[0036] In some embodiments, boundary indication information includes the start and end positions of the bit streams of a plurality of first devices in a multiplexed bit stream.

[0037] In some embodiments, the boundary indication information includes the concatenation order of the bit streams of multiple first devices and the boundary positions of the bit streams of different first devices in the multiplexed bit stream. In one example, the multiple first devices in the first device set include UE1, UE2, and UE3. The boundary indication information indicates that the concatenation order of the multiple first devices is UE1, UE2, and UE3, and the boundary positions of the bit streams of different first devices in the multiplexed bit stream are the 9th bit and the 19th bit. Thus, it can be determined that bits 0 to 9 in the multiplexed bit stream belong to the bit streams of the first devices, bits 10 to 19 belong to the bit streams of the second devices, and bits 20 to 29 belong to the bit streams of the third devices.

[0038] The terminal device hands over its bit stream to the existing protocol link for further processing, which involves at least MAC layer parsing, RLC layer reassembly, and PDCP layer decryption to obtain the terminal device's data content or service output results.

[0039] In this embodiment, a network device obtains multiple bitstreams, each targeting a different first device in a first device set, which includes multiple first devices. The multiple bitstreams are concatenated into a multiplexed bitstream. The multiplexed bitstream is mapped into a continuous vector. The continuous vector is semantically encoded to obtain a semantic sequence of the first device set. The semantic sequence is sent to the multiple first devices in the first device set. A terminal device receives the semantic sequence of the first device set sent by the network device. The terminal device is one of the multiple first devices in the first device set. Based on boundary indication information, the semantic sequence is semantically decoded to obtain a continuous vector of the terminal device. The continuous vector of the terminal device is then transformed to obtain the bitstream of the terminal device. Thus, by sending semantic sequences to multiple first devices, multi-user multiplexing in the downlink is achieved, improving data transmission efficiency.

[0040] In some embodiments, based on Figure 1 The data transmission method shown in this application embodiment further includes: sending a semantic sequence to multiple first devices in the first device set based on a group identifier of the first device set on a first resource.

[0041] Accordingly, based on Figure 2 The data transmission method shown in this application embodiment further includes: receiving a semantic sequence sent by a network device based on a group identifier of a first device set on a first resource.

[0042] Here, the first resource refers to the downlink transmission resource used to transmit semantic sequences.

[0043] The group identifier is used to indicate that multiple first devices in a first device set receive data on the same resource. In one example, the group identifier is a Group Radio Network Temporary Identifier (G-RNTI) or an equivalent group identifier.

[0044] In this embodiment of the application, the network device sends a semantic sequence to multiple first devices in the first device set based on the group identifier of the first device set on the first resource; the terminal device receives the semantic sequence sent by the network device based on the group identifier of the first device set on the first resource.

[0045] Network devices send semantic sequences to multiple first devices via multicast based on group identifiers; terminal devices listen for multicast messages on the first resource based on group identifiers to receive semantic sequences.

[0046] In this embodiment, a semantic sequence is sent to multiple first devices on a first resource according to a group identifier, so that multiple first devices receive the semantic sequence on the same first resource, thereby realizing downlink transmission multiplexing of multiple first devices and improving downlink transmission efficiency.

[0047] In some embodiments, based on Figure 1 The data transmission method shown in this application embodiment further includes: determining scheduling parameters for a first set of devices; the scheduling parameters include at least one of the following: resource information and boundary indication information of a first resource; the boundary indication information is used to indicate the boundary of multiple bit streams in a multiplexed bit stream; and sending the scheduling parameters to multiple first devices in the first set of devices through downlink control information (DCI).

[0048] Accordingly, based on Figure 2 The data transmission method shown in this application embodiment further includes: receiving scheduling parameters of a first set of devices sent by a network device through downlink control information (DCI); the scheduling parameters include at least one of the following: resource information of a first resource and boundary indication information; the boundary indication information is used to indicate the boundary of the bit streams of multiple first devices in the multiplexed bit stream.

[0049] Here, the scheduling parameters are used to indicate the parameters required for this downlink transmission.

[0050] The scheduling parameters include at least one of the following: resource information and boundary indication information of the first resource.

[0051] The resource information of the first resource is used to instruct multiple first devices of the first device set to receive a semantic sequence on the first resource; Boundary indication information is used to indicate the boundaries of the bit streams of multiple first devices in the multiplexed bit stream, so that the multiple first devices can recover the bit stream corresponding to their own device from the semantic sequence according to the boundary indication information.

[0052] In some embodiments, boundary indication information includes the start position and length of the bit stream of a plurality of first devices in a multiplexed bit stream.

[0053] In some embodiments, boundary indication information includes the start and end positions of the bit streams of a plurality of first devices in a multiplexed bit stream.

[0054] In some embodiments, the boundary indication information includes the concatenation order of the bit streams from multiple first devices, and the boundary positions of the bit streams from different first devices in the multiplexed bit stream.

[0055] In this embodiment, the network device determines the scheduling parameters of the first device set and sends the scheduling parameters to multiple first devices in the first device set through the DCI. The DCI is carried by the Physical Downlink Control Channel (PDCCH) and addressed by the group identifier. The terminal device receives the scheduling parameters of the first device set sent by the network device through the DCI based on the group identifier.

[0056] The scheduling parameters also include at least one of the following: the total length of the multiplexed bitstream, the semantic coding rate, and the proportion of the bitstreams of the multiple first devices to the multiplexed bitstream.

[0057] In this embodiment of the application, the network device determines the scheduling parameters of the first set of devices after performing semantic encoding on the continuous vector.

[0058] In some embodiments, the network device sends scheduling parameters to multiple first devices in the first device set during each downlink transmission.

[0059] In some embodiments, if the members of the first device set do not change, the network device sends scheduling parameters to multiple first devices in the first device set. The same scheduling parameters can be reused for multiple downlink transmissions of the first device set in the future, without the need to send scheduling parameters again.

[0060] In this embodiment of the application, the network device sends scheduling parameters to multiple first devices in the first device set, so that the multiple first devices complete the downlink transmission according to the scheduling parameters.

[0061] In some embodiments, based on Figure 1The data transmission method shown in this application embodiment further includes: determining boundary indication information based on the concatenation of multiple bit streams; or, concatenating multiple bit streams into a multiplexed bit stream based on the boundary indication information.

[0062] In this embodiment of the application, when the network device performs downlink transmission for multiple first devices in the first device set, it can determine boundary indication information during each downlink transmission and send the boundary indication information to multiple first devices; the network device can also determine boundary indication information once and only need to send the boundary indication information to multiple first devices once. Subsequent downlink transmissions can reuse the same boundary indication information without sending the boundary indication information again.

[0063] When determining boundary indication information during each downlink transmission, the network device determines the boundary indication information based on the concatenation of multiple bit streams. At this time, the boundary indication information can accurately express the location of the bit streams of multiple first devices in the multiplexed bit stream, and there are no spatial bits in the multiplexed bit stream, nor are there any missing bit values ​​of multiple bit streams.

[0064] When a network device reuses the same boundary indication information in multiple downlink transmissions, it concatenates multiple bit streams into a multiplexed bit stream based on the pre-determined boundary indication information. In this case, there may be idle bits in the multiplexed bit stream. In one example, the boundary indication information indicates that UE1 in the first device set starts at bit 0 in the multiplexed bit stream, with a length of 10 bits. If UE1's bit stream is less than 10 bits, there are idle bits in the bit segment corresponding to UE1 in the multiplexed bit stream.

[0065] In some embodiments, if a network device reuses the same boundary indication information in multiple downlink transmissions, and if the bit stream of the sixth device in the first device set is greater than the length of the bit segment of the sixth device in the reused bit stream indicated by the boundary indication information, the network device will remove the sixth device from the first device set.

[0066] In this embodiment of the application, the network device determines the boundary indication information based on the splicing of multiple bit streams, so that the boundary indication information can accurately express the location of the bit streams of multiple first devices in the multiplexed bit stream; or, by splicing multiple bit streams into a multiplexed bit stream based on the boundary indication information, the number of times the boundary indication information is determined and sent can be reduced, thereby improving the data transmission efficiency.

[0067] In some embodiments, based on Figure 1 The data transmission method shown in this application embodiment further includes: sending a group identifier to a plurality of first devices in a first device set via a first Radio Resource Control (RRC) message.

[0068] Accordingly, based on Figure 2 The data transmission method shown in this application embodiment further includes: receiving a group identifier of a first device set sent by a network device via a first RRC message.

[0069] In this embodiment of the application, the network device sends a group identifier to multiple first devices in the first device set via a first RRC message; the terminal device receives the group identifier sent by the network device via an RRC message.

[0070] In this embodiment of the application, the network device sends a first RRC message to multiple first devices in the first device set. The first RRC message carries a group identifier. The terminal device among the multiple first devices receives the first RRC message, parses the first RRC message to obtain the group identifier, and receives the scheduling parameters and semantic sequence sent by the network device based on the group identifier.

[0071] In this embodiment of the application, the network device sends a group identifier to multiple first devices in the first device set through a first RRC message, so that the multiple first devices can receive semantic sequences on the same resources based on the group identifier, thereby improving the efficiency of downlink transmission.

[0072] In some embodiments, concatenating multiple bit streams into a multiplexed bit stream in S102 includes: concatenating multiple bit streams into a multiplexed bit stream based on concatenation rules.

[0073] In this embodiment of the application, the network device splices multiple bit streams into a multiplexed bit stream according to a preset splicing rule.

[0074] In some embodiments, the splicing rule is used to indicate the splicing order of the bit streams of multiple first devices. In one example, the multiple first devices include UE1, UE2, and UE3, and the splicing rule is used to indicate that the bit streams of UE1, UE2, and UE3 are spliced ​​into a multiplexed bit stream in the order of UE1, UE2, and UE3.

[0075] In some embodiments, splicing rules are used to indicate the splicing positions of the bit streams of multiple first devices. In one example, the multiple first devices include UE1, UE2, and UE3, and the splicing rules are used to indicate that the bit stream of UE1 is spliced ​​in bits 0 to 9, the bit stream of UE2 is spliced ​​in bits 10 to 19, and the bit stream of UE3 is spliced ​​in bits 20 to 29.

[0076] In some embodiments, based on Figure 1 The data transmission method shown in this application embodiment further includes: obtaining target configuration parameters of a first device set, wherein the target configuration parameters include: mapping method identifier and codec identifier; The mapping of multiplexed bit streams to continuous vectors in S103 includes: mapping multiplexed bit streams to continuous vectors based on the mapping method identified by the mapping method identifier; S104 involves semantically encoding continuous vectors to obtain a semantic sequence of the first device set, including: semantically encoding continuous vectors based on the target encoder identified by the codec identifier to obtain a semantic sequence.

[0077] Here, the target configuration parameters refer to the configuration parameters that are commonly supported by multiple first devices in the first device set. The target configuration parameters include: mapping method identifier and codec identifier.

[0078] The codec identifier of the target configuration parameter includes an encoder identifier and multiple decoder identifiers; the multiple decoder identifiers correspond to the target decoders of multiple first devices respectively. In one example, the set of first devices includes UE1, UE2 and UE3, and the codec identifier includes the identifier of the target encoder, the identifier of the target decoder of UE1, the identifier of the target decoder of UE2 and the identifier of the target decoder of UE3.

[0079] In this embodiment of the application, the network device supports the mapping method identified by the mapping method identifier in the target configuration parameters, and multiple first devices all support the demapping method identified by the mapping method identifier in the target configuration parameters; the network device has configured the target encoder identified by the codec identifier in the target configuration parameters, and the multiple first devices are respectively configured with the target decoders of the multiple first devices identified by the codec identifier in the target configuration parameters.

[0080] In this embodiment of the application, the network device obtains the target configuration parameters of the first device set, and maps the multiplexed bit stream into a continuous vector based on the mapping method identifier. Based on the target encoder identified by the codec identifier, the network device performs semantic encoding on the continuous vector to obtain a semantic sequence.

[0081] The target encoder can be a JSCCM encoder, which takes continuous vectors as input and outputs a semantic sequence.

[0082] In this embodiment, the target configuration parameters may further include at least one of the following: output symbol dimension and hard decision threshold. The output symbol dimension represents the dimensional space in which the semantic sequence resides. The hard decision threshold is the decision boundary for multiple first devices in recovering the bitstream.

[0083] In some embodiments, based on Figure 1 The data transmission method shown in this application embodiment further includes: sending target configuration parameters to multiple first devices in the first device set via a second RRC message.

[0084] Accordingly, based on Figure 2 The data transmission method shown in this application embodiment further includes: receiving target configuration parameters of a first device set sent by a network device via a second RRC message; the target configuration parameters include at least: a mapping method identifier and a codec identifier; using the target decoder of the terminal device identified by the codec identifier, semantically decoding the semantic sequence based on boundary indication information to obtain a continuous vector of the terminal device; and converting the continuous vector of the terminal device based on the demapping method identified by the mapping method identifier to obtain a bit stream of the terminal device.

[0085] In this embodiment of the application, the network device sends target configuration parameters to multiple first devices in the first device set via a second RRC message; the terminal device receives the target configuration parameters sent by the network device via a second RRC message; the terminal device determines the target decoder of the terminal device according to the codec identifier; based on the boundary indication information, the target decoder of the terminal device performs semantic decoding on the semantic sequence to obtain the continuous vector of the terminal device; the continuous vector of the terminal device is converted based on the hardware decoding method identified by the mapping method to obtain the bit stream of the terminal device.

[0086] In this embodiment of the application, the target encoder and multiple target decoders identified by the codec identifier are pre-trained jointly. During the joint training process, the multiplexed bitstreams of multiple first devices are used as the input of the target encoder, and the target decoders of multiple first devices are trained with the goal of recovering the bitstream of their own device, thereby improving the accuracy of multiple first devices in recovering the bitstream of their own device.

[0087] In this embodiment of the application, the terminal device determines the position of the terminal device's bit stream in the multiplexed bit stream based on the boundary indication information, and then decodes the corresponding position of the terminal device's bit stream in the semantic sequence to obtain the terminal device's bit stream.

[0088] In this embodiment, the target configuration parameters include at least a mapping method identifier and a codec identifier. The terminal device uses the target decoder identified by the codec identifier to perform semantic decoding on the semantic sequence based on boundary indication information, obtaining a continuous vector of the terminal device. Based on the demapping method identified by the mapping method identifier, the continuous vector of the terminal device is transformed to obtain the bitstream of the terminal device. In this way, the terminal device can accurately recover the bitstream of the terminal device from the semantic sequence through the target configuration parameters.

[0089] In some embodiments, based on Figure 1The data transmission method shown in this application embodiment further includes: receiving data from a plurality of second devices included in the second device set, wherein the data of the second devices is processed by bearer processing to obtain a bit stream of the second devices; determining a first device set and target configuration parameters of the first device set based on the capability information of the plurality of second devices included in the second device set; the first device set includes all or part of the second devices in the second device set; the capability information includes at least one of the following: semantic transmission capability information, a set of supported codec identifiers, a set of supported mapping method identifiers, and group addressing reception capability information.

[0090] Here, the multiple second devices in the second device set refer to user equipment with data to be sent.

[0091] In this embodiment, the network device receives data from multiple second devices, performs bearer processing on the data from each of the multiple second devices, and obtains a bitstream from the multiple second devices. The data from the multiple second devices can be sent to the network device from the same server, or from different servers or information sources.

[0092] In this embodiment of the application, the network device determines a first device set from the multiple second devices based on the capability information of the multiple second devices, and determines the target configuration parameters of the first device set. The first device set includes all or part of the second devices in the second device set; the capability information includes at least one of the following: semantic transmission capability information, a set of supported codec identifiers, a set of supported mapping method identifiers, and group addressing reception capability information.

[0093] In this embodiment of the application, based on the capability information of multiple second devices, a first set of devices is determined from the multiple second devices that supports semantic transmission capability, has matching codec identifiers, matches matching mapping method identifiers, and has group addressing reception capability.

[0094] In one example, the second device includes UE1, UE2, UE3, UE4 and UE5, wherein UE1, UE2, UE3 and UE4 have semantic transmission capabilities, the codec identifiers supported by UE1, UE2 and UE3 include a set of jointly trained decoders, the mapping method identifiers supported by UE1, UE2 and UE3 are the same, and UE1, UE2 and UE3 all support group addressing reception. Therefore, UE1, UE2 and UE3 are determined as the first device set.

[0095] In this embodiment, matching codec identifiers means that the network device and the multiple first device sets each support a set of jointly trained codecs. In one example, the first device set includes UE1, UE2, and UE3. The network device supports encoder 1, UE1 supports decoder 1 and decoder 2, UE2 supports decoder 3 and decoder 4, and UE3 supports decoder 5 and decoder 6. Here, encoder 1, decoder 1, decoder 3, and decoder 5 are a set of jointly trained codecs, so it can be determined that the codec identifiers supported by UE1, UE2, and UE3 match.

[0096] In this embodiment of the application, the network device determines the codec identified by the codec identifier used in this downlink transmission from a plurality of codec identifiers supported by each first device.

[0097] In this embodiment of the application, the network device determines the mapping method and demapping method identified by the mapping method identifier used in this downlink transmission from multiple mapping method identifiers supported by multiple first devices.

[0098] In this embodiment of the application, a first set of devices is determined based on the capability information, quality of service requirements, channel status, and available downlink transmission resources of multiple second devices.

[0099] In this embodiment, the first device set includes all or part of the second devices in the second device set. When the first device set includes some of the second devices in the second device set, the second devices not included in the first device set complete the downlink data transmission using a separate delivery method.

[0100] In some embodiments, if a network device does not receive capability information reported by a fourth device in the first set of devices, it sends a query request to the core network; the core network device then sends the capability information of the fourth device to the network device.

[0101] In this embodiment, a network device receives data from multiple second devices included in a second device set. The data from the second devices undergoes bearer processing to obtain a bitstream of the second devices. Based on the capability information of the multiple second devices included in the second device set, a first device set and target configuration parameters for the first device set are determined. The first device set includes all or some of the second devices in the second device set. The capability information includes at least one of the following: semantic transmission capability information, a set of supported codec identifiers, a set of supported mapping method identifiers, and group addressing reception capability information. Thus, by determining the first device set and its target configuration parameters based on the capability information of the multiple second devices, the multiple first devices in the first device set support downlink transmission multiplexing, improving data transmission efficiency.

[0102] In some embodiments, based on Figure 1 The data transmission method shown in this application embodiment further includes: sending a query request to a plurality of second devices in the second device set; and receiving capability information of the plurality of second devices in the second device set.

[0103] Accordingly, based on Figure 2 The data transmission method shown in this application embodiment further includes: receiving a query request sent by a network device; and sending terminal device capability information to the network device.

[0104] In this embodiment of the application, the terminal device is one of a plurality of second devices. The network device sends a query request to the terminal device; the terminal device receives the query request sent by the network device; sends the terminal device's capability information to the network device; and the network device receives the terminal device's capability information.

[0105] In this embodiment of the application, the network device may obtain the capability information of multiple second devices in advance during the connection establishment, service configuration or codec model configuration stages.

[0106] In some embodiments, based on Figure 1 The data transmission method shown in this application embodiment further includes: when the encoding and decoding configuration information of the first device set meets the joint transmission condition, concatenating multiple bit streams into a multiplexed bit stream; the joint transmission condition is related to at least one of the following: second confirmation information for confirming that the network device is configured with the encoder identified by the codec identifier in the target configuration parameters of the first device set, second confirmation information for confirming that multiple first devices are respectively configured with the decoders of multiple first devices identified by the codec identifier, and third confirmation information for confirming that the codec identified by the codec identifier is available; the encoding and decoding configuration information is used to indicate whether the codec of the first target set has been configured.

[0107] In this embodiment of the application, before splicing multiple bit streams, the network device determines whether the encoding and decoding configuration information of the first device set meets the joint transmission conditions.

[0108] In this embodiment of the application, when the network device determines that the encoder-decoder configuration information of the first device set satisfies the joint transmission condition, and that the network device is configured with an encoder identified by the encoder-decoder in the target configuration parameters and the encoder is available, and that multiple first devices are respectively configured with decoders of multiple first devices identified by the encoder-decoder identifier and the decoders of multiple first devices are available, the network device determines that the encoder-decoder configuration information of the first device set satisfies the joint transmission condition.

[0109] In this embodiment of the application, before splicing multiple bit streams, the network device also needs to confirm that the group identifier of the first device set is configured successfully.

[0110] In this embodiment of the application, when the network device confirms that the encoding and decoding configuration information of the first device set does not meet the joint transmission conditions, it sends the bit streams of the multiple first devices to the multiple first devices respectively.

[0111] In this embodiment, multiple bitstreams are concatenated into a multiplexed bitstream only when the encoding / decoding configuration information of the first device set meets the joint transmission conditions. In this way, after the network device sends a semantic sequence for the first device set, the multiple first devices can accurately recover their own data.

[0112] In some embodiments, based on Figure 1 The data transmission method shown in this application embodiment further includes: adding the third device to the first device set if the codec identifier supported by the third device in the first device set matches the target configuration parameters of the first device set.

[0113] In this embodiment, when selecting a third device to be added to the first device set, it is determined whether the codec identifier supported by the third device matches the target configuration parameters of the first device set. If it is determined that the codec identifier supported by the third device matches the target configuration parameters of the first device set, the third device is added to the first device set, and the decoder identifier matching the target configuration parameters of the first device set is updated to the target configuration parameters. In one example, the codec identifiers supported by the third device include encoder 1, decoder 2, and decoder 3, and the codec identifiers in the target configuration parameters include encoder 1, decoder 4, and decoder 5. Encoder 1, decoder 2, decoder 3, and decoder 4 are a set of jointly trained codecs, so the third device can be added to the first device set, and the decoder identifier of decoder 2 is updated to the target configuration parameters of the first device set.

[0114] In this embodiment of the application, after the network device adds the third device to the first device set, it sends the target configuration parameters of the decoder identifier of the added third device to the multiple first devices in the first device set.

[0115] In this embodiment of the application, after the network device adds the third device to the first device set, it sends the group identifier to the multiple first devices in the first device set.

[0116] In this embodiment of the application, when a network device determines that a fifth device has left the first device set, it sends a semantic sequence to the first devices in the first device set on a first resource. In one example, the first device set includes UE1, UE2, UE3, and UE4. When it is determined that UE4 has left the first device set, the first device set now includes UE1, UE2, and UE3. The network device then sends a semantic sequence to UE1, UE2, and UE3 on the first resource.

[0117] In this embodiment, if the codec identifier supported by a third device in the first device set matches the target configuration parameters of the first device set, the third device is added to the first device set. This further improves data transmission efficiency by promptly adding devices whose target configuration identifiers match those of the first device set.

[0118] In some embodiments, transforming the continuous vector of the terminal device in S103 to obtain the bit stream of the terminal device includes: demapping the continuous vector of the terminal device to obtain bit soft decision information; and determining the bit stream of the terminal device based on the bit soft decision information.

[0119] In this embodiment, the terminal device uses a neural network model to demap the terminal device to obtain bit soft decision information. The bit soft decision information can be the probability value of each bit being between 0 and 1, or it can be used to represent the confidence level of each bit, where the confidence level represents the probability of the corresponding bit being 0 or 1.

[0120] In this embodiment, the value of each bit in the bitstream of the terminal device is determined based on bit soft decision information and hard decision threshold. In one example, the bit soft decision information represents a probability of the first bit being between 0 and 1 of 0.85, and the hard decision threshold is 0.6, therefore the final value of the first bit can be determined to be 1.

[0121] In this embodiment, the terminal device demaps its continuous vectors to obtain bit soft decision information; based on the bit soft decision information, it determines the bit stream of the terminal device. In this way, the terminal device can more accurately recover its bit stream using the bit soft decision information.

[0122] The following describes the application of the embodiments of this application in a real-world scenario.

[0123] With the continuous growth of various information services and the increasing demand for multi-user concurrent transmission, communication methods relying on orthogonal resource allocation and bit-level error-free transmission are gradually becoming insufficient to simultaneously meet the requirements of resource utilization efficiency and service semantic expression capabilities. Especially in multi-user downlink service scenarios, when it is necessary to simultaneously provide image, video, text, or other types of service information to multiple terminals within limited time-frequency resources, how to further improve the resource reuse capability while ensuring receiver recoverability has become a continuous focus of 6G. To reduce the amount of data transmitted for service information and improve the utilization efficiency under limited channel resources, related technologies have begun to combine semantic coding, source-channel joint coding, and multiple access transmission mechanisms to support the efficient transmission of multi-user service information.

[0124] To improve spectrum utilization efficiency under multi-user shared channel conditions, related technology 1 introduces a non-orthogonal multiple access (NOA) method for service information transmission based on semantic coding and semantic decomposition. Related technology 1 addresses scenarios where a transmitter transmits a first quantity of similar service information to a receiver. The transmitter converts the service information into semantic code, dividing it into multiple sets of common and unique parts. These common and unique parts are then transmitted to the receiver using NOA. The receiver combines the received common and unique parts to obtain a second semantic code, which is further decoded into the corresponding service information. Related technology 1 combines semantic coding, semantic decomposition, and NOA transmission, enabling service information to be compressed and organized at the semantic layer and transmitted more efficiently under shared channel conditions, thereby further improving the transmission efficiency of information services.

[0125] Furthermore, related technology 2 proposes a method for a base station to transmit service information of the same category to a first number of user equipments. The base station converts the service information to be transmitted into semantic code, further decomposes it into common and individual parts, and then sends the common and individual parts to the user equipment. The user equipment combines the received common and individual parts to obtain a second semantic code, and further decodes it to recover the service information. Simultaneously, this technology also provides implementation methods such as selecting one from multiple common information for transmission, fusing two or more common information before transmission, and transmitting the first number of individual parts on different time-frequency resources. This provides a clearer implementation path for multi-user downlink transmission after semantic decomposition and further improves the transmission efficiency of service information of the same category.

[0126] Furthermore, from the perspective of semantic data and physical layer transport adaptation, related technology 3 proposes a semantic image data transmission scheme. This scheme targets semantically encoded image or video frames, dividing the semantic feature data related to the semantically encoded image or video frame into multiple parts according to the modulation and coding scheme and resource allocation, and carrying the corresponding semantic feature data through transport blocks. In some implementations, the transport block can also contain compressed feature probability data corresponding to the encoded image data. Related transmission can be completed through physical channels such as PUSCH, PDSCH, or PSSCH, and can be scheduled by the control channel. This scheme demonstrates that the combination of semantic data with physical layer resource allocation, modulation and coding scheme, transport block transport, and physical channel scheduling has begun to receive attention, but its focus remains on the block transport and transmission of semantic image or video data, and it does not directly address the same-resource physical layer semantic multiple access transmission of multi-user transport bitstreams.

[0127] However, while related technology 1 introduces a non-orthogonal multiple access method to transmit multiple sets of common and individual parts obtained from semantic coding, and the receiving end then combines and restores the received common and individual parts, it still revolves around the splitting and restoration of common and individual parts. Furthermore, in non-orthogonal multiple access scenarios, the receiving end typically needs to perform more complex restoration processing for superimposed transmission conditions. When facing multi-user downlink services in existing mobile communication systems, this method is quite sensitive to user relationships, consistency of the restoration process, and the complexity of the receiving end implementation. Simultaneously, when service data needs to undergo subsequent protocol processing in the existing bearer link, relying solely on the semantic splitting and non-orthogonal transmission method described in related technology 1 is still insufficient to fully cover the requirements for unified network-side organization, consistent terminal-side configuration, and stable separation and restoration at the receiving end in downlink transmission using the same time-frequency resources for multiple users.

[0128] Related technology 2 presents a downlink scheme for a base station to transmit the same type of service information to a first number of user equipments. This scheme converts the service information to be transmitted into semantic code, then splits it into common and individual parts, which are transmitted by the base station to each user equipment. The user equipment then combines the common and individual parts to recover the service information. While this expands the application scenario to the downlink, its implementation still relies on the existence of a reliably extractable common semantic part between different user services and the receiver's combination and recovery of the common and individual parts. When the service content of the target users differs significantly, or when the content to be transmitted to different users lacks a clear common structure, the construction of the common and individual parts and the receiver's combination and recovery process become more complex, thus affecting the stability of multi-user transmission. Furthermore, this existing technology also includes a method of transmitting the first number of individual parts on different time-frequency resources, indicating that its focus remains on splitting the common and individual parts and transmitting them separately. For scenarios where multiple terminals receive the same downlink data on the same time-frequency resource and recover their corresponding data or service output results, a more direct implementation path is still lacking.

[0129] While related technology 3 further involves the adaptation relationship between semantic feature data and physical layer resource configuration, modulation and coding schemes, transport block carrying, and physical channel scheduling, its focus remains on the block carrying and transmission of semantic image or video data. This scheme focuses on how to divide the semantically encoded image or video frame-related feature data into multiple parts and carry these parts through transport blocks and corresponding physical channels. Its processing objects are mainly semantic feature data or probability data related to semantic features, rather than the separate bearer bitstreams formed for multiple users in the current bearer link. For multi-user downlink scenarios, this scheme does not directly provide how multiple user bearer bitstreams are multiplexed at the MAC side, nor does it provide how to perform joint coding and modulation on the multiplexed bitstream at the physical layer to generate the same downlink physical layer signal, and it does not solve the problem of how each user terminal recovers its own bearer bitstream from the common physical layer signal based on a consistent configuration. Therefore, although the aforementioned existing technologies have improved information transmission efficiency from the perspectives of semantic decomposition and non-orthogonal multiplexing, downlink semantic decomposition transmission, and semantic data physical layer carrying, they still have shortcomings in how to achieve downlink transmission with multiple users sharing the same time-frequency resources under the current mobile communication standard system, and how to enable multiple users' bearer bit streams to be jointly organized, uniformly transmitted at the physical layer, and restored separately on the user side while maintaining the independent processing of each user's upper-layer bearer link.

[0130] Based on the above description, this application provides a multi-user multiple access transmission method for the 3GPP standard system, used to realize multiplexed transmission of multiple users on the same time-frequency resources in the downlink and restore their respective data at each user terminal. On the one hand, addressing the problem that existing downlink multi-user transmission mainly relies on the orthogonality of time-frequency resources and spatial domain orthogonality, which limits the efficiency of multiplexing on the same resource, this application provides an implementation path for carrying multi-user data on the same resource. On the other hand, addressing the problem that multi-user services are usually processed and transmitted separately as independent data streams in the current bearer links, resulting in limited efficiency of joint transmission, this application provides a feasible multiple access scheme that maintains independent processing of each user's upper-layer bearer link and completes joint organization and a single downlink transmission at the lower layer.

[0131] The physical layer joint coding modulation multiple access scheme proposed in this application, which can be implemented under the 3GPP standard system, is used to realize multiplexed downlink transmission of multiple users on the same time-frequency resources, and to recover their respective data at the terminal side. Figure 4 As shown, this scheme maintains the upper-layer bearer link unchanged. Different user data forms their own bearer bitstreams (corresponding to the bitstreams in the previous embodiments). The MAC layer concatenates the multiple bearer bitstreams into a multiplexed bitstream. After entering the PHY, the multiplexed bitstream is converted into a continuous vector representation suitable for neural network processing through bit embedding mapping. This representation is then input into the JSCCM encoder 401, which directly performs joint coding and modulation mapping from the continuous vector representation to complex transmitted symbols. The transmitting end sends complex transmitted symbols to the receiving end through wireless channel 402. After receiving the physical layer received symbols, the receiving end inputs them into the user-side JSCCM decoder matching the JSCCM configuration parameters (in the case of UE1, the received symbols are input to JSCCM decoder 1; in the case of UE2, the received symbols are input to JSCCM decoder 2). Bit embedding demapping yields the soft decision information for the user's bit segment, and hard decision is used to recover the user's bearer bitstream. This allows multiple users to receive the same physical layer signal on the same time-frequency resource and recover their respective data. This application primarily utilizes the learning-based representation and recovery capabilities of the physical layer JSCCM for the carrying bit stream. Unlike the separate channel coding, constellation modulation, and demodulation decision processes in the physical layer of related technologies, JSCCM converts discrete bits into continuous vector representations through bit embedding mapping, and an end-to-end model learns the correspondence between input bits, complex transmitted symbols, and the recovered bit results at the receiving end. Therefore, physical layer symbols no longer merely represent bit mapping relationships at fixed constellation points (variable soft-decision information), but rather embody the characteristics of semantic communication oriented towards information recovery quality rather than simply error-free symbol transmission.

[0132] The physical layer joint coding modulation multiple access scheme provided in the embodiments of this application, such as Figure 4As shown, the design follows the principles of independent bearer links, MAC-side bitstream concatenation, physical layer joint coding and modulation, and single downlink transmission. Data for different users is processed along the existing 3GPP bearer links to form their own bearer bitstreams. The MAC layer concatenates multiple bearer bitstreams according to predetermined rules to form a multiplexed bitstream. At the PHY layer, the multiplexed bitstream first undergoes bit embedding mapping to convert discrete bits into a continuous vector representation that can be processed by the JSCCM model; subsequently, the JSCCM encoder performs end-to-end joint coding and modulation on this continuous vector representation, outputting a complex transmitted symbol sequence. After each receiving user receives the same physical layer signal, it calls the user-side JSCCM decoder that matches the JSCCM configuration parameters. This decoder decodes the received symbol sequence, obtains the soft decision information of the corresponding bit segment for the user through bit embedding demapping, and then obtains the user's bearer bitstream through hard decision. Subsequently, the user's bearer bitstream returns to the existing protocol link for further processing and restores the user's data content or service output results. Through the above processing, JSCCM jointly models the representation of multi-user bitstreams, wireless channel adaptation, and receiver recovery objectives at the physical layer. This enables multi-user data transmission on the same resource to no longer rely solely on fixed modulation constellations and power domains for differentiation. Instead, it achieves semantic transmission at the physical layer, oriented towards recovery performance, through learned joint coding and modulation. The separable recovery of multiple users depends on the predetermined user concatenation order, user boundary information, and consistent JSCCM configuration parameters between both parties.

[0133] In this embodiment of the application, the processing procedure of the network device is as follows: (1) The sending end obtains source data for different users and completes bearer processing according to the current 3GPP protocol stack to form the bearer bit stream corresponding to each user. The bearer processing includes at least PDCP encryption, RLC segmentation and reassembly, and MAC side processing.

[0134] (2) The MAC layer organizes the bearer bit streams of multiple users and splices them together according to preset splicing rules to generate a multiplexed bit stream. User boundary information (corresponding to the boundary indication information in the aforementioned embodiments) is used to indicate the start and end positions or length information of each user bit segment in the multiplexed bit stream.

[0135] After the base station completes the splicing of multiple user bearer bitstreams on the MAC side, it can set the user boundary information as the header or boundary indicator field of the multiplexed bitstream, and enter the PHY side bit embedding mapping and JSCCM encoding together with the multiple user bearer bitstreams. Finally, it is carried in the same PDSCH downlink transmit symbol sequence and sent to each user equipment.

[0136] User boundary information is used to indicate the start and end positions or length of each user bit segment in the multiplexed bit stream. When the receiving end recovers the data, it uses the user boundary information to determine which bit segment belongs to the user.

[0137] User boundary information can be determined according to user boundary rules, such as concatenating them sequentially according to a predetermined user order, dividing them according to a fixed ratio, or determining the boundary according to the length of each user bit segment indicated by the DCI.

[0138] In some embodiments, the base station generates user boundary information after determining the length or proportion of the bit segments to be transmitted by each user.

[0139] (3) The PHY layer performs bit embedding mapping on the multiplexed bit stream (using embedding technology to map to the vector space), converting discrete bits into a continuous vector representation. This continuous vector representation is used as the input of the JSCCM encoder.

[0140] (4) The PHY layer inputs the bit embedding mapping result into the JSCCM encoder (the joint encoder and the decoders of multiple users are trained simultaneously) for joint coding modulation mapping to generate downlink complex transmission symbol sequence (corresponding to the semantic sequence in the aforementioned embodiment).

[0141] (5) The PHY layer performs power normalization, layer mapping, precoding and resource mapping on the downlink complex transmission symbol sequence, and transmits the downlink complex transmission symbol sequence in the downlink direction.

[0142] In this embodiment of the application, the processing procedure of the receiving end is as follows: (1) Each receiving user receives the downlink complex transmission symbol sequence on the same time-frequency resource and obtains the physical layer received signal.

[0143] (2) After the receiver obtains the downlink complex transmission symbol sequence at the physical layer, it inputs the downlink complex transmission symbol sequence into the user-side JSCCM decoder that matches the JSCCM configuration parameters.

[0144] (3) The user-side JSCCM decoder decodes the downlink complex transmission symbol sequence, obtains the bit soft decision information of the corresponding bit segment of the user through bit embedding demapping, and obtains the bearer bit stream of the user through hard decision. For other user bit segments that do not belong to the user, the receiver regards them as interference information in the decoding process and suppresses them through the user-side JSCCM decoder obtained by end-to-end training.

[0145] The output of bit embedding demapping is bit soft decision information. This soft decision information can be a probability value between 0 and 1, or it can be a logit (logistic probability) or a confidence level, used to represent the probability of the corresponding bit being 0 or 1. Since the bit soft decision information is the probability, confidence level, or logit value of each bit being 0 or 1, this information is not the final 0 / 1 hard bit. The receiving end needs to further map the probability value to 0 or 1 through hard decision to obtain the user's bearer bit stream.

[0146] In this embodiment, the transmitting JSCCM encoder and each receiving user-side JSCCM decoder are jointly trained in advance. During training, the transmitting JSCCM encoder receives a multiplexed bitstream concatenated from multiple user bearer bitstreams, and each user-side JSCCM decoder is trained with the goal of recovering its own user bearer bitstream. Therefore, for a given user-side JSCCM decoder, its own user bitstream is the target information to be recovered, while other user bitstreams are non-target information, thus being learned as interference information to be suppressed during decoding. In other words, the receiving end does not rely on a regular decoder to temporarily determine which bits are interference, but rather relies on the pre-trained user-side JSCCM decoders, whose model mapping already reflects the ability to recover its own user information and suppress other user information.

[0147] In this embodiment, the receiving end uses a JSCCM decoder to decode the downlink complex transmission symbol sequence based on user boundary information to obtain the continuous vector of the current user.

[0148] (4) The receiving end will hand over the user's bearer bit stream to the existing protocol link for further processing, including at least MAC parsing, RLC reassembly and PDCP decryption, and finally restore the user's data content or service output results.

[0149] In this embodiment of the application, the algorithm flow is as follows: Figure 5 As shown, the steps include S501 to S511 as follows: Step S501: Business generation; Step S502: The core network sends multi-user data to the gNB; Step S503: The base station performs bearer processing on the data from multiple users and outputs it to the MAC layer; The base station receives data from multiple users in the core network. The base station processes the data of different users along the existing bearer links and forms the bearer bit streams of each user until the MAC output is completed.

[0150] Step S504: The base station determines whether the JSCCM configuration parameters have been configured. If yes, proceed to step S506; otherwise, proceed to step S505. The base station can determine whether the JSCCM configuration parameters are ready based on whether the JSCCM configuration parameters are configured or confirmed, whether the PHY-side JSCCM encoder is available, whether the UE-side is configured with a matching user-side JSCCM decoder, and whether the G-RNTI or equivalent group addressing configuration is valid, thereby determining whether the JSCCM configuration parameters meet the joint transmission conditions.

[0151] Once the JSCCM configuration parameters are determined to meet the joint transmission conditions, the MAC layer performs the splicing of multi-user bearer bit streams according to the splicing rules and determines the user boundary information.

[0152] The MAC layer concatenates the bearer bitstreams of multiple users into a multiplexed bitstream according to predetermined concatenation rules. This refers to the arrangement order of the multiple user bearer bitstreams when forming the multiplexed bitstream on the MAC side, for example, placing the bit segment of UE1 first, then placing the bit segment of UE2. User boundary information is then written according to the order and data length.

[0153] If the JSCCM configuration parameters do not meet the conditions for joint transmission, the system degrades to regular multiple access distribution, where the base station sends bit streams from multiple users to multiple users respectively.

[0154] Step S505: Degradation of conventional multiple access is issued; Step S506: The MAC layer of the base station splices the multiplexed bit stream according to the splicing rules; Step S507: The physical layer of the base station performs bit embedding mapping and joint encoding with JSCCM; The PHY first performs bit embedding mapping on the multiplexed bit stream, converting discrete bits into a continuous vector representation; then, the PHY inputs this continuous vector representation into the JSCCM encoder, which directly generates a sequence of complex transmission symbols.

[0155] Step S508: The physical layer of the base station performs downlink transmission on the same resource; The base station sends a complex sequence of transmission symbols to multiple users on the same resource.

[0156] Step S509: The receiving end performs JSCCM decoding, demapping, and hard decision to recover the user's bitstream; Multiple users receive the same complex transmission symbol sequence, call the matching user-side JSCCM decoder, obtain the bit soft decision information of the user's bit segment through bit embedding demapping, and then recover the user's bearer bit stream through hard decision. Subsequently, the processing continues according to the current protocol link to recover the user's service data.

[0157] Step S510: The receiver returns to the protocol stack and sends back HARQ (Hybrid Automatic Repeat Request). Step S511: Business completed.

[0158] In this embodiment of the application, the signaling interaction is as follows: Figure 6 As shown, the steps include S601 to S608 as follows: Step S601: The base station sends a query message to UE1 to obtain the capability information of UE1; The base station obtains capability information from the UE and stores it on the base station side to determine the set of JSCCM configuration parameters supported by the UE; if the base station does not receive capability information of some UEs before this multi-user joint transmission, the base station can also query again.

[0159] Capability information may include whether the UE supports semantic transmission, the set of JSCCM configuration parameters supported by the UE, and whether the UE supports G-RNTI or equivalent group addressing reception.

[0160] Step S602: UE1 sends its capability information to the base station; Step S603: The base station sends a query message to UE2 to obtain UE2's capability information; Step S604: UE2 sends its capability information to the base station; Step S605: The base station sends JSCCM configuration parameters and group identifier to UE1 via RRC message; JSCCM configuration parameters represent the configuration identifiers corresponding to the set of parameters used, such as the bit mapping method, JSCCM encoder and user-side JSCCM decoder configuration, output complex symbol dimension, and hard decision threshold.

[0161] After receiving data from multiple users to be transmitted, the base station can first form a candidate UE set. The base station then combines the JSCCM configuration parameter set supported by multiple candidate UEs in the candidate UE set (corresponding to the second device set in the aforementioned embodiment), service quality requirements, channel state, available PDSCH resources, and scheduling requirements to determine the target UE set for this same-resource downlink transmission (corresponding to the first device set in the aforementioned embodiment), and the JSCCM configuration parameters to be used for this downlink transmission for the target UE set. The target UE set is the set of UEs involved in this same-resource downlink transmission.

[0162] After receiving the capability information reported by the UE, the base station determines the JSCCM codec model matching relationship corresponding to the target UE set based on the set of JSCCM configuration parameters supported by each UE in the target UE set and the scheduling requirements for this operation, and selects the JSCCM configuration parameters to be used in this operation. In one implementation, the base station may also request the JSCCM configuration parameter information supported by the UE (i.e., the UE's capability information) from the core network.

[0163] The JSCCM codec model matching relationship refers to the matching relationship between the transmitting JSCCM encoder and the JSCCM decoders on each UE side in the target UE set. For example, the transmitting JSCCM encoder E can be pre-trained jointly with decoder A on UE1 and decoder B on UE2 to form a set of codec model combinations that can be used for joint transmission and separate recovery within the same resource. Therefore, when decoder A is assigned to UE1, decoder B should also be assigned to UE2. This model matching relationship can be characterized by the codec identifier in the JSCCM configuration parameters.

[0164] In this embodiment, the capability information reported by the UE includes the set of JSCCM configuration parameters supported by the UE. When the sets of JSCCM configuration parameters supported by multiple UEs are inconsistent, the JSCCM configuration parameters used in this application are not based on any single UE, but rather on JSCCM configuration parameters that are supported or configured by all UEs in the target UE set. If there are no commonly available JSCCM configuration parameters, the base station can adjust the members in the target UE set, redetermine the JSCCM configuration parameters, or revert to the conventional downlink transmission method.

[0165] The JSCCM configuration parameters used in this study include the JSCCM encoder identifier or version on the transmitting end, the JSCCM decoder identifier or version on the user side, the bit embedding mapping or demapping method, the output complex symbol dimension, and the hard decision threshold.

[0166] The base station sends RRC reconfiguration or equivalent control signaling (including G-RNTI identifier and JSCCM configuration parameters used this time) to the target UE set to configure or activate the JSCCM configuration parameters used this time and the G-RNTI or equivalent group addressing identifier.

[0167] Step S606: The base station sends JSCCM configuration parameters and group identifier to UE2 via RRC message; Step S607: The base station sends scheduling parameters to UE1 via PDCCH; The base station sends scheduling parameters for this operation to multiple users. The scheduling parameters may include at least one of the following: total length of the multiplexed bit stream, length or proportion of each user's bit segment, JSCM coding rate, and time-frequency resource configuration.

[0168] Step S608: The base station sends scheduling parameters to UE2 via PDCCH.

[0169] After configuration, the base station issues a shared resource scheduling instruction to the target UE set and allocates PDSCH resources, enabling the target UE set to receive one downlink transmission on the same time-frequency resource and complete JSCCM decoding and user bearer recovery in the PHY. The shared resource scheduling instruction uses G-RNTI for group addressing, ensuring that UEs within the set receive the same scheduling instruction on the same resource. After the JSCCM Profile has been configured or activated, the gNB determines the scheduling parameters for this operation period based on the target UE set, the length of the bearer bitstream to be transmitted by each user, available PDSCH resources, channel quality, and target bit error rate requirements. The operation period scheduling parameters include the total length of the multiplexed bitstream, the length or proportion of each user's bit segment, the JSCCM coding rate, user boundary information, and time-frequency resource configuration. Specifically, the network side can first determine the total length of the multiplexed bitstream that can be carried based on the available PDSCH resources and target recovery performance, and then determine the length or proportion of each user's bit segment based on the amount of data to be transmitted by each user, channel status, or service continuity requirements, and confirm that the above operation period scheduling parameters do not exceed the supported range of the configured or activated JSCCM configuration parameter set. The above scheduling results can be determined by RRC pre-configuration, the JSCCM configuration parameters used in this study, and DCI dynamic indication, so that the physical layer joint coding and modulation process is adapted to the actual radio resource allocation process.

[0170] After receiving a DCI addressed using G-RNTI or equivalent group addressing identifier, the target UE set enters the same resource reception state according to the PDSCH resources, bit segment length or ratio indicated by the DCI, and the JSCCM configuration parameters used this time. Each UE selects a matching user-side JSCCM decoder according to its locally configured JSCCM configuration parameters, and determines the bit segment recovery position corresponding to its user according to the user splicing order and user boundary rules, thereby ensuring that the same physical layer received signal can be recovered into the corresponding user bearer bit stream on different UE sides.

[0171] In this embodiment, the multiplexed bitstream is formed by splicing multiple users' bearer bitstreams according to predetermined splicing rules. The receiving end recovers the bearer bitstream of its own user based on the JSCCM configuration parameters, user splicing order, and user boundary information used in this application. To ensure consistency in user-side recovery, when a participating user leaves or is replaced, the network side first stops the same-resource multiplexing transmission involving the departing user and uses single-user downlink transmission for the remaining users to ensure service continuity. If it is necessary to continue using the same-resource multiplexing method, the network side can first form an updated set of participating users based on the remaining users; when the remaining users still meet the configured or available JSCCM Profile, user boundary rules, and resource conditions, they can directly continue same-resource multiplexing downlink transmission; when the remaining users do not meet the conditions or need to be supplemented, new candidate users are selected to form a new set of participating users, and the participation relationship, user splicing order, and user boundary rules of the multiplexed bitstream are updated. At the same time, the matching JSCCM configuration parameters and necessary parameters are sent or confirmed. After confirmation, same-resource multiplexing downlink transmission is resumed. Figure 7 As shown, the target UE set includes UE1 and UE2. When UE2 leaves the target UE set and UE3 meets the configured or available JSCCM configuration parameters, user boundary rules and resource conditions, UE3 is added to the target UE set, and UE1 and UE3 are distributed with the same resources.

[0172] This application addresses the semantic multiple access requirements of mobile communication downlink by proposing a multi-user co-resource multiplexing downlink transmission path based on physical layer joint coding and modulation. This enables multiple user services to perform joint multiplexing downlink transmission under the same radio resource conditions, and recover the corresponding data content or service output results at their respective receivers. Compared to related technologies that mainly rely on time-frequency orthogonality and spatial orthogonality for multiplexing, and power domain superposition-based multiplexing methods, this application introduces a joint organization and joint coding and modulation mechanism for multi-user bearer bitstreams within the 3GPP standard framework. This allows the network side to complete multi-user co-resource multiplexing while maintaining existing bearer and security processing mechanisms, and provides joint transmission capabilities for end-to-end recovery of service data. This improves the efficiency of multi-user concurrent transmission and enhances the reception stability and end-to-end recovery quality under co-resource multiplexing conditions.

[0173] The simulation results of this application's solution and related technical solutions are as follows: Figure 8As shown in the figure, the horizontal axis represents the signal-to-noise ratio (SNR), and the vertical axis represents the bit error rate (BER). The blue and yellow curves represent the BER of two multiple access users under the NOMA scheme, while the green and red curves represent the BER of two multiple access users under the MDMA scheme. The simulation results show that, across the entire SNR range, the BER of both users under the second scheme (the scheme in this application) is significantly lower than that of the first scheme (related technical schemes), indicating that the physical layer joint coding modulation multiple access mechanism proposed in this application can achieve better bit recovery performance under the same time-frequency resource sharing conditions. In particular, compared to the significant performance differentiation between User1 and User2 in the first scheme, the second scheme not only has a lower overall BER, but also exhibits more balanced performance between the two users, demonstrating better user separation capability, transmission stability, and system robustness. Therefore, the simulation results verify the significant advantages of the scheme in this application compared to power domain-differentiated transmission methods in multi-user downlink transmission scenarios with shared resources.

[0174] In this embodiment, under high cell load conditions, the base station needs to simultaneously deliver different services to multiple users within limited resources. For example, UE1 receives video clips or image data, while UE2 receives files, text messages, or model parameters. These services are still processed at the upper layer according to existing protocol links and form bearer bitstreams. This application does not limit the type of upper-layer service, but instead uses JSCCM configuration parameters at the physical layer to perform learning-based joint coding and modulation on the multi-user bearer bitstreams, enabling physical layer symbols to simultaneously carry the multi-user data recovery target. Related technologies typically require allocating orthogonal time-frequency resources to different users, or employing power domain superposition and performing complex recovery at the receiving end. This application, while maintaining independent processing of the upper-layer bearer links for each user, has the network side complete the joint organization of the multi-user bearer bitstreams, JSCCM joint coding and modulation, and single downlink transmission with the same resources at the physical layer, including the following processes: (1) The network side obtains the data to be transmitted from UE1 and UE2, and processes them according to the existing PDCP, RLC and MAC to form their respective bearer bit streams. (2) The base station determines the target UE set, the total length of the multiplexed bit stream, the user splicing order, the length or proportion of each user bit segment and the JSCCM coding rate for this joint transmission based on the length of the bearer bit stream to be transmitted from UE1 and UE2, the available PDSCH resources, the channel quality, the target bit error rate requirement and the set of JSCCM configuration parameters supported by the UE. (3) The base station pre-configures or confirms the JSCCM configuration parameters through RRC, and indicates the scheduling information such as the PDSCH resources, bit segment length or proportion, JSCCM configuration parameters or pre-configured index used for this same resource transmission to the target UE set through DCI addressed by G-RNTI or equivalent group addressing identifier. (4) The MAC layer splices the bearer bit streams of UE1 and UE2 into a multiplexed bit stream according to the predetermined user order and determines the user boundary information. (5) The PHY layer performs bit embedding mapping on the multiplexed bit stream, converting discrete bits into continuous vector representations. Then, the JSCCM encoder generates complex transmission symbols based on the end-to-end recovery target. After power normalization, layer mapping, precoding, and resource mapping are completed, a downlink transmission is completed on the same time-frequency resource. (6) UE1 and UE2 enter the same PDSCH resource reception state on the receiving side according to the same DCI. After obtaining the same physical layer reception symbols, they respectively call the user-side JSCCM decoder that matches the JSCCM configuration parameters. The bit embedding demapping and hard decision are then used to recover the user's bearer bit stream. (7) The recovered user's bearer bit stream continues to enter the current MAC, RLC, and PDCP processing flow, and finally recovers the corresponding service content.

[0175] Through the above process, JSCCM does not simply replace constellation mapping in traditional modulation. Instead, it jointly models bit embedding representation, wireless channel adaptation, multi-user interference suppression, and receiver recovery objectives at the physical layer, enabling the same physical layer signal to serve the independent data recovery needs of multiple users. Therefore, this application embodies the integration of the learning-based representation capability of semantic communication "oriented towards information recovery quality" with physical layer resource transmission, PDSCH resource scheduling, DCI indication, and user-side decoding recovery.

[0176] In this embodiment, the upper-layer bearer links of each user remain independently processed. After each user's data forms its own bearer bitstream, the MAC layer splices them together according to predetermined rules to form a multiplexed bitstream. The physical layer generates complex transmission symbols through bit embedding mapping and JSCCM encoder and transmits them downlink in one go. The receiving end calls the matching user-side JSCCM decoder, obtains the bit soft decision information of the user's bit segment through bit embedding demapping, and recovers the user's bearer bitstream through hard decision. Then, it returns to the existing protocol link to continue processing to recover the user's data content or service output result. Since JSCCM end-to-end joint coding and modulation is adaptable to channel disturbances, this application's scheme improves the transmission robustness under resource reuse without changing the existing bearer and security mechanisms, and provides a feasible joint transmission and separable reception path for multi-user concurrent downlink.

[0177] Fourthly, to implement the above-mentioned data transmission method, an embodiment of this application provides a device 900 (network device or terminal device), such as... Figure 9 As shown, it may include at least one processor 901 and at least one transceiver 902 coupled to at least one processor 901. The transceiver 902 may include at least one separate receiving circuitry and a transmitting circuitry, or at least one integrated receiving circuitry and a transmitting circuitry. The at least one processor 901 may be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP), or a field-programmable gate array (FPGA), etc.

[0178] According to some embodiments of this application, when device 900 is a network device, the first device includes a first transceiver; and A first processor, coupled to a first transceiver; the first processor is configured to: Multiple bitstreams are obtained, with different bitstreams targeting different first devices in a first device set, which includes multiple first devices. Concatenate multiple bitstreams into a multiplexed bitstream; Map the multiplexed bitstream to a continuous vector; Semantic encoding is performed on continuous vectors to obtain a semantic sequence of the first device set; A semantic sequence is sent to multiple first devices in the first device set via a first transceiver.

[0179] In some embodiments, the first processor is configured to: On the first resource, a semantic sequence is sent to multiple first devices in the first device set based on the group identifier of the first device set.

[0180] In some embodiments, the first processor is configured to: Determine the scheduling parameters for the first set of devices; the scheduling parameters include at least one of the following: resource information and boundary indication information of the first resource; the boundary indication information is used to indicate the boundary of multiple bit streams in the multiplexed bit stream; Scheduling parameters are sent to multiple first devices in the first device set via downlink control information (DCI).

[0181] In some embodiments, the first processor is configured to: Boundary indication information is determined by concatenating multiple bit streams; or, Multiple bit streams are concatenated into a multiplexed bit stream based on boundary indication information.

[0182] In some embodiments, the first processor is configured to: A group identifier is sent to multiple first devices in the first device set via a first Radio Resource Control (RRC) message.

[0183] In some embodiments, the first processor is configured to: Based on the splicing rules, multiple bit streams are spliced ​​together into a multiplexed bit stream.

[0184] In some embodiments, the first processor is configured to: Obtain the target configuration parameters for the first set of devices. The target configuration parameters include: mapping method identifier and codec identifier. Based on the mapping method identifier, the multiplexed bit stream is mapped into a continuous vector; Based on the target encoder identified by the encoder-decoder identifier, semantic encoding is performed on continuous vectors to obtain semantic sequences.

[0185] In some embodiments, the first processor is configured to: The target configuration parameters are sent to multiple first devices in the first device set via a second RRC message.

[0186] In some embodiments, the first processor is configured to: The system receives data from multiple second devices included in the second device set. The data from the second devices undergoes bearer processing to obtain the bit stream of the second devices. Based on the capability information of the multiple second devices included in the second device set, the first device set and the target configuration parameters of the first device set are determined. The first set of equipment includes all or part of the second equipment in the second set of equipment; The capability information includes at least one of the following: semantic transmission capability information, a set of supported codec identifiers, a set of supported mapping method identifiers, and group addressing reception capability information.

[0187] In some embodiments, the first processor is configured to: Send a query request to multiple second devices in the second device set; Receive capability information of multiple second devices in the second device set.

[0188] In some embodiments, the first processor is configured to: When the encoding and decoding configuration information of the first set of devices meets the joint transmission conditions, multiple bit streams are concatenated into a multiplexed bit stream; the joint transmission conditions are related to at least one of the following: a first confirmation message for confirming that the codec configuration identified by the codec identifier in the target configuration parameters of the first set of devices is complete, and a second confirmation message for confirming that the group identifier configuration of the first set of devices is valid; The codec configuration information is used to indicate whether the codecs for the first target set have been configured.

[0189] In some embodiments, the first processor is configured to: If the codec identifier supported by the third device in the first set of devices to be connected matches the target configuration parameters of the first set of devices, the third device will be added to the first set of devices.

[0190] According to some embodiments of this application, when device 900 is a terminal device, the terminal device includes a second transceiver; and A second processor, coupled to a second transceiver; the second processor is configured to: The terminal device receives a semantic sequence of a first set of devices sent by a network device via a second transceiver; the terminal device is one of a plurality of first devices in the first set of devices. Based on boundary indication information, semantic decoding is performed on the semantic sequence to obtain the continuous vector of the terminal device; The continuous vectors of the terminal device are transformed to obtain the bit stream of the terminal device.

[0191] In some embodiments, the second processor is configured to: Demapping the continuous vectors of the terminal device yields bit-soft decision information; The bit stream of the terminal device is determined based on bit soft decision information.

[0192] In some embodiments, the second processor is configured to: On the first resource, a semantic sequence sent by a network device is received based on a group identifier of a first set of devices.

[0193] In some embodiments, the second processor is configured to: The network device receives scheduling parameters for a first set of devices via downlink control information (DCI). The scheduling parameters include at least one of the following: resource information and boundary indication information for a first resource. The boundary indication information is used to indicate the boundary of the bit streams of multiple first devices in the multiplexed bit stream.

[0194] In some embodiments, the second processor is configured to: The network device receives the group identifier of the first set of devices via the first RRC message.

[0195] In some embodiments, the second processor is configured to: The target configuration parameters of the first set of devices sent by the network device are received via the second RRC message; the target configuration parameters include at least: mapping method identifier and codec identifier. The target decoder of the identified terminal device is identified by the codec, and semantic decoding is performed on the semantic sequence based on the boundary indication information to obtain the continuous vector of the terminal device; Based on the demapping method identified by the mapping method identifier, the continuous vector of the terminal device is transformed to obtain the bit stream of the terminal device.

[0196] In some embodiments, the second processor is configured to: Receive query requests sent by network devices; Send terminal device capability information to network devices.

[0197] It should be noted that, in the embodiments of this application, if the above-described data transmission method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0198] Fifthly, to implement the above-mentioned wireless communication method, embodiments of this application provide an electronic device, including a memory and a processor. The memory stores a computer program that can run on the processor, and when the processor executes the program, it implements the steps in the wireless communication method provided in the above embodiments.

[0199] Sixthly, embodiments of this application provide a storage medium, namely a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the steps in the wireless communication method provided in the above embodiments.

[0200] It should be noted that the descriptions of the storage medium and device embodiments above are similar to those of the method embodiments above, and have similar beneficial effects. For technical details not disclosed in the storage medium and device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0201] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in some embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0202] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0203] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0204] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0205] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0206] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, read-only memory (ROM), magnetic disks, or optical disks.

[0207] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0208] The above are merely embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A network device, the network device comprising a first transceiver, and A first processor, coupled to the first transceiver; the first processor is configured to: Multiple bitstreams are obtained, with different bitstreams targeting different first devices in a first device set, which includes multiple first devices. The multiple bit streams are concatenated into a multiplexed bit stream; Map the multiplexed bitstream into a continuous vector; Semantic encoding is performed on the continuous vectors to obtain the semantic sequence of the first device set; The semantic sequence is sent to multiple first devices in the first device set via the first transceiver.

2. The network device according to claim 1, wherein the first processor is configured to: On the first resource, the semantic sequence is sent to multiple first devices in the first device set based on the group identifier of the first device set.

3. The network device according to claim 2, wherein the first processor is configured to: Determine the scheduling parameters for the first set of devices; the scheduling parameters include at least one of the following: resource information and boundary indication information of the first resource; the boundary indication information is used to indicate the boundaries of the multiple bit streams in the multiplexed bit stream; The scheduling parameters are sent to multiple first devices in the first device set via downlink control information (DCI).

4. The network device according to claim 3, wherein the first processor is configured to: The boundary indication information is determined based on the concatenation of the multiple bit streams; or, The multiple bit streams are concatenated into the multiplexed bit stream based on the boundary indication information.

5. The network device according to claim 1, wherein the first processor is configured to: Obtain the target configuration parameters of the first set of devices, the target configuration parameters including: Mapping method identifier and codec identifier; Based on the mapping method identifier, the multiplexed bit stream is mapped to the continuous vector; Based on the target encoder identified by the encoder-decoder identifier, the continuous vector is semantically encoded to obtain the semantic sequence.

6. The network device according to claim 5, wherein the first processor is configured to: The target configuration parameters are sent to multiple first devices in the first device set via a second Radio Resource Control (RRC) message.

7. The network device according to claim 6, wherein the first processor is configured to: The system receives data from multiple second devices included in the second device set. The data from the second devices undergoes bearer processing to obtain the bit stream of the second devices. Based on the capability information of the multiple second devices included in the second device set, the first device set and the target configuration parameters of the first device set are determined; The first set of devices includes all or part of the second devices in the second set of devices; The capability information includes at least one of the following: semantic transmission capability information, a set of supported codec identifiers, a set of supported mapping method identifiers, and group addressing reception capability information.

8. The network device according to claim 1, wherein the first processor is configured to: When the encoding and decoding configuration information of the first device set meets the joint transmission condition, the multiple bit streams are concatenated into the multiplexed bit stream; the joint transmission condition is related to at least one of the following: second confirmation information for confirming that the network device is configured with the encoder identified by the codec identifier in the target configuration parameters of the first device set, second confirmation information for confirming that multiple first devices are respectively configured with the decoders of the multiple first devices identified by the codec identifier, and third confirmation information for confirming that the codec identified by the codec identifier is available; The codec configuration information is used to indicate whether the codec configuration of the first target set is complete.

9. A terminal device, the terminal device comprising a second transceiver, and A second processor, coupled to the second transceiver; the second processor is configured to: The terminal device receives a semantic sequence of a first set of devices sent by a network device via the second transceiver; the terminal device is one of a plurality of first devices in the first set of devices. Based on the boundary indication information, the semantic sequence is semantically decoded to obtain the continuous vector of the terminal device; The continuous vectors of the terminal device are transformed to obtain the bit stream of the terminal device.

10. A data transmission method, applied to a network device, comprising: Multiple bitstreams are obtained, with different bitstreams targeting different first devices in a first device set, which includes multiple first devices. The multiple bit streams are concatenated into a multiplexed bit stream; Map the multiplexed bitstream into a continuous vector; Semantic encoding is performed on the continuous vectors to obtain the semantic sequence of the first device set; The semantic sequence is sent to multiple first devices in the first set of devices.

Images