[go: up one dir, main page]

WO2023056843A1 - 一种通信方法、通信装置及通信系统 - Google Patents

一种通信方法、通信装置及通信系统 Download PDF

Info

Publication number
WO2023056843A1
WO2023056843A1 PCT/CN2022/120600 CN2022120600W WO2023056843A1 WO 2023056843 A1 WO2023056843 A1 WO 2023056843A1 CN 2022120600 W CN2022120600 W CN 2022120600W WO 2023056843 A1 WO2023056843 A1 WO 2023056843A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
satellite
information
network
covered
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2022/120600
Other languages
English (en)
French (fr)
Inventor
潘奇
黄正磊
张万强
李永翠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN202111308873.5A external-priority patent/CN115968017A/zh
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to AU2022360194A priority Critical patent/AU2022360194B2/en
Priority to EP22877862.7A priority patent/EP4391657A4/en
Priority to JP2024521270A priority patent/JP7704972B2/ja
Priority to CA3233648A priority patent/CA3233648A1/en
Publication of WO2023056843A1 publication Critical patent/WO2023056843A1/zh
Priority to US18/608,950 priority patent/US20240224217A1/en
Anticipated expiration legal-status Critical
Priority to JP2025108103A priority patent/JP2025143332A/ja
Priority to AU2025213602A priority patent/AU2025213602A1/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/1853—Satellite systems for providing telephony service to a mobile station, i.e. mobile satellite service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0248—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal dependent on the time of the day, e.g. according to expected transmission activity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • 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
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the technical field of communication, and in particular to a communication method, a communication device and a communication system.
  • Satellite communications can enhance network coverage to a certain extent.
  • the terminal device cannot be covered by the satellite network during a certain period of time.
  • Embodiments of the present application provide a communication method, a communication device, and a communication system, which are used to reduce energy consumption of terminal equipment or core network equipment (such as mobility management network elements) in a satellite communication-based scenario.
  • terminal equipment or core network equipment such as mobility management network elements
  • the embodiment of the present application provides a communication method, and the method may be executed by a mobility management network element or a module (such as a chip) applied to the mobility management network element.
  • the method includes: determining sleep time information of the terminal device according to the satellite coverage information of the terminal device, the satellite coverage information indicating the time period during which the terminal device is covered by the satellite network and/or the time period during which the terminal device is not covered by the satellite network.
  • the sleep time period corresponding to the time information includes a time period when the terminal device is not covered by the satellite network; and the sleep time information is sent to the terminal device.
  • the mobility management network element determines the sleep time information according to the satellite coverage information of the terminal device, and the sleep time period corresponding to the sleep time information includes the time period when the terminal device is not covered by the satellite network, so as to ensure that the terminal device can The ground sleeps during the time period not covered by the satellite network, avoiding unnecessary network connection operations such as cell selection, so as to save energy consumption of terminal equipment.
  • one or more of the eDRX cycle, periodic TAU cycle, or periodic registration cycle of the terminal device is determined; wherein, the sleep time information includes sleep start time, The dormancy start time is within the eDRX cycle and the period of the periodic TAU.
  • the sleep time information includes a sleep start time and a sleep end time; or, the sleep time information includes a sleep start time and a sleep duration.
  • the terminal device will continue to sleep and will not perform business, including not performing periodic TAU, not performing periodic registration, and not performing uplink data transmission, Energy consumption of terminal equipment can be reduced.
  • the satellite coverage information is received; or, the ephemeris information of the satellite cell where the terminal device is located is received, and the satellite coverage information is determined according to the ephemeris information.
  • the terminal device it is determined that the terminal device has a fixed position or a fixed moving track.
  • the de-registration timer corresponding to the terminal device expires, it is determined according to the satellite coverage information that the terminal device is not covered by the satellite network, and it is determined not to perform de-registration on the terminal device.
  • the mobility management network element when the terminal device is not covered by the satellite network, the mobility management network element does not deregister the terminal device, which can reduce the status of the terminal device from switching back and forth between registration and deregistration, thereby reducing the energy consumption of the terminal device and reducing the Frequent signaling interaction with the network.
  • the embodiment of the present application provides a communication method, and the method may be executed by a mobility management network element or a module (such as a chip) applied to the mobility management network element.
  • the method includes: when the corresponding de-registration timer of the terminal device expires, according to the satellite coverage information of the terminal device, it is determined that the terminal device is not covered by the satellite network, and the satellite coverage information indicates the time period and the period during which the terminal device is covered by the satellite network. /or a time period not covered by the satellite network; in response to the terminal device not being covered by the satellite network, it is determined not to perform de-registration on the terminal device.
  • the mobility management network element when the terminal device is not covered by the satellite network, the mobility management network element does not deregister the terminal device, which can reduce the status of the terminal device from switching back and forth between registration and deregistration, thereby reducing the energy consumption of the terminal device.
  • first information is sent to the terminal device, where the first information indicates that the terminal device performs uplink transmission according to satellite network coverage when it has an uplink transmission requirement.
  • the first information is the satellite coverage information; the first information is specifically used to instruct the terminal device to initiate uplink transmission according to the satellite coverage information when there is an uplink transmission requirement.
  • the satellite coverage information is sent to the terminal device; the first information is specifically used to instruct the terminal device to initiate uplink transmission according to the satellite coverage information when there is an uplink transmission requirement.
  • the uplink transmission requirement includes one or more of periodic TAU, periodic registration, or uplink data transmission.
  • the satellite coverage information is received; or, the ephemeris information of the satellite cell where the terminal device is located is received, and the satellite coverage information is determined according to the ephemeris information.
  • the terminal device it is determined that the terminal device has a fixed position or a fixed moving track.
  • the embodiment of the present application provides a communication method, and the method may be executed by a mobility management network element or a module (such as a chip) applied to the mobility management network element.
  • the method includes: determining satellite coverage information of the terminal device, the satellite coverage information indicating the time period during which the terminal device is covered by the satellite network and/or the time period not covered by the satellite network; determining the maximum waiting time according to the satellite coverage information, The maximum waiting time indicates the maximum duration of waiting for the terminal device to be reachable.
  • the mobility management network element can judge the reachability according to the satellite coverage information of the terminal equipment.
  • the paging of the terminal device can reduce unnecessary signaling interaction between the mobility management network element and the access network device, and at the same time avoid waste of paging resources of the access network device and loss of downlink data of the terminal device.
  • the terminal device is unreachable according to the satellite coverage information.
  • the satellite coverage information is received.
  • the ephemeris information of the satellite cell where the terminal device is located is received; and the satellite coverage information is determined according to the ephemeris information.
  • a paging message is sent to the access network device, the paging message includes the identification information of the terminal device, and the paging message indicates to paging the terminal device; receiving a message from the access network device A first message, where the first message includes a paging failure indication and the satellite coverage information, where the paging failure indication is used to indicate that the cause of the paging failure is not being covered by the satellite network.
  • the paging failure indication also indicates that the mobility management network element needs to perform reachability judgment/paging according to the satellite coverage information.
  • a paging message is sent to the access network device, the paging message includes the identification information of the terminal device, and the paging message indicates to paging the terminal device; receiving a message from the access network device
  • the first message the first message includes the satellite coverage information of the terminal equipment, and the satellite coverage information indicates that the cause of the paging failure is that it is not covered by the satellite network. Satellite coverage information for reachability judgment/paging.
  • the terminal device it is determined that the terminal device has a fixed position or a fixed moving track.
  • the embodiment of the present application provides a communication method, and the method may be executed by a terminal device or a module (such as a chip) applied to the terminal device.
  • the method includes: receiving first information, the first information indicating that the terminal equipment performs uplink transmission according to the coverage of the satellite network when there is an uplink transmission demand; when there is an uplink transmission demand, according to the first information, it is determined that the terminal equipment is not covered by the satellite network coverage, it is determined not to perform uplink transmission.
  • the first information is satellite coverage information
  • the satellite coverage information indicates the time period during which the terminal device is covered by the satellite network and/or the time period during which the terminal device is not covered by the satellite network; the first information specifically It is used to instruct the terminal device to initiate uplink transmission according to the satellite coverage information when there is an uplink transmission requirement.
  • satellite coverage information is received, and the satellite coverage information indicates the time period during which the terminal device is covered by the satellite network and/or the time period during which the terminal device is not covered by the satellite network; the first information is specifically used to indicate the When the terminal device has an uplink transmission requirement, it initiates an uplink transmission according to the satellite coverage information.
  • the uplink transmission requirement includes one or more of periodic TAU, periodic registration, or uplink data transmission.
  • the embodiment of the present application provides a communication method, and the method may be executed by a terminal device or a module (such as a chip) applied to the terminal device.
  • the method includes: receiving sleep time information, the sleep time period corresponding to the sleep time information includes a time period when the terminal device is not covered by the satellite network, the sleep time information is determined according to the satellite coverage information of the terminal device, the satellite coverage information Indicate the period of time that the terminal device is covered by the satellite network and/or the period of time not covered by the satellite network; perform sleep according to the sleep time information.
  • the terminal device can sleep as much as possible during the time period not covered by the satellite network, avoiding unnecessary network connection operations such as cell scanning and cell selection, so as to save energy consumption of the terminal device.
  • the sleep time information includes a sleep start time
  • the sleep start time is located in the eDRX cycle of the terminal device, in the periodic TAU cycle of the terminal device, or in the periodic registration cycle of the terminal device .
  • the sleep time information includes a sleep start time and a sleep end time; or, the sleep time information includes a sleep start time and a sleep duration.
  • the embodiment of the present application provides a communication method, and the method may be executed by an access network device or a module (such as a chip) applied to the access network device.
  • the method includes: obtaining satellite coverage information or ephemeris information of a satellite cell, the satellite coverage information indicating the time period during which the satellite cell is covered by the satellite network and/or the time period not covered by the satellite network; sending the information to the mobility management network element Satellite coverage information or ephemeris information of the satellite cell.
  • the satellite coverage information or ephemeris information corresponding to the satellite cell of the access network device is sent to the mobility management network element.
  • the satellite coverage information or ephemeris information of the satellite cell where the terminal device is located is sent to the mobility management network element.
  • a paging message from the mobility management network element is received, the paging message includes identification information of the terminal device, and the paging message indicates that the terminal device is to be paged;
  • the satellite coverage information of the satellite cell determining that the satellite cell has no network coverage, sending a first message to the mobility management network element, the first message includes a paging failure indication and the satellite coverage information of the satellite cell where the terminal device is located,
  • the paging failure indication is used to indicate that the cause of the paging failure is not being covered by the satellite network.
  • the paging failure indication also indicates that the mobility management network element needs to perform reachability judgment/paging according to the satellite coverage information.
  • a paging message from the mobility management network element is received, the paging message includes identification information of the terminal device, and the paging message indicates that the terminal device is to be paged;
  • the satellite coverage information of the satellite cell determines that the satellite cell has no network coverage, and sends a first message to the mobility management network element.
  • the first message includes the satellite coverage information of the satellite cell where the terminal device is located, and the satellite cell where the terminal device is located.
  • the satellite coverage information of the satellite cell is the satellite coverage information of the terminal device, and the satellite coverage information is used to indicate that the reason for the paging failure is that it is not covered by the satellite network.
  • the satellite coverage information also indicates the need to move
  • the management network element performs reachability judgment/paging according to the satellite coverage information.
  • the embodiment of the present application provides a communication method, and the method may be executed by a mobility management network element or a module (such as a chip) applied to the mobility management network element.
  • the method includes: determining the periodic TAU cycle of the terminal device according to the satellite coverage information of the terminal device, and sending the periodic TAU cycle to the terminal device; or determining the periodic registration of the terminal device according to the satellite coverage information of the terminal device period, and send the periodic registration period to the terminal device; wherein, the satellite coverage information indicates the time period during which the terminal device is covered by the satellite network and/or the time period during which the terminal device is not covered by the satellite network.
  • the mobility management network element determines the periodic TAU period or the periodic registration period according to the satellite coverage information of the terminal equipment, so that the time period corresponding to the periodic TAU period or the period corresponding to the periodic registration period can include the terminal equipment During the time period not covered by the satellite network, ensure that the terminal device can not perform the periodic TAU process or the periodic registration process during the time period not covered by the satellite network as much as possible, so as to avoid unnecessary network connection operations such as cell selection, so as to Save energy consumption of terminal equipment.
  • the time period corresponding to the periodic TAU period includes the time period when the terminal device is not covered by the satellite network; or, the time period corresponding to the periodic registration period includes the time period when the terminal device is not covered by the satellite network. The time period covered.
  • instruction information is sent to the access network device, where the instruction information instructs the access network device to execute the terminal device release procedure.
  • the first duration is determined according to the satellite coverage information of the terminal device, and the first duration is the duration after the terminal device enters the idle state and before entering the dormant state; and the first duration is sent to the terminal device for a while.
  • a cause value is sent to the terminal device, where the cause value is discontinuous satellite coverage.
  • the cause value is also used to indicate that the terminal device does not perform uplink transmission during sleep.
  • a GUTI reallocation command is sent to the terminal device, and the GUTI reallocation command includes the periodic TAU cycle; or, a TAU acceptance message is sent to the terminal device, and the TAU acceptance message includes the periodic TAU period. TAU cycle.
  • a configuration update command is sent to the terminal device, and the configuration update command includes the periodic registration period; or, a mobile registration update acceptance message is sent to the terminal device, and the mobile registration update acceptance message includes the Periodic registration period.
  • the embodiment of the present application provides a communication method, and the method may be executed by a terminal device or a module (such as a chip) applied to the terminal device.
  • the method includes: receiving a periodic TAU cycle from a mobility management network element, and performing a periodic TAU according to the periodic TAU cycle, the time period corresponding to the periodic TAU cycle includes a time period when the terminal device is not covered by the satellite network ; Or, receiving a periodic registration period from a mobility management network element, and performing periodic registration according to the periodic registration period, where the time period corresponding to the periodic registration period includes a time period when the terminal device is not covered by the satellite network.
  • the time period corresponding to the periodic TAU cycle received by the terminal device or the time period corresponding to the periodic registration period includes the time period when the terminal device is not covered by the satellite network, so as to ensure that the terminal device can be as far as possible without being covered by the satellite network.
  • Periodic TAU process or periodic registration process is not executed during the period of time to avoid unnecessary network connection operations such as cell selection, so as to save energy consumption of terminal equipment.
  • the periodic TAU period or the periodic registration period is determined according to the satellite coverage information of the terminal device, and the satellite coverage information indicates the time period during which the terminal device is covered by the satellite network and/or The period of time not covered by the satellite network.
  • a mobile registration update request is sent to the mobility management network element; wherein the satellite coverage information indicates the time period during which the terminal device is covered by the satellite network and/or Or periods of time not covered by satellite networks.
  • the first duration is received from the mobility management network element, the first duration is the duration after the terminal device enters the idle state and before entering the dormant state, and the first duration is based on the terminal device's Satellite coverage information determined.
  • a cause value from the mobility management network element is received, and the cause value is discontinuous satellite coverage.
  • the cause value is used to indicate that the terminal device does not perform uplink transmission during sleep; when there is a demand for uplink transmission, it is determined not to perform uplink transmission according to the cause value.
  • the embodiment of the present application provides a communication method, and the method may be executed by an access network device or a module (such as a chip) applied to the access network device.
  • the method includes: sending a context release request to a mobility management network element according to satellite coverage information of the terminal device, where the context release request is used to request the mobility management network element to release the context of the terminal device, and the satellite coverage
  • the information indicates the period of time that the terminal device is covered by the satellite network and/or the period of time that is not covered by the satellite network; receiving a periodic TAU cycle from the mobility management network element, and sending the cycle to the terminal device Periodic TAU period, the time period corresponding to the periodic TAU period includes the time period when the terminal device is not covered by the satellite network; or, receive the periodical registration period from the mobility management network element, and send to the terminal
  • the device sends the periodic registration period, and the time period corresponding to the periodic registration period includes a time period when the terminal device is not covered by the satellite network.
  • the embodiment of the present application provides a communication device, and the device may be a mobility management network element or a module (such as a chip) applied to the mobility management network element.
  • the device has the function of realizing any realization method of the first aspect to the third aspect and the seventh aspect. This function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the embodiment of the present application provides a communication device, and the device may be a terminal device or a module (such as a chip) applied to the terminal device.
  • the device has the function of realizing any realization method of the fourth aspect, the fifth aspect or the eighth aspect. This function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the embodiment of the present application provides a communication device, and the device may be an access network device or a module (such as a chip) applied to the access network device.
  • the device has the function of implementing any implementation method of the sixth aspect or the ninth aspect. This function may be implemented by hardware, or may be implemented by executing corresponding software on the hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the embodiment of the present application provides a communication device, including a processor and a memory; the memory is used to store computer instructions, and when the device is running, the processor executes the computer instructions stored in the memory, so that the device Execute any implementation method in the first aspect to the ninth aspect above.
  • the embodiment of the present application provides a communication device, including a unit or means (means) for performing each step of any implementation method in the first aspect to the ninth aspect.
  • the embodiment of the present application provides a communication device, including a processor and an interface circuit, the processor is used to communicate with other devices through the interface circuit, and execute any implementation method in the first aspect to the ninth aspect above .
  • the processor includes one or more.
  • an embodiment of the present application provides a communication device, including a processor coupled to a memory, and the processor is used to call a program stored in the memory to execute any implementation in the first aspect to the ninth aspect above method.
  • the memory may be located within the device or external to the device. And there may be one or more processors.
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores instructions, and when it is run on the communication device, the above-mentioned first aspect to the ninth aspect Any implementation method of is executed.
  • the embodiment of the present application also provides a computer program product, the computer program product includes a computer program or instruction, when the computer program or instruction is run by the communication device, any of the above first to ninth aspects The implementation method is executed.
  • the embodiment of the present application further provides a chip system, including: a processor, configured to execute any implementation method in the first aspect to the sixth aspect above.
  • the embodiment of the present application further provides a communication system, including: a mobility management network element and an access network device.
  • the mobility management network element is used to execute any implementation method of the first aspect to the third aspect.
  • the access network device is used to send the satellite coverage information of the cell where the terminal device is located to the mobility management network element.
  • the embodiment of the present application further provides a communication system, including: a mobility management network element and an access network device.
  • the mobility management network element is used to implement any implementation method of the seventh aspect.
  • the access network device is configured to execute any implementation method of the ninth aspect.
  • Figure 1(a) is a schematic diagram of a 5G network architecture based on a service architecture
  • Figure 1(b) is a schematic diagram of a 5G network architecture based on a point-to-point interface
  • FIG. 2 is a schematic flowchart of a communication method provided in an embodiment of the present application.
  • Figure 3(a) is a schematic diagram of the periodic TAU cycle provided by the embodiment of the present application.
  • FIG. 3(b) is a schematic diagram of the eDRX cycle provided by the embodiment of the present application.
  • FIG. 3(c) is a schematic diagram of a dormant time period provided by the embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • Figure 13(a) is a schematic diagram of a periodic TAU cycle or a periodic registration cycle provided by the embodiment of the present application;
  • FIG. 13(b) is another schematic diagram of the periodic TAU cycle or the periodic registration cycle provided by the embodiment of the present application.
  • FIG. 14 is a schematic flowchart of a communication method provided in an embodiment of the present application.
  • FIG. 15 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • Fig. 16(a) is a schematic flowchart of a communication method provided by the embodiment of the present application.
  • FIG. 16(b) is a schematic flowchart of a communication method provided by the embodiment of the present application.
  • FIG. 17 is a schematic diagram of a communication device provided by an embodiment of the present application.
  • FIG. 18 is a schematic diagram of a communication device provided by an embodiment of the present application.
  • the 3GPP standard group has formulated the architecture of the next generation mobile communication network system (next generation system), called the fifth Generation (the 5th generation, 5G) network architecture.
  • This architecture not only supports wireless access technologies (such as long term evolution (LTE) access technologies, 5G radio access network (RAN) access technologies, etc.) defined by the 3GPP standard group to access the 5G core Network (core network, CN), and supports the use of non-3GPP (non-3GPP) access technology through non-3GPP interworking function (non-3GPP interworking function, N3IWF) or next generation access gateway (next generation packet data gateway, ngPDG) Access to the core network.
  • wireless access technologies such as long term evolution (LTE) access technologies, 5G radio access network (RAN) access technologies, etc.
  • RAN radio access network
  • CN 5G core Network
  • N3IWF non-3GPP interworking function
  • next generation access gateway next generation packet data gateway
  • Figure 1(a) is a schematic diagram of a 5G network architecture based on a service-based architecture.
  • the 5G network architecture shown in Figure 1(a) may include terminal equipment, access network equipment, and core network equipment.
  • the terminal device accesses the data network (data network, DN) through the access network device and the core network device.
  • data network data network
  • the core network equipment includes but not limited to some or all of the following network elements: authentication server function (authentication server function, AUSF) network element (not shown in the figure), unified data management (unified data management, UDM) network element, unified data repository (unified data repository, UDR) network element, network repository function (network repository function, NRF) network element (not shown in the figure), network exposure function (network exposure function, NEF) network element (not shown in the figure) shown), application function (application function, AF) network element, policy control function (policy control function, PCF) network element, access and mobility management function (access and mobility management function, AMF) network element, session management function (session management function, SMF) network element, user plane function (user plane function, UPF) network element, binding support function (binding support funciton, BSF) network element (not shown in the figure), network data analysis function (network data analysis function, NWDAF) network element (not shown in the figure).
  • authentication server function authentication server function, AUSF
  • UDM unified data
  • the terminal device may be a user equipment (user equipment, UE), a mobile station, a mobile terminal, and the like.
  • Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (internet of things, IOT), virtual reality, augmented reality, industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc.
  • Terminal devices can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, urban air vehicles (such as drones, helicopters, etc.), ships, robots, robotic arms, smart home devices, etc.
  • the access network device may be a radio access network (RAN) device or a wired access network (wireline access network, FAN) device.
  • the wireless access network equipment includes 3GPP access network equipment, untrusted non-3GPP access network equipment and trusted non-3GPP access network equipment.
  • 3GPP access network equipment includes but not limited to: evolved base station (evolved NodeB, eNodeB) in LTE, next generation base station (next generation NodeB, gNB) in 5G mobile communication system, base station or completed base station in future mobile communication system Partial functional modules or units, such as centralized unit (central unit, CU), distributed unit (distributed unit, DU), etc.
  • Untrusted non-3GPP access network equipment includes but not limited to: untrusted non-3GPP access gateway or N3IWF equipment, untrusted wireless local area network (wireless local area network, WLAN) access point (access point, AP), switch ,router.
  • Trusted non-3GPP access network devices include, but are not limited to: trusted non-3GPP access gateways, trusted WLAN APs, switches, and routers.
  • Wired access network equipment includes but not limited to: wired access gateway (wireline access gateway), fixed telephone network equipment, switches, routers.
  • Access network equipment and terminal equipment can be fixed or mobile. Access network equipment and terminal equipment can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and artificial satellites in the air.
  • the AMF network element includes functions such as mobility management and access authentication/authorization. In addition, it is also responsible for transferring user policies between terminal equipment and PCF network elements.
  • the SMF network element includes the functions of performing session management, executing the control strategy delivered by the PCF network element, selecting UPF network elements, and assigning Internet protocol (internet protocol, IP) addresses of terminal equipment, etc.
  • Internet protocol Internet protocol, IP
  • the UPF network element includes functions such as user plane data forwarding, session/flow-based charging statistics, and bandwidth limitation.
  • UDM network element including the execution management of subscription data, user access authorization and other functions.
  • the UDR network element includes the access function for performing subscription data, policy data, application data and other types of data.
  • NEF network elements are used to support the opening of capabilities and events.
  • the AF network element transmits the requirements from the application side to the network side, such as QoS requirements or user status event subscription.
  • the AF network element may be a third-party functional entity, or an application service deployed by an operator, such as an IP Multimedia Subsystem (IP Multimedia Subsystem, IMS) voice call service.
  • IP Multimedia Subsystem IP Multimedia Subsystem, IMS
  • the PCF network element includes policy control functions such as charging for sessions and service flow levels, QoS bandwidth guarantee, mobility management, and terminal policy decision-making.
  • PCF network elements include access and mobility management policy control function (access and mobility management policy control function, AM PCF) network elements and session management policy control function (session management PCF, SM PCF) network elements, AM PCF network elements can To provide mobility management policies, SM PCF network elements can provide session management policies.
  • the NRF network element can be used to provide a network element discovery function, and provide network element information corresponding to the network element type based on the request of other network elements.
  • NRF network elements also provide network element management services, such as network element registration, update, de-registration, and network element status subscription and push.
  • BSF network element can provide functions such as BSF service registration/logout/update, connection detection with NRF network element, creation of session binding information, acquisition of terminal device information, and query of session binding information with duplicate IP addresses.
  • the AUSF network element is responsible for authenticating users to determine whether users or devices are allowed to access the network.
  • NWDAF network elements are mainly used to collect data (including one or more of terminal equipment data, access network equipment data, core network network element data, and third-party application data), and provide data analysis services based on machine learning models, Data analysis results can be output for network, network management, and application execution policy decisions.
  • the NWDAF network element can be a single network element, or it can be set up together with other network elements.
  • the NWDAF network element can be set in the PCF network element or the AMF network element.
  • DN is a network outside the operator's network.
  • the operator's network can access multiple DNs, and various services can be deployed on the DN, which can provide data and/or voice services for terminals.
  • DN is a private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be terminals, and the control server of the sensors is deployed in the DN, and the control server can provide services for the sensors.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • DN is a company's internal office network.
  • the mobile phone or computer of the company's employees can be a terminal, and the employee's mobile phone or computer can access information and data resources on the company's internal office network.
  • Npcf, Nufr, Nudm, Naf, Namf, and Nsmf are the service interfaces provided by the above-mentioned PCF, UDR, UDM, AF, AMF, and SMF, respectively, and are used to call corresponding service operations.
  • N1, N2, N3, N4, and N6 are interface serial numbers. The meanings of these interface serial numbers are as follows:
  • N1 the interface between the AMF and the terminal device, which can be used to transmit non-access stratum (non access stratum, NAS) signaling (such as including QoS rules from the AMF) to the terminal device.
  • non-access stratum non access stratum, NAS
  • N2 the interface between the AMF and the access network device, which can be used to transfer radio bearer control information from the core network side to the access network device.
  • N3 the interface between the access network device and the UPF, mainly used to transfer the uplink and downlink user plane data between the access network device and the UPF.
  • N4 The interface between SMF and UPF, which can be used to transfer information between the control plane and the user plane, including controlling the delivery of forwarding rules, QoS rules, traffic statistics rules, etc. for the user plane, as well as user plane information report.
  • N6 interface between UPF and DN, used to transmit uplink and downlink user data flow between UPF and DN.
  • Figure 1(b) is a schematic diagram of a 5G network architecture based on a point-to-point interface.
  • the introduction of the functions of the network elements can refer to the introduction of the functions of the corresponding network elements in Figure 1(a), and will not be repeated here.
  • the main difference between Figure 1(b) and Figure 1(a) is that the interface between each control plane network element in Figure 1(a) is a service interface, and each control plane network element in Figure 1(b) The interface between them is a point-to-point interface.
  • N1, N2, N3, N4 and N6 interfaces can refer to the foregoing description.
  • N5 the interface between the AF and the PCF, which can be used for sending application service requests and reporting network events.
  • N7 the interface between PCF and SMF, which can be used to deliver protocol data unit (protocol data unit, PDU) session granularity and service data flow granularity control policy.
  • protocol data unit protocol data unit
  • PDU protocol data unit
  • N8 The interface between AMF and UDM, which can be used for AMF to obtain subscription data and authentication data related to access and mobility management from UDM, and for AMF to register information related to terminal equipment mobility management with UDM.
  • N9 a user plane interface between UPF and UPF, used to transmit uplink and downlink user data flows between UPFs.
  • N10 the interface between SMF and UDM, which can be used for SMF to obtain session management-related subscription data from UDM, and for SMF to register terminal device session-related information with UDM.
  • N11 The interface between SMF and AMF, which can be used to transfer the PDU session tunnel information between the access network device and UPF, transfer the control message sent to the terminal device, and transfer the wireless resource sent to the access network device control information, etc.
  • N15 the interface between the PCF and the AMF, which can be used to issue terminal policies and access control-related policies.
  • N35 the interface between UDM and UDR, which can be used for UDM to obtain user subscription data information from UDR.
  • N36 the interface between PCF and UDR, which can be used for PCF to obtain policy-related subscription data and application data-related information from UDR.
  • the above-mentioned network element or function may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform.
  • the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.
  • the mobility management network element may be a mobility management entity (mobility management entity, MME) in a fourth generation (4th generation, 4G) network, an AMF network element in a 5G network, or a future communication system
  • MME mobility management entity
  • 4G fourth generation
  • AMF AMF network element
  • 5G 5th generation
  • 5G 5th generation
  • future communication system Other network elements having the functions of MME or AMF network elements.
  • the access network device may be an access network device (such as eNB, etc.) in a 4G network, an access network device (such as a gNB, etc.) Other network elements that function as network access equipment or access network equipment of the 5G network.
  • an access network device such as eNB, etc.
  • an access network device such as a gNB, etc.
  • Other network elements that function as network access equipment or access network equipment of the 5G network.
  • the policy control network element may be a policy and charging rules function (policy and charging rules function, PCRF) network element in a 4G network, a PCF network element in a 5G network, or a PCRF network element in a future communication system. other network elements that function as PCF network elements.
  • policy and charging rules function policy and charging rules function, PCRF
  • the storage network element may be a home subscriber server (HSS) in a 4G network, a UDR network element in a 5G network, or other devices that have the function of an HSS or UDR network element in a future communication system. network element.
  • HSS home subscriber server
  • periodic tracking area update tilt area update
  • periodic registration is a term in 5G.
  • the periodic TAU period may be represented by a periodic TAU timer (timer), and the periodic registration period may be represented by a periodic registration timer (timer).
  • timer a periodic TAU timer
  • timer a periodic registration timer
  • the periodic TAU timer is a name in 4G
  • the periodic registration timer is a name in 5G.
  • the detachment process and the deregistration process have the same meaning in the embodiment of the present application.
  • the de-attachment process is a name in 4G
  • the de-registration process is a name in 5G.
  • the maximum waiting time may be the downlink buffer duration in the 4G network, or the maximum waiting time in the 5G network, or other parameters with the downlink buffer duration or the maximum waiting time in the future communication system.
  • mMTC is one of the important application scenarios of 5G network, mainly for various Internet of things (IoT) business applications based on cellular network, such as sea/land/railway/air transportation, oil and gas exploration measurement, environmental monitoring and mine development etc.
  • IoT Internet of things
  • 3GPP defined narrowband internet of things narrowband internet of things, NB-IoT
  • enhanced machine type communication enhanced machine type communication
  • eMTC enhanced machine type communication
  • LTE -machine type communication LTE-machine type communication
  • Low-orbit satellites can assist NB-IoT/eMTC to achieve global coverage of the Internet of Things, thereby avoiding network coverage problems caused by insufficient deployment of ground network facilities.
  • a terminal device in the NB-IoT/eMTC scenario when it enters the idle state, it may enter the dormant state. At this time, the terminal device and the AMF on the core network side will maintain a rough synchronization to ensure that the AMF can Perceive when the terminal device enters the sleep state.
  • the UPF When the downlink data of the terminal device arrives, the UPF will notify the SMF, and then the SMF will notify the AMF. If the AMF finds that the terminal device is still in a sleep state and cannot be reached, it will estimate a maximum waiting time based on the sleep time of the terminal device.
  • the data is cached and waits for the end device to be reachable.
  • PSM power saving model
  • eDRX extended discontinuous reception
  • 3GPP introduces NB-IoT and eMTC into the satellite network architecture, thereby enabling satellites to support 4G NB-IoT and eMTC.
  • the 5G satellite architecture has been researched as early as R16 5G, aiming to realize the integration of 5G architecture and satellite.
  • ground coverage is always in motion due to the regular movement of satellites around the Earth.
  • the definition continues to use the original concept of ground coverage fixed cells, that is, although the satellite covered cells are moving, the ground access network equipment will be based on the corresponding relationship between the satellite coverage and the ground fixed cells , and map the cell covered by the satellite to a fixed cell on the ground, so as to ensure that the cell where the terminal device is located is still a fixed cell on the ground as perceived by the core network side.
  • one or more satellites may only provide network communication services for the oilfield mining site within a specific period of time while regularly revolving around the earth, such as oil field Mining data collection and reporting of various sensors. That is to say, the network communication service provided by the satellite to the terminal equipment on the ground is discontinuously covered, and the terminal equipment will be covered by the satellite network in some periods of time, and not covered by the satellite network in another period of time.
  • the terminal device may not be covered by the satellite network for a long time, and the sleep time of eDRX in the traditional NB-IoT or eMTC scenario is short, so it cannot be applied to this scenario. That is to say, according to the sleep mode of eDRX in the traditional NB-IoT or eMTC scenario, the terminal device may still be in a scenario not covered by the satellite network after waking up after the sleep.
  • the satellite coverage information of the terminal device indicates a time period during which the terminal device is covered by the satellite network and/or a time period during which the terminal device is not covered by the satellite network.
  • the satellite coverage information of the terminal device indicates that the terminal device is not covered by the satellite network from 8 am to 9 am every day, and/or indicates that the terminal device is not covered by the satellite network from 0 am to 8 am every day, and from 9 am to 9 am. Covered by satellite network at 0:00 am.
  • the satellite coverage information of the terminal device may be the satellite coverage information corresponding to the location of the terminal device, or the satellite coverage information of the satellite cell where the terminal device is located, or the satellite coverage information corresponding to the tracking area (Tracking Area, TA) where the terminal device is located. Satellite coverage information. For example, if the terminal device is located in cell 1, the satellite coverage information of the terminal device may be the satellite coverage information of cell 1. For another example, if the terminal device is located in the cell 2, the satellite coverage information of the terminal device may be the satellite coverage information of the cell 2. Alternatively, the satellite coverage information of the terminal device in the embodiment of the present application may also be ephemeris information.
  • the ephemeris information of a cell refers to the regularity of the satellites corresponding to the cell revolving around the earth.
  • the ephemeris information includes satellite orbit plane parameters and satellite parameters, such as satellite moving speed, satellite moving direction, satellite orbit The distance from the ground, the reference time point, etc., according to the ephemeris information of one or more satellites corresponding to the satellite cell, the time period when the cell is covered by the satellite network and/or the time period when the cell is not covered by the satellite network can be known.
  • the satellite coverage information of the cell indicates the time period during which the cell is covered by the satellite network and/or the time period during which the cell is not covered by the satellite network.
  • the N2 establishment message includes the identification information of satellite cell 1, ephemeris information 1 or satellite cell 1 corresponding to satellite cell 1.
  • Coverage information 1 identification information of satellite cell 2, ephemeris information 2 or satellite coverage information 2 corresponding to satellite cell 2, identification information of satellite cell 3, and ephemeris information 3 or satellite coverage information 3 corresponding to satellite cell 3.
  • FIG. 2 it is a schematic flowchart of a communication method provided by an embodiment of the present application. This method can be used to solve problem 1 above. The method includes the following steps:
  • Step 201 the mobility management network element determines the sleep time information of the terminal device according to the satellite coverage information of the terminal device.
  • the access network device needs to establish a connection with the mobility management network element.
  • this interface is the N2 interface.
  • the permanent management network element sends an N2 establishment message, and the N2 establishment message may carry identification information of satellite cells under the access network device and ephemeris information or satellite coverage information of satellites corresponding to each satellite cell.
  • the mobility management network element can obtain the satellite cell information where the terminal device is located. For example, the terminal device is located in the satellite cell 1 under the access network device, and the mobility management network element determines the The satellite coverage information is the satellite coverage information of the terminal device.
  • the mobility management network element if the mobility management network element receives the ephemeris information of the satellite corresponding to cell 1 from the access network device, the mobility management network element needs to first determine the ephemeris information of cell 1 according to the ephemeris information of the satellite corresponding to cell 1. Satellite coverage information.
  • the mobility management network element may also save the satellite coverage information as satellite coverage information of a terminal device accessing the network from cell 1.
  • the access network device sends the ephemeris information or satellite coverage information of the satellite corresponding to the satellite cell where the terminal device is located to the mobility management network Yuan.
  • the terminal device sends a registration request message to the access network device.
  • the access network device After receiving the registration request message, the access network device sends the registration request message to the mobility management network element, and at the same time sends the ephemeris information or satellite coverage information of the satellite corresponding to the satellite cell where the terminal device is located, that is, in the initial N2 message Add the ephemeris information or satellite coverage information of the satellite corresponding to the satellite cell where the terminal device is located in.
  • the mobility management network element needs to determine the satellite coverage information of the satellite cell where the terminal device is located according to the ephemeris information. Then, the mobility management network element uses the satellite coverage information of the cell as the satellite coverage information of the terminal equipment.
  • a third-party network element such as an application server outside the core network or a network element dedicated to interacting with satellites or network elements dedicated to satellite management in the core network, may provide mobility management The network element sends ephemeris information or satellite coverage information of the satellite corresponding to the satellite cell where the terminal device is located. If the third-party network element sends the ephemeris information of the satellite corresponding to the satellite cell where the terminal device is located, the mobility management network element needs to determine the satellite coverage information of the satellite cell where the terminal device is located according to the ephemeris information. Then, the mobility management network element uses the satellite coverage information of the cell as the satellite coverage information of the terminal device.
  • the sleep time period corresponding to the sleep time information includes a time period when the terminal device is not covered by the satellite network.
  • the mobility management network element also determines one or more of the eDRX cycle, periodic TAU cycle, or periodic registration cycle of the terminal device according to the satellite coverage information, and the sleep time period corresponding to the sleep time information is determined by Included in the sleep time range of the eDRX cycle, periodic TAU cycle or periodic registration cycle.
  • the sleep time information here includes the sleep start time, and the sleep start time is located in the eDRX cycle, the periodic TAU cycle or the periodic registration cycle. Referring to FIG. 3( a ), it is a schematic diagram of a periodic TAU.
  • the terminal device executes the periodic TAU process, initiates a network connection, and then the terminal device enters the sleep state from the sleep start time, and the sleep period of the terminal device in the periodic TAU period includes terminal
  • the time period when the device is not covered by the satellite network can ensure that the terminal device enters the dormant state during the time period not covered by the satellite network, avoiding the periodic TAU process of the terminal device during the time period without network coverage, and reducing the energy consumption of the terminal device. consumption.
  • the dormancy time is greater than or equal to the time when the terminal device is not covered by the satellite network. Referring to FIG.
  • time T1 is the start time of dormancy
  • time T2 is the end time of dormancy
  • T2 is also the end time of the TAU cycle.
  • the difference between T2 and T1 is equal to the time period during which the terminal device is not covered by the satellite network.
  • the sleep time information determined in step 201 is the sleep start time in the example of FIG. 3( a ).
  • this process is generally called a periodic TAU process in a 4G network, and it is called a periodic registration process in a 5G network.
  • FIG. 3( b ) it is a schematic diagram of a certain eDRX cycle.
  • the terminal device performs monitoring according to the DRX cycle, and if there is no network connection requirement after the paging time window arrives, it will enter the sleep state at the sleep start time, and the terminal device
  • the sleep time period in the eDRX cycle includes the time period when the terminal device is not covered by the satellite network, so that the terminal device can be guaranteed to enter the sleep state during the time period not covered by the satellite network, and the terminal device can be avoided when there is no satellite network coverage. Wake up during the segment to monitor paging messages, reducing the energy consumption of terminal equipment. Wherein, the dormancy time is greater than or equal to the time when the terminal device is not covered by the satellite network. Referring to FIG.
  • time T1 is the start time of sleep
  • time T2 is the end time of sleep
  • T2 is also the end time of the eDRX cycle.
  • the difference between T2 and T1 is equal to or greater than the time period during which the terminal device is not covered by the satellite network.
  • the sleep time information determined in step 201 includes the sleep start time in the example of FIG. 3( b ).
  • the sleep time information includes a sleep start time and a sleep end time, and the sleep time period between the sleep start time and the sleep end time includes a time period when the terminal device is not covered by the satellite network.
  • the sleep time information includes a sleep start time and a sleep duration, and the sleep end time can be obtained according to the sleep start time and the sleep duration.
  • the terminal device within the sleep time period corresponding to the sleep time information, the terminal device will continue to sleep and will not perform services, including not performing a periodic TAU process or a periodic registration process.
  • the time period not covered by the satellite network indicated by the satellite coverage information of the terminal device is not included in any eDRX cycle or TAU cycle, but is a separate sleep time period. Referring to FIG.
  • the sleep time information indicates a separate sleep time period, the sleep time period coincides with the time period when the terminal device is not covered by the satellite network or the sleep time period is greater than the time period when the terminal device is not covered by the satellite network, in this sleep time period
  • the internal terminal equipment enters the dormant state, which can ensure that the terminal equipment enters the dormant state during the period of time when it is not covered by the satellite network, which can avoid unnecessary and invalid network connections and reduce the energy consumption of the terminal equipment.
  • time T1 is the start time of dormancy
  • time T2 is the end time of dormancy
  • the time period from T1 to T2 coincides with the time period when the terminal device is not covered by the satellite network or is longer than the time period when the terminal device is not covered by the satellite network time period.
  • an eDRX cycle is entered.
  • the eDRX cycle may be determined according to an existing scheme.
  • There is also a dormancy time period in the eDRX cycle, and the dormancy time period may be called a normal eDRX dormancy time period.
  • the sleep time information determined in step 201 includes the sleep start time and sleep end time in the example in FIG. 3( c ).
  • the sleep time information determined in step 201 includes the sleep start time and sleep duration in the example in FIG. 3( c ).
  • Step 202 the mobility management network element sends sleep time information to the terminal equipment.
  • the terminal device receives the sleep time information.
  • the mobility management network element can carry the sleep time information in the registration acceptance message sent to the terminal device.
  • the registration acceptance message also includes the eDRX period, periodic registration period or periodic TAU One or more of the cycles.
  • the sleep time information may be carried in an attach accept message or a TAU accept message sent to the terminal device.
  • Step 203 the terminal device sleeps according to the sleep time information.
  • the terminal device enters a sleep state within a sleep time period corresponding to the sleep time information, and the sleep time period includes a time period when the terminal device is not covered by the satellite network.
  • Step 204 when the de-registration timer (or de-attach timer) corresponding to the terminal device expires, the mobility management network element determines that the terminal device is not covered by the satellite network according to the satellite coverage information, and determines not to perform de-registration (or de-attachment timer) on the terminal device. ).
  • This step 204 is an optional step.
  • not performing de-registration on the terminal device can also be understood as keeping the registration status of the terminal device unchanged.
  • Not performing detachment on the terminal device can also be understood as keeping the attachment state of the terminal device unchanged.
  • the mobility management network element that is, the MME, determines that the terminal device is not covered by the satellite network according to the satellite coverage information, Determine not to perform detachment on the terminal device, that is, keep the current mobility management state of the terminal device as attached or EMM-registered (EPSMobility Management-Registered, EMM-Registered); if the mobility management network element determines that the terminal device is For satellite network coverage, it is determined to perform detachment on the terminal device, that is, the current mobility management state of the terminal device is changed to a detachment or EMM deregistration state.
  • EMM-registered EMM-registered
  • the mobility management network element when the terminal device is not covered by the satellite network, the mobility management network element does not perform the detach process for the terminal device, which can reduce the state of the terminal device between attaching and detaching, or between registration and non-registration. Handover, thereby reducing the signaling interaction between the terminal device and the network, and reducing the energy consumption of the terminal device. This is because: when the terminal device is not covered by the satellite network, the energy consumption of the terminal device is relatively low at this time. If the mobility management network element detaches the terminal device, after the terminal device is covered by the satellite network The device needs to be re-attached again, which instead causes more signaling interactions, resulting in increased energy consumption of the terminal device.
  • the de-registration timer (or implicit de-attach timer) corresponding to the terminal device expires
  • the mobility management network element AMF determines that the terminal device is not covered by the satellite network according to the satellite coverage information, the determination is incorrect.
  • the end device performs a de-registration. If the mobility management network element determines that the terminal device is covered by the satellite network according to the satellite coverage information, it determines not to register the terminal device, that is, keeps the current terminal device in the registered state.
  • the mobility management network element when the terminal device is not covered by the satellite network, the mobility management network element does not deregister the terminal device, which can reduce the status of the terminal device from switching back and forth between registration and deregistration, thereby reducing the communication between the terminal device and the network. Command interaction, reducing the energy consumption of terminal equipment. This is because: when the terminal device is not covered by the satellite network, the energy consumption of the terminal device is relatively low. If the mobility management network element deregisters the terminal device, after the terminal device is covered by the satellite network, the terminal device The device needs to re-register again, which instead causes more signaling interactions, resulting in increased energy consumption of the terminal device.
  • the mobility management network element determines the sleep time information according to the satellite coverage information of the terminal device, and the sleep time period corresponding to the sleep time information includes the time period when the terminal device is not covered by the satellite network, so as to ensure that the terminal device can The ground sleeps during the time period not covered by the satellite network, avoiding unnecessary network connection operations such as cell scanning and cell selection, so as to save energy consumption of terminal equipment.
  • FIG. 4 it is a schematic flowchart of a communication method provided by an embodiment of the present application. This method can be used to solve problem 1 above. The method includes the following steps:
  • Step 401 when the de-registration timer (or detach timer) corresponding to the terminal device expires, the mobility management network element determines that the terminal device is not covered by the satellite network according to the satellite coverage information of the terminal device.
  • the implementation method for the mobility management network element to determine the satellite coverage information of the terminal device may refer to the description of the foregoing step 201, and details are not repeated here.
  • the de-registration timer may also be an implicit de-registration timer, which is not limited herein.
  • the detach timer may also be an implicit detach timer, which is not limited herein.
  • Step 402 the mobility management network element determines not to perform de-registration (or de-attachment) on the terminal device.
  • not performing de-registration on the terminal device can also be understood as keeping the registration status of the terminal device unchanged.
  • Not performing detachment on the terminal device can also be understood as keeping the attachment state of the terminal device unchanged, that is, keeping the terminal device in the EMM registration state.
  • the response is that the terminal device is not covered by the satellite network.
  • the mobility management network element that is, the MME
  • determines that the terminal device is not covered by the satellite network according to the satellite coverage information it is determined not to detach the terminal device, that is Keep the current mobility management state of the terminal device as attached or EMM registration state
  • the mobility management network element determines that the terminal device is covered by the satellite network according to the satellite coverage information, it is determined to perform detachment on the terminal device, that is, the current mobility of the terminal device
  • the permanent management state changes to the deattached or EMM deregistered state.
  • the mobility management network element when the terminal device is not covered by the satellite network, the mobility management network element does not perform the detach process for the terminal device, which can reduce the state of the terminal device from switching back and forth between attach and detach, thereby reducing the number of connections between the terminal device and the network. signaling interaction to reduce the energy consumption of terminal equipment. This is because: when the terminal device is not covered by the satellite network, the energy consumption of the terminal device is relatively low at this time. If the mobility management network element detaches the terminal device, after the terminal device is covered by the satellite network The device needs to be re-attached again, which instead causes more signaling interactions, resulting in increased energy consumption of the terminal device.
  • the mobility management network element determines that the terminal device is not covered by the satellite network according to the satellite coverage information, it is determined not to perform de-registration on the terminal device. If the mobility management network element determines that the terminal device is covered by the satellite network according to the satellite coverage information, it determines not to register the terminal device, that is, keeps the current terminal device in the registered state. According to this solution, when the terminal device is not covered by the satellite network, the mobility management network element does not deregister the terminal device, which can reduce the status of the terminal device from switching back and forth between registration and deregistration, thereby reducing the communication between the terminal device and the network.
  • the switching of the state of the terminal device between registration and de-registration, or switching between attachment and detachment is reduced, the signaling interaction between the terminal device and the network can be reduced, and the energy consumption of the terminal device can be reduced.
  • step 402 the following step 403 and step 404 may also be performed.
  • Step 403 the mobility management network element sends the first information to the terminal device.
  • the terminal device receives the first information.
  • the first information instructs the terminal device to perform uplink transmission according to satellite network coverage when there is a need for uplink transmission.
  • Step 404 when there is a demand for uplink transmission, the terminal device determines, according to the first information, that the terminal device is not covered by the satellite network, and then determines not to perform uplink transmission.
  • the uplink transmission requirements here include but are not limited to: periodic TAU, periodic registration, and uplink data transmission.
  • the first information is the satellite coverage information of the terminal device described in step 401 above.
  • the mobility management network element sends the satellite coverage information of the terminal device to the terminal device, which is used to instruct the terminal device to perform uplink transmission according to the satellite coverage information when there is an uplink transmission requirement. Therefore, when the terminal device has an uplink transmission requirement, it is judged whether the terminal device currently has satellite network coverage according to the satellite coverage information. If not covered by the satellite network, it is determined not to perform uplink transmission. If it is covered by the satellite network, it is determined to perform uplink transmission.
  • the first information is instruction information
  • the instruction information specifically indicates that when the terminal device has an uplink transmission requirement, it checks satellite network coverage by itself, and performs uplink transmission according to the satellite network coverage. Therefore, when the terminal device has an uplink transmission requirement, the terminal device first checks whether it is currently covered by the satellite network. If not covered by the satellite network, it is determined not to perform uplink transmission. If it is covered by the satellite network, it is determined to perform uplink transmission.
  • the mobility management network element sends the first information to the terminal device, it also sends the satellite coverage information of the terminal device to the terminal device.
  • the first information here is A piece of instruction information
  • the instruction information specifically indicates: when the terminal device has an uplink transmission requirement, perform uplink transmission according to the satellite coverage information. Therefore, when the terminal device has an uplink transmission requirement, the terminal device judges whether it is covered by the satellite network according to the satellite coverage information. If not covered by the satellite network, it is determined not to perform uplink transmission. If it is covered by the satellite network, it is determined to perform uplink transmission.
  • step 403 and step 404 when the terminal device is not covered by the satellite network, even if there is a demand for uplink transmission, it will not perform uplink transmission, so that unnecessary and invalid network connection operations such as cell scanning and cell selection can be avoided to save Energy consumption of terminal equipment.
  • FIG. 5 it is a schematic flowchart of a communication method provided by an embodiment of the present application. This method can be used to solve problem 2 above. The method includes the following steps:
  • Step 501 the mobility management network element determines the satellite coverage information of the terminal equipment.
  • the mobility management network element may determine the satellite coverage information of the terminal device according to the method described in step 201 above.
  • the mobility management network element can also determine the satellite coverage information of the terminal device by the following method: the mobility management network element sends a paging message to the access network device, and the paging message includes the information of the terminal device in the idle state. Identification information, the paging message indicates the paging terminal device.
  • the access network device paging the terminal device, if the access network device determines that the cell where the terminal device is located is not currently covered by the satellite network, the access network device will fail to page, so the access network device sends a message to the mobility management network element sending a first message, where the first message includes a paging failure indication and satellite coverage information of the satellite cell where the terminal device is located, where the paging failure indication is used to indicate that the cause of the paging failure is that it is not covered by the satellite network.
  • the paging failure indication also indicates that the mobility management network element needs to perform reachability judgment/paging according to the satellite coverage information.
  • the satellite coverage information of the satellite cell where the terminal device is located is the satellite coverage information of the terminal device.
  • the mobility management network element can also determine the satellite coverage information of the terminal device by the following method: the mobility management network element sends a paging message to the access network device, and the paging message includes the information of the terminal device in the idle state. Identification information, the paging message indicates the paging terminal device.
  • the access network device paging the terminal device, if the access network device determines that the cell where the terminal device is located is not currently covered by the satellite network, the access network device will fail to page, so the access network device sends a message to the mobility management network element sending a first message, where the first message includes satellite coverage information of the satellite cell where the terminal device is located, where the satellite coverage information of the satellite cell where the terminal device is located is the satellite coverage information of the terminal device, and the satellite coverage information is used for Indicating that the reason for the paging failure is not being covered by the satellite network.
  • the satellite coverage information also indicates that the mobility management network element needs to perform reachability judgment/paging according to the satellite coverage information.
  • the AMF network element can execute step 501 after receiving the downlink data arrival notification from the SMF network element, that is, the downlink data arrival notification
  • the mobility management network element is triggered to execute step 501 .
  • the MME may execute step 501 after determining that there is downlink data to be transmitted on the user plane.
  • Step 502 the mobility management network element determines the maximum waiting time according to the satellite coverage information, and the maximum waiting time indicates the maximum time for waiting for the terminal device to be reachable.
  • the maximum waiting time here needs to cover the time period when the terminal device is not covered by the satellite network, or it can be understood that after the maximum waiting time is reached, the terminal device should be covered by the satellite network.
  • the maximum waiting time may be the downlink buffering time in 4G or the maximum waiting time in 5G.
  • the mobility management network element also determines that the terminal device is unreachable according to the satellite coverage information.
  • the mobility management network element is an MME.
  • the MME determines the maximum waiting time, it can determine the downlink data buffer timeout time according to the maximum waiting time, which is used to indicate whether the current core network side has cached the terminal device. data, and after the downlink data cache timeout period is reached, the MME will determine that there is no downlink cache data for the terminal device at present.
  • the maximum waiting time may also be referred to as downlink data buffering time.
  • the mobility management network element is an AMF network element.
  • the AMF network element determines the maximum waiting time, it can send the maximum waiting time to the SMF network element, and then the SMF network element can determine the extension according to the maximum waiting time.
  • Buffering time indicates the specific length of time for the user plane network element to buffer the downlink data, and after the extended buffering time is reached and the buffered data has not been sent to the terminal device, the SMF will discard the corresponding buffered data.
  • the maximum waiting time may also be referred to as an estimated maximum waiting time.
  • the mobility management network element can judge the reachability according to the satellite coverage information of the terminal equipment.
  • the terminal device performs paging without sending downlink data to the terminal device, which can reduce the energy consumption of the mobility management network element and reduce data loss.
  • the mobility management network element before step 201, before step 401, and/or before step 501, the mobility management network element also determines that the terminal device has a fixed location or a fixed moving trajectory. Or it can be understood that the mobility management network element determines that the terminal device is a terminal device with a fixed location or a terminal device with a fixed moving trajectory. For example, the mobility management network element may acquire the subscription information of the terminal device, and determine that the terminal device has a fixed location or a fixed moving track according to the subscription information of the terminal device. That is to say, the mobility management network element only executes the solutions of the embodiments corresponding to Fig. 2 , Fig. 4 and/or Fig. 5 for terminal devices with fixed positions or fixed moving trajectories.
  • the fixed moving track can be understood as the terminal device has certain mobility, but its moving track is predictable, and the network side can perceive the geographical location of the terminal device.
  • FIG. 6 it is a schematic flowchart of a communication method provided by an embodiment of the present application. This solution is a specific implementation of the above-mentioned embodiment corresponding to FIG. 2 .
  • the method includes the following steps:
  • Step 601 the access network device sends an N2 setup message (N2 setup message) to the mobility management network element.
  • the mobility management network element receives the N2 setup message.
  • the N2 establishment message is sent by the process of establishing an N2 interface with the mobility management network element after the access network equipment is powered on. If the current network is a 4G network, the N2 interface corresponds to the S1-MME interface in the 4G network.
  • the N2 establishment message includes identification information of satellite cells under the access network device and ephemeris information or satellite coverage information of satellites corresponding to each satellite cell.
  • Step 602 the terminal device sends a registration request message to the access network device.
  • the access network device receives the registration request message.
  • the registration request message is used to request registration to the network.
  • the registration request message may be a registration request message in a 5G network, or an attach message or a TAU request message in a 4G network.
  • Step 603 the access network device sends the registration request message and access network (access network, AN) parameters to the mobility management network element.
  • the mobility management network element receives the registration request message and the AN parameter.
  • the registration request message is carried by the terminal device in the NAS message sent to the mobility management network element, and the AN parameter is added by the access network device in the initial N2 message, and sent to the mobility management network element side together with the registration request message.
  • the access The AN parameters added by the network device may include ephemeris information or satellite coverage information corresponding to the satellite cell where the terminal device is located.
  • step 604 the mobility management network element determines that the terminal equipment has a fixed location or a fixed moving trajectory.
  • the mobility management network element determines that the terminal device is a terminal device with a fixed location or a terminal device with a fixed moving trajectory.
  • the mobility management network element may obtain the subscription information of the terminal device, and determine that the terminal device has a fixed location or a fixed moving track according to the subscription information of the terminal device.
  • This step 604 is an optional step.
  • Step 605 the mobility management network element determines the sleep start time of the terminal device, and one or more of the periodic TAU cycle, periodic registration or eDRX cycle according to the ephemeris information or satellite coverage information corresponding to the satellite cell where the terminal device is located .
  • the mobility management network element determines the ephemeris information corresponding to the satellite cell where the terminal device is located. Satellite coverage information corresponding to the satellite cell.
  • the periodic TAU corresponds to the periodic registration process in the 5G network, and corresponds to the periodic TAU process in the 4G network.
  • the satellite coverage information corresponding to the satellite cell where the terminal device is located is the satellite coverage information of the terminal device.
  • the time period not covered by the satellite network indicated by the satellite coverage information of the terminal device is included in a certain periodic registration period, or understood as the sleep time in the periodic registration period
  • the segment includes a time segment not covered by the satellite network indicated by the satellite coverage information of the terminal device.
  • the time period indicated by the satellite coverage information of the terminal device that is not covered by the satellite network is included in a certain eDRX cycle, or it can be understood that the sleep time period in the eDRX cycle includes the time period of the terminal device The period of time indicated by the satellite coverage information that is not covered by the satellite network.
  • the sleep time period in the eDRX cycle includes the time period of the terminal device The period of time indicated by the satellite coverage information that is not covered by the satellite network.
  • Step 606 other steps of the registration process.
  • Step 607 the mobility management network element sends a non-access stratum (non access stratum, NAS) message to the terminal device.
  • NAS non access stratum
  • the NAS message includes a dormancy start time, and also includes one or more of a periodic TAU cycle, an eDRX cycle, or a periodic registration cycle.
  • the NAS message includes a registration acceptance message or an attachment acceptance message or a TAU acceptance message, and the message includes the dormancy start time, and also includes one or more of the periodic registration cycle, the periodic TAU cycle, or the eDRX cycle .
  • Step 608 the terminal device sleeps in a periodic TAU cycle, a periodic registration cycle or an eDRX cycle according to the sleep start time.
  • the terminal device enters the sleep state from the sleep start time within the periodic TAU period, and ends the sleep state at the end of the periodic TAU period.
  • the sleep time period of the terminal device includes The period of time covered by the satellite network.
  • the terminal device may go to sleep according to the method shown in FIG. 3( a ).
  • the terminal device enters the sleep state from the start time of sleep within the eDRX cycle, and ends the sleep state at the end of the eDRX cycle.
  • the sleep time period of the terminal device includes that the terminal device is not covered by the satellite network. time period.
  • the terminal device may go to sleep according to the method shown in FIG. 3( b ).
  • the mobility management network element determines the dormancy start time, and determines the eDRX cycle, periodic TAU cycle or period according to the ephemeris information or satellite coverage information corresponding to the cell provided by the access network device One or more of the permanent registration periods, so as to ensure that the terminal device can sleep as much as possible within the time period not covered by the satellite network, avoid unnecessary network connection operations such as cell scanning and cell selection, and save terminal equipment. energy consumption.
  • FIG. 7 it is a schematic flowchart of a communication method provided by an embodiment of the present application. This solution is a specific implementation of the above-mentioned embodiment corresponding to FIG. 2 .
  • the method includes the following steps:
  • Step 701 to step 704 are the same as above step 601 to step 604.
  • step 704 is an optional step.
  • Step 705 the mobility management network element determines the sleep time information of the terminal device according to the ephemeris information or satellite coverage information corresponding to the satellite cell where the terminal device is located.
  • the mobility management network element determines the ephemeris information corresponding to the satellite cell where the terminal device is located. Satellite coverage information corresponding to the satellite cell.
  • the satellite coverage information corresponding to the satellite cell where the terminal device is located is the satellite coverage information of the terminal device.
  • the sleep time information includes a sleep start time and a sleep end time
  • the sleep time period between the sleep start time and the sleep end time is a time period when the terminal device is not covered by the satellite network.
  • the sleep time information includes the sleep start time and the sleep end time
  • the sleep time period between the sleep start time and the sleep end time includes the time period when the terminal device is not covered by the satellite network, that is, the sleep The sleep time period indicated by the start time and the sleep end time is longer than the time period when the terminal device is not covered by the satellite network.
  • the sleep time information includes a sleep start time and a sleep duration, wherein the sleep end time can be obtained according to the sleep start time and the sleep duration.
  • the terminal device will continue to sleep and will not perform services, even if it is periodic TAU, periodic registration or uplink data to be transmitted.
  • the mobility management network element may determine one or more of the eDRX cycle, periodic TAU cycle, or periodic registration cycle according to service information during the time period when the terminal device is covered by the satellite network according to the existing method.
  • the time period not covered by the satellite network indicated by the satellite coverage information of the terminal device is not included in any eDRX cycle, periodic TAU cycle or periodic registration cycle, but a separate sleep time part.
  • Step 706 other steps of the registration process.
  • Step 707 the mobility management network element sends a NAS message to the terminal device.
  • the terminal device receives the NAS message.
  • the NAS message includes sleep time information, and optionally, the NAS message also includes one or more of an eDRX cycle, a periodic TAU cycle, or a periodic registration cycle.
  • the NAS message includes a registration acceptance message, an attach acceptance message, or a TAU acceptance message, and the message includes sleep time information.
  • the registration acceptance message also includes an eDRX cycle, a periodic TAU cycle, or a periodic registration One or more of the cycles.
  • Step 708 the terminal device sleeps according to the sleep time information.
  • Sleep during the sleep time period indicated by the sleep time information and do not execute services, even if it is periodic TAU, periodic registration, or uplink data to be transmitted.
  • the terminal device after the sleep period indicated by the sleep time information, the terminal device enters the coverage of the satellite network, at this time, it may sleep according to an eDRX cycle, a periodic TAU cycle or a periodic registration cycle.
  • Step 709 when the deregistration timer (or detach timer) corresponding to the terminal device times out, the mobility management network element judges whether to perform deregistration (or detachment) on the terminal device according to the sleep time information of the terminal device.
  • the mobility management network element judges whether the terminal device is currently in an unattended state according to the sleep time information of the terminal device. During the sleep time period corresponding to the network coverage, if the terminal device is currently in the sleep time period corresponding to not being covered by the satellite network, the mobility management network element determines not to perform de-registration (or detachment) on the terminal device. If the terminal device is not currently in the sleep time period corresponding to not being covered by the satellite network, the mobility management network element determines to perform de-registration (or detachment) on the terminal device.
  • This step 709 is an optional step.
  • the mobility management network element determines the sleep time information according to the ephemeris information or satellite coverage information corresponding to the satellite cell provided by the access network device, so as to ensure that the terminal device can be in the Sleep during the time not covered by the satellite network, avoid unnecessary network connection operations such as cell selection, and save energy consumption of terminal equipment.
  • the above embodiment corresponding to FIG. 7 may be applied to a scenario where the terminal device is not covered by the satellite network for a long time.
  • the terminal device is always dormant and does not perform any business, including not performing periodic TAU, periodic registration or uplink data transmission, which can avoid unnecessary and ineffective Network connection operations such as cell scanning and cell selection can minimize the energy consumption of terminal equipment.
  • FIG. 8 it is a schematic flowchart of a communication method provided by an embodiment of the present application. This solution is a specific implementation of the above-mentioned embodiment corresponding to FIG. 4 .
  • the method includes the following steps:
  • Step 801 to step 804 are the same as above step 601 to step 604.
  • step 804 is an optional step.
  • Step 805 the mobility management network element determines the satellite coverage information of the terminal equipment.
  • the mobility management network element determines the ephemeris information corresponding to the satellite cell where the terminal device is located. Satellite coverage information corresponding to the satellite cell.
  • the satellite coverage information corresponding to the satellite cell where the terminal device is located is the satellite coverage information of the terminal device.
  • the satellite coverage information corresponding to the satellite cell where the terminal device is located is the satellite coverage information of the terminal device.
  • the mobility management network element may determine the eDRX cycle, the periodic TAU cycle or the periodic registration cycle according to the existing method.
  • Step 806 other steps of the registration process.
  • Step 807 the mobility management network element sends a NAS message to the terminal device.
  • the terminal device receives the NAS message.
  • the NAS message includes indication information and satellite coverage information of the terminal device.
  • the NAS message further includes one or more of an eDRX cycle, a periodic TAU cycle or a periodic registration cycle.
  • the instruction information is used to instruct the terminal device to initiate a periodic TAU, a periodic registration process or transmit uplink data according to the satellite coverage information of the terminal device when the periodic TAU, the periodic registration timer expires or when there is uplink data transmission.
  • the NAS message includes a registration acceptance message, an attachment acceptance message, or a TAU acceptance message, and the message includes indication information and satellite coverage information of the terminal device.
  • the message also includes eDRX cycle, periodic TAU cycle or one or more of the periodic registration cycles.
  • Step 808 the terminal device judges whether to initiate periodic TAU, periodic registration or transmit uplink data according to the indication information and the satellite coverage information of the terminal device.
  • the terminal device it is judged whether the terminal device is covered by the satellite network, that is, whether the terminal device is covered by the satellite network at the current moment.
  • the terminal device initiates periodic TAU, registers periodically or transmits uplink data.
  • the terminal device does not initiate periodic TAU, register periodically or transmit uplink data.
  • Step 809 the mobility management network element judges whether to perform de-registration (or de-attachment) of the terminal device according to the indication information and the satellite coverage information of the terminal device.
  • the corresponding de-registration timer (or de-attach timer) of the terminal device expires, it is judged whether to perform de-registration (or de-attachment) of the terminal device according to the satellite coverage information of the terminal device.
  • the mobility management network element performs de-registration (or de-attachment) on the terminal equipment.
  • the mobility management network element does not perform de-registration (or de-attachment) on the terminal device.
  • the mobility management network element determines the satellite coverage information of the terminal device, and instructs the terminal device to perform periodic TAU, periodic registration or transmission according to the satellite coverage information
  • Uplink data can prevent terminal equipment from performing periodic TAU, periodic registration or transmission of uplink data within the time range not covered by the satellite network, and can avoid unnecessary network connection operations such as cell scanning and cell selection to save terminal equipment. energy consumption. Moreover, it can also prevent the terminal device from being deregistered (or detached) by the network side within the time range not covered by the satellite network.
  • the above embodiment corresponding to FIG. 8 may be applied to a scenario where the terminal device is not covered by the satellite network for a long time. This is because: there is a limit to the cycle time of periodic TAU or periodic registration, which cannot be very large. Therefore, when the terminal device is not covered by the satellite network for a long time, it is inevitable to perform periodic TAU or periodic registration. At this time, the terminal device is not covered by the satellite network, which will cause the terminal device to perform cell scanning and cell selection continuously, resulting in higher energy consumption loss.
  • the network side does not receive periodic TAU or Periodic registration will deregister or deattach the terminal device, so in order to avoid unnecessary periodic TAU or periodic registration when the terminal device in the idle state is not covered by the satellite network, in the embodiment corresponding to Figure 8 above, when When the terminal device is not covered by the satellite network, the terminal device will not perform periodic TAU or periodic registration and uplink data transmission, and the mobility management network element on the network side will not perform de-registration (or de-attachment) on the terminal device, thus It can minimize the signaling interaction between the terminal equipment and the mobility management network element, and reduce the energy consumption of the terminal equipment.
  • FIG. 9 it is a schematic flowchart of a communication method provided by an embodiment of the present application. This solution is a specific implementation of the above-mentioned embodiment corresponding to FIG. 4 .
  • the method includes the following steps:
  • Step 901 to step 906 are the same as above step 801 to step 806.
  • Step 907 the mobility management network element sends a NAS message to the terminal device.
  • the terminal device receives the NAS message.
  • the NAS message includes indication information.
  • the NAS message further includes one or more of an eDRX cycle, a periodic TAU cycle or a periodic registration cycle.
  • the indication information is used to instruct the terminal device to self-detect whether it is covered by the satellite network when the periodic TAU timer expires or the periodic registration timer expires or there is uplink data transmission.
  • the NAS message includes a registration acceptance message, an attach acceptance message or a TAU acceptance message, and the message includes the indication information.
  • the registration acceptance message also includes an eDRX cycle and/or a TAU cycle.
  • Step 908 the terminal device judges whether to initiate periodic TAU, periodic registration or transmit uplink data according to the indication information.
  • the terminal device it is judged whether the terminal device is covered by the satellite network, that is, whether the terminal device is covered by the satellite network at the current moment.
  • the terminal device initiates periodic TAU, registers periodically or transmits uplink data.
  • the terminal device does not initiate periodic TAU, register periodically or transmit uplink data.
  • Step 909 is the same as step 809 above.
  • the mobility management network element instructs the terminal device to perform periodic TAU, periodic registration, or transmit uplink data according to whether it is covered by the satellite network, which can prevent the terminal device from being covered by the satellite network.
  • Periodic TAU, periodical registration, or uplink data transmission within a certain time range can avoid unnecessary network connection operations such as cell scanning and cell selection, so as to save energy consumption of terminal equipment.
  • it can also prevent the terminal device from being deregistered (or detached) by the network side within the time range not covered by the satellite network.
  • the above embodiment corresponding to FIG. 9 may be applied to a scenario where the terminal device is not covered by the satellite network for a long time. This is because: there is a limit to the cycle time of periodic TAU and periodic registration, which cannot be very large. Therefore, when the terminal device is not covered by the satellite network for a long time, it is inevitable to perform periodic TAU and periodic registration. At this time, the terminal device is not covered by the satellite network, which will cause the terminal device to continuously perform network connection operations such as cell scanning and cell selection, resulting in higher energy consumption loss.
  • a periodic TAU request or a periodic registration request will deregister or deattach the terminal device, so in order to avoid unnecessary periodic TAU or periodic registration when the idle terminal device is not covered by the satellite network, the above Figure 9 corresponds to
  • the terminal device when the terminal device is not covered by the satellite network, the terminal device will not perform periodic TAU or periodic registration and uplink data transmission, and the mobility management network element on the network side will not perform de-registration on the terminal device ( or detachment), so that the signaling interaction between the terminal device and the mobility management network element can be minimized, and the energy consumption of the terminal device can be reduced.
  • FIG. 10 it is a schematic flowchart of a communication method provided by an embodiment of the present application. This solution is a specific implementation of the above-mentioned embodiment corresponding to FIG. 5 .
  • the method includes the following steps:
  • Step 1001 is the same as step 601 above.
  • Step 1002 after the terminal equipment enters the idle state, the access network equipment sends an N2 message to the mobility management network element.
  • the mobility management network element receives the N2 message.
  • the N2 message may include the satellite where the terminal device is located Ephemeris information or satellite coverage information corresponding to the cell.
  • the N2 message also includes identification information of the satellite cell where the terminal device is located.
  • the satellite cell where the terminal device is located can also be understood as the last satellite cell visited by the terminal device before entering the idle state.
  • the N2 message may be an N2 release message, which corresponds to an S1 release message in a 4G network.
  • Step 1003 is the same as step 604 above.
  • This step 1003 is an optional step.
  • Step 1004 the mobility management network element judges whether the terminal equipment is reachable.
  • the mobility management network element judges whether the terminal device is reachable according to the satellite coverage information of the terminal device. If the terminal device is not currently covered by the satellite network, the terminal device is unreachable. If the terminal device is currently covered by the satellite network, it is determined whether the terminal device is reachable according to the existing scheme, such as according to the energy-saving sleep state of the terminal device.
  • the satellite coverage information of the terminal device is the satellite coverage information of the satellite cell where the terminal device is located.
  • the mobility management network element judges whether the terminal device is reachable according to the satellite coverage information of the terminal device and according to the eDRX cycle, periodic TAU cycle or periodic registration cycle. If the terminal device is not currently covered by the satellite network, or the terminal device is in the sleep time of the eDRX cycle, or the terminal device is in the sleep time of the periodic TAU cycle, or the terminal device is in the sleep time of the periodic registration cycle, the terminal device Unreachable. If the terminal device is currently covered by the satellite network, and the terminal device is not in the sleep time of the eDRX cycle, the terminal device is not in the sleep time of the periodic TAU cycle, and the terminal device is not in the sleep time of the periodic registration cycle, the terminal device reachable.
  • the dormancy time in the periodic TAU period or the periodic registration period refers to the dormancy time period in which the terminal equipment enters the dormancy period after a timer has elapsed after it enters the idle state from the connected state, such as the power saving mode (PowerSaving Mode) in a 4G network. , PSM), the uplink-only connection (Mobile Initiated Connection Only, MICO) mode in the 5G network.
  • PSM power saving mode
  • MICO Mobile Initiated Connection Only
  • Step 1005 if the terminal equipment is unreachable, the mobility management network element determines the maximum waiting time according to the satellite coverage information of the terminal equipment.
  • Step 1006 when the terminal equipment enters the reachable state, the mobility management network element sends a paging message to the access network equipment.
  • the access network device receives the paging message.
  • the paging message includes identification information of the terminal equipment and identification information of the paging cell.
  • the paging cell may be the cell last visited by the terminal device, or may be all cells in the tracking area where the cell last visited by the terminal device is located.
  • Step 1007 the access network device pages the terminal device.
  • the mobility management network element can judge the reachability according to the satellite coverage information of the terminal equipment.
  • the terminal device performs paging without sending downlink data to the terminal device, which can reduce the energy consumption of the mobility management network element and reduce data loss.
  • the MME may also receive a downlink data arrival notification from the user plane network element, and the downlink data arrival notification triggers the MME Execute step 1004. Moreover, after step 1005, the MME also determines the downlink data cache timeout period according to the maximum waiting time or downlink cache time, which is used to indicate whether the current core network side has cached data of the terminal device, and after the downlink data cache timeout period reaches , the MME will determine that there is no downlink buffer data of the terminal device at present.
  • the AMF network element can also receive a downlink data arrival notification from the SMF network element, and the downlink data arrival The notification triggers the AMF network element to perform step 1004 .
  • the AMF network element also instructs the SMF network element and/or the user plane network element to perform data caching according to the maximum waiting time, and then the SMF network element can determine the extended cache time according to the maximum waiting time, and the extended cache The time indicates the specific length of time for the user plane network element to cache the downlink data, and after the extended cache time is reached and the cached data has not been sent to the terminal device, the SMF network element will discard the corresponding cached data.
  • FIG. 11 it is a schematic flowchart of a communication method provided by an embodiment of the present application. This solution is a specific implementation of the above-mentioned embodiment corresponding to FIG. 5 .
  • the method includes the following steps:
  • Step 1101 the mobility management network element sends a paging message to the access network device.
  • the access network device receives the paging message.
  • the paging message includes identification information of the terminal equipment and identification information of the paging cell.
  • the paging cell may be the cell last visited by the terminal device, or may be all cells in the tracking area where the cell last visited by the terminal device is located.
  • Step 1102 the access network device determines that the satellite cell where the terminal device is located is not covered by the satellite network.
  • the access network device judges whether the terminal device has satellite network coverage according to the satellite coverage information of the terminal device. If the terminal device is not currently covered by the satellite network, the paging will fail this time. If the terminal device is currently covered by the satellite network, the terminal device is paged. Wherein, the satellite coverage information of the terminal device is the satellite coverage information of the satellite cell where the terminal device is located.
  • Step 1103 the access network device sends a first message to the mobility management network element.
  • the mobility management network element receives the first message.
  • the first message may be an N2 message or a paging failure message.
  • the access network equipment Since the access network equipment determines that the terminal equipment is not currently covered by satellites, it sends a first message to the mobility management network element, where the first message includes a paging failure indication and satellite coverage information of the terminal equipment, and the paging failure indication is used for It indicates that the cause of the paging failure is that the terminal device is not covered by the satellite network.
  • the paging failure indication also indicates that the mobility management network element needs to perform reachability judgment/paging according to the satellite coverage information.
  • the access network device since the access network device determines that the terminal device is not currently covered by satellites, it sends a first message to the mobility management network element, the first message includes satellite coverage information of the terminal device, and the satellite coverage information indicates The reason for the paging failure this time is that the terminal equipment is not covered by the satellite network.
  • the satellite coverage information also indicates that the mobility management network element needs to perform reachability judgment/paging according to the satellite coverage information.
  • Step 1104 the mobility management network element determines the maximum waiting time according to the satellite coverage information of the terminal equipment.
  • Step 1105 to step 1106 are the same as above step 1006 to step 1007.
  • the access network device judges whether the current terminal device can perform paging according to the satellite coverage information of the terminal device. If the terminal device is not within the satellite network coverage , the access network device notifies the mobility management network element of paging failure and sends the satellite coverage information of the terminal device to the mobility management network element, so that the mobility management network element determines the maximum waiting time according to the satellite coverage information to ensure that the terminal device does not When covered by the satellite network, the terminal equipment is not paging, which can reduce unnecessary signaling interaction between the mobility management network element and the access network equipment, and at the same time avoid the waste of paging resources of the access network equipment and the downlink data of the terminal equipment. lost.
  • the MME may also receive a downlink data arrival notification from the user plane network element, and the downlink data arrival notification triggers the MME Execute step 1101. Moreover, after step 1104, the MME also determines the downlink data cache timeout period according to the maximum waiting time, that is, the downlink cache time, which is used to indicate whether the current core network side has cached data of the terminal device, and after the downlink data cache timeout period reaches , the MME will determine that there is no downlink buffer data of the terminal device at present.
  • the AMF network element can also receive a downlink data arrival notification from the SMF network element, and the downlink data arrival The notification triggers the AMF network element to execute step 1101 .
  • the AMF network element also instructs the SMF network element and/or the user plane network element to perform data caching according to the maximum waiting time, and then the SMF network element can determine the extended cache time according to the maximum waiting time, and the extended cache The time indicates the specific length of time for the user plane network element to cache the downlink data, and after the extended cache time is reached and the cached data has not been sent to the terminal device, the SMF network element will discard the corresponding cached data.
  • the mobility management network element determines an appropriate periodic TAU period or periodic registration period, so that the terminal device The period is described as an example in which no uplink signaling or uplink data transmission is performed during the time period not covered by the satellite network. In practical applications, the mobility management network element can also determine other parameters (such as service interval (service gap), eDRX), so that the terminal device does not perform uplink communication during the time period not covered by the satellite network according to the other parameters. command or upstream data transmission.
  • service interval service gap
  • eDRX service gap
  • the terminal device does not perform uplink communication during the time period not covered by the satellite network according to the other parameters. command or upstream data transmission.
  • the "periodic TAU period” and “periodic registration period” appearing in the embodiment corresponding to FIG. 12 and the embodiment corresponding to FIG. 14 can be replaced with other parameters (such as service interval, eDRX).
  • the definition of service interval can refer to TS23.401 V17.2.0.
  • the "other parameter" may be a parameter indicating
  • the mobility management network element and the access network device may be MME and eNB respectively.
  • the mobility management network element and the access network device can be AMF and gNB respectively.
  • the terminal device in this embodiment is a satellite access type terminal device.
  • the method includes the following steps:
  • Step 1201 the mobility management network element determines a periodic TAU period or a periodic registration period according to the satellite coverage information of the terminal equipment.
  • the position or moving track of the terminal device is fixed.
  • the mobility management network element may determine the periodic TAU period or periodic registration period according to the satellite coverage information of the terminal device .
  • the mobility management network element is an MME, and the MME determines a periodic TAU period, wherein, in specific implementation, the periodic TAU period may be represented by a periodic TAU timer.
  • the mobility management network element is an AMF, and the AMF determines a periodic registration period, wherein, in a specific implementation, the periodic registration period may be represented by a periodic registration timer.
  • the time period corresponding to the periodic TAU period includes the time period when the terminal device is not covered by the satellite network, or the time period corresponding to the periodic registration period includes the time period when the terminal device is not covered by the satellite network, so as to ensure that when the terminal device When not covered by the satellite network, the terminal device will not perform the periodic TAU process or the periodic registration process, and the terminal device will continue to be in a dormant state, that is, from the time when the terminal device enters the idle state until the periodic TAU timer or periodic registration timing
  • the time period before the device times out includes the time period when the terminal device is not covered by the satellite network.
  • Method 1 The mobility management network element determines that the terminal device will not have satellite network coverage according to the satellite coverage information of the terminal device, and then sends an instruction message to the access network device, and the instruction information instructs the access network device to execute the terminal device connection release process , and then the access network device sends a UE context release request to the mobility management network element, the UE context release request is used to request the mobility management network element to release the context of the terminal device, and the mobility management network element receives the UE context release request Afterwards, the execution of the above step 1201 is triggered.
  • Method 2 The access network device determines that the terminal device will not have satellite network coverage according to the satellite coverage information of the terminal device, and then triggers the access network device to send a context release request to the mobility management network element.
  • the context release request is used to request mobility
  • the mobility management network element releases the context of the terminal equipment, and the mobility management network element triggers the execution of the above step 1201 after receiving the UE context release request.
  • Method 3 The terminal device determines that the terminal device will not have satellite network coverage according to the satellite coverage information of the terminal device, and then sends a TAU request or a mobile registration update request to the mobility management network element, and the mobility management network element receives the TAU request. Or after the mobile registration update request, the execution of the above step 1201 is triggered.
  • the mobility management network element also determines the first duration according to the satellite coverage information of the terminal device, and the first duration refers to the duration after the terminal device enters the idle state and before entering the dormant state.
  • the first duration may also be referred to as a duration (active time) during which the terminal device is in an active state.
  • the network can call the terminal equipment from the idle state to the connected state through paging.
  • Step 1202 the mobility management network element sends a periodic TAU period or a periodic registration period to the terminal equipment.
  • a mobility management network element such as MME sends a periodic TAU cycle to the terminal equipment.
  • the MME sends a GUTI reconfiguration command (GUTI Reallocation Command) to the terminal device, and the GUTI Reallocation Command carries a periodic TAU cycle.
  • the MME sends a TAU acceptance message to the terminal device, where the TAU acceptance message carries a periodic TAU period.
  • mobility management elements such as AMF send periodic registration periods to terminal devices.
  • the AMF sends a configuration update command (UE Configuration Update Command) to the terminal device, and the UE Configuration Update Command carries a periodic registration period.
  • the AMF sends a mobile registration update acceptance message to the terminal device, where the mobile registration update acceptance message carries a periodic registration period.
  • the mobility management network element sends a periodic TAU cycle or a periodic registration cycle to the terminal device through the access network device. That is, the mobility management network element sends the periodic TAU period or the periodic registration period to the access network device, and then the access network device sends the periodic TAU period or the periodic registration period to the terminal device.
  • the mobility management network element may also send the first duration to the terminal device, where the first duration refers to the duration after the terminal device enters the idle state and before entering the dormant state.
  • the first duration may also be referred to as a duration (active time) during which the terminal device is in an active state.
  • the network can call the terminal device from the idle state to the connected state through paging.
  • the mobility management network element may also send a cause value to the terminal device, where the cause value is discontinuous satellite coverage, or the cause value is used to instruct the terminal device not to perform uplink transmission during sleep.
  • Step 1203 the terminal device performs periodic TAU according to the periodic TAU period, or performs periodic registration according to the periodic registration period.
  • the start time of the periodic TAU period (that is, the periodic TAU timer) or the periodic registration period (that is, the periodic registration timer) may be the time when the terminal device enters the idle state.
  • the time period corresponding to the periodic TAU period or the time period corresponding to the periodic registration period includes a time period when the terminal device is not covered by the satellite network. The terminal device enters the dormant state during the period of time when it is not covered by the satellite network.
  • the start time of the periodic TAU period (that is, the periodic TAU timer) or the periodic registration period (that is, the periodic registration timer) may be the time when the terminal device enters the idle state.
  • the time period corresponding to the periodic TAU period or the time period corresponding to the periodic registration period includes a time period when the terminal device is not covered by the satellite network.
  • the time period corresponding to the periodic TAU period or the time period corresponding to the periodic registration period further includes a first duration, and the terminal device may be awakened by paging on the network side within the first duration, thereby entering a connected state.
  • the terminal device enters the dormant state during the period of time when it is not covered by the satellite network.
  • the terminal device when there is a demand for uplink transmission, the terminal device will register in the periodic TAU period or periodically according to the cause value. During the time period corresponding to the period, no uplink transmission is performed.
  • the mobility management network element determines the periodic TAU period or the periodic registration period according to the satellite coverage information of the terminal equipment, so that the time period corresponding to the periodic TAU period or the period corresponding to the periodic registration period can include During the time period covered by the satellite network, ensure that the terminal device can not perform the periodic TAU process or the periodic registration process during the time period not covered by the satellite network as much as possible, so as to avoid unnecessary network connection operations such as cell selection, so as to save Energy consumption of terminal equipment.
  • the mobility management network element and the access network device may be MME and eNB respectively.
  • the mobility management network element and the access network device can be AMF and gNB respectively.
  • the terminal device in this embodiment is a satellite access type terminal device.
  • the method includes the following steps:
  • Step 1401 the mobility management network element determines that the terminal device will not have satellite network coverage soon according to the satellite coverage information of the terminal device, and then sends instruction information to the access network device. Correspondingly, the access network device receives the indication information.
  • the position or moving track of the terminal device is fixed.
  • the mobility management network element may receive the satellite coverage information of the terminal device from the access network device, a third party or the terminal device.
  • the mobility management network element may receive the ephemeris information of the cell from the access network device, a third party or the terminal device, and then determine the satellite coverage information of the terminal device according to the ephemeris information of the cell.
  • the instruction information instructs the access network device to perform a terminal device release procedure.
  • the terminal device release process refers to the S1 release process.
  • the terminal device release process refers to the access network (access network, AN) release process.
  • This step 1401 is an optional step.
  • Step 1402 the access network device sends a UE context release request to the mobility management network element.
  • the mobility management network element receives the UE context release request.
  • the UE context release request is used to request the mobility management network element to release the UE context, so that the mobility management network element can release the connection with the terminal device, so that the terminal device enters an idle state.
  • the above instruction information triggers the access network device to execute this step 1402 .
  • the access network device may determine that the terminal device will not have satellite network coverage according to the satellite coverage information of the terminal device, and then trigger the access network device to perform step 1402 .
  • the access network device may trigger the access network device to perform step 1402 based on other reasons, where other reasons include but are not limited to: the terminal device is not executing Intervention (O&M Intervention) or Unspecified Failure (Unspecified Failure) of business and operator's operation and maintenance system.
  • reasons include but are not limited to: the terminal device is not executing Intervention (O&M Intervention) or Unspecified Failure (Unspecified Failure) of business and operator's operation and maintenance system.
  • the mobility management network element after receiving the UE context release request, the mobility management network element (ie, MME) may also request a serving gateway (serving gateway, S-GW) to release bearer resources.
  • a serving gateway serving gateway, S-GW
  • the mobility management network element after receiving the UE context release request, the mobility management network element (namely AMF) can also request the SMF to release the bearer resources.
  • Step 1403 the mobility management network element determines a periodic TAU period or a periodic registration period according to the satellite coverage information of the terminal equipment.
  • the mobility management network element may determine the periodic TAU period or periodic registration period according to the satellite coverage information of the terminal device .
  • the mobility management network element is an MME, and the MME determines a periodic TAU period, wherein, in specific implementation, the periodic TAU period may be represented by a periodic TAU timer.
  • the mobility management network element is the AMF, and the AMF determines the periodic registration period, wherein, in specific implementation, the periodic registration period can be represented by a periodic registration timer.
  • the time period corresponding to the periodic TAU period includes the time period when the terminal device is not covered by the satellite network, or the time period corresponding to the periodic registration period includes the time period when the terminal device is not covered by the satellite network, so as to ensure that when the terminal device When not covered by the satellite network, the terminal device will not perform the periodic TAU process or the periodic registration process, and the terminal device will continue to be in a dormant state, that is, from the time when the terminal device enters the idle state until the periodic TAU timer or periodic registration timing
  • the time period before the device times out includes the time period when the terminal device is not covered by the satellite network.
  • the mobility management network element further determines the first duration, where the first duration refers to the duration after the terminal device enters the idle state and before entering the dormant state.
  • the first duration may also be referred to as a duration (active time) during which the terminal device is in an active state.
  • the network can call the terminal device from the idle state to the connected state through paging.
  • Step 1404 the mobility management network element sends a reconfiguration command to the terminal device, and the reconfiguration command includes a periodic TAU period or a periodic registration period.
  • the terminal device receives the reconfiguration command.
  • the reconfiguration command also includes the duration of the terminal device being in an active state.
  • the reconfiguration command further includes a cause value, which is discontinuous satellite coverage, and optionally, the cause value also instructs the terminal device not to perform uplink transmission during sleep.
  • the uplink transmission here includes data transmission of uplink services and/or transmission of uplink signaling.
  • Step 1405 the terminal device sends a reconfiguration response to the mobility management network element.
  • the mobility management network element receives the reconfiguration response.
  • the reconfiguration command can be a GUTI Reallocation Command, which includes a periodic TAU cycle, and optionally also includes a first duration and/or a cause value.
  • the reconfiguration response may be a GUTI Reallocation Complete message.
  • the reconfiguration command can be a UE Configuration Update Command, which includes a periodic registration period, and optionally includes a first duration and/or a cause value.
  • the reconfiguration response may be a UE Configuration Update Complete message.
  • step 1404 and step 1405 are optional steps.
  • Step 1406 the mobility management network element sends a UE context release command to the access network device.
  • the access network device receives the UE context release command.
  • the UE context release command is used to instruct the access network device to release the UE context.
  • the UE context release command includes a periodic TAU period or a periodic registration period, and optionally also includes a first duration and/or a cause value.
  • Step 1407 the access network device sends an RRC connection release request to the terminal device.
  • the terminal device receives the RRC connection release request.
  • the RRC connection release request includes the periodic TAU period or periodic registration period. If the UE context release command further includes the first duration and/or cause value, the RRC connection release request further includes the first duration and/or cause value.
  • Step 1408 the access network device sends a UE context release complete message to the mobility management network element.
  • the mobility management network element receives the UE context release complete message.
  • This step 1408 is optional.
  • Step 1409 according to the cause value, the terminal device does not perform uplink transmission within the time period corresponding to the periodic TAU period or the periodic registration period.
  • the terminal device when there is a demand for uplink transmission, the terminal device does not perform uplink transmission within a time period corresponding to the periodic TAU period or the periodic registration period according to the cause value.
  • This step 1409 is an optional step.
  • step 1409 When the above step 1404 or step 1407 contains a cause value, then execute this step 1409 .
  • the update of the periodic TAU cycle or the periodic registration cycle is triggered, so as to ensure that after the terminal device enters the idle state, it is not covered by the satellite network. Dormancy in the segment, thereby reducing the power consumption of the terminal equipment.
  • the mobility management network element and the access network device may be MME and eNB respectively.
  • the mobility management network element and the access network device can be AMF and gNB respectively.
  • the method includes the following steps:
  • Step 1501 the terminal device determines that the terminal device will not have satellite network coverage according to the satellite coverage information of the terminal device, and then sends a TAU request or a Mobility Registration Update (Mobility Registration Update) request to the mobility management network element through the access network device.
  • the mobility management network element receives the TAU request or the mobile registration update request.
  • the position or moving track of the terminal device is fixed.
  • the terminal device may receive satellite coverage information of the terminal device from an access network device, a third party or a core network device.
  • the terminal device may receive the ephemeris information of the cell from the access network device, a third party or the core network device, and then determine the satellite coverage information of the terminal device according to the ephemeris information of the cell.
  • the access network equipment sends a TAU request to a mobility management network element (ie MME).
  • a mobility management network element ie MME
  • the access network equipment sends a mobile registration update request to the mobility management network element (ie AMF).
  • Step 1502 is the same as step 1403 above.
  • Step 1503 the mobility management network element sends a TAU acceptance message or a mobile registration update acceptance message to the terminal device through the access network device, the TAU acceptance message includes a periodic TAU period, or the mobile registration update acceptance message includes a periodic registration update acceptance message cycle.
  • the terminal device receives the TAU acceptance message or the mobile registration update acceptance message.
  • the access network device sends a TAU request to the mobility management network element (ie MME), and correspondingly, the MME sends a TAU acceptance message to the access network device.
  • the access network device sends a mobile registration update request to the mobility management network element (ie, AMF), and correspondingly, the AMF sends a mobile registration update acceptance message to the access network device.
  • the TAU acceptance message or the mobile registration update acceptance message also includes a first duration, and for the meaning of the first duration, refer to the description in step 1403 .
  • the TAU acceptance message or the mobile registration update acceptance message also includes a cause value, and for the meaning of the cause value, refer to the description in step 1403 .
  • Step 1504 the terminal device does not perform uplink transmission within the time period corresponding to the periodic TAU period or the periodic registration period.
  • the terminal device when there is a demand for uplink transmission, the terminal device does not perform uplink transmission within a time period corresponding to the periodic TAU period or the periodic registration period according to the cause value.
  • This step 1504 is an optional step. When the above step 1503 contains the reason value, then execute the step 1504 .
  • the terminal device before the terminal device is about to have no satellite network coverage, the terminal device triggers a periodic TAU process or a periodic registration process, so that the mobility management network element determines the periodic TAU period or periodic registration period according to the satellite coverage information of the terminal device , the time period corresponding to the periodic TAU period or the periodic registration period includes the time period when the terminal device is not covered by the satellite network, so as to ensure that the terminal device enters the idle state and sleeps in the time period not covered by the satellite network, thereby Reduce power consumption of end devices.
  • FIG. 16( a ) it is a schematic flowchart of a communication method provided by an embodiment of the present application. This solution is a specific implementation of the above-mentioned embodiment corresponding to FIG. 4 .
  • the method includes the following steps:
  • Step 1601a the terminal device acquires satellite coverage information of the terminal device.
  • the position or moving track of the terminal device is fixed.
  • a terminal device may receive satellite coverage information of the terminal device from an access network device, a third party, or a core network device (such as a mobility management network element).
  • the terminal device may receive ephemeris information from an access network device, a third party, or a core network device, and then determine satellite coverage information of the terminal device according to the ephemeris information.
  • the terminal device when the terminal device receives the satellite coverage information or ephemeris information of the terminal device from the access network device, it can be realized by the following method: the terminal device receives an RRC message from the access network device, and the RRC message includes the satellite information of the terminal device Overlay information or ephemeris information.
  • the RRC message may be an RRC reconfiguration or broadcast message.
  • the terminal device when the terminal device receives the satellite coverage information or ephemeris information of the terminal device from the mobility management network element, it can be realized by the following method: the terminal device receives the NAS message from the mobility management network element, and the NAS message includes the terminal device's Satellite coverage information or ephemeris information.
  • the NAS message further includes one or more of an eDRX cycle, a periodic TAU cycle or a periodic registration cycle.
  • the NAS message may be a Registration Accept message, an Attach Accept message or a TAU Accept message.
  • the satellite coverage information of the terminal device may also be ephemeris information.
  • Step 1602a the terminal device judges whether to initiate periodic TAU, periodic registration or transmit uplink data according to the satellite coverage information of the terminal device.
  • the terminal device judges whether the terminal device is covered by the satellite network according to the satellite coverage information of the terminal device, that is, whether the terminal device is covered by the satellite network at the current moment.
  • the terminal device initiates periodic TAU, registers periodically or transmits uplink data.
  • the terminal device does not initiate periodic TAU, register periodically or transmit uplink data.
  • the terminal device can also receive indication information from the access network device or the mobility management network element.
  • the indication information is used to instruct the terminal device to check the satellite network coverage by itself when there is an uplink transmission demand, and to check the satellite network coverage according to the satellite network coverage.
  • the uplink transmission requirements here include but are not limited to: periodic TAU, periodic registration, and uplink data transmission.
  • the step 1602a may be: the terminal device judges whether to initiate periodic TAU, periodic registration or transmit uplink data according to the satellite coverage information of the terminal device and the instruction information. Wherein, when the terminal device is covered by the satellite network, the terminal device initiates periodic TAU, registers periodically or transmits uplink data. When the terminal device is not covered by the satellite network, it does not initiate periodic TAU, register periodically or transmit uplink data.
  • the above-mentioned embodiment corresponding to FIG. 16( a ) may be applied to a scenario where the terminal device is not covered by the satellite network for a long time. This is because: there is a limit to the cycle time of periodic TAU or periodic registration, which cannot be very large. Therefore, when the terminal device is not covered by the satellite network for a long time, it is inevitable to perform periodic TAU or periodic registration.
  • FIG. 16( b ) it is a schematic flowchart of a communication method provided by an embodiment of the present application. This solution is a specific implementation of the above-mentioned embodiment corresponding to FIG. 4 .
  • the method includes the following steps:
  • Step 1601b the mobility management network element acquires satellite coverage information of the terminal equipment.
  • the mobility management network element may receive the satellite coverage information of the terminal device from the terminal device, the access network device or a third party, where the satellite coverage information of the terminal device may also be ephemeris information.
  • the mobility management network element may receive ephemeris information from the terminal device, the access network device or a third party, and then determine the satellite coverage information of the terminal device according to the ephemeris information.
  • Step 1602b the mobility management network element judges whether to perform de-registration (or de-attachment) of the terminal device according to the satellite coverage information of the terminal device.
  • the de-registration timer (or detach timer) corresponding to the terminal device times out, it is judged whether to perform de-registration (or detachment) of the terminal device according to the satellite coverage information of the terminal device.
  • the mobility management network element performs de-registration (or de-attachment) on the terminal equipment.
  • the mobility management network element does not perform de-registration (or de-attachment) on the terminal device.
  • not performing de-registration on the terminal device can also be understood as keeping the registration status of the terminal device unchanged.
  • Not performing detachment on the terminal device can also be understood as keeping the attachment state of the terminal device unchanged, that is, keeping the terminal device in the EMM registration state.
  • the response is that the terminal device is not covered by the satellite network.
  • the switching of the state of the terminal device between registration and de-registration, or switching between attachment and detachment is reduced, the signaling interaction between the terminal device and the network can be reduced, and the energy consumption of the terminal device can be reduced.
  • the above-mentioned embodiment corresponding to FIG. 16(a) may be implemented in combination with the embodiment corresponding to FIG. 16(b).
  • the mobility management network element, access network device or terminal device includes corresponding hardware structures and/or software modules for performing various functions.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software with reference to the units and method steps of the examples described in the embodiments disclosed in the present application. Whether a certain function is executed by hardware or computer software drives the hardware depends on the specific application scenario and design constraints of the technical solution.
  • FIG. 17 and FIG. 18 are schematic structural diagrams of possible communication devices provided by the embodiments of the present application. These communication devices can be used to implement the functions of the mobility management network element, access network device, or terminal device in the above method embodiments, and thus can also realize the beneficial effects of the above method embodiments.
  • the communication device may be a mobility management network element, access network device or terminal device, or a module (such as a chip) applied to a mobility management network element, access network device or terminal device. ).
  • a communication device 1700 includes a processing unit 1710 and a transceiver unit 1720 .
  • the communication device 1700 is used to implement the functions of the mobility management network element, access network device or terminal device in the above method embodiments.
  • the communication device is used to perform the operation of the mobility management network element
  • the processing unit 1710 is used to determine the sleep time information of the terminal device according to the satellite coverage information of the terminal device, the satellite coverage information Indicate the time period during which the terminal device is covered by the satellite network and/or the time period not covered by the satellite network, and the sleep time period corresponding to the sleep time information includes the time period during which the terminal device is not covered by the satellite network; the transceiver unit 1720 uses to send the sleep time information to the terminal device.
  • the processing unit 1710 is configured to determine one or more of the eDRX cycle, periodic TAU cycle, or periodic registration cycle of the terminal device according to the satellite coverage information; wherein, the sleep time The information includes dormancy start time, and the dormancy start time is within the eDRX cycle, the periodic TAU cycle or the periodic registration cycle.
  • the sleep time information includes a sleep start time and a sleep end time; or, the sleep time information includes a sleep start time and a sleep duration.
  • the processing unit 1710 is configured to receive the satellite coverage information through the transceiver unit 1720; or, receive the ephemeris information of the satellite cell where the terminal device is located through the transceiver unit 1720, and according to the ephemeris information Determine the satellite coverage information.
  • the processing unit 1710 is configured to determine that the terminal device has a fixed position or a fixed movement track.
  • the processing unit 1710 is configured to determine, according to the satellite coverage information, that the terminal device is not covered by the satellite network when the de-registration timer corresponding to the terminal device expires, and determine not to perform de-registration on the terminal device .
  • the communication device is used to perform the operation of the mobility management network element
  • the processing unit 1710 is used to determine the The terminal device is not covered by the satellite network
  • the satellite coverage information indicates the time period that the terminal device is covered by the satellite network and/or the time period that is not covered by the satellite network; and in response to the terminal device not being covered by the satellite network, it is determined that the The terminal device performs de-registration or de-attachment.
  • the transceiver unit 1720 is configured to send first information to the terminal device, where the first information indicates that the terminal device performs uplink transmission according to satellite network coverage when it has an uplink transmission requirement.
  • the first information is the satellite coverage information; the first information is specifically used to instruct the terminal device to initiate uplink transmission according to the satellite coverage information when there is an uplink transmission requirement.
  • the transceiver unit 1720 is configured to send the satellite coverage information to the terminal device; the first information is specifically used to instruct the terminal device to initiate uplink transmission according to the satellite coverage information when there is an uplink transmission requirement.
  • the uplink transmission requirement includes one or more of periodic TAU, periodic registration, or uplink data transmission.
  • the processing unit 1710 is configured to receive the satellite coverage information through the transceiver unit 1720; or, receive the ephemeris information of the satellite cell where the terminal device is located through the transceiver unit 1720, and according to the ephemeris information Determine the satellite coverage information.
  • the processing unit 1710 is configured to determine that the terminal device has a fixed position or a fixed movement track.
  • the communication device is used to perform the operation of the mobility management network element
  • the processing unit 1710 is used to determine the satellite coverage information of the terminal equipment, and the satellite coverage information indicates that the terminal equipment is covered by the satellite network A time period and/or a time period that is not covered by the satellite network; and according to the satellite coverage information, determine a maximum waiting time, where the maximum waiting time indicates the maximum time for waiting for the terminal device to be reachable.
  • the processing unit 1710 is configured to determine that the terminal device is unreachable according to the satellite coverage information.
  • the processing unit 1710 is configured to receive the satellite coverage information through the transceiver unit 1720 .
  • the processing unit 1710 is configured to receive the ephemeris information of the satellite cell where the terminal device is located through the transceiver unit 1720; and determine the satellite coverage information according to the ephemeris information.
  • the processing unit 1710 is configured to send a paging message to the access network device through the transceiver unit 1720, where the paging message includes identification information of the terminal device, and the paging message indicates that the terminal is paging device; receiving a first message from the access network device through the transceiver unit 1720, the first message includes a paging failure indication and satellite coverage information of the terminal device, and the paging failure indication is used to indicate that the cause of the paging failure is The terminal device is not covered by the satellite network.
  • the paging failure indication also indicates that the mobility management network element needs to perform reachability judgment/paging according to the satellite coverage information.
  • the processing unit 1710 is configured to determine that the terminal device has a fixed position or a fixed movement track.
  • the communication device is used to execute the operation of the terminal equipment
  • the transceiver unit 1720 is used to receive the first information
  • the first information indicates that the terminal equipment performs uplink transmission according to the coverage of the satellite network when there is an uplink transmission demand
  • the processing unit 1710 is configured to determine not to perform uplink transmission when it is determined that the terminal device is not covered by the satellite network according to the first information when there is a demand for uplink transmission.
  • the first information is satellite coverage information
  • the satellite coverage information indicates the time period during which the terminal device is covered by the satellite network and/or the time period during which the terminal device is not covered by the satellite network; the first information specifically It is used to instruct the terminal device to initiate uplink transmission according to the satellite coverage information when there is an uplink transmission requirement.
  • the processing unit 1710 is configured to receive satellite coverage information through the transceiver unit 1720, and the satellite coverage information indicates the time period during which the terminal device is covered by the satellite network and/or the time period during which it is not covered by the satellite network ;
  • the first information is specifically used to instruct the terminal device to initiate uplink transmission according to the satellite coverage information when there is an uplink transmission requirement.
  • the uplink transmission requirement includes one or more of periodic TAU, periodic registration, or uplink data transmission.
  • the communication device is used to execute the operation of the terminal equipment
  • the transceiver unit 1720 is used to receive sleep time information
  • the sleep time period corresponding to the sleep time information includes the time period when the terminal equipment is not covered by the satellite network
  • the sleep time information is determined according to the satellite coverage information of the terminal device
  • the satellite coverage information indicates the time period during which the terminal device is covered by the satellite network and/or the time period during which the terminal device is not covered by the satellite network
  • the processing unit 1710 is configured to Sleep is performed based on the sleep time information.
  • the sleep time information includes a sleep start time, and the sleep start time is located within the eDRX cycle of the terminal device, the periodic TAU cycle of the terminal device, or the periodic registration cycle of the terminal device.
  • the sleep time information includes a sleep start time and a sleep end time; or, the sleep time information includes a sleep start time and a sleep duration.
  • the communication device is used to execute the operation of the access network equipment, and the processing unit 1710 is used to obtain the satellite coverage information or ephemeris information of the satellite cell, and the satellite coverage information indicates that the satellite cell is covered by the satellite network The covered time period and/or the time period not covered by the satellite network; the transceiver unit 1720, configured to send the satellite coverage information or ephemeris information of the satellite cell to the mobility management network element.
  • the transceiver unit 1720 is configured to send the satellite coverage information or ephemeris information corresponding to the satellite cell of the access network device to the mobility management network element during the N2 interface establishment process.
  • the transceiving unit 1720 is configured to send the satellite coverage information or ephemeris information of the satellite cell where the terminal device is located to the mobility management network element during the registration process of the terminal device.
  • the transceiver unit 1720 is configured to receive a paging message from the mobility management network element, where the paging message includes identification information of the terminal device, and the paging message indicates to paging the terminal device;
  • the processing unit 1710 is configured to determine that the terminal device is unreachable according to the satellite coverage information of the satellite cell where the terminal device is located, and send a first message to the mobility management network element through the transceiver unit 1720, where the first message includes paging failure Indication and satellite coverage information of the terminal equipment.
  • the paging failure indication is used to indicate that the cause of the paging failure is that the terminal equipment is not covered by the satellite network. Coverage information for reachability judgment/paging.
  • the communication device is used to perform the operation of the mobility management network element
  • the processing unit 1710 is used to determine the periodic TAU period of the terminal device according to the satellite coverage information of the terminal device; the transceiver unit 1720, It is used to send the periodic TAU period to the terminal device; or, the processing unit 1710 is used to determine the periodic registration period of the terminal device according to the satellite coverage information of the terminal device; the transceiver unit 1720 is used to send the periodic TAU period to the terminal device.
  • Periodic registration period wherein, the satellite coverage information indicates the time period during which the terminal device is covered by the satellite network and/or the time period during which the terminal device is not covered by the satellite network.
  • the time period corresponding to the periodic TAU period includes the time period when the terminal device is not covered by the satellite network; or, the time period corresponding to the periodic registration period includes the time period when the terminal device is not covered by the satellite network. The time period covered.
  • the processing unit 1710 is further configured to send instruction information to the access network device through the transceiver unit 1720 according to the satellite coverage information, and the instruction information instructs the access network device to execute the terminal device release process .
  • the processing unit 1710 is configured to determine a first duration according to the satellite coverage information of the terminal device, where the first duration is the duration after the terminal device enters the idle state and before entering the sleep state;
  • the transceiver unit 1720 is configured to send the first duration to the terminal device.
  • the transceiver unit 1720 is further configured to send a cause value to the terminal device, where the cause value is discontinuous satellite coverage.
  • the cause value is also used to indicate that the terminal device does not perform uplink transmission during sleep.
  • the transceiver unit 1720 is configured to send a GUTI reallocation command to the terminal device, where the GUTI reallocation command includes the periodic TAU cycle; or, send a TAU acceptance message to the terminal device, where the TAU The acceptance message includes the periodic TAU period.
  • the transceiver unit 1720 is configured to send a configuration update command to the terminal device, where the configuration update command includes the periodic registration period; or, send a mobile registration update acceptance message to the terminal device, the mobile The Registration Update Accept message includes the periodic registration period.
  • the communication device is used to execute the operation of the terminal equipment
  • the transceiver unit 1720 is used to receive the periodic TAU cycle from the mobility management network element
  • the processing unit 1710 is used to receive the periodic TAU cycle according to the periodic TAU cycle Executing periodic TAU, the time period corresponding to the periodic TAU period includes the time period when the terminal device is not covered by the satellite network; or, the transceiver unit 1720 is used to receive the periodic registration period from the mobility management network element; the processing unit 1710.
  • Perform periodic registration according to the periodic registration period where the time period corresponding to the periodic registration period includes a time period when the terminal device is not covered by the satellite network.
  • the periodic TAU period or the periodic registration period is determined according to the satellite coverage information of the terminal device, and the satellite coverage information indicates the time period during which the terminal device is covered by the satellite network and/or The period of time not covered by the satellite network.
  • the processing unit 1710 is configured to, before the transceiver unit 1720 receives the periodical TAU cycle from the mobility management network element, send the mobile network information to the mobile terminal through the transceiver unit 1720 according to the satellite coverage information of the terminal device.
  • the management network element sends a TAU request; or, before the transceiver unit 1720 receives the periodic registration period from the mobility management network element, according to the satellite coverage information of the terminal device, the transceiver unit 1720 sends a mobile registration to the mobility management network element.
  • An update request wherein, the satellite coverage information indicates the time period during which the terminal device is covered by the satellite network and/or the time period during which the terminal device is not covered by the satellite network.
  • the transceiver unit 1720 is further configured to receive a first duration from the mobility management network element, where the first duration is the duration after the terminal device enters the idle state and before entering the sleep state, and the first duration is The first duration is determined according to the satellite coverage information of the terminal device.
  • the transceiver unit 1720 is configured to receive a cause value from the mobility management network element, where the cause value is discontinuous satellite coverage.
  • the cause value is also used to indicate that the terminal device does not perform uplink transmission during sleep; when there is a demand for uplink transmission, it is determined not to perform uplink transmission according to the cause value.
  • the communication device is used to execute the operation of the access network equipment, and the processing unit 1710 is used to send a context release request to the mobility management network element through the transceiver unit 1720 according to the satellite coverage information of the terminal equipment,
  • the context release request is used to request the mobility management network element to release the context of the terminal device, and the satellite coverage information indicates the time period when the terminal device is covered by the satellite network and/or the time when it is not covered by the satellite network segment;
  • the transceiver unit 1720 is further configured to receive the periodic TAU cycle from the mobility management network element, and send the periodic TAU cycle to the terminal device, and the time segment corresponding to the periodic TAU cycle includes the The time period during which the terminal device is not covered by the satellite network; or, the transceiver unit 1720 is further configured to receive a periodic registration period from the mobility management network element, and send the periodic registration period to the terminal device, The time period corresponding to the periodic registration period includes a time period when the terminal device is not covered by the satellite network.
  • processing unit 1710 and the transceiver unit 1720 can be directly obtained by referring to related descriptions in the above method embodiments, and details are not repeated here.
  • the communication device 1800 includes a processor 1810 , and optionally, the communication device 1800 may further include an interface circuit 1820 .
  • the processor 1810 and the interface circuit 1820 are coupled to each other. It can be understood that the interface circuit 1820 may be a transceiver or an input-output interface.
  • the communication device 1800 may further include a memory 1830 for storing instructions executed by the processor 1810 or storing input data required by the processor 1810 to execute the instructions or storing data generated after the processor 1810 executes the instructions.
  • the processor 1810 is used to realize the functions of the above-mentioned processing unit 1710
  • the interface circuit 1820 is used to realize the functions of the above-mentioned transceiver unit 1720 .
  • processor in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor can be a microprocessor, or any conventional processor.
  • the method steps in the embodiments of the present application may be implemented by means of hardware, or may be implemented by means of a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, and software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only Memory, registers, hard disk, removable hard disk, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be a component of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the ASIC can be located in the base station or the terminal.
  • the processor and the storage medium may also exist in the base station or the terminal as discrete components.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product comprises one or more computer programs or instructions. When the computer program or instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are executed in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, a base station, user equipment or other programmable devices.
  • the computer program or instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instructions may be downloaded from a website, computer, A server or data center transmits to another website site, computer, server or data center by wired or wireless means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrating one or more available media.
  • the available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; and it may also be a semiconductor medium, such as a solid state disk.
  • the computer readable storage medium may be a volatile or a nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.
  • “at least one” means one or more, and “multiple” means two or more.
  • “And/or” describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the contextual objects are an “or” relationship; in the formulas of this application, the character “/” indicates that the contextual objects are a "division” Relationship.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • General Physics & Mathematics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种通信方法、通信装置及通信系统。该方法包括：根据终端设备的卫星覆盖信息，确定该终端设备的休眠时间信息，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段，该休眠时间信息对应的休眠时间段包括该终端设备未被卫星网络覆盖的时间段；向该终端设备发送该休眠时间信息。该方案，根据终端设备的卫星覆盖信息确定休眠时间信息，该休眠时间信息对应的休眠时间段包括该终端设备未被卫星网络覆盖的时间段，从而确保终端设备能够尽可能地在未被卫星网络覆盖的时间段内进行休眠，避免不必要的小区选择等网络连接操作，以节省终端设备的能耗。

