WO2023123335A1 - Procédé et dispositif de communication - Google Patents

Procédé et dispositif de communication Download PDF

Info

Publication number
WO2023123335A1
WO2023123335A1 PCT/CN2021/143639 CN2021143639W WO2023123335A1 WO 2023123335 A1 WO2023123335 A1 WO 2023123335A1 CN 2021143639 W CN2021143639 W CN 2021143639W WO 2023123335 A1 WO2023123335 A1 WO 2023123335A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration information
following
input
path
entity
Prior art date
Application number
PCT/CN2021/143639
Other languages
English (en)
Chinese (zh)
Inventor
付喆
张博源
卢前溪
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN202180103176.8A priority Critical patent/CN118056364A/zh
Priority to PCT/CN2021/143639 priority patent/WO2023123335A1/fr
Publication of WO2023123335A1 publication Critical patent/WO2023123335A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path

Definitions

  • the present application relates to the communication field, and more specifically, to a communication method and device.
  • Network coding (network coding, NC) is an information exchange technology that combines routing and coding.
  • Network coding mainly includes: each node in the network performs linear or nonlinear processing on the information received on each data stream, and then forwards it to the downstream node, and the intermediate node plays the role of encoder or signal processor. It is necessary to consider how to use network coding to improve the reliability of data transmission.
  • Embodiments of the present application provide a communication method and device, which can improve the reliability of data transmission.
  • An embodiment of the present application provides a communication method, including: a first device receives network coding NC configuration information.
  • An embodiment of the present application provides a communication method, including: sending NC configuration information by a second device.
  • An embodiment of the present application provides a first device, including: a receiving unit, configured to receive NC configuration information.
  • An embodiment of the present application provides a second device, including: a sending unit, configured to send NC configuration information.
  • An embodiment of the present application provides a first device, including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to invoke and run the computer program stored in the memory, so that the first device executes the communication method in any embodiment of the present application.
  • An embodiment of the present application provides a second device, including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory, so that the second device executes the communication method in any embodiment of the present application.
  • An embodiment of the present application provides a chip configured to implement the above communication method.
  • the chip includes: a processor, configured to invoke and run a computer program from a memory, so that a device installed with the chip executes the communication method of any embodiment of the present application.
  • An embodiment of the present application provides a computer-readable storage medium, which is used to store a computer program, and when the computer program is executed by a device, the device executes the communication method of any embodiment of the present application.
  • An embodiment of the present application provides a computer program product, including computer program instructions, where the computer program instructions cause a computer to execute the communication method of any embodiment of the present application.
  • An embodiment of the present application provides a computer program that, when running on a computer, causes the computer to execute the communication method of any embodiment of the present application.
  • the reliability of data transmission can be improved through network coding.
  • Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.
  • Figure 2 is the PDU session in the 5GS system and the data flow (QoS Flow) it contains.
  • Fig. 3 is a schematic flowchart of a communication method according to an embodiment of the present application.
  • Fig. 4 is a schematic flowchart of a communication method according to another embodiment of the present application.
  • Fig. 5 is a schematic block diagram of a first device according to an embodiment of the present application.
  • Fig. 6 is a schematic block diagram of a second device according to an embodiment of the present application.
  • Fig. 7 is a flow chart of Example 1 of the communication method according to the embodiment of the present application.
  • Fig. 8 is a flow chart of Example 2 of the communication method according to the embodiment of the present application.
  • Fig. 9 is a flow chart of Example 3 of the communication method according to the 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 present application.
  • Fig. 12 is a schematic block diagram of a communication system according to an embodiment of the present application.
  • the technical solution of the embodiment of the present application can be applied to various communication systems, such as: Global System of Mobile communication (Global System of Mobile communication, GSM) system, code division multiple access (Code Division Multiple Access, CDMA) system, broadband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system , New Radio (NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) on unlicensed spectrum unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunications System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.
  • GSM Global System of Mobile
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • V2V Vehicle to Vehicle
  • V2X Vehicle to everything
  • the communication system in the embodiment of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, can also be applied to a dual connectivity (Dual Connectivity, DC) scenario, and can also be applied to an independent (Standalone, SA) Network deployment scene.
  • Carrier Aggregation, CA Carrier Aggregation
  • DC Dual Connectivity
  • SA independent Network deployment scene
  • the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to a licensed spectrum , where the licensed spectrum can also be considered as a non-shared spectrum.
  • the embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, wherein the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • user equipment User Equipment, UE
  • access terminal user unit
  • user station mobile station
  • mobile station mobile station
  • remote station remote terminal
  • mobile device user terminal
  • terminal wireless communication device
  • wireless communication device user agent or user device
  • the terminal device can be a station (STAION, ST) in the WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, next-generation communication systems such as terminal devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.
  • STAION, ST Session Initiation Protocol
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites) superior).
  • the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home.
  • a virtual reality (Virtual Reality, VR) terminal device an augmented reality (Augmented Reality, AR) terminal Equipment
  • wireless terminal equipment in industrial control wireless terminal equipment in self driving
  • wireless terminal equipment in remote medical wireless terminal equipment in smart grid
  • wireless terminal equipment in transportation safety wireless terminal equipment in smart city, or wireless terminal equipment in smart home.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.
  • the network device may be a device for communicating with the mobile device, and the network device may be an access point (Access Point, AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA , or a base station (NodeB, NB) in WCDMA, or an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and an NR network
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • Evolutional Node B, eNB or eNodeB evolved base station
  • LTE Long Term Evolutional Node B, eNB or eNodeB
  • gNB network equipment in the network or the network equipment in the future evolved PLMN network or the network equipment in the NTN network, etc.
  • the network device may have a mobile feature, for example, the network device may be a mobile device.
  • the network equipment may be a satellite or a balloon station.
  • the satellite can be a low earth orbit (low earth orbit, LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous earth orbit (geosynchronous earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite. ) Satellite etc.
  • the network device may also be a base station installed on land, water, and other locations.
  • the network device may provide services for a cell, and the terminal device communicates with the network device through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device ( For example, a cell corresponding to a base station), the cell may belong to a macro base station, or may belong to a base station corresponding to a small cell (Small cell), and the small cell here may include: a metro cell (Metro cell), a micro cell (Micro cell), a pico cell ( Pico cell), Femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • the transmission resources for example, frequency domain resources, or spectrum resources
  • the cell may be a network device (
  • the cell may belong to a macro base station, or may belong to a base station corresponding to a small cell (Small cell)
  • the small cell here may include: a metro cell (Metro cell), a micro cell (Micro
  • FIG. 1 exemplarily shows a communication system 100 .
  • the communication system includes a network device 110 and two terminal devices 120 .
  • the communication system 100 may include multiple network devices 110, and the coverage of each network device 110 may include other numbers of terminal devices 120, which is not limited in this embodiment of the present application.
  • the communication system 100 may also include other network entities such as a mobility management entity (Mobility Management Entity, MME) and an access and mobility management function (Access and Mobility Management Function, AMF). Examples are not limited to this.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • the network equipment may further include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with access network devices.
  • the access network device may be a long-term evolution (long-term evolution, LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA- Evolved base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called “small base station”), pico base station, access point (access point, AP), Transmission point (transmission point, TP) or new generation base station (new generation Node B, gNodeB), etc.
  • LTE long-term evolution
  • NR next-generation
  • LAA- Evolved base station evolutional node B, abbreviated as eNB or e-NodeB
  • eNB next-generation
  • NR next-generation
  • a device with a communication function in the network/system in the embodiment of the present application may be referred to as a communication device.
  • the communication equipment may include network equipment and terminal equipment with communication functions. It may include other devices in the communication system, such as network controllers, mobility management entities and other network entities, which are not limited in this embodiment of the present application.
  • the "indication" mentioned in the embodiments of the present application may be a direct indication, may also be an indirect indication, and may also mean that there is an association relationship.
  • a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.
  • the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or that there is an association between the two, or that it indicates and is indicated, configuration and is configuration etc.
  • NC is used for 3GPP (NC for 3GPP)
  • NC network coding
  • PDCP Packet Data Convergence Protocol
  • Research on layers that perform network coding includes research on protocol stacks for network coding based on PDCP replication, e.g., between the network coding layers between Radio Link Control (RLC) and PDCP (RAN2). Study of protocol stacks (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))
  • the main idea of network coding includes: each node in the network performs linear or nonlinear processing on the information received on each data stream, and then forwards it to the downstream node, and the intermediate node plays the role of encoder or signal processor.
  • the intermediate node may combine the data byte groups (x, y) on multiple paths into a group of data byte groups (xXORy) through logical operation processing (such as XOR processing) for transmission.
  • logical operation processing such as XOR processing
  • the receiving terminal can solve each data bit group (x, y) in (xXORy) through logic operation processing.
  • the number N of data streams or data packet processing supported by the NC is 2.
  • network coding may have great gains in the following scenarios:
  • the simple forwarding strategy will make the transmission rate decrease exponentially with the increase of the packet loss rate, and the network coding can basically reach the network capacity.
  • the QoS mechanism of 5GS is needed.
  • one or more QoS Flows (data flows) need to be established, and different data flows correspond to different QoS parameters.
  • QoS parameters are usually used to indicate the characteristics of QoS Flow.
  • QoS parameters can include but are not limited to: 5QI, Address Resolution Protocol (Address Resolution Protocol, ARP), Guaranteed Flow bit rate (GuaranteedFlow Bit Rate, GFBR), maximum flow 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, Resource Type, Maximum Data Burst Volume, UE-Aggregate Maximum Bit Rate (AMBR) , Session (Session)-AMBR, etc.
  • a filter (or called an SDF template) contains parameters describing the characteristics of a data packet, and is used to filter out a specific data packet bound to a specific QoS Flow.
  • a commonly used Filter is an IP quintuple, that is, source and destination IP addresses, source and destination port numbers, and protocol type.
  • the reliability requirements of Qos Flow are different, and the Qos Flow with relatively high reliability requirements can improve reliability and/or reduce delay through the NC function.
  • different services have different reliability and/or delay requirements, which can be achieved by using NC.
  • the embodiment of the present application may provide a communication method, including acquiring NC configuration, or acquiring NC input, or setting an NC input mode when using an NC function or an NC protocol.
  • the physical usage of the NC function is to obtain NC configuration when using NC-based duplication or NC-instead duplication, or obtain NC input, Or, set the way of NC input.
  • Fig. 3 is a schematic flowchart of a communication method 300 according to an embodiment of the present application.
  • the method can optionally be applied to the system shown in Fig. 1, but is not limited thereto.
  • the method includes at least some of the following.
  • the first device receives network coding NC configuration information.
  • NC may also be referred to as a network codec.
  • the first device may be a terminal device such as a UE.
  • the first device may be a sending end device or a receiving end device.
  • the second device at the peer end of the first device may be a network device.
  • the second device may be a sending end device or a receiving end device.
  • the first device is a sending end device
  • the second device is a receiving end device.
  • the first device is a receiving end device.
  • the NC configuration information is included in at least one of the following: radio resource control (Radio Resource Control, RRC) configuration information, radio bearer configuration information, PDCP configuration information, RLC configuration information, media access control ( Media Access Control (MAC) configuration information, cell configuration information, logical channel configuration information.
  • RRC Radio Resource Control
  • RLC Physical Downlink Control
  • MAC Media Access Control
  • the NC configuration information is for at least one of the following: bearer (Radio Bearer, RB), PDCP entity, RLC entity, NC entity, user equipment, cell, and MAC entity.
  • the NC configuration information is for at least one of the following: each or at least one bearer, each or at least one bearer group, each or at least one PDCP entity, each or at least one PDCP entity group, each or At least each or at least one PDCP entity group, one 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, each or at least one cell group, Each or at least one MAC entity, each or at least one MAC entity group, each or at least one carrier, each or at least one carrier group.
  • the bearer may be a user plane bearer ((user) Data Radio Bearer, DRB). Of course, it does not rule out that it can be used for bearing the control plane.
  • the NC configuration information includes at least one of the following: a used path (leg) identifier, a default path (default leg), a primary path (primary leg), a secondary path (secondary leg), a slave path ( slave leg).
  • the NC configuration information includes at least one of the following: the maximum segment length L supported, the maximum segment number K supported, the number of data streams or the number of data packets processed by the NC supported N, The encoding profile ID to use.
  • the obtained segmented data packet length is less than or equal to the supported maximum segment length L.
  • the number of data packets obtained by segmenting a data packet may be N.
  • a packet is received, it is divided into two packets according to L. The number of these two packets is N.
  • use fountain code for example, the configuration file flag is 1
  • NC encoding may be performed on the received N data packets using fountain code (for example, the configuration file identifier is 1).
  • a padding operation may also be performed to ensure that the sizes of the two data packets match or are equal.
  • the NC configuration information includes at least one of the following:
  • the indication information of whether to support NC may indicate different states through different values. For example, if the indication information of whether to support NC is a first value, it indicates that NC protocol or NC function is supported; if it is a second value, it indicates that NC protocol or NC function is not supported.
  • the NC-enabled flag may represent different states through different flags.
  • the NC enabled flag is the first flag, which means that the NC is enabled, the NC protocol is enabled, or the NC protocol function is used; it is the second flag, which means that the NC function is not used, or the NC protocol function is not used, or the NC protocol is not used.
  • the appearance of a specific information element means enabling, and the absence means disenabling.
  • the indication information of whether to execute NC may indicate different states through different values. For example, if the indication information of whether to execute NC is a first value, it indicates that an NC operation is performed; if it is a second value, it indicates that an NC operation is not performed.
  • the presence of a specific IE means execution, and the absence of specific IE means no execution.
  • the physical layer parameters include at least one of the following: code rate and transmission power.
  • the code rate may be a bit rate, indicating the number of transmitted bits per unit time.
  • the transmission power may represent the power used to transmit the NC PDU.
  • the encoding method includes an encoding algorithm or an encoding configuration file.
  • the encoding manner is configured at a granularity of bearer configuration.
  • the encoding mode may also be configured at least one of bearer group, carrier, carrier group, PDCP entity, RLC entity, NC entity, user equipment, user equipment group, cell, cell group, and MAC entity as a granular configuration.
  • the indication information of whether to support the NC, the identification of the NC enablement, or the indication information of whether to execute the NC are used to instruct the first device to enable the NC after M times of retransmission of the data packet.
  • the first device enables the NC after M retransmissions of the data packet according to the indication information of whether the NC is supported, the identifier of the NC enabled, or the indication information of whether the NC is executed in the received NC configuration information.
  • the method further includes: the first device receives the indication information of whether to support NC, the identification of the NC enablement, or the indication information of whether to execute NC after the data packet is retransmitted M times, to Determine whether to enable the NC; or, after the data packet is retransmitted M times, the first device receives the indication information of whether to support the NC, the identification of the NC enablement, or the indication information of whether to execute the NC, so as to enable the NC.
  • the first device receives the NC configuration information after the data packet is retransmitted M times, if the NC configuration information includes the indication information of whether to support the NC, the identification of the NC enablement, or the indication information of whether to execute the NC, it indicates that the If the NC is enabled, it can be determined to enable the NC. Otherwise, NC is not enabled.
  • the first device receives the NC configuration information including the indication information of whether to support the NC, the identification of the NC enablement, or the indication information of whether to execute the NC after the data packet is retransmitted for M times, the NC is enabled.
  • the indication information of whether to support the NC, the NC configuration information or whether to configure the NC configuration information is determined based on at least one of the following:
  • the capability to support NC includes at least one of the following: capability to support NC protocol or NC function or algorithm, capability to support NC-based PDCP replication, and capability to support NC to replace PDCP replication.
  • the ability to support NC protocol or NC function or algorithm, or the ability to support NC to replace PDCP replication, or the ability to support NC-based PDCP replication may also include supporting different coding profiles (coding profiles), supported At least one of the maximum segment length L, the maximum supported segment number K, the number of data streams supported by the NC or the number N of data packets to be processed.
  • coding profiles coding profiles
  • the indication information of whether to support the NC, the identification of the NC enablement, or the indication information of whether to execute the NC, the NC configuration information, or the NC configuration information includes at least one of the following:
  • the number of data streams or data packet processing N supported by the NC is the number of data streams or data packet processing N supported by the NC.
  • the QoS transmission requirement includes a QoS transmission requirement corresponding to at least one of the following: service, session (session), QoS flow, bearer, and logical channel (Logical CHannel, LCH).
  • the QoS transmission requirement includes a reliability transmission requirement and/or a delay requirement.
  • the threshold of the QoS transmission requirement can be set, and the threshold of different transmission requirements can be different. For example, if the service transmission requirement exceeds the corresponding service transmission threshold, the NC is enabled. If the transmission demand of QoS flow exceeds the corresponding QoS flow transmission threshold, enable NC. If the bearer transmission requirement exceeds the corresponding bearer transmission threshold, the NC is enabled. If the transmission demand of the LCH exceeds the corresponding LCH transmission threshold, the NC is enabled. If the reliability transmission requirement exceeds the reliability threshold, enable NC. If the delay requirement exceeds the delay threshold, enable NC. In one approach, NC functions/protocols can be directly enabled (independent of or not limited to PDCP copy transport). In another implementation manner, NC-based PDCP replication can be enabled.
  • the channel quality includes at least one of the following:
  • Reference Signal Received Quality Reference Signal Received Quality (Reference Signal Received Quality, RSRQ);
  • Reference Signal Received Power Reference Signal Received Power
  • the channel quality is reported by the first device.
  • the method further includes: the first device determining an NC input.
  • NC input may be referred to as NC input information, NC input indication, NC input command, NC input element, and the like.
  • NC inputs may include input parameters for NC algorithms.
  • the NC input may further include data packets received from an upper layer or an upper sublayer.
  • the NC input includes at least one of the following: the code configuration file identifier used, the maximum segment length L supported, the maximum segment number K supported, the number of data streams supported by the NC, or Number of data packets processed N, NC algorithm, whether to perform NC operation.
  • the NC input is for at least one of the following: a bearer, a PDCP entity, an RLC entity, an NC entity, a user equipment, a cell, and a MAC entity.
  • the NC input is for at least one of the following: each bearer, each PDCP entity, each RLC entity, each NC entity, each user equipment, each cell, and each MAC entity.
  • the bearer may be a user plane bearer. Of course, it does not rule out that it can be used for bearing the control plane.
  • the NC input, NC configuration information or NC transmission path includes at least one of the following: a used path identifier, a default path, a primary path, a secondary path, and a secondary path.
  • the path identifier includes at least one of the following: an RLC identifier, a logical channel identifier, a MAC entity identifier, a carrier identifier, and a PDCP identifier.
  • the path identifier used to transmit the NC PDU can be configured through the NC configuration information.
  • different paths can be configured for the NC PDU through the NC configuration information.
  • the path of the segmented NC PDU is the master path
  • the path of the non-segmented NC PDU is the slave path.
  • the path of the NC PDU that is filled is the default path
  • the path of the NC PDU that is not filled is the secondary path.
  • the path of the NC PDU directly adding the header is the default path
  • the path of the NC PDU adding the header after XOR is the secondary path.
  • the protocol layer or the protocol function randomly selects the path to be used by the specific data packet (transmitting from the path corresponding to the configured path identifier).
  • the acquisition manner of the NC input includes at least one of the following: configured by the network, determined by the first device, and predefined.
  • the method further includes: the first device executes NC operations according to NC configuration and/or NC input.
  • the NC operations may include network encoding and/or network decoding.
  • the NC operation performed by the sending end device may include an encoding operation and/or some preparatory operations before encoding, such as segmentation (Segment), padding (Padding), and the like.
  • the peer end of the sending end device may be a receiving end device, and the NC operation performed by the receiving end device may include a decoding operation and/or some preparatory operations before decoding, such as buffering, reorganization, concatenation, and defilling.
  • the method further includes: the first device sending the NC input to the second device.
  • the NC input is sent by the first device to the second device through a user plane or a control plane.
  • the NC input is carried in a header of a data packet sent by the first device to the second device.
  • the NC input is carried in auxiliary information reported by the first device to the second device.
  • the assistance information may be UE assistance information (assistance information).
  • the auxiliary information may be an RRC message.
  • the NC input is determined by the first device according to at least one of the following:
  • QoS transmission requirements corresponding to at least one of service, session, QoS flow, bearer, and LCH;
  • the determining the NC input by the first device includes: determining the NC input by the first device using the segment length L and/or the number of data streams or the number N of data packets processed by the NC supported.
  • the NC input is determined by at least one of the NC layer of the first device, the function supporting NC, and the NC protocol stack.
  • the method further includes: performing, by the first device, NC-based PDCP replication according to the NC configuration information.
  • the output result of the NC algorithm is transmitted to the lower layer through 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.
  • the method further includes: when the NC is enabled, or when the NC-based PDCP replication is enabled, or when the NC replaces the PDCP replication, the first device transmits
  • the way of data includes at least one of the following:
  • Data processed/generated using NC algorithms or protocols is transmitted from the secondary path or from the secondary path.
  • the data processed by the NC may include the data obtained by adding the NC header to the original data.
  • the data generated by using the NC algorithm or protocol may include the original data A XOR original data B, and the data after adding the header.
  • the data processed by the NC is transmitted through a dedicated DRB and its corresponding path entity.
  • one of the functions of PDCP replication and NC-based PDCP replication is activated.
  • the NC support includes: enabling NC codec-related operations, enabling NC transmission methods, enabling NC codecs, the ability to use NC codec-related operations, the ability to use NC transmission methods, and the ability to use NC codecs.
  • the capability of encoding and decoding enables the NC-based PDCP replication, or supports the NC-based PDCP replication.
  • Fig. 4 is a schematic flowchart of a communication method 400 according to an embodiment of the present application.
  • the method can optionally 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 and the method 300 have the same meanings, and reference may be made to the relevant descriptions in the above method 300 , and details are not repeated here for brevity.
  • the second device sends NC configuration information.
  • NC may also be referred to as a network codec.
  • the second device may be a network device such as a base station.
  • the second device may be a sending end device or a receiving end device.
  • the first device opposite to the second device may be a terminal device.
  • the first device may be a sending end device or a receiving end device.
  • the first device is a sending end device
  • the second device is a receiving end device.
  • the first device is a receiving end device.
  • the NC configuration information is included in at least one of the following: RRC configuration information, radio bearer configuration information, PDCP configuration information, RLC configuration information, MAC configuration information, cell configuration information, logical channel configuration information.
  • the NC configuration information is for at least one of the following: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, and MAC entity.
  • the NC configuration information is for at least one of the following: each or at least one bearer, each or at least one bearer group, each or at least one PDCP entity, each or at least one PDCP entity group, each or At least each or at least one PDCP entity group, one 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, each or at least one cell group, Each or at least one MAC entity, each or at least one MAC entity group, each or at least one carrier, each or at least one carrier group.
  • the NC configuration information includes at least one of the following: used path identifier, default path, primary path, secondary path, and secondary path.
  • the NC configuration information includes at least one of the following: the maximum segment length L supported, the maximum segment number K supported, the number of data streams or the number of data packets processed by the NC supported N, The encoding profile ID to use.
  • the NC configuration information includes at least one of the following:
  • the physical layer parameters include at least one of the following: code rate and transmission power.
  • the encoding method includes an encoding algorithm or an encoding configuration file.
  • the encoding manner is configured at a granularity of bearer configuration.
  • the encoding mode may also be configured at least one of bearer group, carrier, carrier group, PDCP entity, RLC entity, NC entity, user equipment, user equipment group, cell, cell group, and MAC entity as a granular configuration.
  • the indication information of whether to support the NC, the identification of the NC enablement, or the indication information of whether to execute the NC are used to instruct the first device to enable the NC after M times of retransmission of the data packet.
  • the method also includes:
  • the second device After the first device retransmits the data packet M times, the second device sends to the first device the indication information of whether to support NC, the identification of the NC enablement, or the indication information of whether to execute NC to indicate The first device determines whether to enable NC; or,
  • the second device After the first device retransmits the data packet M times, the second device sends the indication information of whether to support NC to the first device, so as to instruct the first device to enable NC.
  • the indication information of whether to support the NC, the identification of the NC enablement, or the indication information of whether to execute the NC, the NC configuration information or whether to configure the NC configuration information are determined based on at least one of the following :
  • the capability to support NC includes at least one of the following: capability to support NC protocol or NC function or algorithm, capability to support NC-based PDCP replication, and capability to support NC to replace PDCP replication.
  • the NC configuration information or the whether to configure the NC configuration information includes at least one of the following:
  • the number of data streams or data packet processing N supported by the NC is the number of data streams or data packet processing N supported by the NC.
  • the QoS transmission requirement includes a QoS transmission requirement corresponding to at least one of the following: service, session, QoS flow, bearer, and logical channel LCH.
  • the QoS transmission requirement includes a reliability transmission requirement and/or a delay requirement.
  • the channel quality includes at least one of the following:
  • the channel quality is reported by the first device.
  • the method further includes: the second device determining an NC input.
  • the NC input includes at least one of the following: the code configuration file identifier used, the maximum segment length L supported, the maximum segment number K supported, the number of data streams supported by the NC, or Number of data packets processed N, NC algorithm, whether to perform NC operation.
  • the NC input is for at least one of the following: a bearer, a PDCP entity, an RLC entity, an NC entity, a user equipment, a cell, and a MAC entity.
  • the NC input, NC configuration information or NC transmission path includes at least one of the following: a used path identifier, a default path, a primary path, a secondary path, and a secondary path.
  • the path identifier includes at least one of the following: an RLC identifier, a logical channel identifier, a MAC entity identifier, a carrier identifier, and a PDCP identifier.
  • the manner of obtaining the NC input includes at least one of the following: configured by the network, determined by the second device, and predefined.
  • the method further includes: the second device receiving the NC input.
  • the receiving the NC input by the second device includes: receiving, by the second device, a data packet from the first device, and the NC input is carried in a header of the data packet.
  • the second device receiving NC input includes: the second device receiving auxiliary information reported from the first device, and the NC input is carried in the auxiliary information.
  • the NC input is received by the second device from the first device through a user plane or a control plane.
  • the NC input is determined by the second device according to at least one of the following:
  • QoS transmission requirements corresponding to at least one of service, session, QoS flow, bearer, and LCH;
  • the determining the NC input by the second device includes: determining the NC input by the second device using the segment length L and/or the number of data streams or data packet processing numbers N supported by the NC.
  • the NC input is determined by at least one of the NC layer of the second device, the function supporting NC, and the NC protocol stack.
  • the NC support includes: enabling NC codec-related operations, enabling NC transmission methods, enabling NC codecs, the ability to use NC codec-related operations, the ability to use NC transmission methods, and the ability to use NC codecs.
  • the capability of encoding and decoding enables the NC-based PDCP replication, or supports the NC-based PDCP replication.
  • Fig. 5 is a schematic block diagram of a first device 500 according to an embodiment of the present application.
  • the first device 500 may include: a receiving unit 510, configured to receive NC configuration information.
  • the NC configuration information is included in at least one of the following: RRC configuration information, radio bearer configuration information, PDCP configuration information, RLC configuration information, MAC configuration information, cell configuration information, logical channel configuration information.
  • the NC configuration information is for at least one of the following: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, and MAC entity.
  • the NC configuration information is for at least one of the following: each or at least one bearer, each or at least one bearer group, carrier group, each or at least one PDCP entity, each or at least one PDCP entity group, Each or at least each or at least one PDCP entity group, one NC entity, each NC entity group, each or at least one user equipment, each or at least one user equipment group, each or at least one cell, each or at least one Cell group, each or at least one MAC entity, each or at least one MAC entity group, each or at least one carrier, each or at least one carrier group.
  • the NC configuration information includes at least one of the following: used path identifier, default path, primary path, secondary path, and secondary path.
  • the NC configuration information includes at least one of the following: the maximum segment length L supported, the maximum segment number K supported, the number of data streams or the number of data packets processed by the NC supported N, The encoding profile ID to use.
  • the NC configuration information includes at least one of the following:
  • the physical layer parameters include at least one of the following: code rate and transmission power.
  • the encoding method includes an encoding algorithm or an encoding configuration file.
  • the encoding manner is configured at a granularity of bearer configuration.
  • the encoding mode may also be configured at least one of bearer group, carrier, carrier group, PDCP entity, RLC entity, NC entity, user equipment, user equipment group, cell, cell group, and MAC entity as a granular configuration.
  • the indication information of whether to support the NC, the identification of the NC enablement, or the indication information of whether to execute the NC are used to instruct the first device to enable the NC after M times of retransmission of the data packet.
  • the method further includes: the first device receives the indication information of whether to support NC, the identification of the NC enablement, or the indication information of whether to execute NC after the data packet is retransmitted M times, to Determine whether to enable the NC; or, after the data packet is retransmitted M times, the first device receives the indication information of whether to support the NC, the identification of the NC enablement, or the indication information of whether to execute the NC, so as to enable the NC.
  • the indication information of whether to support the NC, the NC configuration information or whether to configure the NC configuration information is determined based on at least one of the following:
  • the capability to support NC includes at least one of the following: capability to support NC protocol or NC function or algorithm, capability to support NC-based PDCP replication, and capability to support NC to replace PDCP replication.
  • the indication information of whether to support the NC, the identification of the NC enablement, or the indication information of whether to execute the NC, the NC configuration information, or the NC configuration information includes at least one of the following:
  • the number of data streams or data packet processing N supported by the NC is the number of data streams or data packet processing N supported by the NC.
  • the QoS transmission requirement includes a QoS transmission requirement corresponding to at least one of the following: service, session, QoS flow, bearer, and logical channel LCH.
  • the QoS transmission requirement includes a reliability transmission requirement and/or a delay requirement.
  • the channel quality includes at least one of the following:
  • the channel quality is reported by the first device.
  • the device further comprises: a processing unit for determining the NC input.
  • the NC input includes at least one of the following: the code configuration file identifier used, the maximum segment length L supported, the maximum segment number K supported, the number of data streams supported by the NC, or Number of data packets processed N, NC algorithm, whether to perform NC operation.
  • the NC input is for at least one of the following: a bearer, a PDCP entity, an RLC entity, an NC entity, a user equipment, a cell, and a MAC entity.
  • the NC input, NC configuration information or NC transmission path includes at least one of the following: a used path identifier, a default path, a primary path, a secondary path, and a secondary path.
  • the path identifier includes at least one of the following: an RLC identifier, a logical channel identifier, a MAC entity identifier, a carrier identifier, and a PDCP identifier.
  • the acquisition manner of the NC input includes at least one of the following: configured by the network, determined by the first device, and predefined.
  • the device further includes: an NC unit, configured to perform NC operations according to NC configuration and/or NC input.
  • an NC unit configured to perform NC operations according to NC configuration and/or NC input.
  • the device further includes: a sending unit, configured to send the NC input to a second device.
  • the NC input is sent by the first device to the second device through a user plane or a control plane.
  • the NC input is carried in a header of a data packet sent by the first device to the second device.
  • the NC input is carried in auxiliary information reported by the first device to the second device.
  • the NC input is determined by the first device according to at least one of the following:
  • QoS transmission requirements corresponding to at least one of service, session, QoS flow, bearer, and LCH;
  • the processing unit is further configured to determine the NC input using the segment length L and/or the number of data streams or data packet processing numbers N supported by the NC.
  • the NC input is determined by at least one of the NC layer of the first device, the function supporting NC, and the NC protocol stack.
  • the device further includes: a PDCP replication unit, configured to perform NC-based PDCP replication according to the NC configuration information.
  • a PDCP replication unit configured to perform NC-based PDCP replication according to the NC configuration information.
  • the output result of the NC algorithm is transmitted to the lower layer through the same path or different paths.
  • the device further includes: a data transmission unit, configured to enable NC, or enable NC-based PDCP replication, or enable NC to replace PDCP replication , the way the first device transmits data includes at least one of the following:
  • Data processed/generated using NC algorithms or protocols is transmitted from the secondary path or from the secondary path.
  • the data processed by the NC is transmitted through a dedicated DRB and its corresponding path entity.
  • one of the functions of PDCP replication and NC-based PDCP replication is activated.
  • the NC support includes: enabling NC codec-related operations, enabling NC transmission methods, enabling NC codecs, the ability to use NC codec-related operations, the ability to use NC transmission methods, and the ability to use NC codecs.
  • the capability of encoding and decoding enables the NC-based PDCP replication, or supports the NC-based PDCP replication.
  • the first device 500 in the embodiment of the present application can implement the corresponding function of the first device in the foregoing method 300 embodiment.
  • each module (submodule, unit, or component, etc.) in the first device 500 refers to the corresponding descriptions in the above method embodiments, and details will not be repeated here.
  • the functions described by the modules (submodules, units or components, etc.) in the first device 500 of the embodiment of the application may be implemented by different modules (submodules, units or components, etc.), or by the same A module (submodule, unit or component, etc.) implementation.
  • Fig. 6 is a schematic block diagram of a second device 600 according to an embodiment of the present application.
  • the second device 600 may include: a sending unit 610, configured to send NC configuration information.
  • the NC configuration information is included in at least one of the following: RRC configuration information, radio bearer configuration information, PDCP configuration information, RLC configuration information, MAC configuration information, cell configuration information, logical channel configuration information.
  • the NC configuration information is for at least one of the following: bearer, PDCP entity, RLC entity, NC entity, user equipment, cell, and MAC entity.
  • the NC configuration information is for at least one of the following: each or at least one bearer, each or at least one bearer group, each or at least one PDCP entity, each or at least one PDCP entity group, each or At least each or at least one PDCP entity group, one 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, each or at least one cell group, Each or at least one MAC entity, each or at least one MAC entity group, each or at least one carrier, each or at least one carrier group.
  • the NC configuration information includes at least one of the following: used path identifier, default path, primary path, secondary path, and secondary path.
  • the NC configuration information includes at least one of the following: the maximum segment length L supported, the maximum segment number K supported, the number of data streams or the number of data packets processed by the NC supported N, The encoding profile ID to use.
  • the NC configuration information includes at least one of the following:
  • the physical layer parameters include at least one of the following: code rate and transmission power.
  • the encoding method includes an encoding algorithm or an encoding configuration file.
  • the encoding manner is configured at a granularity of bearer configuration.
  • the encoding mode may also be configured at least one of bearer group, carrier, carrier group, PDCP entity, RLC entity, NC entity, user equipment, user equipment group, cell, cell group, and MAC entity as a granular configuration.
  • the indication information of whether to support the NC, the identification of the NC enablement, or the indication information of whether to execute the NC are used to instruct the first device to enable the NC after M times of retransmission of the data packet.
  • the sending unit is also used for:
  • the first device After the first device retransmits the data packet M times, send the indication information of whether to support NC, the identification of the NC enablement, or the indication information of whether to execute NC to the first device to indicate to the first device determine whether NC is enabled; or,
  • the first device After the first device retransmits the data packet for M times, it sends the indication information of whether to support NC to the first device, so as to instruct the first device to enable NC.
  • the indication information of whether to support the NC, the identification of the NC enablement, or the indication information of whether to execute the NC, the NC configuration information or whether to configure the NC configuration information are determined based on at least one of the following :
  • the capability to support NC includes at least one of the following: capability to support NC protocol or NC function or algorithm, capability to support NC-based PDCP replication, and capability to support NC to replace PDCP replication.
  • the NC configuration information or the whether to configure the NC configuration information includes at least one of the following:
  • the number of data streams or data packet processing N supported by the NC is the number of data streams or data packet processing N supported by the NC.
  • the QoS transmission requirement includes a QoS transmission requirement corresponding to at least one of the following: service, session, QoS flow, bearer, and logical channel LCH.
  • the QoS transmission requirement includes a reliability transmission requirement and/or a delay requirement.
  • the channel quality includes at least one of the following:
  • the channel quality is reported by the first device.
  • the device further comprises: a processing unit for determining the NC input.
  • the NC input includes at least one of the following: the code configuration file identifier used, the maximum segment length L supported, the maximum segment number K supported, the number of data streams supported by the NC, or Number of data packets processed N, NC algorithm, whether to perform NC operation.
  • the NC input is for at least one of the following: a bearer, a PDCP entity, an RLC entity, an NC entity, a user equipment, a cell, and a MAC entity.
  • the NC input, NC configuration information or NC transmission path includes at least one of the following: a used path identifier, a default path, a primary path, a secondary path, and a secondary path.
  • the path identifier includes at least one of the following: an RLC identifier, a logical channel identifier, a MAC entity identifier, a carrier identifier, and a PDCP identifier.
  • the manner of obtaining the NC input includes at least one of the following: configured by the network, determined by the second device, and predefined.
  • the device further includes: a receiving unit, configured to receive the NC input.
  • the receiving unit is further configured to receive a data packet from the first device, and the NC input is carried in a packet header of the data packet.
  • 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 NC input is received by the second device from the first device through a user plane or a control plane.
  • the NC input is determined by the second device according to at least one of the following:
  • QoS transmission requirements corresponding to at least one of service, session, QoS flow, bearer, and LCH;
  • the processing unit is further configured to determine the NC input using the segment length L and/or the number of data streams or data packet processing numbers N supported by the NC.
  • the NC input is determined by at least one of the NC layer of the second device, the function supporting NC, and the NC protocol stack.
  • the NC support includes: enabling NC codec-related operations, enabling NC transmission methods, enabling NC codecs, the ability to use NC codec-related operations, the ability to use NC transmission methods, and the ability to use NC codecs.
  • the capability of encoding and decoding enables the NC-based PDCP replication, or supports the NC-based PDCP replication.
  • the second device 600 in the embodiment of the present application can implement the corresponding function of the second device in the foregoing method 400 embodiment.
  • functions, implementations and beneficial effects corresponding to each module (submodule, unit or component, etc.) in the second device 600 refer to the corresponding description in the above method embodiment, and details are not repeated here.
  • the functions described by the modules (submodules, units or components, etc.) in the second device 600 of the embodiment of the application can be realized by different modules (submodules, units or components, etc.), or by the same A module (submodule, unit or component, etc.) implementation.
  • the communication method in the embodiment of the present application may be a method supporting network coding, and has at least one of the following characteristics:
  • NC configuration or NC-based PDCP duplication (NC-based PDCP duplication).
  • the network configures NC parameters, including all NC inputs.
  • the NC parameter or NC input includes at least one of the following: encoding profile ID (coding profile ID), supported maximum segment length L, supported maximum segment number K, supported NC data stream number or Number of data packets processed N, NC algorithm, whether to perform NC operation.
  • the network configuration is based on the NC usage indication, or the NC duplication (NC-based duplication) usage indication, 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 to indicate the coding mode of the current NC packet, or to ensure the consistency of the NC mechanism used by the UE and the base station.
  • the NC input is carried in the auxiliary information to the base station, and is used to indicate the coding mode of the current NC packet, or to ensure the consistency of the NC mechanism used by the UE and the base station.
  • NC-based PDCP duplication is also applicable to the case where the NC protocol or algorithm is applicable to the 3GPP protocol.
  • the example or method is equally applicable to the case of using NC algorithm or protocol or function (not related to or limited to PDCP copy transmission), applicable to the case of using NC instead of PDCP copy, and so on. They are not listed here.
  • Example 1 The network sends the NC configuration to a terminal device such as a UE.
  • the NC configuration includes at least segment N, and segment N may indicate the number of data streams or data packet processing numbers supported by the NC.
  • a network device such as gNB configures NC configuration information. Specifically, including at least one of the following:
  • leg identification
  • default path default leg
  • primary path primary leg
  • secondary path secondary leg
  • slave path slave leg
  • the NC configuration information is carried in PDCP configuration information (PDCP-config) or radio bearer configuration information (radio bearer config).
  • NC packet transmission may also include configuration of physical layer parameters for NC packet transmission, such as code rate, transmission power, etc.
  • different encoding methods can also be configured, such as encoding profile (similar to ROHC profile).
  • the encoding method can be configured per bearer config
  • the network can be configured to enable NC after performing M retransmissions.
  • the network can instruct enable NC after M retransmissions of data packets (such as HARQ NACK, RLC NACK, etc.).
  • the gNB receives at least one of the following information, or determines whether to enable NC-based PDCP duplication/configure NC-based PDCP duplication (enable NC-based PDCP duplication/config NC -based PDCP duplication).
  • NC-based PDCP duplication The ability to support NC. Or, support for NC-based PDCP duplication (NC-based PDCP duplication). This capability is reported by the UE.
  • this capability further includes: such as supporting different configuration files (coding profile), supporting the maximum segment length L (segment L), the number of data streams or the number of data packets processed by the NC supported (for example, two-way or more channels of data NC)
  • the transmission requirement is a reliability transmission requirement (such as availability, etc.).
  • NC-based PDCP replication is enabled.
  • the channel quality is reported by the UE.
  • the channel quality is the channel quality of each (Per) UE, each LCH or each bearer;
  • the channel quality is RSRQ/RSRP.
  • the UE executes the NC or performs NC-based PDCP duplication (NC-based PDCP duplication) according to the NC configuration.
  • NC-based PDCP duplication NC-based PDCP duplication
  • the UE determines the input parameters of the NC algorithm (may be NC input for short).
  • the output result of the NC algorithm is transmitted to the lower layer through the same path (leg), or different paths (leg).
  • the original data is transmitted from the default path (default leg), and the data processed by the NC (such as the data after XOR) is transmitted from the secondary path ( secondary leg) transmission.
  • raw data and NC-processed data can be transmitted over the same or different legs.
  • a and B are transmitted from the default path, A&B are transmitted from the secondary path, etc.
  • a and B are transmitted from the original DRB and the corresponding leg, and A&B are transmitted from the dedicated DRB and the corresponding leg.
  • a and A&B are transmitted from the default path, B is transmitted from the secondary path, etc.
  • data processed by the NC is transmitted from a dedicated DRB and its corresponding leg entity.
  • NC and PDCP replication activate only one function.
  • PDCP duplication and NC-based PDCP duplication activate only one function.
  • NC-based duplication in the case of using the NC method to perform duplication transmission, a method for the network to determine NC parameters is given to improve the configuration process of NC transmission or NC-based duplication (NC-based duplication).
  • Example 2 the network (network, NW) sends the NC configuration to the UE.
  • NW network
  • the UE determines the NC parameters and carries them to the base station through the packet header to indicate the encoding mode of the current NC packet, or to realize the synchronization between the UE and the base station.
  • a network device such as gNB configures NC configuration information. Specifically, including at least one of the following:
  • NC parameters including at least one of the following: the used path (leg) identification (such as RLC identification, carrier identification, MAC entity identification, etc.), default path (default leg), primary path (primary leg), secondary path (secondary leg), from the path (slave leg).
  • leg identification
  • default path default leg
  • primary path primary leg
  • secondary path secondary leg
  • the NC configuration is carried in PDCP-config or radio bearer (radio bearer) config.
  • NC data packet (packet) transmission may also include configuration of physical layer parameters for NC data packet (packet) transmission, such as code rate, transmission power, etc.
  • different encoding methods can also be configured, such as encoding profile (similar to ROHC (Robust Header Compression, reliable header compression) profile).
  • the encoding method may be configured per bearer configuration (per bearer config) at a granularity, or related to channel quality.
  • the encoding mode may also be configured at a granularity of at least one of bearer group, carrier, PDCP entity, RLC entity, NC entity, user equipment, user equipment group, cell, cell group, and MAC entity.
  • the network can be configured: the UE can only activate the enable NC after performing M retransmissions.
  • the gNB receives the capability to support NC or the capability to support NC-based duplication reported by the UE.
  • this capability further includes: such as supporting different encoding configuration file IDs, supporting the largest segment L, the number of data streams or the number of data packets processed by the NC supported N (for example, two or more data NCs)
  • NC-based PDCP duplication determines the NC input, executes NC or performs NC-based PDCP duplication (NC-based PDCP duplication), and carries the NC input in the packet header (perform NC-based duplication, and include NC input in packet header to gNB), To ensure the consistency of the implementation of the NC mechanism by the UE and the network.
  • NC-based PDCP duplication executes NC or performs NC-based PDCP duplication
  • NC-based PDCP duplication carries the NC input in the packet header (perform NC-based duplication, and include NC input in packet header to gNB),
  • the NC input is at least one of the following: segment L; and/or the number of data streams or data packet processing N (two or more data NCs) supported by the NC, and the encoding configuration file ID
  • the UE determines the NC input according to the service, QoS flow, bearer or QoS transmission requirements corresponding to the LCH, channel quality and other information.
  • 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 encoding profile ID.
  • the indication information is used to indicate the coding mode of the current NC packet, or is used to ensure the consistency of the execution of the NC mechanism by the UE and the network.
  • the output result of the NC algorithm is transmitted to the lower layer through the same leg, or different legs.
  • the original data is transmitted from the default path (default leg), and the data processed by the NC (such as the data after XOR) is transmitted from the secondary path (secondary leg) transmission.
  • raw data and NC-processed data can be transmitted over the same or different legs.
  • a and B are transmitted from the default path, A&B are transmitted from the secondary path, etc.
  • a and B are transmitted from the original DRB and the corresponding leg, and A&B are transmitted from the dedicated DRB and the corresponding leg.
  • a and A&B are transmitted from the default path, B is transmitted from the secondary path, etc.
  • data processed by the NC is transmitted from a dedicated DRB and its corresponding leg entity.
  • only one function is activated for NC and PDCP replication.
  • only one function is activated for PDCP replication and NC-based PDCP replication.
  • a method for the UE to determine the NC input and indicate the synchronization between the UE and the gNB through the packet header information is given, and it is provided that the UE uses NC-based replication (NC- based duplication) flexibility, but also to ensure the synchronization of the use of the NC mechanism.
  • Example 3 The network sends the NC configuration to the UE.
  • the UE determines and other NC parameters, and reports to the base station through the auxiliary information, which is used to indicate the encoding mode of the current NC packet, or to realize the synchronization between the UE and the base station.
  • the gNB configures the NC configuration. Specifically, including at least one of the following:
  • the NC configuration is carried in PDCP-config or radio bearer (radio bearer) config.
  • NC data packet (packet) transmission may also include configuration of physical layer parameters for NC data packet (packet) transmission, such as code rate, transmission power, etc.
  • encoding profile similar to ROHC profile
  • encoding method can be configured per bearer config
  • the network can configure the UE to activate the enable NC after performing M retransmissions.
  • the gNB receives the capability to support NC or the capability to support NC-based duplication reported by the UE.
  • this capability further includes: such as supporting different encoding profiles, supporting the largest segment L, and supporting the number of NC data streams N (two or more data NCs)
  • the UE determines the NC input and reports it to the gNB through auxiliary information.
  • the NC input includes at least one of the following: segment L, the number of data streams supported by the NC or the number of data packets processed N (two or more data NCs); encoding configuration file ID, the path used (leg) Identification (such as RLC identification, carrier identification, MAC entity identification, etc.), default path (default leg), primary path (primary leg), secondary path (secondary leg), and slave path (slave leg).
  • segment L the number of data streams supported by the NC or the number of data packets processed N (two or more data NCs); encoding configuration file ID, the path used (leg) Identification (such as RLC identification, carrier identification, MAC entity identification, etc.), default path (default leg), primary path (primary leg), secondary path (secondary leg), and slave path (slave leg).
  • segment L the number of data streams supported by the NC or the number of data packets processed N (two or more data NCs)
  • encoding configuration file ID the path used (leg) Identification (such as RLC identification, carrier identification, MAC entity identification, etc.), default
  • the UE determines the NC input according to the service, QoS flow, bearer or QoS transmission requirements corresponding to the LCH, channel quality and other information.
  • the UE may be all parameters used by the defined NC mechanism, or some of them.
  • the network determines the NC input used by the NC mechanism according to the UE report, which is used to indicate the encoding mode of the current NC packet, or to realize the synchronization between the UE and the network.
  • the network may modify NC parameters based on the NC information reported by the UE, and configure the updated parameters to the UE.
  • the UE performs NC-based PDCP replication according to S31 and S32.
  • the UE determines the input parameters of the NC algorithm (ie, NC input) and executes the NC operation.
  • the NC algorithm ie, NC input
  • the output result of the NC algorithm is transmitted to the lower layer through the same leg, or different legs.
  • the original data is transmitted from the default leg, and the data processed by the NC (such as the data after XOR) is transmitted from the secondary path (secondary leg).
  • raw data and NC-processed data can be transmitted over the same or different legs.
  • a and B are transmitted from the default path, A&B are transmitted from the secondary path, etc.
  • a and B are transmitted from the original DRB and the corresponding leg, and A&B are transmitted from the dedicated DRB and the corresponding leg.
  • a and A&B are transmitted from the default path, B is transmitted from the secondary path, etc.
  • data processed by the NC is transmitted from a dedicated DRB and its corresponding leg entity.
  • NC-based duplication in the case of using NC transmission or using NC mode to perform duplication transmission, a method for UE to determine NC input is given, which provides flexibility for UE to use NC-based duplication (NC-based duplication).
  • NC-based duplication NC-based duplication
  • Fig. 10 is a schematic structural diagram of a communication device 1000 according to an embodiment of the present application.
  • the communication device 1000 includes a processor 1010, and the processor 1010 can invoke and run a computer program from a memory, so that the communication device 1000 implements the method in the embodiment of the present application.
  • the communication device 1000 may further include a memory 1020 .
  • the processor 1010 may call and run a computer program from the memory 1020, so that the communication device 1000 implements the method in the embodiment of the present application.
  • the memory 1020 may be an independent device independent of the processor 1010 , or may be integrated in the processor 1010 .
  • the communication device 1000 may further include a transceiver 1030, and the processor 1010 may control the transceiver 1030 to communicate with other devices, specifically, to send information or data to other devices, or to receive information sent by other devices. information or data.
  • the transceiver 1030 may include a transmitter and a receiver.
  • the transceiver 1030 may further include antennas, and the number of antennas may be one or more.
  • the communication device 1000 may be the second device in the embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the second device in each method of the embodiment of the present application. For the sake of brevity, the This will not be repeated here.
  • the communication device 1000 may be the first device in the embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, the This will not be repeated here.
  • FIG. 11 is a schematic structural diagram of a chip 1100 according to an embodiment of the present application.
  • the chip 1100 includes a processor 1110, and the processor 1110 can invoke and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
  • the chip 1100 may further include a memory 1120 .
  • the processor 1110 may invoke and run a computer program from the memory 1120, so as to implement the method executed by the first device or the second device in the embodiment of the present application.
  • the memory 1120 may be an independent device independent of the processor 1110 , or may be integrated in the processor 1110 .
  • the chip 1100 may further include an input interface 1130 .
  • the processor 1110 can control the input interface 1130 to communicate with other devices or chips, specifically, can obtain information or data sent by other devices or chips.
  • the chip 1100 may further include an output interface 1140 .
  • the processor 1110 can control the output interface 1140 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.
  • the chip can be applied to the second device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the second device in the methods of the embodiment of the present application.
  • the Let me repeat for the sake of brevity, the Let me repeat.
  • the chip can be applied to the first device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first device in the various methods of the embodiment of the present application.
  • the Let me repeat for the sake of brevity, the Let me repeat.
  • the chips applied to the second device and the first device may be the same chip or different chips.
  • the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.
  • the processor mentioned above can be a general-purpose processor, a digital signal processor (DSP), an off-the-shelf programmable gate array (FPGA), an application specific integrated circuit (ASIC) or Other programmable logic devices, transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processor
  • FPGA off-the-shelf programmable gate array
  • ASIC application specific integrated circuit
  • the general-purpose processor mentioned above may be a microprocessor or any conventional processor or the like.
  • the aforementioned memories may be volatile memories or nonvolatile memories, or may include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM).
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, 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) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is, the memory in the embodiments of the present application is intended to include, but not be limited to, these and any other suitable types of memory.
  • Fig. 12 is a schematic block diagram of a communication system 1200 according to 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.
  • the second device 1220 is configured to send NC configuration information.
  • the first device 1210 can be used to implement the corresponding functions implemented by the first device, such as a terminal device, in the above method
  • the second device 1220 can be used to implement the corresponding functions implemented by the second device, such as a network device, in the above method. function.
  • the second device 1220 can be used to implement the corresponding functions implemented by the second device, such as a network device, in the above method. function.
  • details are not repeated here.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g.
  • 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 or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (Solid State Disk, SSD)), etc.
  • sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente demande porte sur un procédé de communication et sur un dispositif. Le procédé de communication comprend les étapes suivantes : un premier dispositif reçoit des informations de configuration de codage de réseau (NC). Selon le procédé de communication fourni par des modes de réalisation de la présente demande, la fiabilité de transmission de données peut être améliorée.
PCT/CN2021/143639 2021-12-31 2021-12-31 Procédé et dispositif de communication WO2023123335A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202180103176.8A CN118056364A (zh) 2021-12-31 2021-12-31 通信方法和设备
PCT/CN2021/143639 WO2023123335A1 (fr) 2021-12-31 2021-12-31 Procédé et dispositif de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/143639 WO2023123335A1 (fr) 2021-12-31 2021-12-31 Procédé et dispositif de communication

Publications (1)

Publication Number Publication Date
WO2023123335A1 true WO2023123335A1 (fr) 2023-07-06

Family

ID=86997221

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/143639 WO2023123335A1 (fr) 2021-12-31 2021-12-31 Procédé et dispositif de communication

Country Status (2)

Country Link
CN (1) CN118056364A (fr)
WO (1) WO2023123335A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113114410A (zh) * 2020-01-10 2021-07-13 维沃移动通信有限公司 数据处理方法、配置方法及通信设备
CN113271176A (zh) * 2020-02-14 2021-08-17 华为技术有限公司 网络编码方法和通信装置
WO2021234051A1 (fr) * 2020-05-20 2021-11-25 Canon Kabushiki Kaisha Procédé et appareil de configuration de codage de réseau et de commande d'activation de codage de réseau

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113114410A (zh) * 2020-01-10 2021-07-13 维沃移动通信有限公司 数据处理方法、配置方法及通信设备
CN113271176A (zh) * 2020-02-14 2021-08-17 华为技术有限公司 网络编码方法和通信装置
WO2021234051A1 (fr) * 2020-05-20 2021-11-25 Canon Kabushiki Kaisha Procédé et appareil de configuration de codage de réseau et de commande d'activation de codage de réseau

Also Published As

Publication number Publication date
CN118056364A (zh) 2024-05-17

Similar Documents

Publication Publication Date Title
US11438941B2 (en) Communication method and communications apparatus
US10412650B2 (en) Data transmission method, apparatus and system
WO2019128947A1 (fr) Procédé de communication et dispositif de communication
WO2021160140A1 (fr) Procédé de codage de réseau et appareil de communication
US20230009565A1 (en) Communication method and apparatus applied to multi-link device in wireless local area network
WO2022148154A1 (fr) Procédé et appareil de communication, dispositif et support de stockage lisible
US20230012998A1 (en) Communication method, access network device, terminal device, and core network device
WO2019072170A1 (fr) Procédé de communication et appareil de communication
TW202013936A (zh) 無線通訊方法和通訊設備
WO2023123335A1 (fr) Procédé et dispositif de communication
TW202021329A (zh) 通訊方法、終端設備和網路設備
WO2023123336A1 (fr) Procédé et dispositif de communication
WO2023123515A1 (fr) Procédé de traitement de données, dispositif terminal et dispositif de réseau
WO2023220895A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
WO2023115559A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
WO2023097530A1 (fr) Procédé de contrôle de qualité de service, élément de réseau central, dispositif de réseau d'accès et dispositif terminal
WO2023184542A1 (fr) Procédé et appareil de configuration d'informations et système de communication
WO2022256966A1 (fr) Procédé de contrôle de qualité de service (qos), dispositif terminal et dispositif de réseau
WO2023102693A1 (fr) Procédé de communication sans fil, ue distant et dispositif de réseau
WO2023220961A1 (fr) Procédé de transmission de données, premier dispositif et second dispositif
WO2022233011A1 (fr) Procédé d'établissement de connexion, et dispositif terminal
WO2023272632A1 (fr) Procédé de transmission d'informations, premier élément réseau, second élément réseau, puce et support de stockage
US20230224763A1 (en) Wireless communication method, terminal device, and network device
WO2022082691A1 (fr) Procédé et appareil de reprise sur rlf pour un réseau iab, et dispositif associé
WO2023133685A1 (fr) Procédé de communication sans fil et dispositif terminal

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21969688

Country of ref document: EP

Kind code of ref document: A1