WO2023221794A1 - 控制方法、通信设备及存储介质 - Google Patents

控制方法、通信设备及存储介质 Download PDF

Info

Publication number
WO2023221794A1
WO2023221794A1 PCT/CN2023/092601 CN2023092601W WO2023221794A1 WO 2023221794 A1 WO2023221794 A1 WO 2023221794A1 CN 2023092601 W CN2023092601 W CN 2023092601W WO 2023221794 A1 WO2023221794 A1 WO 2023221794A1
Authority
WO
WIPO (PCT)
Prior art keywords
time
network
preset
terminal
access
Prior art date
Application number
PCT/CN2023/092601
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 EP23806746.6A priority Critical patent/EP4395409A1/en
Publication of WO2023221794A1 publication Critical patent/WO2023221794A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/06—Access restriction performed under specific conditions based on traffic conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H04W74/0841—Random access procedures, e.g. with 4-step access with collision treatment
    • H04W74/085—Random access procedures, e.g. with 4-step access with collision treatment collision avoidance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/06—Airborne or Satellite Networks

Definitions

  • This application relates to the field of communication technology, and specifically to a control method, communication equipment and storage medium.
  • the network instructs the UE to select a time delay RACH (random access channel) in [0, BackoffParameter Value] through the Backoff Indicator carried in the RAR (random access response) Try to relieve congestion.
  • RACH random access channel
  • the inventor discovered that for the NTN network, congestion may be more severe due to larger coverage and more terminals being served. Therefore, the UE may need to try to send Random Access multiple times during the RACH process to successfully access the network (that is, the Backoff Indicator is sent multiple times by the network device to alleviate congestion), because the uplink synchronization timer (Validity timer) is always running, and NTN There is a large propagation delay in the network, so the remaining valid time after the UE successfully accesses the network may not be able to meet the data transmission. After the timer times out, the UE needs to re-obtain the required SI, causing service interruption.
  • the existing mechanism cannot guarantee that when the RACH is congested, the UE can successfully access the network within a limited time (Validity timer) and reserve more time for data transmission.
  • this application provides a control method, communication device and storage medium.
  • One of the purposes is to solve the RACH congestion in the IoT-NTN network and avoid RACH taking up too much time and causing data to be available within the uplink synchronization valid time. Insufficient transmission time leads to business interruption.
  • This application provides a control method that can be applied to communication devices (such as mobile phones), including the following steps:
  • the terminal In response to satisfying the first preset condition, the terminal delays access to the network by a preset time according to the second time issued by the network device.
  • satisfying the first preset condition includes at least one of the following:
  • the first time is the service end time when the network device covers the current service area
  • the second time is the service start time of the next network device covering the current service area
  • the terminal is released through the RRC release message of the network.
  • the parameters carried by the RRC release message include at least one of the following: duration T, specific reason value.
  • step S10 includes:
  • the method of determining the preset time includes at least one of the following:
  • the preset time is determined or generated based on the grouping.
  • the step of determining or generating the preset time according to the first time range includes:
  • a duration in the range of 0 to T is randomly selected as the preset time.
  • T is a value greater than 0, or the T is associated with the current load.
  • step S10 also includes:
  • satisfying the second preset condition includes at least one of the following:
  • the RRC release message does not carry the T value
  • the T value carried by the RRC release message is 0;
  • the release reason value carried by the RRC release message is not a specific reason value
  • the current business is a preset high-priority business.
  • This application also provides a control method, which can be applied to communication devices (such as mobile phones).
  • the method includes the following steps:
  • satisfying the preset condition includes: satisfying the first preset condition and/or satisfying the second preset condition.
  • satisfying the first preset condition includes at least one of the following:
  • the terminal is released by the network before the first time, and the first time is issued by the network device;
  • the terminal accesses the network at the second time, and the second time is delivered by the network device.
  • the first time is the service end time when the network device covers the current service area
  • the second time is the service start time of the next network device covering the current service area
  • the terminal is released through the RRC release message of the network.
  • the parameters carried by the RRC release message include at least one of the following: duration T, specific reason value.
  • satisfying the second preset condition includes at least one of the following:
  • RRC release message carries T value
  • the T value carried by the RRC release message is not 0;
  • the release reason value carried by the RRC release message is a specific reason value
  • the current service is not a preset high-priority service.
  • the terminal delays access to the network according to a preset policy, including:
  • the method also includes:
  • the method of determining the preset time includes at least one of the following:
  • the preset time is determined or generated based on the grouping.
  • the step of determining or generating the preset time according to the first time range includes:
  • a duration in the range of 0 to T is randomly selected as the preset time.
  • T is a value greater than 0, or the T is associated with the current load.
  • This application also provides a control method, which can be applied to communication equipment (such as network equipment such as satellites, base stations or aviation equipment).
  • the method includes the following steps:
  • the network device delivers a second time for the terminal to access the network according to the second time delay preset time.
  • the method also includes:
  • the network device issues an RRC release message to release the terminal.
  • the parameters carried by the RRC release message include at least one of the following: duration T, specific reason value.
  • the network device delivers the first time and/or the second time through a system message
  • the first time is the service end time when the network device covers the current service area
  • the second time is the service start time of the next network device covering the current service area.
  • the terminal determines the preset time in a manner that includes at least one of the following:
  • the terminal determines or generates the preset time according to the first time range
  • the terminal determines or generates the preset time according to the grouping.
  • the step of the terminal determining or generating the preset time according to the first time range includes:
  • the terminal randomly selects a duration in the range of 0 to T as the preset time according to the duration T issued by the network device.
  • T is a value greater than 0, or the T is associated with the current load.
  • This application also provides a control method, which can be applied to communication equipment (such as network equipment such as satellites, base stations or aviation equipment).
  • the method includes the following steps:
  • the network device delivers a message for the terminal to delay access to the network according to the message and the preset policy.
  • the S1001 step includes:
  • the network device issues a second time for the terminal to access the network according to the second time delay and a preset time.
  • the S1001 step also includes:
  • the network device issues an RRC release message to release the terminal.
  • the parameters carried by the RRC release message include at least one of the following: duration T, specific reason value.
  • the network device delivers the first time and/or the second time through a system message
  • the first time is the service end time when the network device covers the current service area
  • the second time is the service start time of the next network device covering the current service area.
  • the terminal determines the preset time in a manner that includes at least one of the following:
  • the terminal determines or generates the preset time according to the first time range
  • the terminal determines or generates the preset time according to the grouping.
  • the step of the terminal determining or generating the preset time according to the first time range includes:
  • the terminal randomly selects a duration in the range of 0 to T as the preset time according to the duration T issued by the network device.
  • T is a value greater than 0, or the T is associated with the current load.
  • This application also provides a control device, which includes:
  • the first access module is configured to delay access to the network for a preset time according to a second time issued by the network device in response to satisfying the first preset condition.
  • This application also provides a control device, which includes:
  • the second access module is configured to delay access to the network according to the preset policy in response to meeting the preset conditions.
  • This application also provides a control device, which includes:
  • the first sending module is used to deliver a second time for the terminal to access the network according to the second time delay preset time.
  • This application also provides a control device.
  • the control device of this application is applied to network equipment.
  • the control device includes:
  • the second sending module is used to send a message for the terminal to delay access to the network according to the message and the preset policy.
  • This application also provides a communication device, including: a memory and a processor.
  • a control program is stored on the memory. When the control program is executed by the processor, the steps of any of the above control methods are implemented.
  • the present application also provides a computer-readable storage medium.
  • a control program is stored on the storage medium.
  • the control program is executed by a processor, the steps of any one of the above control methods are implemented.
  • the control method proposed in this application includes: in response to satisfying the first preset condition, the terminal delays access to the network according to the second time issued by the network device for a preset time. Alternatively, in response to satisfying the preset condition, the terminal delays access to the network according to the preset policy. Therefore, by delaying access to the network, the problem of RACH congestion caused by the centralized access of a large number of UEs in the IoT-NTN network is avoided, thereby avoiding RACH congestion in the IoT-NTN network.
  • RACH takes up too much time and causes ineffective uplink synchronization. There is insufficient time available for data transmission, causing business interruption.
  • Figure 1 is a schematic diagram of the hardware structure of a terminal device that implements various embodiments of the present application
  • FIG. 2 is a communication network system architecture diagram provided by an embodiment of the present application.
  • Figure 3 is a schematic flow chart of a first embodiment of a control method provided by the embodiment of the present application.
  • Figure 4 is a schematic diagram of a terminal delayed access scenario according to an embodiment of the present application.
  • Figure 5 is a schematic interactive flow diagram of a control method provided by an embodiment of the present application.
  • Figure 6 is a schematic flow chart of a second embodiment of a control method provided by the embodiment of the present application.
  • Figure 7 is a schematic flowchart of a third embodiment of a control method provided by the embodiment of the present application.
  • Figure 8 is a schematic flowchart of a fourth embodiment of a control method provided by the embodiment of the present application.
  • Figure 9 is a functional module schematic diagram of a control device provided by an embodiment of the present application.
  • FIG. 10 is a functional module schematic diagram of yet another control device provided by an embodiment of the present application.
  • FIG. 11 is a functional module schematic diagram of yet another control device provided by an embodiment of the present application.
  • Figure 12 is a functional module schematic diagram of yet another control device provided by an embodiment of the present application.
  • the terms “comprises,” “comprises,” or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements, but also It also includes other elements not expressly listed or that are inherent to the process, method, article, or apparatus.
  • an element defined by the statement “comprises a" does not exclude the presence of other identical elements in the process, method, article or device including the element.
  • this application Components, features, and elements with the same names in different embodiments may have the same meaning or may have different meanings, and their specific meanings need to be determined based on their interpretation in the specific embodiment or further combined with the context of the specific embodiment.
  • first, second, third, etc. may be used herein to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
  • first information may also be called second information, and similarly, the second information may also be called first information.
  • word “if” as used herein may be interpreted as “when” or “when” or “in response to determining.”
  • singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context indicates otherwise.
  • A, B, C means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C"; another example is, “ A, B or C” or "A, B and/or C” means "any of the following: A; B; C; A and B; A and C; B and C; A and B and C". Only if the component, function, step Exceptions to this definition arise when combinations of steps or operations are inherently mutually exclusive in some way.
  • each step in the flow chart in the embodiment of the present application is displayed in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated in this article, the execution of these steps is not strictly limited in order, and they can be executed in other orders. Moreover, at least some of the steps in the figure may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but may be executed at different times, and their execution order is not necessarily sequential. may be performed in turn or alternately with other steps or sub-steps of other steps or at least part of stages.
  • the words “if” or “if” as used herein may be interpreted as “when” or “when” or “in response to determination” or “in response to detection.”
  • the phrase “if determined” or “if (stated condition or event) is detected” may be interpreted as “when determined” or “in response to determining” or “when (stated condition or event) is detected )” or “in response to detecting (a stated condition or event)”.
  • step codes such as S10 and S20 are used for the purpose of describing the corresponding content more clearly and concisely, and do not constitute a substantial restriction on the sequence. Those skilled in the art may S20 will be executed first and then S10, etc., but these should be within the protection scope of this application.
  • the communication device can be a terminal device, or a network device such as a satellite, a base station, or an aviation equipment, which needs to be determined according to the specific context. If it is a terminal device, the terminal device can be implemented in various forms.
  • the terminal devices described in this application may include mobile phones, tablet computers, notebook computers, PDAs, personal digital assistants (Personal Digital Assistant, PDA), portable media players (Portable Media Player, PMP), navigation devices, Terminal devices such as wearable devices, smart bracelets, and pedometers, as well as fixed terminals such as base stations, digital TVs, and desktop computers.
  • the network device can be a base station or satellite or aviation equipment, such as low-orbit communication satellites, high-altitude platforms, and drones.
  • the device used to realize the function of the network device may be the network device itself, or it may be a device that can support the network device to realize the function, such as a chip system or a combined device or component that can realize the function of the network device.
  • the device Can be installed on network equipment. The embodiments of this application do not limit the specific technology and specific equipment form used by the network equipment.
  • a terminal device will be taken as an example.
  • the structure according to the embodiments of the present application can also be applied to fixed-type terminals.
  • the terminal device 100 may include: RF (Radio Frequency, radio frequency) unit 101, WiFi module 102, audio output unit 103, A /V (audio/video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111 and other components.
  • RF Radio Frequency, radio frequency
  • WiFi module 102 WiFi module
  • a /V audio/video
  • sensor 105 sensor
  • display unit 106 user input unit 107
  • interface unit 108 user input unit 107
  • memory 109 memory 109
  • processor 110 and power supply 111 and other components.
  • the radio frequency unit 101 can be used to receive and send information or signals during a call. Specifically, after receiving the downlink information of the base station, it is processed by the processor 110; in addition, the uplink data is sent to the base station.
  • the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, transceiver, coupler, low noise amplifier, duplexer, etc.
  • the radio frequency unit 101 can also communicate with the network and other devices through wireless communication.
  • the above wireless communication can use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication, Global Mobile Communications System), GPRS (General Packet Radio Service, General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000 , Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access, Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access, Time Division Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division) Duplexing-Long Term Evolution, Frequency Division Duplex Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution, Time Division Duplex Long Term Evolution) and 5G, etc.
  • GSM Global System of Mobile communication, Global Mobile Communications System
  • GPRS General Packet Radio Service
  • CDMA2000 Code Division Multiple Access 2000
  • WCDMA Wideband Code Division Multiple Access
  • TD-SCDMA Time Division-Synchronous Code Division Multiple Access, Time Division Synchronous Code
  • WiFi is a short-distance wireless transmission technology.
  • the terminal device 100 can help users send and receive emails, browse web pages, access streaming media, etc. through the WiFi module 102. It provides users with wireless broadband Internet access.
  • FIG. 1 shows the WiFi module 102, it can be understood that it is not a necessary component of the terminal device and can be omitted as needed without changing the essence of the invention.
  • the audio output unit 103 can, when the terminal device 100 is in a call signal receiving mode, a call mode, a recording mode, a voice recognition mode, a broadcast receiving mode, etc., receive the audio signal received by the radio frequency unit 101 or the WiFi module 102 or store it in the memory 109 The audio data is converted into audio signals and output as sound. Furthermore, the audio output unit 103 may also provide audio output related to a specific function performed by the terminal device 100 (eg, call signal reception sound, message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, or the like.
  • the A/V input unit 104 is used to receive audio or video signals.
  • the A/V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042.
  • the graphics processor 1041 may process still pictures or images obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. Video image data is processed.
  • the processed image frames may be displayed on the display unit 106.
  • the image frames processed by the graphics processor 1041 may be stored in the memory 109 (or other storage media) or transmitted via a radio frequency unit. module 101 or WiFi module 102 to send.
  • the microphone 1042 can receive sounds (audio data) via the microphone 1042 in operating modes such as a phone call mode, a recording mode, a voice recognition mode, and the like, and can process such sounds into audio data.
  • the processed audio (voice) data can be converted into a format that can be sent to a mobile communication base station via the radio frequency unit 101 for output in a phone call mode.
  • Microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated in the process of receiving and transmitting audio signals.
  • the terminal device 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor.
  • the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of the ambient light.
  • the proximity sensor can turn off the display when the terminal device 100 moves to the ear. Panel 1061 and/or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three axes). It can detect the magnitude and direction of gravity when stationary.
  • It can be used to identify applications of mobile phone posture (such as horizontal and vertical screen switching, related games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for the mobile phone, it can also be configured with fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, Other sensors such as thermometers and infrared sensors will not be described in detail here.
  • the display unit 106 is used to display information input by the user or information provided to the user.
  • the display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • the user input unit 107 may be used to receive input numeric or character information and generate key signal input related to user settings and function control of the terminal device.
  • the user input unit 107 may include a touch panel 1071 and other input devices 1072.
  • the touch panel 1071 also known as a touch screen, can collect the user's touch operations on or near the touch panel 1071 (for example, the user uses a finger, stylus, or any suitable object or accessory on or near the touch panel 1071 operation), and drive the corresponding connection device according to the preset program.
  • the touch panel 1071 may include two parts: a touch detection device and a touch controller.
  • the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device and converts it into contact point coordinates , and then sent to the processor 110, and can receive the commands sent by the processor 110 and execute them.
  • the touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave.
  • the user input unit 107 may also include other input devices 1072.
  • other input devices 1072 may include but are not limited to one or more of physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, joysticks, etc., which are not specifically discussed here. limited.
  • the touch panel 1071 can cover the display panel 1061.
  • the touch panel 1071 detects a touch operation on or near it, it is transmitted to the processor 110 to determine the type of the touch event, and then the processor 110 determines the type of the touch event according to the touch event.
  • the type provides corresponding visual output on the display panel 1061.
  • the touch panel 1071 and the display panel 1061 are used as two independent components to implement the input and output functions of the terminal device, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated. The implementation of the input and output functions of the terminal device is not limited here.
  • the interface unit 108 serves as an interface through which at least one external device can be connected to the terminal device 100 .
  • external devices may include a wired or wireless headphone port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input/output (I/O) port, video I/O port, headphone port, etc.
  • the interface unit 108 may be used to receive input from an external device (eg, data information, power, etc.) and transmit the received input to one or more elements within the terminal device 100 or may be used to connect the terminal device 100 and the external device 100 . Transfer data between devices.
  • Memory 109 may be used to store software programs as well as various data.
  • the memory 109 may mainly include a storage program area and a storage data area.
  • the storage program area may store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), etc.;
  • the storage data area may Store data created based on the use of the mobile phone (such as audio data, phone book, etc.), etc.
  • the memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
  • the processor 110 is the control center of the terminal device 100, using various interfaces and lines to connect various parts of the entire terminal device 100, by running or executing software programs and/or modules stored in the memory 109, and calling the software programs and/or modules stored in the memory 109. data, perform various functions of the terminal device 100 and process data, thereby overall monitoring the terminal device 100.
  • the processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor.
  • the application processor mainly processes the operating system, user interface, application programs, etc., and modulation
  • the demodulation processor mainly handles wireless communications. It can be understood that the above modem processor may not be integrated into the processor 110 .
  • the terminal device 100 may also include a power supply 111 (such as a battery) that supplies power to various components.
  • a power supply 111 such as a battery
  • the power supply 111 may be logically connected to the processor 110 through a power management system, thereby achieving management of charging, discharging, and power consumption management through the power management system. and other functions.
  • the terminal device 100 may also include a Bluetooth module, etc., which will not be described again here.
  • FIG. 2 is an architecture diagram of a communication network system provided by an embodiment of the present application.
  • the communication network system is an LTE system of universal mobile communication technology.
  • the LTE system includes UEs (User Equipment, User Equipment) connected in sequence. ) 201, E-UTRAN (Evolved UMTS Terrestrial Radio Access Network, Evolved UMTS Terrestrial Radio Access Network) 202, EPC (Evolved Packet Core, Evolved Packet Core Network) 203 and the operator's IP business 204.
  • UEs User Equipment, User Equipment
  • E-UTRAN Evolved UMTS Terrestrial Radio Access Network
  • EPC Evolved Packet Core, Evolved Packet Core Network
  • UE 201 may be the above-mentioned terminal device 100, which will not be described again here.
  • E-UTRAN202 includes eNodeB2021 and other eNodeB2022, etc.
  • eNodeB2021 can be connected to other eNodeB2022 through backhaul (for example, X2 interface), eNodeB2021 is connected to EPC203, and eNodeB2021 can provide access from UE201 to EPC203.
  • backhaul for example, X2 interface
  • EPC 203 may include MME (Mobility Management Entity, mobility management entity) 2031, HSS (Home Subscriber Server, home user server) 2032, other MME 2033, SGW (Serving Gate Way, service gateway) 2034, PGW (PDN Gate Way, packet data Network Gateway) 2035 and PCRF (Policy and Charging Rules Function, policy and charging functional entity) 2036, etc.
  • MME2031 is a control node that processes signaling between UE201 and EPC203, and provides bearer and connection management.
  • HSS2032 is used to provide some registers to manage functions such as the home location register (not shown in the figure), and to save some user-specific information about service characteristics, data rates, etc. All user data can be sent through SGW2034.
  • PGW2035 can provide IP address allocation and other functions for UE 201.
  • PCRF2036 is the policy and charging control policy decision point for business data flows and IP bearer resources. It is the policy and charging execution function. The unit (not shown) selects and provides available policy and charging control decisions.
  • IP services 204 may include the Internet, Intranet, IMS (IP Multimedia Subsystem, IP Multimedia Subsystem) or other IP services.
  • IMS IP Multimedia Subsystem, IP Multimedia Subsystem
  • UE User equipment, terminal, terminal equipment
  • RACH Random Access CHannel, random access channel
  • RAR Random access response, random access response
  • SI System information, system message
  • TN Terrestrial Network, terrestrial network
  • NTN Non-Terrestrial Network, non-terrestrial network
  • IoT-NTN Internet of Things-Non-Terrestrial Network, Internet of Things-Non-Terrestrial Network;
  • NB-IoT Narrow Band Internet of Things, narrowband Internet of Things
  • Quasi-earth fixed cell An NTN cell fixed with respect to a certain geographical area on the earth during a certain time duration. This can be provided by beam(s) covering one geographical area for a finite period and a different geographical area during another Period.
  • Pseudo-Earth fixed cell refers to an NTN cell fixed in a certain geographical area of the earth within a certain period of time.
  • the control method of the present application can be applied to the terminal device (hereinafter referred to as the terminal) as described above, such as a UE.
  • the terminal establishes a communication connection with the network device in the network communication system where it is located.
  • the network device can be Base stations or satellites or aviation equipment, such as low-orbit communication satellites, high-altitude platforms and drones.
  • the device used to realize the function of the network device may be the network device itself, or it may be a device that can support the network device to realize the function, such as a chip system or a combined device or component that can realize the function of the network device.
  • the device Can be installed on network equipment.
  • the embodiments of this application do not limit the specific technology and specific equipment form used by the network equipment.
  • This embodiment takes a communication implementation solution between a satellite and a terminal (UE) as an example.
  • the first embodiment of the present application proposes a control method.
  • the control method of the present application includes the following steps:
  • the terminal In response to satisfying the first preset condition, the terminal delays access to the network by a preset time according to the second time issued by the network device.
  • This embodiment considers that: for IoT-NTN networks, the existing mechanism cannot guarantee that when RACH is congested, the UE can successfully access the network within a limited time (Validity timer) and reserve more time for data transmission. Therefore, this application proposes a solution that can avoid RACH congestion in the IoT-NTN network, thereby avoiding the problem that RACH takes up too much time, resulting in insufficient time available for data transmission within the uplink synchronization valid time, resulting in service interruption.
  • T1 i.e. end-time of Serving satellite's coverage
  • T2 start-time of incoming satellite's coverage
  • Figure 4 is a schematic diagram of a terminal delayed access scenario according to an embodiment of the present application.
  • the current serving satellite broadcasts the first time T1 (i.e., end-time of serving satellite’s coverage) and the second time T2 (i.e., start-time of incoming satellite’s coverage) through system messages.
  • the first time T1 is the service end time when the network device covers the current service area; the second time T2 is the service start time when the next network device covers the current service area.
  • T1 and T2 are broadcast through SI (system information) and are effective for all UEs in the area, so there may be a large number of UEs at this T2 time point. Trying to access the satellite causes RACH congestion.
  • the preset time delay access is delayed based on the time T2, that is, the UE will try to obtain the required SI and access at the T2+delay time point.
  • the network ensures that the time for each UE to access the network is discretized to avoid RACH congestion, thereby avoiding the problem that RACH takes up too much time, resulting in insufficient time available for data transmission within the uplink synchronization valid time, resulting in service interruption.
  • the terminal in response to satisfying the first preset condition, delays access to the network by a preset time according to the second time issued by the network device.
  • RACH congestion in the IoT-NTN network can be avoided, thereby avoiding the problem that RACH takes up too much time, resulting in insufficient time available for data transmission within the uplink synchronization valid time, resulting in service interruption.
  • satisfying the first preset condition includes at least one of the following:
  • the terminal is released by the network before the first time
  • the terminal accesses the network at the second time.
  • the network delivers the above-mentioned first time T1 and second time T2 to the terminal (UE) through SI (system message), and the terminal delays access to the network according to the second time T2 delivered by the network device for a preset time.
  • the terminal is released by the network before the first time.
  • the following solution can be used:
  • the network sends an RRC release message to the terminal, and the terminal releases it through the RRC release message sent by the network device.
  • the parameters carried by the RRC release message issued by the network device may include at least one of the following: duration T, specific reason value.
  • a specific reason value such as coverage discontinuity indicates that the release is because the current satellite is about to stop serving.
  • the step S10 may include: the terminal determines the preset time.
  • the terminal determines the preset time, and delays access to the network by the preset time according to the second time issued by the network device.
  • the terminal determines the preset time in a manner that may include at least one of the following:
  • the first way the terminal determines or generates the preset time according to the first time range
  • the terminal can randomly select a duration in the range of 0 to T as the preset time according to the duration T issued by the network device.
  • T is a value greater than 0.
  • the T value cannot exceed the satellite service time.
  • T can be a fixed value.
  • T may be related to the current cell load. For example, the higher the load, the greater T is.
  • the second way the terminal determines or generates the preset time based on grouping and preset time granularity.
  • the number of packets and the preset time granularity can be determined by the network according to the current load and the random access channel RACH capacity, and delivered to the UE.
  • step S10 may also include:
  • the terminal determines that the preset time is not valid.
  • satisfying the second preset condition includes at least one of the following:
  • the RRC release message does not carry the T value
  • the T value carried by the RRC release message is 0;
  • the release reason value carried in the RRC release message is not a specific reason value
  • the delay will not take effect for the UE.
  • the current service is a preset high-priority service. For example, if the current UE is a high-priority service such as an emergency call, the delay will not take effect.
  • the current serving satellite broadcasts T1 (ie, end-time of serving satellite’s coverage) and T2 (ie, start-time of incoming satellite’s coverage) through system messages.
  • delay access will be delayed based on T2, that is, the UE will try to obtain the required SI and access the network at the T2+delay time point to ensure that each UE has the time to access the network. Discretization to avoid RACH congestion.
  • the UE and corresponding delay can be determined as follows:
  • the UE is a UE released by the network through the RRC release message, and the RRC release message carries a specific cause value, such as coverage discontinuity, indicating that the release is because the current satellite is about to stop serving.
  • the UE is a UE released by the network through the RRC release message, and the RRC release message carries a specific cause value, such as coverage discontinuity, indicating that the release is because the current satellite is about to stop serving.
  • UEs Divide UEs into N groups (such as grouping according to UE identification, UEID mod N), delay delta, N and delta are issued by the network equipment, then the delayed access time of each group of UEs is (UEID mod N)*delta.
  • N and delta can be determined by the network based on the current load and RACH capacity.
  • delta can be the currently configured RACH cycle.
  • This UE is all UEs that attempt to access the network at time T2.
  • the network device sends an RRC release message.
  • This UE is all UEs that attempt to access the network at time T2.
  • N and delta can be determined by the network based on the current load and RACH capacity. For example, delta can be the currently configured RACH cycle.
  • the terminal in response to satisfying the first preset condition, the terminal delays access to the network according to the second time issued by the network device for a preset time. Therefore, by delaying the terminal's access to the network for a preset time, the problem of RACH congestion caused by the centralized access of a large number of UEs in the IoT-NTN network is avoided, thereby avoiding RACH congestion in the IoT-NTN network and RACH taking up too much time. There is insufficient time available for data transmission within the valid period of uplink synchronization, causing service interruption.
  • Satellite1 (Satellite 1)
  • Satellite2 (Satellite 2).
  • the following is a detailed description of the implementation solutions for different scenarios:
  • Satellite1 (Satellite 1) serves area a at the current time and broadcasts T1 and T2 through system messages.
  • the UE receives T1 and T2.
  • the RRC release message carries the release reason value discontinue coverage and time T.
  • Satellite2 (Satellite 2) will serve area a at T2 time point.
  • the T value can be fixed or related to the current cell load. The higher the load, the greater the T value. The T value cannot exceed the satellite service time.
  • the delay will not take effect for the UE.
  • the delay will not take effect if the current UE is engaged in high-priority services such as emergency calls.
  • Satellite1 serves area a at the current time and broadcasts T1 and T2 through system messages.
  • the UE receives T1 and T2.
  • satellite1 releases all connected mode UEs through the RRC Release message.
  • the RRC release message carries the release reason value discontinue coverage.
  • Satellite2 will serve area a at the T2 time point. For UEs whose release reason value is discontinue coverage and try to access the Satellite2 at the T2 time point, access will be delayed by the delay time according to the group index to which it belongs.
  • index UEID mod N
  • N is the number of groups
  • delta is the preset time granularity
  • the UE delay time cannot exceed the satellite service time.
  • the time for each UE to access the network may be as shown in Table 2 below (ideally, the number of UEs in each group is the same):
  • the delay will not take effect if the current UE is engaged in high-priority services such as emergency calls.
  • Satellite1 serves area a at the current time and broadcasts T1, T2, and T through system messages, and the UE receives T1, T2, and T.
  • the time for each UE to access the network may be as shown in Table 3 below:
  • the delay will not take effect if the current UE is engaged in high-priority services such as emergency calls.
  • Satellite1 serves area a at the current time and broadcasts T1 and T2 through system messages.
  • the UE receives T1 and T2.
  • Satellite2 will serve area a at time point T2. For all UEs that attempt to access Satellite2 at time point T2, access will be delayed by the delay time according to the index of the group to which it belongs.
  • index UEID mod N
  • N is the number of groups
  • delta is the preset time granularity
  • the UE delay time cannot exceed the satellite service time.
  • the time for each UE to access the network may be as shown in Table 4 below (ideally, the number of UEs in each group is the same):
  • the delay will not take effect if the current UE is engaged in high-priority services such as emergency calls.
  • the terminal in response to satisfying the first preset condition, the terminal delays access to the network according to the second time issued by the network device for a preset time. Therefore, by delaying the terminal's access to the network for a preset time, the problem of RACH congestion caused by the centralized access of a large number of UEs in the IoT-NTN network is avoided, thereby avoiding RACH congestion in the IoT-NTN network and RACH taking up too much time. There is insufficient time available for data transmission within the valid period of uplink synchronization, causing service interruption.
  • the process of implementing congestion control in communication between the network device and the terminal (UE) can be referred to as shown in Figure 5 .
  • the main interaction processes include:
  • Step A The network device sends a message for the terminal to delay access to the network according to the message and the preset policy;
  • Step A1 The network device delivers the first time and/or the second time through the system message
  • Step A2 The network side issues the RRC release message to release the terminal before the first time;
  • Step B In response to meeting the preset conditions, the terminal delays access to the network according to the preset policy
  • Step B1 In response to satisfying the first preset condition, the terminal delays access to the network by the preset time according to the second time issued by the network device.
  • Step B2 The terminal determines the preset time.
  • Step B21 The terminal determines or generates the preset time based on the first time range; or the terminal determines or generates the preset time based on grouping and preset time granularity.
  • the terminal in response to satisfying the first preset condition, delays access to the network according to the second time issued by the network device, or the terminal delays access to the network according to the message issued by the network device and the preset policy. Access the network. Therefore, by delaying the terminal's access to the network for a preset time, the problem of RACH congestion caused by the centralized access of a large number of UEs in the IoT-NTN network is avoided, thereby avoiding RACH congestion in the IoT-NTN network and RACH taking up too much time. There is insufficient time available for data transmission within the valid period of uplink synchronization, causing service interruption.
  • the second embodiment of the present application proposes a control method, which can be applied to the terminal side.
  • the control method of the present application includes the following steps:
  • a communication connection is established between the terminal and the network equipment in the network communication system where it is located.
  • the network equipment may be a base station, satellite, or aviation equipment, such as low-orbit communication satellites, high-altitude platforms, and drones.
  • the device used to realize the function of the network device may be the network device itself, or it may be a device that can support the network device to realize the function, such as a chip system or a combined device or component that can realize the function of the network device.
  • the device Can be installed on network equipment.
  • the embodiments of this application do not limit the specific technology and specific equipment form used by the network equipment.
  • This embodiment takes a communication implementation solution between a satellite and a terminal (UE) as an example.
  • This embodiment considers that: for IoT-NTN networks, the existing mechanism cannot guarantee that when RACH is congested, the UE can successfully access the network within a limited time (Validity timer) and reserve more time for data transmission. Therefore, this application proposes a solution that can avoid RACH congestion in the IoT-NTN network, thereby avoiding the problem that RACH takes up too much time, resulting in insufficient time available for data transmission within the uplink synchronization valid time, resulting in service interruption.
  • T1 i.e. end-time of Serving satellite's coverage
  • T2 start-time of incoming satellite's coverage
  • Figure 4 is a schematic diagram of a terminal delayed access scenario according to an embodiment of the present application.
  • the current serving satellite broadcasts the first time T1 (i.e., end-time of serving satellite’s coverage) and the second time T2 (i.e., start-time of incoming satellite’s coverage) through system messages.
  • the first time T1 is the service end time when the network device covers the current service area; the second time T2 is the service start time when the next network device covers the current service area.
  • T1 and T2 are broadcast through SI (system information) and are effective for all UEs in the area. Therefore, at the T2 time point, there may be a large number of UEs trying to access the satellite, causing RACH congestion.
  • the preset time delay access is delayed based on the time T2, that is, the UE will try to obtain the required SI and access at the T2+delay time point.
  • the network ensures that the time for each UE to access the network is discretized to avoid RACH congestion, thereby avoiding the problem that RACH takes up too much time, resulting in insufficient time available for data transmission within the uplink synchronization valid time, resulting in service interruption.
  • the terminal in response to meeting the preset conditions, the terminal delays access to the network according to the preset policy.
  • satisfying the preset condition may include: satisfying the first preset condition and/or satisfying the second preset condition.
  • satisfying the first preset condition includes at least one of the following:
  • the terminal is released by the network before the first time
  • the terminal accesses the network at the second time.
  • the network delivers the above-mentioned first time T1 and second time T2 to the terminal (UE) through SI (system message), and the terminal delays access to the network according to the second time T2 delivered by the network device for a preset time.
  • the terminal is released by the network before the first time.
  • the following solution can be used:
  • the network sends an RRC release message to the terminal, and the terminal releases it through the RRC release message sent by the network device.
  • the parameters carried by the RRC release message issued by the network device may include at least one of the following: duration T, specific reason value.
  • a specific reason value such as coverage discontinuity indicates that the release is because the current satellite is about to stop serving.
  • satisfying the second preset condition may include at least one of the following:
  • the RRC release message carries the T value
  • the T value carried by the RRC release message is not 0;
  • the release reason value carried by the RRC release message is a specific reason value
  • the second preset condition is not met and the delay does not take effect for the UE.
  • the current service is not a preset high-priority service.
  • the current UE is a high-priority service such as an emergency call
  • the second preset condition is not met, and the delay does not take effect for the UE.
  • the terminal delays access to the network according to a preset policy in response to satisfying the above-mentioned first preset condition and/or satisfying the above-mentioned second preset condition.
  • the terminal delays access to the network according to a preset policy, including:
  • the terminal delays access to the network according to the preset time.
  • the method also includes:
  • the terminal determines the preset time.
  • the terminal determines the preset time in response to satisfying the first preset condition and/or satisfying the second preset condition, and delays access to the network by the preset time according to the second time issued by the network device.
  • the terminal determines the preset time in a manner that may include at least one of the following:
  • the first way the terminal determines or generates the preset time according to the first time range
  • the terminal can randomly select a duration in the range of 0 to T as the preset time according to the duration T issued by the network device.
  • T is a value greater than 0.
  • the T value cannot exceed the satellite service time.
  • T can be a fixed value.
  • T may be related to the current cell load. For example, the higher the load, the greater T is.
  • the second way the terminal determines or generates the preset time based on grouping and preset time granularity.
  • the number of packets and the preset time granularity can be determined by the network according to the current load and the random access channel RACH capacity, and delivered to the UE.
  • the current serving satellite broadcasts T1 (ie, end-time of serving satellite’s coverage) and T2 (ie, start-time of incoming satellite’s coverage) through system messages.
  • delay access will be delayed based on T2, that is, the UE will try to obtain the required SI and access the network at the T2+delay time point to ensure that each UE has the time to access the network. Discretization to avoid RACH congestion.
  • the UE and corresponding delay can be determined as follows:
  • the UE is a UE released by the network through the RRC release message, and the RRC release message carries a specific cause value, such as coverage discontinuity, indicating that the release is because the current satellite is about to stop serving.
  • the UE is a UE released by the network through the RRC release message, and the RRC release message carries a specific cause value, such as coverage discontinuity, indicating that the release is because the current satellite is about to stop serving.
  • UEs Divide UEs into N groups (such as grouping according to UE identification, UEID mod N), delay delta, N and delta are issued by the network equipment, then the delayed access time of each group of UEs is (UEID mod N)*delta.
  • N and delta can be determined by the network based on the current load and RACH capacity.
  • delta can be the currently configured RACH cycle.
  • This UE is all UEs that attempt to access the network at time T2.
  • the network device sends an RRC release message.
  • This UE is all UEs that attempt to access the network at time T2.
  • N and delta can be determined by the network based on the current load and RACH capacity. For example, delta can be the currently configured RACH cycle.
  • the terminal in response to meeting the preset conditions, the terminal delays access to the network according to the preset policy. Therefore, by delaying access to the network, the problem of RACH congestion caused by the centralized access of a large number of UEs in the IoT-NTN network is avoided, thereby avoiding RACH congestion in the IoT-NTN network.
  • RACH takes up too much time and causes ineffective uplink synchronization. There is insufficient time available for data transmission, causing business interruption.
  • Satellite1 (Satellite 1)
  • Satellite2 (Satellite 2).
  • the following is a detailed description of the implementation solutions for different scenarios:
  • Satellite1 (Satellite 1) serves area a at the current time and broadcasts T1 and T2 through system messages.
  • the UE receives T1 and T2.
  • the RRC release message carries the release reason value discontinue coverage and time T.
  • Satellite2 (Satellite 2) will serve area a at T2 time point.
  • the T value can be fixed or related to the current cell load. The higher the load, the greater the T value. The T value cannot exceed the satellite service time.
  • the delay will not take effect for the UE.
  • the delay will not take effect if the current UE is engaged in high-priority services such as emergency calls.
  • Satellite1 serves area a at the current time and broadcasts T1 and T2 through system messages.
  • the UE receives T1 and T2.
  • satellite1 releases all connected mode UEs through the RRC Release message.
  • the RRC release message carries the release reason value discontinue coverage.
  • Satellite2 will serve area a at the T2 time point. For UEs whose release reason value is discontinue coverage and try to access the Satellite2 at the T2 time point, access will be delayed by the delay time according to the group index to which it belongs.
  • index UEID mod N
  • N is the number of groups
  • delta is the preset time granularity
  • the UE delay time cannot exceed the satellite service time.
  • the time for each UE to access the network may be as shown in Table 2 above (ideally, the number of UEs in each group is the same).
  • the delay will not take effect if the current UE is engaged in high-priority services such as emergency calls.
  • Satellite1 serves area a at the current time and broadcasts T1, T2, and T through system messages, and the UE receives T1, T2, and T.
  • the time for each UE to access the network may be as shown in Table 3 above.
  • the delay will not take effect if the current UE is engaged in high-priority services such as emergency calls.
  • Satellite1 serves area a at the current time and broadcasts T1 and T2 through system messages.
  • the UE receives T1 and T2.
  • Satellite2 will serve area a at time point T2. For all UEs that attempt to access Satellite2 at time point T2, access will be delayed by the delay time according to the index of the group to which it belongs.
  • index UEID mod N
  • N is the number of groups
  • delta is the preset time granularity
  • the UE delay time cannot exceed the satellite service time.
  • the time for each UE to access the network may be as shown in Table 4 above (ideally, the number of UEs in each group is the same).
  • the delay will not take effect if the current UE is engaged in high-priority services such as emergency calls.
  • the terminal in response to satisfying the first preset condition, the terminal delays access to the network according to the second time issued by the network device for a preset time. Therefore, by delaying the terminal's access to the network for a preset time, the problem of RACH congestion caused by the centralized access of a large number of UEs in the IoT-NTN network is avoided, thereby avoiding RACH congestion in the IoT-NTN network and RACH taking up too much time. There is insufficient time available for data transmission within the valid period of uplink synchronization, causing service interruption.
  • the process of communication between the network device and the terminal (UE) to implement congestion control may be referred to as shown in Figure 5 and will not be described again here.
  • control method which can be applied to network equipment.
  • the control method includes the following steps:
  • the network device delivers a second time for the terminal to access the network according to the second time delay preset time.
  • a communication connection is established between the terminal and the network device.
  • the network device may be a base station or satellite or aviation equipment, such as low-orbit communication satellites, high-altitude platforms, and drones.
  • the device used to realize the function of the network device may be the network device itself, or it may be a device that can support the network device to realize the function, such as a chip system or a combined device or component that can realize the function of the network device.
  • the device Can be installed on network equipment.
  • the embodiments of this application do not limit the specific technology and specific equipment form used by the network equipment.
  • This embodiment takes a communication implementation solution between a satellite and a terminal (UE) as an example.
  • This embodiment considers that: for IoT-NTN networks, the existing mechanism cannot guarantee that when RACH is congested, the UE can successfully access the network within a limited time (Validity timer) and reserve more time for data transmission. Therefore, this application proposes a solution that can avoid RACH congestion in the IoT-NTN network, thereby preventing RACH from taking up too much time, resulting in insufficient time for data transmission within the uplink synchronization valid time, and insufficient time available for data transmission, resulting in business interruption. question.
  • T1 and T2 are broadcast through SI (system messages) and take effect for all UEs in the area.
  • Figure 4 is a schematic diagram of a terminal delayed access scenario according to an embodiment of the present application.
  • the current serving satellite broadcasts the first time T1 (i.e., end-time of serving satellite’s coverage) and the second time T2 (i.e., start-time of incoming satellite’s coverage) through system messages.
  • the first time T1 is the service end time when the network device covers the current service area; the second time T2 is the service start time when the next network device covers the current service area.
  • T1 and T2 are broadcast through SI (system information) and are effective for all UEs in the area. Therefore, at the T2 time point, there may be a large number of UEs trying to access the satellite, causing RACH congestion.
  • the preset time delay access is delayed based on the time T2, that is, the UE will try to obtain the required SI and access at the T2+delay time point.
  • the network ensures that the time for each UE to access the network is discretized to avoid RACH congestion, thereby avoiding the problem that RACH takes up too much time, resulting in insufficient time available for data transmission within the uplink synchronization valid time, resulting in service interruption.
  • the network device issues a second time for the terminal to access the network according to the second time delay preset time.
  • the terminal In response to satisfying the first preset condition, the terminal delays access to the network by a preset time according to a second time issued by the network device.
  • RACH congestion in the IoT-NTN network can be avoided, thereby avoiding the problem that RACH takes up too much time, resulting in insufficient time available for data transmission within the uplink synchronization valid time, resulting in service interruption.
  • the method also includes:
  • the network device issues an RRC release message to release the terminal.
  • the parameters carried by the RRC release message include at least one of the following: duration T, specific reason value.
  • the method also includes at least one of the following:
  • the network device delivers the first time and/or the second time through a system message
  • the first time is the service end time when the network device covers the current service area
  • the second time is the service start time of the next network device covering the current service area.
  • the network delivers the above-mentioned first time T1 and second time T2 to the terminal (UE) through SI (system message), and the terminal delays access to the network according to the second time T2 delivered by the network device for a preset time.
  • the terminal meets the first preset condition, including at least one of the following:
  • the terminal is released by the network before the first time
  • the terminal accesses the network at the second time.
  • the terminal is released by the network before the first time.
  • the following solution can be used:
  • the network sends an RRC release message to the terminal, and the terminal releases it through the RRC release message sent by the network device.
  • the parameters carried by the RRC release message issued by the network device may include at least one of the following: duration T, specific reason value.
  • a specific reason value such as coverage discontinuity indicates that the release is because the current satellite is about to stop serving.
  • the terminal determines the preset time in a manner that may include at least one of the following:
  • the first way the terminal determines or generates the preset time according to the first time range
  • the terminal can randomly select a duration in the range of 0 to T as the preset time according to the duration T issued by the network device.
  • T is a value greater than 0.
  • the T value cannot exceed the satellite service time.
  • T can be a fixed value.
  • T may be related to the current cell load. For example, the higher the load, the greater T is.
  • the second way the terminal determines or generates the preset time based on grouping and preset time granularity.
  • the number of packets and the preset time granularity can be determined by the network according to the current load and the random access channel RACH capacity, and delivered to the UE.
  • the terminal determines not to take effect in the preset time in response to satisfying the second preset condition.
  • satisfying the second preset condition includes at least one of the following:
  • the RRC release message does not carry the T value
  • the T value carried by the RRC release message is 0;
  • the release reason value carried in the RRC release message is not a specific reason value
  • the delay will not take effect for the UE.
  • the current service is a preset high-priority service. For example, if the current UE is a high-priority service such as an emergency call, the delay will not take effect.
  • the current serving satellite broadcasts T1 (ie, end-time of serving satellite’s coverage) and T2 (ie, start-time of incoming satellite’s coverage) through system messages.
  • delay access will be delayed based on T2, that is, the UE will try to obtain the required SI and access the network at the T2+delay time point to ensure that each UE has the time to access the network. Discretization to avoid RACH congestion.
  • the UE and corresponding delay can be determined as follows:
  • the UE is a UE released by the network through the RRC release message, and the RRC release message carries a specific cause value, such as coverage discontinuity, indicating that the release is because the current satellite is about to stop serving.
  • the UE is a UE released by the network through the RRC release message, and the RRC release message carries a specific cause value, such as coverage discontinuity, indicating that the release is because the current satellite is about to stop serving.
  • UEs Divide UEs into N groups (such as grouping according to UE identification, UEID mod N), delay delta, N and delta are issued by the network equipment, then the delayed access time of each group of UEs is (UEID mod N)*delta.
  • N and delta can be determined by the network based on the current load and RACH capacity.
  • delta can be the currently configured RACH. cycle.
  • This UE is all UEs that attempt to access the network at time T2.
  • the network device sends an RRC release message.
  • This UE is all UEs that attempt to access the network at time T2.
  • N and delta can be determined by the network based on the current load and RACH capacity. For example, delta can be the currently configured RACH cycle.
  • the network device issues a second time for the terminal to access the network according to the second time delay and the preset time. Therefore, by delaying the terminal's access to the network for a preset time, the problem of RACH congestion caused by the centralized access of a large number of UEs in the IoT-NTN network is avoided, thereby avoiding RACH congestion in the IoT-NTN network and RACH taking up too much time. There is insufficient time available for data transmission within the valid period of uplink synchronization, causing service interruption.
  • the process of communication between the network device and the terminal (UE) to achieve congestion control can be referred to Figure 5.
  • the principle of communication between the network device and the terminal (UE) to achieve congestion control and the principles of each scenario please refer to The above embodiments will not be described again here.
  • the fourth embodiment of the present application proposes a control method.
  • the control method can be applied to network equipment.
  • the control method includes the following steps:
  • the network device delivers a message for the terminal to delay access to the network according to the message and the preset policy.
  • a communication connection is established between the terminal and the network device.
  • the network device may be a base station or satellite or aviation equipment, such as low-orbit communication satellites, high-altitude platforms, and drones.
  • the device used to realize the function of the network device may be the network device itself, or it may be a device that can support the network device to realize the function, such as a chip system or a combined device or component that can realize the function of the network device.
  • the device Can be installed on network equipment.
  • the embodiments of this application do not limit the specific technology and specific equipment form used by the network equipment.
  • This embodiment takes a communication implementation solution between a satellite and a terminal (UE) as an example.
  • the messages sent by the network device include but are not limited to system messages, RRC release messages, etc.
  • This embodiment considers that: for IoT-NTN networks, the existing mechanism cannot guarantee that when RACH is congested, the UE can successfully access the network within a limited time (Validity timer) and reserve more time for data transmission. Therefore, this application proposes a solution that can avoid RACH congestion in the IoT-NTN network, thereby avoiding the problem that RACH takes up too much time, resulting in insufficient time available for data transmission within the uplink synchronization valid time, resulting in service interruption.
  • T1 i.e. end-time of Serving satellite's coverage
  • T2 start-time of incoming satellite's coverage
  • Figure 4 is a schematic diagram of a terminal delayed access scenario according to an embodiment of the present application.
  • the current serving satellite broadcasts the first time T1 (i.e., end-time of serving satellite’s coverage) and the second time T2 (i.e., start-time of incoming satellite’s coverage) through system messages.
  • the first time T1 is the service end time when the network device covers the current service area; the second time T2 is the service start time when the next network device covers the current service area.
  • T1 and T2 are broadcast through SI (system information) and are effective for all UEs in the area. Therefore, at the T2 time point, there may be a large number of UEs trying to access the satellite, causing RACH congestion.
  • the preset time delay access is delayed based on the time T2, that is, the UE will try to obtain the required SI and access at the T2+delay time point.
  • the network ensures that the time for each UE to access the network is discretized to avoid RACH congestion, thereby avoiding the problem that RACH takes up too much time, resulting in insufficient time available for data transmission within the uplink synchronization valid time, resulting in service interruption.
  • the network device delivers a message for the terminal to delay access to the network according to the message and the preset policy.
  • the terminal delays access to the network according to the messages sent by the network device and the preset policy, which avoids the RACH congestion problem caused by the centralized access of a large number of UEs in the IoT-NTN network, thereby avoiding the problem of RACH congestion in the IoT-NTN network.
  • the S1001 step includes:
  • the network device issues a second time for the terminal to access the network according to the second time delay and a preset time.
  • the S1001 step also includes:
  • the network device issues an RRC release message to release the terminal.
  • the parameters carried by the RRC release message include at least one of the following: duration T, specific reason value.
  • the network device delivers the first time T1 and the second time T2 through a system message
  • the first time T1 is the service end time when the network device covers the current service area
  • the second time T2 is the service start time of the next network device covering the current service area.
  • the terminal delays access to the network according to the preset policy.
  • satisfying the preset condition may include: satisfying the first preset condition and/or satisfying the second preset condition.
  • satisfying the first preset condition includes at least one of the following:
  • the terminal is released by the network before the first time
  • the terminal accesses the network at the second time.
  • the terminal is released by the network before the first time.
  • the following solution can be used:
  • the network sends an RRC release message to the terminal, and the terminal releases it through the RRC release message sent by the network device.
  • the parameters carried by the RRC release message issued by the network device may include at least one of the following: duration T, specific reason value.
  • a specific reason value such as coverage discontinuity indicates that the release is because the current satellite is about to stop serving.
  • satisfying the second preset condition may include at least one of the following:
  • the RRC release message carries the T value
  • the T value carried by the RRC release message is not 0;
  • the release reason value carried by the RRC release message is a specific reason value
  • the second preset condition is not met and the delay does not take effect for the UE.
  • the current service is not a preset high-priority service.
  • the current UE is a high-priority service such as an emergency call
  • the second preset condition is not met, and the delay does not take effect for the UE.
  • the terminal delays access to the network according to the preset policy.
  • the terminal delays access to the network according to a preset policy, including:
  • the terminal delays access to the network according to the preset time.
  • the terminal determines the preset time.
  • the terminal determines the preset time in response to satisfying the first preset condition and/or satisfying the second preset condition, and delays access to the network by the preset time according to the second time issued by the network device.
  • the terminal determines the preset time in a manner that may include at least one of the following:
  • the first way the terminal determines or generates the preset time according to the first time range
  • the terminal can randomly select a duration in the range of 0 to T as the preset time according to the duration T issued by the network device.
  • T is a value greater than 0.
  • the T value cannot exceed the satellite service time.
  • T can be a fixed value.
  • T may be related to the current cell load. For example, the higher the load, the greater T is.
  • the second method the terminal determines or generates the preset time based on grouping and preset time granularity.
  • the number of packets and the preset time granularity can be determined by the network according to the current load and the random access channel RACH capacity, and delivered to the UE.
  • the current serving satellite broadcasts T1 (ie, end-time of serving satellite’s coverage) and T2 (ie, start-time of incoming satellite’s coverage) through system messages.
  • delay access will be delayed based on T2, that is, the UE will try to obtain the required SI and access the network at the T2+delay time point to ensure that each UE has the time to access the network. Discretization to avoid RACH congestion.
  • the UE and corresponding delay can be determined as follows:
  • the UE is a UE released by the network through the RRC release message, and the RRC release message carries a specific cause value, such as coverage discontinuity, indicating that the release is because the current satellite is about to stop serving.
  • the UE is a UE released by the network through the RRC release message, and the RRC release message carries a specific cause value, such as coverage discontinuity, indicating that the release is because the current satellite is about to stop serving.
  • UEs Divide UEs into N groups (such as grouping according to UE identification, UEID mod N), delay delta, N and delta are issued by the network equipment, then the delayed access time of each group of UEs is (UEID mod N)*delta.
  • N and delta can be determined by the network based on the current load and RACH capacity.
  • delta can be the currently configured RACH. cycle.
  • This UE is all UEs that attempt to access the network at time T2.
  • the network device sends an RRC release message.
  • This UE is all UEs that attempt to access the network at time T2.
  • N and delta can be determined by the network based on the current load and RACH capacity. For example, delta can be the currently configured RACH cycle.
  • the network device issues a message for the terminal to delay access to the network according to the message and the preset policy. Therefore, by delaying access to the network, the problem of RACH congestion caused by the centralized access of a large number of UEs in the IoT-NTN network is avoided, thereby avoiding RACH congestion in the IoT-NTN network.
  • RACH takes up too much time and causes ineffective uplink synchronization. There is insufficient time available for data transmission, causing business interruption.
  • the process of communication between the network device and the terminal (UE) to achieve congestion control can be referred to Figure 5.
  • the principle of communication between the network device and the terminal (UE) to achieve congestion control and the principles of each scenario please refer to The above embodiments will not be described again here.
  • the embodiment of the present application also provides a control device.
  • the control device of the present application can be applied to terminal equipment.
  • the control device includes:
  • the first access module is configured to delay access to the network for a preset time according to a second time issued by the network device in response to satisfying the first preset condition.
  • control device also includes:
  • the first determining module is used to determine the preset time.
  • the first determination module is also configured to determine or generate the preset time according to the first time range; or, determine or generate the preset time according to the grouping.
  • the first determination module is also configured to randomly select a duration in the range of 0 to T as the preset time according to the duration T issued by the network device.
  • T is a value greater than 0. , or the T is associated with the current load.
  • the first access module is further configured to determine not to take effect for the preset time in response to satisfying the second preset condition.
  • each module in the above-mentioned control device corresponds to each step in the above-mentioned control method embodiment, and its functions and implementation processes will not be described again here.
  • the embodiment of the present application also provides a control device.
  • the control device of the present application can be applied to terminal equipment.
  • the control device includes:
  • the second access module is configured to delay access to the network according to the preset policy in response to meeting the preset conditions.
  • the second access module is also used to delay access to the network according to a preset time.
  • control device also includes:
  • the second determination module is used to determine the preset time.
  • the second determination module is also configured to determine or generate the preset time based on the first time range; or, determine or generate the preset time based on grouping.
  • the second determination module is also configured to randomly select a duration in the range of 0 to T as the preset time according to the duration T issued by the network device.
  • T is a value greater than 0. , or the T is associated with the current load.
  • each module in the above-mentioned control device corresponds to each step in the above-mentioned control method embodiment, and its functions and implementation processes will not be described again here.
  • the embodiment of the present application also provides a control device.
  • the control device of the present application can be applied to network equipment.
  • the control device includes:
  • the first sending module is used to deliver a second time for the terminal to access the network according to the second time delay preset time.
  • the first sending module is also configured to send an RRC release message to release the terminal before the first time comes.
  • each module in the above-mentioned control device corresponds to each step in the above-mentioned control method embodiment, and its functions and implementation processes will not be described again here.
  • the embodiment of the present application also provides a control device.
  • the control device of the present application can be applied to network equipment.
  • the control device includes:
  • the second sending module is used to send a message for the terminal to delay access to the network according to the message and the preset policy.
  • the second sending module is also configured to deliver a second time for the terminal to access the network according to the second time delay preset time.
  • the second sending module is also configured to send an RRC release message to release the terminal before the first time comes.
  • each module in the above-mentioned control device corresponds to each step in the above-mentioned control method embodiment, and its functions and implementation processes will not be described again here.
  • An embodiment of the present application also provides a communication device.
  • the communication device includes a memory and a processor.
  • a communication program is stored on the memory.
  • the steps of the control method in any of the above embodiments are implemented.
  • the communication device can be a terminal device in the above control method.
  • the communication device can be: a mobile phone, a tablet computer, a notebook computer, a handheld computer, a personal digital assistant (Personal Digital Assistant, PDA), a convenient Portable Media Player (PMP), navigation devices, wearable devices, smart bracelets, pedometers and other terminal devices.
  • the communication device may also be a network device in the above communication method.
  • the communication device When used as the network device, the communication device may be a base station or satellite or aviation equipment, such as low-orbit communication satellites, high-altitude platforms and unmanned aerial vehicles. wait.
  • the device used to realize the function of the network device may be the network device itself, or it may be a device that can support the network device to realize the function, such as a chip system or a combined device or component that can realize the function of the network device.
  • the device Can be installed on network equipment.
  • the embodiments of this application do not limit the specific technology and specific equipment form used by the network equipment.
  • Embodiments of the present application also provide a computer-readable storage medium.
  • a control program is stored on the storage medium.
  • the control program is executed by a processor, the steps of the control method described in any of the above embodiments are implemented.
  • the embodiments of communication equipment and computer-readable storage media provided by this application can include all technical features of any of the above control method embodiments.
  • the expansion and explanation content of the description is basically the same as that of each embodiment of the above method, and will not be discussed here. Let’s go into details.
  • Embodiments of the present application also provide a computer program product.
  • the computer program product includes computer program code.
  • the computer program code When the computer program code is run on a computer, it causes the computer to execute the methods in the above various possible implementations.
  • Embodiments of the present application also provide a chip, which includes a memory and a processor.
  • the memory is used to store a computer program.
  • the processor is used to call and run the computer program from the memory, so that the device equipped with the chip executes the above various possible implementations. Methods.
  • the units in the equipment of the embodiments of this application can be merged, divided, and deleted according to actual needs.
  • the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation.
  • the technical solution of the present application can be embodied in the form of a software product in essence or that contributes to the existing technology.
  • the computer software product is stored in one of the above storage media (such as ROM/RAM, magnetic disk, optical disk), including several instructions to cause a terminal device (which can be a mobile phone, a computer, a server, a controlled terminal, or a network device, etc.) to execute the method of each embodiment of the present application.
  • a computer program product includes one or more computer instructions.
  • Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g., computer instructions may be transmitted from a website, computer, server or data center via a wired link (e.g.
  • Coaxial cable, optical fiber, digital subscriber line) or wireless means to transmit to another website, computer, server or data center.
  • Computer-readable storage media can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or other integrated media that contains one or more available media. Available media may be magnetic media (eg, floppy disks, storage disks, tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), etc.

