CN118056364A

CN118056364A - Communication method and device

Info

Publication number: CN118056364A
Application number: CN202180103176.8A
Authority: CN
Inventors: 付喆; 张博源; 卢前溪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-12-31
Filing date: 2021-12-31
Publication date: 2024-05-17
Also published as: WO2023123335A1

Abstract

The application relates to a communication method and equipment, wherein the communication method comprises the following steps: the first device receives network coded NC configuration information. The communication method of the embodiment of the application can improve the reliability of data transmission.

Description

Communication method and device

Technical Field

The present application relates to the field of communications, and more particularly, to a communication method and apparatus.

Background

Network Coding (NC) is an information exchange technology that merges routing and coding. The network coding mainly comprises: the information received on each data stream is processed linearly or non-linearly at each node in the network and then forwarded to the downstream node, the intermediate node acting as an encoder or signal processor. Consideration is needed to improve the reliability of data transmission by using network coding.

Disclosure of Invention

The embodiment of the application provides a communication method and a communication device, which can improve the reliability of data transmission.

The embodiment of the application provides a communication method, which comprises the following steps: the first device receives network coded NC configuration information.

The embodiment of the application provides a communication method, which comprises the following steps: the second device transmits NC configuration information.

The embodiment of the application provides first equipment, which comprises: and the receiving unit is used for receiving the NC configuration information.

The embodiment of the application provides second equipment, which comprises: and the sending unit is used for sending the NC configuration information.

The embodiment of the application provides first equipment, which comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, so that the first device executes the communication method of any embodiment of the application.

The embodiment of the application provides second equipment which comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, so that the second device executes the communication method of any embodiment of the application.

The embodiment of the application provides a chip for realizing the communication method. Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device on which the chip is mounted performs the communication method of any of the embodiments of the present application.

An embodiment of the present application provides a computer-readable storage medium storing a computer program which, when executed by a device, causes the device to perform the communication method of any of the embodiments of the present application.

Embodiments of the present application provide a computer program product comprising computer program instructions for causing a computer to perform the communication method of any of the embodiments of the present application.

The embodiments of the present application provide a computer program which, when run on a computer, causes the computer to perform the communication method of any of the embodiments of the present application.

According to the embodiment of the application, the reliability of data transmission can be improved through network coding.

Drawings

Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

Fig. 2 is a PDU session and a data Flow (QoS Flow) contained therein in the 5GS system.

Fig. 3 is a schematic flow chart of a communication method according to an embodiment of the application.

Fig. 4 is a schematic flow chart of a communication method according to another embodiment of the application.

Fig. 5 is a schematic block diagram of a first device according to an embodiment of the application.

Fig. 6 is a schematic block diagram of a second device according to an embodiment of the application.

Fig. 7 is a flowchart of example 1 of a communication method according to an embodiment of the present application.

Fig. 8 is a flowchart of example 2 of a communication method according to an embodiment of the present application.

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

Fig. 10 is a schematic block diagram of a communication device according to an embodiment of the present application.

Fig. 11 is a schematic block diagram of a chip according to an embodiment of the application.

Fig. 12 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband 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, long term evolution advanced (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, non-terrestrial communication network (Non-TERRESTRIAL NETWORKS, NTN) system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (WIRELESS FIDELITY, WIFI), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.

Generally, the number of connections supported by the conventional Communication system is limited and easy to implement, however, with the development of Communication technology, the mobile Communication system will support not only conventional Communication but also, for example, 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 internet of vehicles (Vehicle to everything, V2X) Communication, etc., and the embodiments of the present application can also be applied to these Communication systems.

In one implementation, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a stand-alone (Standalone, SA) networking scenario.

In one implementation, the communication system in the embodiment of the present application may be applied to unlicensed spectrum, where unlicensed spectrum may also be considered as shared spectrum; or the communication system in the embodiment of the present application may also be applied to licensed spectrum, where licensed spectrum may also be considered as non-shared spectrum.

Embodiments of the present application are described in connection with a network device and a terminal device, where the terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, a User Equipment, or the like.

The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA) device, a handheld device with wireless communication functionality, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In the embodiment of the application, the terminal equipment can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).

In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned (SELF DRIVING), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (SMART GRID), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (SMART CITY), or a wireless terminal device in smart home (smart home), or the like.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In the embodiment of the present application, the network device may be a device for communicating with a mobile device, where the network device may be an Access Point (AP) in a WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, a relay station or an Access Point, a vehicle device, a wearable device, a network device (gNB) in an NR network, a network device in a PLMN network for future evolution, or a network device in an NTN network, etc.

