WO2023115559A1

WO2023115559A1 - Wireless communication method, terminal device, and network device

Info

Publication number: WO2023115559A1
Application number: PCT/CN2021/141310
Authority: WO
Inventors: 张博源; 卢前溪; 付喆
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-12-24
Filing date: 2021-12-24
Publication date: 2023-06-29

Abstract

Provided are a wireless communication method, a terminal, and a network device. The method comprises: a first terminal device receiving or sending NC configuration information for sidelink communication. The wireless communication method provided in the embodiments of the present application realizes the fusion of NC technology and sidelink technology by exchanging NC configuration information for sidelink communication.

Description

Wireless communication method, terminal device and network device

technical field

The present application relates to the field of communication technologies, and more specifically, to a wireless communication method, terminal equipment, and network equipment.

Background technique

Network coding (network coding, NC) is an information exchange technology that combines routing and coding. The core idea of NC is to linearly or nonlinearly process the information received on each data stream on each node in the network, and forward the processed data stream to the downstream node. The 3rd generation partnership project (3rd generation partnership project, 3GPP) will consider applying NC technology to wireless communication systems in the future, such as applying to sidewalk communication systems. However, there is still no clear plan on how to integrate the NC technology with the sidewalk communication system.

Contents of the invention

The present application provides a wireless communication method, terminal equipment and network equipment, so as to realize the integration of NC technology and sidewalk communication system.

In a first aspect, a wireless communication method is provided, including: a first terminal device receives or sends network coding NC configuration information for sidelink communication.

In a second aspect, a wireless communication method is provided, including: a network device receiving or sending network coding NC configuration information for sidelink communication.

In a third aspect, a terminal device is provided, the terminal device is a first terminal device, and the terminal device includes: a communication module, configured to receive or send network coding NC configuration information for sidelink communication.

In a fourth aspect, a network device is provided, including: a communication module, configured to receive or send network coding NC configuration information for sidelink communication.

In a fifth aspect, there is provided a communication device, including a memory and a processor, the memory is used to store programs, and the processor is used to call the programs in the memory to execute the method described in the first aspect or the second aspect method.

According to a sixth aspect, an apparatus is provided, including a processor, configured to call a program from a memory, so as to execute the method described in the first aspect or the second aspect.

In a seventh aspect, a chip is provided, including a processor, configured to call a program from a memory, so that a device installed with the chip executes the method described in the first aspect or the second aspect.

In an eighth aspect, a computer-readable storage medium is provided, on which a program is stored, and the program causes a computer to execute the method described in the first aspect or the second aspect.

In a ninth aspect, a computer program product is provided, including a program, the program causes a computer to execute the method described in the first aspect or the second aspect.

In a tenth aspect, a computer program is provided, the computer program causes a computer to execute the method described in the first aspect or the second aspect.

In the embodiment of the present application, the integration of the NC technology and the side link communication technology is realized by exchanging the NC configuration information used for the side link communication.

Description of drawings

FIG. 1 is a system architecture diagram of a communication system to which an embodiment of the present application can be applied.

Fig. 2 is a schematic diagram of configuring a sidelink in an embodiment of the present application.

Fig. 3 is a flowchart of a wireless communication method according to an embodiment of the present application.

Fig. 4 is a flowchart of a wireless communication method according to another embodiment of the present application.

Fig. 5 is a schematic structural diagram of a terminal device in an embodiment of the present application

Fig. 6 is a schematic structural diagram of a network device in an embodiment of the present application

Fig. 7 is a schematic structural diagram of a communication device in an embodiment of the present application.

Detailed ways

Communication System Architecture

The technical solution of the embodiment of the present application can be applied to various communication systems, for example: global system of mobile communication (global system of mobile communication, GSM) system, code division multiple access (code division multiple access, CDMA) system, broadband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (general packet radio service, GPRS), long term evolution (long term evolution, LTE) system, advanced long term evolution (advanced long term evolution, LTE-A) system , new radio (new radio, NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) on unlicensed spectrum unlicensed spectrum (NR-U) system, NTN system, universal mobile telecommunications system (UMTS), wireless local area network (wireless local area networks, WLAN), wireless fidelity (wireless fidelity, WiFi), fifth-generation communication (5th-generation, 5G) system or other communication systems, such as future communication systems, such as the sixth-generation mobile communication system, and satellite communication systems.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, the mobile communication system will not only support traditional communication, but also support, for example, device to device (device to device, D2D) communication, machine to machine (machine to machine, M2M) communication, machine type Communication (machine type communication, MTC), inter-vehicle (vehicle to vehicle, V2V) communication, or vehicle networking (vehicle to everything, V2X) communication, etc., the embodiments of the present application can also be applied to these communication systems.

The communication system in the embodiment of the present application may be applied to a carrier aggregation (carrier aggregation, CA) scenario, may also be applied to a dual connectivity (dual connectivity, DC) scenario, and may also be applied to an independent (standalone, SA) network deployment scenario.

The communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to a licensed spectrum, wherein the licensed spectrum can also be Considered a dedicated spectrum.

The embodiments of the present application may be applied to an NTN system, and may also be applied to a terrestrial communication network (terrestrial networks, TN) system. By way of example and not limitation, the NTN system includes an NR-based NTN system and an IoT-based NTN system.

Embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, wherein terminal equipment may also be referred to as terminal, user equipment (user equipment, UE), access terminal, vehicle-mounted terminal, industrial control terminal, user unit, user station, mobile station, mobile station (mobile station, MS), mobile terminal (mobile terminal, MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

In the embodiment of the present application, the terminal device may be a station (STATION, ST) in the WLAN, and may be a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) stations, personal digital assistant (PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, next-generation communication systems such as NR networks The terminal equipment in the network, or the terminal equipment in the public land mobile network (public land mobile network, PLMN) network that will evolve in the future, etc.

In this embodiment of the present application, a terminal device may be a device that provides voice and/or data connectivity to users, and may be used to connect people, things and machines, such as handheld devices with wireless connection functions, vehicle-mounted devices, and the like. Terminal equipment can be fixed or mobile. The terminal device in the embodiment of the present application can be mobile phone (mobile phone), tablet computer (Pad), notebook computer, palmtop computer, mobile internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) equipment, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, smart Wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, etc. Optionally, a terminal device can be used to act as a base station. For example, a terminal device may act as a scheduling entity, which provides sidelink signals between terminal devices in V2X or D2D, etc. For example, a cell phone and an automobile communicate with each other using sidelink signals. Communication between cellular phones and smart home devices without relaying communication signals through base stations.

As an example but not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction. Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.