Landscapes

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

Abstract

本申请公开了一种控制方法、通信设备及存储介质，该方法包括：响应于满足第一预设条件，终端根据网络设备下发的第二时间延迟预设时间接入网络。或者，响应于满足预设条件，终端根据预设策略延迟接入网络。由此，通过延迟接入网络，避免了IoT-NTN网络中大量UE集中接入导致RACH拥塞的问题，进而避免了在IoT-NTN网络中RACH拥塞，RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。

Description

控制方法、通信设备及存储介质
相关申请
本申请要求于2022年05月17日提交中国专利局、申请号为202210532039.2、发明名称为“控制方法、通信设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在申请中。
技术领域
本申请涉及通信技术领域，具体涉及一种控制方法、通信设备及存储介质。
背景技术
一些实现中，在UE RACH流程中，当网络拥塞时，网络通过RAR(随机接入响应)中携带的Backoff Indicator指示UE在[0,BackoffParameter Value]中选择一个时间延迟RACH(随机接入信道)尝试来缓解拥塞。
根据RAN2 116-e会议结论，对于IoT-NTN(物联网-非地面网络)Quasi-Earth Fixed satellites(伪地球固定卫星)场景，由于卫星移动，覆盖某个区域的卫星在到达特定时间点T1(即end-time of serving satellite’s coverage)时会停止服务，下个覆盖该区域的卫星的开始服务时间为T2(即start-time of incoming satellite’s coverage)，T1和T2通过SI(系统消息)广播，对该区域的所有UE生效。因此在该T2时间点可能存在大量UE尝试接入该卫星，导致RACH拥塞。
在构思及实现本申请过程中，发明人发现，对于NTN网络，由于覆盖范围更大，服务的终端更多，拥塞可能更严重。因此UE在RACH流程中可能需要多次尝试发送Random Access才能成功接入网络(即多次被网络设备下发Backoff Indicator来缓解拥塞)，由于上行同步定时器(Validity timer)一直在运行，以及NTN网络中大的传播时延，因此UE成功接入网络后剩余的有效时间内可能无法满足数据传输，在定时器超时后，UE需要重新获取required SI，导致业务中断。
即针对IoT NTN网络，现有机制无法保证在RACH拥塞时，在有限的时间内(Validity timer)使得UE成功接入网络并预留更多的时间供数据传输。
前面的叙述在于提供一般的背景信息，并不一定构成现有技术。
发明内容
针对上述技术问题，本申请提供一种控制方法、通信设备及存储介质，其中一个目的是解决在IoT-NTN网络中RACH拥塞，避免RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
本申请提供一种控制方法，可应用于通信设备(如手机)，包括以下步骤：
S10：响应于满足第一预设条件，终端根据网络设备下发的第二时间延迟预设时间接入网络。
可选地，所述满足第一预设条件，包括以下至少一种：
在第一时间前被网络释放，所述第一时间由所述网络设备下发；
在所述第二时间接入网络。
可选地，包括以下至少一种：
所述第一时间为网络设备覆盖当前服务区域的服务结束时间；
所述第二时间为下个网络设备覆盖当前服务区域的服务开始时间；
所述终端通过网络的RRC release消息释放。
可选地，所述RRC release消息携带的参数包括以下至少一种：时长T、特定原因值。
可选地，所述S10步骤包括：
确定所述预设时间。
可选地，所述确定所述预设时间的方式，包括以下至少一种：
根据第一时间范围确定或生成所述预设时间；
根据分组确定或生成所述预设时间。
可选地，所述根据第一时间范围确定或生成所述预设时间的步骤包括：
根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间，可选地，T为大于0的值，或者，所述T与当前负载关联。
可选地，所述S10步骤还包括：
响应于满足第二预设条件，确定不生效所述预设时间。
可选地，所述满足第二预设条件，包括以下至少一种：
RRC release消息未携带T值；
RRC release消息携带的T值为0；
RRC release消息携带的释放原因值不为特定原因值；
当前业务为预设的高优先级业务。
本申请还提供一种控制方法，可应用于通信设备(如手机)，所述方法包括以下步骤：
S100：响应于满足预设条件，终端根据预设策略延迟接入网络。
可选地，所述满足预设条件，包括：满足第一预设条件和/或满足第二预设条件。
可选地，所述满足第一预设条件包括以下至少一种：
终端在第一时间前被网络释放，所述第一时间由所述网络设备下发；
终端在所述第二时间接入网络，所述第二时间由所述网络设备下发。
可选地，包括以下至少一种：
所述第一时间为网络设备覆盖当前服务区域的服务结束时间；
所述第二时间为下个网络设备覆盖当前服务区域的服务开始时间；
所述终端通过网络的RRC release消息释放。
可选地，所述RRC release消息携带的参数包括以下至少一种：时长T、特定原因值。
可选地，所述满足第二预设条件包括以下至少一种：
RRC release消息携带T值；
RRC release消息携带的T值不为0；
RRC release消息携带的释放原因值为特定原因值；
当前业务不为预设的高优先级业务。
可选地，所述终端根据预设策略延迟接入网络，包括：
根据预设时间延迟接入网络。
可选地，所述方法还包括：
确定所述预设时间。
可选地，所述确定所述预设时间的方式，包括以下至少一种：
根据第一时间范围确定或生成所述预设时间；
根据分组确定或生成所述预设时间。
可选地，所述根据第一时间范围确定或生成所述预设时间的步骤包括：
根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间，可选地，T为大于0的值，或者，所述T与当前负载关联。
本申请还提供一种控制方法，可应用于通信设备(如卫星、基站或航空设备等网络设备)，所述方法包括以下步骤：
S101：网络设备下发第二时间，以供终端根据所述第二时间延迟预设时间接入网络。
可选地，所述方法还包括：
在第一时间来临前，所述网络设备下发RRC release消息释放所述终端。
可选地，所述RRC release消息携带的参数包括以下至少一种：时长T、特定原因值。
可选地，包括以下至少一种：
所述网络设备通过系统消息下发所述第一时间和/或第二时间；
所述第一时间为网络设备覆盖当前服务区域的服务结束时间；
所述第二时间为下个网络设备覆盖当前服务区域的服务开始时间。
可选地，所述终端确定所述预设时间的方式包括以下至少一种：
所述终端根据第一时间范围确定或生成所述预设时间；
所述终端根据分组确定或生成所述预设时间。
可选地，所述终端根据第一时间范围确定或生成所述预设时间的步骤包括：
所述终端根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间，可选地，T为大于0的值，或者，所述T与当前负载关联。
本申请还提供一种控制方法，可应用于通信设备(如卫星、基站或航空设备等网络设备)，所述方法包括以下步骤：
S1001：网络设备下发消息，以供终端根据所述消息及预设策略延迟接入网络。
可选地，所述S1001步骤包括：
网络设备下发第二时间，以供终端根据所述第二时间延迟预设时间接入网络。
可选地，所述S1001步骤还包括：
在第一时间来临前，网络设备下发RRC release消息释放所述终端。
可选地，所述RRC release消息携带的参数包括以下至少一种：时长T、特定原因值。
可选地，包括以下至少一种：
所述网络设备通过系统消息下发所述第一时间和/或第二时间；
所述第一时间为网络设备覆盖当前服务区域的服务结束时间；
所述第二时间为下个网络设备覆盖当前服务区域的服务开始时间。
可选地，所述终端确定所述预设时间的方式包括以下至少一种：
所述终端根据第一时间范围确定或生成所述预设时间；
所述终端根据分组确定或生成所述预设时间。
可选地，所述终端根据第一时间范围确定或生成所述预设时间的步骤包括：
所述终端根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间，可选地，T为大于0的值，或者，所述T与当前负载关联。
本申请还提供一种控制装置，该控制装置包括：
第一接入模块，用于响应于满足第一预设条件，根据网络设备下发的第二时间延迟预设时间接入网络。
本申请还提供一种控制装置，该控制装置包括：
第二接入模块，用于响应于满足预设条件，根据预设策略延迟接入网络。
本申请还提供一种控制装置，该控制装置包括：
第一发送模块，用于下发第二时间，以供终端根据所述第二时间延迟预设时间接入网络。
本申请还提供一种控制装置，本申请控制装置应用于网络设备，该控制装置包括：
第二发送模块，用于下发消息，以供终端根据所述消息及预设策略延迟接入网络。
本申请还提供一种通信设备，包括：存储器和处理器，所述存储器上存储有控制程序，所述控制程序被所述处理器执行时实现如上任一所述的控制方法的步骤。
本申请还提供一种计算机可读存储介质，所述存储介质上存储有控制程序，所述控制程序被处理器执行时实现如上述任一所述的控制方法的步骤。
本申请提出的控制方法包括：响应于满足第一预设条件，终端根据网络设备下发的第二时间延迟预设时间接入网络。或者，响应于满足预设条件，终端根据预设策略延迟接入网络。由此，通过延迟接入网络，避免了IoT-NTN网络中大量UE集中接入导致RACH拥塞的问题，进而避免了在IoT-NTN网络中RACH拥塞，RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本申请的实施例，并与说明书一起用于解释本申请的原理。为了更清楚地说明本申请实施例的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，对于本领域普通技术人员而言，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为实现本申请各个实施例的一种终端设备的硬件结构示意图；
图2为本申请实施例提供的一种通信网络系统架构图；
图3为本申请实施例提供的一种控制方法第一实施例的流程示意图；
图4为本申请实施例涉及的终端延迟接入的场景示意图；
图5为本申请实施例提供的一种控制方法的交互流程示意图；
图6为本申请实施例提供的一种控制方法第二实施例的流程示意图；
图7为本申请实施例提供的一种控制方法第三实施例的流程示意图；
图8为本申请实施例提供的一种控制方法第四实施例的流程示意图；
图9为本申请实施例提供的一种控制装置的功能模块示意图；
图10为本申请实施例提供的又一种控制装置的功能模块示意图；
图11为本申请实施例提供的又一种控制装置的功能模块示意图；
图12为本申请实施例提供的又一种控制装置的功能模块示意图。
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。通过上述附图，已示出本申请明确的实施例，后文中将有更详细的描述。这些附图和文字描述并不是为了通过任何方式限制本申请构思的范围，而是通过参考特定实施例为本领域技术人员说明本申请的概念。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
可选地，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素，可选地，本申请不同实施例中具有同样命名的部件、特征、要素可能具有相同含义，也可能具有不同含义，其具体含义需以其在该具体实施例中的解释或者进一步结合该具体实施例中上下文进行确定。
应当理解，尽管在本文可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本文范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语"如果"可以被解释成为"在……时"或"当……时"或"响应于确定"。再者，如同在本文中所使用的，单数形式“一”、“一个”和“该”旨在也包括复数形式，除非上下文中有相反的指示。应当进一步理解，术语“包含”、“包括”表明存在所述的特征、步骤、操作、元件、组件、项目、种类、和/或组，但不排除一个或多个其他特征、步骤、操作、元件、组件、项目、种类、和/或组的存在、出现或添加。本申请使用的术语“或”、“和/或”、“包括以下至少一个”等可被解释为包括性的，或意味着任一个或任何组合。例如，“包括以下至少一个：A、B、C”意味着“以下任一个：A；B；C；A和B；A和C；B和C；A和B和C”，再如，“A、B或C”或者“A、B和/或C”意味着“以下任一个：A；B；C；A和B；A和C；B和C；A和B和C”。仅当元件、功能、步 骤或操作的组合在某些方式下内在地互相排斥时，才会出现该定义的例外。
应该理解的是，虽然本申请实施例中的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，其可以以其他的顺序执行。而且，图中的至少一部分步骤可以包括多个子步骤或者多个阶段，这些子步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，其执行顺序也不必然是依次进行，而是可以与其他步骤或者其他步骤的子步骤或者阶段的至少一部分轮流或者交替地执行。
取决于语境，如在此所使用的词语“如果”、“若”可以被解释成为“在……时”或“当……时”或“响应于确定”或“响应于检测”。类似地，取决于语境，短语“如果确定”或“如果检测(陈述的条件或事件)”可以被解释成为“当确定时”或“响应于确定”或“当检测(陈述的条件或事件)时”或“响应于检测(陈述的条件或事件)”。
需要说明的是，在本文中，采用了诸如S10、S20等步骤代号，其目的是为了更清楚简要地表述相应内容，不构成顺序上的实质性限制，本领域技术人员在具体实施时，可能会先执行S20后执行S10等，但这些均应在本申请的保护范围之内。
应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
在后续的描述中，使用用于表示元件的诸如“模块”、“部件”或者“单元”的后缀仅为了有利于本申请的说明，其本身没有特定的意义。因此，“模块”、“部件”或者“单元”可以混合地使用。
在本申请中，通信设备可以为终端设备，也可以为卫星、基站或航空设备等网络设备，需要根据具体上下文来加以确定，若为终端设备，则终端设备可以以各种形式来实施。例如，本申请中描述的终端设备可以包括诸如手机、平板电脑、笔记本电脑、掌上电脑、个人数字助理(Personal Digital Assistant，PDA)、便捷式媒体播放器(Portable Media Player，PMP)、导航装置、可穿戴设备、智能手环、计步器等终端设备，以及诸如基站、数字TV、台式计算机等固定终端。若为网络设备，网络设备可以是基站或卫星或航空设备等，例如低轨通信卫星、高空平台和无人机等。本申请实施例中，用于实现网络设备功能的装置可以是网络设备本身，也可以是能够支持网络设备实现该功能的装置，例如芯片系统或可实现网络设备功能的组合器件、部件，该装置可以被安装在网络设备中。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。
后续描述中将以终端设备为例进行说明，本领域技术人员将理解的是，除了特别用于移动目的的元件之外，根据本申请的实施方式的构造也能够应用于固定类型的终端。
请参阅图1，其为实现本申请各个实施例的一种终端设备的硬件结构示意图，该终端设备100可以包括：RF(Radio Frequency，射频)单元101、WiFi模块102、音频输出单元103、A/V(音频/视频)输入单元104、传感器105、显示单元106、用户输入单元107、接口单元108、存储器109、处理器110、以及电源111等部件。本领域技术人员可以理解，图1中示出的终端设备结构并不构成对终端设备的限定，终端设备可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
下面结合图1对终端设备的各个部件进行具体的介绍：
射频单元101可用于收发信息或通话过程中，信号的接收和发送，具体的，将基站的下行信息接收后，给处理器110处理；另外，将上行的数据发送给基站。通常，射频单元101包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。可选地，射频单元101还可以通过无线通信与网络和其他设备通信。上述无线通信可以使用任一通信标准或协议，包括但不限于GSM(Global System of Mobile communication，全球移动通讯系统)、GPRS(General Packet Radio Service，通用分组无线服务)、CDMA2000(Code Division Multiple Access 2000，码分多址2000)、WCDMA(Wideband Code Division Multiple Access,宽带码分多址)、TD-SCDMA(Time Division-Synchronous Code Division Multiple Access，时分同步码分多址)、FDD-LTE(Frequency Division Duplexing-Long Term Evolution，频分双工长期演进)、TDD-LTE(Time Division Duplexing-Long Term Evolution，分时双工长期演进)和5G等。
WiFi属于短距离无线传输技术，终端设备100通过WiFi模块102可以帮助用户收发电子邮件、浏览网页和访问流式媒体等，它为用户提供了无线的宽带互联网访问。虽然图1示出了WiFi模块102，但是可以理解的是，其并不属于终端设备的必须构成，完全可以根据需要在不改变发明的本质的范围内而省略。
音频输出单元103可以在终端设备100处于呼叫信号接收模式、通话模式、记录模式、语音识别模式、广播接收模式等等模式下时，将射频单元101或WiFi模块102接收的或者在存储器109中存储的音频数据转换成音频信号并且输出为声音。而且，音频输出单元103还可以提供与终端设备100执行的特定功能相关的音频输出(例如，呼叫信号接收声音、消息接收声音等等)。音频输出单元103可以包括扬声器、蜂鸣器等等。
A/V输入单元104用于接收音频或视频信号。A/V输入单元104可以包括图形处理器(Graphics Processing Unit，GPU)1041和麦克风1042，图形处理器1041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元106上。经图形处理器1041处理后的图像帧可以存储在存储器109(或其它存储介质)中或者经由射频单 元101或WiFi模块102进行发送。麦克风1042可以在电话通话模式、记录模式、语音识别模式等等运行模式中经由麦克风1042接收声音(音频数据)，并且能够将这样的声音处理为音频数据。处理后的音频(语音)数据可以在电话通话模式的情况下转换为可经由射频单元101发送到移动通信基站的格式输出。麦克风1042可以实施各种类型的噪声消除(或抑制)算法以消除(或抑制)在接收和发送音频信号的过程中产生的噪声或者干扰。
终端设备100还包括至少一种传感器105，比如光传感器、运动传感器以及其他传感器。可选地，光传感器包括环境光传感器及接近传感器，可选地，环境光传感器可根据环境光线的明暗来调节显示面板1061的亮度，接近传感器可在终端设备100移动到耳边时，关闭显示面板1061和/或背光。作为运动传感器的一种，加速计传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别手机姿态的应用(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；至于手机还可配置的指纹传感器、压力传感器、虹膜传感器、分子传感器、陀螺仪、气压计、湿度计、温度计、红外线传感器等其他传感器，在此不再赘述。
显示单元106用于显示由用户输入的信息或提供给用户的信息。显示单元106可包括显示面板1061，可以采用液晶显示器(Liquid Crystal Display，LCD)、有机发光二极管(Organic Light-Emitting Diode,OLED)等形式来配置显示面板1061。
用户输入单元107可用于接收输入的数字或字符信息，以及产生与终端设备的用户设置以及功能控制有关的键信号输入。可选地，用户输入单元107可包括触控面板1071以及其他输入设备1072。触控面板1071，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板1071上或在触控面板1071附近的操作)，并根据预先设定的程式驱动相应的连接装置。触控面板1071可包括触摸检测装置和触摸控制器两个部分。可选地，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器110，并能接收处理器110发来的命令并加以执行。可选地，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板1071。除了触控面板1071，用户输入单元107还可以包括其他输入设备1072。可选地，其他输入设备1072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆等中的一种或多种，具体此处不做限定。
可选地，触控面板1071可覆盖显示面板1061，当触控面板1071检测到在其上或附近的触摸操作后，传送给处理器110以确定触摸事件的类型，随后处理器110根据触摸事件的类型在显示面板1061上提供相应的视觉输出。虽然在图1中，触控面板1071与显示面板1061是作为两个独立的部件来实现终端设备的输入和输出功能，但是在某些实施例中，可以将触控面板1071与显示面板1061集成而实现终端设备的输入和输出功能，具体此处不做限定。
接口单元108用作至少一个外部装置与终端设备100连接可以通过的接口。例如，外部装置可以包括有线或无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(I/O)端口、视频I/O端口、耳机端口等等。接口单元108可以用于接收来自外部装置的输入(例如，数据信息、电力等等)并且将接收到的输入传输到终端设备100内的一个或多个元件或者可以用于在终端设备100和外部装置之间传输数据。
存储器109可用于存储软件程序以及各种数据。存储器109可主要包括存储程序区和存储数据区，可选地，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。可选地，存储器109可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器110是终端设备100的控制中心，利用各种接口和线路连接整个终端设备100的各个部分，通过运行或执行存储在存储器109内的软件程序和/或模块，以及调用存储在存储器109内的数据，执行终端设备100的各种功能和处理数据，从而对终端设备100进行整体监控。处理器110可包括一个或多个处理单元；优选的，处理器110可集成应用处理器和调制解调处理器，可选地，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器110中。
终端设备100还可以包括给各个部件供电的电源111(比如电池)，优选的，电源111可以通过电源管理系统与处理器110逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
尽管图1未示出，终端设备100还可以包括蓝牙模块等，在此不再赘述。
为了便于理解本申请实施例，下面对本申请的终端设备所基于的通信网络系统进行描述。
请参阅图2，图2为本申请实施例提供的一种通信网络系统架构图，该通信网络系统为通用移动通信技术的LTE系统，该LTE系统包括依次通讯连接的UE(User Equipment，用户设备)201，E-UTRAN(Evolved UMTS Terrestrial Radio Access Network，演进式UMTS陆地无线接入网)202，EPC(Evolved Packet Core，演进式分组核心网)203和运营商的IP业务204。
可选地，UE201可以是上述终端设备100，此处不再赘述。
E-UTRAN202包括eNodeB2021和其它eNodeB2022等。可选地，eNodeB2021可以通过回程(backhaul)(例如X2接口)与其它eNodeB2022连接，eNodeB2021连接到EPC203，eNodeB2021可以提供UE201到EPC203的接入。
EPC203可以包括MME(Mobility Management Entity，移动性管理实体)2031，HSS(Home Subscriber Server，归属用户服务器)2032，其它MME2033，SGW(Serving Gate Way，服务网关)2034，PGW(PDN Gate Way，分组数据网络网关)2035和PCRF(Policy and Charging Rules Function，政策和资费功能实体)2036等。可选地，MME2031是处理UE201和EPC203之间信令的控制节点，提供承载和连接管理。HSS2032用于提供一些寄存器来管理诸如归属位置寄存器(图中未示)之类的功能，并且保存有一些有关服务特征、数据速率等用户专用的信息。所有用户数据都可以通过SGW2034进行发送，PGW2035可以提供UE 201的IP地址分配以及其它功能，PCRF2036是业务数据流和IP承载资源的策略与计费控制策略决策点，它为策略与计费执行功能单元(图中未示)选择及提供可用的策略和计费控制决策。
IP业务204可以包括因特网、内联网、IMS(IP Multimedia Subsystem，IP多媒体子系统)或其它IP业务等。
虽然上述以LTE系统为例进行了介绍，但本领域技术人员应当知晓，本申请不仅仅适用于LTE系统，也可以适用于其他无线通信系统，例如GSM、CDMA2000、WCDMA、TD-SCDMA以及未来新的网络系统(如5G)等，此处不做限定。
本申请实施例涉及的技术术语包括：
UE:User equipment，终端，终端设备；
RACH:Random Access CHannel，随机接入信道；
RAR：Random access response，随机接入响应；
SI:System information，系统消息；
TN:Terrestrial Network，地面网络；
NTN:Non-Terrestrial Network，非地面网络；
IoT-NTN:Internet of Things-Non-Terrestrial Network，物联网-非地面网络；
NB-IoT:Narrow Band Internet of Things，窄带物联网；
Quasi-earth fixed cell:An NTN cell fixed with respect to a certain geographic area on the earth during a certain time duration.This can be provided by beam(s)covering one geographic area for a finite period and a different geographic area during another period.伪地球固定小区，指在某一段时间内固定于地球某一地理区域的NTN小区。
请参照图3，图3为本申请控制方法第一实施例的流程示意图。在本实施例中，本申请控制方法可应用于如上所述的终端设备(以下简称终端)，比如UE，该终端与所处网络通信系统中网络设备之间建立通信连接，该网络设备可以是基站或卫星或航空设备等，例如低轨通信卫星、高空平台和无人机等。本申请实施例中，用于实现网络设备功能的装置可以是网络设备本身，也可以是能够支持网络设备实现该功能的装置，例如芯片系统或可实现网络设备功能的组合器件、部件，该装置可以被安装在网络设备中。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。
本实施例以卫星与终端(UE)的通信实现方案进行举例。
如图3所示，本申请第一实施例提出一种控制方法，本申请控制方法包括以下步骤：
S10：响应于满足第一预设条件，终端根据网络设备下发的第二时间延迟预设时间接入网络。
本实施例考虑到：针对IoT-NTN网络，现有机制无法保证在RACH拥塞时，在有限的时间内(Validity timer)使得UE成功接入网络并预留更多的时间供数据传输。因此，本申请提出解决方案，可以避免IoT-NTN网络中RACH拥塞，进而避免RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
可选地，如前所述，根据RAN2 116-e会议结论，对于IoT-NTN Quasi-Earth Fixed satellites场景，由于卫星移动，覆盖某个区域的卫星在到达特定时间点T1(即end-time of serving satellite’s coverage)时会停止服务，下个覆盖该区域的卫星的开始服务时间为T2(即start-time of incoming satellite’s coverage)，T1和T2通过SI(系统消息)广播，对该区域的所有UE生效。
参照图4，图4为本申请实施例涉及的终端延迟接入的场景示意图。
如图4所示，当前服务卫星通过系统消息广播第一时间T1(即end-time of serving satellite’s coverage)、第二时间T2(即start-time of incoming satellite’s coverage)。
可选地，第一时间T1为网络设备覆盖当前服务区域的服务结束时间；第二时间T2为下个网络设备覆盖当前服务区域的服务开始时间。以网络设备为卫星进行举例，第一时间T1为覆盖当前网络服务区域卫星的服务结束时间；第二时间T2为下个覆盖当前网络服务区域卫星的服务开始时间。
T1和T2通过SI(系统消息)广播，对该区域的所有UE生效，因此在该T2时间点可能存在大量UE 尝试接入该卫星，导致RACH拥塞。
在本实施例中，对于尝试在T2时刻接入网络的UE，在该T2时刻的基础上，延迟预设时间delay接入，即UE会在T2+delay时间点来尝试获取required SI并接入网络，确保各UE接入网络的时间离散化，避免RACH拥塞，进而避免了RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
在本实施例中，终端响应于满足第一预设条件，根据网络设备下发的第二时间延迟预设时间接入网络。
由此，通过上述方案，可以避免IoT-NTN网络中RACH拥塞，进而避免RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
可选地，所述满足第一预设条件，包括以下至少一种：
终端在第一时间前被网络释放；
终端在第二时间接入网络。
可选地，网络通过SI(系统消息)向终端(UE)下发上述第一时间T1和第二时间T2，终端根据网络设备下发的第二时间T2延迟预设时间接入网络。
可选地，终端在第一时间前被网络释放，可以采用如下方案：
网络向终端下发RRC release消息，终端通过网络设备下发的RRC release消息释放。
可选地，网络设备下发的RRC release消息携带的参数可以包括以下至少一种：时长T、特定原因值，可选地，特定原因值比如coverage discontinuity，表明释放是因为当前卫星即将停止服务。
可选地，所述S10步骤可以包括：终端确定所述预设时间。
终端响应于满足第一预设条件，确定预设时间，并根据网络设备下发的第二时间延迟预设时间接入网络。
可选地，终端确定所述预设时间的方式，可以包括以下至少一种：
第一种方式：终端根据第一时间范围确定或生成所述预设时间；
可选地，终端可以根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间。
可选地，T为大于0的值。T值不能超过卫星服务时间。
可选地，T可以为固定值。
可选地，T可与当前小区负载有关，比如，负载越高T越大。
第二种方式：终端根据分组和预设时间粒度确定或生成所述预设时间。
可选地，所述分组的个数及预设时间粒度可由网络根据当前负载以及随机接入信道RACH容量来决定，并下发给UE。
可选地，所述S10步骤还可以包括：
终端响应于满足第二预设条件，确定不生效所述预设时间。
可选地，所述满足第二预设条件，包括以下至少一种：
第一种情况，RRC release消息未携带T值；
第二种情况，RRC release消息携带的T值为0；
第三种情况，RRC release消息携带的释放原因值不为特定原因值；
即如果RRC release未携带T值或T值为0时或释放原因不为discontinue coverage等特定原因值，则该UE不生效delay。
第四种情况，当前业务为预设的高优先级业务，比如当前UE为紧急呼叫等高优先级业务，则不生效delay。
可选地，结合图4所示，当前服务卫星通过系统消息广播T1(即end-time of serving satellite’s coverage)、T2(即start-time of incoming satellite’s coverage)。
对于尝试在T2时刻接入网络的UE，在该T2的基础上，延迟delay接入，即UE会在T2+delay时间点来尝试获取required SI并接入网络，确保各UE接入网络的时间离散化，避免RACH拥塞。
可选地，UE和对应的delay可以按如下方法确定：
Option a:
该UE为网络通过RRC release消息释放的UE，且RRC release消息携带特定原因值cause，比如coverage discontinuity，表明释放是因为当前卫星即将停止服务。
RRC release消息携带一个时长T,则delay＝random(0,T),即各UE在0～T范围内随机选择一个时间延时接入。
Option b:
该UE为网络通过RRC release消息释放的UE，且RRC release消息携带特定原因值cause，比如coverage discontinuity，表明释放是因为当前卫星即将停止服务。
将UE分成N组(如根据UE标识进行分组，UEID mod N)，延迟delta，N和delta由网络设备下发，则各组UE延迟接入时间为(UEID mod N)*delta。
可选地，N和delta可由网络根据当前负载以及RACH容量来决定，比如delta可为当前配置的RACH周期。
Option c:
该UE为所有尝试在T2时刻接入网络的UE。
网络设备下发RRC release消息，RRC release消息携带一个时长T，则delay＝random(0,T),即各UE在0～T范围内随机选择一个时间延时接入。
Option d:
该UE为所有尝试在T2时刻接入网络的UE。
将UE分成N组(如根据UE标识进行分组，UEID mod N)，延迟delta，N和delta由网络设备下发，则各组UE延迟接入时间为(UEID mod N)*delta。N和delta可由网络根据当前负载以及RACH容量来决定，比如delta可为当前配置的RACH周期。
本实施例通过上述方案，响应于满足第一预设条件，终端根据网络设备下发的第二时间延迟预设时间接入网络。由此，通过终端延迟预设时间接入网络，避免了IoT-NTN网络中大量UE集中接入导致RACH拥塞的问题，进而避免了在IoT-NTN网络中RACH拥塞，RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
假设有服务区域a，Satellite1(卫星1)，Satellite2(卫星2)，以下对不同场景的实现方案进行详细阐述：
第一种场景：
Satellite1(卫星1)在当前时间服务区域a，并通过系统消息广播T1、T2,UE接收T1和T2。
在T1时刻来临前，由于satellite1即将停止服务，将所有处于connected mode UE通过RRC Release消息释放掉，RRC release消息携带释放原因值discontinue coverage以及时间T。
Satellite2(卫星2)将在T2时间点服务区域a，对于被释放原因值为discontinue coverage且尝试在T2时间点接入该Satellite2的UE，延迟delay时间接入，delay＝random(0,T).比如假设T＝10s,当前网络存在10个UE尝试接入Satellite2，则各UE接入网络时间可能为如下表1所示：
表1
可选地，T值可固定，也可与当前小区负载有关，负载越高T越大。T值不能超过卫星服务时间。
可选地，如果RRC release未携带T值或T值为0时或释放原因不为discontinue coverage，则该UE不生效delay。
可选地，如果当前UE为紧急呼叫等高优先级业务，则不生效delay。
第二种场景：
Satellite1在当前时间服务区域a，并通过系统消息广播T1、T2,UE接收T1和T2。
在T1时刻来临前，satellite1将所有处于connected mode UE通过RRC Release消息释放掉，RRC release消息携带释放原因值discontinue coverage。
Satellite2将在T2时间点服务区域a，对于被释放原因值为discontinue coverage且尝试在T2时间点接入该Satellite2的UE，按照所属分组index，延迟delay时间接入。
其中，index＝UEID mod N,各UE delay时间为delay＝index*delta。
其中，N为分组个数，delta为预设时间粒度，UE delay时间不能超过卫星服务时间。
比如假设N＝10,当前网络存在100个UE尝试接入Satellite2，则各UE接入网络时间可能为如下表2所示(理想情况下各组UE分布个数相同)：
表2