Description

一种通信方法、通信装置及通信系统
相关申请的交叉引用
本申请要求在2021年10月10日提交中国专利局、申请号为202111178674.7、申请名称为“一种通信方法、通信装置及通信系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中；本申请要求在2021年11月05日提交中国专利局、申请号为202111308873.5、申请名称为“一种通信方法、通信装置及通信系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法、通信装置及通信系统。
背景技术
目前，在一些通信场景，如大规模机器类型通信(massive machine type communications，mMTC)应用场景，为了保障终端设备的网络覆盖效果，引入了卫星通信。卫星通信能够在一定程度上增强网络覆盖。
然而，由于卫星是处于运动状态的，因此有可能在某个时间段，终端设备不能被卫星网络覆盖。
发明内容
本申请实施例提供一种通信方法、通信装置及通信系统，用于实现基于卫星通信的场景中，减少终端设备或核心网设备(如移动性管理网元)的能耗。
第一方面，本申请实施例提供一种通信方法，该方法可以由移动性管理网元或应用于移动性管理网元中的模块(如芯片)来执行。该方法包括：根据终端设备的卫星覆盖信息，确定该终端设备的休眠时间信息，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段，该休眠时间信息对应的休眠时间段包括该终端设备未被卫星网络覆盖的时间段；向该终端设备发送该休眠时间信息。
上述方案，移动性管理网元根据终端设备的卫星覆盖信息，确定休眠时间信息，该休眠时间信息对应的休眠时间段包括该终端设备未被卫星网络覆盖的时间段，从而确保终端设备能够尽可能地在未被卫星网络覆盖的时间段内进行休眠，避免不必要的小区选择等网络连接操作，以节省终端设备的能耗。
在一种可能的实现方法中，根据该卫星覆盖信息，确定该终端设备的eDRX周期、周期性TAU周期或周期性注册周期中的一个或多个；其中，该休眠时间信息包括休眠开始时间，该休眠开始时间位于该eDRX周期、该周期性TAU的周期内。
在一种可能的实现方法中，该休眠时间信息包括休眠开始时间和休眠结束时间；或者，该休眠时间信息包括休眠开始时间和休眠时长。
上述方案，在该休眠时间信息对应的休眠时间段内，终端设备将会持续进行休眠，不 会进行业务，包括不会执行周期性TAU、不会执行周期性注册以及不会执行上行数据传输，可以减少终端设备的能耗。
在一种可能的实现方法中，接收该卫星覆盖信息；或者，接收该终端设备所在的卫星小区的星历信息，并根据该星历信息确定该卫星覆盖信息。
在一种可能的实现方法中，确定该终端设备的位置固定或移动轨迹固定。
在一种可能的实现方法中，当该终端设备对应的去注册定时器超时，根据该卫星覆盖信息确定该终端设备未被卫星网络覆盖，确定不对该终端设备执行去注册。
根据该方案，当终端设备未被卫星网络覆盖，移动性管理网元不对该终端设备去注册，可以减少终端设备的状态在注册和去注册之间来回切换，从而减少终端设备的能耗，降低与网络间的频繁信令交互。
第二方面，本申请实施例提供一种通信方法，该方法可以由移动性管理网元或应用于移动性管理网元中的模块(如芯片)来执行。该方法包括：当终端设备对应的去注册定时器超时，根据该终端设备的卫星覆盖信息，确定该终端设备未被卫星网络覆盖，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；响应于该终端设备未被卫星网络覆盖，确定不对该终端设备执行去注册。
根据该方案，当终端设备未被卫星网络覆盖，移动性管理网元不对该终端设备去注册，可以减少终端设备的状态在注册和去注册之间来回切换，从而减少终端设备的能耗。在一种可能的实现方法中，向该终端设备发送第一信息，该第一信息指示该终端设备有上行传输需求时根据卫星网络覆盖情况进行上行传输。
在一种可能的实现方法中，该第一信息是该卫星覆盖信息；该第一信息具体用于指示该终端设备有上行传输需求时根据该卫星覆盖信息发起上行传输。
在一种可能的实现方法中，向该终端设备发送该卫星覆盖信息；该第一信息具体用于指示该终端设备有上行传输需求时根据该卫星覆盖信息发起上行传输。
在一种可能的实现方法中，该上行传输需求包括周期性TAU、周期性注册或上行数据传输中的一个或多个。
在一种可能的实现方法中，接收该卫星覆盖信息；或者，接收该终端设备所在的卫星小区的星历信息，并根据该星历信息确定该卫星覆盖信息。
在一种可能的实现方法中，确定该终端设备的位置固定或移动轨迹固定。
第三方面，本申请实施例提供一种通信方法，该方法可以由移动性管理网元或应用于移动性管理网元中的模块(如芯片)来执行。该方法包括：确定终端设备的卫星覆盖信息，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；根据该卫星覆盖信息，确定最大等待时间，该最大等待时间指示等待该终端设备可达的最大时长。
根据上述方案，移动性管理网元可以根据终端设备的卫星覆盖信息进行可达性判断，如果终端设备不可达，则根据卫星覆盖信息确定最大等待时间，确保终端设备未被卫星网络覆盖时，不对终端设备进行寻呼，可以降低移动性管理网元与接入网设备之间不必要的信令交互，同时避免接入网设备寻呼资源浪费以及终端设备的下行数据丢失。
在一种可能的实现方法中，根据该卫星覆盖信息，确定该终端设备不可达。
在一种可能的实现方法中，接收该卫星覆盖信息。
在一种可能的实现方法中，接收该终端设备所在的卫星小区的星历信息；根据该星历 信息，确定该卫星覆盖信息。
在一种可能的实现方法中，向接入网设备发送寻呼消息，该寻呼消息包括该终端设备的标识信息，该寻呼消息指示寻呼该终端设备；接收来自该接入网设备的第一消息，该第一消息包括寻呼失败指示和该卫星覆盖信息，该寻呼失败指示用于指示寻呼失败原因为未被卫星网络覆盖。可选的，该寻呼失败指示还指示需移动管理网元根据该卫星覆盖信息进行可达性判断/寻呼。
在一种可能的实现方法中，向接入网设备发送寻呼消息，该寻呼消息包括该终端设备的标识信息，该寻呼消息指示寻呼该终端设备；接收来自该接入网设备的第一消息，该第一消息包括该终端设备的卫星覆盖信息，该卫星覆盖信息指示寻呼失败原因为未被卫星网络覆盖，可选的，该卫星覆盖信息还指示需移动管理网元根据该卫星覆盖信息进行可达性判断/寻呼。
在一种可能的实现方法中，确定该终端设备的位置固定或移动轨迹固定。
第四方面，本申请实施例提供一种通信方法，该方法可以由终端设备或应用于终端设备中的模块(如芯片)来执行。该方法包括：接收第一信息，该第一信息指示终端设备有上行传输需求时根据卫星网络覆盖情况进行上行传输；当有上行传输需求，根据该第一信息，确定该终端设备未被卫星网络覆盖，则确定不进行上行传输。
根据上述方案，当终端设备未被卫星网络覆盖，即使有上行传输需求，也不执行上行传输，可以避免不必要的小区扫描、小区选择等网络连接操作，以节省终端设备的能耗。
在一种可能的实现方法中，该第一信息是卫星覆盖信息，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；该第一信息具体用于指示该终端设备有上行传输需求时根据该卫星覆盖信息发起上行传输。
在一种可能的实现方法中，接收卫星覆盖信息，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；该第一信息具体用于指示该终端设备有上行传输需求时根据该卫星覆盖信息发起上行传输。
在一种可能的实现方法中，该上行传输需求包括周期性TAU、周期性注册或上行数据传输中的一个或多个。
第五方面，本申请实施例提供一种通信方法，该方法可以由终端设备或应用于终端设备中的模块(如芯片)来执行。该方法包括：接收休眠时间信息，该休眠时间信息对应的休眠时间段包括终端设备未被卫星网络覆盖的时间段，该休眠时间信息是根据该终端设备的卫星覆盖信息确定的，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；根据该休眠时间信息，进行休眠。
上述方案，终端设备能够尽可能地在未被卫星网络覆盖的时间段内进行休眠，避免不必要的小区扫描、小区选择等网络连接操作，以节省终端设备的能耗。
在一种可能的实现方法中，该休眠时间信息包括休眠开始时间，该休眠开始时间位于该终端设备的eDRX周期内、该终端设备的周期性TAU周期内或该终端设备的周期性注册周期内。
在一种可能的实现方法中，该休眠时间信息包括休眠开始时间和休眠结束时间；或者，该休眠时间信息包括休眠开始时间和休眠时长。
第六方面，本申请实施例提供一种通信方法，该方法可以由接入网设备或应用于接入网设备中的模块(如芯片)来执行。该方法包括：获取卫星小区的卫星覆盖信息或星历信 息，该卫星覆盖信息指示该卫星小区被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；向移动性管理网元发送该卫星小区的卫星覆盖信息或星历信息。
在一种可能的实现方法中，在N2接口建立流程中，向该移动性管理网元发送接入网设备的卫星小区对应的卫星覆盖信息或星历信息。
在一种可能的实现方法中，在该终端设备的注册流程中，向该移动性管理网元发送终端设备所在的卫星小区的卫星覆盖信息或星历信息。
在一种可能的实现方法中，接收来自该移动性管理网元的寻呼消息，该寻呼消息包括终端设备的标识信息，该寻呼消息指示寻呼该终端设备；根据该终端设备所在的卫星小区的卫星覆盖信息，确定该卫星小区无网络覆盖，向该移动性管理网元发送第一消息，该第一消息包括寻呼失败指示和该终端设备所在的卫星小区的该卫星覆盖信息，该寻呼失败指示用于指示寻呼失败原因为未被卫星网络覆盖，可选的，寻呼失败指示还指示需移动管理网元根据该卫星覆盖信息进行可达性判断/寻呼。
在一种可能的实现方法中，接收来自该移动性管理网元的寻呼消息，该寻呼消息包括终端设备的标识信息，该寻呼消息指示寻呼该终端设备；根据该终端设备所在的卫星小区的卫星覆盖信息，确定该卫星小区无网络覆盖，向该移动性管理网元发送第一消息，该第一消息包括该终端设备所在的卫星小区的该卫星覆盖信息，该终端设备所在的卫星小区的卫星覆盖信息即为该终端设备的卫星覆盖信息，且该卫星覆盖信息用于指示此次寻呼失败的原因为未被卫星网络覆盖，可选的，该卫星覆盖信息还指示需移动管理网元根据该卫星覆盖信息进行可达性判断/寻呼。
第七方面，本申请实施例提供一种通信方法，该方法可以由移动性管理网元或应用于移动性管理网元中的模块(如芯片)来执行。该方法包括：根据终端设备的卫星覆盖信息确定该终端设备的周期性TAU周期，并向该终端设备发送该周期性TAU周期；或者，根据终端设备的卫星覆盖信息确定该终端设备的周期性注册周期，并向该终端设备发送该周期性注册周期；其中，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段。
上述方案，移动性管理网元根据终端设备的卫星覆盖信息，确定周期性TAU周期或周期性注册周期，可以使得该周期性TAU周期对应的时间段或周期性注册周期对应的时间段包含终端设备未被卫星网络覆盖的时间段，确保终端设备能够尽可能地在未被卫星网络覆盖的时间段内不执行周期性TAU流程或周期性注册流程，避免不必要的小区选择等网络连接操作，以节省终端设备的能耗。
在一种可能的实现方法中，该周期性TAU周期对应的时间段包含该终端设备未被卫星网络覆盖的时间段；或者，该周期性注册周期对应的时间段包含该终端设备未被卫星网络覆盖的时间段。
在一种可能的实现方法中，根据该卫星覆盖信息，向接入网设备发送指示信息，该指示信息指示该接入网设备执行该终端设备释放流程。
在一种可能的实现方法中，根据该终端设备的卫星覆盖信息，确定第一时长，该第一时长为所述终端设备进入空闲态后、进入休眠态之前的时长；向该终端设备发送第一时长。
在一种可能的实现方法中，向该终端设备发送原因值，该原因值为卫星非连续覆盖。
在一种可能的实现方法中，该原因值还用于指示该终端设备在休眠期间不进行上行传输。
在一种可能的实现方法中，向该终端设备发送GUTI重分配命令，该GUTI重分配命令包括该周期性TAU周期；或者，向该终端设备发送TAU接受消息，该TAU接受消息包括该周期性TAU周期。
在一种可能的实现方法中，向该终端设备发送配置更新命令，该配置更新命令包括该周期性注册周期；或者，向该终端设备发送移动注册更新接受消息，该移动注册更新接受消息包括该周期性注册周期。
第八方面，本申请实施例提供一种通信方法，该方法可以由终端设备或应用于终端设备中的模块(如芯片)来执行。该方法包括：接收来自移动性管理网元的周期性TAU周期，并根据该周期性TAU周期执行周期性TAU，该周期性TAU周期对应的时间段包含该终端设备未被卫星网络覆盖的时间段；或者，接收来自移动性管理网元的周期性注册周期，并根据该周期性注册周期执行周期性注册，该周期性注册周期对应的时间段包含该终端设备未被卫星网络覆盖的时间段。
上述方案，终端设备收到的周期性TAU周期对应的时间段或周期性注册周期对应的时间段包含终端设备未被卫星网络覆盖的时间段，确保终端设备能够尽可能地在未被卫星网络覆盖的时间段内不执行周期性TAU流程或周期性注册流程，避免不必要的小区选择等网络连接操作，以节省终端设备的能耗。
在一种可能的实现方法中，该周期性TAU周期或该周期性注册周期是根据该终端设备的卫星覆盖信息确定的，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段。
在一种可能的实现方法中，接收来自移动性管理网元的周期性TAU周期之前，根据该终端设备的卫星覆盖信息，向该移动性管理网元发送TAU请求；或者，接收来自移动性管理网元的周期性注册周期之前，根据该终端设备的卫星覆盖信息，向该移动性管理网元发送移动注册更新请求；其中，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段。
在一种可能的实现方法中，接收来自该移动性管理网元的第一时长，该第一时长为该终端设备进入空闲态后、进入休眠态之前的时长，第一时长是根据终端设备的卫星覆盖信息确定的。
在一种可能的实现方法中，接收来自该移动性管理网元的原因值，该原因值为卫星非连续覆盖。
在一种可能的实现方法中，该原因值用于指示该终端设备在休眠期间不进行上行传输；当有上行传输需求，根据该原因值，确定不进行上行传输。
第九方面，本申请实施例提供一种通信方法，该方法可以由接入网设备或应用于接入网设备中的模块(如芯片)来执行。该方法包括：根据终端设备的卫星覆盖信息，向移动性管理网元发送上下文释放请求，所述上下文释放请求用于请求所述移动性管理网元释放所述终端设备的上下文，所述卫星覆盖信息指示所述终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；接收来自所述移动性管理网元的周期性TAU周期，并向所述终端设备发送所述周期性TAU周期，所述周期性TAU周期对应的时间段包含所述终端设备未被卫星网络覆盖的时间段；或者，接收来自所述移动性管理网元的周期性注册周期，并向所述终端设备发送所述周期性注册周期，所述周期性注册周期对应的时间段包含所述终端设备未被卫星网络覆盖的时间段。
第十方面，本申请实施例提供一种通信装置，该装置可以是移动性管理网元或应用于移动性管理网元中的模块(如芯片)。该装置具有实现上述第一方面至第三方面、第七方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十一方面，本申请实施例提供一种通信装置，该装置可以是终端设备或应用于终端设备中的模块(如芯片)。该装置具有实现上述第四方面、第五方面或第八方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十二方面，本申请实施例提供一种通信装置，该装置可以是接入网设备或应用于接入网设备中的模块(如芯片)。该装置具有实现上述第六方面或第九方面的任意实现方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第十三方面，本申请实施例提供一种通信装置，包括处理器和存储器；该存储器用于存储计算机指令，当该装置运行时，该处理器执行该存储器存储的计算机指令，以使该装置执行上述第一方面至第九方面中的任意实现方法。
第十四方面，本申请实施例提供一种通信装置，包括用于执行上述第一方面至第九方面中的任意实现方法的各个步骤的单元或手段(means)。
第十五方面，本申请实施例提供一种通信装置，包括处理器和接口电路，所述处理器用于通过接口电路与其它装置通信，并执行上述第一方面至第九方面中的任意实现方法。该处理器包括一个或多个。
第十六方面，本申请实施例提供一种通信装置，包括与存储器耦合的处理器，该处理器用于调用所述存储器中存储的程序，以执行上述第一方面至第九方面中的任意实现方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器可以是一个或多个。
第十七方面，本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在通信装置上运行时，使得上述第一方面至第九方面中的任意实现方法被执行。
第十八方面，本申请实施例还提供一种计算机程序产品，该计算机程序产品包括计算机程序或指令，当计算机程序或指令被通信装置运行时，使得上述第一方面至第九方面中的任意实现方法被执行。
第十九方面，本申请实施例还提供一种芯片系统，包括：处理器，用于执行上述第一方面至第六方面中的任意实现方法。
第二十方面，本申请实施例还提供一种通信系统，包括：移动性管理网元和接入网设备。该移动性管理网元用于执行第一方面至第三方面的任意实现方法。该接入网设备用于向移动性管理网元发送终端设备所在小区的卫星覆盖信息。
第二十一方面，本申请实施例还提供一种通信系统，包括：移动性管理网元和接入网设备。该移动性管理网元用于执行第七方面的任意实现方法。该接入网设备用于执行第九方面的任意实现方法。
附图说明
图1(a)为基于服务化架构的5G网络架构示意图；
图1(b)为基于点对点接口的5G网络架构示意图；
图2为本申请实施例提供的一种通信方法的流程示意图；
图3(a)为本申请实施例提供的周期性TAU周期示意图；
图3(b)为本申请实施例提供的eDRX周期示意图；
图3(c)为本申请实施例提供的休眠时间段示意图；
图4为本申请实施例提供的一种通信方法的流程示意图；
图5为本申请实施例提供的一种通信方法的流程示意图；
图6为本申请实施例提供的一种通信方法的流程示意图；
图7为本申请实施例提供的一种通信方法的流程示意图；
图8为本申请实施例提供的一种通信方法的流程示意图；
图9为本申请实施例提供的一种通信方法的流程示意图；
图10为本申请实施例提供的一种通信方法的流程示意图；
图11为本申请实施例提供的一种通信方法的流程示意图；
图12为本申请实施例提供的一种通信方法的流程示意图；
图13(a)为本申请实施例提供的周期性TAU周期或周期性注册周期示意图；
图13(b)为本申请实施例提供的周期性TAU周期或周期性注册周期的另一示意图；
图14为本申请实施例提供的一种通信方法的流程示意图；
图15为本申请实施例提供的一种通信方法的流程示意图；
图16(a)为本申请实施例提供的一种通信方法的流程示意图；
图16(b)为本申请实施例提供的一种通信方法的流程示意图；
图17为本申请实施例提供的一种通信装置示意图；
图18为本申请实施例提供的一种通信装置示意图。
具体实施方式
为了应对无线宽带技术的挑战，保持第三代合作伙伴计划(3rd generation partnership project，3GPP)网络的领先优势，3GPP标准组制定了下一代移动通信网络系统(next generation system)架构，称为第五代(the 5th generation，5G)网络架构。该架构不但支持3GPP标准组定义的无线接入技术(如长期演进(long term evolution，LTE)接入技术，5G无线接入网(radio access network，RAN)接入技术等)接入到5G核心网(core network，CN)，而且支持使用非3GPP(non-3GPP)接入技术通过非3GPP转换功能(non-3GPP interworking function，N3IWF)或下一代接入网关(next generation packet data gateway，ngPDG)接入到核心网。
图1(a)为基于服务化架构的5G网络架构示意图。图1(a)所示的5G网络架构中可包括终端设备、接入网设备以及核心网设备。终端设备通过接入网设备和核心网设备接入数据网络(data network，DN)。其中，核心网设备包括但不限于以下网元中的部分或者全部：鉴权服务器功能(authentication server function，AUSF)网元(图中未示出)、统一数据管理(unified data management，UDM)网元、统一数据库(unified data repository，UDR) 网元、网络存储功能(network repository function，NRF)网元(图中未示出)、网络开放功能(network exposure function，NEF)网元(图中未示出)、应用功能(application function，AF)网元、策略控制功能(policy control function，PCF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、用户面功能(user plane function，UPF)网元、绑定支持功能(binding support funciton，BSF)网元(图中未示出)、网络数据分析功能(network data analysis function，NWDAF)网元(图中未示出)。
终端设备可以是用户设备(user equipment，UE)、移动台、移动终端等。终端设备可以广泛应用于各种场景，例如，设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端设备可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、车辆、城市空中交通工具(如无人驾驶机、直升机等)、轮船、机器人、机械臂、智能家居设备等。
接入网设备可以是无线接入网(RAN)设备或有线接入网(wirelineaccess network，FAN)设备。其中，无线接入网设备包括3GPP接入网设备、非可信非3GPP接入网设备和可信非3GPP接入网设备。3GPP接入网设备包括但不限于：LTE中的演进型基站(evolved NodeB，eNodeB)、5G移动通信系统中的下一代基站(next generation NodeB，gNB)、未来移动通信系统中的基站或完成基站部分功能的模块或单元，如集中式单元(central unit，CU)，分布式单元(distributed unit，DU)等。非可信非3GPP接入网设备包括但不限于：非可信非3GPP接入网关或N3IWF设备、非可信无线局域网(wireless local area network，WLAN)接入点(access point，AP)、交换机、路由器。可信非3GPP接入网设备包括但不限于：可信非3GPP接入网关、可信WLAN AP、交换机、路由器。有线接入网设备包括但不限于：有线接入网关(wireline access gateway)、固定电话网络设备、交换机、路由器。
接入网设备和终端设备可以是固定位置的，也可以是可移动的。接入网设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和人造卫星上。
AMF网元，包含执行移动性管理、接入鉴权/授权等功能。此外，还负责在终端设备与PCF网元间传递用户策略。
SMF网元，包含执行会话管理、执行PCF网元下发的控制策略、选择UPF网元、分配终端设备的互联网协议(internet protocol，IP)地址等功能。
UPF网元，包含完成用户面数据转发、基于会话/流级的计费统计、带宽限制等功能。
UDM网元，包含执行管理签约数据、用户接入授权等功能。
UDR网元，包含执行签约数据、策略数据、应用数据等类型数据的存取功能。
NEF网元，用于支持能力和事件的开放。
AF网元，传递应用侧对网络侧的需求，例如，QoS需求或用户状态事件订阅等。AF网元可以是第三方功能实体，也可以是运营商部署的应用服务，如IP多媒体子系统(IP Multimedia Subsystem，IMS)语音呼叫业务。
PCF网元，包含负责针对会话、业务流级别进行计费、QoS带宽保障及移动性管理、终端策略决策等策略控制功能。PCF网元包括接入与移动性管理策略控制网元(access and  mobility management policy control function，AM PCF)网元和会话管理策略控制功能(session management PCF，SM PCF)网元，AM PCF网元可以提供移动性管理策略，SM PCF网元可以提供会话管理策略。
NRF网元，可用于提供网元发现功能，基于其他网元的请求，提供网元类型对应的网元信息。NRF网元还提供网元管理服务，如网元注册、更新、去注册以及网元状态订阅和推送等。
BSF网元，可提供BSF服务注册/注销/更新，与NRF网元连接检测，会话绑定信息创建，终端设备信息的获取，IP地址重复的会话绑定信息查询等功能。
AUSF网元，负责对用户进行鉴权，以确定是否允许用户或设备接入网络。
NWDAF网元，主要用于收集数据(包括终端设备数据、接入网设备数据、核心网网元数据以及第三方应用数据中的一种或者多种)，并根据机器学习模型提供数据分析服务，可以输出数据分析结果，供网络、网管及应用执行策略决策使用。NWDAF网元可以是一个单独的网元，也可以与其他网元合设，例如将NWDAF网元设置到PCF网元或者AMF网元中。
DN，是位于运营商网络之外的网络，运营商网络可以接入多个DN，DN上可部署多种业务，可为终端提供数据和/或语音等服务。例如，DN是某智能工厂的私有网络，智能工厂安装在车间的传感器可为终端，DN中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，DN是某公司的内部办公网络，该公司员工的手机或者电脑可为终端，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
图1(a)中Npcf、Nufr、Nudm、Naf、Namf、Nsmf分别为上述PCF、UDR、UDM、AF、AMF和SMF提供的服务化接口，用于调用相应的服务化操作。N1、N2、N3、N4以及N6为接口序列号，这些接口序列号的含义如下：
1)、N1：AMF与终端设备之间的接口，可以用于向终端设备传递非接入层(non access stratum，NAS)信令(如包括来自AMF的QoS规则)等。
2)、N2：AMF与接入网设备之间的接口，可以用于传递核心网侧至接入网设备的无线承载控制信息等。
3)、N3：接入网设备与UPF之间的接口，主要用于传递接入网设备与UPF间的上下行用户面数据。
4)、N4：SMF与UPF之间的接口，可以用于控制面与用户面之间传递信息，包括控制面向用户面的转发规则、QoS规则、流量统计规则等的下发以及用户面的信息上报。
5)、N6：UPF与DN的接口，用于传递UPF与DN之间的上下行用户数据流。
图1(b)为基于点对点接口的5G网络架构示意图，其中的网元的功能的介绍可以参考图1(a)中对应的网元的功能的介绍，不再赘述。图1(b)与图1(a)的主要区别在于：图1(a)中的各个控制面网元之间的接口是服务化的接口，图1(b)中的各个控制面网元之间的接口是点对点的接口。
在图1(b)所示的架构中，各个网元之间的接口名称及功能如下：
1)、N1、N2、N3、N4和N6接口的含义可以参考前述描述。
2)、N5：AF与PCF之间的接口，可以用于应用业务请求下发以及网络事件上报。
3)、N7：PCF与SMF之间的接口，可以用于下发协议数据单元(protocol data unit，PDU)会话粒度以及业务数据流粒度控制策略。
4)、N8：AMF与UDM间的接口，可以用于AMF向UDM获取接入与移动性管理相关签约数据与鉴权数据，以及AMF向UDM注册终端设备移动性管理相关信息等。
5)、N9：UPF和UPF之间的用户面接口，用于传递UPF间的上下行用户数据流。
6)、N10：SMF与UDM间的接口，可以用于SMF向UDM获取会话管理相关签约数据，以及SMF向UDM注册终端设备会话相关信息等。
7)、N11：SMF与AMF之间的接口，可以用于传递接入网设备和UPF之间的PDU会话隧道信息、传递发送给终端设备的控制消息、传递发送给接入网设备的无线资源控制信息等。
8)、N15：PCF与AMF之间的接口，可以用于下发终端策略及接入控制相关策略。
9)、N35：UDM与UDR间的接口，可以用于UDM从UDR中获取用户签约数据信息。
10)、N36：PCF与UDR间的接口，可以用于PCF从UDR中获取策略相关签约数据以及应用数据相关信息。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
本申请实施例中，移动性管理网元可以是第四代(4th generation，4G)网络中的移动性管理实体(mobility management entity，MME)，5G网络中的AMF网元，或未来通信系统中具有MME或AMF网元的功能的其它网元。
本申请实施例中，接入网设备可以是4G网络中的接入网设备(如eNB等)，5G网络中的接入网设备(如gNB等)，或未来通信系统中具有4G网络的接入网设备或5G网络的接入网设备的功能的其它网元。
本申请实施例中，策略控制网元可以是4G网络中的策略与计费规则功能(policy and charging rules function，PCRF)网元，5G网络中的PCF网元，或未来通信系统中具有PCRF网元或PCF网元的功能的其它网元。
本申请实施例中，存储网元可以是4G网络中的归属签约用户服务器(home subscriber server，HSS)，5G网络中的UDR网元，或未来通信系统中具有HSS或UDR网元的功能的其它网元。
本申请实施例中，周期性跟踪区更新(tracking area update，TAU)和周期性注册在本申请实施例中的含义一致。周期性TAU是4G中的称呼，周期性注册是5G中的称呼。
本申请实施例中，周期性TAU周期可以用周期性TAU定时器(timer)来表示，周期性注册周期可以用周期性注册定时器(timer)来表示。其中，周期性TAU定时器是4G中的称呼，周期性注册定时器是5G中的称呼。
本申请实施例中，去附着流程和去注册流程在本申请实施例中的含义一致。去附着流程是4G中的称呼，去注册流程是5G中的称呼。
本申请实施例中，最大等待时间可以是4G网络中的下行缓存时长，也可以是5G网络中的最大等待时间，或未来通信系统中具有下行缓存时长或最大等待时间的其他参数。
mMTC是5G网络的重要应用场景之一，主要面向基于蜂窝网络的各类物联网(internet  of things，IoT)业务应用，诸如海上/陆地/铁路/航空运输，油气开采测量，环境监测以及矿井开发等等。为满足上述需求，在4G时代，3GPP定义了窄带物联网(narrowband internet of things，NB-IoT)以及增强型机器类通信(enhanced machine type communication，eMTC)(也称为长期演进机器类型通信(LTE-machine type communication，LTE-M))。
然而，为了保障更为广泛的网络覆盖，进一步实现全球的无死角覆盖，出现了低轨卫星。低轨卫星能够辅助NB-IoT/eMTC实现物联网的全球覆盖，从而能够避免地面网络设施部署不足带来的网络覆盖问题。
以5G为例，对于NB-IoT/eMTC场景下的终端设备，当其进入空闲态后，将有可能进入休眠状态，此时终端设备与核心网侧的AMF会保持一个粗同步，确保AMF能够感知终端设备何时进入休眠态。当有终端设备的下行数据到达时，UPF会通知到SMF，然后SMF会通知到AMF，如果此时AMF发现终端设备还处于休眠状态不可达，将会根据终端设备的休眠时间估计一个最大等待时间并将该最大等待时间返回给SMF，以指示SMF根据该最大等待时间进行等待后再执行下行寻呼，并且SMF基于该最大等待时间确定最大缓存时间，并根据该最大缓存时间对终端设备的下行数据进行缓存，并等待终端设备可达。
其中，终端设备的节能方式主要有两种，分别为节能模式(power saving model，PSM)和扩展非连续性接收(extended discontinuous reception，eDRX)。PSM是指终端设备在进入空闲态后一段时间就会进入休眠状态，直至有上行业务或周期性注册/周期性TAU。eDRX是指终端设备在没有业务传输时，会在固定时间点进入休眠状态，并在指定的时间内醒来监听网络侧的寻呼信息，此时终端设备处于可达状态，能够接收来自网络侧的寻呼消息。其中，本文所讨论的eDRX如无特殊指明是指的空闲态eDRX。
3GPP将NB-IoT与eMTC引入到卫星网络架构，从而使能卫星支持4G的NB-IoT与eMTC。其中5G卫星架构早在R16 5G就已经在研究，旨在实现5G架构与卫星的融合。
与地面覆盖不同的是，由于卫星需要围绕地球进行规律性运动，因而卫星的覆盖一直处于移动状态。R17 5G卫星架构研究中，定义继续沿用原有地面覆盖固定小区的概念，即卫星覆盖的小区虽然是在移动，但是地面的接入网设备会根据卫星的覆盖与地面固定小区之间的对应关系，将卫星覆盖的小区映射为地面固定小区，从而确保核心网侧感知到的终端设备所在小区仍然是地面固定小区。
另外，在卫星部署之初或者为了部署成本考虑，对于某一特定地面区域可能会存在不连续覆盖的场景。比如，地处沙漠深处的油田开采现场，一颗或多颗卫星在围绕地球进行规律性转动的同时，可能只能在特定的时间段内为该油田开采现场提供网络通信服务，如进行油田开采各类传感器的数据采集与上报。也就是说，卫星对地面的终端设备提供的网络通信服务是非连续覆盖的，终端设备在一些时间段会被卫星网络覆盖，在另一段时间内未被卫星网络覆盖。
由于非连续覆盖特性的存在，将会导致以下问题：
问题1，终端设备可能会持续较长时间未被卫星网络覆盖，而传统NB-IoT或eMTC场景下的eDRX的休眠时间较短，无法适用于该场景。也即，按照传统NB-IoT或eMTC场景下的eDRX的休眠方式，终端设备在休眠结束后醒来，仍然可能处于未被卫星网络覆盖场景。
问题2，当网络侧有下行数据到达时，核心网无法确定终端设备是否处于可达状态，难以确保寻呼成功。
本申请的实施例中，终端设备的卫星覆盖信息指示终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段。示例性的，终端设备的卫星覆盖信息指示了该终端设备每天上午8点至9点未被卫星网络覆盖，和/或指示了该终端设备每天凌晨0点至上午8点，以及上午9点至凌晨0点被卫星网络覆盖。终端设备的卫星覆盖信息可以是该终端设备所在位置对应的卫星覆盖信息，或者是该终端设备所在的卫星小区的卫星覆盖信息，或者是该终端设备所在的跟踪区域(Tracking Area，TA)对应的卫星覆盖信息。比如，终端设备位于小区1，则该终端设备的卫星覆盖信息可以是小区1的卫星覆盖信息。再比如，终端设备位于小区2，则该终端设备的卫星覆盖信息可以是小区2的卫星覆盖信息。或者，本申请实施例中的终端设备的卫星覆盖信息也可以是星历信息。
本申请的实施例中，小区的星历信息是指该小区对应的卫星围绕地球转动的规律性，比如星历信息包括卫星轨道平面参数、卫星参数，如卫星移动速度、卫星移动方向、卫星轨道距离地面距离、参考时间点等等，根据卫星小区对应的一个或多个卫星的星历信息可以获知小区被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段。小区的卫星覆盖信息指示小区被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段。例如，接入网设备下有三个卫星小区，分别为卫星小区1、卫星小区2、卫星小区3，则该N2建立消息包括卫星小区1的标识信息、卫星小区1对应的星历信息1或卫星覆盖信息1、卫星小区2的标识信息、卫星小区2对应的星历信息2或卫星覆盖信息2、卫星小区3的标识信息，以及卫星小区3对应的星历信息3或卫星覆盖信息3。
参考图2，为本申请实施例提供的一种通信方法的流程示意图。该方法可用于解决上述问题1。该方法包括以下步骤：
步骤201，移动性管理网元根据终端设备的卫星覆盖信息，确定终端设备的休眠时间信息。
作为一种实现方法，在接入网设备上电之后，接入网设备需要与移动性管理网元之间建立连接，以5G网络为例，该接口为N2接口，因此接入网设备向移动性管理网元发送N2建立消息，该N2建立消息可以携带该接入网设备下的卫星小区的标识信息以及每个卫星小区对应的卫星的星历信息或卫星覆盖信息。后续，当终端设备注册至网络时，移动性管理网元可以获取该终端设备所在的卫星小区信息，比如终端设备位于接入网设备下的卫星小区1，则移动性管理网元确定小区1的卫星覆盖信息为该终端设备的卫星覆盖信息。其中，如果移动性管理网元从接入网设备收到的是小区1对应的卫星的星历信息，则移动性管理网元还需要先根据小区1对应的卫星的星历信息确定小区1的卫星覆盖信息，可选地，移动性管理网元还可以保存该卫星覆盖信息作为从小区1接入网络的终端设备的卫星覆盖信息。
作为另一种实现方法，也可以是在终端设备注册至网络的过程中，由接入网设备将该终端设备所在的卫星小区对应的卫星的星历信息或卫星覆盖信息发送给移动性管理网元。比如，终端设备向接入网设备发送注册请求消息。接入网设备收到注册请求消息之后，向移动性管理网元发送注册请求消息的同时，还发送该终端设备所在的卫星小区对应的卫星的星历信息或卫星覆盖信息，即在初始N2消息中添加该终端设备所在的卫星小区对应的卫星的星历信息或卫星覆盖信息。如果接入网设备发送的是该终端设备所在的卫星小区对应的卫星的星历信息，则移动性管理网元需要根据该星历信息确定该终端设备所在的卫星小区的卫星覆盖信息。然后，移动性管理网元将该小区的卫星覆盖信息作为该终端设备的 卫星覆盖信息。
作为另一种实现方法，也可以是由第三方网元，如核心网之外的应用服务器或核心网内的专用于与卫星交互的网元或专用于卫星管理的网元，向移动性管理网元发送该终端设备所在的卫星小区对应的卫星的星历信息或卫星覆盖信息。如果第三方网元发送的是该终端设备所在的卫星小区对应的卫星的星历信息，则移动性管理网元需要根据该星历信息确定该终端设备所在的卫星小区的卫星覆盖信息。然后，移动性管理网元将该小区的卫星覆盖信息作为该终端设备的卫星覆盖信息。
其中，休眠时间信息对应的休眠时间段包括终端设备未被卫星网络覆盖的时间段。
作为一种实现方法，移动性管理网元还根据卫星覆盖信息确定该终端设备的eDRX周期、周期性TAU周期或周期性注册周期中的一个或多个，该休眠时间信息对应的休眠时间段被包含在该eDRX周期、周期性TAU周期或周期性注册周期的休眠时间范围内。该实现方法下，这里的休眠时间信息包括休眠开始时间，该休眠开始时间位于eDRX周期、周期性TAU的周期或周期性注册周期内。参考图3(a)，为某个周期性TAU的周期示意图。在一个周期性TAU周期的开始时刻，终端设备执行周期性TAU流程，发起网络连接，随后终端设备从休眠开始时间开始进入休眠状态，并且终端设备在该周期性TAU周期内的休眠时间段包括终端设备未被卫星网络覆盖的时间段，从而可以保障终端设备在未被卫星网络覆盖的时间段进入休眠状态，避免终端设备在无网络覆盖时间段内进行周期性TAU流程，可以减少终端设备的能耗。其中，休眠时长大于或等于该终端设备未被卫星网络覆盖的时长。参考图3(a)，T1时刻为休眠开始时间，T2时刻为休眠结束时间，T2也是该TAU周期的结束时间。T2与T1的差值等于该终端设备未被卫星网络覆盖的时长。其中，该步骤201确定的休眠时间信息即为该图3(a)的示例中的休眠开始时间。其中，在4G网络中一般称该流程为周期性TAU流程，而在5G网络中该流程被称为周期性注册流程。参考图3(b)，为某个eDRX周期示意图。在一个eDRX周期的开始之后的一个寻呼时间窗内，终端设备根据DRX周期执行监听，并在寻呼时间窗到达之后若无网络连接需求，会在休眠开始时间开始进入休眠状态，并且终端设备在该eDRX周期内的休眠时间段包括终端设备未被卫星网络覆盖的时间段，从而可以保障终端设备在未被卫星网络覆盖的时间段进入休眠状态，可以避免终端设备在无卫星网络覆盖的时间段内醒来监听寻呼消息，减少终端设备的能耗。其中，休眠时长大于或等于该终端设备未被卫星网络覆盖的时长。参考图3(b)，T1时刻为休眠开始时间，T2时刻为休眠结束时间，T2也是该eDRX周期的结束时间。T2与T1的差值等于或大于该终端设备未被卫星网络覆盖的时长。其中，该步骤201确定的休眠时间信息包括该图3(b)的示例中的休眠开始时间。
作为另一种实现方法，该休眠时间信息包括休眠开始时间和休眠结束时间，且该休眠开始时间与休眠结束时间之间的休眠时间段即包含该终端设备未被卫星网络覆盖的时间段。或者，该休眠时间信息包括休眠开始时间和休眠时长，且根据休眠开始时间和休眠时长可以得到休眠结束时间。其中，在该休眠时间信息对应的休眠时间段内，终端设备将会持续进行休眠，不会进行业务，包括不会执行周期性TAU流程或周期性注册流程。该方法中，终端设备的卫星覆盖信息所指示的未被卫星网络覆盖的时间段，未被包含在任何eDRX周期或TAU周期内，而是一个单独的休眠时间段。参考图3(c)，为休眠时间段示意图。休眠时间信息指示了一个单独的休眠时间段，该休眠时间段与终端设备未被卫星网络覆盖的时间段重合或该休眠时间段大于终端设备未被卫星网络覆盖的时间段，在该休眠时 间段内终端设备进入休眠状态，可以保障终端设备在未被卫星网络覆盖的时间段进入休眠状态，可以避免不必要、无效的网络连接，减少终端设备的能耗。参考图3(c)，T1时刻为休眠开始时间，T2时刻为休眠结束时间，T1到T2的时间段与该终端设备未被卫星网络覆盖的时间段重合或大于该终端设备未被卫星网络覆盖的时间段。可选的，在该休眠时间段之后，进入eDRX周期，该eDRX周期可以根据现有方案确定，该eDRX周期内也有休眠时间段，该休眠时间段可以称为常规eDRX休眠时间段。其中，该步骤201确定的休眠时间信息包括该图3(c)的示例中的休眠开始时间和休眠结束时间。或者，该步骤201确定的休眠时间信息包括该图3(c)的示例中的休眠开始时间和休眠时长。
步骤202，移动性管理网元向终端设备发送休眠时间信息。相应的，终端设备接收该休眠时间信息。
作为一种实现方法，移动性管理网元可以在发送给终端设备的注册接受消息中携带该休眠时间信息，可选的，该注册接受消息还包括eDRX周期、周期性注册的周期或周期性TAU的周期中的一个或多个。以4G网络为例，可以在发送给终端设备的附着接受消息中或TAU接受消息中携带该休眠时间信息。
步骤203，终端设备根据休眠时间信息，进行休眠。
具体的，终端设备在休眠时间信息对应的休眠时间段内进入休眠状态，该休眠时间段包括该终端设备未被卫星网络覆盖的时间段。
步骤204，当终端设备对应的去注册定时器(或去附着定时器)超时，移动性管理网元根据卫星覆盖信息确定终端设备未被卫星网络覆盖，确定不对终端设备执行去注册(或去附着)。
该步骤204为可选步骤。
其中，不对终端设备执行去注册，也可以理解为是保持终端设备的注册状态不变。不对终端设备执行去附着，也可以理解为是保持终端设备的附着状态不变。
其中，在4G网络中，当终端设备对应的去附着定时器(或隐式去附着定时器)超时，如果移动性管理网元，即MME，根据卫星覆盖信息确定终端设备未被卫星网络覆盖，确定不对终端设备执行去附着，即保持该终端设备当前的移动性管理状态为附着或EMM注册状态(EPSMobility Management-Registered,EMM-Registered)；如果移动性管理网元根据卫星覆盖信息确定终端设备被卫星网络覆盖，确定对终端设备执行去附着，即将该终端设备当前的移动性管理状态变为去附着或EMM去注册状态。根据该方案，当终端设备未被卫星网络覆盖，移动性管理网元不对该终端设备执行去附着流程，可以减少终端设备的状态在附着和去附着之间，或在注册和非注册之间来回切换，从而减少终端设备与网络间的信令交互，降低终端设备的能耗。这是因为：当终端设备未被卫星网络覆盖，此时终端设备的能耗是比较低的，如果移动性管理网元对该终端设备去附着，后续当终端设备被卫星网络覆盖之后，该终端设备又要重新附着，反而造成更多的信令交互，导致该终端设备的能耗增加。
在5G网络中，当终端设备对应的去注册定时器(或隐式去附着定时器)超时，如果移动性管理网元，即AMF，根据卫星覆盖信息确定终端设备未被卫星网络覆盖，确定不对终端设备执行去注册。如果移动性管理网元根据卫星覆盖信息确定终端设备被卫星网络覆盖，确定不对终端设备执行注册，即保持当前终端设备维持在注册状态。根据该方案，当终端设备未被卫星网络覆盖，移动性管理网元不对该终端设备去注册，可以减少终端设备 的状态在注册和去注册之间来回切换，从而减少终端设备与网络间的信令交互，降低终端设备的能耗。这是因为：当终端设备未被卫星网络覆盖，此时终端设备的能耗是比较低的，如果移动性管理网元对该终端设备去注册，后续当终端设备被卫星网络覆盖之后，该终端设备又要重新注册，反而造成更多的信令交互，导致该终端设备的能耗增加。
上述方案，移动性管理网元根据终端设备的卫星覆盖信息，确定休眠时间信息，该休眠时间信息对应的休眠时间段包括该终端设备未被卫星网络覆盖的时间段，从而确保终端设备能够尽可能地在未被卫星网络覆盖的时间段内进行休眠，避免不必要的小区扫描、小区选择等网络连接操作，以节省终端设备的能耗。
参考图4，为本申请实施例提供的一种通信方法的流程示意图。该方法可用于解决上述问题1。该方法包括以下步骤：
步骤401，当终端设备对应的去注册定时器(或去附着定时器)超时，移动性管理网元根据终端设备的卫星覆盖信息，确定终端设备未被卫星网络覆盖。
其中，移动性管理网元确定终端设备的卫星覆盖信息的实现方法，可以参考前述步骤201的描述，不再赘述。
其中，去注册定时器也可以为隐式去注册定时器，本文中对此不做限定。去附着定时器也可以为隐式去附着定时器，本文中对此不做限定。
步骤402，移动性管理网元确定不对终端设备执行去注册(或去附着)。
其中，不对终端设备执行去注册，也可以理解为是保持终端设备的注册状态不变。不对终端设备执行去附着，也可以理解为是保持终端设备的附着状态不变，即保持终端设备一直处于EMM注册状态。可选的，不对终端设备执行去注册时响应于终端设备未被卫星网络覆盖。
其中，在4G网络中，当终端设备对应的去附着定时器超时，如果移动性管理网元，即MME，根据卫星覆盖信息确定终端设备未被卫星网络覆盖，确定不对终端设备执行去附着，即保持该终端设备当前的移动性管理状态为附着或EMM注册状态；如果移动性管理网元根据卫星覆盖信息确定终端设备被卫星网络覆盖，确定对终端设备执行去附着，即将该终端设备当前的移动性管理状态变为去附着或EMM去注册状态。根据该方案，当终端设备未被卫星网络覆盖，移动性管理网元不对该终端设备执行去附着流程，可以减少终端设备的状态在附着和去附着之间来回切换，从而减少终端设备与网络间的信令交互，降低终端设备的能耗。这是因为：当终端设备未被卫星网络覆盖，此时终端设备的能耗是比较低的，如果移动性管理网元对该终端设备去附着，后续当终端设备被卫星网络覆盖之后，该终端设备又要重新附着，反而造成更多的信令交互，导致该终端设备的能耗增加。
在5G网络中，当终端设备对应的去注册定时器超时，如果移动性管理网元，即AMF，根据卫星覆盖信息确定终端设备未被卫星网络覆盖，确定不对终端设备执行去注册。如果移动性管理网元根据卫星覆盖信息确定终端设备被卫星网络覆盖，确定不对终端设备执行注册，即保持当前终端设备维持在注册状态。根据该方案，当终端设备未被卫星网络覆盖，移动性管理网元不对该终端设备去注册，可以减少终端设备的状态在注册和去注册之间来回切换，从而减少终端设备与网络间的信令交互，降低终端设备的能耗。这是因为：当终端设备未被卫星网络覆盖，此时终端设备的能耗是比较低的，如果移动性管理网元对该终端设备去注册，后续当终端设备被卫星网络覆盖之后，该终端设备又要重新注册，反而造成更多的信令交互，导致该终端设备的能耗增加。
根据上述方案，由于减少了终端设备的状态在注册和去注册之间来回切换，或者附着和去附着之间来回切换，可以减少终端设备与网络间的信令交互，降低终端设备的能耗。
作为一种实现方法，在上述步骤402之后，还可以执行以下步骤403和步骤404。
步骤403，移动性管理网元向终端设备发送第一信息。相应的，终端设备接收该第一信息。
该第一信息指示终端设备有上行传输需求时根据卫星网络覆盖情况进行上行传输。
步骤404，当有上行传输需求，终端设备根据第一信息，确定终端设备未被卫星网络覆盖，则确定不进行上行传输。
这里的上行传输需求包括但不限于：周期性TAU、周期性注册、上行数据传输。
作为一种实现方法，该第一信息是上述步骤401中所描述的终端设备的卫星覆盖信息。移动性管理网元向终端设备发送该终端设备的卫星覆盖信息，用于指示终端设备有上行传输需求时根据该卫星覆盖信息进行上行传输。因此，当终端设备有上行传输需求时，根据该卫星覆盖信息，判断终端设备当前是否有卫星网络覆盖。如果未被卫星网络覆盖，则确定不进行上行传输。如果被卫星网络覆盖，则确定进行上行传输。
作为另一种实现方法，该第一信息是一个指示信息，该指示信息具体指示：终端设备有上行传输需求时自行检查卫星网络覆盖情况，并根据卫星网络覆盖情况进行上行传输。因此，当终端设备有上行传输需求时，终端设备先自行检查当前是否被卫星网络覆盖。如果未被卫星网络覆盖，则确定不进行上行传输。如果被卫星网络覆盖，则确定进行上行传输。
作为另一种实现方法，在上述步骤403中，移动性管理网元向终端设备发送第一信息的同时，还向终端设备发送终端设备的卫星覆盖信息，该情况下，这里的第一信息是一个指示信息，该指示信息具体指示：终端设备有上行传输需求时根据该卫星覆盖信息进行上行传输。因此，当终端设备有上行传输需求时，终端设备根据该卫星覆盖信息判断是否被卫星网络覆盖。如果未被卫星网络覆盖，则确定不进行上行传输。如果被卫星网络覆盖，则确定进行上行传输。
根据上述步骤403和步骤404的方案，当终端设备未被卫星网络覆盖，即使有上行传输需求，也不执行上行传输，可以避免不必要且无效的小区扫描、小区选择等网络连接操作，以节省终端设备的能耗。
参考图5，为本申请实施例提供的一种通信方法的流程示意图。该方法可用于解决上述问题2。该方法包括以下步骤：
步骤501，移动性管理网元确定终端设备的卫星覆盖信息。
作为一种实现方法，移动性管理网元可以按照前述步骤201所描述的方法，确定终端设备的卫星覆盖信息。
作为另一种实现方法，移动性管理网元也可以通过以下方法确定终端设备的卫星覆盖信息：移动性管理网元向接入网设备发送寻呼消息，该寻呼消息包括空闲态终端设备的标识信息，该寻呼消息指示寻呼终端设备。然后接入网设备寻呼终端设备，如果接入网设备确定该终端设备所在小区当前未被卫星网络覆盖，则接入网设备将会寻呼失败，因此接入网设备向移动性管理网元发送第一消息，该第一消息包括寻呼失败指示和该终端设备所在的卫星小区的卫星覆盖信息，该寻呼失败指示用于指示此次寻呼失败的原因为未被卫星网络覆盖，可选的，寻呼失败指示还指示需移动管理网元根据该卫星覆盖信息进行可达性判 断/寻呼。其中，该终端设备所在的卫星小区的卫星覆盖信息即为该终端设备的卫星覆盖信息。
作为另一种实现方法，移动性管理网元也可以通过以下方法确定终端设备的卫星覆盖信息：移动性管理网元向接入网设备发送寻呼消息，该寻呼消息包括空闲态终端设备的标识信息，该寻呼消息指示寻呼终端设备。然后接入网设备寻呼终端设备，如果接入网设备确定该终端设备所在小区当前未被卫星网络覆盖，则接入网设备将会寻呼失败，因此接入网设备向移动性管理网元发送第一消息，该第一消息包括该终端设备所在的卫星小区的卫星覆盖信息，该终端设备所在的卫星小区的卫星覆盖信息即为该终端设备的卫星覆盖信息，且该卫星覆盖信息用于指示此次寻呼失败的原因为未被卫星网络覆盖，可选的，该卫星覆盖信息还指示需移动管理网元根据该卫星覆盖信息进行可达性判断/寻呼。
作为一种实现方法，当该移动性管理网元是5G的AMF网元，则AMF网元可以在收到来自SMF网元的下行数据到达通知后，执行该步骤501，也即下行数据到达通知触发移动性管理网元执行该步骤501。
作为一种实现方法，当该移动性管理网元是4G的MME，则MME可以在确定用户面有下行数据需要传输后，执行该步骤501。
步骤502，移动性管理网元根据卫星覆盖信息，确定最大等待时间，该最大等待时间指示等待终端设备可达的最大时长。
其中，这里的最大等待时间需要覆盖该终端设备未被卫星网络覆盖的时间段，或者理解为，在最大等待时间到达后，终端设备应该是被卫星网络覆盖的。该最大等待时间可以是4G中的下行缓存时长或5G中的最大等待时长。
可选的，移动性管理网元在步骤502之前，还根据卫星覆盖信息，确定该终端设备不可达。
在4G网络中，该移动性管理网元是MME，该MME确定最大等待时间之后，可以根据该最大等待时间，确定下行数据缓存超时时长，用于指示当前核心网侧是否缓存有该终端设备的数据，并在下行数据缓存超时时长到达后，MME会认定当前已经没有该终端设备的下行缓存数据。其中，在4G网络中，最大等待时间也可以被称为下行数据缓存时间。
在5G网络中，该移动性管理网元是AMF网元，该AMF网元确定最大等待时间之后，可以将最大等待时间发送给SMF网元，然后SMF网元可以根据该最大等待时间，确定扩展缓存时间，该扩展缓存时间指示用户面网元缓存下行数据的具体时长，并在扩展缓存时间到达后且该缓存数据仍未发送给终端设备，SMF将会丢弃对应缓存的数据。其中，在5G网络中，最大等待时间也可以被称为估计最大等待时间。
根据上述方案，移动性管理网元可以根据终端设备的卫星覆盖信息进行可达性判断，如果终端设备不可达，则根据卫星覆盖信息确定最大等待时间，确保终端设备未被卫星网络覆盖时，不对终端设备进行寻呼，也不向终端设备发送下行数据，可以减少移动性管理网元的能耗以及减少数据丢失。
作为一种实现方法，在上述步骤201之前，步骤401之前，和/或步骤501之前，移动性管理网元还确定该终端设备的位置固定或移动轨迹固定。或者理解为，移动性管理网元确定该终端设备是位置固定的终端设备或移动轨迹固定的终端设备。例如，移动性管理网元可以获取该终端设备的签约信息，并根据该终端设备的签约信息，确定该终端设备的位置固定或移动轨迹固定。也即，移动性管理网元仅针对位置固定或移动轨迹固定的终端设 备执行上述图2、图4和/或图5对应的实施例方案。其中移动轨迹固定可以理解为终端设备具有一定的移动性，但其移动轨迹是可预测的，网络侧能够感知该终端设备的地理位置情况。
下面结合具体示例，对上述方案进行说明。以下方案适用于4G网络，5G网络，或未来通信网络如6G网络等。
参考图6，为本申请实施例提供的一种通信方法的流程示意图。该方案是上述图2对应的实施例的一种具体实现。
该方法包括以下步骤：
步骤601，接入网设备向移动性管理网元发送N2建立消息(N2 setup message)。相应的，移动性管理网元接收该N2建立消息。
其中，该N2建立消息是在接入网设备上电之后，与移动性管理网元之间建立N2接口的流程发送的。如果当前网络为4G网络，那么该N2接口对应4G网络中的S1-MME接口。
可选的，该N2建立消息包括该接入网设备下的卫星小区的标识信息以及每个卫星小区对应的卫星的星历信息或卫星覆盖信息。
步骤602，终端设备向接入网设备发送注册请求消息。相应的，接入网设备接收该注册请求消息。
该注册请求消息用于请求注册至网络。
其中，该注册请求消息可以是5G网络中的注册请求消息，也可以是4G网络中的附着消息或TAU请求消息。
步骤603，接入网设备向移动性管理网元发送该注册请求消息和接入网(access network，AN)参数。相应的，移动性管理网元接收该注册请求消息和该AN参数。其中注册请求消息是终端设备承载于发往移动性管理网元的NAS消息中，AN参数是接入网设备在初始N2消息中添加的，跟注册请求消息一起发往移动性管理网元侧。
如果上述步骤601的N2建立消息中未携带接入网设备下的卫星小区的标识信息以及每个卫星小区对应的星历信息或卫星覆盖信息，则后续在该终端设备的注册流程中，接入网设备添加的AN参数可以包括终端设备所在的卫星小区对应的星历信息或卫星覆盖信息。
步骤604，移动性管理网元确定该终端设备的位置固定或移动轨迹固定。
或者理解为，移动性管理网元确定该终端设备是位置固定的终端设备或移动轨迹固定的终端设备。
作为一种实现方法，移动性管理网元可以获取该终端设备的签约信息，并根据该终端设备的签约信息，确定该终端设备的位置固定或移动轨迹固定。
该步骤604为可选步骤。
步骤605，移动性管理网元根据终端设备所在的卫星小区对应的星历信息或卫星覆盖信息，确定终端设备休眠开始时间，以及周期性TAU周期、周期性注册或eDRX周期中的一个或多个。
其中，如果移动性管理网元从接入网设备收到终端设备所在的卫星小区对应的星历信息，则移动性管理网元根据终端设备所在的卫星小区对应的星历信息确定终端设备所在的卫星小区对应的卫星覆盖信息。
其中，周期性TAU在5G网络中对应周期性注册流程，在4G网络中对应周期性TAU流程。
终端设备所在的卫星小区对应的卫星覆盖信息，即为该终端设备的卫星覆盖信息。
作为一种实现方法，终端设备的卫星覆盖信息所指示的未被卫星网络覆盖的时间段，被包含在某一个周期性注册的周期内，或者理解为，该周期性注册的周期内的休眠时间段包括该终端设备的卫星覆盖信息所指示的未被卫星网络覆盖的时间段。该实现方法的具体示例可以参考前述图3(a)。
作为一种实现方法，终端设备的卫星覆盖信息所指示的未被卫星网络覆盖的时间段，被包含在某一个eDRX周期内，或者理解为，该eDRX周期内的休眠时间段包括该终端设备的卫星覆盖信息所指示的未被卫星网络覆盖的时间段。该实现方法的具体示例可以参考前述图3(b)。
步骤606，注册流程的其它步骤。
步骤607，移动性管理网元向终端设备发送非接入层(non access stratum，NAS)消息。相应的，终端设备接收该NAS消息。
该NAS消息包括休眠开始时间，以及还包括周期性TAU周期、eDRX周期或周期性注册周期中的一个或多个。
作为一种实现方法，该NAS消息包括注册接受消息或附着接受消息或TAU接受消息，该消息包括休眠开始时间，以及还包括周期性注册周期、周期性TAU周期或eDRX周期中的一个或多个。
步骤608，终端设备根据休眠开始时间，在周期性TAU周期、周期性注册周期或eDRX周期内进行休眠。
作为一种实现方法，终端设备根据在周期性TAU周期内，从休眠开始时间开始进入休眠状态，并在该周期性TAU周期结束时结束休眠状态，该终端设备的休眠时间段包括该终端设备未被卫星网络覆盖的时间段。示例性地，终端设备可以按照图3(a)所示的方法进行休眠。
作为一种实现方法，终端设备根据在eDRX周期内，从休眠开始时间开始进入休眠状态，并在该eDRX周期结束时结束休眠状态，该终端设备的休眠时间段包括该终端设备未被卫星网络覆盖的时间段。示例性地，终端设备可以按照图3(b)所示的方法进行休眠。
上述方案，在终端设备的注册过程中，移动性管理网元根据接入网设备提供的小区对应的星历信息或卫星覆盖信息，确定休眠开始时间，以及确定eDRX周期、周期性TAU周期或周期性注册周期中的一个或多个，从而确保终端设备能够尽可能地在未被卫星网络覆盖的时间段内进行休眠，避免不必要的小区扫描、小区选择等网络连接操作，以节省终端设备的能耗。
参考图7，为本申请实施例提供的一种通信方法的流程示意图。该方案是上述图2对应的实施例的一种具体实现。该方法包括以下步骤：
步骤701至步骤704，同上述步骤601至步骤604。
其中，步骤704为可选步骤。
步骤705，移动性管理网元根据终端设备所在的卫星小区对应的星历信息或卫星覆盖信息，确定终端设备的休眠时间信息。
其中，如果移动性管理网元从接入网设备收到终端设备所在的卫星小区对应的星历信息，则移动性管理网元根据终端设备所在的卫星小区对应的星历信息确定终端设备所在的卫星小区对应的卫星覆盖信息。终端设备所在的卫星小区对应的卫星覆盖信息，即为该终 端设备的卫星覆盖信息。
作为一种实现方法，该休眠时间信息包括休眠开始时间和休眠结束时间，且该休眠开始时间与休眠结束时间之间的休眠时间段即为该终端设备未被卫星网络覆盖的时间段。
作为一种实现方法，该休眠时间信息包括休眠开始时间和休眠结束时间，且该休眠开始时间与休眠结束时间之间的休眠时间段包含该终端设备未被卫星网络覆盖的时间段，即该休眠开始时间与休眠结束时间指明的休眠时间段大于该终端设备未被卫星网络覆盖的时间段。
作为另一种实现方法，该休眠时间信息包括休眠开始时间和休眠时长，其中，根据休眠开始时间和休眠时长可以得到休眠结束时间。
其中，在该休眠时间信息对应的休眠时间段内，终端设备将会持续进行休眠，不会进行业务，即使是周期性TAU、周期性注册或有上行数据待传输也不会执行。
可选的，移动性管理网元可以按照现有方法，在终端设备被卫星网络覆盖的时间段内，根据业务信息确定eDRX周期、周期性TAU周期或周期性注册周期中的一个或多个。
作为一种实现方法，终端设备的卫星覆盖信息所指示的未被卫星网络覆盖的时间段，未被包含在任何eDRX周期、周期性TAU周期或周期性注册周期内，而是一个单独的休眠时间段。
步骤706，注册流程的其它步骤。
步骤707，移动性管理网元向终端设备发送NAS消息。相应的，终端设备接收该NAS消息。
该NAS消息包括休眠时间信息，可选的，该NAS消息还包括eDRX周期、周期性TAU周期或周期性注册周期中的一个或多个。
作为一种实现方法，该NAS消息包括注册接受消息、附着接受消息或TAU接受消息，该消息包括休眠时间信息，可选的，该注册接受消息还包括eDRX周期、周期性TAU周期或周期性注册周期中的一个或多个。
步骤708，终端设备根据休眠时间信息进行休眠。
在休眠时间信息指示的休眠时间段内进行休眠，不执行业务，即使是周期性TAU、周期性注册或有上行数据待传输也不执行。
可选的，该休眠时间信息指示的休眠时间段之后，终端设备进入卫星网络覆盖范围之内，此时可以根据eDRX周期、周期性TAU周期或周期性注册周期进行休眠。
步骤709，当终端设备对应的去注册定时器(或去附着定时器)超时，移动性管理网元根据终端设备的休眠时间信息，判断是否对该终端设备执行去注册(或去附着)。
当移动性管理网元确定该终端设备对应的去注册定时器(或去附着定时器)超时之后，移动性管理网元根据该终端设备的休眠时间信息，判断该终端设备当前是否处于未被卫星网络覆盖对应的休眠时间段内，如果该终端设备当前处于未被卫星网络覆盖对应的休眠时间段内，则移动性管理网元确定不对该终端设备执行去注册(或去附着)。如果该终端设备当前没有处于未被卫星网络覆盖对应的休眠时间段内，则移动性管理网元确定对该终端设备执行去注册(或去附着)。
该步骤709为可选步骤。
上述实施例是在终端设备的注册过程中，移动性管理网元根据接入网设备提供的卫星小区对应的星历信息或卫星覆盖信息，确定休眠时间信息，从而确保终端设备能够尽可能 地在未被卫星网络覆盖的时间内进行休眠，避免不必要的小区选择等网络连接操作，以节省终端设备的能耗。
作为一种实现方法，上述图7对应的实施例，可以应用于终端设备未被卫星网络覆盖的时间较长的场景。通过引入全新的节能模式，即在未被卫星网络覆盖的时间段内，终端设备始终休眠，不执行任何业务，包括不执行周期性TAU、周期性注册或上行数据传输，可以避免不必要且无效的小区扫描、小区选择等网络连接操作，最大程度减少终端设备的能耗。
参考图8，为本申请实施例提供的一种通信方法的流程示意图。该方案是上述图4对应的实施例的一种具体实现。
该方法包括以下步骤：
步骤801至步骤804，同上述步骤601至步骤604。
其中，步骤804为可选步骤。
步骤805，移动性管理网元确定终端设备的卫星覆盖信息。
其中，如果移动性管理网元从接入网设备收到终端设备所在的卫星小区对应的星历信息，则移动性管理网元根据终端设备所在的卫星小区对应的星历信息确定终端设备所在的卫星小区对应的卫星覆盖信息。终端设备所在的卫星小区对应的卫星覆盖信息，即为该终端设备的卫星覆盖信息。
如果移动性管理网元从接入网设备收到终端设备所在的卫星小区对应的卫星覆盖信息，则该终端设备所在的卫星小区对应的卫星覆盖信息，即为该终端设备的卫星覆盖信息。
可选的，移动性管理网元可以按照现有方法，确定eDRX周期、周期性TAU周期或周期性注册周期。
步骤806，注册流程的其它步骤。
步骤807，移动性管理网元向终端设备发送NAS消息。相应的，终端设备接收该NAS消息。
该NAS消息包括指示信息和终端设备的卫星覆盖信息。可选的，该NAS消息还包括eDRX周期、周期性TAU周期或周期性注册周期中的一个或多个。其中，该指示信息用于指示终端设备在周期性TAU、周期性注册定时器超时或有上行数据传输时，根据终端设备的卫星覆盖信息发起周期性TAU、周期性注册流程或传输上行数据。
作为一种实现方法，该NAS消息包括注册接受消息、附着接受消息或TAU接受消息，该消息包括指示信息和终端设备的卫星覆盖信息，可选的，该消息还包括eDRX周期、周期性TAU周期或周期性注册周期中的一个或多个。
步骤808，终端设备根据指示信息和终端设备的卫星覆盖信息，判断是否发起周期性TAU、周期性注册或传输上行数据。
具体的，根据指示信息和终端设备的卫星覆盖信息，判断终端设备是否被卫星网络覆盖，也即终端设备当前时刻是否被卫星网络覆盖。当终端设备被卫星网络覆盖，则终端设备发起周期性TAU、周期性注册或传输上行数据。当终端设备未被卫星网络覆盖，不发起周期性TAU、周期性注册或不传输上行数据。
步骤809，移动性管理网元根据指示信息和终端设备的卫星覆盖信息，判断是否执行终端设备去注册(或去附着)。
具体的，当终端设备对应的去注册定时器(或去附着定时器)超时，根据终端设备的 卫星覆盖信息，判断是否执行终端设备去注册(或去附着)。其中，当终端设备被卫星网络覆盖，移动性管理网元对终端设备执行去注册(或去附着)。当终端设备未被卫星网络覆盖，移动性管理网元不对终端设备执行去注册(或去附着)。
上述实施例是在终端设备的注册过程、附着过程或TAU过程中，移动性管理网元确定终端设备的卫星覆盖信息，并指示终端设备根据该卫星覆盖信息执行周期性TAU、周期性注册或传输上行数据，可以避免终端设备在未被卫星网络覆盖的时间范围内执行周期性TAU、周期性注册或传输上行数据，可以避免不必要的小区扫描、小区选择等网络连接操作，以节省终端设备的能耗。并且，也可以避免终端设备在未被卫星网络覆盖的时间范围内被网络侧去注册(或去附着)。
作为一种实现方法，上述图8对应的实施例，可以应用于终端设备未被卫星网络覆盖的时间较长的场景。这是因为：周期性TAU或周期性注册的周期时间存在一个限值，不可能很大，因此当终端设备未被卫星网络覆盖的时间比较长时，不可避免地需要进行周期性TAU或周期性注册，而此时终端设备未被卫星网络覆盖，将导致终端设备不停地进行小区扫描与小区选择，造成更高的能耗损失，同时网络侧由于未接收到来自终端设备的周期性TAU或周期性注册，会将终端设备去注册或去附着，因此为了使得空闲态的终端设备未被卫星网络覆盖时避免不必要的周期性TAU或周期性注册，上述图8对应的实施例中，当终端设备未被卫星网络覆盖时，终端设备不会执行周期性TAU或周期性注册和上行数据传输，网络侧的移动性管理网元也不会对终端设备执行去注册(或去附着)，从而可以最大程度减少终端设备和移动性管理网元间的信令交互，降低终端设备的能耗。
参考图9，为本申请实施例提供的一种通信方法的流程示意图。该方案是上述图4对应的实施例的一种具体实现。
该方法包括以下步骤：
步骤901至步骤906，同上述步骤801至步骤806。
步骤907，移动性管理网元向终端设备发送NAS消息。相应的，终端设备接收该NAS消息。
该NAS消息包括指示信息。可选的，该NAS消息还包括eDRX周期、周期性TAU周期或周期性注册周期中的一个或多个。其中，该指示信息用于指示终端设备在周期性TAU定时器超时或周期性注册定时器超时或有上行数据传输时，自行检测是否被卫星网络覆盖。
作为一种实现方法，该NAS消息包括注册接受消息、附着接受消息或TAU接受消息，该消息包括该指示信息，可选的，该注册接受消息还包括eDRX周期和/或TAU周期。
步骤908，终端设备根据指示信息，判断是否发起周期性TAU、周期性注册或传输上行数据。
具体的，根据指示信息，判断终端设备是否被卫星网络覆盖，也即终端设备当前时刻是否被卫星网络覆盖。当终端设备被卫星网络覆盖，则终端设备发起周期性TAU、周期性注册或传输上行数据。当终端设备未被卫星网络覆盖，不发起周期性TAU、周期性注册或不传输上行数据。
步骤909，同上述步骤809。
上述实施例是在终端设备的注册过程中，移动性管理网元指示终端设备根据是否被卫星网络覆盖来执行周期性TAU、周期性注册或传输上行数据，可以避免终端设备在未被卫 星网络覆盖的时间范围内执行周期性TAU、周期性注册或传输上行数据，可以避免不必要的小区扫描、小区选择等网络连接操作，以节省终端设备的能耗。并且，也可以避免终端设备在未被卫星网络覆盖的时间范围内被网络侧去注册(或去附着)。
作为一种实现方法，上述图9对应的实施例，可以应用于终端设备未被卫星网络覆盖的时间较长的场景。这是因为：周期性TAU、周期性注册的周期时间存在一个限值，不可能很大，因此当终端设备未被卫星网络覆盖的时间比较长时，不可避免地需要进行周期性TAU、周期性注册，而此时终端设备未被卫星网络覆盖，将导致终端设备不停地进行小区扫描与小区选择等网络连接操作，造成更高的能耗损失，同时网络侧由于未接收到来自终端设备的周期性TAU请求或周期性注册请求，会将终端设备去注册或去附着，因此为了使得空闲态的终端设备未被卫星网络覆盖时避免不必要的周期性TAU或周期性注册，上述图9对应的实施例中，当终端设备未被卫星网络覆盖时，终端设备不会执行周期性TAU或周期性注册和上行数据传输，网络侧的移动性管理网元也不会对终端设备执行去注册(或去附着)，从而可以最大程度减少终端设备和移动性管理网元间的信令交互，降低终端设备的能耗。
参考图10，为本申请实施例提供的一种通信方法的流程示意图。该方案是上述图5对应的实施例的一种具体实现。
该方法包括以下步骤：
步骤1001，同上述步骤601。
步骤1002，终端设备进入空闲态后，接入网设备向移动性管理网元发送N2消息。相应的，移动性管理网元接收该N2消息。
如果上述步骤1001的N2建立消息中未携带接入网设备下的卫星小区的标识信息以及每个卫星小区对应的星历信息或卫星覆盖信息，则该N2消息中可以包括该终端设备所在的卫星小区对应的星历信息或卫星覆盖信息。可选的，该N2消息还包括终端设备所在的卫星小区的标识信息。该终端设备所在的卫星小区，也可以理解为是该终端设备进入空闲态之前，最后访问的卫星小区。具体的，该N2消息可以是N2释放消息，在4G网络中对应的为S1释放消息。
步骤1003，同上述步骤604。
该步骤1003为可选步骤。
步骤1004，移动性管理网元判断终端设备是否可达。
作为一种实现方法，移动性管理网元根据终端设备的卫星覆盖信息，判断终端设备是否可达。如果终端设备当前未被卫星网络覆盖，则终端设备不可达。如果终端设备当前被卫星网络覆盖，则根据现有方案判断终端设备是否可达，如根据终端设备的节能休眠状态等。其中，终端设备的卫星覆盖信息即为终端设备所在的卫星小区的卫星覆盖信息。
作为一种实现方法，移动性管理网元根据终端设备的卫星覆盖信息，以及根据eDRX周期、周期性TAU周期或周期性注册周期，判断终端设备是否可达。如果终端设备当前未被卫星网络覆盖，或者终端设备处于eDRX周期的休眠时间内，或者终端设备处于周期性TAU周期的休眠时间内，或者终端设备处于周期性注册周期的休眠时间内，则终端设备不可达。如果终端设备当前被卫星网络覆盖，并且终端设备未处于eDRX周期的休眠时间内、终端设备未处于周期性TAU周期的休眠时间内以及终端设备未处于周期性注册周期的休眠时间内，则终端设备可达。应理解，周期性TAU周期或周期性注册周期内的休 眠时间是指终端设备从连接态进入空闲态后，经过一段定时器后进入休眠的休眠时间段，如4G网络中的节能模式(PowerSaving Mode，PSM)，5G网络中的仅上行连接(Mobile Initiated Connection Only,MICO)模式。
步骤1005，如果终端设备不可达，移动性管理网元根据终端设备的卫星覆盖信息，确定最大等待时间。
该步骤的具体实现可以参考前述步骤502的描述。
步骤1006，在终端设备进入可达状态时，移动性管理网元向接入网设备发送寻呼消息。相应的，接入网设备接收该寻呼消息。
该寻呼消息包括终端设备的标识信息以及寻呼小区的标识信息。
该寻呼小区，可以是该终端设备最后访问的小区，或者也可以是该终端设备最后访问的小区所在的跟踪区域内的所有小区。
步骤1007，接入网设备寻呼终端设备。
根据上述方案，移动性管理网元可以根据终端设备的卫星覆盖信息进行可达性判断，如果终端设备不可达，则根据卫星覆盖信息确定最大等待时间，确保终端设备未被卫星网络覆盖时，不对终端设备进行寻呼，也不向终端设备发送下行数据，可以减少移动性管理网元的能耗以及减少数据丢失。
作为一种实现方法，如果该方案中的移动性管理网元是4G中的MME，则在步骤1004之前，MME还可以从用户面网元收到下行数据到达通知，该下行数据到达通知触发MME执行步骤1004。并且，在步骤1005之后，MME还根据最大等待时间或下行缓存时间，确定下行数据缓存超时时长，用于指示当前核心网侧是否缓存有该终端设备的数据，并在下行数据缓存超时时长到达后，MME会认定当前已经没有该终端设备的下行缓存数据。
作为一种实现方法，如果该方案中的移动性管理网元是5G中的AMF网元，则在步骤1004之前，AMF网元还可以从SMF网元收到下行数据到达通知，该下行数据到达通知触发AMF网元执行步骤1004。并且，在步骤1005之后，AMF网元还根据最大等待时间，指示SMF网元和/或用户面网元进行数据缓存，然后SMF网元可以根据该最大等待时间，确定扩展缓存时间，该扩展缓存时间指示用户面网元缓存下行数据的具体时长，并在扩展缓存时间到达后且该缓存数据仍未发送给终端设备，SMF网元将会丢弃对应缓存的数据。
参考图11，为本申请实施例提供的一种通信方法的流程示意图。该方案是上述图5对应的实施例的一种具体实现。
该方法包括以下步骤：
步骤1101，移动性管理网元向接入网设备发送寻呼消息。相应的，接入网设备接收该寻呼消息。
该寻呼消息包括终端设备的标识信息以及寻呼小区的标识信息。
该寻呼小区，可以是该终端设备最后访问的小区，或者也可以是该终端设备最后访问的小区所在的跟踪区域内的所有小区。
步骤1102，接入网设备确定终端设备所在的卫星小区未被卫星网络覆盖。
作为一种实现方法，接入网设备根据终端设备的卫星覆盖信息，判断终端设备是否有卫星网络覆盖。如果终端设备当前未被卫星网络覆盖，则此次寻呼失败。如果终端设备当前被卫星网络覆盖，则对终端设备进行寻呼。其中，终端设备的卫星覆盖信息即为终端设 备所在的卫星小区的卫星覆盖信息。
步骤1103，接入网设备向移动性管理网元发送第一消息。相应的，移动性管理网元接收该第一消息。
具体地，该第一消息可以为N2消息或寻呼失败消息。
由于接入网设备确定终端设备当前未被卫星覆盖，则向移动性管理网元发送第一消息，该第一消息包括寻呼失败指示和终端设备的卫星覆盖信息，该寻呼失败指示用于指示此次寻呼失败原因为终端设备未被卫星网络覆盖，可选的，寻呼失败指示还指示需移动管理网元根据该卫星覆盖信息进行可达性判断/寻呼。
作为另一种实现方法，由于接入网设备确定终端设备当前未被卫星覆盖，则向移动性管理网元发送第一消息，该第一消息包括终端设备的卫星覆盖信息，该卫星覆盖信息指示此次寻呼失败原因为终端设备未被卫星网络覆盖，可选的，该卫星覆盖信息还指示需移动管理网元根据该卫星覆盖信息进行可达性判断/寻呼。
步骤1104，移动性管理网元根据终端设备的卫星覆盖信息，确定最大等待时间。
该步骤的具体实现可以参考前述步骤502的描述。
步骤1105至步骤1106，同上述步骤1006至步骤1007。
根据上述方案，移动性管理网元通知接入网设备寻呼终端设备时，接入网设备根据终端设备的卫星覆盖信息判断当前终端设备是否可进行寻呼，如果终端设备不在卫星网络覆盖范围内，则接入网设备通知移动性管理网元寻呼失败且将终端设备的卫星覆盖信息发送给移动性管理网元，从而移动性管理网元根据卫星覆盖信息确定最大等待时间，确保终端设备未被卫星网络覆盖时，不对终端设备进行寻呼，可以降低移动性管理网元与接入网设备之间不必要的信令交互，同时避免接入网设备寻呼资源浪费以及终端设备的下行数据丢失。
作为一种实现方法，如果该方案中的移动性管理网元是4G中的MME，则在步骤1101之前，MME还可以从用户面网元收到下行数据到达通知，该下行数据到达通知触发MME执行步骤1101。并且，在步骤1104之后，MME还根据最大等待时间，即下行缓存时间确定下行数据缓存超时时长，用于指示当前核心网侧是否缓存有该终端设备的数据，并在下行数据缓存超时时长到达后，MME会认定当前已经没有该终端设备的下行缓存数据。
作为一种实现方法，如果该方案中的移动性管理网元是5G中的AMF网元，则在步骤1101之前，AMF网元还可以从SMF网元收到下行数据到达通知，该下行数据到达通知触发AMF网元执行步骤1101。并且，在步骤1104之后，AMF网元还根据最大等待时间，指示SMF网元和/或用户面网元进行数据缓存，然后SMF网元可以根据该最大等待时间，确定扩展缓存时间，该扩展缓存时间指示用户面网元缓存下行数据的具体时长，并在扩展缓存时间到达后且该缓存数据仍未发送给终端设备，SMF网元将会丢弃对应缓存的数据。
以下图12对应的实施例和图14对应的实施例中，以移动性管理网元确定一个合适的周期性TAU周期或周期性注册周期，以使得终端设备根据该周期性TAU周期或周期性注册周期，在未被卫星网络覆盖的时间段内不执行上行信令或上行数据传输为例，进行说明。在实际应用中，移动性管理网元也可以确定其它参数(比如服务间隔(service gap)、eDRX)，以使得终端设备根据该其它参数，在未被卫星网络覆盖的时间段内不执行上行信令或上行数据传输。可以理解为，该图12对应的实施例和图14对应的实施例中出现的“周期性TAU 周期”、“周期性注册周期”可以替换为其它参数(如服务间隔、eDRX)。其中，服务间隔的定义可以参考TS23.401 V17.2.0。其中，该“其它参数”可以是表示时长的参数。
参考图12，为本申请实施例提供的一种通信方法的流程示意图。示例性的，在4G应用场景中，移动性管理网元、接入网设备分别可以是MME、eNB。在5G应用场景中，移动性管理网元、接入网设备分别可以是AMF、gNB。其中，该实施例中的终端设备是卫星接入类型的终端设备。
该方法包括以下步骤：
步骤1201，移动性管理网元根据终端设备的卫星覆盖信息，确定周期性TAU周期或周期性注册周期。
可选的，终端设备的位置固定或移动轨迹固定。
其中，卫星覆盖信息的含义可以参考前述描述，这里不再赘述。
可选，在移动性管理网元确定该终端设备是一个卫星接入类型的终端设备的情形下，移动性管理网元可以根据终端设备的卫星覆盖信息，确定周期性TAU周期或周期性注册周期。
其中，在4G中，移动性管理网元是MME，MME确定周期性TAU周期，其中，在具体实现时，该周期性TAU周期可以用周期性TAU定时器来表示。在5G中，移动性管理网元是AMF，AMF确定周期性注册周期，其中，在具体实现时，该周期性注册周期可以用周期性注册定时器来表示。
其中，该周期性TAU周期对应的时间段包括终端设备未被卫星网络覆盖的时间段，或周期性注册周期对应的时间段包括终端设备未被卫星网络覆盖的时间段，从而确保当该终端设备未被卫星网络覆盖时，终端设备不会进行周期性TAU流程或周期性注册流程，终端设备持续处于休眠状态，也即从终端设备进入空闲态开始，到周期性TAU定时器或周期性注册定时器超时之前的时间段包含终端设备未被卫星网络覆盖的时间段。
下面介绍触发移动性管理网元执行上述步骤1201的不同实现方法。
方法一，移动性管理网元根据终端设备的卫星覆盖信息，确定该终端设备即将无卫星网络覆盖，则向接入网设备发送指示信息，该指示信息指示接入网设备执行终端设备连接释放流程，然后接入网设备向移动性管理网元发送UE上下文释放请求，该UE上下文释放请求用于请求移动性管理网元释放终端设备的上下文，移动性管理网元在收到该UE上下文释放请求之后，触发执行上述步骤1201。
方法二，接入网设备根据终端设备的卫星覆盖信息，确定该终端设备即将无卫星网络覆盖，进而触发接入网设备向移动性管理网元发送上下文释放请求，该上下文释放请求用于请求移动性管理网元释放终端设备的上下文，移动性管理网元在收到该UE上下文释放请求之后，触发执行上述步骤1201。
方法三，终端设备根据终端设备的卫星覆盖信息，确定该终端设备即将无卫星网络覆盖，进而向移动性管理网元发送TAU请求或移动注册更新请求，移动性管理网元在收到该TAU请求或移动注册更新请求之后，触发执行上述步骤1201。
可选的，移动性管理网元还根据终端设备的卫星覆盖信息确定第一时长，该第一时长指的是终端设备进入空闲态后、进入休眠态之前的时长。该第一时长也可以称为终端设备处于活跃态的时长(active time)。其中，当终端设备处于活跃态时，网络可以通过寻呼将 终端设备从空闲态呼入连接态。
步骤1202，移动性管理网元向终端设备发送周期性TAU周期或周期性注册周期。
其中，在4G中，移动性管理网元，如MME，向终端设备发送周期性TAU周期。可选的，MME向终端设备发送GUTI重配置命令(GUTI Reallocation Command)，该GUTI Reallocation Command中携带周期性TAU周期。或者，MME向终端设备发送TAU接受消息，该TAU接受消息中携带周期性TAU周期。
在5G中，移动性管理网元，如AMF，向终端设备发送周期性注册周期。可选的，AMF向终端设备发送配置更新命令(UE Configuration Update Command)，该UE Configuration Update Command中携带周期性注册周期。或者，AMF向终端设备发送移动注册更新接受消息，该移动注册更新接受消息中携带周期性注册周期。
作为一种实现方法，移动性管理网元通过接入网设备向终端设备发送周期性TAU周期或周期性注册周期。也即移动性管理网元向接入网设备发送周期性TAU周期或周期性注册周期，然后接入网设备向终端设备发送周期性TAU周期或周期性注册周期。
可选的，移动性管理网元还可以向终端设备发送第一时长，该第一时长指的是终端设备进入空闲态后、进入休眠态之前的时长。该第一时长也可以称为终端设备处于活跃态的时长(active time)。其中，当终端设备处于活跃态时，网络可以通过寻呼将终端设备从空闲态呼入连接态。
可选地，移动性管理网元还可以向终端设备发送原因值，该原因值为卫星非连续覆盖，或者该原因值用于指示该终端设备在休眠期间不进行上行传输。
步骤1203，终端设备根据周期性TAU周期执行周期性TAU，或者根据周期性注册周期执行周期性注册。
参考图13(a)，为本申请实施例提供的周期性TAU周期或周期性注册周期示意图。其中，周期性TAU周期(也即周期性TAU定时器)或周期性注册周期(也即周期性注册定时器)的起始时刻，可以是终端设备进入空闲态的时刻。周期性TAU周期对应的时间段或周期性注册周期对应的时间段，包含终端设备未被卫星网络覆盖的时间段。终端设备在未被卫星网络覆盖的时间段内，进入休眠态。
参考图13(b)，为本申请实施例提供的周期性TAU周期或周期性注册周期另一个示意图。其中，周期性TAU周期(也即周期性TAU定时器)或周期性注册周期(也即周期性注册定时器)的起始时刻，可以是终端设备进入空闲态的时刻。周期性TAU周期对应的时间段或周期性注册周期对应的时间段，包含终端设备未被卫星网络覆盖的时间段。周期性TAU周期对应的时间段或周期性注册周期对应的时间段还包含第一时长，终端设备在该第一时长内可以被网络侧寻呼唤醒，从而进入连接态。终端设备在未被卫星网络覆盖的时间段内，进入休眠态。
可选的，如果终端设备收到上述原因值，且原因值指示终端设备在休眠期间不进行上行传输，则当有上行传输需求，终端设备根据该原因值，在周期性TAU周期或周期性注册周期对应的时间段内，不进行上行传输。
上述方案，移动性管理网元根据终端设备的卫星覆盖信息，确定周期性TAU周期或周期性注册周期，可以使得周期性TAU周期对应的时间段或周期性注册周期对应的时间段包含终端设备未被卫星网络覆盖的时间段，确保终端设备能够尽可能地在未被卫星网络覆盖的时间段内不执行周期性TAU流程或周期性注册流程，避免不必要的小区选择等网 络连接操作，以节省终端设备的能耗。
参考图14，为本申请实施例提供的一种通信方法的流程示意图。该方案是上述图12对应的实施例的一种具体实现。示例性的，在4G应用场景中，移动性管理网元、接入网设备分别可以是MME、eNB。在5G应用场景中，移动性管理网元、接入网设备分别可以是AMF、gNB。其中，该实施例中的终端设备是卫星接入类型的终端设备。
该方法包括以下步骤：
步骤1401，移动性管理网元根据终端设备的卫星覆盖信息，确定该终端设备即将无卫星网络覆盖，则向接入网设备发送指示信息。相应的，接入网设备接收该指示信息。
可选的，终端设备的位置固定或移动轨迹固定。
作为一种实现方法，移动性管理网元可以从接入网设备、第三方或终端设备接收该终端设备的卫星覆盖信息。作为另一种实现方法，移动性管理网元可以从接入网设备、第三方或终端设备接收小区的星历信息，然后根据该小区的星历信息确定该终端设备的卫星覆盖信息。
该指示信息指示接入网设备执行终端设备释放流程。其中，在4G中，终端设备释放流程指的是S1释放流程。在5G中，终端设备释放流程指的是接入网(access network，AN)释放流程。
该步骤1401为可选步骤。
步骤1402，接入网设备向移动性管理网元发送UE上下文释放请求。相应的，移动性管理网元接收该UE上下文释放请求。
其中，该UE上下文释放请求用于请求移动性管理网元释放UE上下文，从而移动性管理网元可以释放与终端设备之间的连接，使得终端设备进入空闲态。
作为一种实现方法，如果执行上述步骤1401，则上述指示信息触发接入网设备执行该步骤1402。
作为另一种实现方法，如果不执行上述步骤1401，则可以是接入网设备根据终端设备的卫星覆盖信息，确定该终端设备即将无卫星网络覆盖，进而触发接入网设备执行该步骤1402。
作为另一种实现方法，如果不执行上述步骤1401，则可以是接入网设备根据其它原因触发接入网设备执行该步骤1402，这里的其它原因包括但不限于：该终端设备没有正在执行的业务、运营商的运维系统的介入(O&M Intervention)或未知错误(Unspecified Failure)。
可选的，在4G中，移动性管理网元(即MME)收到UE上下文释放请求之后，还可以请求服务网关(serving gateway，S-GW)进行承载资源的释放。在5G中，移动性管理网元(即AMF)收到UE上下文释放请求之后，还可以请求SMF进行承载资源的释放。
步骤1403，移动性管理网元根据终端设备的卫星覆盖信息，确定周期性TAU周期或周期性注册周期。
可选，在移动性管理网元确定该终端设备是一个卫星接入类型的终端设备的情形下，移动性管理网元可以根据终端设备的卫星覆盖信息，确定周期性TAU周期或周期性注册周期。
其中，在4G中，移动性管理网元是MME，MME确定周期性TAU周期，其中，在具体实现时，该周期性TAU周期可以用周期性TAU定时器来表示。在5G中，移动性管 理网元是AMF，AMF确定周期性注册周期，其中，在具体实现时，该周期性注册周期可以用周期性注册定时器来表示。
其中，该周期性TAU周期对应的时间段包括终端设备未被卫星网络覆盖的时间段，或周期性注册周期对应的时间段包括终端设备未被卫星网络覆盖的时间段，从而确保当该终端设备未被卫星网络覆盖时，终端设备不会进行周期性TAU流程或周期性注册流程，终端设备持续处于休眠状态，也即从终端设备进入空闲态开始，到周期性TAU定时器或周期性注册定时器超时之前的时间段包含终端设备未被卫星网络覆盖的时间段。
可选的，移动性管理网元还确定第一时长，该第一时长指的是终端设备进入空闲态后、进入休眠态之前的时长。该第一时长也可以称为终端设备处于活跃态的时长(active time)。其中，当终端设备处于活跃态时，网络可以通过寻呼将终端设备从空闲态呼入连接态。
步骤1404，移动性管理网元向终端设备发送重配置命令，该重配置命令中包含周期性TAU周期或周期性注册周期。相应的，终端设备接收该重配置命令。
可选的，该重配置命令还包含终端设备处于活跃态的时长。
可选的，该重配置命令还包含原因值，该原因值为卫星非连续覆盖，可选的，该原因值还指示终端设备在休眠期间不进行上行传输。其中，这里的上行传输包括上行业务的数据传输和/或上行信令的传输。
步骤1405，终端设备向移动性管理网元发送重配置响应。相应的，移动性管理网元接收该重配置响应。
其中，在4G中，重配置命令可以是GUTI Reallocation Command，GUTI Reallocation Command中包含周期性TAU周期，可选的还包含第一时长和/或原因值。重配置响应可以是GUTI Reallocation Complete消息。
在4G中，重配置命令可以是UE Configuration Update Command，UE Configuration Update Command中包含周期性注册周期，可选的还包含第一时长和/或原因值。重配置响应可以是UE Configuration Update Complete消息。
上述步骤1404和步骤1405为可选步骤。
步骤1406，移动性管理网元向接入网设备发送UE上下文释放命令。相应的，接入网设备接收UE上下文释放命令。
该UE上下文释放命令用于指示接入网设备释放UE上下文。
其中，如果没有执行上述步骤1404和步骤1405，则该UE上下文释放命令中包含周期性TAU周期或周期性注册周期，可选的还包含第一时长和/或原因值。
步骤1407，接入网设备向终端设备发送RRC连接释放请求。相应的，终端设备接收该RRC连接释放请求。
如果上述UE上下文释放命令中包含周期性TAU周期或周期性注册周期，则该RRC连接释放请求包括该周期性TAU周期或周期性注册周期。如果上述UE上下文释放命令中还包含第一时长和/或原因值，则该RRC连接释放请求还包括第一时长和/或原因值。
步骤1408，接入网设备向移动性管理网元发送UE上下文释放完成消息。相应的，移动性管理网元接收该UE上下文释放完成消息。
该步骤1408可选。
步骤1409，终端设备根据原因值，在周期性TAU周期或周期性注册周期对应的时间段内，不进行上行传输。
也即，当有上行传输需求，终端设备根据该原因值，在周期性TAU周期或周期性注册周期对应的时间段内，不进行上行传输。
该步骤1409为可选步骤。
当上述步骤1404或步骤1407包含原因值，则执行该步骤1409。
根据上述方案，在终端设备的释放流程中，在终端设备进入空闲态时，触发周期性TAU周期或周期性注册周期的更新，从而保证终端设备进入空闲态后，在未被卫星网络覆盖的时间段内进行休眠，从而减少终端设备的功耗。
参考图15，为本申请实施例提供的一种通信方法的流程示意图。该方案是上述图12对应的实施例的一种具体实现。示例性的，在4G应用场景中，移动性管理网元、接入网设备分别可以是MME、eNB。在5G应用场景中，移动性管理网元、接入网设备分别可以是AMF、gNB。
该方法包括以下步骤：
步骤1501，终端设备根据终端设备的卫星覆盖信息，确定该终端设备即将无卫星网络覆盖，则通过接入网设备向移动性管理网元发送TAU请求或移动注册更新(Mobility Registration Update)请求。相应的，移动性管理网元接收该TAU请求或移动注册更新请求。
可选的，终端设备的位置固定或移动轨迹固定。
作为一种实现方法，终端设备可以从接入网设备、第三方或核心网设备接收该终端设备的卫星覆盖信息。作为另一种实现方法，终端设备可以从接入网设备、第三方或核心网设备接收小区的星历信息，然后根据该小区的星历信息确定该终端设备的卫星覆盖信息。
其中，在4G中，接入网设备向移动性管理网元(即MME)发送TAU请求。在5G中，接入网设备向移动性管理网元(即AMF)发送移动注册更新请求。
步骤1502，同上述步骤1403。
步骤1503，移动性管理网元通过接入网设备向终端设备发送TAU接受消息或移动注册更新接受消息，该TAU接受消息中包含周期性TAU周期，或者该移动注册更新接受消息中包含周期性注册周期。相应的，终端设备接收该TAU接受消息或移动注册更新接受消息。
其中，在4G中，接入网设备向移动性管理网元(即MME)发送TAU请求，相应的，MME向接入网设备发送TAU接受消息。在5G中，接入网设备向移动性管理网元(即AMF)发送移动注册更新请求，相应的，AMF向接入网设备发送移动注册更新接受消息。
可选的，该TAU接受消息或移动注册更新接受消息还包含第一时长，该第一时长的含义参考步骤1403中的描述。
可选的，该TAU接受消息或移动注册更新接受消息还包含原因值，该原因值的含义参考步骤1403中的描述。
步骤1504，终端设备根据原因值，在周期性TAU周期或周期性注册周期对应的时间段内，不进行上行传输。
也即，当有上行传输需求，终端设备根据该原因值，在周期性TAU周期或周期性注册周期对应的时间段内，不进行上行传输。
该步骤1504为可选步骤。当上述步骤1503包含原因值，则执行该步骤1504。
根据上述方案，在终端设备即将无卫星网络覆盖之前，终端设备触发周期性TAU流程或周期性注册流程，使得移动性管理网元根据终端设备的卫星覆盖信息确定周期性TAU周期或周期性注册周期，该周期性TAU周期或周期性注册周期对应的时间段包括终端设备未被卫星网络覆盖的时间段，从而保证终端设备进入空闲态后，在未被卫星网络覆盖的时间段内进行休眠，从而减少终端设备的功耗。
参考图16(a)，为本申请实施例提供的一种通信方法的流程示意图。该方案是上述图4对应的实施例的一种具体实现。该方法包括以下步骤：
步骤1601a，终端设备获取终端设备的卫星覆盖信息。
可选的，终端设备的位置固定或移动轨迹固定。
作为一种实现方法，终端设备可以从接入网设备、第三方或核心网设备(如移动性管理网元)接收该终端设备的卫星覆盖信息。作为另一种实现方法，终端设备可以从接入网设备、第三方或核心网设备接收星历信息，然后根据该星历信息确定该终端设备的卫星覆盖信息。
其中，当终端设备从接入网设备接收该终端设备的卫星覆盖信息或星历信息，则可以通过以下方法实现：终端设备从接入网设备接收RRC消息，该RRC消息包括该终端设备的卫星覆盖信息或星历信息。其中，该RRC消息可以是RRC重配置或广播消息。
其中，当终端设备从移动性管理网元接收该终端设备的卫星覆盖信息或星历信息，则可以通过以下方法实现：终端设备从移动性管理网元接收NAS消息，该NAS消息包括终端设备的卫星覆盖信息或星历信息。可选的，该NAS消息还包括eDRX周期、周期性TAU周期或周期性注册周期中的一个或多个。该NAS消息可以是注册接受消息、附着接受消息或TAU接受消息。
其中，该终端设备的卫星覆盖信息也可以是星历信息。
步骤1602a，终端设备根据终端设备的卫星覆盖信息，判断是否发起周期性TAU、周期性注册或传输上行数据。
具体的，终端设备根据终端设备的卫星覆盖信息，判断终端设备是否被卫星网络覆盖，也即终端设备当前时刻是否被卫星网络覆盖。当终端设备被卫星网络覆盖，则终端设备发起周期性TAU、周期性注册或传输上行数据。当终端设备未被卫星网络覆盖，不发起周期性TAU、周期性注册或不传输上行数据。
作为一种实现方法，终端设备还可以从接入网设备或移动性管理网元接收指示信息，该指示信息用于指示终端设备有上行传输需求时自行检查卫星网络覆盖情况，并根据卫星网络覆盖情况进行上行传输。这里的上行传输需求包括但不限于：周期性TAU、周期性注册、上行数据传输。当终端设备收到该指示信息，则该步骤1602a可以是：终端设备根据终端设备的卫星覆盖信息和该指示信息，判断是否发起周期性TAU、周期性注册或传输上行数据。其中，当终端设备被卫星网络覆盖，则终端设备发起周期性TAU、周期性注册或传输上行数据。当终端设备未被卫星网络覆盖，不发起周期性TAU、周期性注册或不传输上行数据。
根据上述方案，当终端设备未被卫星网络覆盖，即使有上行传输需求，也不执行上行传输，可以避免不必要且无效的小区扫描、小区选择等网络连接操作，以节省终端设备的能耗。
可选的，上述图16(a)对应的实施例可以应用于终端设备未被卫星网络覆盖的时间较长的场景。这是因为：周期性TAU或周期性注册的周期时间存在一个限值，不可能很大，因此当终端设备未被卫星网络覆盖的时间比较长时，不可避免地需要进行周期性TAU或周期性注册，而此时终端设备未被卫星网络覆盖，将导致终端设备不停地进行小区扫描与小区选择，造成更高的能耗损失，因此为了使得空闲态的终端设备未被卫星网络覆盖时避免不必要的周期性TAU或周期性注册，上述图16(a)对应的实施例中，当终端设备未被卫星网络覆盖时，终端设备不会执行周期性TAU或周期性注册和上行数据传输，从而可以最大程度减少终端设备和移动性管理网元间的信令交互，降低终端设备的能耗。
参考图16(b)，为本申请实施例提供的一种通信方法的流程示意图。该方案是上述图4对应的实施例的一种具体实现。该方法包括以下步骤：
步骤1601b，移动性管理网元获取终端设备的卫星覆盖信息。
作为一种实现方法，移动性管理网元可以从终端设备、接入网设备或第三方接收该终端设备的卫星覆盖信息，其中该终端设备的卫星覆盖信息也可以是星历信息。
作为另一种实现方法，移动性管理网元可以从终端设备、接入网设备或第三方接收星历信息，然后根据该星历信息确定该终端设备的卫星覆盖信息。
步骤1602b，移动性管理网元根据终端设备的卫星覆盖信息，判断是否执行终端设备去注册(或去附着)。
具体的，当终端设备对应的去注册定时器(或去附着定时器)超时，根据终端设备的卫星覆盖信息，判断是否执行终端设备去注册(或去附着)。其中，当终端设备被卫星网络覆盖，移动性管理网元对终端设备执行去注册(或去附着)。当终端设备未被卫星网络覆盖，移动性管理网元不对终端设备执行去注册(或去附着)。
其中，不对终端设备执行去注册，也可以理解为是保持终端设备的注册状态不变。不对终端设备执行去附着，也可以理解为是保持终端设备的附着状态不变，即保持终端设备一直处于EMM注册状态。可选的，不对终端设备执行去注册时响应于终端设备未被卫星网络覆盖。
根据上述方案，由于减少了终端设备的状态在注册和去注册之间来回切换，或者附着和去附着之间来回切换，可以减少终端设备与网络间的信令交互，降低终端设备的能耗。
作为一种实现方法，可以将上述图16(a)对应的实施例与图16(b)对应的实施例相结合实施。
可以理解的是，为了实现上述实施例中功能，移动性管理网元、接入网设备或终端设备包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件或硬件和计算机软件相结合的形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图17和图18为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中移动性管理网元、接入网设备或终端设备的功能，因此也能实现上述方法实施例所具备的有益效果。在本申请的实施例中，该通信装置可以是移动性管理网元、接入网设备或终端设备，也可以是应用于移动性管理网元、接入网设备或终端设备的模块(如芯片)。
如图17所示，通信装置1700包括处理单元1710和收发单元1720。通信装置1700用 于实现上述方法实施例中移动性管理网元、接入网设备或终端设备的功能。
在第一个实施例中，该通信装置用于执行移动性管理性网元的操作，处理单元1710，用于根据终端设备的卫星覆盖信息，确定该终端设备的休眠时间信息，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段，该休眠时间信息对应的休眠时间段包括该终端设备未被卫星网络覆盖的时间段；收发单元1720，用于向该终端设备发送该休眠时间信息。
在一种可能的实现方法中，处理单元1710，用于根据该卫星覆盖信息，确定该终端设备的eDRX周期、周期性TAU周期或者周期性注册周期中的一个或多个；其中，该休眠时间信息包括休眠开始时间，该休眠开始时间位于该eDRX周期、该周期性TAU周期或周期性注册周期内。
在一种可能的实现方法中，该休眠时间信息包括休眠开始时间和休眠结束时间；或者，该休眠时间信息包括休眠开始时间和休眠时长。
在一种可能的实现方法中，处理单元1710，用于通过收发单元1720接收该卫星覆盖信息；或者，通过收发单元1720接收该终端设备所在的卫星小区的星历信息，并根据该星历信息确定该卫星覆盖信息。
在一种可能的实现方法中，处理单元1710，用于确定该终端设备的位置固定或移动轨迹固定。
在一种可能的实现方法中，处理单元1710，用于当该终端设备对应的去注册定时器超时，根据该卫星覆盖信息确定该终端设备未被卫星网络覆盖，确定不对该终端设备执行去注册。
在第二个实施例中，该通信装置用于执行移动性管理性网元的操作，处理单元1710，用于当终端设备对应的去注册定时器超时，根据该终端设备的卫星覆盖信息，确定该终端设备未被卫星网络覆盖，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；以及响应于该终端设备未被卫星网络覆盖，确定不对该终端设备执行去注册或去附着。
在一种可能的实现方法中，收发单元1720，用于向该终端设备发送第一信息，该第一信息指示该终端设备有上行传输需求时根据卫星网络覆盖情况进行上行传输。
在一种可能的实现方法中，该第一信息是该卫星覆盖信息；该第一信息具体用于指示该终端设备有上行传输需求时根据该卫星覆盖信息发起上行传输。
在一种可能的实现方法中，收发单元1720，用于向该终端设备发送该卫星覆盖信息；该第一信息具体用于指示该终端设备有上行传输需求时根据该卫星覆盖信息发起上行传输。
在一种可能的实现方法中，该上行传输需求包括周期性TAU、周期性注册或上行数据传输中的一个或多个。
在一种可能的实现方法中，处理单元1710，用于通过收发单元1720接收该卫星覆盖信息；或者，通过收发单元1720接收该终端设备所在的卫星小区的星历信息，并根据该星历信息确定该卫星覆盖信息。
在一种可能的实现方法中，处理单元1710，用于确定该终端设备的位置固定或移动轨迹固定。
在第三个实施例中，该通信装置用于执行移动性管理性网元的操作，处理单元1710，用于确定终端设备的卫星覆盖信息，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；以及根据该卫星覆盖信息，确定最大等待时间，该最大等待时间指示等待该终端设备可达的最大时长。
在一种可能的实现方法中，处理单元1710，用于根据该卫星覆盖信息，确定该终端设备不可达。
在一种可能的实现方法中，处理单元1710，用于通过收发单元1720接收该卫星覆盖信息。
在一种可能的实现方法中，处理单元1710，用于通过收发单元1720接收该终端设备所在的卫星小区的星历信息；根据该星历信息，确定该卫星覆盖信息。
在一种可能的实现方法中，处理单元1710，用于通过收发单元1720向接入网设备发送寻呼消息，该寻呼消息包括该终端设备的标识信息，该寻呼消息指示寻呼该终端设备；通过收发单元1720接收来自该接入网设备的第一消息，该第一消息包括寻呼失败指示和终端设备的卫星覆盖信息，该寻呼失败指示用于指示此次寻呼失败原因为终端设备未被卫星网络覆盖，可选的，寻呼失败指示还指示需移动管理网元根据该卫星覆盖信息进行可达性判断/寻呼。
在一种可能的实现方法中，处理单元1710，用于确定该终端设备的位置固定或移动轨迹固定。
在第四个实施例中，该通信装置用于执行终端设备的操作，收发单元1720，用于接收第一信息，该第一信息指示终端设备有上行传输需求时根据卫星网络覆盖情况进行上行传输；处理单元1710，用于当有上行传输需求，根据该第一信息，确定该终端设备未被卫星网络覆盖，则确定不进行上行传输。
在一种可能的实现方法中，该第一信息是卫星覆盖信息，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；该第一信息具体用于指示该终端设备有上行传输需求时根据该卫星覆盖信息发起上行传输。
在一种可能的实现方法中，处理单元1710，用于通过收发单元1720接收卫星覆盖信息，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；该第一信息具体用于指示该终端设备有上行传输需求时根据该卫星覆盖信息发起上行传输。
在一种可能的实现方法中，该上行传输需求包括周期性TAU、周期性注册或上行数据传输中的一个或多个。
在第五个实施例中，该通信装置用于执行终端设备的操作，收发单元1720，用于接收休眠时间信息，该休眠时间信息对应的休眠时间段包括终端设备未被卫星网络覆盖的时间段，该休眠时间信息是根据该终端设备的卫星覆盖信息确定的，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；处理单元1710，用于根据该休眠时间信息，进行休眠。
在一种可能的实现方法中，该休眠时间信息包括休眠开始时间，该休眠开始时间位于该终端设备的eDRX周期、该终端设备的周期性TAU周期或该终端设备的周期性注册周 期内。
在一种可能的实现方法中，该休眠时间信息包括休眠开始时间和休眠结束时间；或者，该休眠时间信息包括休眠开始时间和休眠时长。
在第六个实施例中，该通信装置用于执行接入网设备的操作，处理单元1710，用于获取卫星小区的卫星覆盖信息或星历信息，该卫星覆盖信息指示该卫星小区被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；收发单元1720，用于向移动性管理网元发送该卫星小区的卫星覆盖信息或星历信息。
在一种可能的实现方法中，收发单元1720，用于在N2接口建立流程中，向该移动性管理网元发送接入网设备的卫星小区对应的卫星覆盖信息或星历信息。
在一种可能的实现方法中，收发单元1720，用于在该终端设备的注册流程中，向该移动性管理网元发送终端设备所在的卫星小区的卫星覆盖信息或星历信息。
在一种可能的实现方法中，收发单元1720，用于接收来自该移动性管理网元的寻呼消息，该寻呼消息包括终端设备的标识信息，该寻呼消息指示寻呼该终端设备；处理单元1710，用于根据该终端设备所在的卫星小区的卫星覆盖信息，确定该终端设备不可达，通过收发单元1720向该移动性管理网元发送第一消息，该第一消息包括寻呼失败指示和终端设备的卫星覆盖信息，该寻呼失败指示用于指示此次寻呼失败原因为终端设备未被卫星网络覆盖，可选的，寻呼失败指示还指示需移动管理网元根据该卫星覆盖信息进行可达性判断/寻呼。
在第七个实施例中，该通信装置用于执行移动性管理性网元的操作，处理单元1710，用于根据终端设备的卫星覆盖信息确定该终端设备的周期性TAU周期；收发单元1720，用于向该终端设备发送该周期性TAU周期；或者，处理单元1710，用于根据终端设备的卫星覆盖信息确定该终端设备的周期性注册周期；收发单元1720，用于向该终端设备发送该周期性注册周期；其中，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段。
在一种可能的实现方法中，该周期性TAU周期对应的时间段包含该终端设备未被卫星网络覆盖的时间段；或者，该周期性注册周期对应的时间段包含该终端设备未被卫星网络覆盖的时间段。
在一种可能的实现方法中，处理单元1710，还用于根据该卫星覆盖信息，通过收发单元1720向接入网设备发送指示信息，该指示信息指示该接入网设备执行该终端设备释放流程。
在一种可能的实现方法中，处理单元1710，用于根据该终端设备的卫星覆盖信息，确定第一时长，该第一时长为所述终端设备进入空闲态后、进入休眠态之前的时长；收发单元1720，用于向该终端设备发送第一时长。
在一种可能的实现方法中，收发单元1720，还用于向该终端设备发送原因值，该原因值为卫星非连续覆盖。
在一种可能的实现方法中，该原因值还用于指示该终端设备在休眠期间不进行上行传输。
在一种可能的实现方法中，收发单元1720，用于向该终端设备发送GUTI重分配命令， 该GUTI重分配命令包括该周期性TAU周期；或者，向该终端设备发送TAU接受消息，该TAU接受消息包括该周期性TAU周期。
在一种可能的实现方法中，收发单元1720，用于向该终端设备发送配置更新命令，该配置更新命令包括该周期性注册周期；或者，向该终端设备发送移动注册更新接受消息，该移动注册更新接受消息包括该周期性注册周期。
在第八个实施例中，该通信装置用于执行终端设备的操作，收发单元1720，用于接收来自移动性管理网元的周期性TAU周期；处理单元1710，用于根据该周期性TAU周期执行周期性TAU，该周期性TAU周期对应的时间段包含该终端设备未被卫星网络覆盖的时间段；或者，收发单元1720，用于接收来自移动性管理网元的周期性注册周期；处理单元1710，用于根据该周期性注册周期执行周期性注册，该周期性注册周期对应的时间段包含该终端设备未被卫星网络覆盖的时间段。
在一种可能的实现方法中，该周期性TAU周期或该周期性注册周期是根据该终端设备的卫星覆盖信息确定的，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段。
在一种可能的实现方法中，处理单元1710，用于在收发单元1720接收来自移动性管理网元的周期性TAU周期之前，根据该终端设备的卫星覆盖信息，通过收发单元1720向该移动性管理网元发送TAU请求；或者，在收发单元1720接收来自移动性管理网元的周期性注册周期之前，根据该终端设备的卫星覆盖信息，通过收发单元1720向该移动性管理网元发送移动注册更新请求；其中，该卫星覆盖信息指示该终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段。
在一种可能的实现方法中，收发单元1720，还用于接收来自该移动性管理网元的第一时长，该第一时长为该终端设备进入空闲态后、进入休眠态之前的时长，第一时长是根据终端设备的卫星覆盖信息确定的。
在一种可能的实现方法中，收发单元1720，用于接收来自该移动性管理网元的原因值，该原因值为卫星非连续覆盖。
在一种可能的实现方法中，该原因值还用于指示该终端设备在休眠期间不进行上行传输；当有上行传输需求，根据该原因值，确定不进行上行传输。
在第九个实施例中，该通信装置用于执行接入网设备的操作，处理单元1710，用于根据终端设备的卫星覆盖信息，通过收发单元1720向移动性管理网元发送上下文释放请求，所述上下文释放请求用于请求所述移动性管理网元释放所述终端设备的上下文，所述卫星覆盖信息指示所述终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；收发单元1720，还用于接收来自所述移动性管理网元的周期性TAU周期，并向所述终端设备发送所述周期性TAU周期，所述周期性TAU周期对应的时间段包含所述终端设备未被卫星网络覆盖的时间段；或者，收发单元1720，还用于接收来自所述移动性管理网元的周期性注册周期，并向所述终端设备发送所述周期性注册周期，所述周期性注册周期对应的时间段包含所述终端设备未被卫星网络覆盖的时间段。
有关上述处理单元1710和收发单元1720更详细的描述可以直接参考上述方法实施例中相关描述直接得到，这里不加赘述。
如图18所示，通信装置1800包括处理器1810，可选的，通信装置1800还可以还包括接口电路1820。处理器1810和接口电路1820之间相互耦合。可以理解的是，接口电路1820可以为收发器或输入输出接口。可选的，通信装置1800还可以包括存储器1830，用于存储处理器1810执行的指令或存储处理器1810运行指令所需要的输入数据或存储处理器1810运行指令后产生的数据。
当通信装置1800用于实现上述方法实施例时，处理器1810用于实现上述处理单元1710的功能，接口电路1820用于实现上述收发单元1720的功能。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器、闪存、只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于基站或终端中。当然，处理器和存储介质也可以作为分立组件存在于基站或终端中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、基站、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘；还可以是半导体介质，例如，固态硬盘。该计算机可读存储介质可以是易失性或非易失性存储介质，或可包括易失性和非易失性两种类型的存储介质。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式 中，字符“/”，表示前后关联对象是一种“相除”的关系。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。