The network device in this embodiment of the present application may be a device for communicating with a terminal device, and the network device may also be called an access network device or a wireless access network device, for example, the network device may be a base station. The network device in this embodiment of the present application may refer to a radio access network (radio access network, RAN) node (or device) that connects a terminal device to a wireless network. The base station can broadly cover various names in the following, or replace with the following names, such as: Node B (NodeB), evolved base station (evolved NodeB, eNB), next generation base station (next generation NodeB, gNB), relay station, Access point, transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), primary station MeNB, secondary station SeNB, multi-standard wireless (MSR) node, home base station, network controller, access node , wireless node, access point (access piont, AP), transmission node, transceiver node, base band unit (base band unit, BBU), remote radio unit (remote radio unit, RRU), active antenna unit (active antenna unit) , AAU), radio head (remote radio head, RRH), central unit (central unit, CU), distributed unit (distributed unit, DU), positioning nodes, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station may also refer to a communication module, modem or chip configured in the aforementioned equipment or device. The base station can also be a mobile switching center, a device that undertakes the function of a base station in D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communication, and a device in a 6G network. Network-side equipment, equipment that assumes base station functions in future communication systems, etc. Base stations can support networks of the same or different access technologies. The embodiment of the present application does not limit the specific technology and specific device form adopted by the network device.

Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move according to the location of the mobile base station. In other examples, a helicopter or drone may be configured to serve as a device in communication with another base station.

In some deployments, the network device in this embodiment of the present application may refer to a CU or a DU, or, the network device includes a CU and a DU. A gNB may also include an AAU.

In the embodiment of this application, network devices and/or terminal devices can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; they can also be deployed on water (such as ships, etc.); they can also be deployed on aircraft in the air , balloons and satellites. In the embodiments of the present application, there is no limitation on the scenarios where the network devices and/or terminal devices are located.