可选地，如果当前UE为紧急呼叫等高优先级业务，则不生效delay。
第三种场景：
Satellite1在当前时间服务区域a,并通过系统消息广播T1、T2和T,UE接收T1,T2,T。
Satellite2将在T2时间点服务区域a,对于尝试在T2时间点接入该Satellite2的所有UE，延迟delay时间接入，delay＝random(0,T)。
比如假设T＝10s,当前网络存在10个UE尝试接入Satellite2，则各UE接入网络时间可能为如下表3所示：
表3
可选地，如果当前UE为紧急呼叫等高优先级业务，则不生效delay。
第四种场景：
Satellite1在当前时间服务区域a,并通过系统消息广播T1、T2,UE接收T1和T2。
Satellite2将在T2时间点服务区域a,对于尝试在T2时间点接入该Satellite2的所有UE，按照所属分组index，延迟delay时间接入。
其中，index＝UEID mod N,各UE delay时间为delay＝index*delta、
其中，N为分组个数，delta为预设时间粒度，UE delay时间不能超过卫星服务时间。
比如假设N＝10,当前网络存在100个UE尝试接入Satellite2，则各UE接入网络时间可能为如下表4所示(理想情况下各组UE分布个数相同)：
表4

可选地，如果当前UE为紧急呼叫等高优先级业务，则不生效delay。
本实施例通过上述方案，响应于满足第一预设条件，终端根据网络设备下发的第二时间延迟预设时间接入网络。由此，通过终端延迟预设时间接入网络，避免了IoT-NTN网络中大量UE集中接入导致RACH拥塞的问题，进而避免了在IoT-NTN网络中RACH拥塞，RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
本实施例中网络设备与终端(UE)通信的实现拥塞控制的流程可以参照图5所示。
如图5所示，主要交互流程包括：
步骤A：网络设备下发消息，以供终端根据所述消息及预设策略延迟接入网络；
步骤A1：网络设备通过系统消息下发第一时间和/或第二时间；
步骤A2：网络侧在第一时间前下发RRC release消息释放终端；
步骤B：响应于满足预设条件，终端根据预设策略延迟接入网络；
步骤B1：响应于满足第一预设条件，终端根据网络设备下发的第二时间延迟预设时间接入网络。
步骤B2：终端确定所述预设时间。
步骤B21：终端根据第一时间范围确定或生成所述预设时间；或者终端根据分组和预设时间粒度确定或生成所述预设时间。
具体交互控制流程，可以参照上述各实施例，在此不再赘述。
本实施例通过上述方案，响应于满足第一预设条件，终端根据网络设备下发的第二时间延迟预设时间接入网络，或者供终端根据网络设备下发的消息，以及预设策略延迟接入网络。由此，通过终端延迟预设时间接入网络，避免了IoT-NTN网络中大量UE集中接入导致RACH拥塞的问题，进而避免了在IoT-NTN网络中RACH拥塞，RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
如图6所示，本申请第二实施例提出一种控制方法，所述方法可应用于终端侧，本申请控制方法包括以下步骤：
S100：响应于满足预设条件，终端根据预设策略延迟接入网络。
本实施例终端与所处网络通信系统中网络设备之间建立通信连接，该网络设备可以是基站或卫星或航空设备等，例如低轨通信卫星、高空平台和无人机等。本申请实施例中，用于实现网络设备功能的装置可以是网络设备本身，也可以是能够支持网络设备实现该功能的装置，例如芯片系统或可实现网络设备功能的组合器件、部件，该装置可以被安装在网络设备中。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。
本实施例以卫星与终端(UE)的通信实现方案进行举例。
本实施例考虑到：针对IoT-NTN网络，现有机制无法保证在RACH拥塞时，在有限的时间内(Validity timer)使得UE成功接入网络并预留更多的时间供数据传输。因此，本申请提出解决方案，可以避免IoT-NTN网络中RACH拥塞，进而避免RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
可选地，如前所述，根据RAN2 116-e会议结论，对于IoT-NTN Quasi-Earth Fixed satellites场景，由于卫星移动，覆盖某个区域的卫星在到达特定时间点T1(即end-time of serving satellite’s coverage)时会停止服务，下个覆盖该区域的卫星的开始服务时间为T2(即start-time of incoming satellite’s coverage)，T1和T2通过SI(系统消息)广播，对该区域的所有UE生效。
参照图4，图4为本申请实施例涉及的终端延迟接入的场景示意图。
如图4所示，当前服务卫星通过系统消息广播第一时间T1(即end-time of serving satellite’s coverage)、第二时间T2(即start-time of incoming satellite’s coverage)。
可选地，第一时间T1为网络设备覆盖当前服务区域的服务结束时间；第二时间T2为下个网络设备覆盖当前服务区域的服务开始时间。以网络设备为卫星进行举例，第一时间T1为覆盖当前网络服务区域卫星的服务结束时间；第二时间T2为下个覆盖当前网络服务区域卫星的服务开始时间。
T1和T2通过SI(系统消息)广播，对该区域的所有UE生效，因此在该T2时间点可能存在大量UE尝试接入该卫星，导致RACH拥塞。
在本实施例中，对于尝试在T2时刻接入网络的UE，在该T2时刻的基础上，延迟预设时间delay接入，即UE会在T2+delay时间点来尝试获取required SI并接入网络，确保各UE接入网络的时间离散化，避免RACH拥塞，进而避免了RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
在本实施例中，终端响应于满足预设条件，根据预设策略延迟接入网络。
可选地，所述满足预设条件，可以包括：满足第一预设条件和/或满足第二预设条件。
可选地，所述满足第一预设条件包括以下至少一种：
终端在第一时间前被网络释放；
终端在所述第二时间接入网络。
可选地，网络通过SI(系统消息)向终端(UE)下发上述第一时间T1和第二时间T2，终端根据网络设备下发的第二时间T2延迟预设时间接入网络。
可选地，终端在第一时间前被网络释放，可以采用如下方案：
网络向终端下发RRC release消息，终端通过网络设备下发的RRC release消息释放。
可选地，网络设备下发的RRC release消息携带的参数可以包括以下至少一种：时长T、特定原因值，可选地，特定原因值比如coverage discontinuity，表明释放是因为当前卫星即将停止服务。
可选地，所述满足第二预设条件可以包括以下至少一种：
第一种情况，RRC release消息携带T值；
第二种情况，RRC release消息携带的T值不为0；
第三种情况，RRC release消息携带的释放原因值为特定原因值；
即如果RRC release未携带T值或T值为0时或释放原因不为discontinue coverage等特定原因值，则不满足第二预设条件，该UE不生效delay。
第四种情况，当前业务不为预设的高优先级业务，比如当前UE为紧急呼叫等高优先级业务，则不满足第二预设条件，该UE不生效delay。
可选地，终端响应于满足上述第一预设条件和/或满足上述第二预设条件，根据预设策略延迟接入网络。
可选地，所述终端根据预设策略延迟接入网络，包括：
终端根据预设时间延迟接入网络。
可选地，所述方法还包括：
终端确定所述预设时间。
可选地，终端响应于满足第一预设条件和/或满足第二预设条件，确定预设时间，并根据网络设备下发的第二时间延迟预设时间接入网络。
可选地，终端确定所述预设时间的方式，可以包括以下至少一种：
第一种方式：终端根据第一时间范围确定或生成所述预设时间；
可选地，终端可以根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间。
可选地，T为大于0的值。T值不能超过卫星服务时间。
可选地，T可以为固定值。
可选地，T可与当前小区负载有关，比如，负载越高T越大。
第二种方式：终端根据分组和预设时间粒度确定或生成所述预设时间。
可选地，所述分组的个数及预设时间粒度可由网络根据当前负载以及随机接入信道RACH容量来决定，并下发给UE。
可选地，结合图4所示，当前服务卫星通过系统消息广播T1(即end-time of serving satellite’s coverage)、T2(即start-time of incoming satellite’s coverage)。
对于尝试在T2时刻接入网络的UE，在该T2的基础上，延迟delay接入，即UE会在T2+delay时间点来尝试获取required SI并接入网络，确保各UE接入网络的时间离散化，避免RACH拥塞。
可选地，UE和对应的delay可以按如下方法确定：
Option a:
该UE为网络通过RRC release消息释放的UE，且RRC release消息携带特定原因值cause，比如coverage discontinuity，表明释放是因为当前卫星即将停止服务。
RRC release消息携带一个时长T,则delay＝random(0,T),即各UE在0～T范围内随机选择一个时间延时接入。
Option b:
该UE为网络通过RRC release消息释放的UE，且RRC release消息携带特定原因值cause，比如coverage discontinuity，表明释放是因为当前卫星即将停止服务。
将UE分成N组(如根据UE标识进行分组，UEID mod N)，延迟delta，N和delta由网络设备下发，则各组UE延迟接入时间为(UEID mod N)*delta。
可选地，N和delta可由网络根据当前负载以及RACH容量来决定，比如delta可为当前配置的RACH周期。
Option c:
该UE为所有尝试在T2时刻接入网络的UE。
网络设备下发RRC release消息，RRC release消息携带一个时长T，则delay＝random(0,T),即各UE在0～T范围内随机选择一个时间延时接入。
Option d:
该UE为所有尝试在T2时刻接入网络的UE。
将UE分成N组(如根据UE标识进行分组，UEID mod N)，延迟delta，N和delta由网络设备下发，则各组UE延迟接入时间为(UEID mod N)*delta。N和delta可由网络根据当前负载以及RACH容量来决定，比如delta可为当前配置的RACH周期。
本实施例通过上述方案，响应于满足预设条件，终端根据预设策略延迟接入网络。由此，通过延迟接入网络，避免了IoT-NTN网络中大量UE集中接入导致RACH拥塞的问题，进而避免了在IoT-NTN网络中RACH拥塞，RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
假设有服务区域a，Satellite1(卫星1)，Satellite2(卫星2)，以下对不同场景的实现方案进行详细阐述：
第一种场景：
Satellite1(卫星1)在当前时间服务区域a，并通过系统消息广播T1、T2,UE接收T1和T2。
在T1时刻来临前，由于satellite1即将停止服务，将所有处于connected mode UE通过RRC Release消息释放掉，RRC release消息携带释放原因值discontinue coverage以及时间T。
Satellite2(卫星2)将在T2时间点服务区域a，对于被释放原因值为discontinue coverage且尝试在T2时间点接入该Satellite2的UE，延迟delay时间接入，delay＝random(0,T).比如假设T＝10s,当前网络存在10个UE尝试接入Satellite2，则各UE接入网络时间可能为如上表1所示。
可选地，T值可固定，也可与当前小区负载有关，负载越高T越大。T值不能超过卫星服务时间。
可选地，如果RRC release未携带T值或T值为0时或释放原因不为discontinue coverage，则该UE不生效delay。
可选地，如果当前UE为紧急呼叫等高优先级业务，则不生效delay。
第二种场景：
Satellite1在当前时间服务区域a，并通过系统消息广播T1、T2,UE接收T1和T2。
在T1时刻来临前，satellite1将所有处于connected mode UE通过RRC Release消息释放掉，RRC release消息携带释放原因值discontinue coverage。
Satellite2将在T2时间点服务区域a，对于被释放原因值为discontinue coverage且尝试在T2时间点接入该Satellite2的UE，按照所属分组index，延迟delay时间接入。
其中，index＝UEID mod N,各UE delay时间为delay＝index*delta。
其中，N为分组个数，delta为预设时间粒度，UE delay时间不能超过卫星服务时间。
比如假设N＝10,当前网络存在100个UE尝试接入Satellite2，则各UE接入网络时间可能为如上表2所示(理想情况下各组UE分布个数相同)。
可选地，如果当前UE为紧急呼叫等高优先级业务，则不生效delay。
第三种场景：
Satellite1在当前时间服务区域a,并通过系统消息广播T1、T2和T,UE接收T1,T2,T。
Satellite2将在T2时间点服务区域a,对于尝试在T2时间点接入该Satellite2的所有UE，延迟delay时间接入，delay＝random(0,T)。
比如假设T＝10s,当前网络存在10个UE尝试接入Satellite2，则各UE接入网络时间可能为如上表3所示。
可选地，如果当前UE为紧急呼叫等高优先级业务，则不生效delay。
第四种场景：
Satellite1在当前时间服务区域a,并通过系统消息广播T1、T2,UE接收T1和T2。
Satellite2将在T2时间点服务区域a,对于尝试在T2时间点接入该Satellite2的所有UE，按照所属分组index，延迟delay时间接入。
其中，index＝UEID mod N,各UE delay时间为delay＝index*delta、
其中，N为分组个数，delta为预设时间粒度，UE delay时间不能超过卫星服务时间。
比如假设N＝10,当前网络存在100个UE尝试接入Satellite2，则各UE接入网络时间可能为如上表4所示(理想情况下各组UE分布个数相同)。
可选地，如果当前UE为紧急呼叫等高优先级业务，则不生效delay。
本实施例通过上述方案，响应于满足第一预设条件，终端根据网络设备下发的第二时间延迟预设时间接入网络。由此，通过终端延迟预设时间接入网络，避免了IoT-NTN网络中大量UE集中接入导致RACH拥塞的问题，进而避免了在IoT-NTN网络中RACH拥塞，RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
本实施例中网络设备与终端(UE)通信实现拥塞控制的流程，可以参照图5所示，在此不再赘述。
如图7所示，本申请第三实施例提出一种控制方法，所述方法可应用于网络设备，所述控制方法包括以下步骤：
S101：网络设备下发第二时间，以供终端根据所述第二时间延迟预设时间接入网络。
本实施例终端与网络设备之间建立通信连接，该网络设备可以是基站或卫星或航空设备等，例如低轨通信卫星、高空平台和无人机等。本申请实施例中，用于实现网络设备功能的装置可以是网络设备本身，也可以是能够支持网络设备实现该功能的装置，例如芯片系统或可实现网络设备功能的组合器件、部件，该装置可以被安装在网络设备中。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。
本实施例以卫星与终端(UE)的通信实现方案进行举例。
本实施例考虑到：针对IoT-NTN网络，现有机制无法保证在RACH拥塞时，在有限的时间内(Validity timer)使得UE成功接入网络并预留更多的时间供数据传输。因此，本申请提出解决方案，可以避免IoT-NTN网络中RACH拥塞，进而避免RACH占用过多时间而导致在上行同步有效时间内数据传输的时间不足可用于数据传输的时间不足，导致业务中断的问题。
根据RAN2 116-e会议结论，对于IoT-NTN Quasi-Earth Fixed satellites场景，由于卫星移动，覆盖某个区域的卫星在到达特定时间点T1(即end-time of serving satellite’s coverage)时会停止服务，下个覆盖该区域的卫星的开始服务时间为T2(即start-time of incoming satellite’s coverage)，T1和T2通过SI(系统消息)广播，对该区域的所有UE生效。
参照图4，图4为本申请实施例涉及的终端延迟接入的场景示意图。
如图4所示，当前服务卫星通过系统消息广播第一时间T1(即end-time of serving satellite’s coverage)、第二时间T2(即start-time of incoming satellite’s coverage)。
可选地，第一时间T1为网络设备覆盖当前服务区域的服务结束时间；第二时间T2为下个网络设备覆盖当前服务区域的服务开始时间。以网络设备为卫星进行举例，第一时间T1为覆盖当前网络服务区域卫星的服务结束时间；第二时间T2为下个覆盖当前网络服务区域卫星的服务开始时间。
T1和T2通过SI(系统消息)广播，对该区域的所有UE生效，因此在该T2时间点可能存在大量UE尝试接入该卫星，导致RACH拥塞。
在本实施例中，对于尝试在T2时刻接入网络的UE，在该T2时刻的基础上，延迟预设时间delay接入，即UE会在T2+delay时间点来尝试获取required SI并接入网络，确保各UE接入网络的时间离散化，避免RACH拥塞，进而避免了RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
在本实施例中，网络设备下发第二时间，以供终端根据所述第二时间延迟预设时间接入网络。
终端响应于满足第一预设条件，根据网络设备下发的第二时间延迟预设时间接入网络。
由此，通过上述方案，可以避免IoT-NTN网络中RACH拥塞，进而避免RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
可选地，所述方法还包括：
在第一时间来临前，所述网络设备下发RRC release消息释放所述终端。
可选地，所述RRC release消息携带的参数包括以下至少一种：时长T、特定原因值。
可选地，所述方法还包括以下至少一种：
所述网络设备通过系统消息下发所述第一时间和/或第二时间；
所述第一时间为网络设备覆盖当前服务区域的服务结束时间；
所述第二时间为下个网络设备覆盖当前服务区域的服务开始时间。
可选地，网络通过SI(系统消息)向终端(UE)下发上述第一时间T1和第二时间T2，终端根据网络设备下发的第二时间T2延迟预设时间接入网络。
可选地，终端满足第一预设条件，包括以下至少一种：
终端在第一时间前被网络释放；
终端在第二时间接入网络。
可选地，终端在第一时间前被网络释放，可以采用如下方案：
网络向终端下发RRC release消息，终端通过网络设备下发的RRC release消息释放。
可选地，网络设备下发的RRC release消息携带的参数可以包括以下至少一种：时长T、特定原因值，可选地，特定原因值比如coverage discontinuity，表明释放是因为当前卫星即将停止服务。
可选地，终端确定所述预设时间的方式，可以包括以下至少一种：
第一种方式：终端根据第一时间范围确定或生成所述预设时间；
可选地，终端可以根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间。
可选地，T为大于0的值。T值不能超过卫星服务时间。
可选地，T可以为固定值。
可选地，T可与当前小区负载有关，比如，负载越高T越大。
第二种方式：终端根据分组和预设时间粒度确定或生成所述预设时间。
可选地，所述分组的个数及预设时间粒度可由网络根据当前负载以及随机接入信道RACH容量来决定，并下发给UE。
可选地，终端响应于满足第二预设条件，确定不生效所述预设时间。
可选地，所述满足第二预设条件，包括以下至少一种：
第一种情况，RRC release消息未携带T值；
第二种情况，RRC release消息携带的T值为0；
第三种情况，RRC release消息携带的释放原因值不为特定原因值；
即如果RRC release未携带T值或T值为0时或释放原因不为discontinue coverage等特定原因值，则该UE不生效delay。
第四种情况，当前业务为预设的高优先级业务，比如当前UE为紧急呼叫等高优先级业务，则不生效delay。
可选地，结合图4所示，当前服务卫星通过系统消息广播T1(即end-time of serving satellite’s coverage)、T2(即start-time of incoming satellite’s coverage)。
对于尝试在T2时刻接入网络的UE，在该T2的基础上，延迟delay接入，即UE会在T2+delay时间点来尝试获取required SI并接入网络，确保各UE接入网络的时间离散化，避免RACH拥塞。
可选地，UE和对应的delay可以按如下方法确定：
Option a:
该UE为网络通过RRC release消息释放的UE，且RRC release消息携带特定原因值cause，比如coverage discontinuity，表明释放是因为当前卫星即将停止服务。
RRC release消息携带一个时长T,则delay＝random(0,T),即各UE在0～T范围内随机选择一个时间延时接入。
Option b:
该UE为网络通过RRC release消息释放的UE，且RRC release消息携带特定原因值cause，比如coverage discontinuity，表明释放是因为当前卫星即将停止服务。
将UE分成N组(如根据UE标识进行分组，UEID mod N)，延迟delta，N和delta由网络设备下发，则各组UE延迟接入时间为(UEID mod N)*delta。
可选地，N和delta可由网络根据当前负载以及RACH容量来决定，比如delta可为当前配置的RACH 周期。
Option c:
该UE为所有尝试在T2时刻接入网络的UE。
网络设备下发RRC release消息，RRC release消息携带一个时长T，则delay＝random(0,T),即各UE在0～T范围内随机选择一个时间延时接入。
Option d:
该UE为所有尝试在T2时刻接入网络的UE。
将UE分成N组(如根据UE标识进行分组，UEID mod N)，延迟delta，N和delta由网络设备下发，则各组UE延迟接入时间为(UEID mod N)*delta。N和delta可由网络根据当前负载以及RACH容量来决定，比如delta可为当前配置的RACH周期。
本实施例通过上述方案，网络设备下发第二时间，以供终端根据所述第二时间延迟预设时间接入网络。由此，通过终端延迟预设时间接入网络，避免了IoT-NTN网络中大量UE集中接入导致RACH拥塞的问题，进而避免了在IoT-NTN网络中RACH拥塞，RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
本实施例中网络设备与终端(UE)通信实现拥塞控制的流程，可以参照图5所示，本实施例中网络设备与终端(UE)通信实现拥塞控制的原理以及各个场景的原理，请参照上述各实施例，在此不再赘述。
如图8所示，本申请第四实施例提出一种控制方法，所述控制方法可应用于网络设备，所述控制方法包括以下步骤：
S1001：网络设备下发消息，以供终端根据所述消息及预设策略延迟接入网络。
本实施例终端与网络设备之间建立通信连接，该网络设备可以是基站或卫星或航空设备等，例如低轨通信卫星、高空平台和无人机等。本申请实施例中，用于实现网络设备功能的装置可以是网络设备本身，也可以是能够支持网络设备实现该功能的装置，例如芯片系统或可实现网络设备功能的组合器件、部件，该装置可以被安装在网络设备中。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。
本实施例以卫星与终端(UE)的通信实现方案进行举例。
可选地，网络设备下发的消息包括但不限于系统消息、RRC release消息等。
本实施例考虑到：针对IoT-NTN网络，现有机制无法保证在RACH拥塞时，在有限的时间内(Validity timer)使得UE成功接入网络并预留更多的时间供数据传输。因此，本申请提出解决方案，可以避免IoT-NTN网络中RACH拥塞，进而避免RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
可选地，如前所述，根据RAN2 116-e会议结论，对于IoT-NTN Quasi-Earth Fixed satellites场景，由于卫星移动，覆盖某个区域的卫星在到达特定时间点T1(即end-time of serving satellite’s coverage)时会停止服务，下个覆盖该区域的卫星的开始服务时间为T2(即start-time of incoming satellite’s coverage)，T1和T2通过SI(系统消息)广播，对该区域的所有UE生效。
参照图4，图4为本申请实施例涉及的终端延迟接入的场景示意图。
如图4所示，当前服务卫星通过系统消息广播第一时间T1(即end-time of serving satellite’s coverage)、第二时间T2(即start-time of incoming satellite’s coverage)。
可选地，第一时间T1为网络设备覆盖当前服务区域的服务结束时间；第二时间T2为下个网络设备覆盖当前服务区域的服务开始时间。以网络设备为卫星进行举例，第一时间T1为覆盖当前网络服务区域卫星的服务结束时间；第二时间T2为下个覆盖当前网络服务区域卫星的服务开始时间。
T1和T2通过SI(系统消息)广播，对该区域的所有UE生效，因此在该T2时间点可能存在大量UE尝试接入该卫星，导致RACH拥塞。
在本实施例中，对于尝试在T2时刻接入网络的UE，在该T2时刻的基础上，延迟预设时间delay接入，即UE会在T2+delay时间点来尝试获取required SI并接入网络，确保各UE接入网络的时间离散化，避免RACH拥塞，进而避免了RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
在本实施例中，网络设备下发消息，以供终端根据所述消息及预设策略延迟接入网络。
由此，通过终端根据网络设备下发的消息，及预设策略延迟接入网络，避免了IoT-NTN网络中大量UE集中接入导致RACH拥塞的问题，进而避免了在IoT-NTN网络中RACH拥塞，RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
可选地，所述S1001步骤包括：
网络设备下发第二时间，以供终端根据所述第二时间延迟预设时间接入网络。
可选地，所述S1001步骤还包括：
在第一时间来临前，网络设备下发RRC release消息释放所述终端。
可选地，所述RRC release消息携带的参数包括以下至少一种：时长T、特定原因值。
可选地，包括以下至少一种：
所述网络设备通过系统消息下发所述第一时间T1和第二时间T2；
所述第一时间T1为网络设备覆盖当前服务区域的服务结束时间；
所述第二时间T2为下个网络设备覆盖当前服务区域的服务开始时间。
可选地，终端响应于满足预设条件，根据预设策略延迟接入网络。
可选地，所述满足预设条件，可以包括：满足第一预设条件和/或满足第二预设条件。
可选地，所述满足第一预设条件包括以下至少一种：
终端在第一时间前被网络释放；
终端在所述第二时间接入网络。
可选地，终端在第一时间前被网络释放，可以采用如下方案：
网络向终端下发RRC release消息，终端通过网络设备下发的RRC release消息释放。
可选地，网络设备下发的RRC release消息携带的参数可以包括以下至少一种：时长T、特定原因值，可选地，特定原因值比如coverage discontinuity，表明释放是因为当前卫星即将停止服务。
可选地，所述满足第二预设条件可以包括以下至少一种：
第一种情况，RRC release消息携带T值；
第二种情况，RRC release消息携带的T值不为0；
第三种情况，RRC release消息携带的释放原因值为特定原因值；
即如果RRC release未携带T值或T值为0时或释放原因不为discontinue coverage等特定原因值，则不满足第二预设条件，该UE不生效delay。
第四种情况，当前业务不为预设的高优先级业务，比如当前UE为紧急呼叫等高优先级业务，则不满足第二预设条件，该UE不生效delay。
由此，终端响应于满足上述第一预设条件和/或满足上述第二预设条件，根据预设策略延迟接入网络。
可选地，所述终端根据预设策略延迟接入网络，包括：
终端根据预设时间延迟接入网络。
可选地，终端确定所述预设时间。
可选地，终端响应于满足第一预设条件和/或满足第二预设条件，确定预设时间，并根据网络设备下发的第二时间延迟预设时间接入网络。
可选地，终端确定所述预设时间的方式，可以包括以下至少一种：
第一种方式：终端根据第一时间范围确定或生成所述预设时间；
可选地，终端可以根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间。
可选地，T为大于0的值。T值不能超过卫星服务时间。
可选地，T可以为固定值。
可选地，T可与当前小区负载有关，比如，负载越高T越大。
第二种方式：终端根据分组及预设时间粒度确定或生成所述预设时间。
可选地，所述分组的个数及预设时间粒度可由网络根据当前负载以及随机接入信道RACH容量来决定，并下发给UE。
可选地，结合图4所示，当前服务卫星通过系统消息广播T1(即end-time of serving satellite’s coverage)、T2(即start-time of incoming satellite’s coverage)。
对于尝试在T2时刻接入网络的UE，在该T2的基础上，延迟delay接入，即UE会在T2+delay时间点来尝试获取required SI并接入网络，确保各UE接入网络的时间离散化，避免RACH拥塞。
可选地，UE和对应的delay可以按如下方法确定：
Option a:
该UE为网络通过RRC release消息释放的UE，且RRC release消息携带特定原因值cause，比如coverage discontinuity，表明释放是因为当前卫星即将停止服务。
RRC release消息携带一个时长T,则delay＝random(0,T),即各UE在0～T范围内随机选择一个时间延时接入。
Option b:
该UE为网络通过RRC release消息释放的UE，且RRC release消息携带特定原因值cause，比如coverage discontinuity，表明释放是因为当前卫星即将停止服务。
将UE分成N组(如根据UE标识进行分组，UEID mod N)，延迟delta，N和delta由网络设备下发，则各组UE延迟接入时间为(UEID mod N)*delta。
可选地，N和delta可由网络根据当前负载以及RACH容量来决定，比如delta可为当前配置的RACH 周期。
Option c:
该UE为所有尝试在T2时刻接入网络的UE。
网络设备下发RRC release消息，RRC release消息携带一个时长T，则delay＝random(0,T),即各UE在0～T范围内随机选择一个时间延时接入。
Option d:
该UE为所有尝试在T2时刻接入网络的UE。
将UE分成N组(如根据UE标识进行分组，UEID mod N)，延迟delta，N和delta由网络设备下发，则各组UE延迟接入时间为(UEID mod N)*delta。N和delta可由网络根据当前负载以及RACH容量来决定，比如delta可为当前配置的RACH周期。
本实施例通过上述方案，网络设备下发消息，以供终端根据所述消息及预设策略延迟接入网络。由此，通过延迟接入网络，避免了IoT-NTN网络中大量UE集中接入导致RACH拥塞的问题，进而避免了在IoT-NTN网络中RACH拥塞，RACH占用过多时间而导致在上行同步有效时间内可用于数据传输的时间不足，导致业务中断的问题。
本实施例中网络设备与终端(UE)通信实现拥塞控制的流程，可以参照图5所示，本实施例中网络设备与终端(UE)通信实现拥塞控制的原理以及各个场景的原理，请参照上述各实施例，在此不再赘述。
如图9所示，本申请实施例还提出一种控制装置，本申请控制装置可应用于终端设备，该控制装置包括：
第一接入模块，用于响应于满足第一预设条件，根据网络设备下发的第二时间延迟预设时间接入网络。
可选地，该控制装置还包括：
第一确定模块，用于确定所述预设时间。
可选地，所述第一确定模块，还用于根据第一时间范围确定或生成所述预设时间；或者，根据分组确定或生成所述预设时间。
可选地，所述第一确定模块，还用于根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间，可选地，T为大于0的值，或者，所述T与当前负载关联。
可选地，所述第一接入模块，还用于响应于满足第二预设条件，确定不生效所述预设时间。
可选地，上述控制装置中各个模块的功能实现，与上述控制方法实施例中各步骤相对应，其功能和实现过程在此处不再一一赘述。
如图10所示，本申请实施例还提出一种控制装置，本申请控制装置可应用于终端设备，该控制装置包括：
第二接入模块，用于响应于满足预设条件，根据预设策略延迟接入网络。
可选地，所述第二接入模块，还用于根据预设时间延迟接入网络。
可选地，该控制装置还包括：
第二确定模块，用于确定所述预设时间。
可选地，所述第二确定模块，还用于根据第一时间范围确定或生成所述预设时间；或者，根据分组确定或生成所述预设时间。
可选地，所述第二确定模块，还用于根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间，可选地，T为大于0的值，或者，所述T与当前负载关联。
可选地，上述控制装置中各个模块的功能实现，与上述控制方法实施例中各步骤相对应，其功能和实现过程在此处不再一一赘述。
如图11所示，本申请实施例还提出一种控制装置，本申请控制装置可应用于网络设备，该控制装置包括：
第一发送模块，用于下发第二时间，以供终端根据所述第二时间延迟预设时间接入网络。
可选地，所述第一发送模块，还用于在第一时间来临前，下发RRC release消息释放所述终端。
可选地，上述控制装置中各个模块的功能实现，与上述控制方法实施例中各步骤相对应，其功能和实现过程在此处不再一一赘述。
如图12所示，本申请实施例还提出一种控制装置，本申请控制装置可应用于网络设备，该控制装置包括：
第二发送模块，用于下发消息，以供终端根据所述消息及预设策略延迟接入网络。
可选地，所述第二发送模块，还用于下发第二时间，以供终端根据所述第二时间延迟预设时间接入网络。
可选地，所述第二发送模块，还用于在第一时间来临前，下发RRC release消息释放所述终端。
可选地，上述控制装置中各个模块的功能实现，与上述控制方法实施例中各步骤相对应，其功能和实现过程在此处不再一一赘述。
本申请实施例还提供一种通信设备，该通信设备包括存储器、处理器，存储器上存储有通信程序，通信程序被处理器执行时实现上述任一实施例中的控制方法的步骤。该通信设备既可以为上述控制方法中的终端设备，该通信设备在作为该终端设备时具体可以为：手机、平板电脑、笔记本电脑、掌上电脑、个人数字助理(Personal Digital Assistant，PDA)、便捷式媒体播放器(Portable Media Player，PMP)、导航装置、可穿戴设备、智能手环、计步器等终端设备。可选地，该通信设备也可以为上述通信方法中的网络设备，该通信设备在作为该网络设备时具体可以为基站或卫星或航空设备等，例如低轨通信卫星、高空平台和无人机等。本申请实施例中，用于实现网络设备功能的装置可以是网络设备本身，也可以是能够支持网络设备实现该功能的装置，例如芯片系统或可实现网络设备功能的组合器件、部件，该装置可以被安装在网络设备中。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。
本申请实施例还提出一种计算机可读存储介质，所述存储介质上存储有控制程序，所述控制程序被处理器执行时实现上述任一实施例中所述的控制方法的步骤。
在本申请提供的通信设备和计算机可读存储介质的实施例中，可以包含任一上述控制方法实施例的全部技术特征，说明书拓展和解释内容与上述方法的各实施例基本相同，在此不做再赘述。
本申请实施例还提供一种计算机程序产品，计算机程序产品包括计算机程序代码，当计算机程序代码在计算机上运行时，使得计算机执行如上各种可能的实施方式中的方法。
本申请实施例还提供一种芯片，包括存储器和处理器，存储器用于存储计算机程序，处理器用于从存储器中调用并运行计算机程序，使得安装有芯片的设备执行如上各种可能的实施方式中的方法。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
可以理解，上述场景仅是作为示例，并不构成对于本申请实施例提供的技术方案的应用场景的限定，本申请的技术方案还可应用于其他场景。例如，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
本申请实施例方法中的步骤可以根据实际需要进行顺序调整、合并和删减。
本申请实施例设备中的单元可以根据实际需要进行合并、划分和删减。
在本申请中，对于相同或相似的术语概念、技术方案和/或应用场景描述，一般只在第一次出现时进行详细描述，后面再重复出现时，为了简洁，一般未再重复阐述，在理解本申请技术方案等内容时，对于在后未详细描述的相同或相似的术语概念、技术方案和/或应用场景描述等，可以参考其之前的相关详细描述。
在本申请中，对各个实施例的描述都各有侧重，某个实施例中没有详述或记载的部分，可以参见其它实施例的相关描述。
本申请技术方案的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本申请记载的范围。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在如上的一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，被控终端，或者网络设备等)执行本申请每个实施例的方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络，或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质，(例如，软盘、存储盘、磁带)、光介质(例如，DVD)，或者半导体介质(例如固态存储盘Solid State Disk(SSD))等。
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (34)

  1. 一种控制方法，其特征在于，所述方法包括以下步骤：
    S10：响应于满足第一预设条件，终端根据网络设备下发的第二时间延迟预设时间接入网络。
  2. 根据权利要求1所述的方法，其特征在于，所述满足第一预设条件，包括以下至少一种：
    在第一时间前被网络释放，所述第一时间由所述网络设备下发；
    在所述第二时间接入网络。
  3. 根据权利要求2所述的方法，其特征在于，包括以下至少一种：
    所述第一时间为网络设备覆盖当前服务区域的服务结束时间；
    所述第二时间为下个网络设备覆盖当前服务区域的服务开始时间；
    所述终端通过网络的RRC release消息释放。
  4. 根据权利要求3所述的方法，其特征在于，所述RRC release消息携带的参数包括以下至少一种：时长T、特定原因值。
  5. 根据权利要求1所述的方法，其特征在于，所述S10步骤包括：
    确定所述预设时间。
  6. 根据权利要求5所述的方法，其特征在于，所述确定所述预设时间的方式，包括以下至少一种：
    根据第一时间范围确定或生成所述预设时间；
    根据分组确定或生成所述预设时间。
  7. 根据权利要求6所述的方法，其特征在于，所述根据第一时间范围确定或生成所述预设时间的步骤包括：
    根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间，其中，T为大于0的值，或者，所述T与当前负载关联。
  8. 根据权利要求5所述的方法，其特征在于，所述S10步骤还包括：
    响应于满足第二预设条件，确定不生效所述预设时间。
  9. 根据权利要求8所述的方法，其特征在于，所述满足第二预设条件，包括以下至少一种：
    RRC release消息未携带T值；
    RRC release消息携带的T值为0；
    RRC release消息携带的释放原因值不为特定原因值；
    当前业务为预设的高优先级业务。
  10. 一种控制方法，其特征在于，所述方法包括以下步骤：
    S100：响应于满足预设条件，终端根据预设策略延迟接入网络。
  11. 根据权利要求10所述的方法，其特征在于，所述满足预设条件，包括：满足第一预设条件和/或满足第二预设条件。
  12. 根据权利要求11所述的方法，其特征在于，所述满足第一预设条件包括以下至少一种：
    终端在第一时间前被网络释放，所述第一时间由所述网络设备下发；
    终端在第二时间接入网络，所述第二时间由所述网络设备下发。
  13. 根据权利要求12所述的方法，其特征在于，包括以下至少一种：
    所述第一时间为网络设备覆盖当前服务区域的服务结束时间；
    所述第二时间为下个网络设备覆盖当前服务区域的服务开始时间；
    所述终端通过网络的RRC release消息释放。
  14. 根据权利要求13所述的方法，其特征在于，所述RRC release消息携带的参数包括以下至少一种：时长T、特定原因值。
  15. 根据权利要求11所述的方法，其特征在于，所述满足第二预设条件包括以下至少一种：
    RRC release消息携带T值；
    RRC release消息携带的T值不为0；
    RRC release消息携带的释放原因值为特定原因值；
    当前业务不为预设的高优先级业务。
  16. 根据权利要求10所述的方法，其特征在于，所述终端根据预设策略延迟接入网络，包括：
    根据预设时间延迟接入网络。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    确定所述预设时间。
  18. 根据权利要求17所述的方法，其特征在于，所述确定所述预设时间的方式，包括以下至少一 种：
    根据第一时间范围确定或生成所述预设时间；
    根据分组确定或生成所述预设时间。
  19. 根据权利要求18所述的方法，其特征在于，所述根据第一时间范围确定或生成所述预设时间的步骤包括：
    根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间，其中，T为大于0的值，或者，所述T与当前负载关联。
  20. 一种控制方法，其特征在于，所述方法包括以下步骤：
    S101：网络设备下发第二时间，以供终端根据所述第二时间延迟预设时间接入网络。
  21. 根据权利要求20所述的方法，其特征在于，所述方法还包括：
    在第一时间来临前，所述网络设备下发RRC release消息释放所述终端。
  22. 根据权利要求21所述的方法，其特征在于，所述RRC release消息携带的参数包括以下至少一种：时长T、特定原因值。
  23. 根据权利要求21所述的方法，其特征在于，包括以下至少一种：
    所述网络设备通过系统消息下发所述第一时间和/或第二时间；
    所述第一时间为网络设备覆盖当前服务区域的服务结束时间；
    所述第二时间为下个网络设备覆盖当前服务区域的服务开始时间。
  24. 根据权利要求21所述的方法，其特征在于，所述终端确定所述预设时间的方式包括以下至少一种：
    所述终端根据第一时间范围确定或生成所述预设时间；
    所述终端根据分组确定或生成所述预设时间。
  25. 根据权利要求24所述的方法，其特征在于，所述终端根据第一时间范围确定或生成所述预设时间的步骤包括：
    所述终端根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间，其中，T为大于0的值，或者，所述T与当前负载关联。
  26. 一种控制方法，其特征在于，所述方法包括以下步骤：
    S1001：网络设备下发消息，以供终端根据所述消息及预设策略延迟接入网络。
  27. 根据权利要求26所述的方法，其特征在于，所述S1001步骤包括：
    网络设备下发第二时间，以供终端根据所述第二时间延迟预设时间接入网络。
  28. 根据权利要求27所述的方法，其特征在于，所述S1001步骤还包括：
    在第一时间来临前，网络设备下发RRC release消息释放所述终端。
  29. 根据权利要求28所述的方法，其特征在于，所述RRC release消息携带的参数包括以下至少一种：时长T、特定原因值。
  30. 根据权利要求28所述的方法，其特征在于，包括以下至少一种：
    所述网络设备通过系统消息下发所述第一时间和/或第二时间；
    所述第一时间为网络设备覆盖当前服务区域的服务结束时间；
    所述第二时间为下个网络设备覆盖当前服务区域的服务开始时间。
  31. 根据权利要求27所述的方法，其特征在于，所述终端确定所述预设时间的方式包括以下至少一种：
    所述终端根据第一时间范围确定或生成所述预设时间；
    所述终端根据分组确定或生成所述预设时间。
  32. 根据权利要求31所述的方法，其特征在于，所述终端根据第一时间范围确定或生成所述预设时间的步骤包括：
    所述终端根据网络设备下发的时长T，在0～T范围内随机选择一个时长作为所述预设时间，其中，T为大于0的值，或者，所述T与当前负载关联。
  33. 一种通信设备，其特征在于，包括：存储器和处理器，所述存储器上存储有控制程序，所述控制程序被所述处理器执行时实现如权利要求1所述的控制方法的步骤。
  34. 一种计算机可读存储介质，其特征在于，所述存储介质上存储有控制程序，所述控制程序被处理器执行时实现如权利要求1所述的控制方法的步骤。