Claims (34)

  1. 一种通信方法，其特征在于，包括：
    根据终端设备的卫星覆盖信息，确定所述终端设备的休眠时间信息，所述卫星覆盖信息指示所述终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段，所述休眠时间信息对应的休眠时间段包括所述终端设备未被卫星网络覆盖的时间段；
    向所述终端设备发送所述休眠时间信息。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    根据所述卫星覆盖信息，确定所述终端设备的扩展非连续接收eDRX周期、周期性跟踪区域更新TAU周期或周期性注册周期中的一个或多个；
    其中，所述休眠时间信息包括休眠开始时间，所述休眠开始时间位于所述eDRX周期内、所述周期性TAU周期内或所述周期性注册周期内。
  3. 如权利要求1所述的方法，其特征在于，
    所述休眠时间信息包括休眠开始时间和休眠结束时间；或者，
    所述休眠时间信息包括休眠开始时间和休眠时长。
  4. 如权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    接收所述卫星覆盖信息；或者，
    接收所述终端设备所在的卫星小区的星历信息，并根据所述星历信息确定所述卫星覆盖信息。
  5. 如权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    当所述终端设备对应的去注册定时器超时，根据所述卫星覆盖信息确定所述终端设备未被卫星网络覆盖，确定不对所述终端设备执行去注册。
  6. 一种通信方法，其特征在于，包括：
    当终端设备对应的去注册定时器超时，根据所述终端设备的卫星覆盖信息，确定所述终端设备未被卫星网络覆盖，所述卫星覆盖信息指示所述终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；
    响应于所述终端设备未被卫星网络覆盖，确定不对所述终端设备执行去注册。
  7. 如权利要求6所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送第一信息，所述第一信息指示所述终端设备有上行传输需求时根据卫星网络覆盖情况进行上行传输。
  8. 如权利要求7所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送所述卫星覆盖信息；
    所述第一信息具体用于指示所述终端设备有上行传输需求时根据所述卫星覆盖信息发起上行传输。
  9. 如权利要求6至8中任一项所述的方法，其特征在于，所述方法还包括：
    接收所述卫星覆盖信息；或者，
    接收所述终端设备所在的卫星小区的星历信息，并根据所述星历信息确定所述卫星覆盖信息。
  10. 一种通信方法，其特征在于，包括：
    确定终端设备的卫星覆盖信息，所述卫星覆盖信息指示所述终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；
    根据所述卫星覆盖信息，确定最大等待时间，所述最大等待时间指示等待所述终端设备可达的最大时长。
  11. 如权利要求10所述的方法，其特征在于，所述方法还包括：
    根据所述卫星覆盖信息，确定所述终端设备不可达。
  12. 如权利要求10或11所述的方法，其特征在于，所述确定终端设备的卫星覆盖信息，包括：
    接收所述卫星覆盖信息。
  13. 如权利要求10或11所述的方法，其特征在于，所述确定终端设备的卫星覆盖信息，包括：
    接收所述终端设备所在的卫星小区的星历信息；
    根据所述星历信息，确定所述卫星覆盖信息。
  14. 一种通信方法，其特征在于，包括：
    接收第一信息，所述第一信息指示终端设备有上行传输需求时根据卫星网络覆盖情况进行上行传输；
    当有上行传输需求，根据所述第一信息，确定所述终端设备未被卫星网络覆盖，则确定不进行上行传输。
  15. 如权利要求14所述的方法，其特征在于，所述第一信息是卫星覆盖信息，所述卫星覆盖信息指示所述终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；
    所述第一信息具体用于指示所述终端设备有上行传输需求时根据所述卫星覆盖信息发起上行传输。
  16. 如权利要求14所述的方法，其特征在于，所述方法还包括：
    接收卫星覆盖信息，所述卫星覆盖信息指示所述终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；
    所述第一信息具体用于指示所述终端设备有上行传输需求时根据所述卫星覆盖信息发起上行传输。
  17. 如权利要求14至16中任一项所述的方法，其特征在于，所述上行传输需求包括周期性TAU、周期性注册或上行数据传输中的一个或多个。
  18. 一种通信方法，其特征在于，包括：
    接收休眠时间信息，所述休眠时间信息对应的休眠时间段包括终端设备未被卫星网络覆盖的时间段，所述休眠时间信息是根据所述终端设备的卫星覆盖信息确定的，所述卫星覆盖信息指示所述终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段；
    根据所述休眠时间信息，进行休眠。
  19. 如权利要求18所述的方法，其特征在于，
    所述休眠时间信息包括休眠开始时间，所述休眠开始时间位于所述终端设备的eDRX周期内、所述终端设备的周期性TAU周期内或所述终端设备的周期性注册周期内。
  20. 如权利要求18所述的方法，其特征在于，
    所述休眠时间信息包括休眠开始时间和休眠结束时间；或者，
    所述休眠时间信息包括休眠开始时间和休眠时长。
  21. 一种通信方法，其特征在于，包括：
    根据终端设备的卫星覆盖信息确定所述终端设备的周期性跟踪区域更新TAU周期，并向所述终端设备发送所述周期性TAU周期；或者，
    根据终端设备的卫星覆盖信息确定所述终端设备的周期性注册周期，并向所述终端设备发送所述周期性注册周期；
    其中，所述卫星覆盖信息指示所述终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段。
  22. 如权利要求21所述的方法，其特征在于，所述周期性TAU周期对应的时间段包含所述终端设备未被卫星网络覆盖的时间段；或者，
    所述周期性注册周期对应的时间段包含所述终端设备未被卫星网络覆盖的时间段。
  23. 如权利要求21或22所述的方法，其特征在于，所述方法还包括：
    根据所述卫星覆盖信息，向接入网设备发送指示信息，所述指示信息指示所述接入网设备执行所述终端设备释放流程。
  24. 如权利要求21至23中任一项所述的方法，其特征在于，所述方法还包括：
    根据所述终端设备的卫星覆盖信息，确定第一时长，所述第一时长为所述终端设备进入空闲态后、进入休眠态之前的时长；
    向所述终端设备发送所述第一时长。
  25. 如权利要求21至24中任一项所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送原因值，所述原因值用于指示所述终端设备在休眠期间不进行上行传输。
  26. 一种通信方法，其特征在于，包括：
    接收来自移动性管理网元的周期性TAU周期，并根据所述周期性TAU周期执行周期性TAU，所述周期性TAU周期对应的时间段包含所述终端设备未被卫星网络覆盖的时间段；或者，
    接收来自移动性管理网元的周期性注册周期，并根据所述周期性注册周期执行周期性注册，所述周期性注册周期对应的时间段包含所述终端设备未被卫星网络覆盖的时间段。
  27. 如权利要求26所述的方法，其特征在于，所述周期性TAU周期或所述周期性注册周期是根据所述终端设备的卫星覆盖信息确定的，所述卫星覆盖信息指示所述终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段。
  28. 如权利要求26或27所述的方法，其特征在于，所述接收来自移动性管理网元的周期性TAU周期之前，还包括：
    根据所述终端设备的卫星覆盖信息，向所述移动性管理网元发送TAU请求；或者，
    所述接收来自移动性管理网元的周期性注册周期之前，还包括：
    根据所述终端设备的卫星覆盖信息，向所述移动性管理网元发送移动注册更新请求；
    其中，所述卫星覆盖信息指示所述终端设备被卫星网络覆盖的时间段和/或未被卫星网络覆盖的时间段。
  29. 如权利要求26至28中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述移动性管理网元的第一时长，所述第一时长为所述终端设备进入空闲态后、进入休眠态之前的时长，所述第一时长是根据所述终端设备的卫星覆盖信息确定的。
  30. 如权利要求26至29中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述移动性管理网元的原因值，所述原因值为卫星非连续覆盖。
  31. 如权利要求30所述的方法，其特征在于，所述原因值还用于指示所述终端设备在休眠期间不进行上行传输；
    所述方法还包括：
    当有上行传输需求，根据所述原因值，确定不进行上行传输。
  32. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至13、21至25中任一项所述的方法，或用于实现如权利要求14至20、26至31中任一项所述的方法。
  33. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至31中任一项所述的方法。
  34. 一种通信系统，其特征在于，包括：
    移动性管理网元，用于执行如权利要求1至13中任一项所述的方法；
    接入网设备，用于向所述移动性管理网元发送终端设备所在小区的卫星覆盖信息。