As an example but not a limitation, in this embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. In some embodiments of the present application, the network device may be a satellite or a balloon station. For example, the satellite can be a low earth orbit (low earth orbit, LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous earth orbit (geosynchronous earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite. ) Satellite etc. In some embodiments of the present application, the network device may also be a base station installed on land, in water, and other locations.

In this embodiment of the present application, the network device may provide services for a cell, and the terminal device communicates with the network device through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device ( For example, a cell corresponding to a base station), the cell may belong to a macro base station, or may belong to a base station corresponding to a small cell, where the small cell may include: a metro cell, a micro cell, a pico cell ( pico cell), femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

Exemplarily, FIG. 1A is a schematic structural diagram of a communication system provided by an embodiment of the present application. As shown in FIG. 1A , a communication system 100 may include a network device 110, and the network device 110 may be a device for communicating with a terminal device 120 (or called a communication terminal, terminal). The network device 110 can provide communication coverage for a specific geographical area, and can communicate with terminal devices located in the coverage area.

FIG. 1A exemplarily shows one network device and two terminal devices. In some embodiments of the present application, the communication system 100 may include multiple network devices and each network device may include other numbers of terminals within the coverage area. The device is not limited in the embodiment of this application.

Exemplarily, FIG. 1B is a schematic structural diagram of another communication system provided by an embodiment of the present application. Referring to FIG. 1B , the communication system includes a terminal device 1101 and a satellite 1102 , and wireless communication can be performed between the terminal device 1101 and the satellite 1102 . The network formed between the terminal device 1101 and the satellite 1102 may also be referred to as NTN. In the architecture of the communication system shown in FIG. 1B , the satellite 1102 may function as a base station, and the terminal device 1101 and the satellite 1102 may communicate directly. Under the system architecture, the satellite 1102 can be referred to as a network device. In some embodiments of the present application, the communication system may include multiple network devices 1102, and the coverage of each network device 1102 may include other numbers of terminal devices, which is not limited in this embodiment of the present application.

Exemplarily, FIG. 1C is a schematic structural diagram of another communication system provided by an embodiment of the present application. Referring to FIG. 1C , the communication system includes a terminal device 1201 , a satellite 1202 and a base station 1203 , and wireless communication can be performed between the terminal device 1201 and the satellite 1202 . The network formed among the terminal equipment 1201, the satellite 1202 and the base station 1203 may also be referred to as NTN. In the architecture of the communication system shown in FIG. 1C , the satellite 1202 may not have the function of a base station, and the communication between the terminal device 1201 and the base station 1203 needs to be relayed through the satellite 1202 . Under this system architecture, the base station 1203 may be called a network device. In some embodiments of the present application, the communication system may include multiple network devices 1203, and the coverage of each network device 1203 may include other numbers of terminal devices, which is not limited in this embodiment of the present application.

It should be noted that Fig. 1A-Fig. 1C are only illustrations of the systems to which this application is applicable. Of course, the methods shown in the embodiments of this application can also be applied to other systems, for example, 5G communication systems, LTE communication systems, etc. , which is not specifically limited in this embodiment of the present application.

In some embodiments of the present application, the wireless communication system shown in FIG. 1A-FIG. 1C may further include a mobility management entity (mobility management entity, MME), an access and mobility management function (access and mobility management function, AMF) and other network entities, which are not limited in this embodiment of the present application.

It should be understood that a device with a communication function in the network/system in the embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in FIG. 1A as an example, the communication equipment may include a network equipment 110 and a terminal equipment 120 with communication functions, and the network equipment 110 and the terminal equipment 120 may be the specific equipment described above, which will not be repeated here. The communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the "indication" mentioned in the embodiments of the present application may be a direct indication, may also be an indirect indication, and may also mean that there is an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or that there is an association between the two, or that it indicates and is indicated, configuration and is configuration etc.

The "configuration" in this embodiment of the present application may include configuring by at least one of system messages, radio resource control (radio resource control, RRC) signaling, and media access control element (MAC CE) .

In some embodiments of the present application, "predefined" or "preset" may be pre-saved in devices (for example, including terminal devices and network devices) with corresponding codes, tables or other methods that can be used to indicate related information implementation, and the present application does not limit the specific implementation manner. For example, the predefined ones may refer to those defined in the protocol.

In some embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include the LTE protocol, the NR protocol, and related protocols applied to future communication systems, which is not limited in the present application.

For ease of understanding, some relevant technical knowledge involved in the embodiments of the present application is introduced first. The following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as optional solutions, and all of them belong to the protection scope of the embodiments of the present application. The embodiment of the present application includes at least part of the following content.

LTE D2D

D2D (it should be noted that, in the case of no clear distinction, the D2D mentioned in the embodiment of the present application may include V2V and V2X) is a sidelink (sidelink, SL) transmission technology. In a traditional cellular system, communication data between terminal devices generally needs to be received and/or forwarded by network devices. Different from the traditional cellular communication method, D2D adopts the method of direct communication between terminal equipment and terminal equipment. Therefore, D2D has higher spectral efficiency and lower transmission delay.

The 3rd generation partnership project (3rd generation partnership project, 3GPP) defines two transmission modes: mode A and mode B.

In mode A, the transmission resources of the terminal equipment are allocated by the network equipment. That is, the terminal device sends data on the sidelink according to the resource allocated by the network device. In mode A, the network device may allocate resources for a single transmission to the terminal device, or may allocate resources for semi-static transmission to the terminal device. Taking the terminal device as a vehicle as an example, referring to FIG. 2A , before the side travel communication, the network device 110 first allocates transmission resources for the side travel communication to the vehicle 120A or the vehicle 120B, and then the vehicle 120A or the vehicle 120B can Transmission resources for vehicle-to-vehicle side traffic communication.

In mode B, the terminal device selects a resource from the resource pool for data transmission. Still taking the terminal device as a vehicle as an example, referring to FIG. 2B ,

vehicles

120A and 120B can independently start vehicle-to-vehicle communication after selecting resources from the resource pool, and do not need the network device 110 to allocate transmission resources.

In 3GPP, D2D is divided into different stages for research.

In Rel-12/13 (Rel refers to release), D2D communication is researched on scenarios based on Proximity based Service (ProSe), which is mainly aimed at public security services. In the ProSe scenario, by configuring the position of the resource pool in the time domain, for example, configuring the resource pool to be discontinuous in the time domain, the terminal device can discontinuously send/receive data on the sidelink, thereby saving The effect of electricity.

In Rel-14/15, the V2X system is researched on the scene of vehicle-to-vehicle communication, which is mainly oriented to relatively high-speed mobile vehicle-to-vehicle and vehicle-to-human communication services. In the V2X system, since the on-board system can continuously supply power, the power efficiency of the on-board system is not the main concern of the V2X system. The main issue related to the V2X system is the delay of data transmission. Therefore, in order to reduce the data transmission delay, the V2X system generally requires the vehicle system to perform continuous transmission and reception during the lateral communication process.

In Rel-14, further enhancement D2D (further enhancement D2D, FeD2D) is introduced to study the scenario where wearable devices access network devices through terminal devices (such as mobile phones). FeD2D is mainly oriented to low mobile speed and low power access scenarios.

In FeD2D, in the pre-research stage, 3GPP gave the following conclusion: the network device can configure the discontinuous reception (DRX) parameters of the remote (remote) terminal through a relay (relay) terminal. However, since this topic has not further entered the standardization stage, it has not discussed the specific details of how to configure DRX.

In Rel-15 LTE V2X, a multi-carrier mechanism is introduced. The multi-carrier mechanism is reflected in that the terminal device can support data packet segmentation, so as to transmit data packets through multiple carriers to improve the data transmission rate. Alternatively, the terminal device can perform data packet duplication, thereby duplicating the same data packet into multiple (such as two) data packets; then, the terminal device can use multiple carriers to send the multiple data packets respectively, thereby improving transmission efficiency. Reliability and multi-carrier reception enhancements at the receiver.

For data packet replication, V2X supports terminal devices to perform sidelink data packet replication (or sidelink packet replication) at the packet data convergence protocol (PDCP) layer. Specifically, a PDCP packet data unit (PDU) can be duplicated at a PDCP entity (PDCP duplication), and then two packet data protocol (PDP) PDUs duplicated by the same PDCP entity are submitted Two different radio link control (radio link control, RLC) entities are assigned to two different sidelink logical channels respectively. Different PDP PDUs replicated by the same PDCP entity are only allowed to be transmitted on different sidelink carriers.

End-devices can activate or deactivate packet replication for the sidelink based on (pre-)configuration. Sidelink packet replication is not available for transports with the Rel-14 transport profile (see TS 23.285 [72]). ProSe per-packet reliability (PPPR) values that support sidelink packet replication can be (pre)configured via PPPR thresholds. For the resource selection method performed by the terminal device independently and the resource allocation method based on network device scheduling, the terminal device should perform sidelink data packet replication for data packets with a configured PPPR value until the configuration of data packet replication corresponding to the PPPR value is cleared. until cancelled. In addition, for the resource allocation method based on network device scheduling, the terminal device can report the data volume of the data packets associated with one or more PPPR values and the destination. The mapping of the PPPR value to the logical channel group can be configured by the network device, and the PPPR value is reflected by the logical channel group identification (identity, ID) associated with the PPPR value included in the sidelink BSR. A list of one or more PPPR values may be reported by a terminal device in an RRC connection in the sidelink UE information.

NR V2X

NR V2X expands on the basis of LTE V2X. For example, NR V2X is not limited to broadcast scenarios, but also extends to unicast and multicast scenarios, and studies the application of V2X in these scenarios.

Similar to LTE V2X, NR V2X will also define the above two resource authorization modes of mode A and mode B. Furthermore, the terminal device can be in a mixed mode, that is, the terminal device can use mode A to obtain resources, and can also use mode B to obtain resources. The resource acquisition of the terminal device can be indicated by way of side link authorization. For example, the sidelink grant may be used to indicate the time-frequency positions of physical sidelink control channel (physical sidelink control channel, PSCCH) and physical sidelink shared channel (physical sidelink shared channel, PSSCH) resources.

Unlike LTE V2X, in addition to the hybrid automatic repeat reQuest (HARQ) retransmission initiated by terminal equipment without feedback, NR V2X introduces feedback-based HARQ retransmission, and the feedback-based HARQ retransmission It is not limited to unicast scenarios, but also applicable to multicast scenarios.

Similar to LTE V2X, in NR V2X, since the on-board system can continuously supply power, the power efficiency of the on-board system is not the main concern of the V2X system. The main issue related to the V2X system is the delay of data transmission. Therefore, in order to reduce the data transmission delay, the V2X system generally requires the vehicle system to perform continuous transmission and reception during the lateral communication process.

NC mechanism

NC is an information exchange technology that combines routing and coding. The core idea of NC is to linearly or nonlinearly process the information received on each data stream on each node in the network, and forward the processed data stream to the downstream node. It can be seen that in the NC scene, the intermediate node plays the role of encoder or signal processor.

Exemplarily, the intermediate node may process the data bit groups (x, y) on multiple paths into a group of data bit groups through logical operation and send them. For example, the intermediate node may perform an exclusive OR operation (XOR) on the data bit group (x, y), ie "xXORy", and then send the result of the XOR operation to the downstream node. On the premise of knowing x and/or y in advance, the receiving end can solve each data group (x, y) in "xXORy" through logic operation processing. The number of NC data streams supported by the intermediate node or the number of data packets processed can be represented by N. In the above example, since the intermediate node has performed encoding operations on 2 data bit groups (that is, two data streams), the value of N The value is 2.

As a new technology that can reach network capacity, NC may have great gains in the following two scenarios.

Scenario 1: For point-to-point multi-channel replication transmission, the traditional separate transmission gain is limited by the worst path condition, while NC transmission can adapt and adjust the data flow direction, so that the transmission gain mainly depends on the best path condition.

Scenario 2: For multi-hop network transmission, the traditional router-based simple forwarding strategy will cause the transmission rate to decrease exponentially as the packet loss rate increases, and NC transmission can basically reach the network capacity.

NC for 3GPP

3GPP can consider how to apply the NC mechanism in the wireless communication network, so as to improve the reliability of data transmission while using less transmission resources. As an example, the PDCP duplication was introduced above, and the NC mechanism can be applied to the PDCP duplication, that is, the terminal device can use NC-based PDCP duplication.

However, how to apply NC technology to existing wireless communication systems, such as side-travel communication systems, has not yet had a clear solution.

In view of this, the present application provides a wireless communication method, which realizes the fusion of NC technology and sidelink communication technology by exchanging NC configuration information for sidelink communication.

The following describes the embodiment of the present application in detail with reference to FIG. 3 . The method in FIG. 3 may be executed by the first terminal device, or may be executed by the network device. The first terminal device mentioned here refers to any terminal device that wants or is performing sidelink communication. The first terminal device may be the sending end of the sidelink communication, and may also be the receiving end of the sidelink communication. In some embodiments, the first terminal device may be referred to as a through-link terminal.

Referring to Fig. 3, in step S310, NC configuration information for sidelink communication is received or sent.

In some embodiments, step S310 may include the first terminal device receiving NC configuration information from the network device. For example, the first terminal device may receive NC configuration information sent by the network device for the first terminal device. For example, the network device may send the NC configuration information to the first terminal device through RRC signaling (such as RRC dedicated signaling), system message or pre-configuration.

In some embodiments, step S310 may include the first terminal device sending the NC configuration information of the first terminal device to the second terminal device (the terminal device performing side communication with the first terminal device). For example, during the side link communication process, the first terminal device may send the NC configuration information of the first terminal device to the second terminal device, so as to negotiate with the second terminal device on appropriate NC configuration information.

In some embodiments, step S310 may include that the first terminal device receives the NC configuration information of the second terminal device from the second terminal device (the terminal device performing lateral communication with the first terminal device). For example, during the side link communication process, the second terminal device may send the NC configuration information of the second terminal device to the first terminal device, so as to negotiate with the first terminal device on appropriate NC configuration information.

In some embodiments, step S310 may include the first terminal device sending NC configuration information to the network device. For example, after receiving the NC configuration information of the second terminal device, the first terminal device can send the NC configuration information of the second terminal device to the network device, so that the network device can determine whether to reconfigure the NC configuration information of the first terminal device .

NC configuration information may be associated with one or more types of information (or configuration information). As an example, one or more types of information (or configuration information) mentioned below may include NC configuration information.

In some embodiments, the NC configuration information may be associated with configuration enabling NC-based PDCP duplication (enable NC-based PDCP duplication) indication information.

In some embodiments, the NC configuration information is associated with configuration information for one or more quality of service (QoS) flows. As an example, NC configuration information may be associated with configuration information for one QoS flow. For example, NC can be used for each QoS flow (per QoS flow). As another example, NC configuration information may be associated with configuration information for multiple QoS flows. The multiple QoS flows may be represented by, for example, a QoS flow list (QoS flow list). For example, when the first terminal device simultaneously generates data to be transmitted corresponding to different QoS flows in the same QoS flow list, the terminal device can enable or enable the NC function to encode the data on different QoS flows into one group data.

In some embodiments, the NC configuration information is associated with configuration information for one or more bearers. As an example, NC configuration information is associated with configuration information for one bearer. For example, NC can be used per bearer (per SL-RB). As another example, NC configuration information is associated with configuration information for multiple bearers. The multiple bearers may be represented by, for example, a bearer list (SL-RB list). For example, when the first terminal device generates data to be transmitted on different bearers in the same bearer list at the same time, the first terminal device can enable or enable the NC function to encode the data of different SL-RBs into a set of data through the NC function .

In some embodiments, the NC configuration information is associated with configuration information for the destination address of the data packet. For example, NC can be used for each destination address (per destination ID) of a packet.

In some embodiments, NC configuration information is associated with configuration information for resource pools. For example, NC can be used per resource pool. As an example, within the resource pool configuration, the NC configuration information may be associated with the channel busy ratio (channel busy ratio, CBR) and service priority (priority) of the resource pool. The priority can be represented by ProSe per-packet priority (PPPP), for example. For example, the terminal device may determine whether to enable the NC function for transmission according to different priorities of current services and the congestion degree of the resource pool.

As another example, within a resource pool configuration, NC configuration information may be associated with a resource pool's CBR threshold. In other words, the CBR threshold value can be configured, and it is judged whether to enable the NC function according to the relationship between the CBR measurement value and the threshold value. For example, when the measured value of the CBR is lower than the threshold value, the terminal device may enable the NC function.

In some embodiments, the NC configuration information may be associated with the configuration information for the transmission mode of the sidelink. For example, NC can be used for each transport. The embodiment of the present application does not specifically limit the specific form of the transmission mode, for example, the transmission mode may include one or more of unicast, multicast, and broadcast.

In some embodiments, the NC configuration information is associated with configuration information of a sidelink reference signal received power (SL-reference signal received power, SL-RSRP) threshold value. As an example, the SL-RSRP threshold can be configured, and whether to enable the NC function can be determined according to the relationship between the measured value of SL-RSRP and the threshold. For example, when the measured value of SL-RSRP is higher than the threshold value of SL-RSRP, the terminal device may enable the NC function.

In some embodiments, the NC configuration information may be located in PDCP configuration information (PDCP-config) or radio bearer configuration information (radio bearer config).

The NC configuration information may include one or more of the following information: transmission information, bearer information, or usage information.

In some embodiments, the NC configuration information may include configuration information of physical layer parameters transmitted by the NC data packet. The configuration information of the physical layer parameters may include, for example, one or more of the following information: code rate, transmission power (transmission power) and other information.

In some embodiments, the NC configuration information may include configuration information of bearers corresponding to the NC data flow. The configuration information of the bearer corresponding to the NC data flow may include one or more of the following information: configuration information of the PDCP layer, configuration information of the RLC layer, and configuration information of the MAC layer.

As an example, the NC configuration information may include PDCP layer configuration information. For example, the configuration information of the PDCP layer may include one or more of the following information: whether to activate robust header compression (robust header compression, ROHC) information, whether to activate out-of-order delivery (out-of-order delivery) information , Information on whether to activate PDCP duplication, information on the length of a PDCP secondary node (SN), information on whether to perform PDCP encryption and decryption, or information on whether to perform PDCP layer integrity protection, etc.

As another example, the NC configuration information may include RLC layer configuration information. For example, the configuration information of the RLC layer may include one or more of the following information: information about the RLC mode, information about the length of the RLC SN, information about the number of polling data packets or information about the length of the polling byte, and the like.

As yet another example, the NC configuration information may be MAC layer configuration information. For example, the configuration information of the MAC layer may include one or more of the following information: logical channel priority information, logical channel priority bit rate information, logical channel token bucket size duration (bucket size duration, BSD) information , Whether to allow the use of configured grant (configured grant) information, available configured grant index (configured grant index) information, logical channel group information to which it belongs, attribute information of HARQ feedback or selective repeat corresponding to logical channels , SR) configuration information, etc.

