Wireless communication method, terminal device and network device

Abstract

The embodiment of the present application provides a method, terminal device and network device for wireless communication, wherein a terminal in an RRC deactivated state can determine a period for obtaining a system message update indication and an updated system message, thereby optimizing the transmission of the system message. The wireless communication method includes: the terminal device uses a target period to obtain a system message update indication and an updated system message; wherein the terminal device is in an RRC deactivated state.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and more specifically, to a wireless communication method, terminal equipment, and network equipment. Background Art

[0002] In the Long Term Evolution (LTE) system, for a terminal whose extended discontinuous reception (eDRX) period is greater than the system message update period, when the terminal is in the Radio Resource Control (RRC) idle (IDLE) state, the terminal uses the eDRX acquisition period to obtain updated system messages. For a terminal in the RRC deactivated (INACTIVE) state, how to determine the period for obtaining updated system messages is an urgent problem to be solved. Summary of the invention

[0003] The embodiments of the present application provide a method, terminal device and network device for wireless communication. A terminal in an RRC deactivated state can determine the period for obtaining a system message update indication and an updated system message, thereby optimizing the transmission of system messages.

[0004] In a first aspect, a wireless communication method is provided, the method comprising:

[0005] The terminal device uses the target period to obtain the system message update indication and the updated system message;

[0006] Among them, the terminal device is in the RRC deactivated state.

[0007] In a second aspect, a wireless communication method is provided, the method comprising:

[0008] The network device sends a system message update indication and an updated system message to the terminal device using a target period;

[0009] Among them, the terminal device is in the RRC deactivated state.

[0010] In a third aspect, a terminal device is provided for executing the method in the first aspect.

[0011] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect.

[0012] In a fourth aspect, a network device is provided for executing the method in the second aspect.

[0013] Specifically, the network device includes a functional module for executing the method in the above second aspect.

[0014] In a fifth aspect, a terminal device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect.

[0015] In a sixth aspect, a network device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect.

[0016] In a seventh aspect, a device is provided for implementing the method in any one of the first to second aspects above.

[0017] Specifically, the apparatus includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the apparatus executes the method in any one of the first to second aspects described above.

[0018] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method in any one of the first to second aspects above.

[0019] In a ninth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to second aspects above.

[0020] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects above.

[0021] Through the above technical solution, a terminal in an RRC deactivated state can use the target period to obtain a system message update indication and an updated system message, and a network device can use the target period to send a system message update indication and an updated system message to a terminal in an RRC deactivated state, thereby optimizing the transmission of system messages. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 It is a schematic diagram of a communication system architecture applied in an embodiment of the present application.

[0023] Figure 2 It is a schematic diagram of a system message update cycle provided by the present application.

[0024] Figure 3 It is a schematic flowchart of a wireless communication method provided according to an embodiment of the present application.

[0025] Figure 4 It is a schematic diagram of a system message update period and a first eDRX acquisition period provided in an embodiment of the present application.

[0026] Figure 5 It is a schematic diagram of a system message update period, a first eDRX acquisition period and a second eDRX acquisition period provided in an embodiment of the present application.

[0027] Figure 6 It is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

[0028] Figure 7 It is a schematic block diagram of a network device provided according to an embodiment of the present application.

[0029] Figure 8 It is a schematic block diagram of a communication device provided according to an embodiment of the present application.

[0030] Fig. 9 It is a schematic block diagram of a device provided according to an embodiment of the present application.

[0031] Fig.10 It is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0032] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. For the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0033] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0034] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0035] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0036] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0037] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0038] The terminal device can be a station (STATION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0039] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).

[0040] In the embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0041] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

[0042] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode 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 or base station (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.

[0043] As an example but not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0044] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0045] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 1 The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographical area and may communicate with terminal devices located in the coverage area.

[0046] Figure 1 One network device and two terminal devices are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0047] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0048] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0049] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0050] The terms used in the implementation mode of this application are only used to explain the specific embodiments of this application, and are not intended to limit this application. The terms "first", "second", "third" and "fourth" in the specification and claims of this application and the drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0051] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0052] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.

[0053] In the embodiments of the present application, "pre-definition" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

[0054] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0055] In order to better understand the embodiments of the present application, the RRC state of the terminal related to the present application is explained.

[0056] In LTE and 5G systems, there are three RRC protocol states, namely, RRC idle (RRC_IDLE) state, RRC deactivated (RRC_INACTIVE) state and RRC connected (RRC_CONNECTED) state.

[0057] RRC_IDLE: Mobility is based on terminal cell selection reselection, paging is initiated by the core network (CN), and the paging area is configured by the CN. There is no access stratum (AS) context of the terminal on the base station side. There is no RRC connection.

[0058] RRC_INACTIVE: Mobility is based on terminal cell selection reselection, there is a connection between CN and NR, the UE AS context exists on a base station, paging is triggered by the Radio Access Network (RAN), the RAN-based paging area is managed by the RAN, and the network side knows the location of the terminal based on the RAN paging area level.

[0059] RRC_CONNECTED: An RRC connection exists, and a UE AS context exists between the base station and the terminal. The network knows the location of the terminal at the cell level. The mobility is controlled by the network. Data can be transmitted between the terminal and the base station.

[0060] In order to better understand the embodiments of the present application, the 5G NR paging mechanism related to the present application is described.

[0061] The main function of paging is to enable the network to page the UE through a paging message when the UE is in RRC IDLE or RRC INACTIVE state, or to notify the UE of system message changes or earthquake tsunami / public warning information through a short message (applicable to all RRC states of the UE, including the connected state).

[0062] Paging includes the Physical Downlink Control Channel (PDCCH) scrambled by the Paging Radio Network Temporary Identity (P-RNTI) and the Physical Downlink Shared Channel (PDSCH) scheduled by the PDCCH. Paging message is transmitted in PDSCH, and short message is 8 bits in PDCCH.

[0063] For UEs in RRC_IDLE or RRC_INACTIVE states, since there is no other data communication between the UE and the network, in order to save power on the terminal, the UE can monitor the paging channel discontinuously, that is, adopt the paging DRX mechanism. Under the Paging DRX mechanism, the UE only needs to monitor paging during one paging occasion (Paging Occasion, PO) in each discontinuous reception (DRX) cycle. PO is a series of PDCCH monitoring opportunities and it can be composed of multiple time slots. There is also the concept of paging frame (Paging Frame, PF), which refers to a radio frame (fixed 10ms), which can contain multiple POs or the starting positions of multiple POs.

[0064] The Paging DRX cycle is determined by the common cycle in the system broadcast and the dedicated cycle configured in the high-level signaling (Non-AccessStratum (NAS) signaling). The UE takes the minimum cycle of the two as the Paging Cycle cycle. From the network perspective, a paging DRX cycle can have multiple POs. The location where the UE monitors the PO is related to the UE's identity (ID). The specific method for determining the PF and PO of a UE in a Paging DRX can be as follows:

[0065] The PF system frame number (SFN) is determined by the following formula 1:

[0066] (SFN + PF_offset) mod T = (T div N)*(UE_ID mod N) Formula 1 The index (Index(i_s)) of the PO in a PF is determined by the following formula 2:

[0067] i_s = floor (UE_ID / N) mod Ns Formula 2

[0068] Wherein, T represents the DRX cycle of the UE receiving paging. The network will broadcast a default DRX cycle. If the RRC / higher layer has configured a UE-specific DRX cycle for the UE, the minimum of the DRX cycle broadcast by the network and the UE-specific DRX cycle configured by the RRC / higher layer will be used as the DRX cycle of the UE. If the RRC / higher layer has not configured a UE-specific DRX cycle for the UE, the DRX cycle broadcast by the network will be used as the DRX cycle of the UE. N represents the number of PFs contained in a DRX cycle. Ns represents the number of POs contained in a PF. PF_offset represents a time domain offset used to determine the PF. UE_ID is used to represent 5G-S-TMSI mod 1024.