PCT/CN2022/120600 2021-10-10 2022-09-22 一种通信方法、通信装置及通信系统 Ceased WO2023056843A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
AU2022360194A AU2022360194B2 (en) 2021-10-10 2022-09-22 Communication method, communication apparatus and communication system
EP22877862.7A EP4391657A4 (en) 2021-10-10 2022-09-22 COMMUNICATION METHOD, COMMUNICATION APPARATUS AND COMMUNICATION SYSTEM
JP2024521270A JP7704972B2 (ja) 2021-10-10 2022-09-22 通信方法、通信装置、および通信システム
CA3233648A CA3233648A1 (en) 2021-10-10 2022-09-22 Communication method, communication apparatus, and communication system
US18/608,950 US20240224217A1 (en) 2021-10-10 2024-03-19 Communication method, communication apparatus, and communication system
JP2025108103A JP2025143332A (ja) 2021-10-10 2025-06-26 通信方法、通信装置、および通信システム
AU2025213602A AU2025213602A1 (en) 2021-10-10 2025-08-06 Communication method, communication apparatus and communication system

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202111178674 2021-10-10
CN202111178674.7 2021-10-10
CN202111308873.5 2021-11-05
CN202111308873.5A CN115968017A (zh) 2021-10-10 2021-11-05 一种通信方法、通信装置及通信系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/608,950 Continuation US20240224217A1 (en) 2021-10-10 2024-03-19 Communication method, communication apparatus, and communication system