In some embodiments, the NC configuration information may include configuration information of parameters used by the NC. The configuration information of the parameters used by the NC may include one or more of the following parameters: the number of data streams participating in the NC (or called segment N, where N is a positive integer greater than 1), the bearer identifier used by the NC, and the number of data streams used by the NC. encoding method.

As an example, the configuration information of the parameters used by the NC may include the number of data streams participating in the NC.

As another example, the configuration information of the parameters used by the NC may include one or more of the following identifiers: bearer identifiers used by the NC, default bearer identifiers, primary bearer identifiers, secondary bearer identifiers, or subordinate bearer identifiers. In some implementation manners, the above-mentioned identifier may refer to an RLC identifier or a MAC entity identifier.

As yet another example, the configuration information of the parameters used by the NC may include the encoding method used by the NC. For example, the coding profile used by NC (similar to ROHC profile).

In some embodiments, the NC configuration information may include configuration information enabling the number of data packet retransmissions required by the NC. Optionally, the network device may be configured to enable the NC (enable NC) after performing M retransmissions, or the network device may indicate to enable the NC after N retransmissions of the data packet (such as receiving N HARQ-NACKs).

In some embodiments, before receiving or sending the NC configuration information, the capability information associated with the NC of the terminal device may also be exchanged.

In some embodiments, the first terminal device may send the capability information associated with the NC to the network device. For example, if the first terminal device is in the RRC connection state, before obtaining the NC configuration information, it may report the capability information about the NC of the first terminal device to the network device.

