WO2021258962A1 - 数据下发方法、设备和存储介质 - Google Patents

数据下发方法、设备和存储介质 Download PDF

Info

Publication number
WO2021258962A1
WO2021258962A1 PCT/CN2021/095878 CN2021095878W WO2021258962A1 WO 2021258962 A1 WO2021258962 A1 WO 2021258962A1 CN 2021095878 W CN2021095878 W CN 2021095878W WO 2021258962 A1 WO2021258962 A1 WO 2021258962A1
Authority
WO
WIPO (PCT)
Prior art keywords
drx
data
gnb
enb
information
Prior art date
Application number
PCT/CN2021/095878
Other languages
English (en)
French (fr)
Inventor
徐洪斌
徐军领
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP21828037.8A priority Critical patent/EP4175406A4/en
Publication of WO2021258962A1 publication Critical patent/WO2021258962A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a power saving command
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H04W52/028—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer

Definitions

  • the present disclosure relates to the field of communication technologies, and in particular, to a data distribution method, device, and storage medium.
  • SA independent networking
  • NSA non-independent networking
  • EN-DC E-UTRA-NR Dual Connectivity
  • the current mainstream NSA topology at home and abroad is the option3x structure, which implements data offloading according to the EN-DC protocol standard formulated by 3GPP.
  • the 5G flow control module distributes data to the eNB RLC and gNB RLC, it directly delivers the data to the eNB RLC and/or gNB RLC, so that the eNB RLC and/or gNB RLC will receive the data.
  • the received data is delivered to the associated UE.
  • the UE cannot receive data at any time, that is, eNB RLC and/or gNB RLC may not be able to send data after receiving, resulting in negative gain. , And then affect the system to affect the entire TCP business.
  • the main purpose of the embodiments of the present disclosure is to propose a data distribution method and storage medium, which aims to avoid the occurrence of the negative gain phenomenon and ensure the timeliness of the data.
  • the embodiments of the present disclosure provide a data distribution method.
  • the method includes the following steps: according to the DRX information of the user equipment UE, determine the DRX status of the fourth-generation evolved base station eNB and the 5G base station gNB respectively. Information; the data receiving end is determined according to the DRX status information, and the data to be synchronized is sent to the data receiving end to instruct the data receiving end to send the synchronization data to the UE, where the The data receiving end is one or both of the eNB and the gNB.
  • the embodiments of the present disclosure also propose a data distribution device, the device includes a memory and a processor; the memory is configured to store a computer program; the processor is configured to execute the computer program and When the computer program is executed, the steps of the data distribution method described above are realized.
  • the present disclosure provides a storage medium configured as a computer-readable storage, the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors, In order to realize the steps of the aforementioned data distribution method.
  • the data distribution method, device and storage medium proposed in the present disclosure acquire the DRX information of the user equipment UE when receiving the data synchronization instruction, and then determine whether the current corresponding data receiving end is an eNB or a gNB according to the obtained DRX information, Furthermore, after the data receiving end is determined, the data to be synchronized is received, and the data receiving end is instructed to deliver the received data to be synchronized to the user equipment UE.
  • the flow control OMG module PDCP of the gNB requests the data volume, and the data information is sent by selecting the appropriate and active end to avoid the inconsistency of the status on both sides.
  • the negative gain phenomenon ensures the timeliness of data.
  • FIG. 1 is a schematic flowchart of a data distribution method provided by an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of the DRX principle provided by an embodiment of the disclosure.
  • FIG. 3 is a schematic flowchart of the steps of determining DRX status information provided by an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart of a typical long and short period DRX provided by an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of the steps of determining DRX status information in another embodiment of the present disclosure
  • FIG. 6 is a schematic block diagram of the structure of a data distribution device provided by an embodiment of the disclosure.
  • Fig. 1 is a schematic flow chart of a method for processing subscription messages of an IP multimedia subsystem according to an embodiment of the present disclosure. The method includes the following steps:
  • Step S101 According to the DRX information of the user equipment UE, determine the DRX state information respectively corresponding to the fourth-generation evolved base station eNB and the 5G base station gNB.
  • Discontinuous Reception is discontinuous reception. This method allows the user equipment UE to periodically enter the sleep state at certain times without monitoring the PDCCH subframes, but when it needs to be monitored, it will start from the sleep state. Wake up and enter the active state, so that the UE can achieve the purpose of saving power.
  • a typical DRX cycle (DRX cycle) can be as shown in Figure 2.
  • a DRX cycle consists of "On Duration” and "Opportunity for DRX".
  • the UE monitors and receives PDCCH subframes;
  • the UE will not monitor and receive PDCCH subframes.
  • the system can configure different cycles for the UE according to different business scenarios.
  • the short cycle (short DRX cycle) or the long cycle (long DRX cycle) emerges accordingly, such as VOIP services.
  • VOIP services such as VOIP services.
  • the voice codec usually sends a VOIP packet in 20ms, then a short DRX cycle with a length of 20ms can be configured, and a long DRX cycle can be configured for a longer silent period during a voice call.
  • the DRX information is obtained to determine the DRX status of the eNB and gNB, and then how to issue the data is determined according to the obtained DRX status.
  • the DRX status information corresponding to the eNB and the gNB will be determined according to the DRX information of the user equipment UE.
  • the DRX status information includes the dormant state and the active state, that is, when data synchronization is required. Firstly, determine the DRX status information corresponding to the eNB and the gNB respectively, and then determine how to synchronize the data information according to the obtained DRX status information.
  • each is configured with its corresponding DRX configuration. Due to the difference in DRX configuration, the DRX status of its own determined according to the UE’s DRX information will also be different. That is, when connecting and communicating with the UE, there will be respective corresponding data delivery states at the same time.
  • the flow control reporting module RLC included in the eNB and the gNB is controlled to obtain the user equipment.
  • DRX information of the UE when determining how to perform data delivery and synchronization, it is necessary to obtain the relevant data information of the UE. Therefore, when the data synchronization instruction is received, the flow control reporting module RLC included in the eNB and the gNB is controlled to obtain the user equipment. DRX information of the UE.
  • a corresponding communication connection is established between the UE, the eNB and the gNB, and the eNB and the gNB deliver the data traffic packets that need to be delivered to the UE according to the actual situation, so that the UE can respond to different services.
  • Both eNB and gNB include their corresponding flow control module PDCP and flow control reporting module RLC, and when the data flow packet is sent, it is delivered through the flow control module PDCP on the gNB side.
  • the flow control reporting module first receives the data flow packet sent by the flow control module, and then delivers the received data flow packet to the UE.
  • the flow control module does not know the status of the RLC corresponding to each of the eNB and gNB (which may be an active period or a dormant period), it must first determine the DRX status of the eNB and gNB compared to the UE. The status is determined according to the DRX information of the UE. Therefore, it is necessary to control the flow control reporting modules corresponding to the eNB and gNB to obtain the DRX information of the UE, and then determine which end is currently selected to implement the data flow according to the difference in the DRX configuration configured by each Delivery of the package.
  • the DRX configuration includes: on_duration duration, drx-Inactivity duration, long/short cycle duration, drxShortCycle duration, drxStartOffset, etc., which are not examples here. Because of the difference in DRX configuration, eNB and gNB will have different state information at the same time.
  • Step S102 Determine the data receiving end according to the DRX status information, and deliver the data to be synchronized to the data receiving end, so as to instruct the data receiving end to deliver the synchronization data to the UE.
  • the data receiving end is one or both of the eNB and the gNB.
  • the data to be synchronized will be controlled to be sent to the data receiving end, and then Instruct the data receiving end to deliver the received data to be synchronized to the UE.
  • the DRX status information of the eNB and gNB can be activated or dormant.
  • the appropriate data receiving end can be selected to send the data.
  • the data receiving end when the data receiving end is determined, it includes: if the first DRX state information is in a dormant state and the second DRX state information is in an active state, then determining that the gNB is the data receiving end ; If the first DRX state information is in the active state, and the second DRX state information is in the dormant state, then it is determined that the eNB is the data receiving end; if the first DRX state information is the same as the second If the DRX status information is in an active state, it is determined that the gNB and the eNB are the data receiving ends.
  • the DRX status information When the DRX status information is in the active state, it is determined that the data can be received and sent, regardless of whether it is the eNB or the gNB at this time, the data can be received and sent. At the same time, when both are in the active state, how to receive and deliver data can be determined according to the actual situation, for example, according to the respective air interface capabilities of the eNB and gNB, that is, the data reception and delivery capabilities.
  • the eNB and the gNB when receiving and sending data, are not only connected with the current UE, but also connected with several other UEs to meet the service requirements of different UEs. Therefore, when receiving and sending data, it is not possible to directly use all air interfaces of the eNB or gNB for data receiving and sending, but to realize timely data receiving and sending according to the current air interface capabilities of the eNB and gNB.
  • the data receiving end When determining the data receiving end for data receiving and sending, if there is only one port that can be set to receive and send data at the current moment, there will be no choice for the data sending end, but the current The end that can be used receives and sends data.
  • the corresponding air interface capabilities of eNB and gNB When it is determined that both eNB and gNB can be used as data receivers to receive and send data, the corresponding air interface capabilities of eNB and gNB will be used to determine the amount of data to be sent respectively corresponding to eNB and gNB, so that eNB and gNB The data is received and sent according to the respective corresponding data delivery.
  • the data to be synchronized currently needs to be synchronized is 200 Mbps
  • the current air interface capabilities of gNB and eNB are 1.0 Gbps (equal to 1024 Mbps) and 100 Mbps, respectively.
  • the appropriate allocation method can be selected according to the respective air interface capabilities, such as gNB and eNB All are 100Mbps, or it can be only applicable to gNB, that is, gNB is 200Mbps, or other allocation methods.
  • gNB has faster data processing capabilities, when receiving and sending data based on the air interface capabilities, gNB can be selected as the data processing end for data receiving and sending, which is the corresponding time at this time.
  • the data traffic packet distribution method can be 200Mbps for gNB and 0 for eNB, but it does not mean that it can only be in this way.
  • FIG. 3 is a schematic flowchart of the steps of determining DRX status information provided by an embodiment of the present disclosure.
  • determining the DRX state information corresponding to the fourth-generation evolved base station eNB and the 5G base station gNB respectively includes step S301 to step S302.
  • Step S301 Acquire the frame number and subframe number of the current frame included in the DRX information.
  • the relevant information contained in the DRX information will be identified and acquired, so as to determine the DRX status information corresponding to the eNB and the gNB. Therefore, after obtaining the DRX information, the frame number and subframe number of the current frame contained in the DRX information are obtained, and then the DRX status information corresponding to the eNB and the gNB is determined according to the obtained frame number and subframe number of the current frame.
  • a long and short cycle DRX process is shown in Figure 4.
  • the short cycle corresponds to ShortDrxCycle
  • the long cycle corresponds to LongDrxCycle. It contains several subframes and exists in the corresponding system frame. Each subframe is up to 1ms.
  • FDD Frequency-division Duplex
  • TDD Time-division Duplex
  • the number range of the system frame is 0-1023
  • the number range of subframes within a system frame is 0-9
  • Each system frame is 10ms long and consists of 10 subframes.
  • the UE enters Long DRX cycle, and the long cycle ends at time (2, 9), and the UE receives the PDCCH subframe at time (3, 0), so the drx-inactivity timer is restarted.
  • the status of the UE will continue to change, and since the DRX configuration of a system/device is fixed, it is determined that it is better than a certain system.
  • the device it can be determined whether it is in the active state or the dormant state at the current moment according to some of the currently obtained parameters. For example, the time (0, 8) is in the dormant state, and the time (2, 1) is in the active state.
  • the frame number and subframe number of the current frame contained in the DRX information are obtained, and then the frame number and subframe number of the current frame are determined according to all of them.
  • the main scenario for the distribution is the long cycle.
  • the DRx state corresponding to the eNB and gNB it is actually to determine whether the eNB and gNB have entered the active state under the UE’s DRX information. Therefore, the current frame and subframe location will be determined at this time. Whether the corresponding moment is in the corresponding active state.
  • Step S302 Determine the DRX state information corresponding to the eNB and the gNB respectively according to the frame number of the current frame and the subframe number, where the DRX state information includes a dormant state and an active state.
  • the DRX status information corresponding to each of the eNB and gNB will be determined according to the respective DRX configuration of the eNB and gNB, and then appropriate data receiving and sending methods will be selected to implement data offload processing.
  • drxOffset [(SFN ⁇ 10)+subFrameNumber]%longDRX_Cycle;
  • drxOffset is the calculation result corresponding to the time corresponding to the current frame and the subframe
  • SFN is the frame number of the current frame
  • subFrameNumber is the current corresponding subframe number
  • longDRX_Cycle is the long DRX cycle
  • the cycle unit is milliseconds (ms).
  • the corresponding drxOffset is obtained by taking the modulus of longDRX_Cycle.
  • drxOffset when determining whether it is in the active state, compare the drxOffset with the corresponding drxStartOffset. When the two are equal, the active state is determined, but it is not only when the two are equal that the active state is entered.
  • the active moment in the DRX cycle is not only one frame and the corresponding moment of the subframe, so a range of values in the active state can be determined.
  • the drxOffset is within this range, it means it is in the active state, otherwise it is in the dormant state.
  • drxStartOffset is the start value of the DRX cycle, and the value range is (0, longDRX_Cycle-1).
  • the drxStartOffset is 9
  • the on_Duration is 10
  • the DRX configuration information of the eNB and gNB is obtained to perform corresponding calculation and processing.
  • FIG. 5 is a schematic flowchart of the steps of determining DRX status information in another embodiment of the present disclosure.
  • determining the DRX state information corresponding to the eNB and the gNB respectively according to the frame number of the current frame and the subframe number includes step S501 to step S503.
  • Step S501 Acquire first DRX configuration information and second DRX configuration information respectively corresponding to the eNB and the gNB;
  • Step S502 Determine first DRX state information corresponding to the eNB according to the frame number of the current frame, the subframe number, and the first DRX configuration information;
  • Step S503 Determine second DRX state information corresponding to the gNB according to the frame number of the current frame, the subframe number, and the second DRX configuration information.
  • the eNB when determining the DRX status information corresponding to the eNB and the gNB, in addition to obtaining the DRX information of the UE, it also needs to be determined according to the DRX configuration information corresponding to the eNB and the gNB. Therefore, the eNB will be obtained at this time. And the first DRX configuration information and the second DRX configuration information respectively corresponding to the gNB, and then determine the first DRX status information corresponding to the eNB according to the obtained frame number, subframe number, and first DRX configuration information of the current frame, and The second DRX state information corresponding to the gNB is determined according to the obtained frame number, subframe number, and second DRX configuration information of the current frame.
  • when determining the DRX status information corresponding to the eNB according to the frame number and subframe number of the current frame it includes: acquiring the first DRX cycle and the first virtual activation period included in the first DRX configuration information ; According to the frame number of the current frame, the subframe number and the first DRX cycle, determine whether it is currently in the first virtual active period; if it is determined to be in the first virtual active period, then determine The first DRX state information is an active state; if it is determined that it is not within the first virtual active period, it is determined that the first DRX state information is a dormant state.
  • the first DRX cycle and the recorded first activation period from the first DRX configuration information, where the first DRX cycle is the long period corresponding to the eNB, and then, according to the obtained
  • the frame number, subframe number, and first period of the current frame are calculated according to the calculation formula mentioned above, and the corresponding calculation result is obtained. Then, the calculated result is compared with the first activation period to determine the corresponding eNB The DRX status.
  • the calculated drxOffset is compared with the first virtual active period, and when the drxOffset is in the first virtual active period, it is determined that the first DRX state information of the eNB is the active state, otherwise it is the dormant state.
  • DRX is configured as longDRX_Cycle as 320ms
  • drxStartOffset is configured as 19, and on_duration is 15ms
  • step S502 and step S503 there is no specific sequence between step S502 and step S503. It can be step S502 before step S503, or step S503 before step S502, or step S502 and step S503 occur at the same time, which is not limited. .
  • the method when determining the DRX status information corresponding to the gNB according to the frame number and the subframe number of the current frame, includes: acquiring the second DRX cycle and the second activation period included in the second DRX configuration information; According to the frame number of the current frame, the subframe number, and the second DRX cycle, determine whether it is currently in the second active period; if it is determined to be in the second active period, determine the first 2.
  • the DRX state information is an active state; if it is determined that it is not within the second active period, it is determined that the second DRX state information is a dormant state.
  • the process is the same as the process of obtaining the first status information corresponding to the eNB, except that the judgment object is changed from the eNB to the gNB, and the frame number and subframe number of the current frame are used to determine whether it is in the second activation period corresponding to the gNB. If it is determined that it is in the second active period, it is determined that the second DRX state information is the active state, anyway, it is the dormant state.
  • the data traffic packet that needs to be sent can be sent to the eNB and/or gNB in advance before the data is sent, and then the eNB and/or gNB can enter In the activated state, the data traffic packet that needs to be delivered can be delivered to the corresponding UE as soon as possible.
  • the next activation state can be predicted, so that the data traffic packet can be sent to the eNB and/or gNB in advance when there is a data traffic packet to be sent.
  • the data traffic packet that needs to be delivered is obtained in the flow control module PDCP of the gNB, and stored in the flow control reporting module RLC of the gNB and/or eNB.
  • the data sent by PDCP to RLC can be sent to the UE in time.
  • the prediction is made 10 subframes in advance, it is calculated according to the above-described DRX state calculation formula The results will be pre-judged as follows.
  • drxOffsetFinal drxOffset-10, drxOffset ⁇ 10;
  • drxOffsetFinal longDRX_Cycle-10+drxOffset, drxOffset ⁇ 10.
  • drxOffsetFinal is the time when the prediction is made, and the prediction is for the next DRX cycle. Therefore, using the above method, after determining the state information in the current DRX cycle, the actual state can be used to determine the next DRX cycle. The time when RLC makes a data request to PDCP.
  • the DRX information of the user equipment UE is obtained, and then according to the obtained DRX information, it is determined that the current corresponding data receiving end is an eNB It is still the gNB, and then after determining the data receiving end, it receives the data to be synchronized and instructs the data receiving end to deliver the received data to be synchronized to the user equipment UE.
  • the flow control OMG module PDCP of the gNB requests the data volume, and the data information is sent by selecting the appropriate and active end to avoid the inconsistency of the status on both sides.
  • the negative gain phenomenon ensures the timeliness of data.
  • FIG. 6 is a schematic block diagram of the structure of a data distribution device provided by an embodiment of the present disclosure.
  • the electronic device may be a mobile phone, a tablet, a notebook, a desktop computer, a TV, a special input device, a cash machine, and the like.
  • the device also includes a processor and a memory, and the memory is configured to store a computer program.
  • the processor is configured to execute the computer program and, when executing the computer program, implement any one of the data distribution methods provided in the embodiments of the present disclosure.
  • the processor may be a central processing unit (Central Processing Unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), and application specific integrated circuits (Application Specific Integrated Circuits). Circuit, ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the embodiments of the present disclosure also provide a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor realizes the functions provided by the embodiments of the present disclosure. Any network deployment method of an autonomous domain system AS.
  • Computer-readable storage medium includes volatile and non-volatile properties implemented in any method or technology configured to store information (such as computer-readable instructions, data structures, program modules, or other data). Volatile, removable and non-removable media.
  • Computer-readable storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, Or it can be set as any other medium that stores desired information and can be accessed by a computer.
  • a communication medium usually contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium. .
  • the computer-readable storage medium may be the internal storage unit of the electronic device described in the foregoing embodiment, such as the hard disk or memory of the electronic device.
  • the computer-readable storage medium may also be an external storage device of the electronic device, such as a plug-in hard disk equipped on the electronic device, a smart memory card (Smart Media Card, SMC), or Secure Digital (SD) ) Card, Flash Card, etc.
  • the electronic device and computer-readable storage medium provided by the foregoing embodiments display at least two virtual keyboards in different display areas on the display screen when the user inputs information, so that information can be input through the at least two virtual keyboards;
  • the software predicts the difficulty of inputting information by monitoring the state of the sensor, which enhances the security of information input.

