WO2019153285A1 - Procédé de configuration d'entité rlc, et dispositif associé - Google Patents

Procédé de configuration d'entité rlc, et dispositif associé Download PDF

Info

Publication number
WO2019153285A1
WO2019153285A1 PCT/CN2018/076075 CN2018076075W WO2019153285A1 WO 2019153285 A1 WO2019153285 A1 WO 2019153285A1 CN 2018076075 W CN2018076075 W CN 2018076075W WO 2019153285 A1 WO2019153285 A1 WO 2019153285A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc entity
user equipment
rlc
entity
suspending
Prior art date
Application number
PCT/CN2018/076075
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 CN201880003256.4A priority Critical patent/CN109644359B/zh
Priority to PCT/CN2018/076075 priority patent/WO2019153285A1/fr
Publication of WO2019153285A1 publication Critical patent/WO2019153285A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0238—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is an unwanted signal, e.g. interference or idle signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0241—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where no transmission is received, e.g. out of range of the transmitter
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method for configuring an RLC entity and related devices.
  • Radio Resource Control RRC
  • Packet Data Convergence Protocol PDCP
  • Radio Radio link layer control protocol
  • RLC Link Control
  • MAC Media Access Control
  • the embodiment of the present application provides a method for configuring an RLC entity and related devices, which are used to improve the function of the RLC entity in the case of a radio link failure, and save power consumption of the device.
  • the embodiment of the present application provides a method for configuring an RLC entity, which is applied to a user equipment, where the user equipment includes an RLC entity, including:
  • the user equipment In the case that the user equipment triggers a link failure, the user equipment configures a related operation of suspending the RLC entity.
  • the embodiment of the present application provides a user equipment, where the user equipment includes an RLC entity, including:
  • a processing unit configured to configure a related operation of suspending the RLC entity if the user equipment triggers a link failure.
  • an embodiment of the present application provides a user equipment, including one or more processors, one or more memories, one or more transceivers, and one or more programs, where the one or more programs are Stored in the memory and configured to be executed by the one or more processors, the program comprising instructions for performing the steps in the method of the first aspect.
  • an embodiment of the present application provides a computer readable storage medium storing a computer program for electronic data exchange, wherein the computer program causes a computer to perform the portion described by the method of the first aspect or Instructions for all steps.
  • an embodiment of the present application provides a computer program product, where the computer program product includes a non-transitory computer readable storage medium storing a computer program, the computer program being operative to cause a computer to perform the first aspect
  • the instructions of some or all of the steps described in the method can be a software installation package.
  • the user equipment configures the related operation of suspending the RLC entity, and improves the function of the RLC entity in case the radio link fails.
  • the failure of the radio link indicates that the user equipment cannot accurately transmit data to the network device.
  • the user equipment configuration suspends the related operations of the RLC entity, which can reduce power consumption and save power consumption of the device.
  • FIG. 1 is a schematic structural diagram of a wireless communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of a user equipment according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • 4A is a schematic flowchart of a method for configuring an RLC entity according to an embodiment of the present application
  • 4B is a schematic diagram of a protocol stack provided by an embodiment of the present application.
  • 4C is a schematic diagram of another protocol stack provided by an embodiment of the present application.
  • 4D is a schematic diagram of an aggregate carrier provided by an embodiment of the present application.
  • 4E is a schematic diagram of another aggregate carrier provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of another user equipment according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of another user equipment according to an embodiment of the present application.
  • FIG. 1 shows a wireless communication system to which the present application relates.
  • the wireless communication system is not limited to a Long Term Evolution (LTE) system, and may be a fifth-generation mobile communication (the 5th Generation, 5G) system, an NR system, and a machine to machine communication (Machine to Machine, M2M) system, etc.
  • LTE Long Term Evolution
  • 5G fifth-generation mobile communication
  • NR NR
  • M2M Machine to Machine
  • wireless communication system 100 can include one or more network devices 101 and one or more user devices 102. among them:
  • the network device 101 may be a base station, and the base station may be used to communicate with one or more user equipments, or may be used to communicate with one or more base stations having partial user equipment functions (such as a macro base station and a micro base station, such as access). Point, communication between).
  • the base station may be a Base Transceiver Station (BTS) in a Time Division Synchronous Code Division Multiple Access (TD-SCDMA) system, or may be an evolved base station in an LTE system (Evolutional Node B). , eNB), and base stations in 5G systems, new air interface (NR) systems.
  • the base station may also be an Access Point (AP), a TransNode (Trans TRP), a Central Unit (CU), or other network entity, and may include some or all of the functions of the above network entities. .
  • User equipment 102 may be distributed throughout wireless communication system 100, either stationary or mobile.
  • terminal 102 may be a mobile device, a mobile station, a mobile unit, an M2M terminal, a wireless unit, a remote unit, a user agent, a mobile client, and the like.
  • network device 101 can be used to communicate with user device 102 over wireless interface 103 under the control of a network device controller (not shown).
  • the network device controller may be part of the core network or may be integrated into the network device 101.
  • the network device 101 and the network device 101 can also communicate with each other directly or indirectly via a blackhaul interface 104 (such as an X2 interface).
  • the user equipment in the case that the user equipment fails to trigger the radio link, the user equipment configures the related operations of the PDCP entity, so that the PDCP entity is configured correspondingly if the radio link fails.
  • the failure of the radio link indicates that the user equipment cannot accurately transmit the data to the network device.
  • the user equipment configures the PDCP entity to suspend transmission of data to the first RLC entity, so that the first RLC entity can continue to transmit data (ie, the user equipment). Continue to transmit data to network devices) and cause waste of resources.
  • the wireless communication system 100 shown in FIG. 1 is only for the purpose of more clearly explaining the technical solutions of the present application, and does not constitute a limitation of the present application.
  • Those skilled in the art may know that with the evolution of the network architecture and new services, The appearance of the scenario, the technical solution provided by the present application is equally applicable to similar technical problems.
  • user equipment 200 can include: one or more user equipment processors 201, memory 202, communication interface 203, receiver 205, transmitter 206, coupler 207, antenna 208, user interface 202, and inputs.
  • the output module (including the audio input and output module 210, the key input module 211, the display 212, and the like). These components can be connected by bus 204 or other means, and FIG. 2 is exemplified by a bus connection. among them:
  • Communication interface 203 can be used for user equipment 200 to communicate with other communication devices, such as network devices.
  • the network device may be the network device 300 shown in FIG. 3.
  • the communication interface 203 may be a Long Term Evolution (LTE) (4G) communication interface, or may be a 5G or a future communication interface of a new air interface.
  • LTE Long Term Evolution
  • 5G Fifth Generation
  • the user equipment 200 may also be configured with a wired communication interface 203, such as a Local Access Network (LAN) interface.
  • LAN Local Access Network
  • Transmitter 206 can be used to perform transmission processing, such as signal modulation, on signals output by user equipment processor 201.
  • Receiver 205 can be used to perform reception processing, such as signal demodulation, on the mobile communication signals received by antenna 208.
  • transmitter 206 and receiver 205 can be viewed as a wireless modem. In the user equipment 200, the number of the transmitter 206 and the receiver 205 may each be one or more.
  • the antenna 208 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in a transmission line.
  • the coupler 207 is configured to divide the mobile communication signal received by the antenna 308 into multiple channels and distribute it to a plurality of receivers 205.
  • the user equipment 200 may also include other communication components such as a GPS module, a Bluetooth module, a Wireless Fidelity (Wi-Fi) module, and the like. Without being limited to the wireless communication signals described above, the user equipment 200 may also support other wireless communication signals, such as satellite signals, short wave signals, and the like. Not limited to wireless communication, the user equipment 200 may also be configured with a wired network interface (such as a LAN interface) to support wired communication.
  • a wired network interface such as a LAN interface
  • the input and output module can be used to implement interaction between the household device 200 and the user/external environment, and can mainly include an audio input and output module 210, a key input module 211, a display 212, and the like. Specifically, the input and output module may further include: a camera, a touch screen, a sensor, and the like. The input and output modules communicate with the user equipment processor 201 through the user interface 209.
  • Memory 202 is coupled to terminal processor 201 for storing various software programs and/or sets of instructions.
  • memory 202 can include high speed random access memory, and can also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices.
  • the memory 202 can store an operating system (hereinafter referred to as a system) such as an embedded operating system such as ANDROID, IOS, WINDOWS, or LINUX.
  • the memory 202 can also store a network communication program that can be used to communicate with one or more additional devices, one or more user devices, one or more network devices.
  • the memory 202 can also store a user interface program, which can realistically display the content of the application through a graphical operation interface, and receive user control operations on the application through input controls such as menus, dialog boxes, and keys. .
  • the memory 202 may be used to store an implementation program of the RLC entity configuration method provided by one or more embodiments of the present application on the user equipment 200 side.
  • the configuration method of the RLC entity provided by one or more embodiments of the present application refer to the following method embodiments.
  • user device processor 201 is operable to read and execute computer readable instructions.
  • the user equipment processor 201 can be used to invoke a program stored in the memory 212.
  • the configuration method of the RLC entity provided by one or more embodiments of the present application is implemented on the user equipment 200 side, and the program is executed. Instructions.
  • the user equipment 200 shown in FIG. 2 is only one implementation of the embodiment of the present application. In an actual application, the user equipment 200 may further include more or fewer components, which are not limited herein.
  • FIG. 3 illustrates a network device 300 provided by some embodiments of the present application.
  • network device 300 can include one or more network device processors 301, memory 302, communication interface 303, transmitter 305, receiver 306, coupler 307, and antenna 308. These components can be connected via bus 304 or other types, and FIG. 4 is exemplified by a bus connection. among them:
  • Communication interface 303 can be used by network device 300 to communicate with other communication devices, such as user devices or other network devices.
  • the user equipment may be the user equipment 200 shown in FIG. 2.
  • the communication interface 303 may be a Long Term Evolution (LTE) (4G) communication interface, or may be a 5G or a future communication interface of a new air interface.
  • LTE Long Term Evolution
  • the network device 300 may also be configured with a wired communication interface 303 to support wired communication.
  • the backhaul link between one network device 300 and other network devices 300 may be a wired communication connection.
  • Transmitter 305 can be used to perform transmission processing, such as signal modulation, on signals output by network device processor 301.
  • Receiver 306 can be used to perform reception processing on the mobile communication signals received by antenna 308. For example, signal demodulation.
  • transmitter 305 and receiver 306 can be viewed as a wireless modem. In the network device 300, the number of the transmitter 305 and the receiver 306 may each be one or more.
  • the antenna 308 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in a transmission line.
  • Coupler 307 can be used to divide the mobile pass signal into multiple channels and distribute it to multiple receivers 306.
  • Memory 302 is coupled to network device processor 301 for storing various software programs and/or sets of instructions.
  • memory 302 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices.
  • the memory 302 can store an operating system (hereinafter referred to as a system) such as an embedded operating system such as uCOS, VxWorks, or RTLinux.
  • the memory 402 can also store a network communication program that can be used to communicate with one or more additional devices, one or more terminal devices, one or more network devices.
  • the network device processor 301 can be used to perform wireless channel management, implement call and communication link establishment and teardown, and provide cell handover control and the like for users in the control area.
  • the network device processor 301 may include: an Administration Module/Communication Module (AM/CM) (a center for voice exchange and information exchange), and a Basic Module (BM). Complete call processing, signaling processing, radio resource management, radio link management and circuit maintenance functions, Transcoder and SubMultiplexer (TCSM) (for multiplexing demultiplexing and code conversion) Function) and so on.
  • AM/CM Administration Module/Communication Module
  • BM Basic Module
  • TCSM Transcoder and SubMultiplexer
  • the memory 302 can be used to store an implementation program of the RLC entity configuration method provided by one or more embodiments of the present application on the network device 300 side.
  • the configuration method of the RLC entity provided by one or more embodiments of the present application refer to the following method embodiments.
  • the network device processor 301 can be used to read and execute computer readable instructions. Specifically, the network device processor 301 can be used to invoke a program stored in the memory 302. For example, the configuration method of the RLC entity provided by one or more embodiments of the present application is implemented on the network device 300 side, and the program is executed. Instructions.
  • the network device 300 shown in FIG. 3 is only one implementation of the embodiment of the present application. In actual applications, the network device 300 may further include more or fewer components, which are not limited herein.
  • the embodiment of the present application provides a method for configuring an RLC entity.
  • FIG. 4A is a schematic flowchart of a method for configuring an RLC entity according to an embodiment of the present disclosure. The method is applied to a user equipment, where the user equipment includes an RLC entity, and the following steps are included:
  • Step 401 In a case that the user equipment triggers a link failure, the user equipment configures a related operation of suspending the RLC entity.
  • the user equipment includes one RLC entity, or the user equipment includes two RLC entities.
  • the user equipment includes an RLC entity, and the specific protocol structure is as shown in FIG. 4B.
  • the CA Carrier Aggregation
  • the CA if the user equipment is configured with the duplicate data transmission, the user equipment includes two RLC entities, and the specific protocol structure is as shown in FIG. 4C.
  • the PDCP entity is located above the RLC entity, and the PDCP entity is configured to process the RRC message on the control plane and the IP data packet on the user plane.
  • the RLC entity is located above the MAC entity, and the RLC entity is used to provide segmentation and retransmission services for user data and control data.
  • the CA technology can aggregate 2 to 5 carriers to achieve a transmission bandwidth of up to 100 MHz.
  • the CA function can support continuous CA or non-continuous CA.
  • a continuous CA is transmitted (as specifically shown in FIG. 4D).
  • carrier 1, carrier 2, and carrier 3 are adjacent to each other, and they can be aggregated for communication between the user equipment and the network device.
  • a discontinuous CA occurs (as specifically shown in FIG. 4E).
  • carrier 1, carrier 2, and carrier 3 are separated along a frequency band, which can be aggregated for communication between the user equipment and the network device.
  • the PDCP entity is located above the RLC entity, and the PDCP entity is configured to process the RRC message on the control plane and the IP data packet on the user plane.
  • the wireless link failure refers to one communication failure in the communication channel.
  • the signal quality drops during communication and communication cannot be successfully performed, it is determined that the wireless link has failed.
  • the user equipment triggering the radio link failure may be triggered by the user equipment receiving the radio link failure indication from the network device; or the user equipment detecting that one or more carriers are generated. Triggered if the radio link fails; or the user equipment triggers when it detects that one or more RLC entities reach the maximum number of retransmissions, and so on.
  • the pause refers to stopping in a certain process, and then proceeding to the process.
  • the related operation of suspending the RLC entity refers to the service that the RLC entity stops for a while after the user equipment processes the service, and the subsequent RLC entity performs the subsequent execution.
  • the specific implementation manner in which the user equipment is configured to suspend the related operations of the RLC entity may be: the user equipment may configure to suspend the related operations of the RLC entity by using inter-entity interaction signaling.
  • the user equipment configures the related operation of suspending the RLC entity, and improves the function of the RLC entity in case the radio link fails.
  • the failure of the radio link indicates that the user equipment cannot accurately transmit data to the network device.
  • the user equipment configuration suspends the related operations of the RLC entity, which can reduce power consumption and save power consumption of the device.
  • the RLC entity includes a first RLC entity
  • the user equipment triggers a link failure, including:
  • the user equipment triggers a link failure.
  • the number of retransmissions of the first RLC entity is equal to the set threshold value, indicating that the first RLC entity has reached the maximum number of retransmissions, and the radio link fails on the link where the first RLC entity is located.
  • the threshold value may be set by the protocol, or may be configured by the network device to the user equipment, and is not limited herein.
  • any radio network link fails in any RLC entity, the user equipment triggers the radio link failure.
  • the user equipment initiates an RRC connection re-establishment process to restore the connection between the user equipment and the network device.
  • the RRC connection re-establishment process is too long, which increases the length of time that the user equipment is in poor signal quality, thereby reducing the efficiency of the user equipment processing service.
  • the user equipment when the number of retransmissions of the first RLC entity is equal to the set threshold, the user equipment triggers the radio link failure. If the user equipment does not need to initiate an RRC re-establishment process after the user equipment fails to trigger the radio link, the unnecessary RRC re-establishment process can be avoided, and the duration of the signal quality of the user equipment is shortened, thereby improving the processing of the user equipment. Business efficiency.
  • the suspending the RLC entity related operation includes the first RLC entity suspending transmission of data to the MAC entity.
  • the first RLC entity has failed to transmit data to the network device because the link where the first RLC entity is located has failed.
  • the first RLC is The entity suspends the transmission of data to the MAC entity, which avoids the problem of wasted resources.
  • the logical channel of the first RLC entity maps at least one secondary cell (SCell).
  • the logical channel of the first RLC entity maps at least one secondary cell.
  • the primary cell refers to a cell that operates at the primary frequency point.
  • the secondary cell is a cell operating at a secondary frequency point.
  • the frequency point refers to a specific absolute frequency value, which is generally the center frequency of the modulated signal.
  • the center frequency of the primary carrier is called the primary frequency point, and the center frequency of the secondary carrier is called the secondary frequency point.
  • the user equipment further includes a PDCP entity, where the user equipment includes two RLC entities used by the PDCP entity to perform the CA replication data transmission, where the configuration is CA replication data transmission,
  • the RLC entities include the first RLC entity.
  • the first RLC entity is one of FIG. 4C.
  • the user equipment further includes a second RLC entity
  • the related operation of the suspended RLC entity includes the second RLC entity suspending transmission of data to the MAC entity.
  • the first RLC entity is different from the second RLC entity.
  • the signal quality of the user equipment is deteriorated due to the radio link failure of the link where the first RLC entity is located.
  • the second RLC entity directly suspends transmission of data to the MAC entity, avoiding the second RLC.
  • the entity continues to transmit data downwards (ie, the user equipment continues to transmit data to the network device), thereby avoiding the problem of wasted resources.
  • the logical channel of the second RLC entity maps at least one secondary cell.
  • the logical channel of the second RLC entity maps at least one secondary cell without being configured for CA replication data transmission.
  • the user equipment further includes a PDCP entity, where the user equipment includes two PDCP entities for performing the CA replication data transmission, where configured as a CA replication data transmission.
  • An RLC entity the two RLC entities including the second RLC entity.
  • the second RLC entity is one of FIG. 4C.
  • the user equipment further includes a PDCP entity, where the user equipment includes two PDCP entities for performing the CA replication data transmission, where configured as a CA replication data transmission.
  • An RLC entity the two RLC entities including the first RLC entity and the second RLC entity.
  • the first RLC entity and the second RLC entity are two RLC entities in FIG. 4C.
  • the serving cell group of the first RLC entity and the second RLC entity is a Secondary Cell Group (SCG).
  • SCG Secondary Cell Group
  • the serving cell group of the first RLC entity and the second RLC entity is a Primary Cell Group (SCG).
  • SCG Primary Cell Group
  • the serving cell group of the first RLC entity is different from the serving cell group of the second RLC entity.
  • the serving cell group of the first RLC entity is a secondary cell group
  • the serving cell group of the second RLC entity is a primary cell group.
  • the serving cell group of the first RLC entity is a primary cell group
  • the serving cell group of the second RLC entity is a secondary cell group.
  • each carrier corresponds to one cell.
  • the cell operating at the primary frequency point is the primary cell.
  • the cell operating at the secondary frequency point is a secondary cell.
  • a plurality of secondary cells form a secondary cell group.
  • a plurality of primary cells constitute a primary cell group.
  • the first RLC entity and the second RLC entity correspond to at least one identical carrier.
  • the first RLC entity corresponds to carrier 1, carrier 3, and the second RLC entity corresponds to carrier 1, carrier 2, and carrier 3, it can be seen that the first RLC entity and the second RLC entity correspond to two identical carriers.
  • At least one carrier corresponding to the second RLC entity is deactivated.
  • all carriers corresponding to the second RLC entity are deactivated.
  • the data transmission function of the carrier needs to be activated or deactivated by signal indication.
  • the carrier is activated to indicate that the data transmission function of the carrier is enabled, and the carrier is capable of data transmission. Deactivating the carrier indicates that the data transmission function of the carrier is not enabled, and the carrier cannot perform data transmission.
  • the user equipment when the carrier is deactivated, performs at least one of the following operations in the carrier: 1) not transmitting a Sounding Reference Signal (SRS); 2) not reporting a physical uplink control channel (Physical) Uplink Control CHannel, PUCCH) Channel Quality Indicator (CQI), rank indication (RI), Precoding Matrix Indicator (PMI), Channel State Information Reference Signal At least one of CRS); 3) not transmitting uplink data; 4) not detecting physical downlink control channel information (Physical Downlink Control Channel, PDCCH) for the carrier and transmitting on the carrier; 5) not transmitting random Access channel information (Random Access Channel, RACH).
  • SRS Sounding Reference Signal
  • PUCCH Physical Uplink Control CHannel
  • CQI Channel Quality Indicator
  • RI rank indication
  • PMI Precoding Matrix Indicator
  • RACH Random Access Channel
  • the related operation of suspending the RLC entity includes the RLC entity suspending the relevant counter.
  • the related operation of suspending the RLC entity includes the first RLC entity suspending the relevant counter; in the case that the second RLC entity suspends transmitting data to the MAC entity, The related operation of suspending the RLC entity includes suspending the correlation counter by the second RLC entity; in the case that the first RLC entity and the second RLC entity suspend transmission of data to the MAC entity, the related operation of suspending the RLC entity includes the first RLC entity The associated counter is suspended with the second RLC entity.
  • the related counter includes at least one of the following: t-PollRetransmit, t-Reassembly, and t-StatusProhibit.
  • the t-PollRetransmit refers to a polling retransmission timer, which is used to indicate that the transmitting end controls the retransmission interval of the polling.
  • t-Reassembly refers to the reassembly interval timer.
  • the t-StatusProhibit refers to a status report prohibition timer, which is used to indicate the transmission interval of the receiver control status report.
  • the related operation of suspending the RLC entity includes the RLC entity modifying a related variable of the RLC AM or the RLC UM.
  • the related operation of suspending the RLC entity includes: the first RLC entity modifies a related variable of the RLC AM or the RLC UM; and the second RLC entity suspends to the MAC entity
  • the related operation of suspending the RLC entity includes the second RLC entity modifying the relevant variable of the RLC AM or the RLC UM; in the case that the first RLC entity and the second RLC entity suspend transmission of data to the MAC entity,
  • the related operations of suspending the RLC entity include the first RLC entity and the second RLC entity modifying the relevant variables of the RLC AM or RLC UM.
  • the related variables of the RLC AM include at least one of the following: TX_Next_Ack, TX_Next, POLL_SN, PDU_WITHOUT_POLL, and BYTE_WITHOUT_POLL.
  • TX_Next_Ack represents the next transmission signal confirmation frame.
  • TX_Next represents the next data that is expected to be sent.
  • the Acknowledged Mode is to ensure the correct transmission of the RLC PDU.
  • ARQ Automatic Repeat-reQuest
  • a polling mechanism is introduced to enable the transmitting end to receive from the receiving end.
  • Receive status report STATUS PDU
  • NACK NACK information.
  • the PDU_WITHOUT_POLL refers to the total number of acknowledged mode data protocol data units (AMD PDUs) sent after the last polling process.
  • BYTE_WITHOUT_POLL refers to the total number of bytes sent after the last polling process is recorded.
  • the POLL_SN is a sequence number of a Radio Link Control Data Protocol Data Unit (RDC data PDU) in which the last discriminant test field is set to 1.
  • RDC data PDU Radio Link Control Data Protocol Data Unit
  • RLC UM includes TX_Next (TX side).
  • TX_Next indicates the transmission traffic of the next cycle of the transmitting end.
  • the related operation of suspending the RLC entity includes the RLC entity modifying the corresponding carrier.
  • the related operation of the suspended RLC entity includes: the first RLC entity modifies the corresponding carrier; and in the case that the second RLC entity suspends transmitting data to the MAC entity, And the related operation of the suspended RLC entity includes: modifying, by the second RLC entity, the corresponding carrier; where the first RLC entity and the second RLC entity suspend transmitting data to the MAC entity, the related operation of the suspended RLC entity includes the first The RLC entity and the second RLC entity modify the corresponding carrier.
  • the modifying the corresponding carrier includes at least one of the following: releasing the restriction of the corresponding carrier set, so that the RLC entity corresponds to all carriers; configuring the RLC entity to correspond only to the primary cell (Pcell) or the primary secondary cell (PSCell); and the second RLC
  • the carrier corresponding to the entity is removed from the carrier set corresponding to the first RLC entity.
  • the related operation of suspending the RLC entity includes the RLC entity performing a packet loss operation.
  • the related operation of suspending the RLC entity includes the first RLC entity performing a packet loss operation; and in the case that the second RLC entity suspends transmitting data to the MAC entity, And the related operation of the suspended RLC entity includes: performing, by the second RLC entity, a packet loss operation; where the first RLC entity and the second RLC entity suspend transmitting data to the MAC entity, the related operation of the suspended RLC entity includes the first The RLC entity and the second RLC entity perform a packet loss operation.
  • the performing the packet loss operation by the RLC entity includes discarding all or part of the data packet that does not correspond to the RLC PDU, and/or the packet loss operation includes discarding all the data packets that do not cause the RLC SN gap to be generated.
  • FIG. 5 is a user equipment 500 according to an embodiment of the present application.
  • the user equipment 500 includes an RLC entity, where the user equipment 500 includes: one or more processors, one or more memories, one or more a transceiver, and one or more programs;
  • the one or more programs are stored in the memory and configured to be executed by the one or more processors;
  • the program includes instructions for performing the following steps:
  • the related operation of suspending the RLC entity is configured.
  • the user equipment configures the related operation of suspending the RLC entity, and improves the function of the RLC entity in case the radio link fails.
  • the failure of the radio link indicates that the user equipment cannot accurately transmit data to the network device.
  • the user equipment configuration suspends the related operations of the RLC entity, which can reduce power consumption and save power consumption of the device.
  • the RLC entity includes a first RLC entity
  • the user equipment triggers a link failure, including:
  • the user equipment triggers a link failure.
  • the suspending the RLC entity related operation includes the first RLC entity suspending transmission of data to the medium access control MAC entity.
  • the logical channel of the first RLC entity maps at least one secondary cell.
  • the user equipment further includes a PDCP entity, where the user equipment includes two PDCP entities for performing the CA replication data transmission, where configured as a CA replication data transmission.
  • An RLC entity the two RLC entities including the first RLC entity.
  • the user equipment further includes a second RLC entity
  • the related operation of the suspended RLC entity includes the second RLC entity suspending transmission of data to the MAC entity.
  • the logical channel of the second RLC entity maps at least one secondary cell.
  • the user equipment further includes a PDCP entity, where the user equipment includes two PDCP entities for performing the CA replication data transmission, where configured as a CA replication data transmission.
  • An RLC entity the two RLC entities including the second RLC entity.
  • the user equipment further includes a PDCP entity, where the user equipment includes two RLC entities used by the PDCP entity to perform the CA replication data transmission.
  • the two RLC entities include the first RLC entity and the second RLC entity.
  • the first RLC entity and the second RLC entity correspond to at least one identical carrier.
  • the serving cell group of the first RLC entity and the second RLC entity is configured as a secondary cell group.
  • the serving cell group of the first RLC entity and the second RLC entity is configured as a primary cell group.
  • At least one carrier corresponding to the second RLC entity is deactivated.
  • all carriers corresponding to the second RLC entity are deactivated.
  • the related operation of suspending the RLC entity includes the RLC entity suspending the relevant counter.
  • the related operation of suspending the RLC entity includes the RLC entity modifying a related variable of the RLC AM or the RLC UM.
  • the related operation of suspending the RLC entity includes the RLC entity modifying the corresponding carrier.
  • the related operation of suspending the RLC entity includes the RLC entity performing a packet loss operation.
  • FIG. 6 is a user equipment 600 according to an embodiment of the present disclosure.
  • the user equipment 600 includes an RLC entity, and the user equipment 600 includes a processing unit 601, a communication unit 602, and a storage unit 603.
  • the processing unit 601 includes receiving Unit and parameter adjustment unit, where:
  • the processing unit 601 is configured to configure a related operation of suspending the RLC entity if the user equipment triggers a link failure.
  • the user equipment configures the related operation of suspending the RLC entity, and improves the function of the RLC entity in case the radio link fails.
  • the failure of the radio link indicates that the user equipment cannot accurately transmit data to the network device.
  • the user equipment configuration suspends the related operations of the RLC entity, which can reduce power consumption and save power consumption of the device.
  • the RLC entity includes a first RLC entity
  • the user equipment triggers a link failure, including:
  • the user equipment triggers a link failure.
  • the suspending the RLC entity related operation includes the first RLC entity suspending transmission of data to the medium access control MAC entity.
  • the logical channel of the first RLC entity maps at least one secondary cell.
  • the user equipment further includes a PDCP entity, where the user equipment includes two PDCP entities for performing the CA replication data transmission, where configured as a CA replication data transmission.
  • An RLC entity the two RLC entities including the first RLC entity.
  • the user equipment further includes a second RLC entity
  • the related operation of the suspended RLC entity includes the second RLC entity suspending transmission of data to the MAC entity.
  • the logical channel of the second RLC entity maps at least one secondary cell.
  • the user equipment further includes a PDCP entity, where the user equipment includes two PDCP entities for performing the CA replication data transmission, where configured as a CA replication data transmission.
  • An RLC entity the two RLC entities including the second RLC entity.
  • the user equipment further includes a PDCP entity, where the user equipment includes two RLC entities used by the PDCP entity to perform the CA replication data transmission.
  • the two RLC entities include the first RLC entity and the second RLC entity.
  • the first RLC entity and the second RLC entity correspond to at least one identical carrier.
  • the serving cell group of the first RLC entity and the second RLC entity is configured as a secondary cell group.
  • the serving cell group of the first RLC entity and the second RLC entity is configured as a primary cell group.
  • At least one carrier corresponding to the second RLC entity is deactivated.
  • all carriers corresponding to the second RLC entity are deactivated.
  • the related operation of suspending the RLC entity includes the RLC entity suspending the relevant counter.
  • the related operation of suspending the RLC entity includes the RLC entity modifying a related variable of the RLC AM or the RLC UM.
  • the related operation of suspending the RLC entity includes the RLC entity modifying the corresponding carrier.
  • the related operation of suspending the RLC entity includes the RLC entity performing a packet loss operation.
  • the processing unit 601 may be a processor or a controller, and may be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application specific integrated circuit (Application- Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof, which may be implemented or executed in conjunction with the present disclosure.
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC Application- Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication unit 602 can be a transceiver, a transceiver circuit, a radio frequency chip, a communication interface, etc.
  • the storage unit 603 can be a memory.
  • the processing unit 601 is a processor
  • the communication unit 602 is a communication interface
  • the storage unit 603 is a memory
  • the user equipment involved in the embodiment of the present application may be the user equipment shown in FIG. 5.
  • the embodiment of the present application further provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program for electronic data exchange, wherein the computer program causes the computer to execute a user in the method embodiment as described above Some or all of the steps described by the device.
  • the embodiment of the present application further provides a computer program product, wherein the computer program product comprises a non-transitory computer readable storage medium storing a computer program, the computer program being operative to cause a computer to execute a user as in the above method Some or all of the steps described by the device.
  • the computer program product can be a software installation package.
  • the steps of the method or algorithm described in the embodiments of the present application may be implemented in a hardware manner, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in an access network device, a target network device, or a core network device. Of course, the processor and the storage medium may also exist as discrete components in the access network device, the target network device, or the core network device.
  • the functions described in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • 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.
  • the processes or functions described in accordance with embodiments of the present application are 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 can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)). )Wait.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a digital video disc (DVD)
  • DVD digital video disc
  • SSD solid state disk