In some embodiments, the first terminal device may send NC-associated capability information to the second terminal device, or the first terminal device may receive NC-associated capability information from the second terminal device. The second terminal device is a terminal device that performs lateral communication with the first terminal device. For example, in unicast communication, a PC5-RRC link will first be established between terminal devices (the first terminal device and the second terminal device). During the establishment of the PC5-RRC link, both terminal devices need to report their own Capability information associated with the NC.

In some embodiments, the capability information associated with the NC includes a coding mode (NC coding profile) for the NC supported by the terminal device.

In some embodiments, the capability information associated with the NC includes the maximum number (segment N) of data streams participating in the NC supported by the terminal device or the minimum number (segment L) of the data streams participating in the NC supported by the terminal device.

In some embodiments, the capability information associated with the NC includes physical layer parameters supported by the terminal device for transmission of the NC data packet. For example, maximum code rate, minimum code rate and/or maximum transmit power.

In the embodiment of the present application, after the above capability information exchange is completed, the two terminal devices (the first terminal device and the second terminal device) in the sidelink communication can further exchange the NC configuration information of both parties, so that The NC configuration of both sides can match.

In some embodiments, the NC configuration information of the terminal device may be reconfigured through the network device, or the NC configuration information may be actively reconfigured by the terminal device.

The negotiation process of the NC configuration information of the first terminal device and the second terminal device is illustrated in detail below with reference to FIG. 4 .

Referring to Fig. 4, in step S410a, the first network device sends NC configuration information A to the first terminal device as the NC configuration information of the first terminal device; similarly, in step S410b, the second network device sends to the second terminal device The NC configuration information B is used as the NC configuration information of the second terminal device. Of course, if the first terminal device and the second terminal device are located within the coverage of the same network device, the first network device and the second network device may be the same network device.

In step S420, the first terminal device and the second terminal device exchange capability information (NC-related capability information) to confirm whether both parties support NC functions.

After the capability information exchange is completed, the first terminal device and the second terminal device may further exchange NC configuration information.

Continuing to refer to FIG. 4, in step S430a, the first terminal device sends NC configuration information A to the second terminal device; similarly, in step S430b, the second terminal device sends NC configuration information B to the first terminal device.

After the first terminal device receives the NC configuration information B, if the first terminal device is in the RRC connection state, the first terminal device may execute step S440a to send the NC configuration information B to the first network device, so that the first network device can determine Whether RRC reconfiguration is required. If RRC reconfiguration is required, the first network device executes step S450a, and sends the reconfiguration information of the NC configuration information A to the first terminal device.

If the first terminal device is in the radio resource control idle state (RRC_IDLE) or radio resource control inactive (RRC_INACTIVE) state, the first terminal device may be triggered to enter the RRC connection state to perform the above-mentioned step S440a and step S450a. Of course, in some other embodiments, the first terminal device may also actively determine whether to receive the NC configuration information B of the second terminal device.

Similar to steps S440a and S450a, the second terminal device may also perform steps S440b and S450b correspondingly, which will not be described in detail here to avoid repetition.

After the NC configuration information interaction is completed, in some embodiments, step S460 and step S470 may be continued. The second terminal device sends the first message to the first terminal device. The first message may include available NC configuration information determined based on the NC configuration information of the second terminal device. The first terminal device receives the feedback message of the first message sent by the second terminal device. The feedback message may indicate that the second terminal device accepts or does not accept the above available NC configuration information. In some embodiments, if the feedback message indicates that the second terminal device accepts the above-mentioned available NC configuration information, the feedback message may be an RRC reconfiguration complete (RRC reconfiguration complete) message; if the feedback message indicates that the second terminal device does not accept the above-mentioned available NC configuration information, the feedback message is an RRC reconfiguration failure (RRC reconfiguration failure) message.

In some embodiments, the first terminal device may also send the first message to the second terminal device, and the second terminal device may provide a feedback message for the first message. Alternatively, the first terminal device and the second terminal device may send the first message to each other, and receive a feedback message of the first message from the other party.