[0069] For a UE, according to the above formula 1 and formula 2, the position of PF and the index of PO in a paging DRX cycle can be known. PO is composed of multiple PDCCH monitoring occasions. A PO contains X PDCCH monitoring occasions, where X is equal to the number of synchronization signal blocks (SSB) actually sent in the Master Information Block (MIB).

[0070] After the UE knows the PF, the index of the PO, and the number of PDCCH monitoring occasions in the PO, it only needs to know the starting position of the first PDCCH monitoring occasion of the PO through the relevant configuration parameters. The starting position can be configured through high-level signaling or obtained based on the PO index. The UE blindly detects the paging message based on the determined PO.

[0071] In order to better understand the embodiments of the present application, the LTE paging mechanism related to the present application is described.

[0072] In the LTE system, the pagingDRX mechanism is also used for UEs in the RRC_IDLE state or RRC_INACTIVE state. Similar to the NR system, under the PagingDRX mechanism, the UE only needs to monitor paging during a PO period in each DRX cycle. The LTE system also defines the concepts of PF and PO. Unlike the NR system, in the LTE system, PO corresponds to a subframe within the PF.

[0073] Similar to the NR system, in the LTE system, for a UE in the RRC IDLE state or the RRC INACTIVE state, the UE calculates its PO based on parameters such as the UE ID and T. T represents the DRX cycle of the UE receiving paging, which is determined as follows:

[0074] For UE in RRC IDLE state, if the upper layer configures eDRX for the UE and the configured eDRX cycle is 5.12s, T is taken as 5.12s. Otherwise, if the upper layer configures a UE-specific DRX cycle for the UE, the minimum of the network broadcast DRX cycle and the UE-specific DRX cycle configured by the upper layer is taken as T. If the upper layer does not configure a UE-specific DRX cycle for the UE, the network broadcast DRX cycle is taken as T.

[0075] For UE in RRC INACTIVE state, if the upper layer does not configure eDRX for the UE, the minimum of the DRX cycle broadcast by the network and the UE-specific DRX cycle configured by RRC / upper layer is used as T. Otherwise, if the upper layer configures eDRX for the UE, the minimum of the DRX cycle broadcast by the network and the UE-specific DRX cycle configured by RRC / upper layer is used as T during the paging time window (PTW); outside the PTW, the UE-specific DRX cycle configured by RRC is used as T.

[0076] In order to better understand the embodiments of the present application, the LTE eDRX mechanism related to the present application is described.

[0077] Considering that the services of NB-IoT and eMTC terminals are relatively simple and their service activity is low, these terminals are in a non-connected state most of the time. In addition, considering that the services of these terminals are not sensitive to latency requirements, in order to further save power in a non-connected state, LTE introduces the eDRX mechanism for these terminals, which can support a larger paging cycle, that is, a paging cycle greater than 256 SFNs. In LTE, the minimum value of the eDRX cycle configured by the high layer is 5.12s.

[0078] For a UE configured with eDRX, if the eDRX cycle of the UE is 5.12s, the UE calculates its corresponding PO based on T=5.12s. If the eDRX cycle of the UE is greater than or equal to 1 Hyper System Frame Number (H-SFN), the UE monitors the P-RNTI-scrambled PDCCH on its PO within the PTW time window within an eDRX cycle. Among them, PTW is exclusive to the UE and is determined based on the paging hyper system frame number (paging H-SFN, PH), a starting time point (PTW_start) and an ending time point (PTW_end) within the PH.

[0079] PH is an H-SFN that meets the following conditions:

[0080] H-SFN mod TeDRX, H=(UE_ID_H mod T eDRX,H );

[0081] Among them, UE_ID_H is obtained based on the hash ID, T eDRX,H It is an eDRX cycle in superframe units and is configured by the Access and Mobility Management Function (AMF) entity.

[0082] PTW_start is the starting radio frame number of PTW, which is an SFN that meets the following conditions:

[0083] SFN=256*i eDRX ,i eDRX =floor(UE_ID_H / T eDRX,H )mod 4.

[0084] PTW_end is the end radio frame number of PTW, which is the SFN that meets the following conditions:

[0085] SFN = (PTW_start + L*100-1) mod 1024; where L is the window length of PTW, configured by AMF.

[0086] In order to better understand the embodiments of the present application, the NR reduced capability (RedCap) terminal eDRX mechanism related to the present application is described.

[0087] In the work items of Release 17 (R17) NR, the 3GPP RAN Plenary Meeting agreed to study the low-capability NR terminal project (RP-193238). One of the goals of this project is to save power and extend battery life of RedCap terminals by introducing the eDRX mechanism in idle or deactivated state.

[0088] The following conclusions have been drawn about the eDRX mechanism for RedCap terminals:

[0089] For the RRC IDLE state, the DRX cycle is extended to greater than 2621.44s as a baseline. At the same time, it is also possible to study whether it is necessary to support a larger eDRX cycle (for example, 10485.76s).

[0090] For the RRC INACTIVE state, the DRX cycle is extended to 10.24s as a baseline. Whether a larger DRX cycle needs to be supported can be discussed later.

[0091] RAN2 needs to study whether the eDRX cycle in RRC IDLE and RRC INACTIVE states needs to support a value less than 5.12s;

[0092] For UEs in RRC IDLE and RRC INACTIVE states, if the maximum supported DRX cycle exceeds 10.24s, the eDRX mechanism in LTE with an eDRX cycle exceeding 10.24s (i.e., using PTW, PH, etc.) is used as the baseline;

[0093] For UEs in RRC IDLE and RRC INACTIVE states, if the eDRX cycle is less than 10.24s, paging monitoring does not use PTW and PH.

[0094] For UEs in RRC IDLE and RRC INACTIVE states, if the eDRX cycle is equal to 10.24s, the basic assumption is that PTW and PH are not used, but other solutions are not excluded.

[0095] In order to facilitate a better understanding of the embodiments of the present application, the system message update cycle related to the present application is explained.

[0096] In LTE and NR systems, the concept of system message update period is used. When the network wants to update the system message, the network first repeatedly sends the system message update indication in the nth system message update period, and then repeatedly sends the updated system message in the n+1th system message update period, such as Figure 2 The boundary of the system message update period is defined as the SFN that satisfies SFN mod m=0, where m is the number of SFNs included in one system message update period.

[0097] Optionally, the system message update period may be determined according to the following formula 3.

[0098] m=modificationPeriodCoeff*defaultPagingCycle, wherein m represents the system message update cycle, modificationPeriodCoeff represents the system message update cycle coefficient, and defaultPagingCycle represents the default paging cycle. Both the modificationPeriodCoeff and defaultPagingCycle parameters are determined by network broadcast.

[0099] In the LTE system, due to the introduction of the eDRX mechanism, in order to enable UEs in the RRC IDLE state and configured with a DRX cycle greater than the system message update cycle to receive system message update indications, the eDRX acquisition cycle is introduced. The boundary of the eDRX acquisition cycle is defined as the H-SFN that satisfies H-SFN mod 256 = 0. For NB-IoT, the boundary of the eDRX acquisition cycle is defined as the H-SFN that satisfies H-SFN mod1024 = 0. For a UE in the RRC IDLE state and configured with a DRX cycle not greater than the system message update cycle, if the UE receives a system message update indication (systemInfoModification) in the nth system message update cycle, the UE receives the updated system message in the n+1th system message update cycle. For a UE in the RRC IDLE state and configured with a DRX cycle greater than the system message update cycle, if the UE receives a system message update indication (systemInfoModification-eDRX) in the nth eDRX acquisition cycle, the UE receives the updated system message in the n+1th eDRX acquisition cycle.