By way of example, and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth Orbit (medium earth Orbit, MEO) satellite, a geosynchronous Orbit (geostationary earth Orbit, GEO) satellite, a high elliptical Orbit (HIGH ELLIPTICAL Orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.

In the embodiment of the present application, a network device may provide services for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a small cell (SMALL CELL), where the small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

Fig. 1 schematically illustrates a communication system 100. The communication system comprises one network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include a plurality of network devices 110, and each network device 110 may include other numbers of terminal devices 120 within a coverage area of the network device 110, which is not limited by the embodiment of the present application.

In one embodiment, the communication system 100 may further include other network entities such as Mobility management entity (Mobility MANAGEMENT ENTITY, MME), access and Mobility management function (ACCESS AND Mobility Management Function, AMF), which is not limited by the embodiment of the present application.

The network device may further include an access network device and a core network device. I.e. the wireless communication system further comprises a plurality of core networks for communicating with the access network devices. The access network device may be a long-term evolution (LTE) system, a next-generation (NR) system, or an evolved base station (evolutional node B, which may be simply an eNB or e-NodeB) macro base station, a micro base station (also referred to as a "small base station"), a pico base station, an Access Point (AP), a transmission point (transmission point, TP), a new generation base station (new generation Node B, gNodeB), or the like in an licensed assisted access long-term evolution (LAA-LTE) system.

It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system shown in fig. 1 as an example, the communication device may include a network device and a terminal device with a communication function, where the network device and the terminal device may be specific devices in the embodiments of the present application, and are not described herein again; the communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

It should be understood that the "indication" mentioned in the embodiments of the present application may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.

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

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description describes related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as alternatives, which all belong to the protection scope of the embodiments of the present application.

1. NC for 3GPP (NC for 3 GPP)

The 3GPP will consider how to apply Network Coding (NC) in the network, improving the reliability of data transmission with less transmission resources. One method of use is to use NC-based packet data convergence protocol (PACKET DATA Convergence Protocol, PDCP) duplication (duplication).

The investigation of the layer performing network coding includes investigation of the protocol stack of network coding based on PDCP duplication, e.g. between the network coding layers between radio link control (Radio Link Control, RLC) and PDCP (RAN 2) (Study of layer(s)on which network coding should be performed including study of protocol stacks of network coding based on PDCP duplication,e.g.,network coding layer between RLC and PDCP(RAN2))

2. NC mechanism

The main ideas of network coding include: the information received on each data stream is processed linearly or non-linearly at each node in the network and then forwarded to the downstream node, the intermediate node acting as an encoder or signal processor.

For example, the intermediate node may send the data bits (x, y) on multiple paths by logically processing (e.g., exclusive-or processing) into a set of data bits (xXORy). On the premise that x and/or y are known in advance, the receiving terminal can understand each path of data bit group (x, y) in the xXORy through a logic operation. Here, the number of supported NC data flows or the number of packet processing N is 2.

Network coding is a new technology for achieving network capacity, and there may be large gains in the following scenarios:

(1) For point-to-point multiplexed transmission, the split individual transmission gain is limited by the worst-case path situation, while the network encoded transmission can adapt the data flow so that the transmission depends primarily on the best-case path situation.

(2) For multi-hop network transmission, a simple forwarding strategy can enable the transmission rate to drop exponentially along with the increase of the packet loss rate, and network coding can basically reach network capacity.

3. NR quality of service (Quality of Service, qoS)

In order to guarantee the transmission rate, a QoS mechanism of 5GS is required. As shown in fig. 2, in a mobile communication network, in order to be able to transmit user plane data, one or more QoS flows (data flows) need to be established, and different data flows correspond to different QoS parameters. As an important measure of communication quality (Communication quality), qoS parameters are typically used to indicate the characteristics of QoS Flow, which may include, but are not limited to: 5QI, address resolution protocol (Address Resolution Protocol, ARP), guaranteed stream bit rate (GuaranteedFlow Bit Rate, GFBR), maximum stream bit rate (Maximum Flow Bit Rate, MFBR), maximum packet loss rate (Maximum Packet Loss Rate) (UL, DL), end-to-end PDB, AN-PDB, packet error rate (Packet Error Rate), priority Level, averaging window (AVERAGING WINDOW), resource Type (Resource Type), maximum data burst (Maximum Data Burst Volume), UE-aggregate maximum bit rate (AGGREGATE MAXIMUM BIT RATE, AMBR), session-AMBR, etc.

A Filter (or SDF template) contains parameters that describe the characteristics of the packet and is used to Filter out that a particular packet has been bound to a particular QoS Flow. Here, one commonly used Filter is an IP five-tuple, i.e. source and destination IP addresses, source and destination port numbers, protocol type.

In a scenario where a packet data Unit (PACKET DATA Unit, PDU) session includes a Qos Flow, the reliability requirements of the Qos Flow are different, and a Qos Flow with a relatively high reliability requirement may improve reliability and/or reduce latency through NC functions. Likewise, the reliability and/or latency requirements of different services are different, which can be achieved using NC. The higher the number of data streams or data packet processing numbers N of the supported NC is, the higher the reliability is; and the higher the number of N, the higher the processing complexity.

Since the performance and complexity of NC are related to NC inputs (inputs), such as the maximum segment length supported L (segment L) and the number of supported NC data streams or packet processing number N, the NC implementation is also related to NC inputs. Therefore, the embodiment of the application can provide a communication method, which comprises the steps of acquiring NC configuration, acquiring NC input or setting an NC input mode when an NC function or an NC protocol is used. In one implementation, the entity of the NC function uses the NC configuration, or the NC input is set when using NC-based replication (NC-based duplication) or when substituting for NC replication (NC-instead duplication).

Fig. 3 is a schematic flow chart of a communication method 300 according to an embodiment of the application. The method may alternatively be applied to the system shown in fig. 1, but is not limited thereto. The method includes at least some of the following.

S310, the first device receives network coding NC configuration information.

In the embodiment of the present application, NC may also be referred to as network codec. In the embodiment of the present application, the first device may be a terminal device, for example, UE. The first device may be a transmitting device or a receiving device. The second device opposite the first device may be a network device. The second device may be a transmitting device or a receiving device. For example, in the case where the first device is a transmitting-end device, the second device is a receiving-end device. In the case where the second device is a transmitting-end device, the first device is a receiving-end device.

In one embodiment, the NC configuration information is contained in at least one of: radio resource Control (Radio Resource Control, RRC) configuration information, radio bearer configuration information, PDCP configuration information, RLC configuration information, medium access Control (MEDIA ACCESS Control, MAC) configuration information, cell configuration information, logical channel configuration information.

In one embodiment, the NC configuration information is for at least one of: a Bearer (RB), PDCP entity, RLC entity, NC entity, user equipment, cell, MAC entity. For example, the NC configuration information is for at least one of: each or at least one PDCP entity group an NC entity each or at least one PDCP entity group, an NC entity NC entity group, each or at least one user equipment each or at least one user equipment group, each or at least one cell group, each or at least one MAC entity group, each or at least one carrier group. The Bearer (RB) may be a user plane Bearer ((user) Data Radio Bearer, DRB). Of course, it is not excluded that it can be used for control plane loading.

In one embodiment, the NC configuration information includes at least one of: the path used (leg) identification, default path (default leg), primary path (PRIMARY LEG), secondary path (secondary leg), slave path (slave leg).

In one embodiment, the NC configuration information includes at least one of: the maximum supported segment length L, the maximum supported segment number K, the supported NC data flow number or data packet processing number N and the used coding configuration file identification.

In the embodiment of the present disclosure, after the received data packet is segmented, the length of the obtained segmented data packet is smaller than or equal to the supported maximum segment length L. The number of packets obtained by segmenting one packet may be N. For example, a packet is received and split into two packets according to L. The number of these two packets is N. For another example, NC encoding is performed using a fountain code (e.g., profile identification 1). In another implementation, NC encoding may be performed on the N received data packets using a fountain code (e.g., profile identification of 1). Optionally, for either implementation, a padding operation may also be performed when the two packets are acquired to ensure that the two packets are matched or equal in size.

In one embodiment, the NC configuration information includes at least one of:

Physical layer parameters for NC PDU transmission;

A coding mode;

Indication information of whether NC is supported;

NC enabled identification;

indication information of whether NC is performed.

For example, the indication information of whether NC is supported may represent different states by different values. For example, the indication information of whether NC is supported is a first value indicating that NC protocol or NC function is supported; for the second value, it indicates that NC protocol or NC function is not supported.

For another example, NC-enabled flags may represent different states by different flags. For example, the NC-enabled flag is a first flag indicating that NC is enabled, NC protocol is turned on, or NC protocol functions are used; for the second identification, it means that NC functions are not used, NC protocol functions are not used, or NC protocols are not used. Or the presence of a specific information element (Information Element, IE) represents an enable and the absence of a representative disable.

For another example, the indication information of whether to execute NC may represent different states by different values. For example, the instruction information of whether to execute NC is a first value indicating that NC operation is executed; a second value indicates that no NC operation is performed. Or the occurrence of a particular IE represents execution and the non-occurrence represents non-execution.

In one embodiment, the physical layer parameters include at least one of: code rate, transmission power (transmission power). For example, the code rate may be a bit rate representing the number of transmitted bits per unit time. For another example, the transmission power may represent the power used to transmit NC PDUs.

In one embodiment, the encoding means comprises an encoding algorithm or an encoding profile.

In one embodiment, the encoding is configured with a granularity of bearer configuration. The coding scheme may be configured with granularity by at least one of a bearer group, carrier group, PDCP entity, RLC entity, NC entity, user equipment group, cell group, and MAC entity.

In one embodiment, the indication information of whether NC is supported, the identification enabled by the NC, or the indication information of whether NC is executed is used to indicate that the first device enables the NC after M retransmissions of the data packet.

For example, the first device enables NC after M retransmissions of the packet according to the received indication information of whether NC is supported in the NC configuration information, the NC-enabled flag, or the indication information of whether NC is executed.

In one embodiment, the method further comprises: the first device receives the indication information of whether NC is supported, the NC enabled mark or the indication information of whether NC is executed after the data packet is retransmitted for M times so as to determine whether NC is enabled; or the first device receives the indication information of whether NC is supported, the NC enabled flag, or the indication information of whether NC is executed after M retransmissions of the data packet, so as to enable NC.

For example, the first device receives NC configuration information after M retransmissions of the data packet, and if the indication information of whether NC is supported, the flag of enabling NC, or the indication information of whether NC is executed in the NC configuration information indicates that NC is enabled, it may be determined that NC is enabled. Otherwise, NC is not enabled.

For another example, if the first device receives NC configuration information including indication information of whether NC is supported, an identification enabled by the NC, or indication information of whether NC is performed after M retransmissions of the data packet, the NC is enabled.

In one embodiment, the indication of whether NC is supported, the NC configuration information, or whether NC configuration information is configured is determined based on at least one of:

Support capability for NC;

QoS transmission requirements;

Channel quality.

In one embodiment, the support capability for the NC includes at least one of: the ability to support NC protocols or NC functions or algorithms, the ability to support NC-based PDCP duplication, the ability of NC to replace PDCP duplication.

For example, the capability to support NC protocol or NC function or algorithm, or the capability of NC to replace PDCP duplication, or the capability of NC-based PDCP duplication may further include at least one of supporting a different coding profile (coding profile), a maximum supported segment length L, a maximum supported segment number K, a supported NC data stream number, or a packet processing number N.

In one embodiment, the indication information of whether NC is supported, the NC-enabled identification, or the indication information of whether NC is performed, the NC configuration information, or the whether NC configuration information includes at least one of:

different coding configuration files are supported;

The maximum supported segment length L;

The maximum number of supported segments K;

the number of supported NC data streams or the number of data packet processing N.

In one embodiment, the QoS transmission requirements include QoS transmission requirements corresponding to at least one of: traffic, session, qoS flows, bearers, logical Channels (LCHs).

In one embodiment, the QoS transmission requirements include reliability transmission requirements and/or latency requirements.

In one embodiment, at least one of traffic, session, qoS flow, bearer, LCH of the transmission requirement exceeding the first threshold enables NC, configures NC configuration information, or enables NC-based PDCP duplication.

In the embodiment of the application, the threshold of QoS transmission requirement can be set, and the thresholds of different transmission requirements can be different. For example, if the transmission requirement of the service exceeds the corresponding service transmission threshold, the NC is enabled. And enabling the NC if the transmission requirement of the QoS flow exceeds the corresponding QoS flow transmission threshold. Enabling NC if the transmission requirement of the bearer exceeds the corresponding bearer transmission threshold. Enabling the NC if the transmission requirement of the LCH exceeds the corresponding LCH transmission threshold. The NC is enabled if the reliability transmission requirement exceeds a reliability threshold. Enabling the NC if the latency requirement exceeds a latency threshold. In one approach, NC functionality/protocols may be enabled directly (independent of or not limited to PDCP duplicate transmissions). In another implementation, NC-based PDCP copying may be enabled.

In one embodiment, the channel quality comprises at least one of:

channel quality for each first device;

Channel quality for each LCH;

channel quality for each bearer;

channel quality for each carrier;

Channel quality for each MAC entity;

reference signal received Quality (REFERENCE SIGNAL RECEIVED Quality, RSRQ);

Reference signal received Power (REFERENCE SIGNAL RECEIVED Power, RSRP).

In one embodiment, the channel quality is reported by the first device.

In one embodiment, the channel quality is below a second threshold, enabling NC, configuring NC configuration information, or enabling NC-based PDCP duplication.

In one embodiment, the method further comprises: the first device determines NC inputs.

In the embodiment of the present application, NC input may be referred to as NC input information, NC input instructions, NC input commands, NC input elements, or the like. The NC inputs may include input parameters of an NC algorithm. The NC input may further include a packet received from a previous layer or a previous sub-layer.

In one embodiment, the NC input includes at least one of: the coding profile used identifies, the maximum supported segment length L, the maximum supported segment number K, the number of supported NC data streams or packet processing number N, NC algorithm, whether NC operations are to be performed.

In one embodiment, the NC input is for at least one of: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, MAC entity. For example, the NC input is for at least one of: each bearer, each PDCP entity, each RLC entity, each NC entity, each user equipment, each cell, each MAC entity. The bearer may be a user plane bearer. Of course, it is not excluded that it can be used for control plane loading.

In one embodiment, the NC input, NC configuration information, or NC transmission path includes at least one of: the path identification used, the default path, the primary path, the secondary path.

In one embodiment, the path identification includes at least one of: RLC identity, logical channel identity, MAC entity identity, carrier identity, PDCP identity.

For example, path identifications used for transmitting NC PDUs may be configured by NC configuration information. For another example, different paths may be configured for NC PDUs by NC configuration information. For example, a path of NC PDU where segmentation is performed is a master path, and a path of NC PDU where segmentation is not performed is a slave path. For another example, the path of NC PDU where padding is performed is the default path, and the path of NC PDU where padding is not performed is the secondary path. For another example, the path of the NC PDU to which the packet header is directly added is a default path, and the path of the NC PDU to which the packet header is added after exclusive or is a secondary path. For another example, the protocol layer or protocol function randomly selects a path (corresponding path transmission from the configured path identifier) to be used by a particular data packet.

In one embodiment, the NC input is obtained by at least one of: network configured, determined, predefined by the first device.

In one embodiment, the method further comprises: the first device performs NC operations according to NC configuration and/or NC input. The NC operation may include network coding and/or network decoding. The sending device performing NC operations may include encoding operations and/or some preparation operations prior to encoding, such as: segment (segmentation), padding (Padding), etc. The opposite end of the sender device may be the receiver device, and the receiver device performing NC operations may include decoding operations and/or some preparatory operations prior to decoding, such as: caching, reorganizing, cascading, de-stuffing, etc.

In one embodiment, the method further comprises: the first device sends the NC input to a second device.

In one embodiment, the NC input is sent by the first device to the second device via a user plane or control plane.

In one embodiment, the NC input is carried in a header of a data packet sent by the first device to the second device. For example: the NC inputs into the header of a packet carrying one of PDCP, RLC, MAC.

In one embodiment, the NC input is carried in auxiliary information reported by the first device to the second device. For example, the assistance information may be UE assistance information (ASSISTANCE INFORMATION). And the following steps: the assistance information may be an RRC message.

In one embodiment, the NC input is determined by the first device according to at least one of:

QoS transmission requirements corresponding to at least one of traffic, session, qoS flows, bearers, LCHs;

Channel quality.

In one embodiment, the first device determines NC inputs comprising: the first device determines NC inputs using the segment length L and/or the number of supported NC data streams or packet processing number N.

In one embodiment, the NC input is determined by at least one of an NC layer, NC supporting functions, NC protocol stacks of the first device.

In one embodiment, the method further comprises: the first device performs NC-based PDCP duplication according to the NC configuration information.

In one embodiment, the output of the NC algorithm is transmitted to lower layers via the same path or different paths. The output result of the NC algorithm may be referred to as NC result, NC output result, or NC output. The lower layer may be a PDCP layer, an RLC layer, a MAC layer, or a Physical (PHY) layer.

In one embodiment, the method further comprises: in the case where NC is enabled, or in the case where NC-based PDCP duplication is enabled, or in the case where NC replaces PDCP duplication, the manner in which the first device transmits data includes at least one of:

transmitting the original data or NC processed data from a default path or a main path;

data processed/generated using NC algorithms or protocols is transmitted from the secondary path or from the path.

For example, the NC-processed data may include data obtained by adding an NC header to the original data.

For another example, the data generated using NC algorithm or protocol may include the original data a or the original data B, and the data after header addition.

In one embodiment, the NC-processed data is transmitted through a dedicated DRB and its corresponding path entity.

In one embodiment, the PDCP duplication and NC-based PDCP duplication functions are alternatively activated.

In one embodiment, the support NC includes: enabling NC codec related operations, enabling NC transport, enabling NC codec, using capabilities of NC codec related operations, using capabilities of NC transport, using capabilities of NC codec, enabling NC-based PDCP duplication, or supporting capabilities of NC-based PDCP duplication.

Fig. 4 is a schematic flow chart of a communication method 400 according to an embodiment of the application. The method may alternatively be applied to the system shown in fig. 1, but is not limited thereto. The method includes at least some of the following. The same descriptions in this embodiment have the same meaning as those in the method 300, and reference may be made to the related descriptions in the method 300, which are not repeated herein for brevity.

S410, the second device sends NC configuration information.

In the embodiment of the present application, NC may also be referred to as network codec. In the embodiment of the present application, the second device may be a network device, such as a base station. The second device may be a transmitting device or a receiving device. The first device at the opposite end of the second device may be a terminal device. The functionality of the first device may be as described in relation to method 300. The first device may be a transmitting device or a receiving device. For example, in the case where the first device is a transmitting-end device, the second device is a receiving-end device. In the case where the second device is a transmitting-end device, the first device is a receiving-end device.

In one embodiment, the NC configuration information is contained in at least one of: RRC configuration information, radio bearer configuration information, PDCP configuration information, RLC configuration information, MAC configuration information, cell configuration information, logical channel configuration information.

In one embodiment, the NC configuration information is for at least one of: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, MAC entity. For example, the NC configuration information is for at least one of: each or at least one PDCP entity group an NC entity each or at least one PDCP entity group, an NC entity NC entity group, each or at least one user equipment each or at least one user equipment group, each or at least one cell group, each or at least one MAC entity group, each or at least one carrier group.

In one embodiment, the NC configuration information includes at least one of: the path identification used, the default path, the primary path, the secondary path.

In one embodiment, the NC configuration information includes at least one of:

Physical layer parameters for NC PDU transmission;

A coding mode;

Indication information of whether NC is supported;

NC enabled identification;

indication information of whether NC is performed.

In one embodiment, the physical layer parameters include at least one of: code rate, transmission power.

In one embodiment, the method further comprises:

After the first device retransmits the data packet M times, the second device sends the indication information of whether NC is supported, the NC enabled mark or the indication information of whether NC is executed to the first device so as to indicate the first device to determine whether NC is enabled; or alternatively

After the first device retransmits the data packet M times, the second device sends the indication information of whether NC is supported or not to the first device so as to indicate the first device to enable NC.

In one embodiment, the indication of whether NC is supported, the identification of NC enabled, or the indication of whether NC is performed, the NC configuration information, or whether NC configuration information is configured is determined based on at least one of:

Support capability for NC;

QoS transmission requirements;

Channel quality.

In one embodiment, the indication information of whether NC is supported, the NC-enabled flag, or the indication information of whether NC is executed, the NC configuration information, or the whether NC configuration information includes at least one of:

different coding configuration files are supported;

The maximum supported segment length L;

The maximum number of supported segments K;

In one embodiment, the QoS transmission requirements include QoS transmission requirements corresponding to at least one of: traffic, session, qoS flows, bearers, logical channels LCH.

In one embodiment, the channel quality comprises at least one of:

channel quality for each first device;

Channel quality for each LCH;

channel quality for each bearer;

channel quality for each carrier;

Channel quality for each MAC entity;

RSRQ；

RSRP。

in one embodiment, the channel quality is reported by the first device.

In one embodiment, the method further comprises: the second device determines NC inputs.

In one embodiment, the NC input is for at least one of: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, MAC entity.

In one embodiment, the NC input is obtained by at least one of: network configured, determined by the second device, predefined.

In one embodiment, the method further comprises: the second device receives the NC input.

In one embodiment, the second device receives NC input, including: the second device receives a data packet from the first device, the NC input being carried in a header of the data packet.

In one embodiment, the second device receives NC input, including: the second device receives auxiliary information reported from the first device, and the NC input is carried in the auxiliary information.

In one embodiment, the NC input is received by the second device from the first device via a user plane or a control plane.

In one embodiment, the NC input is determined by the second device according to at least one of:

Channel quality.

In one embodiment, the second device determines NC inputs comprising: the second device determines NC inputs using the segment length L and/or the number of supported NC data streams or packet processing number N.

In one embodiment, the NC input is determined by at least one of an NC layer, NC supporting functions, NC protocol stacks of the second device.

Specific examples of the second device performing method 400 in this embodiment may refer to the related descriptions about the network device in the above method 300, and are not repeated herein for brevity.

Fig. 5 is a schematic block diagram of a first device 500 in accordance with an embodiment of the application. The first device 500 may include: a receiving unit 510, configured to receive NC configuration information.

In one embodiment, the NC configuration information includes at least one of:

Physical layer parameters for NC PDU transmission;

A coding mode;

Indication information of whether NC is supported;

NC enabled identification;

indication information of whether NC is performed.

Support capability for NC;

QoS transmission requirements;

Channel quality.

different coding configuration files are supported;

The maximum supported segment length L;

The maximum number of supported segments K;

In one embodiment, the channel quality comprises at least one of:

channel quality for each first device;

Channel quality for each LCH;

channel quality for each bearer;

channel quality for each carrier;

Channel quality for each MAC entity;

RSRQ；

RSRP。

in one embodiment, the channel quality is reported by the first device.

In one embodiment, the apparatus further comprises: and the processing unit is used for determining NC input.

In one embodiment, the apparatus further comprises: and the NC unit is used for executing NC operation according to NC configuration and/or NC input.

In one embodiment, the apparatus further comprises: and a transmitting unit configured to transmit the NC input to the second device.

In one embodiment, the NC input is carried in a header of a data packet sent by the first device to the second device.

In one embodiment, the NC input is carried in auxiliary information reported by the first device to the second device.

Channel quality.

In one embodiment, the processing unit is further configured to determine NC inputs using the segment length L and/or the number of supported NC data streams or packet processing number N.

In one embodiment, the apparatus further comprises: and the PDCP copying unit is used for executing PDCP copying based on the NC according to the NC configuration information.

In one embodiment, the output of the NC algorithm is transmitted to lower layers via the same path or different paths.

In one embodiment, the apparatus further comprises: a data transmission unit, configured to, in a case where NC is enabled, or in a case where NC-based PDCP duplication is enabled, or in a case where NC replaces PDCP duplication, transmit data in a manner including at least one of:

The first device 500 of the embodiment of the present application can implement the corresponding functions of the first device in the foregoing embodiment of the method 300. The flow, function, implementation and beneficial effects corresponding to each module (sub-module, unit or assembly, etc.) in the first device 500 can be referred to the corresponding description in the above method embodiments, which are not repeated here. It should be noted that, the functions described in the respective modules (sub-modules, units, or components, etc.) in the first device 500 of the application embodiment may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-module, unit, component, etc.).