Abstract

La présente invention concerne, selon un mode de réalisation, un procédé de configuration d'entité RLC, et un dispositif associé. Le procédé est appliqué dans une unité équipement utilisateur comprenant une entité RLC. Selon le procédé, lors d'un échec de déclenchement de liaison, l'unité équipement utilisateur interrompt les activités associées de l'entité RLC. Le mode de réalisation de la présente invention améliore une fonction d'une entité RLC en cas d'échec de liaison radio et réduit la consommation en énergie d'un dispositif.
PCT/CN2018/076075 2018-02-09 2018-02-09 Procédé de configuration d'entité rlc, et dispositif associé WO2019153285A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201880003256.4A CN109644359B (zh) 2018-02-09 2018-02-09 Rlc实体的配置方法及相关设备
PCT/CN2018/076075 WO2019153285A1 (fr) 2018-02-09 2018-02-09 Procédé de configuration d'entité rlc, et dispositif associé

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/076075 WO2019153285A1 (fr) 2018-02-09 2018-02-09 Procédé de configuration d'entité rlc, et dispositif associé

Publications (1)

Publication Number Publication Date
WO2019153285A1 true WO2019153285A1 (fr) 2019-08-15

Family

ID=66060285

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/076075 WO2019153285A1 (fr) 2018-02-09 2018-02-09 Procédé de configuration d'entité rlc, et dispositif associé