[0100] In the NR system, the system message update period applies to all information blocks except the System Information Block (SIB).

[0101] 6, SIB7, SIB8, and updates of system messages other than positioning assistance data.

[0102] In the LTE system, for UEs whose eDRX cycle is greater than the system message update cycle, when the UE is in the RRC IDLE state, the UE uses the eDRX acquisition cycle to obtain updated system messages; when the UE is in the RRC INACTIVE state, how the UE determines the cycle for obtaining updated system messages is not specified in the current standard. Similarly, in the NR system, for RedCap terminals whose eDRX cycle is greater than the system message update cycle, when the UE is in the RRC INACTIVE state, how the UE determines the cycle for obtaining updated system messages is also a problem that needs to be solved.

[0103] Based on the above problems, the present application proposes a solution for determining the period for obtaining updated system messages. A terminal in an RRC deactivated state can determine the period for obtaining system message update indications and updated system messages, thereby optimizing the transmission of system messages.

[0104] The technical solution of the present application is described in detail below through specific embodiments.

[0105] Figure 3 is a schematic flow chart of a wireless communication method 200 according to an embodiment of the present application, such as Figure 3 As shown, the method 200 may include at least part of the following contents:

[0106] S210, the network device sends a system message update indication and an updated system message to the terminal device using a target period;

[0107] S220, the terminal device uses the target period to obtain the system message update indication and the updated system message.

[0108] Among them, the terminal device is in the RRC deactivated state.

[0109] Optionally, in an embodiment of the present application, the terminal device may determine the target cycle according to DRX cycle information and / or eDRX cycle information. And / or, the network device may determine the target cycle according to DRX cycle information and / or eDRX cycle information.

[0110] Optionally, the DRX cycle information may be a CN DRX cycle, for example, a UE-specific DRX cycle included in a DRX parameter configured by a NAS message from the CN, i.e., a CN DRX cycle. The DRX cycle information may also be a RAN DRX cycle, for example, an RRC release message from the RAN instructs the UE to enter an RRC deactivated state, and configures a UE-specific RAN paging cycle (ran-PagingCycle), i.e., a RAN DRX cycle.

[0111] Optionally, the eDRX cycle information may be a CN eDRX cycle, for example, an eDRX cycle included in an eDRX parameter configured by a NAS message from the CN, i.e., a CN eDRX cycle. The eDRX cycle information may also be a RAN eDRX cycle, for example, an RRC release message from the RAN instructs the UE to enter an RRC deactivated state, and configures a UE-specific RAN paging cycle (ran-PagingCycle), i.e., a RAN DRX cycle, and configures a UE-specific RAN eDRX cycle.

[0112] Optionally, as embodiment 1, the terminal device and / or the network device may determine the target period in the following manner:

[0113] In the case where the CN eDRX cycle is greater than the system message update cycle, and the RAN DRX cycle is greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle; and / or,

[0114] When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0115] When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, determining the first eDRX acquisition cycle as the target cycle; and / or,

[0116] When the CN eDRX period is less than or equal to the system message update period, the system message update period is determined as the target period.

[0117] That is, in one implementation, for a terminal device in an RRC deactivated state, if the network device configures a CN eDRX cycle for the terminal device, and the CN eDRX cycle is greater than the system message update cycle. In this case, if the network device configures a RAN DRX cycle for the terminal device through RRC signaling, and the RAN DRX cycle is greater than the system message update cycle, the terminal device uses the first eDRX acquisition cycle to obtain updated system messages. If the network device configures a RAN DRX cycle for the terminal device through RRC signaling, and the RAN DRX cycle is less than or equal to the system message update cycle, the terminal device uses the system message update cycle to obtain updated system messages. If the network device does not configure a RAN DRX cycle for the terminal device through RRC signaling, the terminal device uses the first eDRX acquisition cycle to obtain updated system messages.

[0118] That is, in another implementation, for a terminal device in an RRC deactivated state, if the network device configures a CN eDRX cycle for the terminal device, and the CN eDRX cycle is less than or equal to the system message update cycle, the terminal device uses the system message update cycle to obtain updated system messages.

[0119] Optionally, in an implementation manner of embodiment 1, the first eDRX acquisition cycle is an eDRX acquisition cycle configured for a terminal whose CN eDRX cycle is greater than a system message update cycle. For example, for an LTE system, the first eDRX acquisition cycle is an eDRX acquisition cycle defined in the current standard for a terminal whose CN eDRX cycle is greater than a system message update cycle.

[0120] Optionally, in another implementation of Embodiment 1, the first eDRX acquisition cycle is the product of the maximum CN eDRX cycle supported by the terminal device and the coefficient M1, M1≥1. Optionally, the terminal device is a reduced capability (RedCap) terminal. Optionally, the value of the coefficient M1 is pre-configured or agreed upon by the protocol, or the value of the coefficient M1 is configured by the network device. For example, for an NR RedCap terminal, the first eDRX acquisition cycle is defined as m1=M1*the maximum CNeDRX cycle that the RedCap terminal can support.

[0121] Optionally, in embodiment 1, the RRC idle state and the RRC deactivated state share the first eDRX acquisition cycle.

[0122] That is to say, in Example 1, a common first eDRX acquisition cycle is defined for the RRC idle state and the RRC deactivated state. For the terminal in the RRC deactivated state, when the CN eDRX cycle and RAN DRX cycle (if the RRC configures this parameter) configured by the network for the terminal are both greater than the system message update cycle, the terminal uses the first eDRX acquisition cycle to obtain updated system messages.

[0123] In Embodiment 1, for example, the system information (SI) update period and the first eDRX acquisition period may be as follows: Figure 4 shown.

[0124] It should be noted that, in Embodiment 1, only NAS configuration of CN eDRX is supported, and RRC configuration of RAN eDRX is not supported (for example, the maximum value of the RAN paging cycle configurable by the base station does not exceed 10.24s).

[0125] Optionally, as embodiment 2, the terminal device and / or the network device may specifically determine the target period in the following manner:

[0126] When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is greater than the system message update cycle, determining the second eDRX acquisition cycle as the target cycle; and / or,

[0127] When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0128] When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, determining the first eDRX acquisition cycle as the target cycle; and / or,

[0129] When the CN eDRX period is less than or equal to the system message update period, the system message update period is determined as the target period.

[0130] That is, in one implementation, for a terminal device in an RRC deactivated state, if the network device configures a CN eDRX cycle for the terminal device, and the CN eDRX cycle is greater than the system message update cycle. In this case, if the network device configures a RAN DRX cycle for the terminal device through RRC signaling, and the RAN DRX cycle is greater than the system message update cycle, the terminal device uses the second eDRX acquisition cycle to obtain updated system messages. If the network device configures a RAN DRX cycle for the terminal device through RRC signaling, and the RAN DRX cycle is less than or equal to the system message update cycle, the terminal device uses the system message update cycle to obtain updated system messages. If the network device does not configure a RAN DRX cycle for the terminal device through RRC signaling, the terminal device uses the first eDRX acquisition cycle to obtain updated system messages.

[0131] That is, in another implementation, for a terminal device in an RRC deactivated state, if the network device configures a CN eDRX cycle for the terminal device, and the CN eDRX cycle is less than or equal to the system message update cycle, the terminal device uses the system message update cycle to obtain updated system messages.

[0132] Optionally, in an implementation manner of Embodiment 2, the first eDRX acquisition period is an eDRX acquisition period configured for a terminal whose CN eDRX period is greater than a system message update period; and / or, the second eDRX acquisition period is a product of a maximum RAN DRX period supported by the first network and a coefficient M2, where M2≥1. Optionally, the first network is an LTE network or an NR network. Optionally, the value of the coefficient M2 is pre-configured or agreed upon by a protocol, or the value of the coefficient M2 is configured by a network device.