Publications (1)

Publication Number Publication Date
WO2023056843A1 true WO2023056843A1 (zh) 2023-04-13

Family

ID=85803892

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/120600 Ceased WO2023056843A1 (zh) 2021-10-10 2022-09-22 一种通信方法、通信装置及通信系统

Country Status (7)

Country Link
US (1) US20240224217A1 (zh)
EP (1) EP4391657A4 (zh)
JP (2) JP7704972B2 (zh)
CN (2) CN117241355A (zh)
AU (2) AU2022360194B2 (zh)
CA (1) CA3233648A1 (zh)
WO (1) WO2023056843A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024212253A1 (zh) * 2023-04-14 2024-10-17 北京小米移动软件有限公司 信息处理方法及装置、通信设备及存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12470294B1 (en) * 2023-08-23 2025-11-11 Amazon Technologies, Inc. System for inter-satellite communication
CN117981401B (zh) * 2023-12-25 2025-11-18 上海移远通信技术股份有限公司 用于无线通信的方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108700669A (zh) * 2016-02-25 2018-10-23 迈锐奥塔企业有限公司 卫星通信系统中的终端调度方法
CN113114333A (zh) * 2021-03-11 2021-07-13 中国电子科技集团公司第五十四研究所 一种同步轨道卫星移动通信终端快速入网方法及装置
CN113411810A (zh) * 2021-05-24 2021-09-17 广东省大湾区集成电路与系统应用研究院 天基物联网通信系统
WO2021196769A1 (zh) * 2020-04-02 2021-10-07 海能达通信股份有限公司 一种切换方法及终端、基站

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6418314B2 (en) * 1998-05-01 2002-07-09 Ericsson Inc. Methods for determining registration at a satellite communications system and related user terminals and systems
US11641564B2 (en) * 2019-08-16 2023-05-02 Ofinno, Llc Flexible zone-based registration area tracking in a wireless network
EP3787352B1 (en) 2019-08-29 2023-05-31 Nokia Technologies Oy Method for user equipment's registration update
US11811488B2 (en) * 2019-11-07 2023-11-07 Qualcomm Incorporated Systems and methods for support of a 5G satellite radio access technology

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108700669A (zh) * 2016-02-25 2018-10-23 迈锐奥塔企业有限公司 卫星通信系统中的终端调度方法
WO2021196769A1 (zh) * 2020-04-02 2021-10-07 海能达通信股份有限公司 一种切换方法及终端、基站
CN113114333A (zh) * 2021-03-11 2021-07-13 中国电子科技集团公司第五十四研究所 一种同步轨道卫星移动通信终端快速入网方法及装置
CN113411810A (zh) * 2021-05-24 2021-09-17 广东省大湾区集成电路与系统应用研究院 天基物联网通信系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024212253A1 (zh) * 2023-04-14 2024-10-17 北京小米移动软件有限公司 信息处理方法及装置、通信设备及存储介质