The method embodiment of the present application is described in detail above with reference to FIG. 1 to FIG. 4 , and the device embodiment of the present application is described in detail below in conjunction with FIG. 5 to FIG. 7 . It should be understood that the descriptions of the method embodiments correspond to the descriptions of the device embodiments, therefore, for parts not described in detail, reference may be made to the foregoing method embodiments.

FIG. 5 is a schematic diagram of a terminal device in an embodiment of the present application, where the terminal device is a first terminal device. The terminal device 500 shown in FIG. 5 includes a communication module 510 .

A communication module 510, configured to receive or send NC configuration information for sidelink communication.

Optionally, the NC configuration information is associated with one or more of the following information: an instruction letter for enabling NC-based PDCP replication; configuration information for one or more QoS flows; Configuration information; configuration information for the destination address of the data packet; configuration information for the resource pool; configuration information for the transmission mode of the sidelink, wherein the transmission mode includes one or more of unicast, multicast and broadcast Various; and the configuration information of the sidelink RSRP threshold.

Optionally, the NC configuration information is associated with configuration information for a resource pool, including: the NC configuration information is associated with the CBR and service priority of the resource pool; and/or, the NC configuration information is associated with the CBR threshold association of resource pools.

Optionally, the NC configuration information includes one or more of the following information: configuration information of physical layer parameters transmitted by NC data packets; configuration information of bearers corresponding to NC data streams; configuration information of parameters used by NC; And enable the configuration information of the number of data packet retransmissions required by the NC.

Optionally, the bearer configuration information corresponding to the NC data flow includes one or more of the following information: PDCP layer configuration information, RLC layer configuration information, and MAC layer configuration information.

Optionally, the parameters used by the NC include one or more of the following parameters: the number of data streams participating in the NC, the bearer identifier used by the NC, and the encoding method used by the NC.

Optionally, the NC configuration information is located in PDCP configuration information or radio bearer configuration information.

Optionally, the communication module 510 is further configured to: send NC-associated capability information to the network device; or, send NC-associated capability information to the second terminal device; or, receive NC-associated capability information from the second terminal device , wherein the second terminal device is a terminal device on the sidelink.

Optionally, the capability information includes one or more of the following information: a supported encoding method for NC; a maximum number of data streams supporting NC participation; a minimum number of data streams supporting NC participation; and NC Physical layer parameters supported by packet transmission.

Optionally, the communication module 510 is configured to: receive the NC configuration information of the terminal device from the network device; or, send the NC configuration information of the terminal device to the second terminal device; or, receive the NC configuration information of the second terminal device. NC configuration information; wherein, the second terminal device is a terminal device on the sidelink.

Optionally, the communication module 510 is further configured to: send the NC configuration information of the second terminal device to a network device; and receive reconfiguration information of the NC configuration information of the terminal device from the network device.

Optionally, the communication module 510 is further configured to: send a first message to the second terminal device, where the first message includes available NC configuration information determined based on the NC configuration information of the second terminal device; receive A feedback message of the first message sent by the second terminal device, where the feedback message indicates whether the second terminal device accepts or does not accept the available NC configuration information.

Optionally, the communication module 510 is further configured to: receive a first message sent by the second terminal device, where the first message includes available NC configuration information determined based on the NC configuration information of the terminal device; The second terminal device sends a feedback message of the first message, where the feedback message indicates whether the terminal device accepts or not accepts the available NC configuration information.

Optionally, the feedback message is an RRC reconfiguration complete message, and the RRC reconfiguration complete message indicates acceptance of the available NC configuration information; or, the feedback message is an RRC reconfiguration failure message, and the RRC reconfiguration failure The message indicates that the available NC configuration information is not accepted.

Fig. 6 is a schematic diagram of a network device according to an embodiment of the present application. The network device 600 in FIG. 6 includes: a communication module 610 .

A communication module 610, configured to receive or send NC configuration information for sidelink communication.

Optionally, the communication module 610 is further configured to: receive NC-associated capability information sent by the first terminal device.

Optionally, the communication module 610 is configured to: send the NC configuration information of the first terminal device to the first terminal device; or receive the NC configuration information of the second terminal device from the first terminal device, Wherein, the second terminal device is a terminal device on the sidelink.

Optionally, the communication module 610 is further configured to: in response to receiving the NC configuration information of the second terminal device, send the reconfiguration of the NC configuration information of the first terminal device to the first terminal device information.

Fig. 7 is a schematic structural diagram of a device according to an embodiment of the present application. The dotted line in Figure 7 indicates that the unit or module is optional. The apparatus 700 may be used to implement the methods described in the foregoing method embodiments. Apparatus 700 may be a chip, a terminal device or a network device.

Apparatus 700 may include one or more processors 710 . The processor 710 may support the device 700 to implement the methods described in the foregoing method embodiments. The processor 710 may be a general purpose processor or a special purpose processor. For example, the processor may be a central processing unit (central processing unit, CPU). Alternatively, the processor can also be other general-purpose processors, digital signal processors (digital signal processors, DSPs), application specific integrated circuits (application specific integrated circuits, ASICs), off-the-shelf programmable gate arrays (field programmable gate arrays, FPGAs) Or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

Apparatus 700 may also include one or more memories 720 . A program is stored in the memory 720, and the program can be executed by the processor 710, so that the processor 710 executes the methods described in the foregoing method embodiments. The memory 720 may be independent from the processor 710 or may be integrated in the processor 710 .

Apparatus 700 may also include a transceiver 730 . The processor 710 can communicate with other devices or chips through the transceiver 730 . For example, the processor 710 may send and receive data with other devices or chips through the transceiver 730 .

The embodiment of the present application also provides a computer-readable storage medium for storing programs. The computer-readable storage medium can be applied to the terminal device or the network device provided in the embodiments of the present application, and the program enables the computer to execute the methods performed by the terminal device or the network device in the various embodiments of the present application.

The embodiment of the present application also provides a computer program product. The computer program product includes programs. The computer program product can be applied to the terminal device or the network device provided in the embodiments of the present application, and the program enables the computer to execute the methods performed by the terminal device or the network device in the various embodiments of the present application.

The embodiment of the present application also provides a computer program. The computer program can be applied to the terminal device or the network device provided in the embodiments of the present application, and the computer program enables the computer to execute the methods performed by the terminal device or the network device in the various embodiments of the present application.

It should be understood that in this embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B may also be determined according to A and/or other information.

It should be understood that the term "and/or" in this article is only an association relationship describing associated objects, indicating that there may be three relationships, for example, A and/or B may mean: A exists alone, and A and B exist at the same time , there are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be read by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital versatile disc (digital video disc, DVD)) or a semiconductor medium (for example, a solid state disk (solid state disk, SSD) )wait.

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims

A method for wireless communication, comprising:

The first terminal device receives or sends network coding NC configuration information for sidelink communication.
The method according to claim 1, wherein the NC configuration information is associated with one or more of the following information:

Instruction information for enabling NC-based packet data convergence protocol PDCP replication;

Configuration information for one or more quality of service QoS flows;

Configuration information for one or more bearers;

Configuration information for the destination address of the data packet;

Configuration information for resource pools;

Configuration information for the transmission mode of the sidelink, wherein the transmission mode includes one or more of unicast, multicast and broadcast; and

Configuration information of the RSRP threshold of the sidelink reference signal received power.
The method according to claim 2, wherein the NC configuration information is associated with configuration information for a resource pool, comprising: the NC configuration information is associated with the channel busy rate CBR and service priority of the resource pool; And/or, the NC configuration information is associated with the CBR threshold of the resource pool.
The method according to any one of claims 1-3, wherein the NC configuration information includes one or more of the following information:

Configuration information of physical layer parameters for NC data packet transmission;

Configuration information of the bearer corresponding to the NC data stream;

configuration information for parameters used by the NC; and

Enable the configuration information of the number of data packet retransmissions required by the NC.
The method according to claim 4, wherein the configuration information of the bearer corresponding to the NC data flow includes one or more of the following information: configuration information of the PDCP layer, configuration information of the radio link control RLC layer , and configuration information of the media access control MAC layer.
The method according to claim 4 or 5, wherein the parameters used by the NC include one or more of the following parameters: the number of data streams participating in the NC, the bearer identifier used by the NC, and the Encoding.
The method according to any one of claims 1-6, wherein the NC configuration information is located in PDCP configuration information or radio bearer configuration information.
The method according to any one of claims 1-7, further comprising:

The first terminal device sends NC-associated capability information to the network device; or,

The first terminal device sends NC-associated capability information to the second terminal device; or,

The first terminal device receives NC-associated capability information from the second terminal device;

Wherein, the second terminal device is a terminal device on the sidelink.
The method according to claim 8, wherein the capability information includes one or more of the following information:

Supported encoding methods for NC;

Support the maximum number of data streams participating in NC;

Support the minimum number of data streams participating in the NC; and

Physical layer parameters supported by NC data packet transmission.
The method according to any one of claims 1-9, wherein the first terminal device receives or sends NC configuration information for sidelink communication, including:

The first terminal device receives the NC configuration information of the first terminal device from a network device; or,

The first terminal device sends the NC configuration information of the first terminal device to the second terminal device; or,

The first terminal device receives NC configuration information of the second terminal device;

Wherein, the second terminal device is a terminal device on the sidelink.
The method according to claim 10, further comprising:

The first terminal device sends the NC configuration information of the second terminal device to a network device;

The first terminal device receives reconfiguration information of the NC configuration information of the first terminal device from the network device.
The method according to claim 10 or 11, further comprising:

The first terminal device sends a first message to the second terminal device, where the first message includes available NC configuration information determined based on the NC configuration information of the second terminal device;

The first terminal device receives a feedback message of the first message sent by the second terminal device, where the feedback message indicates whether the second terminal device accepts or not accepts the available NC configuration information.
The method according to claim 10 or 11, further comprising:

The first terminal device receives a first message sent by the second terminal device, where the first message includes available NC configuration information determined based on the NC configuration information of the first terminal device;

The first terminal device sends a feedback message of the first message to the second terminal device, where the feedback message instructs the first terminal device to accept or not to accept the available NC configuration information.
The method according to claim 12 or 13, wherein the feedback message is a radio resource control RRC reconfiguration complete message, and the RRC reconfiguration complete message indicates acceptance of the available NC configuration information; or, the feedback The message is an RRC reconfiguration failure message, and the RRC reconfiguration failure message indicates that the available NC configuration information is not accepted.
A method for wireless communication, comprising:

A network device receives or transmits network coded NC configuration information for sidelink communications.
The method according to claim 15, wherein the NC configuration information is associated with one or more of the following information:

Instruction information for enabling NC-based packet data convergence protocol PDCP replication;

Configuration information for one or more quality of service QoS flows;

Configuration information for one or more bearers;

Configuration information for the destination address of the data packet;

Configuration information for resource pools;

Configuration information for the transmission mode of the sidelink, wherein the transmission mode includes one or more of unicast, multicast and broadcast; and

Configuration information of the RSRP threshold of the sidelink reference signal received power.
The method according to claim 16, wherein the NC configuration information is associated with configuration information for a resource pool, comprising: the NC configuration information is associated with the channel busy rate CBR and service priority of the resource pool; And/or, the NC configuration information is associated with the CBR threshold of the resource pool.
The method according to any one of claims 15-17, wherein the NC configuration information includes one or more of the following information:

Configuration information of physical layer parameters for NC data packet transmission;

Configuration information of the bearer corresponding to the NC data stream;

configuration information for parameters used by the NC; and

Enable the configuration information of the number of data packet retransmissions required by the NC.
The method according to claim 18, wherein the configuration information of the bearer corresponding to the NC data flow includes one or more of the following information: configuration information of the PDCP layer, configuration information of the radio link control RLC layer , and configuration information of the media access control MAC layer.
The method according to claim 18 or 19, wherein the parameters used by the NC include one or more of the following parameters: the number of data streams participating in the NC, the bearer identifier used by the NC, and the Encoding.
The method according to any one of claims 15-20, wherein the NC configuration information is located in PDCP configuration information or radio bearer configuration information.
The method according to any one of claims 15-21, further comprising:

The network device receives the NC-associated capability information sent by the first terminal device.
The method according to claim 22, wherein the capability information includes one or more of the following information:

Supported encoding methods for NC;

Support the maximum number of data streams participating in NC;

Support the minimum number of data streams participating in the NC; and

Physical layer parameters supported by NC data packet transmission.
The method according to any one of claims 15-23, wherein the network device receives or sends NC configuration information for sidelink communication, including:

The network device sends the NC configuration information of the first terminal device to the first terminal device; or,

The network device receives NC configuration information of a second terminal device from the first terminal device, where the second terminal device is a terminal device on the sidelink.
The method according to claim 24, further comprising:

In response to receiving the NC configuration information of the second terminal device, the network device sends reconfiguration information of the NC configuration information of the first terminal device to the first terminal device.
A terminal device, characterized in that the terminal device is a first terminal device, and the terminal device includes:

A communication module for receiving or sending network coding NC configuration information for sidelink communication.
The terminal device according to claim 26, wherein the NC configuration information is associated with one or more of the following information:

Instruction information for enabling NC-based packet data convergence protocol PDCP replication;

