WO2019061137A1 - 无线通信的方法和终端设备 - Google Patents

无线通信的方法和终端设备 Download PDF

Info

Publication number
WO2019061137A1
WO2019061137A1 PCT/CN2017/103919 CN2017103919W WO2019061137A1 WO 2019061137 A1 WO2019061137 A1 WO 2019061137A1 CN 2017103919 W CN2017103919 W CN 2017103919W WO 2019061137 A1 WO2019061137 A1 WO 2019061137A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
layer entity
pdcp layer
indication information
information
Prior art date
Application number
PCT/CN2017/103919
Other languages
English (en)
French (fr)
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
Priority to KR1020207006953A priority Critical patent/KR102375440B1/ko
Priority to PCT/CN2017/103919 priority patent/WO2019061137A1/zh
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to JP2020514546A priority patent/JP7024067B2/ja
Priority to MX2020002997A priority patent/MX2020002997A/es
Priority to CN201780092493.8A priority patent/CN110786074A/zh
Priority to BR112020004794-5A priority patent/BR112020004794A2/pt
Priority to CA3075835A priority patent/CA3075835C/en
Priority to CN202010071281.5A priority patent/CN111447610B/zh
Priority to AU2017433998A priority patent/AU2017433998B2/en
Priority to RU2020112505A priority patent/RU2748163C1/ru
Priority to ES17926720T priority patent/ES2907789T3/es
Priority to EP17926720.8A priority patent/EP3661312B1/en
Priority to EP21212114.9A priority patent/EP3982695A1/en
Priority to SG11202002452SA priority patent/SG11202002452SA/en
Priority to TW107133979A priority patent/TW201916656A/zh
Publication of WO2019061137A1 publication Critical patent/WO2019061137A1/zh
Priority to US16/752,377 priority patent/US11483695B2/en
Priority to US17/949,954 priority patent/US11889582B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • 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
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • the present application relates to the field of communications, and more particularly to a method and terminal device for wireless communication.
  • a mobile terminal moves or a network node accessed by a terminal device changes (for example, a network node accessed by a terminal device from a master node (MN))
  • MN master node
  • PDCP Packet Data Convergence Protocol
  • the PDCP layer entity may be arranged in the cloud, that is, different network nodes may have the same PDCP layer entity, and therefore, the PDCP layer entity in the existing LTE system is re-established.
  • the mechanism cannot meet the needs of 5G systems.
  • the embodiment of the present application provides a method and a terminal device for wireless communication, which can flexibly determine whether a PDCP layer entity needs to be re-established according to the configuration information of the network device, and avoid performing a re-establishment operation when the PDCP layer entity does not need to be re-established. , reducing signaling overhead.
  • an embodiment of the present application provides a method for wireless communication, including:
  • the terminal device receives configuration information, which is sent by the network device, for performing mobility management on the terminal device, where the configuration information includes indication information, where the indication information is used to configure a packet data convergence protocol PDCP layer entity;
  • the terminal device determines, according to the indication information, whether to re-establish the PDCP layer entity.
  • the terminal device determines whether to re-establish the PDCP layer entity according to the indication information used by the network device to configure the PDCP layer entity, so that the terminal device needs to re-establish the PDCP layer entity.
  • the re-establishment operation is performed, the re-establishment operation is not performed when the PDCP layer entity does not need to be re-established, thereby avoiding the signaling overhead caused by performing the re-establishment operation when the PDCP layer entity is not required to be re-established.
  • the indication information is key information
  • the terminal device determines, according to the indication information, whether to re-establish the PDCP layer entity, including:
  • the terminal device Upon determining that the key information of the current PDCP layer entity changes, the terminal device re-establishes the PDCP layer entity.
  • the network device may re-establish the PDCP layer entity by implicitly indicating the key information.
  • the indication information is key information
  • the terminal device determines, according to the indication information, whether to re-establish the PDCP layer entity, including:
  • the terminal device When it is determined that the key information of the current PDCP layer entity remains unchanged, the terminal device does not re-establish the PDCP layer entity.
  • the network device may implicitly indicate that the PDCP layer entity is not re-established by using the key information.
  • the terminal device when some or all of the network nodes that are accessed by the terminal device are changed, the terminal device receives the configuration information sent by the network device.
  • the network device configures the indication information when the part or all of the network nodes accessed by the terminal device change, thereby guiding the terminal device to determine whether to re-establish the PDCP layer entity.
  • the method further includes:
  • the terminal device determines that the compression algorithm needs to be reset.
  • the method further includes:
  • the terminal device determines that the encryption and decryption algorithm needs to be reconfigured.
  • the method further includes:
  • the terminal device determines that the process variable needs to be reset.
  • the embodiment of the present application provides a terminal device, which can execute the module or unit of the method in the first aspect or any optional implementation manner of the first aspect.
  • a terminal device comprising a processor, a memory, and a communication interface.
  • the processor is coupled to the memory and communication interface.
  • the memory is for storing instructions for the processor to execute, and the communication interface is for communicating with other network elements under the control of the processor.
  • the processor executes the instructions stored by the memory, the executing causes the processor to perform the first aspect or the first A method in any possible implementation of the aspect.
  • a computer storage medium storing program code for instructing a computer to perform the method of any of the first aspect or the first aspect of the first aspect. instruction.
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform the methods described in the various aspects above.
  • FIG. 1 shows a wireless communication system to which the embodiment of the present application is applied.
  • FIG. 2 is a schematic diagram showing a dual connectivity system architecture applied in an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a method for wireless communication according to an embodiment of the present application.
  • FIG. 4 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of an apparatus for wireless communication provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a system chip according to an embodiment of the present application.
  • the technical solution of the embodiment of the present application can be applied to a dual connectivity (DC) communication system, for example, a communication system in which LTE and 5G NR are dual-connected, and can also be applied to an NR communication system.
  • DC dual connectivity
  • FIG. 1 shows a wireless communication system 100 to which an embodiment of the present application is applied.
  • the wireless communication system 100 can include a network device 110.
  • Network device 110 may be a device that communicates with a terminal device.
  • Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices (e.g., UEs) located within the coverage area.
  • the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or may be a base station (NodeB, NB) in a WCDMA system, or may be an evolved base station in an LTE system.
  • BTS Base Transceiver Station
  • NodeB NodeB
  • the network device can be a relay station, an access point, an in-vehicle device, a wearable device, Network-side devices in future 5G networks or network designs in the future evolution of Public Land Mobile Network (PLMN) Prepare.
  • PLMN Public Land Mobile Network
  • the wireless communication system 100 also includes at least one terminal device 120 located within the coverage of the network device 110.
  • Terminal device 120 can be mobile or fixed.
  • the terminal device 120 may refer to an access terminal, a user equipment (User Equipment, UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, and a wireless communication.
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • FIG. 1 exemplarily shows one base station, one core network device, and two terminal devices.
  • the wireless communication system 100 may include multiple base station devices and may include other numbers of terminals within the coverage of each base station.
  • the device is not limited in this embodiment.
  • the wireless communication system 100 may further include a network management function (SMF), a unified data management (UDM), an authentication server function (AUSF), and other network entities.
  • SMS network management function
  • UDM unified data management
  • AUSF authentication server function
  • the application embodiment does not limit this.
  • FIG. 2 is a schematic diagram showing a dual connectivity system architecture applied in an embodiment of the present application.
  • the terminal device can connect two different communication systems at the same time.
  • FIG. 2 is an example in which the terminal device simultaneously connects LTE and NR.
  • the MN node of the terminal device is an LTE communication node, can access a network node supporting LTE communication, or can access a network node supporting NR communication
  • the SN node of the terminal device is an NR communication node, and can access a network node supporting LTE communication. It is also possible to access a network node that supports NR communication.
  • the MN node may also be an NR communication node, may access a network node that supports LTE communication, or may access a network node that supports NR communication, and the SN node of the terminal device may also be an LTE communication node, and may access and support.
  • the network node of the LTE communication can also access the network node supporting the NR communication.
  • the terminal device may maintain a master cell group (MCG) bearer and an MCG offload bearer at the MN node, and maintain a slave cell (SCG) bearer and an SCG offload bearer at the SN node.
  • the SCG bearer connects SN PDCP 1, SN RLC 1 and SN MAC, the SCG offload bearer connects SN PDCP 2, SN RLC 2 and SN MAC, and the SCG offload bearer also connects SN PDCP 2, MN RLC 3 and MN MAC, SN PDCP 2 and MN RLC 3 is connected through the X2 interface.
  • MN PDCP 1 and MN PDCP 2 are only differentiated for convenience of description, and the actual deployment is not necessarily distinguished as shown in FIG. 2, and MN RLC 1, MN RLC 2, and MN RLC 3 are the same.
  • SN PDCP 1 and SN PDCP 2 are the same, and SN RLC 1, SN RLC 2 and SN RLC 3 are the same.
  • the central unit (CU) and the remote unit (Distributed Unit (DU) are separated in the network device accessed by the terminal device, and the LUN and the DU are separated to form the RLC layer/
  • the entities of the MAC layer/physical (PHY) layer are deployed separately from the entities of the PDCP layer. That is, for the entities of the RLC layer/MAC layer/PHY layer, different network nodes have different entities, and the entities for the PDCP layer may be Different network nodes have the same entity, and the entity of this PDCP layer is deployed in the cloud (on the side close to the server).
  • the physical location of the PDCP layer entity does not change, and there is no need to re-establish PDCP.
  • the method for wireless communication may be applied to a terminal device, where the terminal device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also referred to as main memory).
  • the operating system may be any one or more computer operating systems that implement business processing through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system.
  • the application layer includes applications such as browsers, contacts, word processing software, and instant messaging software.
  • the term "article of manufacture” as used in this application is encompassed by any computer.
  • a computer program that reads a device, carrier, or media access may include, but is not limited to, a magnetic storage device (eg, a hard disk, a floppy disk, or a magnetic tape, etc.), such as a compact disc (CD), a digital versatile disc (Digital Versatile Disc, DVD). Etc.), smart cards and flash memory devices (eg, Erasable Programmable Read-Only Memory (EPROM), cards, sticks or key drivers, etc.).
  • a magnetic storage device eg, a hard disk, a floppy disk, or a magnetic tape, etc.
  • CD compact disc
  • DVD Digital Versatile Disc
  • Etc. smart cards and flash memory devices
  • EPROM Erasable Programmable Read-Only Memory
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, a variety of media capable of storing, containing, and/or carrying instructions and/or data.
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • FIG. 3 is a schematic flowchart of a method 200 for wireless communication according to an embodiment of the present application.
  • the method 200 may be performed by a terminal device, which may be a terminal device as shown in FIG. 1, and the terminal device may be applied to a dual connectivity system architecture as shown in FIG.
  • the network device in the network device may be a network device as shown in FIG. 1, which may implement separation of a CU and a DU, and the network device may communicate with a terminal device having a dual connectivity system architecture as shown in FIG. 2.
  • the method 200 includes the following.
  • the terminal device receives, by the network device, configuration information, where the terminal device performs mobility management, where the configuration information includes indication information, where the indication information is used to configure a PDCP layer entity.
  • the network device may send the configuration information to the terminal device in advance, or may send the configuration information to the terminal device when the location where the terminal device is located.
  • the network device may explicitly indicate whether the terminal device re-establishes the PDPC layer entity.
  • the indication information may directly indicate whether the terminal device re-establishes the PDPC layer entity.
  • the indication information may be an identifier bit. When the identifier bit has a value of 0, the terminal device is instructed to re-establish the PDCP layer entity. When the identifier bit has a value of 1, the terminal device is instructed not to re-establish the PDCP layer entity. .
  • the network device may implicitly indicate whether the terminal device re-establishes the PDPC layer entity.
  • the indication information is key information, and the key letter of the current PDCP layer entity is determined.
  • the terminal device re-establishes the PDCP layer entity; when determining that the key information of the PDCP layer entity remains unchanged, the terminal device does not re-establish the PDCP layer entity.
  • each PDCP layer entity is configured with unique key information.
  • the terminal device receives the configuration information sent by the network device.
  • the network device may be a network device where the changed network node is located, that is, a network device where the re-accessed network node is located.
  • the terminal device receives the configuration information sent by the network device, and determines whether to re-establish the PDCP according to the indication information in the configuration information.
  • Layer entity the configuration information sent by the network device, and determines whether to re-establish the PDCP according to the indication information in the configuration information.
  • the terminal device does not re-establish the PDCP layer entity.
  • the terminal device needs to re-establish the PDCP layer entity.
  • the terminal device receives the configuration information sent by the network device, and determines whether to re-establish the PDCP according to the indication information in the configuration information.
  • Layer entity when the SN of the terminal device changes (switching from SN 1 to SN 2), the terminal device receives the configuration information sent by the network device, and determines whether to re-establish the PDCP according to the indication information in the configuration information. Layer entity.
  • the key used is the key for the MN PDCP.
  • the physical location of the PDCP layer entity does not change.
  • the terminal device does not re-establish the PDCP layer entity.
  • the terminal device may be that all network nodes accessed by the terminal device are changed.
  • whether the PDCP layer entity is re-established may be determined by determining whether the key information is changed.
  • the terminal device determines, according to the indication information, whether to re-establish the PDCP layer entity.
  • the terminal device determines that the compression algorithm needs to be reset.
  • the terminal device determines that the encryption and decryption algorithm needs to be reconfigured.
  • the terminal device determines that the process variable needs to be reset.
  • the terminal device determines that a reset needs to be performed. At least one of a compression algorithm, a reconfiguration encryption decryption algorithm, and a reset process variable.
  • the terminal device determines that it is necessary to simultaneously perform a reset compression algorithm, a reconfiguration encryption decryption algorithm, and a reset process variable, resetting the compression algorithm, reconfiguring the encryption and decryption algorithm, and resetting
  • the process variable is executed in a non-sequential manner, that is, the terminal device may perform the reset compression algorithm first, or may perform the reconfiguration encryption and decryption algorithm first, and may also perform the reset process variable first, and the application embodiment does not limit this.
  • the sequence of execution is not performed.
  • the terminal device determines whether to re-establish the PDCP layer entity according to the indication information used by the network device to configure the PDCP layer entity, so that the terminal device needs to re-establish the PDCP layer entity.
  • the re-establishment operation is performed, the re-establishment operation is not performed when the PDCP layer entity does not need to be re-established, thereby avoiding the signaling overhead caused by performing the re-establishment operation when the PDCP layer entity is not required to be re-established.
  • the network device configures the indication information when some or all of the network nodes accessed by the terminal device change, thereby guiding the terminal device to determine whether to re-establish the PDCP layer entity.
  • FIG. 4 is a schematic block diagram of a terminal device 300 according to an embodiment of the present application. As shown in FIG. 4, the terminal device 300 includes:
  • the receiving unit 310 is configured to receive configuration information that is sent by the network device for mobility management of the terminal device, where the configuration information includes indication information, where the indication information is used to configure a packet data convergence protocol PDCP layer entity;
  • the processing unit 320 is configured to determine, according to the indication information, whether to re-establish the PDCP layer entity.
  • the indication information is key information
  • the processing unit 320 is specifically configured to:
  • the PDCP layer entity is re-established when it is determined that the key information of the current PDCP layer entity is changed.
  • the indication information is key information
  • the processing unit 320 is specifically configured to:
  • the PDCP layer entity is not re-established when it is determined that the key information of the current PDCP layer entity remains unchanged.
  • the receiving unit 310 receives the configuration information sent by the network device.
  • the processing unit 320 is further configured to: when the PDCP layer entity is re-established according to the indication information, determine that the compression algorithm needs to be reset.
  • the processing unit 320 is further configured to determine, when the PDCP layer entity is re-established according to the indication information, that the encryption and decryption algorithm needs to be reconfigured.
  • the processing unit 320 is further configured to determine that the process variable needs to be reset when the PDCP layer entity is re-established according to the indication information.
  • terminal device 300 may correspond to the terminal device in the method 200 of the present application, and the foregoing and other operations and/or functions of the respective units in the terminal device 300 respectively implement the method 200 shown in FIG.
  • the corresponding process of the terminal device is not described here for brevity.
  • FIG. 5 is a schematic block diagram of a device 400 for wireless communication provided by an embodiment of the present application.
  • the device 400 includes:
  • the memory 410 is configured to store a program, where the program includes a code
  • the transceiver 420 is configured to communicate with other devices;
  • the processor 430 is configured to execute program code in the memory 410.
  • the processor 430 can implement various operations performed by the terminal device in the method 200 in FIG. 3, and details are not described herein for brevity.
  • the device 400 may be a terminal device (for example, a mobile phone).
  • the transceiver 420 is configured to perform specific signal transceiving under the driving of the processor 430.
  • the processor 430 may be a central processing unit (CPU), and the processor 430 may also be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits. (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and more.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 410 can include read only memory and random access memory and provides instructions and data to the processor 430. A portion of the memory 410 may also include a non-volatile random access memory. For example, the memory 410 can also store information of the device type.
  • the transceiver 420 can be used to implement signal transmission and reception functions, such as frequency modulation and demodulation functions or upconversion and down conversion functions.
  • the device 400 for wireless communication can be a chip or chipset.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware processor, or may be performed by a combination of hardware and software modules in the 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, and the processor 430 reads the information in the memory and completes the steps of the above method in combination with the hardware thereof. To avoid repetition, it will not be described in detail here.
  • FIG. 6 is a schematic structural diagram of a system chip 500 according to an embodiment of the present application.
  • the system chip 500 of FIG. 6 includes an input interface 501, an output interface 502, a processor 503, and a memory 504 that can be connected by an internal communication connection line for executing code in the memory 504.
  • the processor 503 when the code is executed, the processor 503 implements a method performed by the terminal device in the method embodiment. For the sake of brevity, it will not be repeated here.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separate.
  • the components displayed for the unit may or may not be physical units, ie may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

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

Abstract

本申请实施例提供了一种无线通信的方法和终端设备，能够根据网络设备的配置信息灵活判断是否需要重新建立PDCP层实体，避免在不需要重新建立PDCP层实体时，执行重新建立操作，进而，减少信令开销。该方法包括：终端设备接收网络设备发送的用于对该终端设备进行移动性管理的配置信息，该配置信息包括指示信息，该指示信息用于配置分组数据汇聚协议PDCP层实体；终端设备根据该指示信息，确定是否重新建立该PDCP层实体。

Description

无线通信的方法和终端设备 技术领域
本申请涉及通信领域，并且更具体地，涉及一种无线通信的方法和终端设备。
背景技术
在长期演进(Long Term Evolution，LTE)通信系统中，在终端设备发生移动或者终端设备所接入的网络节点发生改变(例如，终端设备接入的网络节点从主节点1(Master Node，MN)变到MN2，从节点1(Slave Node，SN)变到SN2)时，分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层实体的物理位置发生变化，因此，需要重新建立PDCP层实体。
在5G新无线(New Radio，NR)通信系统中，可以将PDCP层实体布置云端，即不同的网络节点可以具有相同的PDCP层实体，因此，现有的LTE系统中的PDCP层实体重新建立的机制无法满足5G系统的需求。
发明内容
本申请实施例提供了一种无线通信的方法和终端设备，能够根据网络设备的配置信息灵活判断是否需要重新建立PDCP层实体，避免在不需要重新建立PDCP层实体时，执行重新建立操作，进而，减少信令开销。
第一方面，本申请实施例提供了一种无线通信的方法，包括：
终端设备接收网络设备发送的用于对该终端设备进行移动性管理的配置信息，该配置信息包括指示信息，该指示信息用于配置分组数据汇聚协议PDCP层实体；
该终端设备根据该指示信息，确定是否重新建立该PDCP层实体。
因此，在本申请实施例的无线通信的方法中，终端设备根据网络设备发送的用于配置PDCP层实体的指示信息，确定是否重新建立PDCP层实体，从而，终端设备在需要重新建立PDCP层实体时，执行重新建立操作，在不需要重新建立PDCP层实体时，不执行重新建立操作，进而，避免在不需要重新建立PDCP层实体时，因执行重新建立操作而造成的信令开销。
可选地，在第一方面的一种实现方式中，该指示信息为密钥信息；
该终端设备根据该指示信息，确定是否重新建立该PDCP层实体，包括：
在确定当前该PDCP层实体的密钥信息变化时，该终端设备重新建立该PDCP层实体。
因此，在本申请实施例的无线通信的方法中，网络设备可以通过密钥信息隐式指示重新建立PDCP层实体。
可选地，在第一方面的一种实现方式中，该指示信息为密钥信息；
该终端设备根据该指示信息，确定是否重新建立该PDCP层实体，包括：
在确定当前该PDCP层实体的密钥信息保持不变时，该终端设备不重新建立该PDCP层实体。
因此，在本申请实施例的无线通信的方法中，网络设备可以通过密钥信息隐式指示不重新建立PDCP层实体。
可选地，在第一方面的一种实现方式中，在该终端设备接入的部分或者全部网络节点改变时，该终端设备接收该网络设备发送的该配置信息。
因此，在本申请实施例的无线通信的方法中，网络设备在终端设备接入的部分或者全部网络节点改变时，配置指示信息，从而，指导终端设备确定是否重新建立PDCP层实体。
可选地，在第一方面的一种实现方式中，该方法还包括：
在该终端设备根据该指示信息重新建立该PDCP层实体时，该终端设备确定需要重置压缩算法。
可选地，在第一方面的一种实现方式中，该方法还包括：
在该终端设备根据该指示信息重新建立该PDCP层实体时，该终端设备确定需要重配置加密解密算法。
可选地，在第一方面的一种实现方式中，该方法还包括：
在该终端设备根据该指示信息重新建立该PDCP层实体时，该终端设备确定需要重置过程变量。
第二方面，本申请实施例提供了一种终端设备，可以执行第一方面或第一方面的任一可选的实现方式中的方法的模块或者单元。
第三方面，提供了一种终端设备，该终端设备包括处理器、存储器和通信接口。处理器与存储器和通信接口连接。存储器用于存储指令，处理器用于执行该指令，通信接口用于在处理器的控制下与其他网元进行通信。该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一 方面的任意可能的实现方式中的方法。
第四方面，提供了一种计算机存储介质，该计算机存储介质中存储有程序代码，该程序代码用于指示计算机执行上述第一方面或第一方面的任一种可能的实现方式中的方法的指令。
第五方面，提供了一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
图1示出了本申请实施例应用的无线通信系统。
图2示出了本申请实施例应用的双连接系统架构的示意图。
图3是根据本申请实施例的一种无线通信的方法的示意性流程图。
图4是根据本申请实施例的终端设备的示意性框图。
图5示出了本申请实施例提供的无线通信的设备的示意性框图。
图6是根据本申请实施例的系统芯片的示意性结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
本申请实施例的技术方案可以应用于双连接(Dual Connectivity，DC)通信系统，例如，LTE与5G NR双连接的通信系统，也可以应用于NR通信系统。
图1示出了本申请实施例应用的无线通信系统100。该无线通信系统100可以包括网络设备110。网络设备110可以是与终端设备通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备(例如UE)进行通信。可选地，该网络设备110可以是GSM系统或CDMA系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备、未来5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设 备等。
该无线通信系统100还包括位于网络设备110覆盖范围内的至少一个终端设备120。终端设备120可以是移动的或固定的。可选地，终端设备120可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、未来5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
图1示例性地示出了一个基站、一个核心网设备和两个终端设备，可选地，该无线通信系统100可以包括多个基站设备并且每个基站的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
可选地，该无线通信系统100还可以包括会话管理功能(Session Management Function，SMF)、统一数据管理(Unified Data Management，UDM)，认证服务器功能(Authentication Server Function，AUSF)等其他网络实体，本申请实施例对此不作限定。
图2示出了本申请实施例应用的双连接系统架构的示意图。如图2所示，终端设备可以同时连接两种不同的通信系统，图2是以终端设备同时连接LTE和NR为例进行说明。终端设备的MN节点为LTE通信节点，可以接入支持LTE通信的网络节点，也可以接入支持NR通信的网络节点，终端设备的SN节点为NR通信节点，可以接入支持LTE通信的网络节点，也可以接入支持NR通信的网络节点。
可选地，MN节点也可以为NR通信节点，可以接入支持LTE通信的网络节点，也可以接入支持NR通信的网络节点，终端设备的SN节点也可以为LTE通信节点，可以接入支持LTE通信的网络节点，也可以接入支持NR通信的网络节点。
如图2所示，终端设备可以在MN节点保持主小区(Master Cell Group，MCG)承载和MCG分流承载，在SN节点保持从小区(Slave Cell Group，SCG)承载和SCG分流承载。MCG承载连接MN PDCP 1、MN无线链路控 制(Radio Link Control，RLC)1和MN媒体接入控制(Media Access Control，MAC)，MCG分流承载连接MN PDCP 2、MN RLC 2和MN MAC，MCG分流承载还连接MN PDCP 2、SN RLC 3和SN MAC，MN PDCP 2与SN RLC3之间通过X2接口进行连接。SCG承载连接SN PDCP 1、SN RLC 1和SN MAC，SCG分流承载连接SN PDCP 2、SN RLC 2和SN MAC，SCG分流承载还连接SN PDCP 2、MN RLC 3和MN MAC，SN PDCP 2与MN RLC 3之间通过X2接口进行连接。
应理解，上述图2中，MN PDCP 1和MN PDCP 2仅仅只是为了方便描述而进行的区分，实际部署中并不一定如图2一样进行区分，MN RLC 1、MN RLC 2和MN RLC 3同理，SN PDCP 1和SN PDCP 2同理，SN RLC 1、SN RLC 2和SN RLC 3同理。
可选地，在本申请实施例中，终端设备接入的网络设备中可以实现中央单元(Central Unit，CU)和远端单元(Distributed Unit，DU)分离，CU和DU分离造成了RLC层/MAC层/物理(Physics，PHY)层的实体与PDCP层的实体分开部署，即对于RLC层/MAC层/PHY层的实体，不同的网络节点有不同的实体，而对于PDCP层的实体可以是不同的网络节点具有相同的实体，这一PDCP层的实体部署在了云端(靠近服务器的一侧)。当终端设备所接入的MN和/或SN发生变化(例如，从MN1变到MN2，从SN1变到SN2)时，PDCP层的实体所处的物理位置不会发生变化，不需要重新建立PDCP层的实体，RLC层/MAC层/PHY层的实体所处的物理位置会发生变化，需要重新建立RLC层/MAC层/PHY层的实体。
本申请实施例提供的无线通信的方法，可以应用于终端设备，该终端设备包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(Central Processing Unit，CPU)、内存管理单元(Memory Management Unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(Process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。
此外，本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可 读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(Compact Disc，CD)、数字通用盘(Digital Versatile Disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(Erasable Programmable Read-Only Memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，能够存储、包含和/或承载指令和/或数据的各种介质。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
图3是根据本申请实施例的一种无线通信的方法200的示意性流程图。如图3所示，该方法200可以由终端设备执行，该终端设备可以是如图1中所示的终端设备，该终端设备可以应用于如图2所示的双连接系统架构，该方法200中的网络设备可以是如图1所示的网络设备，该网络设备可以实现CU和DU分离，该网络设备可以与如图2所示的具有双连接系统架构的终端设备进行通信。该方法200包括以下内容。
210，终端设备接收网络设备发送的用于对该终端设备进行移动性管理的配置信息，该配置信息包括指示信息，该指示信息用于配置PDCP层实体。
可选地，该网络设备可以预先向该终端设备发送该配置信息，也可以在该终端设备所处的位置发生移动时向该终端设备发送该配置信息。
可选地，该网络设备可以显式指示该终端设备是否重新建立该PDPC层实体。可选地，该指示信息可以直接指示终端设备是否重新建立该PDPC层实体。例如，该指示信息可以是标识位，当该标识位取值为0时，指示终端设备重新建立该PDCP层实体，当该标识位取值为1时，指示终端设备不重新建立该PDCP层实体。
可选地，该网络设备可以隐式指示该终端设备是否重新建立该PDPC层实体。
可选地，该指示信息为密钥信息，在确定当前该PDCP层实体的密钥信 息变化时，该终端设备重新建立该PDCP层实体；在确定当前该PDCP层实体的密钥信息保持不变时，该终端设备不重新建立该PDCP层实体。
应理解，每个PDCP层实体都配置有独有的密钥信息。
可选地，在该终端设备接入的部分或者全部网络节点改变时，该终端设备接收该网络设备发送的该配置信息。
可选地，该网络设备可以是改变之后的网络节点所在的网络设备，即，重新接入的网络节点所在的网络设备。
例如，在终端设备接入的SN节点发生改变(从SN 1切换至SN 2)时，终端设备接收该网络设备发送的该配置信息，以及根据该配置信息中的指示信息确定是否重新建立该PDCP层实体。
若SN 2对应的SCG承载(bearer)的PDCP层实体部署在云端，则PDCP层实体的物理位置没有改变，此时，该终端设备不重新建立该PDCP层实体。
若SN 2对应的SCG承载的PDCP层实体并非部署在云端，则PDCP层实体的物理位置发生了改变，此时，该终端设备需要重新建立该PDCP层实体。
又例如，在终端设备接入的SN发生改变(从SN 1切换至SN 2)时，终端设备接收该网络设备发送的该配置信息，以及根据该配置信息中的指示信息确定是否重新建立该PDCP层实体。
若SN 2对应的SCG承载的PDCP层实体部署在MN侧，使用的密钥为针对MN PDCP的密钥，此时，虽然SN发生改变，但其PDCP层实体的物理位置没有改变，此时，该终端设备不重新建立该PDCP层实体。
可选地，也可以是该终端设备接入的全部网络节点发生改变，此时，可以通过确定密钥信息是否改变来确定是否重新建立该PDCP层实体。
220，该终端设备根据该指示信息，确定是否重新建立该PDCP层实体。
可选地，在该终端设备根据该指示信息重新建立该PDCP层实体时，该终端设备确定需要重置压缩算法。
可选地，在该终端设备根据该指示信息重新建立该PDCP层实体时，该终端设备确定需要重配置加密解密算法。
可选地，在该终端设备根据该指示信息重新建立该PDCP层实体时，该终端设备确定需要重置过程变量。
可选地，在重新建立该PDCP层实体时，该终端设备确定需要执行重置 压缩算法、重配置加密解密算法、重置过程变量中的至少一种操作。
可选地，在重新建立该PDCP层实体，以及该终端设备确定需要同时执行重置压缩算法、重配置加密解密算法和重置过程变量时，重置压缩算法、重配置加密解密算法和重置过程变量在执行时无先后顺序之分，即终端设备可以先执行重置压缩算法，也可以先执行重配置加密解密算法，还可以先执行重置过程变量，并申请实施例对此不作限定。
可选地，在重新建立该PDCP层实体，以及该终端设备确定需要同时执行重置压缩算法、重配置加密解密算法、重置过程变量中的任意两种操作时，也不分执行的先后顺序。
因此，在本申请实施例的无线通信的方法中，终端设备根据网络设备发送的用于配置PDCP层实体的指示信息，确定是否重新建立PDCP层实体，从而，终端设备在需要重新建立PDCP层实体时，执行重新建立操作，在不需要重新建立PDCP层实体时，不执行重新建立操作，进而，避免在不需要重新建立PDCP层实体时，因执行重新建立操作而造成的信令开销。
进一步地，网络设备在终端设备接入的部分或者全部网络节点改变时，配置指示信息，从而，指导终端设备确定是否重新建立PDCP层实体。
图4是根据本申请实施例的终端设备300的示意性框图。如图4所示，该终端设备300包括：
接收单元310，用于接收网络设备发送的用于对该终端设备进行移动性管理的配置信息，该配置信息包括指示信息，该指示信息用于配置分组数据汇聚协议PDCP层实体；
处理单元320，用于根据该指示信息，确定是否重新建立该PDCP层实体。
可选地，该指示信息为密钥信息；
该处理单元320具体用于：
在确定当前该PDCP层实体的密钥信息变化时，重新建立该PDCP层实体。
可选地，该指示信息为密钥信息；
该处理单元320具体用于：
在确定当前该PDCP层实体的密钥信息保持不变时，不重新建立该PDCP层实体。
可选地，在该终端设备接入的部分或者全部网络节点改变时，该接收单元310接收该网络设备发送的该配置信息。
可选地，该处理单元320，还用于在根据该指示信息重新建立该PDCP层实体时，确定需要重置压缩算法。
可选地，该处理单元320，还用于在根据该指示信息重新建立该PDCP层实体时，确定需要重配置加密解密算法。
可选地，该处理单元320，还用于在根据该指示信息重新建立该PDCP层实体时，确定需要重置过程变量。
应理解，根据本申请实施例的终端设备300可对应于本申请方法200中的终端设备，并且终端设备300中的各个单元的上述和其它操作和/或功能分别为了实现图3所示方法200中终端设备的相应流程，为了简洁，在此不再赘述。
图5示出了本申请实施例提供的无线通信的设备400的示意性框图，该设备400包括：
存储器410，用于存储程序，该程序包括代码；
收发器420，用于和其他设备进行通信；
处理器430，用于执行存储器410中的程序代码。
可选地，当该代码被执行时，该处理器430可以实现图3中的方法200中终端设备执行的各个操作，为了简洁，在此不再赘述。此时，该设备400可以为终端设备(例如，手机)。收发器420用于在处理器430的驱动下执行具体的信号收发。
应理解，在本申请实施例中，该处理器430可以是中央处理单元(Central Processing Unit，CPU)，该处理器430还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器410可以包括只读存储器和随机存取存储器，并向处理器430提供指令和数据。存储器410的一部分还可以包括非易失性随机存取存储器。例如，存储器410还可以存储设备类型的信息。
收发器420可以是用于实现信号发送和接收功能，例如频率调制和解调功能或叫上变频和下变频功能。
在实现过程中，上述方法的至少一个步骤可以通过处理器430中的硬件的集成逻辑电路完成，或该集成逻辑电路可在软件形式的指令驱动下完成该至少一个步骤。因此，无线通信的设备400可以是个芯片或者芯片组。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器430读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
图6是根据本申请实施例的系统芯片500的示意性结构图。图6的系统芯片500包括输入接口501、输出接口502、处理器503以及存储器504之间可以通过内部通信连接线路相连，该处理器503用于执行该存储器504中的代码。
可选地，当该代码被执行时，该处理器503实现方法实施例中由终端设备执行的方法。为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作 为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (14)

  1. 一种无线通信的方法，其特征在于，包括：
    终端设备接收网络设备发送的用于对所述终端设备进行移动性管理的配置信息，所述配置信息包括指示信息，所述指示信息用于配置分组数据汇聚协议PDCP层实体；
    所述终端设备根据所述指示信息，确定是否重新建立所述PDCP层实体。
  2. 根据权利要求1所述的方法，其特征在于，所述指示信息为密钥信息；
    所述终端设备根据所述指示信息，确定是否重新建立所述PDCP层实体，包括：
    在确定当前所述PDCP层实体的密钥信息变化时，所述终端设备重新建立所述PDCP层实体。
  3. 根据权利要求1所述的方法，其特征在于，所述指示信息为密钥信息；
    所述终端设备根据所述指示信息，确定是否重新建立所述PDCP层实体，包括：
    在确定当前所述PDCP层实体的密钥信息保持不变时，所述终端设备不重新建立所述PDCP层实体。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，在所述终端设备接入的部分或者全部网络节点改变时，所述终端设备接收所述网络设备发送的所述配置信息。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    在所述终端设备根据所述指示信息重新建立所述PDCP层实体时，所述终端设备确定需要重置压缩算法。
  6. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    在所述终端设备根据所述指示信息重新建立所述PDCP层实体时，所述终端设备确定需要重配置加密解密算法。
  7. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    在所述终端设备根据所述指示信息重新建立所述PDCP层实体时，所述终端设备确定需要重置过程变量。
  8. 一种终端设备，其特征在于，包括：
    接收单元，用于接收网络设备发送的用于对所述终端设备进行移动性管理的配置信息，所述配置信息包括指示信息，所述指示信息用于配置分组数据汇聚协议PDCP层实体；
    处理单元，用于根据所述指示信息，确定是否重新建立所述PDCP层实体。
  9. 根据权利要求8所述的终端设备，其特征在于，所述指示信息为密钥信息；
    所述处理单元具体用于：
    在确定当前所述PDCP层实体的密钥信息变化时，重新建立所述PDCP层实体。
  10. 根据权利要求8所述的终端设备，其特征在于，所述指示信息为密钥信息；
    所述处理单元具体用于：
    在确定当前所述PDCP层实体的密钥信息保持不变时，不重新建立所述PDCP层实体。
  11. 根据权利要求8至10中任一项所述的终端设备，其特征在于，在所述终端设备接入的部分或者全部网络节点改变时，所述接收单元接收所述网络设备发送的所述配置信息。
  12. 根据权利要求8至11中任一项所述的终端设备，其特征在于，所述处理单元，还用于在根据所述指示信息重新建立所述PDCP层实体时，确定需要重置压缩算法。
  13. 根据权利要求8至11中任一项所述的终端设备，其特征在于，所述处理单元，还用于在根据所述指示信息重新建立所述PDCP层实体时，确定需要重配置加密解密算法。
  14. 根据权利要求8至11中任一项所述的终端设备，其特征在于，所述处理单元，还用于在根据所述指示信息重新建立所述PDCP层实体时，确定需要重置过程变量。
PCT/CN2017/103919 2017-09-28 2017-09-28 无线通信的方法和终端设备 WO2019061137A1 (zh)

Priority Applications (17)

Application Number Priority Date Filing Date Title
EP21212114.9A EP3982695A1 (en) 2017-09-28 2017-09-28 Wireless communication method and terminal device
CN202010071281.5A CN111447610B (zh) 2017-09-28 2017-09-28 无线通信的方法和终端设备
JP2020514546A JP7024067B2 (ja) 2017-09-28 2017-09-28 無線通信方法及び端末デバイス
MX2020002997A MX2020002997A (es) 2017-09-28 2017-09-28 Metodo y dispositivo terminal de comunicacion inalambrica.
CN201780092493.8A CN110786074A (zh) 2017-09-28 2017-09-28 无线通信的方法和终端设备
BR112020004794-5A BR112020004794A2 (pt) 2017-09-28 2017-09-28 método de comunicação sem fio, dispositivo terminal e sistema de computador
CA3075835A CA3075835C (en) 2017-09-28 2017-09-28 Wireless communication method and terminal device
KR1020207006953A KR102375440B1 (ko) 2017-09-28 2017-09-28 무선 통신 방법 및 단말기 디바이스
AU2017433998A AU2017433998B2 (en) 2017-09-28 2017-09-28 Wireless communication method and terminal device
ES17926720T ES2907789T3 (es) 2017-09-28 2017-09-28 Método de comunicación inalámbrica y dispositivo terminal
RU2020112505A RU2748163C1 (ru) 2017-09-28 2017-09-28 Способ беспроводной связи и терминальное устройство
EP17926720.8A EP3661312B1 (en) 2017-09-28 2017-09-28 Wireless communication method and terminal device
PCT/CN2017/103919 WO2019061137A1 (zh) 2017-09-28 2017-09-28 无线通信的方法和终端设备
SG11202002452SA SG11202002452SA (en) 2017-09-28 2017-09-28 Wireless communication method and terminal device
TW107133979A TW201916656A (zh) 2017-09-28 2018-09-27 無線通訊的方法和終端設備
US16/752,377 US11483695B2 (en) 2017-09-28 2020-01-24 Wireless communication method and terminal device for new radio communication system
US17/949,954 US11889582B2 (en) 2017-09-28 2022-09-21 Terminal device to determine whether to re-establish a PDCP layer entity based on indication received from a network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/103919 WO2019061137A1 (zh) 2017-09-28 2017-09-28 无线通信的方法和终端设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/752,377 Continuation US11483695B2 (en) 2017-09-28 2020-01-24 Wireless communication method and terminal device for new radio communication system

Publications (1)

Publication Number Publication Date
WO2019061137A1 true WO2019061137A1 (zh) 2019-04-04

Family

ID=65900375

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/103919 WO2019061137A1 (zh) 2017-09-28 2017-09-28 无线通信的方法和终端设备

Country Status (14)

Country Link
US (2) US11483695B2 (zh)
EP (2) EP3661312B1 (zh)
JP (1) JP7024067B2 (zh)
KR (1) KR102375440B1 (zh)
CN (2) CN110786074A (zh)
AU (1) AU2017433998B2 (zh)
BR (1) BR112020004794A2 (zh)
CA (1) CA3075835C (zh)
ES (1) ES2907789T3 (zh)
MX (1) MX2020002997A (zh)
RU (1) RU2748163C1 (zh)
SG (1) SG11202002452SA (zh)
TW (1) TW201916656A (zh)
WO (1) WO2019061137A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116057871A (zh) * 2020-10-27 2023-05-02 Oppo广东移动通信有限公司 一种无线通信方法、终端设备及网络设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102375440B1 (ko) 2017-09-28 2022-03-17 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 무선 통신 방법 및 단말기 디바이스
CN111756485B (zh) * 2019-03-27 2022-09-02 华为技术有限公司 一种控制定时器、数据包处理方法及设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102026324A (zh) * 2009-09-18 2011-04-20 大唐移动通信设备有限公司 一种聚合小区的重配置方法、设备和系统
CN102972088A (zh) * 2011-08-02 2013-03-13 华为技术有限公司 基于分层云计算的移动蜂窝网络
CN103533586A (zh) * 2012-07-03 2014-01-22 电信科学技术研究院 切换过程中的信令交互及层重建的方法和设备
US20140301188A1 (en) * 2013-04-04 2014-10-09 Nokia Siemens Networks Oy Delivery of protocol data units
CN104519486A (zh) * 2013-09-29 2015-04-15 中国电信股份有限公司 用于异构网中无线侧密钥更新的方法和系统

Family Cites Families (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070288556A1 (en) * 2002-05-17 2007-12-13 Anton Richard N System and Method for Encoding and Decoding Data Files
WO2006115212A1 (ja) * 2005-04-21 2006-11-02 Matsushita Electric Industrial Co., Ltd. アルゴリズム更新システム
US20070242703A1 (en) * 2006-04-12 2007-10-18 Telefonaktiebolaget Lm Ericsson (Publ) Binding/combining of plural telecommunications functions
KR100938090B1 (ko) 2006-10-19 2010-01-21 삼성전자주식회사 이동통신 시스템에서 핸드오버 수행 방법 및 장치
US20080119188A1 (en) * 2006-11-21 2008-05-22 Innovative Sonic Limited Method and related apparatus for ciphering algorithm change in a wireless communcations system
KR101392697B1 (ko) * 2007-08-10 2014-05-19 엘지전자 주식회사 이동통신 시스템에서의 보안 오류 검출방법 및 장치
TWI470982B (zh) * 2007-09-28 2015-01-21 Interdigital Patent Holdings 分組數據匯聚協議中控制協議數據單元方法及裝置
WO2009088710A1 (en) * 2008-01-04 2009-07-16 Interdigital Patent Holdings, Inc. Method and apparatus of performing packet data convergence protocol re-establishment
DE602009000944D1 (de) * 2008-04-11 2011-05-05 Innovative Sonic Ltd Verfahren und Vorrichtung zur Handhabung des Weiterleitungsverfahrens
US8396037B2 (en) 2008-06-23 2013-03-12 Htc Corporation Method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system and related apparatus thereof
CN101925121B (zh) 2009-06-10 2014-03-19 中兴通讯股份有限公司 一种分组数据汇聚协议层重建的方法和装置
CN102158303A (zh) * 2010-02-11 2011-08-17 中兴通讯股份有限公司 一种上行链路的重建立方法及用户设备
ES2618934T3 (es) * 2012-07-24 2017-06-22 Huawei Technologies Co., Ltd Procedimiento, aparato y sistema de comprobación y reconfiguración
BR112015010763B1 (pt) * 2012-11-13 2022-04-26 Huawei Technologies Co., Ltd Método e aparelho de transmissão de dados
US10075881B2 (en) * 2013-04-02 2018-09-11 Lg Electronics Inc. Method for performing a cell change procedure in a wireless communication system and a device therefor
CN104247550B (zh) 2013-04-03 2019-03-26 华为技术有限公司 一种数据的传输方法、通信设备和通信系统
CN105230077B (zh) 2013-04-12 2020-02-21 诺基亚通信公司 用于pdcp操作的装置、方法以及用户设备
US9015429B2 (en) * 2013-04-18 2015-04-21 Xerox Corporation Method and apparatus for an efficient hardware implementation of dictionary based lossless compression
US9538371B2 (en) * 2013-07-10 2017-01-03 Htc Corporation Method of handling data transmission and reception in device to device communication in wireless communication systems
EP3668044B1 (en) * 2014-01-28 2021-12-15 Huawei Technologies Co., Ltd. Security key change method, base station, and user equipment
US9713044B2 (en) * 2014-01-30 2017-07-18 Sharp Kabushiki Kaisha Systems and methods for dual-connectivity operation
CN104935413B (zh) 2014-03-19 2019-12-27 夏普株式会社 分组数据汇聚协议pdcp实体及其执行的方法
EP3120604B1 (en) * 2014-03-21 2019-06-26 Samsung Electronics Co., Ltd. Method and apparatus for transmitting/receiving signal in mobile communication system supporting a plurality of carriers
CN104955064B (zh) * 2014-03-28 2019-01-11 上海诺基亚贝尔股份有限公司 一种在双连接系统中处理用户设备端rlc/pdcp实体的方法与设备
JP2017514367A (ja) 2014-03-28 2017-06-01 富士通株式会社 ベアラ管理装置、方法及び通信システム
JP6422514B2 (ja) * 2014-08-07 2018-11-14 エルジー エレクトロニクス インコーポレイティド 端末が二重連結システムでｐｄｃｐ ｐｄｕを処理する方法及びその装置
WO2016021820A1 (en) 2014-08-08 2016-02-11 Lg Electronics Inc. Method for processing a packet data convergence protocol re-ordering function at a user equipment in a dual connectivity system and device therefor
WO2016068655A1 (en) * 2014-10-30 2016-05-06 Samsung Electronics Co., Ltd. Method of performing device to device communication between user equipments
US10869344B2 (en) * 2015-03-19 2020-12-15 Acer Incorporated Method of radio bearer transmission in dual connectivity
WO2016153130A1 (ko) * 2015-03-23 2016-09-29 엘지전자(주) 무선 통신 시스템에서 단말의 데이터 송수신 방법 및 장치
CN106304398B (zh) * 2015-05-15 2021-08-27 夏普株式会社 用于重配置数据承载的方法和用户设备
CN114885375A (zh) 2016-08-09 2022-08-09 三星电子株式会社 无线通信系统中管理用户平面操作的方法和装置
US9986069B2 (en) * 2016-09-28 2018-05-29 Intel Corporation Devices and methods to compress sensor data
EP4358623A1 (en) * 2016-11-17 2024-04-24 Samsung Electronics Co., Ltd. Method and apparatus for activating/deactivating cells with scalable transmission time intervals in wireless communication system using cell aggregation
CN108243469B (zh) * 2016-12-23 2021-07-16 夏普株式会社 用户移动性方法和设备
US10664413B2 (en) * 2017-01-27 2020-05-26 Lear Corporation Hardware security for an electronic control unit
WO2018144233A1 (en) * 2017-02-03 2018-08-09 Intel Corporation Concatenation of service data units above a packet data convergence protocol layer
CN108632810B (zh) * 2017-03-24 2021-08-20 华为技术有限公司 控制终端设备状态的方法、终端设备和网络设备
US11219077B2 (en) * 2017-05-05 2022-01-04 Samsung Electronics Co., Ltd. Method and apparatus for coordination of RRC configurations between interworking nodes in dual connectivity
GB2563584B (en) * 2017-06-16 2022-05-04 Tcl Communication Ltd Bearer control
KR102376115B1 (ko) * 2017-08-10 2022-03-18 삼성전자 주식회사 차세대 이동 통신 시스템에서 pdcp 버전 변경에 따른 재설정 방법 및 장치
JP6845263B2 (ja) * 2017-08-10 2021-03-17 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおけるＵＭ ＲＬＣエンティティに関連したＰＤＣＰエンティティの再構成（ｒｅ−ｅｓｔａｂｌｉｓｈｍｅｎｔ）のための方法及びその装置
EP3659391B1 (en) * 2017-08-11 2024-05-01 Samsung Electronics Co., Ltd. Method for performing bearer type change of a plurality of bearers configured for user equipment
KR102375440B1 (ko) 2017-09-28 2022-03-17 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 무선 통신 방법 및 단말기 디바이스

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102026324A (zh) * 2009-09-18 2011-04-20 大唐移动通信设备有限公司 一种聚合小区的重配置方法、设备和系统
CN102972088A (zh) * 2011-08-02 2013-03-13 华为技术有限公司 基于分层云计算的移动蜂窝网络
CN103533586A (zh) * 2012-07-03 2014-01-22 电信科学技术研究院 切换过程中的信令交互及层重建的方法和设备
US20140301188A1 (en) * 2013-04-04 2014-10-09 Nokia Siemens Networks Oy Delivery of protocol data units
CN104519486A (zh) * 2013-09-29 2015-04-15 中国电信股份有限公司 用于异构网中无线侧密钥更新的方法和系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116057871A (zh) * 2020-10-27 2023-05-02 Oppo广东移动通信有限公司 一种无线通信方法、终端设备及网络设备

Also Published As

Publication number Publication date
EP3661312A4 (en) 2020-08-05
EP3661312A1 (en) 2020-06-03
AU2017433998B2 (en) 2023-06-08
US11483695B2 (en) 2022-10-25
EP3661312B1 (en) 2022-01-19
CN111447610B (zh) 2021-08-31
US20230015741A1 (en) 2023-01-19
CN110786074A (zh) 2020-02-11
KR102375440B1 (ko) 2022-03-17
CA3075835C (en) 2023-08-15
BR112020004794A2 (pt) 2020-09-24
ES2907789T3 (es) 2022-04-26
JP7024067B2 (ja) 2022-02-22
TW201916656A (zh) 2019-04-16
EP3982695A1 (en) 2022-04-13
MX2020002997A (es) 2020-07-22
US20200162886A1 (en) 2020-05-21
SG11202002452SA (en) 2020-04-29
AU2017433998A1 (en) 2020-04-02
RU2748163C1 (ru) 2021-05-20
US11889582B2 (en) 2024-01-30
JP2021502010A (ja) 2021-01-21
CA3075835A1 (en) 2019-04-04
KR20200055712A (ko) 2020-05-21
CN111447610A (zh) 2020-07-24

Similar Documents

Publication Publication Date Title
US11889582B2 (en) Terminal device to determine whether to re-establish a PDCP layer entity based on indication received from a network device
WO2020200034A1 (zh) 一种网络接入的方法和装置
JP7019793B2 (ja) 無線通信方法、ネットワーク機器及び端末装置
CN108476444A (zh) 获取终端无线能力信息的方法、核心网实体、基站和终端
AU2017401979B2 (en) Data transmission method and device
WO2019183848A1 (zh) 监听pdcch的方法、终端设备和网络设备
US11317453B2 (en) Device to device communication method for reducing mutual interference between different types of terminal devices, terminal device and network device
TW201844038A (zh) 傳輸信號的方法、網絡設備和終端設備
CN110912661A (zh) 一种能力信息接收、发送方法及装置
JP2021510021A (ja) 無線通信方法、端末デバイス及びネットワークデバイス
BR112019026433A2 (pt) método de comunicação de rádio, dispositivo de terminal e dispositivo de rede
WO2021017611A1 (zh) 数据传输方法和装置
WO2019140664A1 (zh) 信令无线承载的配置方法、终端设备和网络设备
WO2020088467A1 (zh) 一种终端通信能力发送、接收方法及装置
WO2019090770A1 (zh) 切换过程中确定核心网类型的方法、终端设备、接入网设备和核心网设备
WO2019024108A1 (zh) 通信方法、网络设备和终端设备
TWI771368B (zh) 通信方法、終端設備和接入網設備
WO2020142884A1 (zh) 切换传输路径的方法及装置
TWI743184B (zh) 傳輸資料的方法、存取網路裝置和終端裝置
WO2019153350A1 (zh) 一种通信方法、通信设备及计算机程序存储介质
WO2024077446A1 (zh) 无线通信的方法、终端设备和网络设备
WO2019047163A1 (zh) 配置分组数据汇聚协议pdcp的方法、终端设备和网络设备

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017926720

Country of ref document: EP

Effective date: 20200227

ENP Entry into the national phase

Ref document number: 2020514546

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 3075835

Country of ref document: CA

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020004794

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017433998

Country of ref document: AU

Date of ref document: 20170928

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 112020004794

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200310