Country Status (2)

Country Link
CN (1) CN109644359B (fr)
WO (1) WO2019153285A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112073210A (zh) * 2019-06-11 2020-12-11 夏普株式会社 由用户设备执行的方法以及用户设备
CN115118400A (zh) * 2021-03-17 2022-09-27 上海朗帛通信技术有限公司 一种被用于无线通信的方法和设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102104892A (zh) * 2009-12-22 2011-06-22 中兴通讯股份有限公司 检测无线链路失败的方法
CN102223658A (zh) * 2010-04-19 2011-10-19 中兴通讯股份有限公司 一种处理无线链路失败的方法和中继节点
CN105393582A (zh) * 2013-07-17 2016-03-09 Lg电子株式会社 报告无线电链路控制重传失败的方法及其设备
US20160182276A1 (en) * 2013-06-28 2016-06-23 Nokia Solutions And Networks Oy Master base station-controlled response to detected failure of radio link between secondary base station and mobile station in dual connectivity wireless networks
CN106105373A (zh) * 2014-03-18 2016-11-09 夏普株式会社 无线通信系统、终端装置、无线通信方法、集成电路以及处理方法
CN107070607A (zh) * 2008-01-04 2017-08-18 交互数字专利控股公司 一种由wtru实施的方法及该wtru

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107070607A (zh) * 2008-01-04 2017-08-18 交互数字专利控股公司 一种由wtru实施的方法及该wtru
CN102104892A (zh) * 2009-12-22 2011-06-22 中兴通讯股份有限公司 检测无线链路失败的方法
CN102223658A (zh) * 2010-04-19 2011-10-19 中兴通讯股份有限公司 一种处理无线链路失败的方法和中继节点
US20160182276A1 (en) * 2013-06-28 2016-06-23 Nokia Solutions And Networks Oy Master base station-controlled response to detected failure of radio link between secondary base station and mobile station in dual connectivity wireless networks
CN105393582A (zh) * 2013-07-17 2016-03-09 Lg电子株式会社 报告无线电链路控制重传失败的方法及其设备
CN106105373A (zh) * 2014-03-18 2016-11-09 夏普株式会社 无线通信系统、终端装置、无线通信方法、集成电路以及处理方法

