WO2019024792A1 - 激活及去激活数据复制的方法及终端 - Google Patents

激活及去激活数据复制的方法及终端 Download PDF

Info

Publication number
WO2019024792A1
WO2019024792A1 PCT/CN2018/097493 CN2018097493W WO2019024792A1 WO 2019024792 A1 WO2019024792 A1 WO 2019024792A1 CN 2018097493 W CN2018097493 W CN 2018097493W WO 2019024792 A1 WO2019024792 A1 WO 2019024792A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
bearer
function
data replication
deactivate
Prior art date
Application number
PCT/CN2018/097493
Other languages
English (en)
French (fr)
Inventor
吴昱民
岳然
Original Assignee
维沃移动通信有限公司
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 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to US16/635,498 priority Critical patent/US11343172B2/en
Priority to EP18841832.1A priority patent/EP3664572A4/en
Publication of WO2019024792A1 publication Critical patent/WO2019024792A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • 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
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H04W8/245—Transfer of terminal data from a network towards a terminal
    • 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
    • H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present disclosure relates to the field of communication technologies, and in particular, to a method and terminal for activating and deactivating data replication.
  • the function of the Packet Data Convergence Protocol (PDCP) data replication (PDCP duplication) is to configure the PDCP layer of the radio bearer (Radio Bearer, RB) of the user equipment (User Equipment, UE) on the network side.
  • PDCP Packet Data Convergence Protocol
  • RB Radio Bearer
  • UE User Equipment
  • RLC Radio Link Control
  • the PDCP data replication function may indicate whether to start (ie, activate) or stop (ie, deactivate) through a Medium Access Control Control Element (Signaling MAC CE).
  • MAC CE Medium Access Control Control Element
  • the PDCP data replication function includes two types as shown in Figure 1 and Figure 2:
  • Duplicate bearer as shown in Figure 1: One PDCP entity corresponding to the bearer, two (or more) RLC entities and one Medium Access Control (MAC) entity in one Community group.
  • MAC Medium Access Control
  • the PDCP entity corresponding to the bearer is in one cell group, and the corresponding two (or more) RLC entities and two (or more) MAC entities are in different cells. group.
  • the technical problem to be solved by the present disclosure is to provide a method and a terminal for activating and deactivating data replication, which can notify other protocol layer entities after receiving activating or deactivating information by a certain protocol layer entity of the terminal, thereby reducing data transmission. waste.
  • an embodiment of the present disclosure provides a method for activating and deactivating data replication, which is applied to a terminal, including:
  • a protocol layer entity of the terminal receives a command for deactivating or activating data replication of a bearer delivered by the network side;
  • the protocol layer entity instructs other protocol layers of the terminal to deactivate or activate the function of data replication of the bearer.
  • an embodiment of the present disclosure provides a terminal, including multiple protocol layer entities, where a protocol layer entity is configured to receive a command sent by a network side to deactivate or activate a data copy of a bearer, and indicate the terminal.
  • the other protocol layers deactivate or activate the function of the data replication of the bearer.
  • an embodiment of the present disclosure provides a terminal, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, where the computer program is executed by the processor to implement the foregoing The steps to activate and deactivate the method of data replication.
  • an embodiment of the present disclosure provides a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements activation and deactivation of data replication as described above. The steps of the method.
  • FIG. 1 is a schematic diagram of a replication bearer in a communication system in the related art
  • FIG. 2 is a schematic diagram of a separate bearer in a communication system in the related art
  • 3-7 are schematic flowcharts of a method for activating and deactivating data replication according to an embodiment of the present disclosure
  • FIGS. 8-10 are structural block diagrams of a terminal according to an embodiment of the present disclosure.
  • the embodiments of the present disclosure are directed to the related art in the case of activating or deactivating PDCP duplication on the network side, the behavior of each protocol layer of the UE cannot be consistent, resulting in waste of data transmission, providing an activation and deactivation of data replication.
  • the method and the terminal can notify other protocol layer entities after receiving the activation or deactivation information by a certain protocol layer entity of the terminal, thereby reducing waste of data transmission.
  • the embodiment of the present disclosure provides a method for activating and deactivating data replication, which is applied to a terminal. As shown in FIG. 3, the method includes:
  • Step 101 A protocol layer entity of the terminal receives a command for deactivating or activating data replication of a bearer delivered by the network side;
  • Step 102 The protocol layer entity instructs other protocol layers of the terminal to deactivate or activate the function of data replication of the bearer.
  • the network side activates or deactivates the PDCP data replication function
  • the information needs to be exchanged between different protocol layers of the terminal.
  • the functions of different protocol layers are consistent after PDCP duplication activation or deactivation data replication.
  • the UE behavior of each protocol layer after activation or deactivation of data replication is required to be consistent, thereby reducing waste of data transmission.
  • the MAC entity or the RRC (Radio Resource Control) entity of the terminal may receive a command for deactivating or activating data replication of a bearer sent by the network side. After the MAC entity or the RRC entity receives the command for deactivating or activating the data replication of the bearer sent by the network side, the entity entity interacts with the other protocol layer entities to implement the corresponding entity behavior after the PDCP duplication activation is deactivated. be consistent.
  • the PDCP entity needs to discard the duplicated data, and the MAC entity also needs to discard the duplicated data, which saves the overhead of the network resource and saves the transmission power overhead of the UE.
  • the MAC entity of the terminal receives a command for deactivating a PDCP duplication of a bearer sent by the network side.
  • the method for activating and deactivating PDCP duplication in this embodiment includes the following steps:
  • Step 201 The MAC entity of the terminal receives a command for deactivating a PDCP duplication of a bearer sent by the network side;
  • the network side sends a MAC CE to activate PDCP duplication of a bearer.
  • the MAC entity of the UE receives the MAC CE sent by the network side.
  • Step 202 The MAC entity instructs other protocol layer entities of the terminal to deactivate the function of the PDCP duplication of the bearer, where the other protocol layer entities include a PDCP entity and an RLC entity.
  • the MAC entity of the UE instructs other protocol layer entities to activate the PDCP duplication related function, and exchanges information between different protocol layers of the terminal to implement different protocol layers in the PDCP duplication.
  • the functions after activation data replication are consistent, and the behavior of each protocol layer after deactivating data replication is consistent, thereby reducing the waste of data transmission.
  • the function that the MAC entity indicates that the other protocol layer entity of the terminal deactivates the PDCP duplication of the bearer includes:
  • the MAC entity instructs the PDCP entity of the bearer to deactivate the PDCP duplication function
  • the MAC entity instructs the RLC entity that needs to deactivate the PDCP duplication function to deactivate the PDCP duplication function.
  • the RLC entity that needs to deactivate the function of the PDCP duplication is a network side configuration or an RLC entity agreed by a communication protocol.
  • the method further includes:
  • the MAC entity determines, according to the network side configuration, the RLC entity that needs to deactivate the function of the PDCP duplication.
  • the PDCP entity After the MAC entity indicates that the PDCP entity of the bearer deactivates the function of the PDCP duplication, the PDCP entity indicates to discard the copied data packet that has not been successfully transmitted, and the indication information includes any combination of one or more of the following:
  • the bearer PDCP entity discards the copied data packet that has not been successfully sent, including:
  • the PDCP entity discards any duplicated data packet that has not been successfully transmitted, for example, copying 2 copies of the data packet 1 and discarding any one of the copied data packets; and/or
  • the PDCP entity discards a data packet of an RLC entity that is ready to be sent to the bearer that needs to deactivate the PDCP duplication function.
  • the data packet indicating that the other protocol layer entity discards the replication that has not been successfully sent includes:
  • the PDCP entity instructs the RLC entity that needs to deactivate the PDCP duplication function to discard the copied data packet that has not been successfully transmitted;
  • the PDCP entity instructs the MAC entity to discard duplicated data packets that have not been successfully transmitted.
  • the MAC entity After the MAC entity receives the PDCP duplication command sent by the network side to deactivate a bearer, or receives the data packet sent by the PDCP entity indicating that the replication has not been successfully sent, the MAC entity discards the bearer.
  • the data of the RLC entity that needs to activate the function of PDCP duplication.
  • the data of the above RLC entity includes any combination of one or more of the following:
  • RLC PDU Protocol Data Unit
  • MAC control signaling (eg, corresponding MAC subheader) generated from RLC PDUs of the deactivated RLC entity of the bearer.
  • the data of the RLC entity that the MAC entity discards the function that needs to deactivate the PDCP duplication includes:
  • the MAC entity discards the RLC from the RLC entity that bears the function of deactivating PDCP duplication;
  • the MAC entity discards MAC control signaling generated according to the RLC protocol data unit.
  • the MAC entity of the terminal receives a command for a PDCP duplication to be activated by the network side.
  • the method for activating and deactivating PDCP duplication in this embodiment includes the following steps:
  • Step 301 The MAC entity of the terminal receives a command for activating a PDCP duplication of a bearer delivered by the network side;
  • the network side sends a MAC CE to activate PDCP duplication of a bearer.
  • the MAC entity of the UE receives the MAC CE sent by the network side.
  • Step 302 The MAC entity indicates that other protocol layer entities of the terminal activate the function of the PDCP duplication of the bearer, where the other protocol layer entities include a PDCP entity and an RLC entity.
  • the MAC entity of the UE instructs other protocol layer entities to activate the PDCP duplication related function, and exchanges information between different protocol layers of the terminal to implement PDCP duplication activation data of different protocol layers.
  • the functions after replication are consistent, and the behavior of each protocol layer is the same after activation data replication.
  • the function that the MAC entity indicates that the other protocol layer entity of the terminal activates the PDCP duplication of the bearer includes:
  • the MAC entity instructs the PDCP entity of the bearer to activate PDCP duplication;
  • the MAC entity instructs the RLC entity that needs to activate the PDCP duplication function to activate the PDCP duplication function.
  • the RLC entity that needs to activate the function of the PDCP duplication is an RLC entity configured by a network side or a communication protocol.
  • the method further includes:
  • the MAC entity determines, according to the network side configuration, the RLC entity that needs to activate the function of PDCP duplication.
  • the network side configures the PDCP duplication bearer to be deactivated by sending an RRC message, and the RRC entity of the terminal receives the RRC message (that is, the configuration command) delivered by the network side.
  • the method for activating and deactivating PDCP duplication in this embodiment includes the following steps:
  • Step 401 The RRC entity of the terminal receives a configuration command sent by the network, where the configuration command configures a PDCP duplication state of the bearer to be deactivated.
  • the network side sends an RRC message to configure the PDCP duplication state of a bearer to be deactivated, and the RRC entity of the terminal receives the RRC message.
  • Step 402 The RRC entity instructs other protocol layer entities of the terminal to deactivate the PDCP duplication function of the bearer, where the other protocol layer entities include a MAC entity, a PDCP entity, and an RLC entity.
  • the RRC entity of the UE instructs other protocol layer entities to deactivate the PDCP duplication related function, and exchanges information between different protocol layers of the terminal to implement Different protocol layers maintain the same function after PDCP duplication deactivates data replication, and the behavior of each protocol layer remains the same after deactivating data replication.
  • the function that the RRC entity instructs the other protocol layer entity of the terminal to deactivate the PDCP duplication of the bearer includes:
  • the RRC entity instructs the PDCP entity of the bearer to deactivate the function of PDCP duplication;
  • the RRC entity instructs the RLC entity that needs to deactivate the PDCP duplication function to deactivate the PDCP duplication function;
  • the RRC entity instructs the bearer's MAC entity to deactivate the PDCP duplication function of the bearer.
  • the RLC entity that needs to deactivate the function of the PDCP duplication is a network side configuration or an RLC entity agreed by a communication protocol.
  • the method further includes:
  • the RRC entity determines, according to the network side configuration, the RLC entity that needs to deactivate the function of the PDCP duplication.
  • the PDCP entity After the RRC entity indicates that the PDCP entity of the bearer deactivates the function of the PDCP duplication, the PDCP entity indicates to discard the copied data packet that has not been successfully transmitted, and the indication information includes any combination of one or more of the following:
  • the bearer PDCP entity discards the copied data packet that has not been successfully sent, including:
  • the PDCP entity discards any duplicated data packet that has not been successfully transmitted, for example, copying 2 copies of the data packet 1 and discarding any one of the copied data packets; and/or
  • the PDCP entity discards a data packet of an RLC entity that is ready to be sent to the bearer that needs to deactivate the PDCP duplication function.
  • the data packet indicating that the other protocol layer entity discards the replication that has not been successfully sent includes:
  • the PDCP entity instructs the RLC entity that needs to deactivate the PDCP duplication function to discard the copied data packet that has not been successfully transmitted;
  • the PDCP entity instructs the MAC entity to discard duplicated data packets that have not been successfully transmitted.
  • the MAC entity After the MAC entity receives the command to deactivate a bearer PDCP duplication delivered by the RRC entity, or receives the data packet sent by the PDCP entity indicating that the replication has not been successfully sent, the MAC entity discards the bearer. The data of the RLC entity that needs to activate the function of PDCP duplication.
  • the data of the above RLC entity includes any combination of one or more of the following:
  • RLC PDU Protocol Data Unit
  • MAC control signaling (eg, corresponding MAC subheader) generated from RLC PDUs of the deactivated RLC entity of the bearer.
  • the data of the RLC entity that the MAC entity discards the function that needs to deactivate the PDCP duplication includes:
  • the MAC entity discards the RLC from the RLC entity that bears the function of deactivating PDCP duplication;
  • the MAC entity discards MAC control signaling generated according to the RLC protocol data unit.
  • the network side configures the PDCP duplication bearer to be activated by sending an RRC message, and the RRC entity of the terminal receives the RRC message (that is, the configuration command) delivered by the network side.
  • the method for activating and deactivating PDCP duplication in this embodiment includes the following steps:
  • Step 501 The RRC entity of the terminal receives a configuration command sent by the network, where the configuration command configures a PDCP duplication state of the bearer to be activated.
  • the network side sends an RRC message to configure the PDCP duplication state of a bearer to be active, and the RRC entity of the terminal receives the RRC message.
  • Step 502 The RRC entity instructs other protocol layer entities of the terminal to activate the function of the PDCP duplication of the bearer, where the other protocol layer entities include a MAC entity, a PDCP entity, and an RLC entity.
  • the RRC entity of the UE instructs other protocol layer entities to activate the PDCP duplication related function, and exchanges information between different protocol layers of the terminal to implement different protocols.
  • the functions of the layer after PDCP duplication activation data replication are consistent, and the behavior of each protocol layer after activation data replication remains the same.
  • the function that the RRC entity indicates that the other protocol layer entity of the terminal activates the PDCP duplication of the bearer includes:
  • the RRC entity instructs the PDCP entity of the bearer to activate the PDCP duplication function
  • the RRC entity instructs the RLC entity that needs to activate the PDCP duplication function to activate the PDCP duplication function;
  • the RRC entity instructs the bearer's MAC entity to activate the PDCP duplication function of the bearer.
  • the RLC entity that needs to deactivate the function of the PDCP duplication is a network side configuration or an RLC entity agreed by a communication protocol.
  • the method further includes:
  • the RRC entity determines, according to the network side configuration, the RLC entity that needs to activate the function of PDCP duplication.
  • the embodiment of the present disclosure further provides a terminal, including multiple protocol layer entities, where a protocol layer entity is configured to receive a command sent by the network side to deactivate or activate a data copy of a bearer, and indicate other terminals of the terminal.
  • the protocol layer deactivates or activates the function of the data replication of the bearer.
  • the terminal includes a MAC entity 21, an RLC entity 22, and a PDCP entity 23.
  • the network side activates or deactivates the PDCP data replication function
  • one of the protocol layer entities of the terminal in this embodiment receives the activation.
  • the information is exchanged between different protocol layers of the terminal to implement the functions of different protocol layers after PDCP duplication activation or deactivation data replication, and each protocol layer activates or deactivates data replication. The behavior is consistent, which reduces the waste of data transmission.
  • the MAC entity 21 is configured to receive a deactivation command or an activation command sent by the network side, and instruct the other protocol layer entity of the terminal to deactivate or activate the data replication function of the bearer;
  • the deactivation command is used to indicate a data replication function for deactivating a bearer; the activation command is used to indicate a function of activating data replication of a bearer; the other protocol layer entity includes a PDCP entity 23 and an RLC entity 22;
  • the deactivation command corresponds to an operation of deactivating a function of data replication of the bearer; the activation command corresponds to an operation of activating a function of data replication of the bearer.
  • the MAC entity 21 is specifically configured to perform at least one of the following:
  • a function is instructed by an RLC entity 22 to deactivate or activate data replication, the RLC entity 22 being the RLC entity 22 carrying the functionality to deactivate or activate data replication.
  • the MAC entity 21 is further configured to determine, according to the network side configuration, the RLC entity 22 that needs to deactivate or activate the function of data replication.
  • the bearer PDCP entity 23 is configured to perform at least one of the following:
  • the MAC entity 21 is further configured to discard the data of the RLC entity 22.
  • the terminal includes a MAC entity 21, an RLC entity 22, a PDCP entity 23, and an RRC entity 24.
  • the network side activates or deactivates the function of PDCP data replication
  • one of the protocol layer entities of the terminal in this embodiment receives the command to activate or deactivate the data replication, and then exchanges information between different protocol layers of the terminal to implement different protocols.
  • the functions of the layer after PDCP duplication activation or deactivation of data replication are consistent, and the behavior of each protocol layer after activation or deactivation of data replication is consistent, thereby reducing the waste of data transmission.
  • the RRC entity 24 is configured to receive a configuration command that is sent by the network side, where the configuration command is used to configure the data replication status of the bearer to be deactivated or activated, and instruct other protocol layer entities of the terminal to deactivate or activate the bearer.
  • RRC entity 24 is configured to perform at least one of the following:
  • the RLC entity 22 Instructing the RLC entity 22 to deactivate or activate the function of data replication, the RLC entity 22 is the RLC entity 22 that carries the function of deactivating or activating data replication;
  • a function of instructing the MAC 21 entity to deactivate or activate the data replication of the bearer is a function of instructing the MAC 21 entity to deactivate or activate the data replication of the bearer.
  • the RRC entity 24 is further configured to determine, according to the network side configuration, the RLC entity 21 that needs to deactivate or activate the function of data replication.
  • the MAC entity 21 is also used to discard the data of the RLC entity 22 when the bearer is deactivated.
  • the PDCP entity 23 is configured to perform at least one of the following:
  • the PDCP entity 23 when the PDCP entity 23 discards the copied data packet that has not been successfully transmitted, it is specifically used to perform at least one of the following:
  • the data packet to be sent to the RLC entity 22 is discarded.
  • the PDCP entity 23 when the PDCP entity 23 instructs other protocol layer entities to discard the copied data packets that have not been successfully transmitted, the PDCP entity 23 is specifically configured to perform at least one of the following:
  • the MAC entity 21 is instructed to discard the copied data packets that have not been successfully transmitted.
  • the MAC entity 21 discards the data of the RLC entity 22
  • the MAC is specifically used to perform at least one of the following:
  • the MAC control signaling is discarded, and the MAC control signaling is generated according to the RLC protocol data unit.
  • Embodiments of the present disclosure also provide a terminal, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program being implemented by the processor to implement the above activation and removal
  • a terminal including: a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program being implemented by the processor to implement the above activation and removal
  • the processes in the method embodiment of the data replication are activated, and the same technical effects can be achieved. To avoid repetition, details are not described herein again.
  • Embodiments of the present disclosure also provide a computer readable storage medium having stored thereon a computer program, the method embodiment of implementing the above-described activation and deactivation data replication when the computer program is executed by a processor
  • a computer readable storage medium such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
  • an embodiment of the present disclosure further provides a terminal.
  • the terminal 300 shown in FIG. 10 includes: at least one processor 301, a memory 302, at least one network interface 304, and other user interfaces 303.
  • the various components in terminal 300 are coupled together by a bus system 305.
  • the bus system 305 is used to implement connection communication between these components.
  • the bus system 305 includes a power bus, a control bus, and a status signal bus in addition to the data bus.
  • various buses are labeled as bus system 305 in FIG.
  • the user interface 303 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touchpad, or a touch screen, etc.).
  • a pointing device eg, a mouse, a trackball, a touchpad, or a touch screen, etc.
  • the memory 302 in an embodiment of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • SDRAM Synchronous Connection Dynamic Random Access Memory
  • DRRAM direct memory bus random access memory
  • memory 302 stores elements, executable modules or data structures, or a subset thereof, or their extended set: operating system 3021 and application 3022.
  • the operating system 3021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, for implementing various basic services and processing hardware-based tasks.
  • the application 3022 includes various applications, such as a media player (Media Player), a browser, and the like, for implementing various application services.
  • a program implementing the method of the embodiments of the present disclosure may be included in the application 3022.
  • the program or instruction stored in the memory 302 may be specifically a program or an instruction stored in the application 3022.
  • the computer program is executed by the processor 301, the following steps are implemented:
  • a protocol layer entity of the terminal When a protocol layer entity of the terminal receives a command for deactivating or activating data replication of a bearer sent by the network side, the other protocol layer of the terminal is instructed to deactivate or activate the function of data replication of the bearer.
  • the MAC entity of the terminal receives a command for deactivating a data replication of a bearer delivered by the network side;
  • the MAC entity instructs other protocol layer entities of the terminal to deactivate the function of data replication of the bearer.
  • the MAC entity instructs the PDCP entity of the bearer to deactivate the function of data replication
  • the MAC entity instructs the RLC entity that needs to deactivate the function of data replication to deactivate the function of data replication.
  • the MAC entity determines, according to the network side configuration, the RLC entity that needs to deactivate the function of data replication.
  • the bearer PDCP entity discards the copied data packet that has not been successfully transmitted.
  • the PDCP entity discards any replicated data packets that have not been successfully transmitted.
  • the PDCP entity discards a data packet of an RLC entity that is ready to be sent to the bearer to deactivate the function of data replication.
  • the PDCP entity instructs the RLC entity that needs to deactivate the function of data replication to discard the copied data packet that has not been successfully transmitted;
  • the PDCP entity instructs the MAC entity to discard duplicated data packets that have not been successfully transmitted.
  • the MAC entity discards data of the RLC entity that needs to deactivate the function of data replication.
  • the MAC entity discards RLC protocol data units from the RLC entity carrying the function of deactivating data replication;
  • the MAC entity discards MAC control signaling generated according to the RLC protocol data unit.
  • the MAC entity of the terminal receives a command for activating data replication of a bearer delivered by the network side;
  • the MAC entity instructs other protocol layer entities of the terminal to activate the function of data replication of the bearer.
  • the MAC entity instructs the PDCP entity of the bearer to activate a function of data replication
  • the MAC entity instructs the RLC entity that needs to activate the function of data replication to activate the function of data replication.
  • the MAC entity determines, according to the network side configuration, the RLC entity that needs to activate the function of data replication.
  • the radio resource control RRC entity of the terminal receives a configuration command sent by the network side, where the configuration command configures a data replication state of the bearer to be deactivated;
  • the RRC entity instructs other protocol layer entities of the terminal to deactivate the function of data replication of the bearer.
  • the RRC entity instructs the PDCP entity of the bearer to deactivate the function of data replication
  • the RRC entity instructs the RLC entity that needs to deactivate the function of data replication to deactivate the function of data replication;
  • the RRC entity instructs the bearer's MAC entity to deactivate the function of the bearer's data replication.
  • the RRC entity determines, according to the network side configuration, the RLC entity that needs to deactivate the function of data replication.
  • the bearer PDCP entity discards the copied data packet that has not been successfully transmitted.
  • the PDCP entity discards any replicated data packets that have not been successfully transmitted.
  • the PDCP entity discards a data packet of an RLC entity that is ready to be sent to the bearer to deactivate the function of data replication.
  • the PDCP entity instructs the RLC entity that needs to deactivate the function of data replication to discard the copied data packet that has not been successfully transmitted;
  • the PDCP entity instructs the MAC entity to discard duplicated data packets that have not been successfully transmitted.
  • the MAC entity discards data of the RLC entity that needs to deactivate the function of data replication.
  • the MAC entity discards RLC protocol data units from the RLC entity carrying the function of deactivating data replication;
  • the MAC entity discards MAC control signaling generated according to the RLC protocol data unit.
  • the RRC entity of the terminal receives a configuration command sent by the network, where the configuration command configures a data replication state of the bearer to be activated;
  • the RRC entity instructs other protocol layer entities of the terminal to activate the function of data replication of the bearer.
  • the RRC entity instructs the PDCP entity of the bearer to activate a function of data replication
  • the RRC entity instructs the RLC entity that needs to activate the function of data replication to activate data replication;
  • the RRC entity instructs the bearer's MAC entity to activate the function of the bearer's data replication.
  • the RRC entity determines, according to the network side configuration, the RLC entity that carries the function of activating data replication.
  • one of the protocol layer entities of the terminal when the network side activates or deactivates the function of PDCP data replication, one of the protocol layer entities of the terminal receives the command to activate or deactivate the data replication, and then exchanges information between different protocol layers of the terminal.
  • the functions of different protocol layers after PDCP duplication activation or deactivation of data replication are consistent, and the behavior of each protocol layer after activation or deactivation of data replication is consistent, thereby reducing waste of data transmission.
  • the terminal of the present disclosure may be, for example, a mobile phone, a tablet computer, a personal digital assistant (PDA), or a car computer or the like.
  • PDA personal digital assistant
  • the terminal 300 can implement various processes implemented by the terminal in the foregoing embodiment. To avoid repetition, details are not described herein again.
  • Processor 301 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 301 or an instruction in a form of software.
  • the processor 301 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in connection with the embodiments of the present disclosure may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 302, and the processor 301 reads the information in the memory 302 and completes the steps of the above method in combination with its hardware.
  • the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processing (DSP), Digital Signal Processing Equipment (DSP Device, DSPD), programmable Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), general purpose processor, controller, microcontroller, microprocessor, other for performing the functions described herein In an electronic unit or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSP Digital Signal Processing
  • DSP Device Digital Signal Processing Equipment
  • PLD programmable Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • the techniques described herein can be implemented by modules (eg, procedures, functions, and so on) that perform the functions described herein.
  • the software code can be stored in memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.
  • embodiments of the disclosed embodiments can be provided as a method, apparatus, or computer program product.
  • embodiments of the present disclosure can take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware aspects.
  • embodiments of the present disclosure may take the form of a computer program product embodied on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • Embodiments of the present disclosure are described with reference to flowchart illustrations and/or block diagrams of a method, a terminal device (system), and a computer program product according to an embodiment of the present disclosure. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing terminal device to produce a machine such that instructions are executed by a processor of a computer or other programmable data processing terminal device
  • Means are provided for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the instruction device implements the functions specified in one or more blocks of the flow or in a flow or block diagram of the flowchart.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开提供了一种激活及去激活数据复制的方法及终端，属于通信技术领域。其中，激活及去激活数据复制的方法包括：所述终端的一协议层实体接收网络侧下发的去激活或激活一承载的数据复制的命令；所述协议层实体指示所述终端的其他协议层去激活或激活所述承载的数据复制的功能。