Fig. 6 is a schematic block diagram of a second device 600 in accordance with an embodiment of the present application. The second device 600 may include: a transmitting unit 610, configured to transmit NC configuration information.

In one embodiment, the NC configuration information includes at least one of:

Physical layer parameters for NC PDU transmission;

A coding mode;

Indication information of whether NC is supported;

NC enabled identification;

indication information of whether NC is performed.

In one embodiment, the transmitting unit is further configured to:

After the first device retransmits the data packet M times, sending the indication information of whether NC is supported, the identification enabled by NC or the indication information of whether NC is executed to the first device so as to indicate the first device to determine whether NC is enabled; or alternatively

After the first device retransmits the data packet M times, the first device is sent with the indication information of whether NC is supported or not, so as to indicate the first device to enable NC.

Support capability for NC;

QoS transmission requirements;

Channel quality.

different coding configuration files are supported;

The maximum supported segment length L;

The maximum number of supported segments K;

In one embodiment, the channel quality comprises at least one of:

channel quality for each first device;

Channel quality for each LCH;

channel quality for each bearer;

channel quality for each carrier;

Channel quality for each MAC entity;

RSRQ；

RSRP。

in one embodiment, the channel quality is reported by the first device.

In one embodiment, the apparatus further comprises: and the receiving unit is used for receiving the NC input.