Landscapes

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

Abstract

本公开公开一种数据下发方法、设备和存储介质，属于通讯技术领域。该方法包括：根据用户设备UE的DRX信息，确定***演进型基站eNB与5G基站gNB分别对应的DRX状态信息；根据所述DRX状态信息确定数据接收端，并将待同步数据下发至所述数据接收端，以指示所述数据接收端将所述同步数据下发至所述UE，其中，所述数据接收端为所述eNB与所述gNB中的一个或者两个。本公开的技术方案，其可实现避免负增益现象的产生，保证数据的及时性。

Description

数据下发方法、设备和存储介质 技术领域
本公开涉及通讯技术领域，尤其涉及一种数据下发方法、设备和存储介质。
背景技术
5G NR的部署方式有两种，分别为独立组网(SA)和非独立组网(NSA)，其中，NSA借助于EN-DC(E-UTRA-NR Dual Connectivity)技术来实现，可利用现存4G LTE基站，迅速完成5G站点的搭建。
目前国内外主流NSA拓扑结构为option3x结构，根据3GPP制定的关于EN-DC的协议标准实现数据分流。具体地，在EN-DC分流时，5G流控模块向eNB RLC和gNB RLC分发数据时，直接将数据下发至eNB RLC和/或gNB RLC，以使得eNB RLC和/或gNB RLC将所接收到的数据下发至相关联的UE端。
但是，由于UE具有DRX机制，使得UE并不是在任何时刻都可以进行数据的接收，也就是eNB RLC和/或gNB RLC可能存存在数据接收之后并不能进行下发的情况，使得出现负增益现象，进而影响***影响整个TCP业务。
因此，现在亟需一种可以在及时进行数据下发的同时降低负增益产生的数据下发方法。
发明内容
本公开实施例的主要目的在于提出一种数据下发方法和存储介质，旨在避免负增益现象的产生，保证数据的及时性。
为实现上述目的，本公开实施例提供了一种数据下发方法，所述方法包括以下步骤：根据用户设备UE的DRX信息，确定***演进型基站eNB与5G基站gNB分别对应的DRX状态信息；根据所述DRX状态信息确定数据接收端，并将待同步数据下发至所述数据接收端，以指示所述数据接收端将所述同步数据下发至所述UE，其中，所述数据接收端为所述eNB与所述gNB中的一个或者两个。
为实现上述目的，本公开实施例还提出了一种数据下发设备，所述设备包括存储器以及处理器；所述存储器设置为存储计算机程序；所述处理器，设置为执行所述计算机程序并在执行所述计算机程序时实现如前述所述的数据下发方法的步骤。
为实现上述目的，本公开提供了一种存储介质，设置为计算机可读存储，所述存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现前述所述的数据下发方法的步骤。
本公开提出的数据下发方法、设备和存储介质，在接收到数据同步指令时，获取用户设备UE的DRX信息，然后根据所得到的DRX信息确定当前所对应的数据接收端是eNB还是gNB，进而在确定数据接收端之后，接收待同步数据，并指示数据接收端将所接收到的待同步数据下发至用户设备UE。实现了在数据同步时，根据当前UE的DRX状态向gNB的流控OMG模块 PDCP进行数据量的请求，通过选择合适的且处于激活状态的一端进行数据信息的下发，避免两侧状态不一致导致的负增益现象，保证数据的及时性。
附图说明
为了更清楚地说明本公开实施例技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本公开一实施例提供的一种数据下发方法的流程示意图；
图2为本公开一实施例提供的DRX原理示意图；
图3为本公开一实施例提供的确定DRX状态信息的步骤的流程示意图；
图4为本公开一实施例提供一个典型的长短周期DRX的流程示意图；
图5为本公开另一个实施例中确定DRX状态信息的步骤的流程示意图；
图6为本公开实施例提供的一种数据下发设备的结构示意性框图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
附图中所示的流程图仅是示例说明，不是必须包括所有的内容和操作/步骤，也不是必须按所描述的顺序执行。例如，有的操作/步骤还可以分解、组合或分合并，因此实际执行的顺序有可能根据实际情况改变。
如图1所示，图1为本公开一实施例提供的一种IP多媒体子***的订阅消息处理方法的流程示意图，该方法包括以下步骤：
步骤S101、根据用户设备UE的DRX信息，确定***演进型基站eNB与5G基站gNB分别对应的DRX状态信息。
DRX，英文全称为Discontinuous Reception，即不连续接收，这种方法可以让用户设备UE周期性的在某些时候进入睡眠状态，不去监听PDCCH子帧，而需要监听的时候，则从睡眠状态中唤醒进入激活状态，进而这样就可以使UE达到省电的目的。
其中，一个典型的DRX周期(DRX cycle)可以如图2所示，一个DRX cycle由“On Duration”和“Opportunity for DRX”组成，在“On Duration”时间内，UE监听并接收PDCCH子帧；在“Opportunity for DRX”时间内，UE将不会监听和接收PDCCH子帧。
另外，对于一个DRX周期而言，***可以根据不同的业务场景给UE配置不同的周期，顺应而生的便是短周期(short DRX cycle)或者长周期(long DRX cycle)，比如在进行VOIP业务时，语音编解码器通常20ms发送一个VOIP包，那么就可以配置长度为20ms的DRX短周期，而在语音通话期间较长的静默期，就可以配置DRX长周期。
但是，针对于长周期和短周期而言，由于短周期本身具有快速响应下行数据传输的特点，因此在进行数据下发时，更多的是针对长周期而言，通过在长周期内对UE的DRX信息进行获取来确定eNB和gNB的DRX状态，进而根据所得到的DRX状态确定如何进行数据的下发。
因此，在有数据需要进行同步时，将根据用户设备UE的DRX信息确定eNB与gNB所分别对应的DRX状态信息，其中，DRX状态信息包括休眠状态和激活状态，也就是在需要进行数据同步时，首先确定eNB与gNB分别对应的DRX状态信息，然后根据所得到的DRX状态信息确定如何进行数据信息的同步。
在实际应用中，对于4G基站和5G基站而言，各自配置有各自所对应的DRX配置，由于DRX配置的不同，使得在根据UE的DRX信息所确定的自身的DRX状态也会有所不同，也就是在与UE端的连接和通信时，在相同时刻也会有着各自对应的数据下发状态。
在一实施例中，在确定如何进行数据下发和同步时，需要获取UE的相关数据信息，因此在接收到数据同步指令时，控制eNB和gNB分别所包含的流控上报模块RLC获取用户设备UE的DRX信息。
实际上，UE与eNB和gNB之间均建立有相应的通讯连接，eNB和gNB根据实际情况将需要进行下发的数据流量包下发至UE，使得在UE上响应不同的业务。对于eNB和gNB均包含有各自对应的流控模块PDCP和流控上报模块RLC，而在进行数据流量包的下发时，是通过gNB侧的流控模块PDCP来实现下发的，在进行数据的下发时，流控上报模块首先接收流控模块所发送的数据流量包，然后将所接收到的数据流量包下发给UE。但是由于流控模块并不知道eNB和gNB中各自所对应的RLC的状态(可能是激活期，也可能是休眠期)，因此，首先要确定eNB和gNB相较于UE的DRX状态，而DRX状态是根据UE的DRX信息而确定的，故，需要控制eNB和gNB分别对应的流控上报模块获取UE的DRX信息，然后根据各自所配置的DRX配置的不同，确定当前选择哪一端实现数据流量包的下发。
一般情况下，DRX配置包括有：on_duration时长、drx-Inactivity时长、长/短周期的时长、drxShortCycle时长、drxStartOffset等，在此不一一举例。因为DRX配置的不同，使得eNB和gNB在相同时刻会出现状态信息不同的情况。
步骤S102、根据所述DRX状态信息确定数据接收端，并将待同步数据下发至所述数据接收端，以指示所述数据接收端将所述同步数据下发至所述UE，其中，所述数据接收端为所述eNB与所述gNB中的一个或者两个。
通过确定eNB和gNB分别对应的DRX状态信息，选择合适的设置为进行数据下发的数据接收端，在确定了数据接收端之后，将会控制将待同步数据下发至数据接收端，接着以指示数据接收端将所接收到的待同步数据下发至UE。
在根据UE的DRX信息确定eNB和gNB所分别对应的DRX状态信息时，eNB和gNB的DRX状态信息可以是激活状态，也可以是休眠状态，而在进行数据的接收和下发时，只有处于激活状态时才能进行数据的接收和下发，因此通过对eNB和gNB的DRX状态信息进行识别，以选择合适的数据接收端进行数据的下发。
在一实施例中，在确定数据接收端时，包括：若所述第一DRX状态信息为休眠状态，且所述第二DRX状态信息为激活状态，则确定所述gNB为所述数据接收端；若所述第一DRX状态信息为激活状态，且所述第二DRX状态信息为休眠状态，则确定所述eNB为所述数据接收端；若所述第一DRX状态信息与所述第二DRX状态信息均为激活状态，则确定所述gNB与所述eNB为所述数据接收端。
在DRX状态信息为激活状态时，便确定可以进行数据的接收和下发，无论此时是eNB还是gNB，都可以进行数据的接收和下发。同时，在两者均处于激活状态时，可以根据实际情 况确定如何进行数据的接收和下发，比如根据eNB和gNB各自对应的空口能力，也就是数据接收和下发能力。
另外，需要说明的是，eNB和gNB同时处于休眠状态的情况几乎不会发生，但并不是不可发生，若此情况发生了，将不会进行数据的接收和下发，而是等到当出现一方处于激活状态时再进行数据的接收和下发。
在一实施例中，在进行数据接收和下发时，eNB和gNB并不是仅仅与当前的UE所连接，还会与其他的若干UE相连接，以满足不同的UE的业务需求。因此在进行数据的接收和下发时，并不是可以直接使用eNB或者gNB的所有空口来进行数据的接收和下发，而是根据eNB和gNB的当前空口能力实现数据的及时接收和下发。
在确定进行数据接收和下发的数据接收端时，若在当前时刻仅存在一个可以设置为进行数据的接收和下发的端口时，并不会存在数据下发端的选择，而是直接使用当前可以使用的一端进行数据的接收和下发。在确定eNB和gNB均可以作为数据接收端来实现数据的接收和下发时，将会根据eNB和gNB分别对应的空口能力，确定eNB和gNB分别对应的数据下发量，进而使得eNB和gNB按照各自对应的数据下发进行数据的接收和下发。
比如，当前需要进行同步的待同步数据有200Mbps，且gNB和eNB的当前空口能力分别为1.0Gbps(等于1024Mbps)和100Mbps，此时可以根据各自的空口能力选择合适的分配方式，如gNB和eNB均为100Mbps，还可以是仅适用gNB，即gNB为200Mbps，也可以是其他的分配方式。但是，由于gNB具有更加快速的数据处理能力，因此在根据空口能力实现对数据的接收和下发时，可以优先选择gNB作为数据处理端来进行数据的接收和下发，也就是此时对应的数据流量包的分配方式可以是gNB为200Mbps，而eNB为0，但是并不是说只能按照这样的方式。
参照图3，图3为本公开一个实施例提供的确定DRX状态信息的步骤的流程示意图。
其中，根据用户设备UE的DRX信息，确定***演进型基站eNB与5G基站gNB分别对应的DRX状态信息，包括步骤S301至步骤S302。
步骤S301、获取所述DRX信息中所包含的当前帧的帧号以及子帧号。
在响应数据同步指令得到用户设备UE的DRX信息之后，将会对DRX信息中所包含的相关信息进行识别和获取，以用于确定eNB和gNB所对应的DRX状态信息。因此，在得到DRX信息之后，获取DRX信息中所包含的当前帧的帧号以及子帧号，然后根据所得到的当前帧的帧号以及子帧号确定eNB和gNB所对应的DRX状态信息。
在一个典型的长短周期DRX流程中，包含有若干长周期和短周期，同时针对于长短周期设置有相应的配置和参数，一个长短周期DRX流程如图4所示。对于一个长短周期而言，短周期对应着ShortDrxCycle，长周期对应着LongDrxCycle，且包含着若干子帧，以及存在于相应的***帧中，其中，每个子帧长达1ms，FDD(Frequency-division Duplex，模式指频分双工模式)和TDD(Time-division Duplex，模式指时分双工模式)而言，***帧的编号范围为0-1023，一个***帧内的子帧编号范围为0-9，每个***帧长达10ms，由10个子帧组成。
由图4可知，UE在时刻(0，0)成功解码到一个PDCCH子帧，其中(0，0)表示帧号为0的***帧中子帧号为0的子帧，因此开启了drx-inactivity Timer(3个子帧的长度)，当drx-inactivity Timer超时后开启drxShortCycle Timer(注意，此时应该是在4号子帧 开启，而不是5号子帧开启drxShortCycle Timer)，然后到了时刻(0，5)，满足了进入短周期的时间条件，UE将被唤醒以进入on duration(持续2个子帧)，并且在时刻(1，0)和时刻(1，5)多次进入短周期，接着到了时刻(1，9)，由于(drxShortCycle Timer×shortDrxCycle)＝15个子帧内没有成功解码到PDCCH子帧，准备进入长DRX周期，在时刻(2，0)满足长周期进入条件时，UE进入长DRX周期，并且在时刻(2，9)结束长周期，而UE在时刻(3，0)收到PDCCH子帧，因此重新启动了drx-inactivity定时器。
针对于一个典型的长短周期DRX流程而言，随着时间的不断推移，UE的状态会不断的进行变化，而由于一个***/设备的DRX配置是固定的，因此在确定相较于某一***/设备而言，可以根据当前所得到的部分参数确定当前时刻是处于激活状态还是休眠状态。如时刻(0，8)即处于休眠状态，而时刻(2，1)即处于激活状态。
因此，在一实施例中，在获取了UE的DRX信息之后，获取DRX信息中所包含的当前帧的帧号以及子帧号，进而根据所的都的当前帧的帧号以及子帧号确定eNB以及gNB所对应的DRX状态信息。
由于，短周期本身具有数据及时响应的特点，因此在进行分流下发时，所针对的主要场景是长周期。对于长周期而言，在确定eNB和gNB所对应的DRx状态时，实际上是确定eNB和gNB在UE的DRX信息的情况下是否进入了激活状态，因此此时将确定当前帧以及子帧所对应的时刻是否出处于相应激活状态。
步骤S302、根据所述当前帧的帧号以及所述子帧号，确定所述eNB与所述gNB分别对应的DRX状态信息，其中，所述DRX状态信息包括休眠状态和激活状态。
在得到当前帧的帧号以及子帧号之后，将会根据eNB以及gNB各自对应的DRX配置确定各自所对应的DRX状态信息，进而选择合适的数据接收和下发方式实现数据的分流处理。
在确定当前帧以及子帧对应的时刻的状态信息时，可以按照如下公式所得到，该公式为：
drxOffset＝[(SFN×10)+subFrameNumber]％longDRX_Cycle；
其中，drxOffset为当前帧以及子帧对应的时刻对应的计算结果，SFN为当前帧的帧号，subFrameNumber为当前所对应的子帧号，longDRX_Cycle为长DRX周期，且周期单位为毫秒(ms)。通过取longDRX_Cycle的模得到对应的drxOffset。
在得到drxOffset之后，在确定是否处于激活状态时，将drxOffset与对应的drxStartOffset进行对比，在两者相等时，确定进而了激活状态，但是并不是只有两者相等时说明进入了激活状态，由于一个DRX周期中处于激活状态的时刻并不是只有一个帧以及子帧对应的时刻，因此可以确定处于激活状态的一个数值范围，在drxOffset处于该数值范围内时，说明处于激活状态，反之则处于休眠状态，其中，drxStartOffset为DRX周期的的起始值，且取值范围为(0,longDRX_Cycle-1)。
比如，在longDRX_Cycle为320ms，drxStartOffset为9，on_Duration为10时，那么此时在drxOffset处于9～18范围内时，确定处于激活状态。
因此，在根据UE的DRX信息中所包含的当前帧的帧号以及子帧号确定eNB和gNB分别对应的DRX状态信息时，通过获取eNB和gNB的DRX配置信息，以进行相应的计算和处理，以根据所得到的结果信息确定eNB以及gNB所对应的DRX状态信息。
参照图5，图5为本公开另一个实施例中确定DRX状态信息的步骤的流程示意图。
其中，根据所述当前帧的帧号以及所述子帧号，确定所述eNB与所述gNB分别对应的DRX 状态信息，包括步骤S501至步骤S503。
步骤S501、获取所述eNB与所述gNB分别对应的第一DRX配置信息与第二DRX配置信息；
步骤S502、根据所述所述当前帧的帧号、所述子帧号以及所述第一DRX配置信息，确定所述eNB对应的第一DRX状态信息；
步骤S503、根据所述所述当前帧的帧号、所述子帧号以及所述第二DRX配置信息，确定所述gNB对应的第二DRX状态信息。
由上述描述可知，在确定eNB和gNB分别对应的DRX状态信息时，除了获取UE的DRX信息之外，还需要根据eNB以及gNB各自所对应的DRX配置信息来确定，因此，此时将获取eNB以及gNB所分别对应的第一DRX配置信息以及第二DRX配置信息，然后根据所得到的当前帧的帧号、子帧号以及第一DRX配置信息确定eNB所对应的第一DRX状态信息，以及根据所得到的当前帧的帧号、子帧号以及第二DRX配置信息确定gNB所对应的第二DRX状态信息。
在确定各自对应的DRX状态信息时，首先可以根据上述描述的计算公式计算得到当前帧的帧号以及子帧号所对应的结果信息，然后将所得到的结果信息与对应的激活状态对应的信息进行对比，确定eNB和gNB分别对应的状态信息，即是否处于激活状态。
在一实施例中，在根据当前帧的帧号以及子帧号，确定eNB对应的DRX状态信息时，包括：获取所述第一DRX配置信息所包含的第一DRX周期以及第一虚拟激活期；根据所述当前帧的帧号、所述子帧号以及所述第一DRX周期，确定当前是否处于所述第一虚拟激活期内；若确定处于所述第一虚拟激活期内，则确定所述第一DRX状态信息为激活状态；若确定不处于所述第一虚拟激活期内，则确定所述第一DRX状态信息为休眠状态。
在确定eNB对应的DRX状态信息时，在第一DRX配置信息中获取第一DRX周期以及所记录的第一激活期，其中，第一DRX周期为eNB所对应的长周期，接着，根据所得到的当前帧的帧号、子帧号以及第一周期按照上述所提及的计算公式进行计算，得到对应的计算结果，进而根据所得到的计算结果与第一激活期进行对比，确定eNB所对应的DRX状态。
示例性的，将计算得到的drxOffset与第一虚拟激活期进行对比，在drxOffset处于第一虚拟激活期内时，确定eNB的第一DRX状态信息为激活状态，反之则为休眠状态。
例如，DRX配置为longDRX_Cycle为320ms,drxStartOffset配置为19，on_duration时长为15ms，若当前帧的帧号为127，子帧号5，按照上述描述的公式，计算得到drxOffset＝(127*10+5)％320＝315，而配置的19～33，那么此刻为休眠状态。若当前帧号129帧，子帧号9，则计算得到drxOffset＝(129*10+9)％320＝19，此时与drxStartOffset相等，则认为处于激活状态。
需要说明的是，步骤S502与步骤S503之间没有具体的先后顺序，可以是步骤S502在步骤S503之前，或者步骤S503在步骤S502之前，还可以是步骤S502与步骤S503同时发生，具体不做限制。
在一实施例中，在根据当前帧的帧号以及子帧号，确定gNB对应的DRX状态信息时，包括：获取所述第二DRX配置信息所包含的第二DRX周期以及第二激活期；根据所述当前帧的帧号、所述子帧号以及所述第二DRX周期，确定当前是否处于所述第二激活期内；若确定处于所述第二激活期内，则确定所述第二DRX状态信息为激活状态；若确定不处于所述第二激活期内，则确定所述第二DRX状态信息为休眠状态。
在实现过程中，与得到eNB所对应的第一状态信息的过程相同，仅仅是判断对象由eNB 变为gNB，利用当前帧的帧号以及子帧号确定是否处于gNB所对应的第二激活期内，若确定处于第二激活期内，则确定第二DRX状态信息为激活状态，反正则为休眠状态。
在一实施例中，由于链路以及数据传输的延时性，可以在进行数据下发之前提前将需要下发的数据流量包发送至eNB和/或gNB中，进而在eNB和/或gNB进入激活状态时，可以第一时间将所需要下发的数据流量包下发至相应的UE。
因此，在根据上述描述的方式计算得到drxOffset之后，可以对下一次的激活状态进行预测，使得在有数据流量包进行下发时可以提前将数据流量包发送至eNB和/或gNB中。在实际应用过程中，可以提前10个子帧(具体不做限制)进行预测，比如在确定进而激活状态的drxOffset＝19时，可以在drxOffset＝9所对应的时刻确定是否有数据流量包需要进行下发，并在确定存在数据流量包需要进行下发时，在gNB的流控模块PDCP中获取需要进行下发的数据流量包，以存储在gNB和/或eNB的流控上报模块RLC中。
示例性的，通过提前进行预测，保证PDCP发送到RLC的数据可及时发送到UE侧，而对于进行预测的时刻来说，若提前10个子帧进行预判，根据上述描述的DRX状态计算公式计算出的结果，按照如下方式进行预判。
drxOffsetFinal＝drxOffset-10，drxOffset≥10；
drxOffsetFinal＝longDRX_Cycle-10+drxOffset,drxOffset＜10。
其中，drxOffsetFinal为进行预测的时刻，而进行预测是针对下一个DRX周期而言，因此，利用上述方式，在确定当前DRX周期内的状态信息之后，可以根据实际的状态确定在下一个DRX周期内的进行RLC向PDCP进行数据请求的时刻。
在上述描述的数据下发方法、设备以及可读存储介质中，在接收到数据同步指令时，获取用户设备UE的DRX信息，然后根据所得到的DRX信息确定当前所对应的数据接收端是eNB还是gNB，进而在确定数据接收端之后，接收待同步数据，并指示数据接收端将接收到的待同步数据下发至用户设备UE。实现了在数据同步时，根据当前UE的DRX状态向gNB的流控OMG模块PDCP进行数据量的请求，通过选择合适的且处于激活状态的一端进行数据信息的下发，避免两侧状态不一致导致的负增益现象，保证数据的及时性。
参照图6，图6为本公开实施例提供的一种数据下发设备的结构示意性框图。
示例性的，电子设备可以为手机、平板、笔记本、台式机、电视、专用输入设备、取款机等。
该设备还包括处理器、存储器，所述存储器设置为存储计算机程序。
所述处理器，设置为执行所述计算机程序并在执行所述计算机程序时实现本公开实施例提供的任一项数据下发方法。
应当理解的是，处理器可以是中央处理单元(Central Processing Unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。其中，通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
本公开的实施例中还提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时，使所述处理器实现本公开实施例提供的任一项 自治域***AS的网络部署方法。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、***、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读存储介质上，计算机可读存储介质可以包括计算机可读存储介质(或非暂时性介质)和通信介质(或暂时性介质)。
如本领域普通技术人员公知的，术语计算机可读存储介质包括在设置为存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机可读存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以设置为存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
示例性的，所述计算机可读存储介质可以是前述实施例所述的电子设备的内部存储单元，例如所述电子设备的硬盘或内存。所述计算机可读存储介质也可以是所述电子设备的外部存储设备，例如所述电子设备上配备的插接式硬盘，智能存储卡(Smart Media Card，SMC)，安全数字(Secure Digital，SD)卡，闪存卡(Flash Card)等。
前述各实施例提供的电子设备和计算机可读存储介质，通过在用户输入信息时，在显示屏上不同的显示区域显示至少两个虚拟键盘，使得可以通过至少两个虚拟键盘输入信息；提高恶意软件通过监听传感器的状态推测输入信息的难度，增强了信息输入的安全性。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以权利要求的保护范围为准。

Claims (10)

  1. 一种数据下发方法，所述方法包括以下步骤：
    根据用户设备UE的DRX信息，确定***演进型基站eNB与5G基站gNB分别对应的DRX状态信息；
    根据所述DRX状态信息确定数据接收端，并将待同步数据下发至所述数据接收端，以指示所述数据接收端将所述同步数据下发至所述UE，其中，所述数据接收端为所述eNB与所述gNB中的一个或者两个。
  2. 根据权利要求1所述的数据下发方法，其中，所述根据用户设备UE的DRX信息，确定***演进型基站eNB与5G基站gNB分别对应的DRX状态信息之前，还包括：
    接收数据同步指令，并控制所述eNB与所述gNB的流控上报模块RLC获取用户设备UE的DRX信息。
  3. 根据权利要求1所述的数据下发方法，其中，所述根据用户设备UE的DRX信息，确定***演进型基站eNB与5G基站gNB分别对应的DRX状态信息，包括：
    获取所述DRX信息中所包含的当前帧的帧号以及子帧号；
    根据所述当前帧的帧号以及所述子帧号，确定所述eNB与所述gNB分别对应的DRX状态信息，其中，所述DRX状态信息包括休眠状态和激活状态。
  4. 根据权利要求3所述的数据下发方法，其中，所述根据所述当前帧的帧号以及所述子帧号，确定所述eNB与所述gNB分别对应的DRX状态信息，包括：
    获取所述eNB与所述gNB分别对应的第一DRX配置信息与第二DRX配置信息；
    根据所述所述当前帧的帧号、所述子帧号以及所述第一DRX配置信息，确定所述eNB对应的第一DRX状态信息；
    根据所述所述当前帧的帧号、所述子帧号以及所述第二DRX配置信息，确定所述gNB对应的第二DRX状态信息。
  5. 根据权利要求4所述的数据下发方法，其中，所述根据所述当前帧的帧号、所述子帧号以及所述第一DRX配置信息，确定所述eNB对应的第一DRX状态信息，包括：
    获取所述第一DRX配置信息所包含的第一DRX周期以及第一激活期；
    根据所述当前帧的帧号、所述子帧号以及所述第一DRX周期，确定当前是否处于所述第一激活期内；
    若确定处于所述第一激活期内，则确定所述第一DRX状态信息为激活状态；
    若确定不处于所述第一激活期内，则确定所述第一DRX状态信息为休眠状态。
  6. 根据权利要4所述的数据下发方法，其中，所述根据所述所述当前帧的帧号、所述子帧号以及所述第二DRX配置信息，确定所述gNB对应的第二DRX状态信息，包括：
    获取所述第二DRX配置信息所包含的第二DRX周期以及第二激活期；
    根据所述当前帧的帧号、所述子帧号以及所述第二DRX周期，确定当前是否处于所述第二激活期内；
    若确定处于所述第二激活期内，则确定所述第二DRX状态信息为激活状态；
    若确定不处于所述第二激活期内，则确定所述第二DRX状态信息为休眠状态。
  7. 根据权利要求4所述的数据下发方法，其中，所述根据所述DRX状态信息确定数据接 收端，包括：
    若所述第一DRX状态信息为休眠状态，且所述第二DRX状态信息为激活状态，则确定所述gNB为所述数据接收端；
    若所述第一DRX状态信息为激活状态，且所述第二DRX状态信息为休眠状态，则确定所述eNB为所述数据接收端；
    若所述第一DRX状态信息与所述第二DRX状态信息均为激活状态，则确定所述gNB与所述eNB为所述数据接收端。
  8. 根据权利要求7所述的方法，其中，若所述第一DRX状态信息与所述第二DRX状态信息均为激活状态，则确定所述gNB与所述eNB为所述数据接收端，所述将待同步数据下发至所述数据接收端，包括：
    根据所述eNB以及所述gNB分别对应的空口能力，确定所述eNB以及所述gNB分别对应的数据下发量，以将所述待同步数据按照各自对应数据下发量进行下发。
  9. 一种数据下发设备，包括存储器以及处理器；
    所述存储器设置为存储计算机程序；
    所述处理器，设置为执行所述计算机程序并在执行所述计算机程序时实现如权利要求1至8任一项所述的数据下发方法的步骤。
  10. 一种存储介质，设置为计算机可读存储，所述存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现权利要求1至8中任一项所述的数据下发的步骤。
PCT/CN2021/095878 2020-06-24 2021-05-25 数据下发方法、设备和存储介质 WO2021258962A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP21828037.8A EP4175406A4 (en) 2020-06-24 2021-05-25 DATA OUTPUT METHOD AND DEVICE AND STORAGE MEDIUM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010589920.7 2020-06-24
CN202010589920.7A CN113840369A (zh) 2020-06-24 2020-06-24 数据下发方法、设备和存储介质

Publications (1)

Publication Number Publication Date
WO2021258962A1 true WO2021258962A1 (zh) 2021-12-30

Family

ID=78964657

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/095878 WO2021258962A1 (zh) 2020-06-24 2021-05-25 数据下发方法、设备和存储介质

Country Status (3)

Country Link
EP (1) EP4175406A4 (zh)
CN (1) CN113840369A (zh)
WO (1) WO2021258962A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103841594A (zh) * 2012-11-21 2014-06-04 中兴通讯股份有限公司 非连续接收模式管理方法、用户设备及基站
US20150327169A1 (en) * 2014-05-07 2015-11-12 Samsung Electronics Co., Ltd. Method, user equipment and base station for controlling discontinuous reception (drx) in wireless communication system
CN107950056A (zh) * 2015-10-06 2018-04-20 英特尔Ip公司 使用3gpp无线电接入技术的接入***之间的双无线电操作
CN108377548A (zh) * 2016-10-12 2018-08-07 中国电信股份有限公司 一种移动性管理方法、ue 和通信***
CN109618419A (zh) * 2018-12-19 2019-04-12 中兴通讯股份有限公司 一种用于支持双连接的安全处理方法及***

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10321513B2 (en) * 2015-08-17 2019-06-11 Samsung Electronics Co., Ltd Method for PDCP control PDU transmission by user equipment (UE)

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103841594A (zh) * 2012-11-21 2014-06-04 中兴通讯股份有限公司 非连续接收模式管理方法、用户设备及基站
US20150327169A1 (en) * 2014-05-07 2015-11-12 Samsung Electronics Co., Ltd. Method, user equipment and base station for controlling discontinuous reception (drx) in wireless communication system
CN107950056A (zh) * 2015-10-06 2018-04-20 英特尔Ip公司 使用3gpp无线电接入技术的接入***之间的双无线电操作
CN108377548A (zh) * 2016-10-12 2018-08-07 中国电信股份有限公司 一种移动性管理方法、ue 和通信***
CN109618419A (zh) * 2018-12-19 2019-04-12 中兴通讯股份有限公司 一种用于支持双连接的安全处理方法及***

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4175406A4 *

Also Published As

Publication number Publication date
EP4175406A4 (en) 2023-12-27
EP4175406A1 (en) 2023-05-03
CN113840369A (zh) 2021-12-24

Similar Documents

Publication Publication Date Title
CN107439030B (zh) 在lte许可协助接入操作中的drx处理
US11089619B2 (en) Data transmission method, device and system
TWI399115B (zh) 改善不連續接收功能的方法及通訊裝置
WO2021082012A1 (zh) 用于确定非连续接收持续定时器的启动状态的方法及设备
WO2018107498A1 (zh) 用于非连续接收的方法和装置
WO2021243600A1 (zh) 数据传输处理方法、装置、用户设备及存储介质
US20210235376A1 (en) Power saving host-modem interaction in a communication device
WO2021129507A1 (zh) 唤醒信号配置方法、唤醒信号处理方法及相关设备
KR101944556B1 (ko) 무선부에서의 절전 모드 제어 방법
US20230208563A1 (en) Discontinuous reception control method and apparatus, terminal, and readable storage medium
WO2021129508A1 (zh) 唤醒信号处理方法、唤醒信号配置方法及相关设备
WO2020063782A1 (zh) 一种通信方法及装置
WO2022184101A1 (zh) 间隙gap处理方法、装置、设备及存储介质
WO2022063232A1 (zh) 确定终端行为的方法、指示终端行为的方法及装置
WO2022194000A1 (zh) 上行发送处理方法、装置、终端及可读存储介质
WO2021258962A1 (zh) 数据下发方法、设备和存储介质
WO2022222892A1 (zh) 一种非连续接收的配置方法及装置
WO2022100505A1 (zh) 信息处理方法、装置及终端
WO2022148431A1 (zh) 非连续接收drx配置切换的方法、装置及终端
WO2021164787A1 (zh) 信息上报方法、用户设备及网络侧设备
WO2021207899A1 (zh) 信息发送方法、用户设备、基站设备及计算机存储介质
WO2022206648A1 (zh) 侧链路非连续接收的实现方法、装置及终端
WO2023108576A1 (zh) 通信方法及装置
WO2024036527A1 (zh) 搜索空间配置方法、装置、通信设备及存储介质
WO2022194177A1 (zh) 监听控制方法及相关设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21828037

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021828037

Country of ref document: EP

Effective date: 20230124