Configuration information for one or more quality of service QoS flows;

Configuration information for one or more bearers;

Configuration information for the destination address of the data packet;

Configuration information for resource pools;

Configuration information for the transmission mode of the sidelink, wherein the transmission mode includes one or more of unicast, multicast and broadcast; and

Configuration information of the RSRP threshold of the sidelink reference signal received power.
The terminal device according to claim 27, wherein the NC configuration information is associated with configuration information for a resource pool, including: the NC configuration information is associated with the channel busy rate CBR and service priority of the resource pool and/or, the NC configuration information is associated with the CBR threshold of the resource pool.
The terminal device according to any one of claims 26-28, wherein the NC configuration information includes one or more of the following information:

Configuration information of physical layer parameters for NC data packet transmission;

Configuration information of the bearer corresponding to the NC data stream;

configuration information for parameters used by the NC; and

Enable the configuration information of the number of data packet retransmissions required by the NC.
The terminal device according to claim 29, wherein the configuration information of the bearer corresponding to the NC data flow includes one or more of the following information: configuration information of the PDCP layer, configuration information of the radio link control RLC layer information, and configuration information of the MAC layer of the media access control.
The terminal device according to claim 29 or 30, wherein the parameters used by the NC include one or more of the following parameters: the number of data streams participating in the NC, the bearer identifier used by the NC, and the number of data streams used by the NC. encoding method.
The terminal device according to any one of claims 26-31, wherein the NC configuration information is located in PDCP configuration information or radio bearer configuration information.
The terminal device according to any one of claims 26-32, wherein the communication module is also used for:

sending NC-associated capability information to the network device; or,

sending NC-associated capability information to the second terminal device; or,

The capability information associated with the NC is received from a second terminal device, where the second terminal device is a terminal device on the sidelink.
The terminal device according to claim 33, wherein the capability information includes one or more of the following information:

Supported encoding methods for NC;

Support the maximum number of data streams participating in NC;

Support the minimum number of data streams participating in the NC; and

Physical layer parameters supported by NC data packet transmission.
The terminal device according to any one of claims 26-34, wherein the communication module is used for:

receiving the NC configuration information of the terminal device from a network device; or,

sending the NC configuration information of the terminal device to the second terminal device; or,

receiving NC configuration information of the second terminal device;

Wherein, the second terminal device is a terminal device on the sidelink.
The terminal device according to claim 35, wherein the communication module is also used for:

sending the NC configuration information of the second terminal device to the network device;

Reconfiguration information of the NC configuration information of the terminal device is received from the network device.
The terminal device according to claim 35 or 36, wherein the communication module is also used for:

sending a first message to the second terminal device, where the first message includes available NC configuration information determined based on the NC configuration information of the second terminal device;

Receive a feedback message of the first message sent by the second terminal device, where the feedback message indicates whether the second terminal device accepts or not accepts the available NC configuration information.
The terminal device according to claim 35 or 36, wherein the communication module is also used for:

Receiving a first message sent by the second terminal device, where the first message includes available NC configuration information determined based on the NC configuration information of the terminal device;

Sending a feedback message of the first message to the second terminal device, where the feedback message indicates whether the terminal device accepts or not accepts the available NC configuration information.
The terminal device according to claim 37 or 38, wherein the feedback message is a radio resource control RRC reconfiguration complete message, and the RRC reconfiguration complete message indicates acceptance of the available NC configuration information; or, the The feedback message is an RRC reconfiguration failure message, and the RRC reconfiguration failure message indicates that the available NC configuration information is not accepted.
A network device, characterized in that it includes:

A communication module for receiving or sending network coding NC configuration information for sidelink communication.
The network device according to claim 40, wherein the NC configuration information is associated with one or more of the following information:

Instruction information for enabling NC-based packet data convergence protocol PDCP replication;

Configuration information for one or more quality of service QoS flows;

Configuration information for one or more bearers;

Configuration information for the destination address of the data packet;

Configuration information for resource pools;

Configuration information for the transmission mode of the sidelink, wherein the transmission mode includes one or more of unicast, multicast and broadcast; and

Configuration information of the RSRP threshold of the sidelink reference signal received power.
The network device according to claim 40, wherein the NC configuration information is associated with configuration information for a resource pool, including: the NC configuration information is associated with the channel busy rate CBR and service priority of the resource pool and/or, the NC configuration information is associated with the CBR threshold of the resource pool.
The network device according to any one of claims 40-42, wherein the NC configuration information includes one or more of the following information:

Configuration information of physical layer parameters for NC data packet transmission;

Configuration information of the bearer corresponding to the NC data stream;

configuration information for parameters used by the NC; and

Enable the configuration information of the number of data packet retransmissions required by the NC.
The network device according to claim 43, wherein the bearer configuration information corresponding to the NC data flow includes one or more of the following information: PDCP layer configuration information, radio link control RLC layer configuration information, and configuration information of the MAC layer of the media access control.
The network device according to claim 43 or 44, wherein the parameters used by the NC include one or more of the following parameters: the number of data streams participating in the NC, the bearer identifier used by the NC, and the encoding method.
The network device according to any one of claims 40-45, wherein the NC configuration information is located in PDCP configuration information or radio bearer configuration information.
The network device according to any one of claims 40-46, wherein the communication module is further used for:

The capability information associated with the NC sent by the first terminal device is received.
The network device according to claim 47, wherein the capability information includes one or more of the following information:

Supported encoding methods for NC;

Support the maximum number of data streams participating in NC;

Support the minimum number of data streams participating in the NC; and

Physical layer parameters supported by NC data packet transmission.
The network device according to any one of claims 40-48, wherein the communication module is used for:

sending the NC configuration information of the first terminal device to the first terminal device; or,

receiving NC configuration information of a second terminal device from the first terminal device, where the second terminal device is a terminal device on the sidelink.
The network device according to claim 49, wherein the communication module is also used for:

In response to receiving the NC configuration information of the second terminal device, sending reconfiguration information of the NC configuration information of the first terminal device to the first terminal device.
A communication device, comprising a memory and a processor, the memory is used to store a program, and the processor is used to call the program in the memory to execute the method according to any one of claims 1-25.
An apparatus, characterized by comprising a processor, configured to call a program from a memory to execute the method according to any one of claims 1-25.
A chip, including a processor, for calling a program from a memory, so that a device installed with the chip executes the method according to any one of claims 1-25.
A computer-readable storage medium, on which a program is stored, the program causes a computer to execute the method according to any one of claims 1-25.
A computer program product comprising a program for causing a computer to perform the method according to any one of claims 1-25.
A computer program that causes a computer to execute the method according to any one of claims 1-25.