Description

激活及去激活数据复制的方法及终端
相关申请的交叉引用
本申请主张在2017年8月2日在中国提交的中国专利申请号No.201710653468.4的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，特别是指一种激活及去激活数据复制的方法及终端。
背景技术
包数据汇聚协议(Packet Data Convergence Protocol，PDCP)数据复制(PDCP duplication)的功能即网络侧配置用户终端(User Equipment，UE)的无线承载(Radio Bearer，RB)的PDCP层是否要将PDCP实体的数据复制后，将复制的数据分别通过两个(或多个)不同的路径(如通过两个不同的无线链路控制(Radio Link Control，RLC)实体)进行发送，不同RLC实体对应不同的逻辑信道。
该PDCP数据复制的功能可以通过媒体接入控制层控制(Medium Access Control Control Element，信令MAC CE)指示是否启动(即激活)还是停止(即去激活)。网络侧在配置该RB的PDCP复制数据功能的时候，可以配置该功能是否在配置后立即开启，即不需要MAC CE信令再额外激活。
在5G系统中由于采用了双连接(Dual Connectivity，DC)架构(包括两个小区组主小区组(Master Cell Group，MCG)和辅小区组(Secondary Cell Group，SCG))，PDCP数据复制功能的承载类型包括如图1和图2所示的两种：
如图1所示的复制承载(Duplicate bearer)：该承载对应的1个PDCP实体，2个(或多个)RLC实体和1个媒体接入控制层(Medium Access Control，MAC)实体在1个小区组。
如图2所示的分离承载(Split bearer)：该承载对应的PDCP实体在1个小区组，对应的2个(或多个)RLC实体和2个(或多个)MAC实体在不同 的小区组。
当网络侧激活或去激活PDCP duplication的时候，如果是终端的某一协议层实体收到激活或去激活命令，将无法告知其他协议层，导致其他协议层实体可能存在发送无用数据的行为，导致数据发送的浪费。
发明内容
本公开要解决的技术问题是提供一种激活及去激活数据复制的方法及终端，能够在终端的某一协议层实体收到激活或去激活信息后告知其他协议层实体，从而减少数据发送的浪费。
为解决上述技术问题，本公开的实施例提供技术方案如下：
第一方面，本公开实施例提供了一种激活及去激活数据复制的方法，应用于终端，包括：
所述终端的一协议层实体接收网络侧下发的去激活或激活一承载的数据复制的命令；
所述协议层实体指示所述终端的其他协议层去激活或激活所述承载的数据复制的功能。
第二方面，本公开实施例提供一种终端，包括多个协议层实体，其中一协议层实体用于接收网络侧下发的去激活或激活一承载的数据复制的命令，并指示所述终端的其他协议层去激活或激活所述承载的数据复制的功能。
第三方面，本公开实施例提供一种终端，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如上所述激活及去激活数据复制的方法的步骤。
第四方面，本公开实施例提供一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如上所述激活及去激活数据复制的方法的步骤。
附图说明
图1为相关技术中的通信系统中复制承载的示意图；
图2为相关技术中的通信系统中分离承载的示意图；
图3-图7为本公开实施例激活及去激活数据复制的方法的流程示意图；
图8-图10为本公开实施例终端的结构框图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完成地描述，显然，所描述的实施例仅仅是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
本公开的实施例针对相关技术中在网络侧激活或去激活PDCP duplication的时候，UE的各个协议层的行为无法保持一致，导致数据发送的浪费的问题，提供一种激活及去激活数据复制的方法及终端，能够在终端的某一协议层实体收到激活或去激活信息后告知其他协议层实体，从而减少数据发送的浪费。
本公开实施例提供了一种激活及去激活数据复制的方法，应用于终端，如图3所示，所述方法包括：
步骤101：所述终端的一协议层实体接收网络侧下发的去激活或激活一承载的数据复制的命令；
步骤102：所述协议层实体指示所述终端的其他协议层去激活或激活所述承载的数据复制的功能。
本实施例中，当网络侧激活或去激活PDCP数据复制的功能的时候，终端的其中一个协议层实体接收到激活或去激活数据复制的命令后，需要在终端的不同协议层间交互信息以实现不同协议层在PDCP duplication激活或去激活数据复制后的功能保持一致，同时也需要各个协议层在激活或去激活数据复制后的UE行为保持一致，从而减少数据发送的浪费。
其中，可以是终端的MAC实体或RRC(无线资源控制)实体接收网络侧下发的去激活或激活一承载的数据复制的命令。MAC实体或RRC实体接收网络侧下发的去激活或激活一承载的数据复制的命令后，通过与其他协议层实体交互信令，实现各协议层实体在PDCP duplication激活去激活后对应的实体行为保持一致。
进一步地，在PDCP duplication去激活的时候，PDCP实体需要丢弃复制的数据，MAC实体也需要丢弃复制的数据，这样节省了网络资源的开销，也节省了UE的传输功率开销。
下面结合具体的实施例对本公开的激活及去激活数据复制的方法进行进一步介绍：
实施例一
本实施例中，由终端的MAC实体接收网络侧下发的去激活一承载的PDCP duplication的命令。
如图4所示，本实施例的激活及去激活PDCP duplication的方法包括以下步骤：
步骤201：所述终端的MAC实体接收网络侧下发的去激活一承载的PDCP duplication的命令；
网络侧发送MAC CE去激活某个承载的PDCP duplication。UE的MAC实体接收到网络侧发送的MAC CE。
步骤202：所述MAC实体指示所述终端的其他协议层实体去激活所述承载的PDCP duplication的功能，所述其他协议层实体包括PDCP实体和RLC实体。
本实施例中，UE的MAC实体接收到网络侧发送的MAC CE命令后，指示其他协议层实体去激活PDCP duplication相关功能，在终端的不同协议层间交互信息以实现不同协议层在PDCP duplication去激活数据复制后的功能保持一致，同时各个协议层在去激活数据复制后的行为保持一致，从而减少数据发送的浪费。具体地，所述MAC实体指示所述终端的其他协议层实体去激活所述承载的PDCP duplication的功能包括：
所述MAC实体指示所述承载的PDCP实体去激活PDCP duplication的功能；和/或
所述MAC实体指示所述承载需要去激活PDCP duplication的功能的RLC实体去激活PDCP duplication的功能。
其中，所述承载需要去激活PDCP duplication的功能的RLC实体为网络侧配置或通信协议约定的RLC实体。
所述MAC实体指示所述承载需要去激活PDCP duplication的功能的RLC实体去激活PDCP duplication的功能之前，所述方法还包括：
所述MAC实体根据网络侧配置确定所述承载需要去激活PDCP duplication的功能的RLC实体。
在所述MAC实体指示所述承载的PDCP实体去激活PDCP duplication的功能之后，PDCP实体指示丢弃还没有发送成功的复制的数据包，该指示信息包括以下一项或多项的任意组合：
指示所述承载的PDCP实体丢弃尚未发送成功的复制的数据包；
指示其他协议层实体丢弃尚未发送成功的复制的数据包。
其中，所述承载的PDCP实体丢弃尚未发送成功的复制的数据包包括：
所述PDCP实体丢弃尚未发送成功的任一复制的数据包，比如数据包1复制2份，可以丢弃任意一份复制的数据包；和/或
所述PDCP实体丢弃准备发送给所述承载需要去激活PDCP duplication的功能的RLC实体的数据包。
其中，所述指示其他协议层实体丢弃尚未发送成功的复制的数据包包括：
所述PDCP实体指示所述承载需要去激活PDCP duplication的功能的RLC实体丢弃尚未发送成功的复制的数据包；和/或
所述PDCP实体指示所述MAC实体丢弃尚未发送成功的复制的数据包。
进一步地，所述MAC实体接收到网络侧下发的去激活一承载的PDCP duplication的命令、或接收到PDCP实体发送的指示尚未发送成功的复制的数据包后，所述MAC实体丢弃所述承载需要去激活PDCP duplication的功能的RLC实体的数据。
上述RLC实体的数据包括以下一项或多项的任意组合：
来自该承载的去激活的RLC实体的RLC PDU(协议数据单元)。
根据来自该承载的去激活的RLC实体的RLC PDU生成的MAC控制信令(如对应的MAC subheader)。
因此，所述MAC实体丢弃所述承载需要去激活PDCP duplication的功能的RLC实体的数据包括：
所述MAC实体丢弃来自所述承载需要去激活PDCP duplication的功能的 RLC实体的RLC；和/或
所述MAC实体丢弃根据所述RLC协议数据单元生成的MAC控制信令。
实施例二
本实施例中，由终端的MAC实体接收网络侧下发的激活一承载的PDCP duplication的命令。
如图5所示，本实施例的激活及去激活PDCP duplication的方法包括以下步骤：
步骤301：所述终端的MAC实体接收网络侧下发的激活一承载的PDCP duplication的命令；
网络侧发送MAC CE激活某个承载的PDCP duplication。UE的MAC实体接收到网络侧发送的MAC CE。
步骤302：所述MAC实体指示所述终端的其他协议层实体激活所述承载的PDCP duplication的功能，所述其他协议层实体包括PDCP实体和RLC实体。
本实施例中，UE的MAC实体接收到网络侧发送的MAC CE命令后，指示其他协议层实体激活PDCP duplication相关功能，在终端的不同协议层间交互信息以实现不同协议层在PDCP duplication激活数据复制后的功能保持一致，同时各个协议层在激活数据复制后的行为保持一致。具体地，所述MAC实体指示所述终端的其他协议层实体激活所述承载的PDCP duplication的功能包括：
所述MAC实体指示所述承载的PDCP实体激活PDCP duplication的功能；和/或
所述MAC实体指示所述承载需要激活PDCP duplication的功能的RLC实体激活PDCP duplication的功能。
其中，所述承载需要激活PDCP duplication的功能的RLC实体为网络侧配置或通信协议约定的RLC实体。
所述MAC实体指示所述承载需要激活PDCP duplication的功能的RLC实体激活PDCP duplication的功能之前，所述方法还包括：
所述MAC实体根据网络侧配置确定所述承载需要激活PDCP duplication 的功能的RLC实体。
实施例三
本实施例中，网络侧通过发送RRC消息配置PDCP duplication承载的状态为去激活，由终端的RRC实体接收网络侧下发的RRC消息(即配置命令)。
如图6所示，本实施例的激活及去激活PDCP duplication的方法包括以下步骤：
步骤401：所述终端的RRC实体接收网络侧下发的配置命令，所述配置命令配置一承载的PDCP duplication状态为去激活；
网络侧发送RRC消息配置某个承载的PDCP duplication状态为去激活，终端的RRC实体接收RRC消息。
步骤402：所述RRC实体指示所述终端的其他协议层实体去激活所述承载的PDCP duplication的功能，所述其他协议层实体包括MAC实体、PDCP实体和RLC实体。
本实施例中，UE的RRC实体接收到配置某个承载的PDCP duplication状态为去激活的RRC消息之后，指示其他协议层实体去激活PDCP duplication相关功能，在终端的不同协议层间交互信息以实现不同协议层在PDCP duplication去激活数据复制后的功能保持一致，同时各个协议层在去激活数据复制后的行为保持一致。具体地，所述RRC实体指示所述终端的其他协议层实体去激活所述承载的PDCP duplication的功能包括：
所述RRC实体指示所述承载的PDCP实体去激活PDCP duplication的功能；和/或
所述RRC实体指示所述承载需要去激活PDCP duplication的功能的RLC实体去激活PDCP duplication的功能；和/或
所述RRC实体指示所述承载的MAC实体去激活所述承载的PDCP duplication的功能。
其中，所述承载需要去激活PDCP duplication的功能的RLC实体为网络侧配置或通信协议约定的RLC实体。
所述RRC实体指示所述承载需要去激活PDCP duplication的功能的RLC实体去激活PDCP duplication的功能之前，所述方法还包括：
所述RRC实体根据网络侧配置确定所述承载需要去激活PDCP duplication的功能的RLC实体。
在所述RRC实体指示所述承载的PDCP实体去激活PDCP duplication的功能之后，PDCP实体指示丢弃还没有发送成功的复制的数据包，该指示信息包括以下一项或多项的任意组合：
指示所述承载的PDCP实体丢弃尚未发送成功的复制的数据包；和/或
指示其他协议层实体丢弃尚未发送成功的复制的数据包。
其中，所述承载的PDCP实体丢弃尚未发送成功的复制的数据包包括：
所述PDCP实体丢弃尚未发送成功的任一复制的数据包，比如数据包1复制2份，可以丢弃任意一份复制的数据包；和/或
所述PDCP实体丢弃准备发送给所述承载需要去激活PDCP duplication的功能的RLC实体的数据包。
其中，所述指示其他协议层实体丢弃尚未发送成功的复制的数据包包括：
所述PDCP实体指示所述承载需要去激活PDCP duplication的功能的RLC实体丢弃尚未发送成功的复制的数据包；和/或
所述PDCP实体指示所述MAC实体丢弃尚未发送成功的复制的数据包。
进一步地，所述MAC实体接收到RRC实体下发的去激活一承载的PDCP duplication的命令、或接收到PDCP实体发送的指示尚未发送成功的复制的数据包后，所述MAC实体丢弃所述承载需要去激活PDCP duplication的功能的RLC实体的数据。
上述RLC实体的数据包括以下一项或多项的任意组合：
来自该承载的去激活的RLC实体的RLC PDU(协议数据单元)。
根据来自该承载的去激活的RLC实体的RLC PDU生成的MAC控制信令(如对应的MAC subheader)。
因此，所述MAC实体丢弃所述承载需要去激活PDCP duplication的功能的RLC实体的数据包括：
所述MAC实体丢弃来自所述承载需要去激活PDCP duplication的功能的RLC实体的RLC；和/或
所述MAC实体丢弃根据所述RLC协议数据单元生成的MAC控制信令。
实施例四
本实施例中，网络侧通过发送RRC消息配置PDCP duplication承载的状态为激活，由终端的RRC实体接收网络侧下发的RRC消息(即配置命令)。
如图7所示，本实施例的激活及去激活PDCP duplication的方法包括以下步骤：
步骤501：所述终端的RRC实体接收网络侧下发的配置命令，所述配置命令配置一承载的PDCP duplication状态为激活；
网络侧发送RRC消息配置某个承载的PDCP duplication状态为激活，终端的RRC实体接收RRC消息。
步骤502：所述RRC实体指示所述终端的其他协议层实体激活所述承载的PDCP duplication的功能，所述其他协议层实体包括MAC实体、PDCP实体和RLC实体。
本实施例中，UE的RRC实体接收到配置某个承载的PDCP duplication状态为激活的RRC消息之后，指示其他协议层实体激活PDCP duplication相关功能，在终端的不同协议层间交互信息以实现不同协议层在PDCP duplication激活数据复制后的功能保持一致，同时各个协议层在激活数据复制后的行为保持一致。具体地，所述RRC实体指示所述终端的其他协议层实体激活所述承载的PDCP duplication的功能包括：
所述RRC实体指示所述承载的PDCP实体激活PDCP duplication的功能；和/或
所述RRC实体指示所述承载需要激活PDCP duplication的功能的RLC实体激活PDCP duplication的功能；和/或
所述RRC实体指示所述承载的MAC实体激活所述承载的PDCP duplication的功能。
其中，所述承载需要去激活PDCP duplication的功能的RLC实体为网络侧配置或通信协议约定的RLC实体。
所述RRC实体指示所述承载需要激活PDCP duplication的功能的RLC实体激活PDCP duplication的功能之前，所述方法还包括：
所述RRC实体根据网络侧配置确定所述承载需要激活PDCP duplication 的功能的RLC实体。
本公开实施例还提供了一种终端，包括多个协议层实体，其中一协议层实体用于接收网络侧下发的去激活或激活一承载的数据复制的命令，并指示所述终端的其他协议层去激活或激活所述承载的数据复制的功能。
如图8所示，所述终端包括MAC实体21、RLC实体22和PDCP实体23，当网络侧激活或去激活PDCP数据复制的功能的时候，本实施例终端的其中一个协议层实体接收到激活或去激活数据复制的命令后，在终端的不同协议层间交互信息以实现不同协议层在PDCP duplication激活或去激活数据复制后的功能保持一致，同时各个协议层在激活或去激活数据复制后的行为保持一致，从而减少数据发送的浪费。
一具体实施例中，MAC实体21用于接收网络侧下发的去激活命令或激活命令，指示所述终端的其他协议层实体去激活或激活所述承载的数据复制的功能；
其中，所述去激活命令用于指示去激活一承载的数据复制功能；所述激活命令用于指示激活一承载的数据复制的功能；所述其他协议层实体包括PDCP实体23和RLC实体22；所述去激活命令对应去激活所述承载的数据复制的功能的操作；所述激活命令对应激活所述承载的数据复制的功能的操作。
进一步地，所述MAC实体21具体用于执行以下至少一项：
指示所述承载的PDCP实体23去激活或激活数据复制的功能；
指示一RLC实体22去激活或激活数据复制的功能，所述RLC实体22为所述承载需要去激活或激活数据复制的功能的RLC实体22。
进一步地，所述MAC实体21还用于根据网络侧配置，确定所述承载需要去激活或激活数据复制的功能的RLC实体22。
进一步地，在去激活承载时，所述承载的PDCP实体23，用于执行以下至少一项：
丢弃尚未发送成功的复制的数据包；
指示其他协议层实体丢弃尚未发送成功的复制的数据包。
进一步地，在去激活承载时，所述MAC实体21还用于丢弃所述RLC实体22的数据。
另一具体实施例中，如图9所示，终端包括MAC实体21、RLC实体22、PDCP实体23和RRC实体24。当网络侧激活或去激活PDCP数据复制的功能的时候，本实施例终端的其中一个协议层实体接收到激活或去激活数据复制的命令后，在终端的不同协议层间交互信息以实现不同协议层在PDCP duplication激活或去激活数据复制后的功能保持一致，同时各个协议层在激活或去激活数据复制后的行为保持一致，从而减少数据发送的浪费。
RRC实体24用于接收网络侧下发的配置命令，所述配置命令用于配置承载的数据复制状态为去激活或激活，并指示所述终端的其他协议层实体去激活或激活所述承载的数据复制的功能，其中，所述配置命令对应去激活或激活所述承载的数据复制的功能的操作，所述其他协议层实体包括MAC实体21、PDCP实体23和RLC实体22。
进一步地，所述RRC实体24用于执行以下至少一项：
指示所述承载的PDCP实体23去激活或激活数据复制的功能；
指示所述RLC实体22去激活或激活数据复制的功能，所述RLC实体22为所述承载需要去激活或激活数据复制的功能的RLC实体22；
指示所述MAC21实体去激活或激活所述承载的数据复制的功能。
所述RRC实体24还用于根据网络侧配置，确定所述承载需要去激活或激活数据复制的功能的RLC实体21。
进一步地，在去激活承载时，所述MAC实体21还用于丢弃RLC实体22的数据。
进一步地，在去激活承载时，PDCP实体23，用于执行以下至少一项：
丢弃尚未发送成功的复制的数据包；
指示其他协议层实体丢弃尚未发送成功的复制的数据包。
进一步地，上述实施例中，PDCP实体23丢弃尚未发送成功的复制的数据包时，具体用于执行以下至少一项：
丢弃尚未发送成功的复制的数据包；
丢弃准备发送给所述RLC实体22的数据包。
进一步地，上述实施例中，PDCP实体23指示其他协议层实体丢弃尚未发送成功的复制的数据包时，具体用于执行以下至少一项：
指示所述RLC实体22丢弃尚未发送成功的复制的数据包；
指示所述MAC实体21丢弃尚未发送成功的复制的数据包。
进一步地，在MAC实体21丢弃所述RLC实体22的数据时，所述MAC具体用于执行以下至少一项：
丢弃来自所述RLC实体22的RLC协议数据单元；
丢弃MAC控制信令，所述MAC控制信令为根据所述RLC协议数据单元生成。
本公开的实施例还提供了一种终端，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述激活及去激活数据复制的方法实施例中的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本公开的实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现上述激活及去激活数据复制的方法实施例中的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
如图10所示，本公开的实施例还提供了一种终端，图10所示的终端300包括：至少一个处理器301、存储器302、至少一个网络接口304和其他用户接口303。终端300中的各个组件通过总线系统305耦合在一起。可理解，总线系统305用于实现这些组件之间的连接通信。总线系统305除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图10中将各种总线都标为总线系统305。
其中，用户接口303可以包括显示器、键盘或者点击设备(例如，鼠标，轨迹球(trackball)、触感板或者触摸屏等。
可以理解，本公开实施例中的存储器302可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、 电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本文描述的系统和方法的存储器302旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中，存储器302存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：操作系统3021和应用程序3022。
其中，操作系统3021，包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。应用程序3022，包含各种应用程序，例如媒体播放器(Media Player)、浏览器(Browser)等，用于实现各种应用业务。实现本公开实施例方法的程序可以包含在应用程序3022中。
在本公开的一实施例中，通过调用存储器302存储的程序或指令，具体的可以是在应用程序3022中存储的程序或指令，计算机程序被处理器301执行时实现如下步骤：
在所述终端的一协议层实体接收到网络侧下发的去激活或激活一承载的数据复制的命令时，指示所述终端的其他协议层去激活或激活所述承载的数据复制的功能。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述终端的MAC实体接收网络侧下发的去激活一承载的数据复制的命令；
所述MAC实体指示所述终端的其他协议层实体去激活所述承载的数据复制的功能。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述MAC实体指示所述承载的PDCP实体去激活数据复制的功能；和/或
所述MAC实体指示所述承载需要去激活数据复制的功能的RLC实体去激活数据复制的功能。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述MAC实体根据网络侧配置确定所述承载需要去激活数据复制的功能的RLC实体。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述承载的PDCP实体丢弃尚未发送成功的复制的数据包；和/或
指示其他协议层实体丢弃尚未发送成功的复制的数据包。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述PDCP实体丢弃尚未发送成功的任一复制的数据包；和/或
所述PDCP实体丢弃准备发送给所述承载需要去激活数据复制的功能的RLC实体的数据包。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述PDCP实体指示所述承载需要去激活数据复制的功能的RLC实体丢弃尚未发送成功的复制的数据包；和/或
所述PDCP实体指示所述MAC实体丢弃尚未发送成功的复制的数据包。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述MAC实体丢弃所述承载需要去激活数据复制的功能的RLC实体的数据。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述MAC实体丢弃来自所述承载需要去激活数据复制的功能的RLC实体的RLC协议数据单元；和/或
所述MAC实体丢弃根据所述RLC协议数据单元生成的MAC控制信令。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述终端的MAC实体接收网络侧下发的激活一承载的数据复制的命令；
所述MAC实体指示所述终端的其他协议层实体激活所述承载的数据复制的功能。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述MAC实体指示所述承载的PDCP实体激活数据复制的功能；和/或
所述MAC实体指示所述承载需要激活数据复制的功能的RLC实体激活数据复制的功能。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述MAC实体根据网络侧配置确定所述承载需要激活数据复制的功能的RLC实体。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述终端的无线资源控制RRC实体接收网络侧下发的配置命令，所述配置命令配置一承载的数据复制状态为去激活；
所述RRC实体指示所述终端的其他协议层实体去激活所述承载的数据复制的功能。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述RRC实体指示所述承载的PDCP实体去激活数据复制的功能；和/或
所述RRC实体指示所述承载需要去激活数据复制的功能的RLC实体去激活数据复制的功能；和/或
所述RRC实体指示所述承载的MAC实体去激活所述承载的数据复制的功能。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述RRC实体根据网络侧配置确定所述承载需要去激活数据复制的功能的RLC实体。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述承载的PDCP实体丢弃尚未发送成功的复制的数据包；和/或
指示其他协议层实体丢弃尚未发送成功的复制的数据包。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述PDCP实体丢弃尚未发送成功的任一复制的数据包；和/或
所述PDCP实体丢弃准备发送给所述承载需要去激活数据复制的功能的RLC实体的数据包。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述PDCP实体指示所述承载需要去激活数据复制的功能的RLC实体丢弃 尚未发送成功的复制的数据包；和/或
所述PDCP实体指示所述MAC实体丢弃尚未发送成功的复制的数据包。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述MAC实体丢弃所述承载需要去激活数据复制的功能的RLC实体的数据。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述MAC实体丢弃来自所述承载需要去激活数据复制的功能的RLC实体的RLC协议数据单元；和/或
所述MAC实体丢弃根据所述RLC协议数据单元生成的MAC控制信令。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述终端的RRC实体接收网络侧下发的配置命令，所述配置命令配置一承载的数据复制状态为激活；
所述RRC实体指示所述终端的其他协议层实体激活所述承载的数据复制的功能。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述RRC实体指示所述承载的PDCP实体激活数据复制的功能；和/或
所述RRC实体指示所述承载需要激活数据复制的功能的RLC实体激活数据复制的功能；和/或
所述RRC实体指示所述承载的MAC实体激活所述承载的数据复制的功能。
可选的，计算机程序被处理器301执行时实现如下步骤：
所述RRC实体根据网络侧配置确定所述承载需要激活数据复制的功能的RLC实体。
本公开实施例的终端，当网络侧激活或去激活PDCP数据复制的功能的时候，终端的其中一个协议层实体接收到激活或去激活数据复制的命令后，在终端的不同协议层间交互信息以实现不同协议层在PDCP duplication激活或去激活数据复制后的功能保持一致，同时各个协议层在激活或去激活数据复制后的行为保持一致，从而减少数据发送的浪费。
本公开的终端如可以是手机、平板电脑、个人数字助理(Personal Digital Assistant，PDA)、或车载电脑等等终端。
终端300能够实现前述实施例中终端实现的各个过程，为避免重复，这里不再赘述。
上述本公开实施例揭示的方法均可以应用于处理器301中，或者由处理器301实现。处理器301可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器301中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器301可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本公开实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本公开实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器302，处理器301读取存储器302中的信息，结合其硬件完成上述方法的步骤。
可以理解的是，本文描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本文所述功能的模块(例如过程、函数等)来实现本文所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
本说明书中的各个实施例均采用递进的方式描述，每个实施例重点说明 的都是与其他实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。
本领域内的技术人员应明白，本公开实施例的实施例可提供为方法、装置、或计算机程序产品。因此，本公开实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本公开实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本公开实施例是参照根据本公开实施例的方法、终端设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理终端设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理终端设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理终端设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理终端设备上，使得在计算机或其他可编程终端设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程终端设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本公开实施例的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本公开实施例范围的所有变更和修改。
还需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者终端设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者终端设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者终端设备中还存在另外的相同要素。
以上所述的是本公开的优选实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开所述的原理前提下还可以作出若干改进和润饰，这些改进和润饰也在本公开的保护范围内。

Claims (30)

  1. 一种激活及去激活数据复制的方法，应用于终端，包括：
    所述终端的一协议层实体接收网络侧下发的去激活或激活一承载的数据复制的命令；
    所述协议层实体指示所述终端的其他协议层去激活或激活所述承载的数据复制的功能。
  2. 根据权利要求1所述的方法，其中，所述终端的一协议层实体接收到网络侧下发的去激活或激活一承载的数据复制的命令，包括：
    所述终端的MAC实体接收网络侧下发的去激活命令或激活命令；
    所述协议层实体指示所述终端的其他协议层去激活或激活所述承载的数据复制的功能，包括：
    所述MAC实体指示所述终端的其他协议层实体去激活或激活所述承载的数据复制的功能；
    其中，所述去激活命令用于指示去激活一承载的数据复制功能；所述激活命令用于指示激活一承载的数据复制的功能；所述其他协议层实体包括PDCP实体和RLC实体；所述去激活命令对应去激活所述承载的数据复制的功能的操作；所述激活命令对应激活所述承载的数据复制的功能的操作。
  3. 根据权利要求2所述的方法，其中，所述MAC实体指示所述终端的其他协议层实体去激活或激活所述承载的数据复制的功能，包括以下至少一项：
    所述MAC实体指示所述承载的PDCP实体去激活或激活数据复制的功能；
    所述MAC实体指示一RLC实体去激活或激活数据复制的功能，所述RLC实体为所述承载需要去激活或激活数据复制的功能的RLC实体。
  4. 根据权利要求3所述的方法，其中，所述MAC实体指示一RLC实体去激活或激活数据复制的功能之前，所述方法还包括：
    所述MAC实体根据网络侧配置，确定所述承载需要去激活或激活数据复制的功能的RLC实体。
  5. 根据权利要求3所述的方法，其中，所述MAC实体指示所述承载的PDCP实体去激活数据复制的功能之后，所述方法还包括以下至少一项：
    所述承载的PDCP实体丢弃尚未发送成功的复制的数据包；
    指示其他协议层实体丢弃尚未发送成功的复制的数据包。
  6. 根据权利要求3所述的方法，其中，所述MAC实体指示所述终端的其他协议层实体去激活或激活所述承载的数据复制的功能之前、之后或同时，所述方法还包括：
    所述MAC实体丢弃所述RLC实体的数据。
  7. 根据权利要求1所述的方法，其中，所述终端的一协议层实体接收到网络侧下发的去激活或激活一承载的数据复制的命令，包括：
    所述终端的无线资源控制RRC实体接收网络侧下发的配置命令，所述配置命令用于配置承载的数据复制状态为去激活或激活；
    所述协议层实体指示所述终端的其他协议层去激活或激活所述承载的数据复制的功能，包括：
    所述RRC实体指示所述终端的其他协议层实体去激活或激活所述承载的数据复制的功能；
    其中，所述配置命令对应去激活或激活所述承载的数据复制的功能的操作，所述其他协议层实体包括MAC实体、PDCP实体和RLC实体。
  8. 根据权利要求7所述的方法，其中，所述RRC实体指示所述终端的其他协议层实体去激活或激活所述承载的数据复制的功能，包括以下至少一项：
    所述RRC实体指示所述承载的PDCP实体去激活或激活数据复制的功能；
    所述RRC实体指示所述RLC实体去激活或激活数据复制的功能，所述RLC实体为所述承载需要去激活或激活数据复制的功能的RLC实体；
    所述RRC实体指示所述MAC实体去激活或激活所述承载的数据复制的功能。
  9. 根据权利要求7所述的方法，其中，所述RRC实体指示所述终端的其他协议层实体去激活或激活所述承载的数据复制的功能之前，所述方法还包括：
    所述RRC实体根据网络侧配置，确定所述承载需要去激活或激活数据复制的功能的RLC实体。
  10. 根据权利要求8所述的方法，其中，所述RRC实体指示所述承载的 MAC实体去激活所述承载的数据复制的功能之后，所述方法还包括：
    所述MAC实体丢弃所述RLC实体的数据。
  11. 根据权利要求8所述的方法，其中，所述RRC实体指示所述承载的PDCP实体去激活数据复制的功能之后，所述方法还包括以下至少一项：
    所述承载的PDCP实体丢弃尚未发送成功的复制的数据包；
    指示其他协议层实体丢弃尚未发送成功的复制的数据包。
  12. 根据权利要求5或11所述的方法，其中，所述承载的PDCP实体丢弃尚未发送成功的复制的数据包，包括以下至少一项：
    所述PDCP实体丢弃尚未发送成功的复制的数据包；
    所述PDCP实体丢弃准备发送给所述RLC实体的数据包。
  13. 根据权利要求5或11所述的方法，其中，所述指示其他协议层实体丢弃尚未发送成功的复制的数据包，包括以下至少一项：
    所述PDCP实体指示所述RLC实体丢弃尚未发送成功的复制的数据包；
    所述PDCP实体指示所述MAC实体丢弃尚未发送成功的复制的数据包。
  14. 根据权利要求6或10所述的方法，其中，所述MAC实体丢弃所述RLC实体的数据，包括以下至少一项：
    所述MAC实体丢弃来自所述RLC实体的RLC协议数据单元；
    所述MAC实体丢弃MAC控制信令，所述MAC控制信令为根据所述RLC协议数据单元生成。
  15. 一种终端，包括多个协议层实体，其中一协议层实体用于接收网络侧下发的去激活或激活一承载的数据复制的命令，并指示所述终端的其他协议层去激活或激活所述承载的数据复制的功能。
  16. 根据权利要求15所述的终端，还包括：
    MAC实体，用于接收网络侧下发的去激活命令或激活命令，指示所述终端的其他协议层实体去激活或激活所述承载的数据复制的功能；
    其中，所述去激活命令用于指示去激活一承载的数据复制功能；所述激活命令用于指示激活一承载的数据复制的功能；所述其他协议层实体包括PDCP实体和RLC实体；所述去激活命令对应去激活所述承载的数据复制的功能的操作；所述激活命令对应激活所述承载的数据复制的功能的操作。
  17. 根据权利要求16所述的终端，其中，
    所述MAC实体具体用于执行以下至少一项：
    指示所述承载的PDCP实体去激活或激活数据复制的功能；
    指示一RLC实体去激活或激活数据复制的功能，所述RLC实体为所述承载需要去激活或激活数据复制的功能的RLC实体。
  18. 根据权利要求17所述的终端，其中，
    所述MAC实体还用于根据网络侧配置，确定所述承载需要去激活或激活数据复制的功能的RLC实体。
  19. 根据权利要求18所述的终端，还包括所述承载的PDCP实体，用于执行以下至少一项：
    丢弃尚未发送成功的复制的数据包；
    指示其他协议层实体丢弃尚未发送成功的复制的数据包。
  20. 根据权利要求18所述的终端，其中，
    所述MAC还用于丢弃所述RLC实体的数据。
  21. 根据权利要求15所述的终端，还包括：
    无线资源控制RRC实体，用于接收网络侧下发的配置命令，所述配置命令用于配置承载的数据复制状态为去激活或激活，并指示所述终端的其他协议层实体去激活或激活所述承载的数据复制的功能，其中，所述配置命令对应去激活或激活所述承载的数据复制的功能的操作，所述其他协议层实体包括MAC实体、PDCP实体和RLC实体。
  22. 根据权利要求21所述的终端，其中，
    所述RRC实体用于执行以下至少一项：
    指示所述承载的PDCP实体去激活或激活数据复制的功能；
    指示所述RLC实体去激活或激活数据复制的功能，所述RLC实体为所述承载需要去激活或激活数据复制的功能的RLC实体；
    指示所述MAC实体去激活或激活所述承载的数据复制的功能。
  23. 根据权利要求21所述的终端，其中，
    所述RRC实体还用于根据网络侧配置，确定所述承载需要去激活或激活数据复制的功能的RLC实体。
  24. 根据权利要求22所述的终端，其中，所述终端还包括：
    所述MAC实体，用于丢弃所述RLC实体的数据。
  25. 根据权利要求22所述的终端，还包括所述承载的PDCP实体，用于执行以下至少一项：
    丢弃尚未发送成功的复制的数据包；
    指示其他协议层实体丢弃尚未发送成功的复制的数据包。
  26. 根据权利要求19或25所述的终端，其中，
    所述PDCP实体具体用于执行以下至少一项：
    丢弃尚未发送成功的复制的数据包；
    丢弃准备发送给所述RLC实体的数据包。
  27. 根据权利要求19或25所述的终端，其中，
    所述PDCP实体具体用于执行以下至少一项：
    指示所述RLC实体丢弃尚未发送成功的复制的数据包；
    指示所述MAC实体丢弃尚未发送成功的复制的数据包。
  28. 根据权利要求20或24所述的终端，其中，所述MAC具体用于执行以下至少一项：
    丢弃来自所述RLC实体的RLC协议数据单元；
    丢弃MAC控制信令，所述MAC控制信令为根据所述RLC协议数据单元生成。
  29. 一种终端，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至14中任一项所述激活及去激活数据复制的方法的步骤。
  30. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1至14中任一项所述激活及去激活数据复制的方法的步骤。
PCT/CN2018/097493 2017-08-02 2018-07-27 激活及去激活数据复制的方法及终端 WO2019024792A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/635,498 US11343172B2 (en) 2017-08-02 2018-07-27 Method of activating and deactivating a data duplication and terminal thereof
EP18841832.1A EP3664572A4 (en) 2017-08-02 2018-07-27 METHOD FOR ACTIVATING AND DEACTIVATING A DATA DUPLICATION AND TERMINAL

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710653468.4A CN109391639B (zh) 2017-08-02 2017-08-02 一种激活及去激活数据复制的方法及终端
CN201710653468.4 2017-08-02

Publications (1)

Publication Number Publication Date
WO2019024792A1 true WO2019024792A1 (zh) 2019-02-07

Family

ID=65233436

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/097493 WO2019024792A1 (zh) 2017-08-02 2018-07-27 激活及去激活数据复制的方法及终端

Country Status (4)

Country Link
US (1) US11343172B2 (zh)
EP (1) EP3664572A4 (zh)
CN (1) CN109391639B (zh)
WO (1) WO2019024792A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180324641A1 (en) * 2017-05-05 2018-11-08 Asustek Computer Inc. Method and apparatus of transmitting data duplication in a wireless communication system
US20180324642A1 (en) * 2017-05-05 2018-11-08 Qualcomm Incorporated Packet duplication at a packet data convergence protocol (pdcp) entity
AU2020214088B2 (en) * 2019-02-03 2022-10-13 FG Innovation Company Limited Evolved packet data convergence protocol duplication

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112615702A (zh) * 2017-05-05 2021-04-06 中兴通讯股份有限公司 一种数据包复制功能的控制方法和装置、通信设备
CN110771244B (zh) * 2017-08-11 2024-07-02 Oppo广东移动通信有限公司 一种控制方法、节点及计算机存储介质
CN111465119B (zh) * 2019-03-28 2023-02-24 维沃移动通信有限公司 数据发送方法、信息配置方法、终端及网络设备
CN111757548B (zh) * 2019-03-29 2022-05-24 华为技术有限公司 通信方法和通信装置
CN111786747B (zh) * 2019-04-03 2023-01-03 中国移动通信有限公司研究院 接收状态反馈方法、状态反馈方法、通信单元及终端
CN110311751B (zh) * 2019-04-25 2021-11-30 维沃移动通信有限公司 一种数据的发送方法及终端
CN113498219B (zh) * 2020-03-18 2024-10-18 深圳传音控股股份有限公司 多连接管理方法及相关产品
WO2021203444A1 (zh) * 2020-04-10 2021-10-14 Oppo广东移动通信有限公司 数据传输方法及相关设备
WO2022027558A1 (en) * 2020-08-07 2022-02-10 JRD Communication (Shenzhen) Ltd. Method for controlling rlc entities of user equipment, network node and user equipment
CN114095873B (zh) * 2020-08-24 2023-07-25 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090016301A1 (en) * 2007-07-11 2009-01-15 Interdigital Technology Corporation Packet data convergence protocol operations

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102037669B (zh) * 2008-05-22 2013-11-06 爱立信电话股份有限公司 增强恢复过程
WO2013144680A1 (en) * 2012-03-26 2013-10-03 Nokia Corporation Method and apparatus for activating frequencies in white spaces
US10117224B2 (en) * 2013-09-20 2018-10-30 Qualcomm Incorporated MAC subheader for D2D broadcast communication for public safety
EP3284273A4 (en) * 2015-04-16 2018-10-10 Telefonaktiebolaget LM Ericsson (publ) Method and apparatus for facilitating mobility in a communications network
US20160308776A1 (en) * 2015-04-20 2016-10-20 Qualcomm Incorporated Enhancements for pdcp layer
US20170041766A1 (en) * 2015-08-05 2017-02-09 Qualcomm Incorporated Media access control segmentation and packet data convergence protocol delivery notification with enhanced component carriers
US10750410B2 (en) * 2016-09-30 2020-08-18 Huawei Technologies Co., Ltd. Ultra reliable low latency connection support in radio access networks
US10448386B2 (en) * 2017-01-06 2019-10-15 Kt Corporation Method and apparatus for controlling redundant data transmission
CN109417723B (zh) * 2017-02-02 2022-04-19 Lg电子株式会社 用于发送数据单元的方法和设备
CN108924871B (zh) * 2017-03-23 2022-09-20 夏普株式会社 无线配置方法、用户设备和基站
US10716094B2 (en) * 2017-03-23 2020-07-14 Ofinno, Llc Packet duplication in a wireless device and wireless network
BR112019019718A2 (pt) * 2017-03-24 2020-04-14 Ericsson Telefon Ab L M método, e, dispositivo sem fio.
EP3603322B1 (en) * 2017-03-24 2023-08-16 Nokia Technologies Oy Handling of pdcp duplication and data recovery in new radio access technology
US10405231B2 (en) * 2017-04-24 2019-09-03 Motorola Mobility Llc Switching between packet duplication operating modes
WO2018200565A1 (en) * 2017-04-24 2018-11-01 Motorola Mobility Llc Duplicating pdcp pdus for a radio bearer
CN112615702A (zh) * 2017-05-05 2021-04-06 中兴通讯股份有限公司 一种数据包复制功能的控制方法和装置、通信设备
EP3399724B1 (en) * 2017-05-05 2022-10-05 ASUSTek Computer Inc. Method and apparatus of transmitting data duplication in a wireless communication system
US10805836B2 (en) * 2017-05-05 2020-10-13 Qualcomm Incorporated Packet duplication at a packet data convergence protocol (PDCP) entity
CN109150415B (zh) * 2017-06-15 2022-01-21 夏普株式会社 基站、用户设备和相关方法
CN109151891B (zh) * 2017-06-15 2022-04-05 华为技术有限公司 一种通信处理方法和通信装置
US20180367288A1 (en) * 2017-06-16 2018-12-20 Huawei Technologies Co., Ltd. Dynamic activation and deactivation of packet duplication
CN109417716A (zh) * 2017-06-16 2019-03-01 联发科技（新加坡）私人有限公司 移动通信中处理数据重复的方法和装置
CN109429257B (zh) * 2017-06-22 2022-11-04 夏普株式会社 用户设备和相关方法

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090016301A1 (en) * 2007-07-11 2009-01-15 Interdigital Technology Corporation Packet data convergence protocol operations

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
See also references of EP3664572A4 *
SHARP: "Enable/Disable PDCP Duplication", 3GPP TSG-RAN2 MEETING #98, R2-1704941, 5 May 2017 (2017-05-05), XP051263897, Retrieved from the Internet <URL:http://www.3gpp.org/FTP/tsg_ran/WG2_RL2/TSGR2_98/Docs/R2-1704941.zip> *
ZTE: "Consideration on the Activation/Deactivation of Data Duplication for CA", 3GPP TSG-RAN WG2 MEETING #98, R2-1704660, 5 May 2017 (2017-05-05), XP051263847, Retrieved from the Internet <URL:http://www.3gpp.org/FTP/tsg_ran/WG2_RL2/TSGR2_98/Docs/R2-1704660.zip> *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180324641A1 (en) * 2017-05-05 2018-11-08 Asustek Computer Inc. Method and apparatus of transmitting data duplication in a wireless communication system
US20180324642A1 (en) * 2017-05-05 2018-11-08 Qualcomm Incorporated Packet duplication at a packet data convergence protocol (pdcp) entity
US10582418B2 (en) * 2017-05-05 2020-03-03 Asustek Computer Inc. Method and apparatus of transmitting data duplication in a wireless communication system
US10805836B2 (en) * 2017-05-05 2020-10-13 Qualcomm Incorporated Packet duplication at a packet data convergence protocol (PDCP) entity
AU2020214088B2 (en) * 2019-02-03 2022-10-13 FG Innovation Company Limited Evolved packet data convergence protocol duplication
US11757760B2 (en) 2019-02-03 2023-09-12 FG Innovation Company Limited Evolved packet data convergence protocol duplication

Also Published As

Publication number Publication date
CN109391639B (zh) 2021-01-08
EP3664572A1 (en) 2020-06-10
EP3664572A4 (en) 2020-07-01
US11343172B2 (en) 2022-05-24
CN109391639A (zh) 2019-02-26
US20200236033A1 (en) 2020-07-23

Similar Documents

Publication Publication Date Title
WO2019024792A1 (zh) 激活及去激活数据复制的方法及终端
WO2019157956A1 (zh) 副链路数据的指示方法及终端设备
WO2019178874A1 (zh) 一种切换方法及装置、计算机存储介质
WO2020221263A1 (zh) 通信方法及其装置
WO2021013236A1 (zh) 副链路数据复制功能控制、信息配置方法和设备
TW201911948A (zh) 雙連接中的複製數據傳輸功能的控制方法和設備
WO2019129252A1 (zh) 一种通知执行pdcp数据恢复的方法及设备
WO2019047123A1 (zh) 用于传输数据的方法、终端设备和网络设备
WO2009111961A1 (zh) 对承载的处理方法及移动管理设备
WO2019014916A1 (zh) 处理数据的方法和设备
WO2019037586A1 (zh) 一种重复传输的激活/去激活方法、基站、终端及装置
RU2732488C1 (ru) Устройство связи, способ связи и компьютерная программа
WO2020093965A1 (zh) 无线通信的方法和设备
CA3068640C (en) Control method, node, and computer storage medium
WO2013102374A1 (zh) 用户设备在无线网络控制器之间迁移的方法、装置及系统
WO2023093285A1 (zh) 一种通信方法及终端
US8412159B2 (en) Method, apparatus and computer program product for security configuration coordination during a cell update procedure
WO2009043306A1 (fr) Procédé pour la négociation d&#39;une configuration et appareil associé
WO2019148369A1 (zh) 一种终端设备触发数据停止传输的方法及终端设备
EP3668168A1 (en) Data transmission method and device, network side apparatus, terminal, and computer readable storage medium
JP7475493B2 (ja) 整合性保護失敗の処理方法、装置及びユーザ機器
US20140031025A1 (en) Method, apparatus and computer program product for security configuration coordination during a cell update procedure
WO2019148373A1 (zh) 一种终端设备去激活辅小区的方法及终端设备
CN111314272A (zh) 一种任务处理方法及装置
US11968728B2 (en) Method of configuring service data adaptation protocol entity and device

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: 18841832

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018841832

Country of ref document: EP

Effective date: 20200302