In one embodiment, the receiving unit is further configured to receive a data packet from the first device, and the NC input is carried in a header of the data packet.

In one embodiment, the receiving unit is further configured to receive auxiliary information reported from the first device, where the NC input is carried in the auxiliary information.

Channel quality.

The second device 600 of the embodiment of the present application can implement the corresponding functions of the second device in the foregoing embodiment of the method 400. The flow, function, implementation and beneficial effects corresponding to each module (sub-module, unit or assembly, etc.) in the second device 600 can be referred to the corresponding description in the above method embodiments, which are not repeated here. It should be noted that, the functions described in the respective modules (sub-modules, units, or components, etc.) in the second device 600 of the application embodiment may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-module, unit, component, etc.).

The communication method of the embodiment of the application can be a method for supporting network coding, and has at least one of the following characteristics:

The network configures NC configuration, or PDCP duplication based on NC (NC-based PDCP duplication).

The network configures NC parameters, including all NC inputs (inputs). For example, NC parameters or NC inputs include at least one of: the encoding profile identifies (coding profile ID), the maximum supported segment length L, the maximum supported segment number K, the number of supported NC data streams or packet processing number N, NC algorithm, whether NC operations are to be performed.

The network configuration is based on an indication of use of the NC, or an indication of use of a duplication of the NC (NC-based duplication), and part or all of the NC input (NC input) is determined by the UE. For example: l, K, N, encoding profile ID.

The NC input is carried in the packet header to the base station and is used for indicating the coding mode of the current NC packet or ensuring the consistency of the use of the NC mechanism by the UE and the base station.

The NC input is carried in auxiliary information to a base station and is used for indicating the coding mode of the current NC packet or ensuring the consistency of the use of NC mechanisms by the UE and the base station.

The following are several examples of applications specific to NC-based PDCP duplication (NC-based PDCP duplication). However, when it is noted, the example or method is equally applicable to the case where the NC protocol or algorithm is applicable to the 3GPP protocol. For example, the example or method is equally applicable to cases where NC algorithms or protocols or functions are used (independent of or not limited to PDCP duplication transmission), to cases where NC is used to replace PDCP duplication, and so on. Not specifically listed here.

Example 1: the network sends the NC configuration to a terminal device, e.g. a UE. The NC configuration includes at least segment N, which may represent the number of data flows or the number of packet processes of the NC supported.

This example above is also applicable to downlink, and as shown in fig. 7, the specific implementation flow is as follows:

S11, configuring NC configuration information by the network equipment such as gNB. Specifically, the method comprises at least one of the following steps:

a) The indication information of the NC enabled or the indication information of the PDCP duplication (enable NC-based PDCP duplication) based on the NC is configured.

B) The bearer for which the configuration is intended, i.e. each (per) DRB uses an NC.

C) Configuring parameters used by the NC, including at least one of: segment N; a path (leg) identity used (e.g., RLC identity, carrier identity, MAC entity identity, etc.), a default path (default leg), a primary path (PRIMARY LEG), a secondary path (secondary leg), a secondary path (slave leg).

D) Optionally, the NC configuration information is carried in PDCP configuration information (PDCP-config) or radio bearer configuration information (radio bearer config).

E) Optionally, physical layer parameters configuring NC packet (packet) transmission, such as code rate, transmission power (transmission power), etc

F) Alternatively, a different coding scheme may be configured, such as a coding profile (similar to ROHC profile). Alternatively, the encoding mode may be per bearer config configured for granularity

G) Alternatively, the network may be configured to enable the NC after M retransmissions are performed. Or the network may indicate the enable NC after M retransmissions of the packet (e.g., HARQ NACK, RLC NACK, etc.).

Optionally, prior to S11, the gNB receives at least one of the following information, or determines whether NC-based PDCP duplication/configuration is enabled based on at least one of the following information (enable NC-based PDCP duplication/config NC-based PDCP duplication).

A) Support capability for NC. Or support capability for NC-based PDCP copying (NC-based PDCP duplication). This capability is reported by the UE.

Optionally, the capability further comprises: e.g. support different configuration files, support maximum segment length L (segment L), number of supported NC data streams or number of packet processing N (e.g. two or more paths of data NC)

B) And the service/QoS flow/bearing/LCH corresponds to the QoS transmission requirement. The transmission requirement is a reliability transmission requirement (e.g., availability, etc.).

E.g., traffic/QoS flow/bearer/LCH that exceeds a certain threshold transmission requirement, NC-based PDCP duplication is enabled.

C) Channel quality.

Optionally, the channel quality is reported by the UE.

Optionally, the channel quality is a channel quality Per (Per) UE, per LCH or Per bearer;

optionally, the channel quality is RSRQ/RSRP.

Optionally, NC-based PDCP duplication (enable NC-based PDCP duplication) is enabled when the channel quality is below a certain threshold.

S12. The UE performs NC or performs NC-based PDCP duplication (NC-based PDCP duplication) according to the NC configuration.

A) Specifically, the UE determines input parameters of the NC algorithm (may be abbreviated as NC input) using the number of data streams or the number of packet processes N (e.g., two or more data NC) supporting the maximum segment length L and/or the supported NC.

B) Alternatively, the output result of the NC algorithm is transmitted to the lower layer through the same path (leg), or different paths (leg).

C) Alternatively, in the case of enabling NC or NC-based PDCP duplication, the original data is transmitted from a default path (default leg), and NC-processed data (e.g., exclusive-or-processed data) is transmitted from a secondary path (secondary leg). Or the original data and NC-processed data may be transmitted through the same or different leg. For example, a and B are transmitted from a default path, a & B are transmitted from a secondary path, etc. Or, a and B are transmitted from the original DRB and the corresponding leg, while a & B are transmitted from the dedicated DRB and the corresponding leg. Such as a and a & B from the default path, B from the secondary path, etc. Or NC-processed data is transmitted from a dedicated DRB and its corresponding leg entity.

D) Alternatively, NC and PDCP duplication activates only one function. Or PDCP duplication (duplication) and NC-based PDCP duplication (NC-based PDCP duplication) activate only one function.

In this example, in the case of performing copy transmission using NC method, a method of determining NC parameters by the network is given, perfecting a configuration flow based on NC transmission or copy of NC (NC-based duplication).

Example 2: the Network (NW) sends the NC configuration to the UE. The UE determines NC parameters and carries the NC parameters to the base station through the packet header, and the NC parameters are used for indicating the coding mode of the current NC packet or realizing the synchronization of the UE and the base station.