Also Published As

Publication number Publication date
CN109644359A (zh) 2019-04-16
CN109644359B (zh) 2020-12-04

Similar Documents

Publication Publication Date Title
JP7018499B2 (ja) 自律アップリンク送信および再送信のための方法
US20210022128A1 (en) Beam indication method, apparatus and system
WO2019153517A1 (fr) Procédé de gestion de défaillance de liaison radio et produit associé
JP2019537857A (ja) Ｈａｒｑタイミング構成の同期制御のためのシステムおよび方法
US10028155B2 (en) Buffer management for wireless networks
WO2016138937A1 (fr) Demandes de suspension et de reprise de connexion pour réseau sans fil
EP3295735B1 (fr) Procédé et appareil de transmission d'informations de commande
WO2021017668A1 (fr) Procédé et dispositif de traitement pour défaillance de faisceaux
US11924875B2 (en) Transmission in unlicensed frequency spectrum
EP3534626B1 (fr) Procédé de traitement dans une réplication de données et dispositif associé
WO2019137641A1 (fr) Soumission d'une pdu pdcp en vue d'une transmission
WO2016161854A1 (fr) Procédé et appareil destinés à la transmission de données
EP3952175A1 (fr) Procédé et appareil de rétablissement après défaillance de faisceau et système de communication
WO2019153285A1 (fr) Procédé de configuration d'entité rlc, et dispositif associé
US20230054066A1 (en) Harq rtt timer adjustment for multi-tb scheduling
US20230088550A1 (en) Conditionally handling hybrid automatic repeat request process in configuration grant activation procedure
WO2019153281A1 (fr) Procédé de configuration pour entité pdcp et dispositif associé
JP7380907B2 (ja) Ｌｂｔ失敗を指示する方法及び装置
WO2019140634A1 (fr) Procédé de réglage de paramètres et dispositif approprié
WO2019090828A1 (fr) Procédé de traitement de réplication de données et dispositif associé
WO2019090964A1 (fr) Procédé de traitement de réplication de données et dispositif associé

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18905840

Country of ref document: EP

Kind code of ref document: A1