[0133] For example, for an LTE system, the first eDRX acquisition cycle is an eDRX acquisition cycle defined in the current standard for a terminal whose CN eDRX cycle is greater than a system message update cycle.

[0134] For example, the second eDRX acquisition cycle is defined as m2=M2*maximum RAN DRX cycle supportable by the first network, where M2 is greater than or equal to 1, and the value of M2 is a predefined value or is determined by system message configuration.

[0135] Optionally, in another implementation of Example 2, the first eDRX acquisition period is the product of the maximum CN eDRX period supported by the terminal device and a coefficient M3, M3≥1; and / or, the second eDRX acquisition period is the product of the maximum RAN DRX period supported by the terminal device and a coefficient M4, M4≥1. Optionally, the terminal device is a reduced capability (RedCap) terminal. Optionally, the value of the coefficient M3 is pre-configured or agreed upon by a protocol, or the value of the coefficient M3 is configured by a network device. Optionally, the value of the coefficient M4 is pre-configured or agreed upon by a protocol, or the value of the coefficient M4 is configured by a network device.

[0136] For example, the first eDRX acquisition cycle is defined as m1=M3*the maximum CN eDRX cycle that the RedCap terminal can support, where M3 is greater than or equal to 1, and the value of M3 is a predefined value or is determined by system message configuration.

[0137] For example, the second eDRX acquisition cycle is defined as m2=M4*the maximum RAN DRX cycle that the RedCap terminal can support, wherein M4 is greater than or equal to 1, and the value of M4 is a predefined value or is determined by system message configuration.

[0138] Optionally, in Embodiment 2, the RRC idle state corresponds to the first eDRX acquisition cycle, and the RRC deactivated state corresponds to the first eDRX acquisition cycle and / or the second eDRX acquisition cycle.

[0139] That is, in Embodiment 2, for a UE in RRC deactivated state, when the CN eDRX cycle configured by the network for the UE is greater than the system message update cycle, the cycle for the UE to obtain updated system messages is determined according to whether the RRC configures a RAN DRX cycle for the UE and the value of the configured RAN DRX cycle.

[0140] In Embodiment 2, for example, the system message update period, the first eDRX acquisition period, and the second eDRX acquisition period may be as follows: Figure 5 shown.

[0141] It should be noted that, in Embodiment 2, only NAS configuration of CN eDRX is supported, and RRC configuration of RAN eDRX is not supported (for example, the maximum value of the RAN paging cycle configurable by the base station does not exceed 10.24s).

[0142] Optionally, as embodiment 3, the terminal device and / or the network device may determine the target period in the following manner:

[0143] In the case that both the CN eDRX cycle and the RAN eDRX cycle are greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle; and / or,

[0144] When the CN eDRX cycle is less than or equal to the system message update cycle, and / or the RAN eDRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0145] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle; and / or,

[0146] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0147] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, determining the first eDRX acquisition cycle as the target cycle; and / or,

[0148] When the CN eDRX cycle is less than or equal to the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, the system message update cycle is determined as the target cycle.

[0149] That is, in some implementations, for a terminal device in an RRC deactivated state, if the network device configures a CN eDRX cycle and a RAN eDRX cycle for the terminal device, if the CN eDRX cycle and the RAN eDRX cycle are both greater than the system message update cycle, the terminal device uses the first eDRX acquisition cycle to obtain updated system messages; otherwise, the terminal device uses the system message update cycle to obtain updated system messages.

[0150] That is, in some other implementations, for a terminal device in an RRC deactivated state, if the network device configures a CN eDRX cycle for the terminal device, but does not configure a RAN eDRX cycle. In this case, if the CN eDRX cycle is greater than the system message update cycle, and if the network device configures a RAN DRX cycle for the terminal device through RRC signaling, and the RAN DRX cycle is greater than the system message update cycle, the terminal device uses the first eDRX acquisition cycle to obtain updated system messages. If the CN eDRX cycle is greater than the system message update cycle, and if the network device configures a RAN DRX cycle for the terminal device through RRC signaling, and the RAN DRX cycle is less than or equal to the system message update cycle, the terminal device uses the system message update cycle to obtain updated system messages. If the CN eDRX cycle is greater than the system message update cycle, and if the network device does not configure a RAN DRX cycle for the terminal device through RRC signaling, the terminal device uses the first eDRX acquisition cycle to obtain updated system messages. If the CN eDRX cycle is less than or equal to the system message update cycle, the terminal device uses the system message update cycle to obtain updated system messages.

[0151] Optionally, in an implementation of Embodiment 3, the first eDRX acquisition period is the product of the maximum CN eDRX period supported by the terminal device and the coefficient M5, M5≥1. Optionally, the terminal device is a reduced capability (RedCap) terminal. Optionally, the value of the coefficient M5 is pre-configured or agreed upon by a protocol, or the value of the coefficient M5 is configured by a network device.

[0152] For example, for the NR RedCap terminal, the first eDRX acquisition cycle is defined as m1=M5*the maximum CN eDRX cycle that the RedCap terminal can support, where M5 is greater than or equal to 1, and the value of M5 is a predefined value or determined by system message configuration.

[0153] Optionally, in another implementation of Embodiment 3, the first eDRX acquisition period is the product of the maximum RAN eDRX period supported by the terminal device and the coefficient M6, M6≥1. Optionally, the terminal device is a reduced capability (RedCap) terminal. Optionally, the value of the coefficient M6 is pre-configured or agreed upon by a protocol, or the value of the coefficient M6 is configured by a network device.

[0154] For example, for an NR RedCap terminal, the first eDRX acquisition cycle is defined as m1=M6*the maximum RAN eDRX cycle that the RedCap terminal can support, where M6 is greater than or equal to 1, and the value of M6 is a predefined value or determined by system message configuration.

[0155] Optionally, in Embodiment 3, the RRC idle state and the RRC deactivated state share the first eDRX acquisition cycle.

[0156] That is, in Embodiment 3, a common first eDRX acquisition cycle is defined for the RRC idle state and the RRC deactivated state. For a terminal in the RRC deactivated state, when the CN eDRX cycle configured by the network for the UE is greater than the system message update cycle, and when the network configures the UE with a RAN eDRX cycle, and the RAN eDRX cycle is greater than the system message update cycle, the UE uses the first eDRX acquisition cycle to obtain updated system messages. Alternatively, when the CN eDRX cycle configured by the network for the UE is greater than the system message update cycle, and when the network does not configure the UE with a RAN eDRX cycle, the network does not configure the UE with a RAN DRX cycle, or the configured RAN DRX cycle is greater than the system message update cycle, the UE uses the first eDRX acquisition cycle to obtain updated system messages.

[0157] It should be noted that, in Embodiment 3, both NAS configuration of CN eDRX and RRC configuration of RAN eDRX are supported (for example, the maximum value of the RAN paging cycle that can be configured by the base station does not exceed 10.24s).

[0158] Optionally, as Embodiment 4, the terminal device and / or the network device may specifically determine the target period in the following manner:

[0159] In the case that both the CN eDRX cycle and the RAN eDRX cycle are greater than the system message update cycle, determining the second eDRX acquisition cycle as the target cycle; and / or,

[0160] When the CN eDRX cycle is less than or equal to the system message update cycle, and / or the RAN eDRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0161] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, determining the second eDRX acquisition cycle as the target cycle; and / or,

[0162] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0163] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, determining the first eDRX acquisition cycle as the target cycle; and / or,

[0164] When the CN eDRX cycle is less than or equal to the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, the system message update cycle is determined as the target cycle.