This example above is also applicable to downlink, and as shown in fig. 8, the specific implementation flow is as follows:

S21, configuring NC configuration information by the network equipment such as gNB. Specifically, the method comprises at least one of the following steps:

a) The indication information enabling NC or the indication information enabling PDCP duplication based on NC is configured.

C) Configuring NC parameters including at least one of: a path (leg) identity used (e.g., RLC identity, carrier identity, MAC entity identity, etc.), a default path (default leg), a primary path (PRIMARY LEG), a secondary path (secondary leg), a secondary path (slave leg).

D) Alternatively, the NC configuration is carried in PDCP-config or radio bearer (radio bearer) config.

E) Optionally, physical layer parameters configuring NC data packet (packet) transmission, such as code rate, transmission power, etc

F) Alternatively, different coding modes may be configured, such as a coding profile (similar to ROHC (Robust Header Compression, reliable header compression). Alternatively, the coding scheme may be granularity configured for each bearer configuration (per bearer config) or may be related to channel quality. In addition, the coding scheme may be configured with granularity by at least one of a bearer group, a carrier, a PDCP entity, an RLC entity, an NC entity, user equipment, a user equipment group, a cell group, and a MAC entity.

G) Alternatively, the network may be configured to: after performing M retransmissions, the UE may activate the enable NC.

Optionally, before S21, the gNB receives the support capability for NC or the support capability for NC-based replication (NC-based duplication) reported by the UE.

Optionally, the capability further comprises: e.g. support different coding profile IDs, support maximum segment L, number of data streams or number of packet processing N of the NC supported (e.g. two or more paths of data NC)

S22, the UE determines NC input, performs NC or performs PDCP duplication (NC-based PDCP duplication) based on NC, and carries the NC input in a packet header (perform NC-based duplication, and include NC input IN PACKET HEADER to gNB) so as to ensure the consistency of the execution of NC mechanisms by the UE and the network. Optionally:

a) The NC input is at least one of the following: segment L; and/or the number of data streams or packet processing N of the supported NC (two or more data NC), encoding profile ID

I. Optionally, the UE determines the NC input according to information such as a service, qoS flow, a QoS transmission requirement corresponding to a bearer or LCH, a channel quality, and the like.

B) Optionally, the UE carries indication information in the packet header, which is used to indicate the value of N, and/or the value of L, and/or the code configuration file ID. The indication information is used for indicating the coding mode of the current NC packet or ensuring the consistency of the execution of NC mechanisms by the UE and the network.

C) Alternatively, the output of the NC algorithm is transmitted to the lower layer through the same leg, or different legs.

D) Alternatively, in the case of enabling NC or NC-based PDCP duplication, the original data is transmitted from a default path (default leg), and NC-processed data (e.g., exclusive-or-processed data) is transmitted from a secondary path (secondary leg). Or the original data and NC-processed data may be transmitted through the same or different leg. For example, a and B are transmitted from a default path, a & B are transmitted from a secondary path, etc. Or a and B are transmitted from the original DRB and the corresponding leg, while a & B are transmitted from the dedicated DRB and the corresponding leg. Such as a and a & B from the default path, B from the secondary path, etc. Or NC-processed data is transmitted from a dedicated DRB and its corresponding leg entity.

E) Alternatively, NC and PDCP duplication activates only one function. Or PDCP duplication and NC-based PDCP duplication activate only one function.

In this example, in the case of using NC transmission or performing copy transmission using NC, a method is provided in which the UE determines NC input and synchronizes the UE and the gNB through the packet header information indication, which provides flexibility in using NC-based copy (NC-based duplication) by the UE and also ensures synchronicity in using NC mechanism.

Example 3: the network sends the NC configuration to the UE. The UE determines the NC parameters and reports the NC parameters to the base station through auxiliary information, and the NC parameters are used for indicating the coding mode of the current NC packet or realizing the synchronization of the UE and the base station.

This example above is also applicable to downlink, and as shown in fig. 9, the specific implementation flow is as follows:

and S31.GNB configures NC configuration. Specifically, the method comprises at least one of the following steps:

C) Alternatively, the NC configuration is carried in PDCP-config or radio bearer (radio bearer) config.

D) Optionally, physical layer parameters configuring NC data packet (packet) transmission, such as code rate, transmission power, etc

E) Alternatively, a different coding scheme may be configured, such as a coding profile (similar to ROHC profile). Alternatively, the encoding mode may be per bearer config configured for granularity

F) Alternatively, the network may be configured such that after M retransmissions are performed, the UE may activate the enable NC.

Optionally, before S31, the gNB receives the support capability for NC or the support capability for NC-based replication (NC-based duplication) reported by the UE.

Optionally, the capability further comprises: e.g. support different coding profiles, support maximum segment L, number of data streams N of NC supported (two or more paths of data NC)

S32, the UE determines NC input and reports the NC input to the gNB through auxiliary information. Optionally:

a) The NC input includes at least one of: segment L, number of data flows or number of packet processing N of NC supported (two or more paths of data NC); the profile ID is encoded, and a path (leg) identity (e.g., RLC identity, carrier identity, MAC entity identity, etc.), default path (default leg), primary path (PRIMARY LEG), secondary path (secondary leg), and secondary path (slave leg) are used.

B) Optionally, the UE determines the NC input according to information such as a service, qoS flow, a QoS transmission requirement corresponding to a bearer or LCH, a channel quality, and the like.

C) Alternatively, if the UE reports the NC input, the UE may be all parameters used by the defined NC mechanism, or may be some of the parameters.

D) Optionally, the network determines NC input used by the NC mechanism according to the UE report, for indicating a coding mode of the current NC packet, or for implementing synchronization between the UE and the network.

Further, the network may modify NC parameters based on NC information reported by the UE, and configure the updated parameters to the UE.

S33. The ue performs NC-based PDCP copying according to S31 and S32.

A) Specifically, the UE determines input parameters of the NC algorithm (i.e., NC input), and performs NC operations.

B) Alternatively, the output of the NC algorithm is transmitted to the lower layer through the same leg, or different legs.

C) Alternatively, in the case of enabling NC or NC-based PDCP duplication, the original data is transmitted from the default leg, and NC-processed data (e.g., exclusive-or-processed data) is transmitted from the secondary leg. Or the original data and NC-processed data may be transmitted through the same or different leg. For example, a and B are transmitted from a default path, a & B are transmitted from a secondary path, etc. Or a and B are transmitted from the original DRB and the corresponding leg, while a & B are transmitted from the dedicated DRB and the corresponding leg. Such as a and a & B from the default path, B from the secondary path, etc. Or NC-processed data is transmitted from a dedicated DRB and its corresponding leg entity.

D) Optionally, PDCP duplication and NC-based PDCP duplication activate only one function.

In this example, in the case of performing copy transmission using NC transmission or using NC mode, a method for determining NC input by the UE is given, providing flexibility for the UE to use NC-based copy (NC-based duplication). The main difference between examples 2 and 3 is that this example reports NC parameters to the base station via the assistance information.

Fig. 10 is a schematic structural diagram of a communication apparatus 1000 according to an embodiment of the present application. The communication device 1000 comprises a processor 1010, from which the processor 1010 may call and run a computer program for causing the communication device 1000 to implement the method in an embodiment of the application.

In one implementation, the communication device 1000 may also include a memory 1020. Wherein the processor 1010 may invoke and run a computer program from the memory 1020 to cause the communication device 1000 to implement the method in embodiments of the present application.

The memory 1020 may be a separate device from the processor 1010 or may be integrated into the processor 1010.

In one embodiment, the communication device 1000 may further include a transceiver 1030, and the processor 1010 may control the transceiver 1030 to communicate with other devices, and in particular, may transmit information or data to other devices or receive information or data transmitted by other devices.

The transceiver 1030 may include, among other things, a transmitter and a receiver. The transceiver 1030 may further include an antenna, the number of which may be one or more.

In an implementation manner, the communication device 1000 may be a second device of the embodiment of the present application, and the communication device 1000 may implement a corresponding flow implemented by the second device in each method of the embodiment of the present application, which is not described herein for brevity.

In an implementation manner, the communication device 1000 may be a first device of the embodiment of the present application, and the communication device 1000 may implement a corresponding flow implemented by the first device in each method of the embodiment of the present application, which is not described herein for brevity.

Fig. 11 is a schematic block diagram of a chip 1100 according to an embodiment of the present application. The chip 1100 includes a processor 1110, and the processor 1110 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

In one embodiment, the chip 1100 may also include a memory 1120. Wherein the processor 1110 may call and run a computer program from the memory 1120 to implement the method performed by the first device or the second device in the embodiment of the present application.

Wherein the memory 1120 may be a separate device from the processor 1110 or may be integrated into the processor 1110.

In one embodiment, the chip 1100 may also include an input interface 1130. The processor 1110 may control the input interface 1130 to communicate with other devices or chips, and in particular, may obtain information or data sent by the other devices or chips.

In one embodiment, the chip 1100 may also include an output interface 1140. Wherein the processor 1110 may control the output interface 1140 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

In an implementation manner, the chip may be applied to the second device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the second device in each method in the embodiment of the present application, which is not described herein for brevity.