Also Published As

Publication number Publication date
AU2022360194B2 (en) 2025-05-08
AU2025213602A1 (en) 2025-08-21
JP7704972B2 (ja) 2025-07-08
JP2025143332A (ja) 2025-10-01
CA3233648A1 (en) 2023-04-13
CN117336831A (zh) 2024-01-02
JP2024538744A (ja) 2024-10-23
CN117241355A (zh) 2023-12-15
EP4391657A4 (en) 2025-01-08
US20240224217A1 (en) 2024-07-04
EP4391657A1 (en) 2024-06-26
AU2022360194A1 (en) 2024-03-28

Similar Documents

Publication Publication Date Title
CN115968017A (zh) 一种通信方法、通信装置及通信系统
US11825437B2 (en) Mobility signaling load reduction
US11083039B2 (en) Mobile network optimization processing method, device, and system
JP7111164B2 (ja) Ｒｒｃインアクティブ状態の最適化
WO2023056843A1 (zh) 一种通信方法、通信装置及通信系统
TW201215064A (en) Application layer protocol support for sleeping nodes in constrained networks
KR101745812B1 (ko) 불연속 수신(drx) 사이클의 적용
CN1836407B (zh) 在无线网络中请求和准许更短的时隙周期
WO2022053003A1 (zh) 一种rrc连接释放的方法及装置
WO2023213204A1 (zh) 通信方法和装置
WO2023087151A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2023087147A1 (zh) 信息处理方法及装置、通信设备及存储介质
WO2023213149A1 (zh) 通信方法和装置
WO2022206945A1 (zh) 一种通信方法、装置及系统
CN113950146B (zh) 一种寻呼方法和通信装置
WO2014067317A1 (zh) 服务小区子帧配置信息的传递方法及供者基站
US20250365808A1 (en) Paging method and apparatus
KR20190052465A (ko) 페이징 처리 장치 및 방법
WO2025195130A1 (zh) 通信方法、通信装置及通信系统
WO2024164941A1 (zh) 终端的寻呼方法和寻呼装置
CN119485357A (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: 22877862

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022360194

Country of ref document: AU

Ref document number: AU2022360194

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 202427018247

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 809131

Country of ref document: NZ

WWE Wipo information: entry into national phase

Ref document number: 2022877862

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 3233648

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2022360194

Country of ref document: AU

Date of ref document: 20220922

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2022877862

Country of ref document: EP

Effective date: 20240321

ENP Entry into the national phase

Ref document number: 2024521270

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 11202401833T

Country of ref document: SG

NENP Non-entry into the national phase

Ref country code: DE