WO2021203439A1 - Procédé de transmission de données, dispositif terminal et dispositif réseau - Google Patents

Procédé de transmission de données, dispositif terminal et dispositif réseau Download PDF

Info

Publication number
WO2021203439A1
WO2021203439A1 PCT/CN2020/084308 CN2020084308W WO2021203439A1 WO 2021203439 A1 WO2021203439 A1 WO 2021203439A1 CN 2020084308 W CN2020084308 W CN 2020084308W WO 2021203439 A1 WO2021203439 A1 WO 2021203439A1
Authority
WO
WIPO (PCT)
Prior art keywords
key
ncc
terminal device
data
valid
Prior art date
Application number
PCT/CN2020/084308
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 CN202080093637.3A priority Critical patent/CN115004739A/zh
Priority to PCT/CN2020/084308 priority patent/WO2021203439A1/fr
Publication of WO2021203439A1 publication Critical patent/WO2021203439A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • 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

  • This application relates to the field of communications, and more specifically, to data transmission methods, terminal devices, and network devices.
  • the radio resource control (RRC, Radio Resource Control) state of terminal equipment is divided into three types, namely: RRC_IDLE (RRC idle state), RRC_INACTIVE (RRC inactive state) State), RRC_CONNECTED (RRC connected state).
  • RRC_IDLE RRC idle state
  • RRC_INACTIVE RRC inactive state
  • RRC_CONNECTED RRC connected state
  • the RRC_INACTIVE state is a new state introduced by the 5G system from the perspective of energy saving.
  • the radio bearer and all radio resources will be released, but the UE side and the base station side retain the UE access context to quickly restore the RRC connection.
  • the UE with infrequent data transmission is kept in the RRC_INACTIVE state.
  • the embodiments of the present application provide a data transmission method, a terminal device, and a communication device, which can realize the transmission of small data in an inactive state by the terminal device.
  • the embodiment of the application proposes a data transmission method, which is applied to a terminal device, and includes:
  • the key When the key is valid, the key is used to encrypt the data, and the pre-configured resource is used to send the encrypted data.
  • the embodiment of the application proposes a data transmission method, which is applied to a network device, and includes:
  • An embodiment of the present application proposes a terminal device, including:
  • the transmission module is used to encrypt data with the key when the key is valid, and use pre-configured resources to send the encrypted data.
  • An embodiment of the application proposes a network device, including:
  • the configuration module is used to send a pre-configured resource and/or a next hop link count NCC for generating a key, where the pre-configured resource and the key are used for the terminal device to send data.
  • the embodiment of the present application proposes a terminal device, including: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any of the above-mentioned data transmission methods. The method described.
  • the embodiment of the application proposes a network device, including: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any of the above data transmission methods. The method described.
  • An embodiment of the present application proposes a chip, including a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the method described in any of the above data transmission methods.
  • the embodiment of the present application proposes a computer-readable storage medium for storing a computer program, and the computer program enables a computer to execute the method described in any of the above-mentioned data transmission methods.
  • the embodiment of the present application proposes a computer program product, including computer program instructions, which cause a computer to execute the method described in any of the above data transmission methods.
  • An embodiment of the present application proposes a computer program that enables a computer to execute the method described in any of the above data transmission methods.
  • the terminal device when the key is valid, uses the key to encrypt data, and uses the pre-configured resource to send the encrypted data, so as to realize the transmission of small data in the inactive state.
  • Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
  • Fig. 2 is an implementation flowchart of a data transmission method 200 according to an embodiment of the present application.
  • FIG. 3 is an implementation flowchart of a data transmission method 300 according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram 1 of an implementation manner of Embodiment 1 of the present application.
  • FIG. 5 is a schematic diagram of a second implementation manner of Embodiment 1 of the present application.
  • FIG. 6 is a schematic diagram of small data transmission 600 based on pre-configured resources according to Embodiment 1 of the present application.
  • FIG. 7 is a schematic diagram 1 of a manner of obtaining an updated NCC in Embodiment 2 of the present application.
  • FIG. 8 is a schematic diagram of the second embodiment of the second embodiment of the present application for obtaining an updated NCC.
  • FIG. 9 is an implementation flowchart of a data transmission method 900 according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a terminal device 1000 according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a terminal device 1100 according to an embodiment of the present application.
  • Fig. 12 is a schematic structural diagram of a network device 1200 according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a network device 1300 according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a communication device 1400 according to an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a chip 1500 according to an embodiment of the present application.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • UMTS universal mobile telecommunication system
  • WLAN wireless Local Area Networks
  • 5G next-generation communications
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC machine type communication
  • V2V vehicle to vehicle
  • the communication system in the embodiments of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, can also be applied to a dual connectivity (DC) scenario, and can also be applied to a standalone (SA) deployment.
  • CA Carrier Aggregation
  • DC dual connectivity
  • SA standalone
  • the embodiment of the application does not limit the applied frequency spectrum.
  • the embodiments of this application can be applied to licensed spectrum or unlicensed spectrum.
  • the embodiments of this application describe various embodiments in combination with network equipment and terminal equipment.
  • the terminal equipment may also be referred to as User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, and remote. Station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • UE User Equipment
  • access terminal subscriber unit, subscriber station, mobile station, mobile station, and remote.
  • Station remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • the terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, and personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, and next-generation communication systems, such as terminal devices in the NR network or Terminal equipment in the public land mobile network (PLMN) network that will evolve in the future.
  • STAION, ST station
  • WLAN Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for using wearable technology to intelligently design everyday wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones.
  • a network device can be a device used to communicate with mobile devices.
  • the network device can be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, or a device in WCDMA.
  • a base station (NodeB, NB) can also be an Evolutional Node B (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in the NR network Or network equipment in the PLMN network that will evolve in the future.
  • AP access point
  • BTS base station
  • gNB network device
  • the network equipment provides services for the cell
  • the terminal equipment communicates with the network equipment through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell
  • the cell may be a network equipment (for example, The cell corresponding to the base station.
  • the cell can belong to a macro base station or a base station corresponding to a small cell.
  • the small cell here can include: Metro cell, Micro cell, Pico Cells, Femto cells, etc. These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.
  • Figure 1 exemplarily shows one network device 110 and two terminal devices 120.
  • the wireless communication system 100 may include multiple network devices 110, and the coverage of each network device 110 may include other numbers.
  • the terminal device 120 is not limited in this embodiment of the application.
  • the embodiments of the present application can be applied to one terminal device 120 and one network device 110, and can also be applied to one terminal device 120 and another terminal device 120.
  • the wireless communication system 100 may also include other network entities such as mobility management entities (Mobility Management Entity, MME), access and mobility management functions (Access and Mobility Management Function, AMF), etc. This is not limited.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • FIG. 2 is an implementation flowchart of a data transmission method 200 according to an embodiment of the present application, including the following steps:
  • the aforementioned data is small data, such as data with a small amount of data sent by the UE in the RRC_INACTIVE state and/or data with a low transmission frequency.
  • the data sent by the terminal device may be small data.
  • the prerequisites of the above method include at least one of the following:
  • the cell where the UE is currently located supports small data transmission based on preconfigured resources (PUR, Preconfigured Uplink Resource);
  • PUR Preconfigured Uplink Resource
  • the UE has the ability to transmit small data in the RRC_INACTIVE state.
  • the step S210 further includes:
  • S320 The terminal device generates the key based on the next hop link count (NCC, NextHopChainingCount).
  • the NCC can be carried in an RRC release message (RRCRelease) to generate a new key.
  • RRCRelease RRC release message
  • the method further includes:
  • RRC release message includes at least one of the following:
  • the terminal device sends a data transmission resource request in the connected state (RRC_CONNECTED state), and after receiving the RRC release message, that is, after the above step S310, the terminal device switches to the inactive state (RRC_INACTIVE state).
  • the terminal device can obtain the updated NCC, use the updated NCC to generate the updated key, and then use the updated key pair
  • the data is encrypted.
  • the above method further includes:
  • S350 Use the updated key to encrypt the data, and use the pre-configured resource to send the encrypted data.
  • the terminal device can obtain the updated NCC when the key is invalid; or the network device updates the NCC through the downlink feedback of a certain small data transmission, and the terminal device obtains the updated NCC from the response to the small data.
  • the terminal device may obtain the updated NCC when the key is invalid, and the obtaining method includes at least one of the following:
  • the terminal device triggers an RRC Resume (RRC Resume) process when/after the key becomes invalid, and receives the updated NCC.
  • the terminal device may send an RRC recovery request (RRCResumeRequest) message to trigger the RRC recovery process; and receive an RRC release (RRCRelease) message containing the updated NCC sent by the network device.
  • RRC Resume RRC Resume
  • RRCResumeRequest RRC recovery request
  • RRC release RRCRelease
  • the terminal device when/after the key becomes invalid, when the terminal device needs to send data or is paged, it triggers the RRC recovery process and receives the updated NCC.
  • the terminal device may send an RRCResumeRequest message to trigger the RRC recovery process; and receive the RRCelease message containing the updated NCC sent by the network device.
  • the terminal device when/after the key becomes invalid, when the terminal device needs to send data and meets the data transmission requirements based on random access, it triggers the data transmission process based on random access and receives the updated NCC.
  • the terminal device sends the preamble of the random access procedure, and after receiving the uplink resource configured on the network side, uses the uplink resource to send the RRCResumeRequest message; and receives the RRCRelease containing the updated NCC sent by the network device information.
  • the terminal device when/after the key becomes invalid, the terminal device multiplexes the RRC recovery request message or the MAC CE indicating the update of the NCC in the data transmitted by the pre-configured resource, and receives the updated NCC.
  • the terminal device multiplexes the RRCResumeRequest message in the small data transmission of the pre-configured resource; and receives the RRCRelease message containing the updated NCC sent by the network device.
  • the aforementioned RRCRelease message may further include the effective duration and/or the number of effective transmissions of the key generated by the updated NCC, or further include new pre-configured resources. If a new pre-configured resource is included, the terminal device can use the new pre-configured resource to send encrypted data.
  • the above-mentioned key valid condition includes: the use duration of the key does not reach the valid duration and/or the number of uses of the key does not reach the number of valid transmissions.
  • the key invalidation conditions include: the use time of the key reaches the effective time length and/or the use times of the key reach the effective transmission times.
  • a timer is started when the key is generated, and during the running of the timer, the key generated based on the currently configured NCC remains valid.
  • the timer expires (for example, the timer reaches the above valid duration), the key generated based on the currently configured NCC becomes invalid.
  • the counter is initialized to 0 when the key is generated, and the counter is incremented by 1 for each uplink data transmission or downlink data reception; the key generated based on the currently configured NCC remains valid before the counter reaches the number of valid transmissions. When the counter reaches the number of valid transmissions mentioned above, the key generated based on the currently configured NCC becomes invalid.
  • the foregoing RRC release message further includes a time advance (TA, Time Advance) verification criterion.
  • TA Time Advance
  • the foregoing TA verification criterion includes a TA timer (TA Timer) and/or a reference signal received power (RSRP, Reference Signal Received Power) conversion threshold.
  • TA Timer TA Timer
  • RSRP Reference Signal Received Power
  • the terminal device verifies that the TA is valid according to the TA verification criterion, and when the key is valid, the encrypted data is sent by using the pre-configured resource.
  • the above-mentioned effective TA may include at least one of the following:
  • the RSRP change (increase or decrease) is smaller than the aforementioned RSRP conversion threshold.
  • the terminal device after sending uplink data, the terminal device receives a response message in the listening window, and the response message includes at least one of the following:
  • the first layer acknowledgement (L1ACK) message The first layer acknowledgement (L1ACK) message
  • MAC Media Access Control
  • CE Control Element
  • the UE may consider that the uplink data transmission is successful.
  • the foregoing L1ACK message includes the TA adjustment amount.
  • the aforementioned downlink data includes a TA adjustment amount.
  • the foregoing RRC message used for NCC update or pre-configured resource reconfiguration is multiplexed with downlink data and/or TA adjustment amount.
  • This embodiment is directed to the small data transmission of the UE in the inactive state in the NR system.
  • the preconditions for the UE to perform small data transmission include:
  • the cell where the UE is currently located supports small data transmission based on pre-configured resources
  • the UE has the function of transmitting small data in the inactive state.
  • Step 1 The UE initiates a small data transmission resource request in the connected state, which can optionally include resource configuration auxiliary information: such as the period of data transmission, the amount of data, and so on.
  • Step 2 The UE receives the RRC release message sent by the network and enters the inactive state, where the RRC release message may at least contain:
  • TA verification criteria including TA timer, RSRP change threshold, etc.
  • Step 3 The UE generates a new key based on the NCC configured in the RRC release message. If the RRC release message contains the valid duration of the key, the UE can start a timer when generating the key. During the running of the timer, the key generated based on the currently configured NCC remains valid. When the timer expires, the key generated based on the currently configured NCC becomes invalid. If the RRC release message contains the number of valid transmissions of the key, the UE initializes the counter to 0 after generating the key, and the counter is incremented by 1 for each uplink data transmission or downlink data reception.
  • FIG. 4 and 5 are schematic diagrams of two implementation manners of Embodiment 1 of the present application. Among them, Fig. 4 corresponds to the method of judging whether the key is invalid by using a timer, and Fig. 5 corresponds to the method of judging whether the key is invalid by using a counter.
  • the horizontal direction represents the time axis, and each rectangle represents the data sent by the UE using the pre-configured resources.
  • Step 4 During the key validity period, when the UE further uses the TA verification criterion to verify that the TA is valid and the configured resources are valid, the UE uses the pre-configured resources to transmit user data without multiplexing RRC messages.
  • Step 5 After the UE sends the uplink user data, it receives the response from the network in the listening window. When one of the following four types of responses is received, the UE can consider that the small data transmission is successful:
  • L1ACK optionally including TA adjustment amount (Time Advance Command);
  • Downlink data can optionally include TA adjustment
  • RRC message used for NCC update or pre-configured resource reconfiguration.
  • the RRC message can be multiplexed with downlink data and/or TA adjustment.
  • the above TA adjustment can be used to update the TA value maintained by the UE and restart the TA timer.
  • Fig. 6 is a schematic diagram of a small data transmission 600 based on pre-configured resources in the first embodiment of the present application, including: the UE sends uplink data (Uplink data) to the ng-eNB on the available PUR.
  • the ng-eNB and the core network equipment implement the 5GS Cellular Internet of Things (CIot, Cellular The Internet of Things) user plane function optimization solution for the mobile terminal caller's early data transmission (MO-EDT, Mobile-Originating Early Data Transmission) transmission process (MO-EDT procedure for user plane CIoT 5GS optimisations), where the aforementioned core network equipment includes access and mobility management functions (AMF, Access and Mobility Management Function), session management functions (SMF, Session Management Function)/user plane management Function (UPF, User Plane Function).
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • the ng-eNB sends feedback for uplink data to the UE, such as downlink data (optionally including TA adjustment), MAC CE indicating the TA adjustment, L1ACK (optionally including TA adjustment), or for NCC update or pre-processing.
  • uplink data such as downlink data (optionally including TA adjustment), MAC CE indicating the TA adjustment, L1ACK (optionally including TA adjustment), or for NCC update or pre-processing.
  • Configure the RRC message for resource reconfiguration.
  • This embodiment relates to a procedure for the UE to acquire a new NCC.
  • the UE can use one of the following methods to obtain a new NCC through the RRC connection release message again:
  • Method 1 The UE updates the NCC and triggers the RRC Resume process. Specifically, the UE may send an RRCResumeRequest message, and receive an RRCRelease message containing a new NCC sent by the network side.
  • Method 2 When uplink data arrives or the UE is paged, the UE triggers the RRC Resume process.
  • the specific method is the same as above.
  • Manner 3 When the uplink data arrives and meets the decimal transmission requirement, the UE triggers the small data transmission process based on random access. Specifically, the UE may send a preamble in the random access process, and after receiving the uplink resource configured on the network side, use the uplink resource to send the RRCResumeRequest message; and receive the RRCRelease message containing the new NCC sent by the network device .
  • FIG. 7 is a schematic diagram 1 of a manner of obtaining an updated NCC in Embodiment 2 of the present application.
  • Figure 7 takes the timer timeout as an example, corresponding to the above-mentioned mode one to the mode three. As shown in Figure 7, the horizontal represents the time axis, and each rectangle represents the data sent by the UE using pre-configured resources.
  • the timer expires/after the timer expires, the RRC Resume process or the small data transmission process based on random access is triggered; then the receiving network
  • the RRCRelease message containing the new NCC sent by the side uses the new NCC to regenerate the key and starts the timer.
  • the RRCRelease message may also carry the effective length of the new NCC generated key or the number of effective transmissions.
  • Manner 4 Multiplexing the RRCResumeRequest message or MAC CE indicating the NCC update in the small data transmission based on pre-configured resources. After that, the UE receives the RRCRelease message containing the new NCC sent by the network device.
  • FIG. 8 is a schematic diagram of a second embodiment of the second embodiment of the present application for obtaining an updated NCC.
  • Figure 8 takes the timer timeout as an example, which corresponds to the fourth mode above.
  • the horizontal direction represents the time axis; each rectangle before the timer expires represents the data sent by the UE using the pre-configured resources.
  • the RRCResumeRequest message or the MAC CE indicating the update of the NCC is multiplexed in the small data based on the pre-configured resource.
  • the UE receives the RRCRelease message containing the new NCC sent by the network side, uses the new NCC to regenerate the key, and starts the timer.
  • the RRCRelease message may also carry the effective length of the new NCC generated key or the number of effective transmissions.
  • the gNB may update the NCC through the downlink feedback of a certain small data transmission.
  • the UE After acquiring a new NCC, the UE generates a key based on the updated NCC and restarts the timer or initializes the counter to 0.
  • the terminal device can use pre-configured resources to transmit uplink user data without multiplexing RRC messages in the small data transmission process; and the key derived from NCC can be reused No need to update NCC frequently.
  • FIG. 9 is an implementation flowchart of a data transmission method 900 according to an embodiment of the present application, including:
  • S910 Send a pre-configured resource and/or a next hop link count NCC used to generate a key, where the pre-configured resource and key are used for the terminal device to send data.
  • sending the pre-configured resource and/or the NCC used to generate the key includes:
  • the above method further includes: sending the updated NCC.
  • the RRC release message also includes TA verification criteria.
  • the TA verification criterion includes a TA timer and/or RSRP conversion threshold.
  • the TA verification criterion is used for the terminal device to verify whether the TA is valid, and when the TA is valid and the key is valid, use pre-configured resources to send encrypted data.
  • the above-mentioned data includes small data transmitted by the terminal device in a disconnected state.
  • the foregoing method further includes: sending a response message, the response message including at least one of the following:
  • the foregoing L1ACK message includes the TA adjustment amount.
  • the aforementioned downlink data includes a TA adjustment amount.
  • the foregoing RRC message used for NCC update or pre-configured resource reconfiguration is multiplexed with downlink data and/or TA adjustment amount.
  • FIG. 10 is a schematic structural diagram of a terminal device 1000 according to an embodiment of the present application, including:
  • the transmission module 1010 is configured to use the key to encrypt data when the key is valid, and use pre-configured resources to send the encrypted data.
  • the above-mentioned terminal device further includes:
  • the key generation module 1120 is configured to generate the key based on the next hop link count NCC.
  • the aforementioned transmission module 1010 is further configured to: send a data transmission resource request; receive a radio resource control RRC release message, where the RRC release message includes at least one of the following:
  • the pre-configured resource
  • the NCC The NCC
  • the above-mentioned transmission module 1010 sends the data transmission resource request when the terminal device is in the connected state
  • a state conversion module 1130 configured to convert the terminal device into an inactive state after receiving the RRC release message.
  • the above-mentioned transmission module 1010 is further configured to: obtain an updated NCC; generate an updated key based on the updated NCC; use the updated key to encrypt data, and send it using pre-configured resources Encrypted data.
  • the above-mentioned transmission module 1010 obtains the updated NCC when the key is invalid.
  • the aforementioned transmission module 1010 uses at least one of the following to obtain the updated NCC:
  • the foregoing case where the key is valid includes: the use duration of the key does not reach the valid duration and/or the number of uses of the key does not reach the number of valid transmissions.
  • the foregoing key invalidation situation includes: the use duration of the key reaches the valid duration and/or the number of uses of the key reaches the number of valid transmissions.
  • the foregoing RRC release message further includes a timing advance TA verification criterion.
  • the above TA verification criterion includes a TA timer and/or a reference signal received power RSRP conversion threshold.
  • the above-mentioned transmission module 1010 uses a pre-configured resource to send encrypted data on the premise that the TA is validated according to the TA verification criterion and when the key is valid.
  • the aforementioned data includes small data transmitted by the terminal device in a non-connected state.
  • the aforementioned terminal device further includes: a response receiving module 1140, configured to receive a response message in the listening window, where the response message includes at least one of the following:
  • the first layer acknowledges the L1ACK message
  • the media access control MAC control unit CE indicating the TA adjustment amount
  • the foregoing L1ACK message includes the TA adjustment amount.
  • the aforementioned downlink data includes a TA adjustment amount.
  • the foregoing RRC message used for NCC update or pre-configured resource reconfiguration is multiplexed with downlink data and/or TA adjustment amount.
  • FIG. 12 is a schematic structural diagram of a network device 1200 according to an embodiment of the present application, including:
  • the configuration module 1210 is configured to send a pre-configured resource and/or a next hop link count NCC used to generate a key, where the pre-configured resource and key are used for the terminal device to send data.
  • the above configuration module 1210 is configured to: receive a data transmission resource request; and send a radio resource control RRC release message, where the RRC release message includes at least one of the following:
  • the pre-configured resource
  • the NCC The NCC
  • the above-mentioned network device further includes: an update module 1320, configured to send an updated NCC.
  • the foregoing RRC release message further includes a timing advance TA verification criterion.
  • the above TA verification criterion includes a TA timer and/or a reference signal received power RSRP conversion threshold.
  • the above TA verification criterion is used for the terminal device to verify whether the TA is valid, and when the TA is valid and the key is valid, the encrypted data is sent using pre-configured resources.
  • the aforementioned data includes small data transmitted by the terminal device in a non-connected state.
  • the aforementioned network device further includes: a response module 1330, configured to send a response message, where the response message includes at least one of the following:
  • the first layer acknowledges the L1ACK message
  • the media access control MAC control unit CE indicating the TA adjustment amount
  • the foregoing L1ACK message includes the TA adjustment amount.
  • the aforementioned downlink data includes a TA adjustment amount.
  • the foregoing RRC message used for NCC update or pre-configured resource reconfiguration is multiplexed with downlink data and/or TA adjustment amount.
  • FIG. 14 is a schematic structural diagram of a communication device 1400 according to an embodiment of the present application.
  • the communication device 1400 shown in FIG. 14 includes a processor 1410, and the processor 1410 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 1400 may further include a memory 1420.
  • the processor 1410 may call and run a computer program from the memory 1420 to implement the method in the embodiment of the present application.
  • the memory 1420 may be a separate device independent of the processor 1410, or may be integrated in the processor 1410.
  • the communication device 1400 may further include a transceiver 1430, and the processor 1410 may control the transceiver 1430 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 1430 may include a transmitter and a receiver.
  • the transceiver 1430 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 1400 may be a terminal device of an embodiment of the present application, and the communication device 1400 may implement corresponding procedures implemented by the terminal device in each method of the embodiments of the present application. For brevity, details are not described herein again.
  • the communication device 1400 may be a network device of an embodiment of the present application, and the communication device 1400 may implement corresponding processes implemented by the network device in each method of the embodiments of the present application. For brevity, details are not described herein again.
  • FIG. 15 is a schematic structural diagram of a chip 1500 according to an embodiment of the present application.
  • the chip 1500 shown in FIG. 15 includes a processor 1510, and the processor 1510 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 1500 may further include a memory 1520.
  • the processor 1510 can call and run a computer program from the memory 1520 to implement the method in the embodiment of the present application.
  • the memory 1520 may be a separate device independent of the processor 1510, or may be integrated in the processor 1510.
  • the chip 1500 may further include an input interface 1530.
  • the processor 1510 can control the input interface 1530 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 1500 may further include an output interface 1540.
  • the processor 1510 can control the output interface 1540 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the terminal device or the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the terminal device or the network device in the various methods of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the terminal device or the network device in the various methods of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the terminal device or the network device in the various methods of the embodiment of the present application.
  • the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip, etc.
  • the aforementioned processors may be general-purpose processors, digital signal processors (digital signal processors, DSP), ready-made programmable gate arrays (field programmable gate arrays, FPGAs), application specific integrated circuits (ASICs), or Other programmable logic devices, transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processors
  • FPGA field programmable gate arrays
  • ASIC application specific integrated circuits
  • the aforementioned general-purpose processor may be a microprocessor or any conventional processor.
  • the above-mentioned memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM).
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instruction may be transmitted from a website, computer, server, or data center through a cable (Such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • the size of the sequence number of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application.
  • the implementation process constitutes any limitation.

Landscapes

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

Abstract

Les modes de réalisation de la présente invention se réfèrent à un procédé de transmission de données, à un dispositif terminal et à un dispositif de communication. Le procédé comprend les étapes suivantes : lorsqu'une clé est valide, chiffrer des données à l'aide de la clé et envoyer les données chiffrées à l'aide d'une ressource préconfigurée. Les modes de réalisation de la présente invention permettent de réaliser la transmission de petites données d'un dispositif terminal dans un état inactif.
PCT/CN2020/084308 2020-04-10 2020-04-10 Procédé de transmission de données, dispositif terminal et dispositif réseau WO2021203439A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202080093637.3A CN115004739A (zh) 2020-04-10 2020-04-10 数据传输方法、终端设备和网络设备
PCT/CN2020/084308 WO2021203439A1 (fr) 2020-04-10 2020-04-10 Procédé de transmission de données, dispositif terminal et dispositif réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/084308 WO2021203439A1 (fr) 2020-04-10 2020-04-10 Procédé de transmission de données, dispositif terminal et dispositif réseau

Publications (1)

Publication Number Publication Date
WO2021203439A1 true WO2021203439A1 (fr) 2021-10-14

Family

ID=78022378

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/084308 WO2021203439A1 (fr) 2020-04-10 2020-04-10 Procédé de transmission de données, dispositif terminal et dispositif réseau

Country Status (2)

Country Link
CN (1) CN115004739A (fr)
WO (1) WO2021203439A1 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108632815A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 通信方法与设备
CN109309918A (zh) * 2017-07-27 2019-02-05 华为技术有限公司 通信方法、基站和终端设备
WO2019140633A1 (fr) * 2018-01-19 2019-07-25 Oppo广东移动通信有限公司 Procédé permettant d'ordonner à un équipement utilisateur d'obtenir une clé, équipement utilisateur et dispositif de réseau
CN110495232A (zh) * 2017-04-03 2019-11-22 华为技术有限公司 用于无线通信系统的资源配置的方法和系统
CN110574334A (zh) * 2017-05-05 2019-12-13 诺基亚技术有限公司 提供安全信息
US20200053791A1 (en) * 2018-08-13 2020-02-13 Qualcomm Incorporated Downlink data transmission in rrc inactive mode
CN110958688A (zh) * 2018-09-26 2020-04-03 夏普株式会社 用户设备及其执行的方法、基站及其执行的方法

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108632815A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 通信方法与设备
CN110495232A (zh) * 2017-04-03 2019-11-22 华为技术有限公司 用于无线通信系统的资源配置的方法和系统
CN110574334A (zh) * 2017-05-05 2019-12-13 诺基亚技术有限公司 提供安全信息
CN109309918A (zh) * 2017-07-27 2019-02-05 华为技术有限公司 通信方法、基站和终端设备
WO2019140633A1 (fr) * 2018-01-19 2019-07-25 Oppo广东移动通信有限公司 Procédé permettant d'ordonner à un équipement utilisateur d'obtenir une clé, équipement utilisateur et dispositif de réseau
US20200053791A1 (en) * 2018-08-13 2020-02-13 Qualcomm Incorporated Downlink data transmission in rrc inactive mode
CN110958688A (zh) * 2018-09-26 2020-04-03 夏普株式会社 用户设备及其执行的方法、基站及其执行的方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON, ZTE CORPORATION: "Early activation of security", 3GPP DRAFT; R2-1816632-EARLY ACTIVATION OF SECURITY, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Spokane, USA; 20181112 - 20181116, 12 November 2018 (2018-11-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051556202 *
OPPO: "The security issues for RRC Resume procedure", 3GPP DRAFT; R2-1806950-THE SECURITY ISSUES FOR RRC RESUME PROCEDURE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Busan, Korea; 20180521 - 20180525, 20 May 2018 (2018-05-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051443384 *

Also Published As

Publication number Publication date
CN115004739A (zh) 2022-09-02

Similar Documents

Publication Publication Date Title
KR20210116602A (ko) 무선 통신 방법, 단말 장치 및 네트워크 장치
US20230070801A1 (en) Multicast downlink service notification method, terminal device and network device
WO2021189461A1 (fr) Procédé de détermination de groupe de radiomessagerie, équipement terminal et dispositif de réseau
WO2019210521A1 (fr) Procédé de mise à jour d'informations système, dispositif terminal et dispositif de réseau
US20230397298A1 (en) Timer operating method, terminal device, and network device
WO2022067771A1 (fr) Procédé de transmission de données et dispositif terminal
US20230337111A1 (en) Terminal device and network device
WO2020164025A1 (fr) Procédé et dispositif de transfert d'état
WO2023108454A1 (fr) Procédé pour maintenir une avance temporelle dans synchronisation de liaison montante, et dispositif terminal et dispositif de réseau
WO2021203439A1 (fr) Procédé de transmission de données, dispositif terminal et dispositif réseau
WO2021212465A1 (fr) Procédé de communication sans fil et dispositif terminal
WO2021189368A1 (fr) Procédé de rapport de libération de groupe de cellules secondaires, et dispositif terminal
WO2022147729A1 (fr) Procédé de commande de puissance, dispositif de terminal et dispositif de réseau
US20230189087A1 (en) Communication method and communication apparatus
WO2022183317A1 (fr) Procédé d'obtention d'informations de tranche et dispositif terminal
WO2021232256A1 (fr) Procédé de notification d'informations d'assistance d'ue, équipement utilisateur et équipement réseau
WO2022213393A1 (fr) Procédé de radiorecherche, dispositif, et support de stockage
WO2024011588A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif réseau
CN115175349B (zh) 参数设置方法、参数指示方法和终端设备
WO2023102829A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif réseau
WO2023102812A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
WO2021163978A1 (fr) Procédé de commande d'un état d'un groupe de cellules secondaires, et dispositif terminal
WO2023133794A1 (fr) Procédé de transmission de données, dispositif terminal et dispositif de réseau
WO2024065137A1 (fr) Procédé d'acquisition d'informations de configuration, procédé de transfert d'informations de configuration et équipement terminal
WO2021253417A1 (fr) Procédé de transmission de données et dispositif de réseau

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

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

Country of ref document: EP

Kind code of ref document: A1