In an implementation manner, the chip may be applied to the first device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the first device in each method in the embodiment of the present application, which is not described herein for brevity.

The chips applied to the second device and the first device may be the same chip or different chips.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The processors mentioned above may be general purpose processors, digital Signal Processors (DSP), off-the-shelf programmable gate arrays (field programmable GATE ARRAY, FPGA), application SPECIFIC INTEGRATED Circuits (ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor.

The memory mentioned above may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an erasable programmable ROM (erasable PROM), an electrically erasable programmable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM).

It should be appreciated that the above memory is exemplary and not limiting, and for example, the memory in the embodiments of the present application may be static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (double DATA RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous connection dynamic random access memory (SYNCH LINK DRAM, SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Fig. 12 is a schematic block diagram of a communication system 1200 in accordance with an embodiment of the present application. The communication system 1200 includes a first device 1210 and a second device 1220. The first device 1210 is configured to receive NC configuration information. And a second device 1220 for transmitting NC configuration information. Wherein the first device 1210 may be adapted to implement the corresponding functionality implemented by a first device, e.g. a terminal device, in the above-described method, and the second device 1220 may be adapted to implement the corresponding functionality implemented by a second device, e.g. a network device, in the above-described method. For brevity, the description is omitted here.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, 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 loaded and executed on a computer, produces a flow or function in accordance with embodiments of the application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (Solid STATE DISK, SSD)), etc.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily appreciate variations or alternatives within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of communication, comprising:

The first device receives network coded NC configuration information.
The method of claim 1, wherein the NC configuration information is contained in at least one of:

Radio resource control, RRC, configuration information, radio bearer configuration information, packet data convergence protocol, PDCP, configuration information, radio link control, RLC, medium access control, MAC, configuration information, cell configuration information, logical channel configuration information.
The method of claim 1 or 2, wherein the NC configuration information is for at least one of: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, MAC entity.
A method according to any one of claims 1 to 3, wherein the NC configuration information includes at least one of:

the path identification used, the default path, the primary path, the secondary path.
The method of any of claims 1-4, wherein the NC configuration information includes at least one of:

the maximum supported segment length L, the maximum supported segment number K, the supported NC data flow number or data packet processing number N and the used coding configuration file identification.
The method of any of claims 1-5, wherein the NC configuration information includes at least one of:

physical layer parameters for NC packet data unit PDU transmission;

A coding mode;

Indication information of whether NC is supported;

NC enabled identification;

indication information of whether NC is performed.
The method of claim 6, wherein the physical layer parameters comprise at least one of: code rate, transmission power.
The method of claim 6 or 7, wherein the encoding means comprises an encoding algorithm or an encoding profile.
The method according to any of claims 6 to 8, wherein the encoding mode is configured with granularity of at least one of the following configurations: at least one of a bearer, a bearer group, a carrier group, a PDCP entity, an RLC entity, an NC entity, a user equipment group, a cell group, a MAC entity.
The method according to any of claims 6 to 9, wherein the indication information of whether NC is supported, the NC-enabled identification, or the indication information of whether NC is performed is used to instruct the first device to enable NC after M retransmissions of a data packet.
The method according to any one of claims 6 to 10, wherein the method further comprises:

The first device receives the indication information of whether NC is supported, the NC enabled mark or the indication information of whether NC is executed after the data packet is retransmitted for M times so as to determine whether NC is enabled; or the first device receives the indication information of whether NC is supported, the identification enabled by NC or the indication information of whether NC is executed after the data packet is retransmitted for M times, so as to enable NC.
The method of any of claims 6 to 11, wherein the indication of whether NC is supported, the NC configuration information, or whether NC configuration information is configured is determined based on at least one of:

Support capability for NC;

Quality of service, qoS, transmission requirements;

Channel quality.
The method of claim 12, wherein the support capability for NC comprises: support capability for NC-based PDCP duplication.
The method of claim 12 or 13, wherein the indication of whether NC is supported, the NC-enabled identification, or the indication of whether NC is performed, the NC configuration information, or the whether NC configuration information includes at least one of:

different coding configuration files are supported;

The maximum supported segment length L;

The maximum number of supported segments K;

the number of supported NC data streams or the number of data packet processing N.
The method of claim 13 or 14, wherein the QoS transmission requirements comprise QoS transmission requirements corresponding to at least one of: traffic, session, qoS flows, bearers, logical channels LCH.
The method of any of claims 13 to 15, wherein the QoS transmission requirements comprise reliability transmission requirements and/or latency requirements.
The method according to any of claims 13 to 16, wherein at least one of traffic, session, qoS flow, bearer, LCH of the transmission requirement exceeding a first threshold, NC enabled, NC configuration information configured or NC based PDCP duplication enabled.
The method of any of claims 13 to 17, wherein the channel quality comprises at least one of:

channel quality for each first device;

Channel quality for each LCH;

channel quality for each bearer;

channel quality for each carrier;

Channel quality for each MAC entity;

reference signal received quality RSRQ;

reference signal received power RSRP.
The method of claim 18, wherein the channel quality is reported by the first device.
The method of any of claims 13 to 19, wherein the channel quality is below a second threshold, enabling NC, configuring NC configuration information, or enabling NC-based PDCP duplication.
The method of any one of claims 1 to 20, wherein the method further comprises:

The first device determines NC inputs.
The method of claim 21, wherein the NC input comprises at least one of: the coding profile used identifies, the maximum supported segment length L, the maximum supported segment number K, the number of supported NC data streams or packet processing number N, NC algorithm, whether NC operations are to be performed.
The method of claim 21 or 22, wherein the NC input is for at least one of: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, MAC entity.
The method of any of claims 21 to 23, wherein the NC input, NC configuration information, or NC transmission path includes at least one of: the path identification used, the default path, the primary path, the secondary path.
The method of claim 24, wherein the path identification comprises at least one of: RLC identity, logical channel identity, MAC entity identity, carrier identity, PDCP identity.
The method of any of claims 21 to 25, wherein the NC input is obtained by at least one of: network configured, determined, predefined by the first device.
The method of any one of claims 1 to 26, wherein the method further comprises:

The first device performs NC operations according to NC configuration and/or NC input.
The method of any one of claims 21 to 27, wherein the method further comprises:

the first device sends the NC input to a second device.
The method of any of claims 28, wherein the NC input is sent by the first device to a second device through a user plane or control plane.
A method as claimed in any of claims 21 to 29, wherein the NC input is carried in a header of a data packet sent by the first device to the second device.
A method according to any of claims 21 to 30, wherein the NC input is carried in auxiliary information reported by the first device to a second device.
The method of any of claims 21 to 31, wherein the NC input is determined by the first device according to at least one of:

QoS transmission requirements corresponding to at least one of traffic, session, qoS flows, bearers, LCHs;

Channel quality.
The method of any of claims 21 to 32, wherein the first device determining NC input comprises:

The first device determines NC inputs using the segment length L and/or the number of supported NC data streams or packet processing number N.
The method of any of claims 21 to 33, wherein the NC input is determined by at least one of an NC layer, NC-capable functions, NC protocol stacks of the first device.
The method of any one of claims 1 to 34, wherein the method further comprises:

And the first equipment executes PDCP copying based on NC according to the NC configuration information.
The method of claim 35, wherein the output result of the NC algorithm is transmitted to a lower layer through the same path or different paths.
The method of claim 36, wherein the method further comprises:

in case of enabling NC, or in case of enabling NC-based PDCP duplication, or in case of NC replacing PDCP duplication, the manner in which the first device transmits data includes at least one of:

transmitting the original data or NC processed data from a default path or a main path;

data processed/generated using NC algorithms or protocols is transmitted from the secondary path or from the path.
The method of claim 37, wherein the NC-processed data is transmitted through a dedicated DRB and its corresponding path entity.
The method of claim 37 or 38 wherein one of a PDCP duplication and NC-based PDCP duplication function is activated.
The method of any one of claims 6 to 39, wherein the supporting NC comprises: enabling NC codec related operations, enabling NC transport, enabling NC codec, using capabilities of NC codec related operations, using capabilities of NC transport, using capabilities of NC codec, enabling NC-based PDCP duplication, or supporting capabilities of NC-based PDCP duplication.
A method of communication, comprising:

The second device transmits NC configuration information.
The method of claim 41, wherein the NC configuration information is included in at least one of:

RRC configuration information, radio bearer configuration information, PDCP configuration information, RLC configuration information, MAC configuration information, cell configuration information, logical channel configuration information.
The method of claim 41 or 42, wherein the NC configuration information is for at least one of: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, MAC entity.
The method of any of claims 41-43, wherein the NC configuration information includes at least one of:

the path identification used, the default path, the primary path, the secondary path.
The method of any of claims 41-44, wherein the NC configuration information includes at least one of:

the maximum supported segment length L, the maximum supported segment number K, the supported NC data flow number or data packet processing number N and the used coding configuration file identification.
The method of any of claims 41-45, wherein the NC configuration information includes at least one of:

Physical layer parameters for NC PDU transmission;

A coding mode;

Indication information of whether NC is supported;

NC enabled identification;

indication information of whether NC is performed.
The method of claim 46, wherein the physical layer parameters comprise at least one of: code rate, transmission power.
The method of claim 46 or 47, wherein the encoding means comprises an encoding algorithm or an encoding profile.
The method of any one of claims 46 to 48, wherein the encoding scheme is configured with granularity of at least one of: at least one of a bearer, a bearer group, a carrier group, a PDCP entity, an RLC entity, an NC entity, a user equipment group, a cell group, a MAC entity.
The method according to any one of claims 46 to 49, wherein the indication information of whether NC is supported, the NC-enabled flag, or the indication information of whether NC is performed is used to instruct the first device to enable NC after M retransmissions of a data packet.
The method of any one of claims 46 to 50, wherein the method further comprises:

After the first device retransmits a data packet for M times, the second device sends the indication information whether NC is supported, the NC enabled mark or the indication information whether NC is executed to the first device so as to indicate the first device to determine whether NC is enabled; or alternatively

And after the first device retransmits the data packet M times, the second device sends the indication information whether NC is supported or not to the first device so as to indicate the first device to enable NC.
The method of any of claims 46 to 51, wherein the indication of whether NC is supported, the NC-enabled identification, or the indication of whether NC is performed, the NC configuration information, or whether NC configuration information is configured is determined based on at least one of:

Support capability for NC;

QoS transmission requirements;

Channel quality.
The method of claim 52, wherein the support capability for NC includes at least one of: the ability to support NC protocols or NC functions or algorithms, the ability to support NC-based PDCP duplication, the ability of NC to replace PDCP duplication.
The method of claim 52 or 53, wherein the indication of whether NC is supported, the NC-enabled identification, or the indication of whether NC is performed, the NC configuration information, or the whether NC configuration information includes at least one of:

different coding configuration files are supported;

The maximum supported segment length L;

The maximum number of supported segments K;

the number of supported NC data streams or the number of data packet processing N.
The method of claim 53 or 54, wherein the QoS transmission requirements include QoS transmission requirements corresponding to at least one of: traffic, session, qoS flows, bearers, logical channels LCH.
A method according to any of claims 53 to 55, wherein the QoS transmission requirements comprise reliability transmission requirements and/or latency requirements.
A method as in any of claims 53-56, wherein at least one of traffic, session, qoS flow, bearer, LCH for transmission requirements exceeding a first threshold enables NC, configures NC configuration information, or enables NC-based PDCP duplication.
The method of any of claims 53-57, wherein the channel quality comprises at least one of:

channel quality for each first device;

Channel quality for each LCH;

channel quality for each bearer;

channel quality for each carrier;

Channel quality for each MAC entity;

RSRQ；

RSRP。
The method of claim 58, wherein the channel quality is reported by the first device.
A method as in any of claims 53-59, wherein the channel quality is below a second threshold, NC is enabled, NC configuration information is configured, or NC-based PDCP copying is enabled.
The method of any one of claims 40 to 60, wherein the method further comprises:

The second device determines NC inputs.
The method of claim 61, wherein the NC input includes at least one of: the coding profile used identifies, the maximum supported segment length L, the maximum supported segment number K, the number of supported NC data streams or packet processing number N, NC algorithm, whether NC operations are to be performed.
The method of claim 61 or 62, wherein the NC input is for at least one of: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, MAC entity.
The method of any of claims 61-63, wherein the NC input, NC configuration information, or NC transmission path includes at least one of: the path identification used, the default path, the primary path, the secondary path.
The method of claim 64, wherein the path identification comprises at least one of: RLC identity, logical channel identity, MAC entity identity, carrier identity, PDCP identity.
The method of any one of claims 61 to 65, wherein the NC input is obtained in a manner comprising at least one of: network configured, determined by the second device, predefined.
The method of any one of claims 61 to 66, wherein the method further comprises:

The second device receives the NC input.
The method of claim 67, wherein said second device receives NC input, comprising:

the second device receives a data packet from the first device, and the NC input is carried in a header of the data packet.
The method of claim 67 or 68, wherein the second device receives NC input, comprising:

And the second equipment receives auxiliary information reported by the first equipment, and the NC input is carried in the auxiliary information.
A method as claimed in any of claims 61 to 69, wherein the NC input is received by the second device from the first device via a user or control plane.
The method of any of claims 61 to 70, wherein the NC input is determined by the second device according to at least one of:

QoS transmission requirements corresponding to at least one of traffic, session, qoS flows, bearers, LCHs;

Channel quality.
The method of any of claims 61-71, wherein the second device determining NC input comprises:

the second device determines NC inputs using the segment length L and/or the number of supported NC data streams or packet processing number N.
The method of any of claims 61 to 72, wherein the NC input is determined by at least one of an NC layer, NC-capable functions, NC protocol stacks of the second device.
The method of any one of claims 45 to 73, wherein the supporting NC comprises: enabling NC codec related operations, enabling NC transport, enabling NC codec, using capabilities of NC codec related operations, using capabilities of NC transport, using capabilities of NC codec, enabling NC-based PDCP duplication, or supporting capabilities of NC-based PDCP duplication.
A first device, comprising: and the receiving unit is used for receiving the NC configuration information.
The apparatus of claim 75, wherein the NC configuration information is contained in at least one of:

RRC configuration information, radio bearer configuration information, PDCP configuration information, RLC configuration information, MAC configuration information, cell configuration information, logical channel configuration information.
The apparatus of claim 75 or 76, wherein the NC configuration information is for at least one of: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, MAC entity.
The apparatus of any one of claims 75 to 77, wherein the NC configuration information includes at least one of:

the path identification used, the default path, the primary path, the secondary path.
The apparatus of any of claims 75-78, wherein the NC configuration information includes at least one of:

the maximum supported segment length L, the maximum supported segment number K, the supported NC data flow number or data packet processing number N and the used coding configuration file identification.
The apparatus of any of claims 75-79, wherein the NC configuration information includes at least one of:

Physical layer parameters for NC PDU transmission;

A coding mode;

Indication information of whether NC is supported;

NC enabled identification;

indication information of whether NC is performed.
The device of claim 80, wherein the physical layer parameters comprise at least one of: code rate, transmission power.
The apparatus of claim 80 or 81, wherein the encoding means comprises an encoding algorithm or an encoding profile.
The apparatus of any one of claims 80 to 82, wherein the encoding scheme is configured with granularity of at least one of: at least one of a bearer, a bearer group, a carrier group, a PDCP entity, an RLC entity, an NC entity, a user equipment group, a cell group, a MAC entity.
The device of any one of claims 80 to 83, wherein the indication information of whether NC is supported, the NC-enabled flag, or the indication information of whether NC is performed is used to instruct the first device to enable NC after M retransmissions of a data packet.
The apparatus of any one of claims 80 to 84, wherein the apparatus further comprises:

The first device receives the indication information of whether NC is supported, the NC enabled mark or the indication information of whether NC is executed after the data packet is retransmitted for M times so as to determine whether NC is enabled; or the first device receives the indication information of whether NC is supported, the identification enabled by NC or the indication information of whether NC is executed after the data packet is retransmitted for M times, so as to enable NC.
The device of any of claims 80-85, wherein the indication of whether NC is supported, the NC configuration information, or whether NC configuration information is configured is determined based on at least one of:

Support capability for NC;

Quality of service, qoS, transmission requirements;

Channel quality.
The apparatus of claim 86, wherein the support capability for NC comprises at least one of: the ability to support NC protocols or NC functions or algorithms, the ability to support NC-based PDCP duplication, the ability of NC to replace PDCP duplication.
The device of claim 86 or 87, wherein the indication of whether NC is supported, the NC-enabled identification, or the indication of whether NC is performed, the NC configuration information, or the whether NC configuration information includes at least one of:

different coding configuration files are supported;

The maximum supported segment length L;

The maximum number of supported segments K;

the number of supported NC data streams or the number of data packet processing N.
The apparatus of claim 87 or 88, wherein the QoS transmission requirements comprise QoS transmission requirements corresponding to at least one of: traffic, session, qoS flows, bearers, logical channels LCH.
The apparatus of any one of claims 87 to 89, wherein the QoS transmission requirements comprise reliability transmission requirements and/or latency requirements.
The apparatus of any of claims 87 to 90, wherein at least one of traffic, session, qoS flow, bearer, LCH of the transmission requirement exceeding a first threshold enables NC, configures NC configuration information, or enables NC-based PDCP duplication.
The apparatus of any one of claims 87-91, wherein the channel quality comprises at least one of:

channel quality for each first device;

Channel quality for each LCH;

channel quality for each bearer;

channel quality for each carrier;

Channel quality for each MAC entity;

RSRQ；

RSRP。
The device of claim 92, wherein the channel quality is reported by the first device.
The apparatus of any of claims 87-93, wherein the channel quality is below a second threshold, NC is enabled, NC configuration information is configured, or NC-based PDCP copying is enabled.
The apparatus of any one of claims 75 to 94, wherein the apparatus further comprises:

And the processing unit is used for determining NC input.
The apparatus of claim 95, wherein the NC input includes at least one of: the coding profile used identifies, the maximum supported segment length L, the maximum supported segment number K, the number of supported NC data streams or packet processing number N, NC algorithm, whether NC operations are to be performed.
The apparatus of claim 95 or 96, wherein the NC input is for at least one of: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, MAC entity.
The device of any of claims 95-97, wherein the NC input, NC configuration information, or NC transmission path includes at least one of: the path identification used, the default path, the primary path, the secondary path.
The device of claim 98, wherein the path identification comprises at least one of: RLC identity, logical channel identity, MAC entity identity, carrier identity, PDCP identity.
The apparatus of any of claims 95-99, wherein the NC input is obtained in a manner that includes at least one of: network configured, determined, predefined by the first device.
The apparatus of any one of claims 75 to 100, wherein the apparatus further comprises:

And the NC unit is used for executing NC operation according to NC configuration and/or NC input.
The apparatus of any one of claims 95 to 101, wherein the apparatus further comprises:

and the sending unit is used for sending the NC input to the second equipment.
The device of any of claims 102, wherein the NC input is sent by the first device to a second device through a user plane or control plane.
The device of any of claims 95-103, wherein the NC input is carried in a header of a data packet sent by the first device to a second device.
The device of any of claims 95-104, wherein the NC input is carried in auxiliary information reported by the first device to a second device.
The device of any of claims 95-105, wherein the NC input is determined by the first device according to at least one of:

QoS transmission requirements corresponding to at least one of traffic, session, qoS flows, bearers, LCHs;

Channel quality.
The apparatus of any one of claims 95 to 106, wherein the processing unit is further configured to determine NC inputs using a segment length L and/or a number of supported NC data streams or packet processing numbers N.
The device of any of claims 95-107, wherein the NC input is determined by at least one of an NC layer, NC-capable functions, NC protocol stacks of the first device.
The apparatus of any one of claims 75 to 108, wherein the apparatus further comprises:

and the PDCP copying unit is used for executing PDCP copying based on NC according to the NC configuration information.
The apparatus of claim 109, wherein the output of the NC algorithm is transmitted to lower layers via the same path or different paths.
The apparatus of claim 110, wherein the apparatus further comprises:

A data transmission unit, configured to, in a case where NC is enabled, or in a case where NC-based PDCP duplication is enabled, or in a case where NC replaces PDCP duplication, transmit data in a manner including at least one of:

transmitting the original data or NC processed data from a default path or a main path;

data processed/generated using NC algorithms or protocols is transmitted from the secondary path or from the path.
The apparatus of claim 111, wherein the NC-processed data is transmitted through a dedicated DRB and its corresponding path entity.
The apparatus of claim 111 or 112, wherein one of a PDCP duplication and NC-based PDCP duplication function is activated.
The device of any one of claims 80-113, wherein the support NC comprises: enabling NC codec related operations, enabling NC transport, enabling NC codec, using capabilities of NC codec related operations, using capabilities of NC transport, using capabilities of NC codec, enabling NC-based PDCP duplication, or supporting capabilities of NC-based PDCP duplication.
A second device, comprising: and the sending unit is used for sending the NC configuration information.
The device of claim 115, wherein the NC configuration information is included in at least one of:

RRC configuration information, radio bearer configuration information, PDCP configuration information, RLC configuration information, MAC configuration information, cell configuration information, logical channel configuration information.
The device of claim 115 or 116, wherein the NC configuration information is for at least one of: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, MAC entity.
The apparatus of any of claims 115-117, wherein the NC configuration information includes at least one of:

the path identification used, the default path, the primary path, the secondary path.
The device of any of claims 115-118, wherein the NC configuration information includes at least one of:

the maximum supported segment length L, the maximum supported segment number K, the supported NC data flow number or data packet processing number N and the used coding configuration file identification.
The device of any of claims 115-119, wherein the NC configuration information includes at least one of:

Physical layer parameters for NC PDU transmission;

A coding mode;

Indication information of whether NC is supported;

NC enabled identification;

indication information of whether NC is performed.
The device of claim 120, wherein the physical layer parameters comprise at least one of: code rate, transmission power.
The apparatus of claim 120 or 121, wherein the encoding means comprises an encoding algorithm or an encoding profile.
The apparatus of any one of claims 120 to 122, wherein the encoding scheme is configured with granularity of at least one of: at least one of a bearer, a bearer group, a carrier group, a PDCP entity, an RLC entity, an NC entity, a user equipment group, a cell group, a MAC entity.
The device of any one of claims 120-123, wherein the indication of whether NC is supported, the NC-enabled identification, or the indication of whether NC is performed is used to indicate that the first device enables NC after M retransmissions of a data packet.
The device of any one of claims 120-124, wherein the transmitting unit is further configured to:

after the first device retransmits the data packet M times, sending the indication information of whether NC is supported, the NC enabled mark or the indication information of whether NC is executed to the first device so as to indicate the first device to determine whether NC is enabled; or alternatively

After the first device retransmits the data packet M times, the indication information of whether NC is supported is sent to the first device so as to indicate the first device to enable NC.
The device of any of claims 120-125, wherein the indication of whether NC is supported, the NC-enabled identification, or the indication of whether NC is performed, the NC configuration information, or whether NC configuration information is configured is determined based on at least one of:

Support capability for NC;

QoS transmission requirements;

Channel quality.
The device of claim 126, wherein the support capability for NC includes at least one of: the ability to support NC protocols or NC functions or algorithms, the ability to support NC-based PDCP duplication, the ability of NC to replace PDCP duplication.
The device of claim 126 or 127, wherein the indication of whether NC is supported, the NC-enabled identification, or the indication of whether NC is performed, the NC configuration information, or the whether NC configuration information includes at least one of:

different coding configuration files are supported;

The maximum supported segment length L;

The maximum number of supported segments K;

the number of supported NC data streams or the number of data packet processing N.
The apparatus of claim 127 or 128, wherein the QoS transmission requirements comprise QoS transmission requirements corresponding to at least one of: traffic, session, qoS flows, bearers, logical channels LCH.
The apparatus of any one of claims 127-129, wherein the QoS transmission requirements comprise reliability transmission requirements and/or latency requirements.
The apparatus of any one of claims 127-130, wherein at least one of traffic, session, qoS flow, bearer, LCH for transmission requirements exceeding a first threshold enables NC, configures NC configuration information, or enables NC-based PDCP duplication.
The apparatus of any one of claims 127-131, wherein the channel quality comprises at least one of:

channel quality for each first device;

Channel quality for each LCH;

channel quality for each bearer;

channel quality for each carrier;

Channel quality for each MAC entity;

RSRQ；

RSRP。
The device of claim 132, wherein the channel quality is reported by the first device.
The apparatus of any of claims 127-133, wherein the channel quality is below a second threshold, NC is enabled, NC configuration information is configured, or NC-based PDCP copying is enabled.
The apparatus of any one of claims 114-134, wherein the apparatus further comprises:

And the processing unit is used for determining NC input.
The device of claim 135, wherein the NC input includes at least one of: the coding profile used identifies, the maximum supported segment length L, the maximum supported segment number K, the number of supported NC data streams or packet processing number N, NC algorithm, whether NC operations are to be performed.
The device of claim 135 or 136, wherein the NC input is for at least one of: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, MAC entity.
The device of any of claims 135-137, wherein the NC input, NC configuration information, or NC transmission path includes at least one of: the path identification used, the default path, the primary path, the secondary path.
The device of claim 138, wherein the path identification comprises at least one of: RLC identity, logical channel identity, MAC entity identity, carrier identity, PDCP identity.
The apparatus of any of claims 135-139, wherein the NC input is obtained in a manner that includes at least one of: network configured, determined by the second device, predefined.
The apparatus of any one of claims 135-140, wherein the apparatus further comprises:

And the receiving unit is used for receiving the NC input.
The device of claim 141, wherein the receiving unit is further configured to receive a data packet from a first device, the NC input being carried in a header of the data packet.
The device of claim 141 or 142, wherein the receiving unit is further configured to receive auxiliary information reported from the first device, and the NC input is carried in the auxiliary information.
The device of any of claims 135-143, wherein the NC input is received by the second device from a first device via a user plane or a control plane.
The device of any of claims 135-144, wherein the NC input is determined by the second device according to at least one of:

QoS transmission requirements corresponding to at least one of traffic, session, qoS flows, bearers, LCHs;

Channel quality.
The device of any one of claims 135 to 145, wherein the processing unit is further configured to determine NC inputs using a segment length L and/or a number of supported NC data streams or packet processing numbers N.
The device of any of claims 135-146, wherein the NC input is determined by at least one of an NC layer, NC-capable functions, and an NC protocol stack of the second device.
The device of any of claims 119-147, wherein the support NC comprises: enabling NC codec related operations, enabling NC transport, enabling NC codec, using capabilities of NC codec related operations, using capabilities of NC transport, using capabilities of NC codec, enabling NC-based PDCP duplication, or supporting capabilities of NC-based PDCP duplication.
A first device, comprising: a processor and a memory for storing a computer program, the processor for invoking and running the computer program stored in the memory to cause the first device to perform the method of any of claims 1 to 40.
A second device, comprising: a processor and a memory for storing a computer program, the processor for invoking and running the computer program stored in the memory to cause the second device to perform the method of any of claims 41 to 74.
A chip, comprising: a processor for calling and running a computer program from memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 40 or 41 to 74.
A computer readable storage medium storing a computer program which, when executed by a device, causes the device to perform the method of any one of claims 1 to 40 or 41 to 74.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 40 or any one of claims 41 to 74.
A computer program which causes a computer to perform the method of any one of claims 1 to 40 or 41 to 74.