PCT/CN2023/092601 2022-05-17 2023-05-06 控制方法、通信设备及存储介质 WO2023221794A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP23806746.6A EP4395409A1 (en) 2022-05-17 2023-05-06 Control method, communication device, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210532039.2A CN114630366B (zh) 2022-05-17 2022-05-17 控制方法、通信设备及存储介质
CN202210532039.2 2022-05-17

Publications (1)

Publication Number Publication Date
WO2023221794A1 true WO2023221794A1 (zh) 2023-11-23

Family

ID=81907102

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/092601 WO2023221794A1 (zh) 2022-05-17 2023-05-06 控制方法、通信设备及存储介质

Country Status (3)

Country Link
EP (1) EP4395409A1 (zh)
CN (1) CN114630366B (zh)
WO (1) WO2023221794A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114630366B (zh) * 2022-05-17 2023-05-09 深圳传音控股股份有限公司 控制方法、通信设备及存储介质
GB2621443A (en) * 2022-08-08 2024-02-14 Samsung Electronics Co Ltd Enhancements for UE - satellite access

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111095820A (zh) * 2017-08-22 2020-05-01 弗劳恩霍夫应用研究促进协会 无线通信系统、基站和用户侧设备
CN112566145A (zh) * 2019-09-25 2021-03-26 深圳市中兴微电子技术有限公司 一种拥塞控制的方法、装置、计算机存储介质及终端
CN113747460A (zh) * 2020-05-30 2021-12-03 华为技术有限公司 通信方法及装置
CN114630366A (zh) * 2022-05-17 2022-06-14 深圳传音控股股份有限公司 控制方法、通信设备及存储介质

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000315972A (ja) * 1999-05-06 2000-11-14 Nec Corp 衛星通信システム及びそのハンドオーバ処理方法
US20180254825A1 (en) * 2017-03-02 2018-09-06 UbiquitiLink, Inc. Method and apparatus for handling communications between spacecraft operating in an orbital environment and terrestrial telecommunications devices that use terrestrial base station communications
US10959201B2 (en) * 2018-04-05 2021-03-23 Qualcomm Incorporated Techniques for initial access in wireless systems
CN114900882A (zh) * 2019-02-23 2022-08-12 华为技术有限公司 一种更新定时提前的方法、终端及网络设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111095820A (zh) * 2017-08-22 2020-05-01 弗劳恩霍夫应用研究促进协会 无线通信系统、基站和用户侧设备
CN112566145A (zh) * 2019-09-25 2021-03-26 深圳市中兴微电子技术有限公司 一种拥塞控制的方法、装置、计算机存储介质及终端
CN113747460A (zh) * 2020-05-30 2021-12-03 华为技术有限公司 通信方法及装置
CN114630366A (zh) * 2022-05-17 2022-06-14 深圳传音控股股份有限公司 控制方法、通信设备及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CMCC: "Discussion on support of Non continuous coverage", 3GPP TSG-RAN WG2 MEETING #116-E, R2-2110262, 22 October 2021 (2021-10-22), XP052066707 *