[0165] That is, in some implementations, for a terminal device in an RRC deactivated state, if the network device configures a CN eDRX cycle and a RAN eDRX cycle for the terminal device, if the CN eDRX cycle and the RAN eDRX cycle are both greater than the system message update cycle, the terminal device uses the second eDRX acquisition cycle to obtain updated system messages; otherwise, the terminal device uses the system message update cycle to obtain updated system messages.

[0166] That is, in some other implementations, for a terminal device in an RRC deactivated state, if the network device configures a CN eDRX cycle for the terminal device, but does not configure a RAN eDRX cycle. In this case, if the CN eDRX cycle is greater than the system message update cycle, and if the network device configures a RAN DRX cycle for the terminal device through RRC signaling, and the RAN DRX cycle is greater than the system message update cycle, the terminal device uses the second eDRX acquisition cycle to obtain updated system messages. If the CN eDRX cycle is greater than the system message update cycle, and if the network device configures a RAN DRX cycle for the terminal device through RRC signaling, and the RAN DRX cycle is less than or equal to the system message update cycle, the terminal device uses the system message update cycle to obtain updated system messages. If the CN eDRX cycle is greater than the system message update cycle, and if the network device does not configure a RAN DRX cycle for the terminal device through RRC signaling, the terminal device uses the first eDRX acquisition cycle to obtain updated system messages. If the CN eDRX cycle is less than or equal to the system message update cycle, the terminal device uses the system message update cycle to obtain updated system messages.

[0167] Optionally, in an implementation manner of Embodiment 4, the first eDRX acquisition period is the product of the maximum CN eDRX period supported by the terminal device and a coefficient M7, M7≥1. The second eDRX acquisition period is the product of the maximum RAN eDRX period supported by the terminal device and a coefficient M8, M8≥1. Optionally, the terminal device is a reduced capability (RedCap) terminal. Optionally, the value of the coefficient M7 is pre-configured or agreed upon by a protocol, or the value of the coefficient M7 is configured by a network device. Optionally, the value of the coefficient M8 is pre-configured or agreed upon by a protocol, or the value of the coefficient M8 is configured by a network device.

[0168] For example, for the NR RedCap terminal, the first eDRX acquisition cycle is defined as m1=M7*the maximum CN eDRX cycle supported by the RedCap terminal, where M7 is greater than or equal to 1, and the value of M7 is a predefined value or determined by system message configuration.

[0169] For example, for an NR RedCap terminal, the second eDRX acquisition cycle is defined as m2=M8*the maximum RAN eDRX cycle that the RedCap terminal can support, where M8 is greater than or equal to 1, and the value of M8 is a predefined value or determined by system message configuration.

[0170] Optionally, in Embodiment 4, the RRC idle state corresponds to the first eDRX acquisition cycle, and the RRC deactivated state corresponds to the first eDRX acquisition cycle and / or the second eDRX acquisition cycle.

[0171] That is, in Embodiment 4, for a UE in RRC deactivated state, when the CN eDRX cycle configured by the network for the UE is greater than the system message update cycle, the UE may determine the cycle for the UE to obtain updated system messages according to the RAN eDRX cycle or RAN DRX cycle configured by the network.

[0172] It should be noted that, in Embodiment 4, both NAS configuration of CN eDRX and RRC configuration of RAN eDRX are supported (for example, the maximum value of the RAN paging cycle configurable by the base station does not exceed 10.24s).

[0173] Optionally, in the embodiment of the present application, the system message update period can be determined according to the above formula 3. That is, the system message update period m=modificationPeriodCoeff*defaultPagingCycle, wherein modificationPeriodCoeff represents the system message update period coefficient indicated in the system message, and defaultPagingCycle represents the cell default paging cycle indicated in the system message.

[0174] Optionally, in some embodiments, the first eDRX acquisition period and / or the second eDRX acquisition period is a predefined value or is determined by system message configuration.

[0175] It should be noted that the "deactivated state" may also be referred to as the "non-activated state", which is not limited in this application.

[0176] Therefore, in the embodiment of the present application, the terminal in the RRC deactivated state can use the target period to obtain the system message update indication and the updated system message, and the network device can use the target period to send the system message update indication and the updated system message to the terminal in the RRC deactivated state, thereby optimizing the transmission of the system message. Further, in the embodiment of the present application, it can be ensured that the terminal device in the RRC deactivated state and the eDRX period is greater than the system message update period obtains the updated system message as timely as possible, and the terminal energy saving requirements can be well taken into account.

[0177] Combination of the above Figures 3 to 5 , describes in detail the method embodiment of the present application, and the following is combined with Figures 6 to 10 , the device embodiments of the present application are described in detail. It should be understood that the device embodiments and the method embodiments correspond to each other, and similar descriptions can refer to the method embodiments.

[0178] Figure 6 FIG. 3 shows a schematic block diagram of a terminal device 300 according to an embodiment of the present application. Figure 6 As shown, the terminal device 300 includes:

[0179] The communication unit 310 uses the target period to obtain the system message update indication and the updated system message;

[0180] Among them, the terminal device is in the radio resource control RRC deactivated state.

[0181] Optionally, the terminal device 300 further includes: a processing unit 320,

[0182] The processing unit 320 is configured to determine the target cycle according to discontinuous reception DRX cycle information and / or extended discontinuous reception eDRX cycle information.

[0183] Optionally, the processing unit 320 is specifically configured to:

[0184] In the case where the core network CN eDRX cycle is greater than the system message update cycle, and the radio access network RAN ​​DRX cycle is greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle; and / or,

[0185] When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0186] When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, the first eDRX acquisition cycle is determined to be the target cycle.

[0187] Optionally, the first eDRX acquisition cycle is an eDRX acquisition cycle configured for a terminal whose CN eDRX cycle is greater than a system message update cycle.

[0188] Optionally, the first eDRX acquisition cycle is the product of a maximum CN eDRX cycle supported by the terminal device and a coefficient M1, where M1≥1.

[0189] Optionally, the RRC idle state and the RRC deactivated state share the first eDRX acquisition cycle.

[0190] Optionally, the processing unit 320 is specifically configured to:

[0191] In a case where the CN eDRX cycle is greater than the system message update cycle, and the RAN DRX cycle is greater than the system message update cycle, the terminal device determines the second eDRX acquisition cycle as the target cycle; and / or,

[0192] When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0193] When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, the first eDRX acquisition cycle is determined to be the target cycle.

[0194] Optionally, the first eDRX acquisition cycle is an eDRX acquisition cycle configured for a terminal whose CN eDRX cycle is greater than a system message update cycle; and / or,

[0195] The second eDRX acquisition period is the product of the maximum RAN DRX period supported by the first network and a coefficient M2, where M2≥1.

[0196] Optionally, the first network is a Long Term Evolution LTE network or a New Radio NR network.

[0197] Optionally, the first eDRX acquisition cycle is the product of a maximum CN eDRX cycle supported by the terminal device and a coefficient M3, where M3≥1; and / or,

[0198] The second eDRX acquisition period is the product of the maximum RAN DRX period supported by the terminal device and a coefficient M4, where M4≥1.

[0199] Optionally, the RRC idle state corresponds to the first eDRX acquisition cycle, and the RRC deactivated state corresponds to the first eDRX acquisition cycle and / or the second eDRX acquisition cycle.

[0200] Optionally, the processing unit 320 is specifically configured to:

[0201] In the case that the CN eDRX period is less than or equal to the system message update period, the system message update period is determined to be the target period.

[0202] Optionally, the processing unit 320 is specifically configured to:

[0203] In the case that both the CN eDRX cycle and the RAN eDRX cycle are greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle; and / or,

[0204] In a case where the CN eDRX cycle is less than or equal to the system message update cycle, and / or the RAN eDRX cycle is less than or equal to the system message update cycle, the system message update cycle is determined to be the target cycle.

[0205] Optionally, the processing unit 320 is specifically configured to:

[0206] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle; and / or,

[0207] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0208] In the case that the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, the first eDRX acquisition cycle is determined to be the target cycle.

[0209] Optionally, the first eDRX acquisition cycle is the product of a maximum CN eDRX cycle supported by the terminal device and a coefficient M5, where M5≥1; or, the first eDRX acquisition cycle is the product of a maximum RAN eDRX cycle supported by the terminal device and a coefficient M6, where M6≥1.

[0210] Optionally, the RRC idle state and the RRC deactivated state share the first eDRX acquisition cycle.

[0211] Optionally, the processing unit 320 is specifically configured to:

[0212] In the case that both the CN eDRX cycle and the RAN eDRX cycle are greater than the system message update cycle, determining the second eDRX acquisition cycle as the target cycle; and / or,

[0213] In a case where the CN eDRX cycle is less than or equal to the system message update cycle, and / or the RAN eDRX cycle is less than or equal to the system message update cycle, the system message update cycle is determined to be the target cycle.

[0214] Optionally, the processing unit 320 is specifically configured to:

[0215] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, determining the second eDRX acquisition cycle as the target cycle; and / or,

[0216] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0217] In the case that the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, the first eDRX acquisition cycle is determined to be the target cycle.

[0218] Optionally, the first eDRX acquisition cycle is the product of a maximum CN eDRX cycle supported by the terminal device and a coefficient M7, where M7≥1.

[0219] Optionally, the RRC idle state corresponds to the first eDRX acquisition cycle.

[0220] Optionally, the second eDRX acquisition cycle is a product of a maximum RAN eDRX cycle supported by the terminal device and a coefficient M8, where M8≥1.

[0221] Optionally, the RRC deactivated state corresponds to the first eDRX acquisition cycle and / or the second eDRX acquisition cycle.

[0222] Optionally, the processing unit 320 is specifically configured to:

[0223] When the CN eDRX cycle is less than or equal to the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, the system message update cycle is determined to be the target cycle.

[0224] Optionally, the terminal device is a reduced capability terminal.

[0225] Optionally, the value of the coefficient is pre-configured or agreed upon by a protocol, or the value of the coefficient is configured by a network device.

[0226] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0227] It should be understood that the terminal device 300 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the terminal device 300 are respectively to implement Figure 3 For the sake of brevity, the corresponding process of the terminal device in the method 200 is not repeated here.

[0228] Figure 7 FIG. 4 shows a schematic block diagram of a network device 400 according to an embodiment of the present application. Figure 7 As shown, the network device 400 includes:

[0229] The communication unit 410 sends a system message update indication and an updated system message to the terminal device using a target period;

[0230] Among them, the terminal device is in the radio resource control RRC deactivated state.

[0231] Optionally, the network device 400 further includes: a processing unit 420,

[0232] The processing unit 420 is configured to determine the target cycle according to discontinuous reception DRX cycle information and / or extended discontinuous reception eDRX cycle information.

[0233] Optionally, the processing unit 420 is specifically configured to:

[0234] In the case where the core network CN eDRX cycle is greater than the system message update cycle, and the radio access network RAN ​​DRX cycle is greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle; and / or,

[0235] When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0236] When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, the first eDRX acquisition cycle is determined to be the target cycle.

[0237] Optionally, the first eDRX acquisition cycle is an eDRX acquisition cycle configured for a terminal whose CN eDRX cycle is greater than a system message update cycle.

[0238] Optionally, the first eDRX acquisition cycle is the product of a maximum CN eDRX cycle supported by the terminal device and a coefficient M1, where M1≥1.

[0239] Optionally, the RRC idle state and the RRC deactivated state share the first eDRX acquisition cycle.

[0240] Optionally, the processing unit 420 is specifically configured to:

[0241] In the case where the CN eDRX cycle is greater than the system message update cycle, and the RAN DRX cycle is greater than the system message update cycle, determining the second eDRX acquisition cycle as the target cycle; and / or,

[0242] When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0243] When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, the first eDRX acquisition cycle is determined to be the target cycle.

[0244] Optionally, the first eDRX acquisition cycle is an eDRX acquisition cycle configured for a terminal whose CN eDRX cycle is greater than a system message update cycle; and / or,

[0245] The second eDRX acquisition period is the product of the maximum RAN DRX period supported by the first network and a coefficient M2, where M2≥1.

[0246] Optionally, the first network is a Long Term Evolution LTE network or a New Radio NR network.

[0247] Optionally, the first eDRX acquisition cycle is the product of a maximum CN eDRX cycle supported by the terminal device and a coefficient M3, where M3≥1; and / or,

[0248] The second eDRX acquisition period is the product of the maximum RAN DRX period supported by the terminal device and a coefficient M4, where M4≥1.

[0249] Optionally, the RRC idle state corresponds to the first eDRX acquisition cycle, and the RRC deactivated state corresponds to the first eDRX acquisition cycle and / or the second eDRX acquisition cycle.

[0250] Optionally, the processing unit 420 is specifically configured to:

[0251] In the case that the CN eDRX period is less than or equal to the system message update period, the system message update period is determined to be the target period.

[0252] Optionally, the processing unit 420 is specifically configured to:

[0253] In the case that both the CN eDRX cycle and the RAN eDRX cycle are greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle; and / or,

[0254] In a case where the CN eDRX cycle is less than or equal to the system message update cycle, and / or the RAN eDRX cycle is less than or equal to the system message update cycle, the system message update cycle is determined to be the target cycle.

[0255] Optionally, the processing unit 420 is specifically configured to:

[0256] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle; and / or,

[0257] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0258] In the case that the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, the first eDRX acquisition cycle is determined to be the target cycle.

[0259] Optionally, the first eDRX acquisition cycle is the product of a maximum CN eDRX cycle supported by the terminal device and a coefficient M5, where M5≥1; or, the first eDRX acquisition cycle is the product of a maximum RAN eDRX cycle supported by the terminal device and a coefficient M6, where M6≥1.

[0260] Optionally, the RRC idle state and the RRC deactivated state share the first eDRX acquisition cycle.

[0261] Optionally, the processing unit 420 is specifically configured to:

[0262] In the case that both the CN eDRX cycle and the RAN eDRX cycle are greater than the system message update cycle, determining the second eDRX acquisition cycle as the target cycle; and / or,

[0263] In a case where the CN eDRX cycle is less than or equal to the system message update cycle, and / or the RAN eDRX cycle is less than or equal to the system message update cycle, the system message update cycle is determined to be the target cycle.

[0264] Optionally, the processing unit 420 is specifically configured to:

[0265] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, determining the second eDRX acquisition cycle as the target cycle; and / or,

[0266] In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or,

[0267] In the case that the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, the first eDRX acquisition cycle is determined to be the target cycle.

[0268] Optionally, the first eDRX acquisition cycle is the product of a maximum CN eDRX cycle supported by the terminal device and a coefficient M7, where M7≥1.

[0269] Optionally, the RRC idle state corresponds to the first eDRX acquisition cycle.

[0270] Optionally, the second eDRX acquisition cycle is a product of a maximum RAN eDRX cycle supported by the terminal device and a coefficient M8, where M8≥1.

[0271] Optionally, the RRC deactivated state corresponds to the first eDRX acquisition cycle and / or the second eDRX acquisition cycle.

[0272] Optionally, the processing unit 420 is specifically configured to:

[0273] When the CN eDRX cycle is less than or equal to the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, the system message update cycle is determined to be the target cycle.

[0274] Optionally, the terminal device is a reduced capability terminal.

[0275] Optionally, the value of the coefficient is pre-configured or agreed upon by a protocol, or the value of the coefficient is configured by a network device.

[0276] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0277] It should be understood that the network device 400 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the network device 400 are respectively to implement Figure 3 For the sake of brevity, the corresponding processes of the network device in the method 200 are not described in detail here.

[0278] Figure 8 It is a schematic structural diagram of a communication device 500 provided in an embodiment of the present application. Figure 8 The communication device 500 shown includes a processor 510, and the processor 510 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0279] Alternatively, if Figure 8 As shown, the communication device 500 may further include a memory 520. The processor 510 may call and run a computer program from the memory 520 to implement the method in the embodiment of the present application.

[0280] The memory 520 may be a separate device independent of the processor 510 , or may be integrated into the processor 510 .

[0281] Alternatively, if Figure 8 As shown, the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0282] The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include an antenna, and the number of the antennas may be one or more.

[0283] Optionally, the communication device 500 may specifically be a network device in an embodiment of the present application, and the communication device 500 may implement corresponding processes implemented by the network device in each method in the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0284] Optionally, the communication device 500 may specifically be a terminal device of an embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0285] Fig. 9 It is a schematic structural diagram of the device of an embodiment of the present application. Fig. 9 The device 600 shown includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0286] Alternatively, if Fig. 9 As shown, the apparatus 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0287] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0288] Optionally, the apparatus 600 may further include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0289] Optionally, the apparatus 600 may further include an output interface 640. The processor 610 may control the output interface 640 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0290] Optionally, the device can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding processes implemented by the network equipment in the various methods in the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0291] Optionally, the apparatus may be applied to a terminal device in an embodiment of the present application, and the apparatus may implement corresponding processes implemented by the terminal device in each method in an embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0292] Optionally, the device mentioned in the embodiments of the present application may also be a chip, for example, a system-on-chip, a system-on-chip, a chip system, or a system-on-chip chip.

[0293] Fig.10 is a schematic block diagram of a communication system 700 provided in an embodiment of the present application. Fig.10 As shown, the communication system 700 includes a terminal device 710 and a network device 720 .

[0294] Among them, the terminal device 710 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 720 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0295] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0296] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0297] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments 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 link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0298] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0299] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0300] Optionally, the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0301] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0302] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0303] Optionally, the computer program product can be applied to the terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0304] The embodiment of the present application also provides a computer program.

[0305] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0306] Optionally, the computer program can be applied to the terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0307] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0308] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0309] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0310] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0311] In addition, 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.

[0312] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. In view of such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0313] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that: include: The terminal device uses the target period to obtain the system message update indication and the updated system message; Wherein, the terminal device is in a radio resource control RRC deactivated state; The method further includes: the terminal device determining the target cycle according to discontinuous reception DRX cycle information and / or extended discontinuous reception eDRX cycle information; The terminal device determines the target cycle according to the DRX cycle information and / or the eDRX cycle information, including: In the case where the core network CN eDRX cycle is greater than the system message update cycle, and the radio access network RAN ​​DRX cycle is greater than the system message update cycle, the terminal device determines the first eDRX acquisition cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, the terminal device determines the system message update cycle as the target cycle; and / or, When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, the terminal device determines the first eDRX acquisition cycle as the target cycle; or, The terminal device determines the target cycle according to the DRX cycle information and / or the eDRX cycle information, including: In a case where the CN eDRX cycle is greater than the system message update cycle, and the RAN DRX cycle is greater than the system message update cycle, the terminal device determines the second eDRX acquisition cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, the terminal device determines the system message update cycle as the target cycle; and / or, When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, the terminal device determines the first eDRX acquisition cycle as the target cycle; or, The terminal device determines the target cycle according to the DRX cycle information and / or the eDRX cycle information, including: In a case where both the CN eDRX cycle and the RAN eDRX cycle are greater than the system message update cycle, the terminal device determines the first eDRX acquisition cycle as the target cycle, or the terminal device determines the second eDRX acquisition cycle as the target cycle; or, The terminal device determines the target cycle according to the DRX cycle information and / or the eDRX cycle information, including: In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, the terminal device determines the first eDRX acquisition cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, the terminal device determines the system message update cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, the terminal device determines the first eDRX acquisition cycle as the target cycle; or, The terminal device determines the target cycle according to the DRX cycle information and / or the eDRX cycle information, including: In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, the terminal device determines the second eDRX acquisition cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, the terminal device determines the system message update cycle as the target cycle; and / or, In the case that the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, the terminal device determines the first eDRX acquisition cycle as the target cycle.

2. The method according to claim 1, characterized in that The first eDRX acquisition cycle is an eDRX acquisition cycle configured for a terminal whose CN eDRX cycle is greater than a system message update cycle.

3. The method according to claim 1, characterized in that The first eDRX acquisition cycle is the product of the maximum CN eDRX cycle supported by the terminal device and a coefficient M1, where M1≥1.

4. The method according to any one of claims 1 to 3, characterized in that The RRC idle state and the RRC deactivated state share the first eDRX acquisition cycle.

5. The method according to claim 1, characterized in that The first eDRX acquisition cycle is an eDRX acquisition cycle configured for a terminal whose CN eDRX cycle is greater than a system message update cycle; and / or, The second eDRX acquisition period is the product of the maximum RAN DRX period supported by the first network and a coefficient M2, where M2≥1.

6. The method according to claim 5, characterized in that The first network is a Long Term Evolution LTE network or a New Radio NR network.

7. The method according to claim 1, characterized in that The first eDRX acquisition cycle is the product of the maximum CN eDRX cycle supported by the terminal device and a coefficient M3, where M3≥1; and / or, The second eDRX acquisition period is the product of the maximum RAN DRX period supported by the terminal device and a coefficient M4, where M4≥1.

8. The method according to any one of claims 1, 5 to 7, characterized in that: The RRC idle state corresponds to the first eDRX acquisition cycle, and the RRC deactivated state corresponds to the first eDRX acquisition cycle and / or the second eDRX acquisition cycle.

9. The method according to claim 1, characterized in that The first eDRX acquisition cycle is the product of a maximum CN eDRX cycle supported by the terminal device and a coefficient M5, where M5≥1; or, the first eDRX acquisition cycle is the product of a maximum RAN eDRX cycle supported by the terminal device and a coefficient M6, where M6≥1.

10. The method according to claim 9, characterized in that The RRC idle state and the RRC deactivated state share the first eDRX acquisition cycle.

11. The method according to claim 1, characterized in that The first eDRX acquisition cycle is the product of the maximum CN eDRX cycle supported by the terminal device and a coefficient M7, where M7≥1.

12. The method according to claim 11, characterized in that The RRC idle state corresponds to the first eDRX acquisition cycle.

13. The method according to claim 1, characterized in that The second eDRX acquisition cycle is the product of the maximum RAN eDRX cycle supported by the terminal device and a coefficient M8, where M8≥1.

14. The method according to claim 13, characterized in that The RRC deactivated state corresponds to the first eDRX acquisition cycle and / or the second eDRX acquisition cycle.

15. The method of claim 3, 7, 9, 11 or 13, wherein: The terminal device is a reduced capability terminal.

16. The method of claim 3, 5, 7, 9, 11 or 13, wherein: The value of the coefficient is pre-configured or agreed upon by a protocol, or the value of the coefficient is configured by a network device.