Also Published As

Publication number Publication date
CN114630366B (zh) 2023-05-09
CN114630366A (zh) 2022-06-14
EP4395409A1 (en) 2024-07-03

Similar Documents

Publication Publication Date Title
CN110175062B (zh) 一种移动终端的屏幕刷新帧率方法、移动终端及存储介质
WO2020007340A1 (zh) Pucch冲突的处理方法和终端
WO2023221794A1 (zh) 控制方法、通信设备及存储介质
CN110784898A (zh) 网络切换方法、移动终端及计算机可读存储介质
WO2020063240A1 (zh) 信道接入方法、配置方法、终端及网络侧设备
WO2020063452A1 (zh) 一种资源调度方法和装置
CN113645345A (zh) 数据发送方法、移动终端及存储介质
WO2019242465A1 (zh) 一种资源请求方法及用户设备
CN114126015A (zh) 功耗控制方法、智能终端及存储介质
WO2021068876A1 (zh) 信息传输、接收方法、终端及网络侧设备
CN110677897B (zh) 一种网络搜索控制方法、终端及计算机可读存储介质
CN109168189B (zh) 一种省电方法、移动终端及计算机可读存储介质
CN108990156B (zh) 一种无线局域网通信方法、终端
CN111970738B (zh) 一种网络切换控制方法、设备及计算机可读存储介质
CN108306856B (zh) 一种接口合并方法、客户端、服务器及计算机可读存储介质
CN113099514A (zh) 接入独立组网网络方法、设备及计算机可读存储介质
WO2023130954A1 (zh) 处理方法、通信设备及存储介质
CN110191477B (zh) 一种网络搜索控制方法、终端及计算机可读存储介质
WO2023082603A1 (zh) 提醒方法、终端设备、网络设备及存储介质
CN114423041A (zh) 通信方法、智能终端及存储介质
CN110087290B (zh) 功耗管控方法、终端以及计算机可读存储介质
CN112672203A (zh) 文件传输控制方法、移动终端及计算机可读存储介质
WO2024050835A1 (zh) 处理方法、通信设备及存储介质
WO2024050834A1 (zh) 处理方法、通信设备及存储介质
WO2023230875A1 (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: 23806746

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023806746

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2023806746

Country of ref document: EP

Effective date: 20240328