17. A wireless communication method, characterized in that: include: The network device sends a system message update indication and an updated system message to the terminal device using a target period; Wherein, the terminal device is in a radio resource control RRC deactivated state; The method further includes: the network device determining the target cycle according to discontinuous reception DRX cycle information and / or extended discontinuous reception eDRX cycle information; The network device determines the target cycle according to the DRX cycle information and / or the eDRX cycle information, including: In the case where the core network CN eDRX cycle is greater than the system message update cycle, and the radio access network RAN ​​DRX cycle is greater than the system message update cycle, the network device determines the first eDRX acquisition cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, the network device determines the system message update cycle as the target cycle; and / or, When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, the network device determines the first eDRX acquisition cycle as the target cycle; or, The network device determines the target cycle according to the DRX cycle information and / or the eDRX cycle information, including: In a case where the CN eDRX cycle is greater than the system message update cycle, and the RAN DRX cycle is greater than the system message update cycle, the network device determines the second eDRX acquisition cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, the network device determines the system message update cycle as the target cycle; and / or, When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, the network device determines the first eDRX acquisition cycle as the target cycle; or, The network device determines the target cycle according to the DRX cycle information and / or the eDRX cycle information, including: In a case where both the CN eDRX cycle and the RAN eDRX cycle are greater than the system message update cycle, the network device determines the first eDRX acquisition cycle as the target cycle, or the network device determines the second eDRX acquisition cycle as the target cycle; or, The network device determines the target cycle according to the DRX cycle information and / or the eDRX cycle information, including: In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, the network device determines the first eDRX acquisition cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, the network device determines the system message update cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, the network device determines the first eDRX acquisition cycle as the target cycle; or, The network device determines the target cycle according to the DRX cycle information and / or the eDRX cycle information, including: In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, the network device determines the second eDRX acquisition cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, the network device determines the system message update cycle as the target cycle; and / or, In the case that the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, the network device determines the first eDRX acquisition cycle as the target cycle.

18. The method according to claim 17, characterized in that The first eDRX acquisition cycle is an eDRX acquisition cycle configured for a terminal whose CN eDRX cycle is greater than a system message update cycle.

19. The method according to claim 17, characterized in that The first eDRX acquisition cycle is the product of the maximum CN eDRX cycle supported by the terminal device and a coefficient M1, where M1≥1.

20. The method according to any one of claims 17 to 19, characterized in that The RRC idle state and the RRC deactivated state share the first eDRX acquisition cycle.

21. The method of claim 17, wherein: The first eDRX acquisition cycle is an eDRX acquisition cycle configured for a terminal whose CN eDRX cycle is greater than a system message update cycle; and / or, The second eDRX acquisition period is the product of the maximum RAN DRX period supported by the first network and a coefficient M2, where M2≥1.

22. The method according to claim 21, characterized in that The first network is a Long Term Evolution LTE network or a New Radio NR network.

23. The method of claim 17, wherein: The first eDRX acquisition cycle is the product of the maximum CN eDRX cycle supported by the terminal device and a coefficient M3, where M3≥1; and / or, The second eDRX acquisition period is the product of the maximum RAN DRX period supported by the terminal device and a coefficient M4, where M4≥1.

24. The method according to any one of claims 17, 21 to 23, characterized in that The RRC idle state corresponds to the first eDRX acquisition cycle, and the RRC deactivated state corresponds to the first eDRX acquisition cycle and / or the second eDRX acquisition cycle.

25. The method of claim 17, wherein: The first eDRX acquisition cycle is the product of a maximum CN eDRX cycle supported by the terminal device and a coefficient M5, where M5≥1; or, the first eDRX acquisition cycle is the product of a maximum RAN eDRX cycle supported by the terminal device and a coefficient M6, where M6≥1.

26. The method of claim 25, wherein: The RRC idle state and the RRC deactivated state share the first eDRX acquisition cycle.

27. The method of claim 17, wherein: The first eDRX acquisition cycle is the product of the maximum CN eDRX cycle supported by the terminal device and a coefficient M7, where M7≥1.

28. The method of claim 27, wherein: The RRC idle state corresponds to the first eDRX acquisition cycle.

29. The method of claim 17, wherein: The second eDRX acquisition cycle is the product of the maximum RAN eDRX cycle supported by the terminal device and a coefficient M8, where M8≥1.

30. The method of claim 29, wherein: The RRC deactivated state corresponds to the first eDRX acquisition cycle and / or the second eDRX acquisition cycle.

31. The method of claim 19, 23, 25, 27 or 29, wherein: The terminal device is a reduced capability terminal.

32. The method of claim 19, 21, 23, 25, 27 or 29, wherein: The value of the coefficient is pre-configured or agreed upon by a protocol, or the value of the coefficient is configured by a network device.

33. A terminal device, characterized in that: include: A communication unit, used to obtain a system message update indication and an updated system message using a target period; Wherein, the terminal device is in a radio resource control RRC deactivated state; The terminal device further includes: a processing unit, configured to determine the target cycle according to discontinuous reception DRX cycle information and / or extended discontinuous reception eDRX cycle information; Wherein, the processing unit is specifically used for: In the case where the core network CN eDRX cycle is greater than the system message update cycle, and the radio access network RAN ​​DRX cycle is greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle; and / or, When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or, When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, determining the first eDRX acquisition cycle as the target cycle; or, The processing unit is specifically used for: In the case where the CN eDRX cycle is greater than the system message update cycle, and the RAN DRX cycle is greater than the system message update cycle, determining the second eDRX acquisition cycle as the target cycle; and / or, When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or, When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, determining the first eDRX acquisition cycle as the target cycle; or, The processing unit is specifically used for: When both the CN eDRX cycle and the RAN eDRX cycle are greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle, or determining the second eDRX acquisition cycle as the target cycle; or, The processing unit is specifically used for: In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle; and / or, In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, determining the first eDRX acquisition cycle as the target cycle; or, The processing unit is specifically used for: In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, determining the second eDRX acquisition cycle as the target cycle; and / or, In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or, In the case that the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, the first eDRX acquisition cycle is determined to be the target cycle.

34. A network device, characterized in that: include: A communication unit, used to send a system message update indication and an updated system message to a terminal device using a target period; Wherein, the terminal device is in a radio resource control RRC deactivated state; The network device further includes: a processing unit, configured to determine the target cycle according to discontinuous reception DRX cycle information and / or extended discontinuous reception eDRX cycle information; Wherein, the processing unit is specifically used for: In the case where the core network CN eDRX cycle is greater than the system message update cycle, and the radio access network RAN ​​DRX cycle is greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle; and / or, When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or, When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, determining the first eDRX acquisition cycle as the target cycle; or, The processing unit is specifically used for: In the case where the CN eDRX cycle is greater than the system message update cycle, and the RAN DRX cycle is greater than the system message update cycle, determining the second eDRX acquisition cycle as the target cycle; and / or, When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or, When the CN eDRX cycle is greater than the system message update cycle and the RAN DRX cycle is not configured at the terminal device, determining the first eDRX acquisition cycle as the target cycle; or, The processing unit is specifically used for: When both the CN eDRX cycle and the RAN eDRX cycle are greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle, or determining the second eDRX acquisition cycle as the target cycle; or, The processing unit is specifically used for: In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, determining the first eDRX acquisition cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, determining the first eDRX acquisition cycle as the target cycle; or, The processing unit is specifically used for: In the case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is greater than the system message update cycle, determining the second eDRX acquisition cycle as the target cycle; and / or, In a case where the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is less than or equal to the system message update cycle, determining the system message update cycle as the target cycle; and / or, In the case that the CN eDRX cycle is greater than the system message update cycle and the RAN eDRX cycle is not configured at the terminal device, if the RAN DRX cycle is not configured at the terminal device, the first eDRX acquisition cycle is determined to be the target cycle.

35. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 16.

36. A network device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 17 to 32.

37. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 16.

38. A chip, characterized in that: It comprises: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 17 to 32.

39. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 16.

40. A computer-readable storage medium, characterized in that Used to store a computer program, the computer program causing a computer to execute the method according to any one of claims 17 to 32.

41. A computer program product, characterized in that The method comprises computer program instructions which cause a computer to execute the method as claimed in any one of claims 1 to 16.

42. A computer program product, characterized in that Comprising computer program instructions causing a computer to perform the method as claimed in any one of claims 17 to 32.

Images