Tracking area TA management method and device and storage medium
By negotiating the TA list update cycle in the 5G satellite network, the RAN node actively updates or updates the TA list in response to the core network request, solving the problem of TA list inconsistency caused by the movement of the RAN node and achieving synchronization and accuracy of the TA list.
Patent Information
- Application Number
- CN202410031114.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-08
- Publication Date
- 2025-07-08
AI Technical Summary
In a 5G satellite network, the RAN node moves with its location, causing the tracking area list they support to continue to change, resulting in inconsistency between the TA list actually supported by the RAN node and the TA list reported to the core network.
By negotiating the update cycle of the TA list between the core network and the RAN node, the RAN node updates the TA list according to the negotiated update cycle, and actively sends the updated TA list to the core network, or sends the supported TA list when the core network actively requests the supported TA list.
The problem of TA list changing as the RAN node moves is solved, and the inconsistency between the TA list actually supported by the RAN node and the TA list reported to the core network is eliminated.
Smart Images

Figure CN120282124A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technologies, and in particular, to a TA management method, apparatus, and storage medium. Background Art
[0002] In the 5th Generation Mobile Communication Technology (5G) satellite network, it is required that if a satellite provides services in the current area, it needs to connect to the ground core network in the current area and broadcast the Public Land Mobile Network Identification (PLMN ID) of the current area. The above process is easy to implement when the control unit (CU) of the base station gNB, that is, the Radio Access Network (RAN) node, is on the ground. However, once the RAN node is deployed on a non-synchronous satellite as a whole, that is, both the CU and the Data Unit (DU) of the RAN node are on the satellite, the RAN node needs to establish a connection with the ground core network in the area passed by the orbit as it moves, and broadcast air interface broadcasts according to the configuration information sent by the ground core network. Since the satellite flies at a relatively high speed, the Tracking Area (TA) list supported by the RAN node deployed on the satellite will change continuously.
[0003] In the related art, the ground core network can store the ephemeris information of the RAN node, and the ground core network can calculate the TA list through the stored ephemeris information, so as to predict the TA change. However, there is an inconsistency problem between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network. Summary of the Invention
[0004] This application provides a TA management method, apparatus, and storage medium, which solves the technical problem of the inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network.
[0005] In a first aspect, this application provides a TA management method, which is applied to a RAN node. The TA management method includes: receiving first information from a core network, where the first information includes the update period of the TA list and / or second information, and the second information includes indication information for requesting the TA list supported by the RAN node and / or indication information for updating the ephemeris information of the RAN node; sending third information to the core network, where the third information includes the TA list supported by the core network requesting the RAN node.
[0006] In some embodiments, the triggering conditions for sending the third information to the core network include at least one of the following: the expiration of the update period indicated by the core network; the expiration of the pre-configured update period on the RAN node; there is no intersection between the TA list currently supported by the RAN node and the TA list last sent by the RAN node to the core network, and the RAN node is mobile; receiving the second information.
[0007] In some embodiments, when receiving the second information, sending the third information to the core network includes: sending a request for ephemeris information update to the network management or other network elements; receiving the updated ephemeris information from the network management or other network elements; generating the third information according to the updated ephemeris information, and sending the third information to the core network.
[0008] In some embodiments, the third information further includes at least one of the following: the time when the RAN node sends the third information; the valid duration of the TA list requested by the core network for the RAN node to support.
[0009] In some embodiments, when the first information includes the update period of the TA list, after receiving the first information from the core network, it further includes: adjusting the original update period of the RAN node using the received update period; sending a response message indicating the successful adjustment of the update period to the core network.
[0010] In some embodiments, after sending the third information to the core network, it further includes: receiving a response message from the core network indicating the completion of the TA list configuration.
[0011] In some embodiments, the RAN node determines the currently supported TA list in the following ways: obtaining the TA list sent by the network management; and / or calculating the TA list according to the configuration information sent by the network management.
[0012] In a second aspect, the present application provides a TA management method applied to the core network. The TA management method includes: sending the first information to the RAN node, where the first information includes the update period of the TA list and / or the second information, and the second information includes the indication information for requesting the TA list supported by the RAN node and / or the indication information for updating the ephemeris information of the RAN node; receiving the third information from the RAN node, where the third information includes the TA list requested by the core network for the RAN node to support.
[0013] In some embodiments, the third information further includes at least one of the following: the time when the RAN node sends the third information; the valid duration of the TA list requested by the core network for the RAN node to support.
[0014] In some embodiments, before sending the first information to the RAN node, it further includes: receiving fourth information from the RAN node, where the fourth information includes the TA list currently supported by the RAN node; determining the update period of the TA list according to the fourth information.
[0015] In some embodiments, the fourth information further includes at least one of the following: the effective duration of the TA list currently supported by the RAN node; the time when the RAN node sends the fourth information.
[0016] In some embodiments, determining the update period of the TA list according to the fourth information includes: determining the update period of the TA list according to the load information of the core network and / or the RAN node, the energy-saving information of the RAN node, and the fourth information.
[0017] In some embodiments, determining the update period of the TA list according to the fourth information includes: if the core network has stored the ephemeris information of the RAN node, calculating the TA list supported by the RAN node according to the ephemeris information of the RAN node; if the TA list included in the fourth information is consistent with the TA list calculated by the core network according to the stored ephemeris information, determining the update period of the TA list according to the load information, the energy-saving information of the RAN node, the ephemeris information stored in the core network, and the effective duration of the TA list; if the TA list included in the fourth information is inconsistent with the TA list calculated by the core network according to the stored ephemeris information, determining the target TA list; determining the update period of the TA list according to the load information, the energy-saving information of the RAN node, the ephemeris information corresponding to the target TA list, and the effective duration of the target TA list.
[0018] In some embodiments, determining the target TA list includes: obtaining the updated ephemeris information of the RAN node from the network management or other network elements; calculating the target TA list according to the updated ephemeris information; or, determining the TA list calculated by the core network as the target TA list; or, sending the second information to the RAN node; obtaining the updated TA list from the RAN node; determining the updated TA list of the RAN node as the target TA list; or, adjusting the ephemeris information stored in the core network according to the TA list included in the fourth information; calculating the target TA list according to the adjusted ephemeris information.
[0019] In some embodiments, after receiving the third information from the RAN node, it further includes: if the core network has stored the ephemeris information of the RAN node, then according to the ephemeris information of the RAN node, calculate the TA list supported by the RAN node, and perform the following operations: if the TA list calculated by the core network based on the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network obtains the updated ephemeris information of the RAN node from the network management or other network elements, then according to the updated ephemeris information, calculate and store the TA list supported by the RAN node; or, if the TA list calculated by the core network based on the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network sends the second information to the RAN node, then wait for the updated TA list from the RAN node, or store the TA list calculated by the core network based on the stored ephemeris information.
[0020] In some embodiments, it further includes: sending a response message indicating that the TA list configuration is completed to the RAN node.
[0021] In some embodiments, the triggering conditions for receiving the second information include at least one of the following: there is no intersection between the TA list supported by the RAN node calculated by the core network and the TA list last sent by the RAN node to the core network; the valid duration of the TA list stored in the core network expires; the core network needs to notify the RAN node to request updated ephemeris information from the network management or other network elements.
[0022] In a third aspect, the present application provides a TA management device applied to the RAN node. The TA management device includes: a receiving module, configured to receive the first information from the core network, where the first information includes the update period of the TA list and / or the second information, and the second information includes the indication information for requesting the TA list supported by the RAN node and / or the indication information for updating the ephemeris information of the RAN node; a sending module, configured to send the third information to the core network, where the third information includes the TA list supported by the core network requesting the RAN node.
[0023] In some embodiments, the triggering conditions for sending the third information to the core network include at least one of the following: the update period indicated by the core network expires; the pre-configured update period on the RAN node expires; there is no intersection between the currently supported TA list of the RAN node and the TA list last sent by the RAN node to the core network, and the RAN node is mobile; receiving the second information.
[0024] In some embodiments, when receiving the second information, when the sending module sends the third information to the core network, it is specifically configured to: send an ephemeris information update request to the network management or other network elements; receive the updated ephemeris information from the network management or other network elements; generate the third information according to the updated ephemeris information, and send the third information to the core network.
[0025] In some embodiments, the third information further includes at least one of the following: the time when the RAN node sends the third information; the valid duration of the TA list requested by the core network for the RAN node to support.
[0026] In some embodiments, when the first information includes the update period of the TA list, it further includes: a processing module, configured to, after receiving the first information from the core network, use the received update period to adjust the original update period of the RAN node; and send a response message indicating successful update period adjustment to the core network.
[0027] In some embodiments, the receiving module is further configured to, after sending the third information to the core network, receive a response message indicating that the TA list configuration by the core network is completed.
[0028] In some embodiments, the RAN node determines the currently supported TA list in the following manner: obtaining the TA list sent by the network management; and / or calculating the TA list according to the configuration information sent by the network management.
[0029] In a fourth aspect, the present application provides a TA management device, which is applied to a core network. The TA management device includes: a sending module, configured to send first information to the RAN node, where the first information includes the update period of the TA list and / or second information, and the second information includes indication information for requesting the TA list supported by the RAN node and / or indication information for updating the ephemeris information of the RAN node; a receiving module, configured to receive third information from the RAN node, where the third information includes the TA list requested by the core network for the RAN node to support.
[0030] In some embodiments, the third information further includes at least one of the following: the time when the RAN node sends the third information; the valid duration of the TA list requested by the core network for the RAN node to support.
[0031] In some embodiments, it further includes: a processing module, configured to, before sending the first information to the RAN node, receive fourth information from the RAN node, where the fourth information includes the TA list currently supported by the RAN node; and determine the update period of the TA list according to the fourth information.
[0032] In some embodiments, the fourth information further includes at least one of the following: the valid duration of the TA list currently supported by the RAN node; the time when the RAN node sends the fourth information.
[0033] In some embodiments, when the processing module determines the update period of the TA list according to the fourth information, it is specifically configured to: determine the update period of the TA list according to the load information of the core network and / or the RAN node, the energy saving information of the RAN node, and the fourth information.
[0034] In some embodiments, when determining the update period of the TA list according to the fourth information, the processing module is specifically configured to: if the core network has stored the ephemeris information of the RAN node, calculate the TA list supported by the RAN node according to the ephemeris information of the RAN node; if the TA list included in the fourth information is consistent with the TA list calculated by the core network according to the stored ephemeris information, determine the update period of the TA list according to the load information, the energy-saving information of the RAN node, the ephemeris information stored in the core network, and the valid duration of the TA list; if the TA list included in the fourth information is inconsistent with the TA list calculated by the core network according to the stored ephemeris information, determine the target TA list; and determine the update period of the TA list according to the load information, the energy-saving information of the RAN node, the ephemeris information corresponding to the target TA list, and the valid duration of the target TA list.
[0035] In some embodiments, when determining the target TA list, the processing module is specifically configured to: obtain the updated ephemeris information of the RAN node from the network management or other network elements; calculate the target TA list according to the updated ephemeris information; or, determine the TA list calculated by the core network as the target TA list; or, send the second information to the RAN node; obtain the updated TA list from the RAN node; and determine the updated TA list of the RAN node as the target TA list; or, adjust the ephemeris information stored in the core network according to the TA list included in the fourth information; and calculate the target TA list according to the adjusted ephemeris information.
[0036] In some embodiments, after receiving the third information from the RAN node, the processing module is further configured to, if the core network has stored the ephemeris information of the RAN node, calculate the TA list supported by the RAN node according to the ephemeris information of the RAN node, and perform the following operations: if the TA list calculated by the core network according to the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network obtains the updated ephemeris information of the RAN node from the network management or other network elements, calculate and store the TA list supported by the RAN node according to the updated ephemeris information; or, if the TA list calculated by the core network according to the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network sends the second information to the RAN node, wait for the updated TA list from the RAN node, or store the TA list calculated by the core network according to the stored ephemeris information.
[0037] In some embodiments, the sending module is further configured to send a response message indicating that the TA list configuration is completed to the RAN node.
[0038] In some embodiments, the triggering conditions for receiving the second information include at least one of the following: there is no intersection between the TA list supported by the RAN node calculated by the core network and the TA list last sent by the RAN node to the core network; the valid duration of the TA list stored in the core network expires; the core network needs to notify the RAN node to request updated ephemeris information from the network management or other network elements.
[0039] In a fifth aspect, the present application further provides a TA management device, including: a memory, a transceiver, and a processor: the memory is used to store computer programs; the transceiver is used to transmit and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations: receive first information from the core network, the first information includes the update period of the TA list and / or second information, the second information includes indication information for requesting the TA list supported by the RAN node and / or indication information for updating the ephemeris information of the RAN node; send third information to the core network, the third information includes the TA list supported by the core network requesting the RAN node.
[0040] In some embodiments, the triggering conditions for sending the third information to the core network include at least one of the following: the update period indicated by the core network expires; the pre-configured update period on the RAN node expires; there is no intersection between the TA list currently supported by the RAN node and the TA list last sent by the RAN node to the core network, and the RAN node is mobile; the second information is received.
[0041] In some embodiments, when the second information is received, sending the third information to the core network includes: sending an ephemeris information update request to the network management or other network elements; receiving the updated ephemeris information from the network management or other network elements; generating the third information according to the updated ephemeris information, and sending the third information to the core network.
[0042] In some embodiments, the third information further includes at least one of the following: the time when the RAN node sends the third information; the valid duration of the TA list supported by the core network requesting the RAN node.
[0043] In some embodiments, when the first information includes the update period of the TA list, after receiving the first information from the core network, it further includes: adjusting the original update period of the RAN node using the received update period; sending a response message indicating successful update period adjustment to the core network.
[0044] In some embodiments, after sending the third information to the core network, it further includes: receiving a response message indicating that the TA list configuration by the core network is completed.
[0045] In some embodiments, the RAN node determines the currently supported TA list in the following manner: obtaining the TA list sent by the network management; and / or calculating the TA list according to the configuration information sent by the network management.
[0046] In a sixth aspect, the present application further provides a TA management device, including: a memory, a transceiver, and a processor: the memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: sending a first piece of information to the RAN node, the first piece of information including the update period of the TA list and / or a second piece of information, the second piece of information including an indication information for requesting the TA list supported by the RAN node and / or an indication information for updating the ephemeris information of the RAN node; receiving a third piece of information from the RAN node, the third piece of information including the TA list supported by the core network requesting the RAN node.
[0047] In some embodiments, the third piece of information further includes at least one of the following: the time when the RAN node sends the third piece of information; the valid duration of the TA list supported by the core network requesting the RAN node.
[0048] In some embodiments, before sending the first piece of information to the RAN node, it further includes: receiving a fourth piece of information from the RAN node, the fourth piece of information including the TA list currently supported by the RAN node; determining the update period of the TA list according to the fourth piece of information.
[0049] In some embodiments, the fourth piece of information further includes at least one of the following: the valid duration of the TA list currently supported by the RAN node; the time when the RAN node sends the fourth piece of information.
[0050] In some embodiments, determining the update period of the TA list according to the fourth piece of information includes: determining the update period of the TA list according to the load information of the core network and / or the RAN node, the energy-saving information of the RAN node, and the fourth piece of information.
[0051] In some embodiments, determining the update period of the TA list according to the fourth piece of information includes: if the core network has stored the ephemeris information of the RAN node, calculating the TA list supported by the RAN node according to the ephemeris information of the RAN node; if the TA list included in the fourth piece of information is consistent with the TA list calculated by the core network according to the stored ephemeris information, determining the update period of the TA list according to the load information, the energy-saving information of the RAN node, the ephemeris information stored by the core network, and the valid duration of the TA list; if the TA list included in the fourth piece of information is inconsistent with the TA list calculated by the core network according to the stored ephemeris information, determining the target TA list; determining the update period of the TA list according to the load information, the energy-saving information of the RAN node, the ephemeris information corresponding to the target TA list, and the valid duration of the target TA list.
[0052] In some embodiments, determining the target TA list includes: obtaining updated ephemeris information of the RAN node from the network management system or other network elements; calculating the target TA list according to the updated ephemeris information; or determining the TA list calculated by the core network as the target TA list; or sending second information to the RAN node; obtaining the updated TA list from the RAN node; determining the updated TA list of the RAN node as the target TA list; or adjusting the ephemeris information stored in the core network according to the TA list included in the fourth information; and calculating the target TA list according to the adjusted ephemeris information.
[0053] In some embodiments, after receiving the third information from the RAN node, it further includes: if the core network has stored the ephemeris information of the RAN node, calculating the TA list supported by the RAN node according to the ephemeris information of the RAN node, and performing the following operations: if the TA list calculated by the core network according to the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network obtains the updated ephemeris information of the RAN node from the network management system or other network elements, calculating and storing the TA list supported by the RAN node according to the updated ephemeris information; or if the TA list calculated by the core network according to the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network sends the second information to the RAN node, waiting for the updated TA list from the RAN node, or storing the TA list calculated by the core network according to the stored ephemeris information.
[0054] In some embodiments, it further includes: sending a response message indicating that the TA list configuration is completed to the RAN node.
[0055] In some embodiments, the triggering conditions for receiving the second information include at least one of the following: there is no intersection between the TA list supported by the RAN node calculated by the core network and the TA list last sent by the RAN node to the core network; the valid duration of the TA list stored in the core network expires; the core network needs to notify the RAN node to request updated ephemeris information from the network management system or other network elements.
[0056] In a seventh aspect, the present application further provides a processor-readable storage medium storing a computer program for causing a processor to execute the above TA management method.
[0057] The TA management method, device, equipment, and storage medium provided by this application. The TA management method includes: receiving first information from the core network, where the first information includes the update period of the TA list and / or second information, and the second information includes indication information for requesting the TA list supported by the RAN node and / or indication information for updating the ephemeris information of the RAN node; sending third information to the core network, where the third information includes the TA list supported by the core network's request for the RAN node. In this application, during the process of establishing an interface between the core network and the RAN node, the update period of the TA list can be negotiated. The RAN node updates the TA list according to the negotiated update period, and can actively send the updated TA list to the core network, or send the supported TA list to the core network when the core network actively requests the supported TA list. This can not only solve the problem that the TA list changes as the RAN node moves, but also solve the problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network, and can also solve the problem of inconsistency between the TA list calculated by the core network based on the stored ephemeris information and the TA list sent by the RAN node.
[0058] It should be understood that the content described in the above-mentioned invention content section is not intended to limit the key or important features of the embodiments of the present invention, nor is it used to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. Brief Description of the Drawings
[0059] In order to more clearly illustrate the technical solutions in this application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.
[0060] Figure 1 It is a schematic flowchart of a TA management method provided by an embodiment of this application;
[0061] Figure 2 It is a schematic flowchart of a RAN node sending third information to the core network provided by an embodiment of this application;
[0062] Figure 3 It is a schematic flowchart of a RAN node adjusting the update period provided by an embodiment of this application;
[0063] Figure 4 It is a schematic diagram of a regenerative satellite access architecture provided by an embodiment of this application;
[0064] Figure 5Schematic flowchart of another TA management method provided by an embodiment of the present application;
[0065] Figure 6 Schematic structural diagram of a TA management device provided by an embodiment of the present application;
[0066] Figure 7 Schematic structural diagram of another TA management device provided by an embodiment of the present application;
[0067] Figure 8 Schematic structural diagram of a TA management device provided by an embodiment of the present application;
[0068] Figure 9 Schematic structural diagram of another TA management device provided by an embodiment of the present application. Detailed implementation manners
[0069] In the embodiments of the present invention, the term "and / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.
[0070] In the embodiments of the present application, the term "plurality" refers to two or more, and other quantifiers are similar.
[0071] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.
[0072] The inventors found in the research that in the 5G satellite network, it is required that if a satellite provides services in the current area, it needs to connect to the ground core network in the current area and broadcast the PLMN ID of the current area. The above process is easy to implement when the CU of the base station gNB, that is, the RAN node, is on the ground. However, once the RAN node is deployed on a non-synchronous satellite as a whole, that is, both the CU and DU of the RAN node are on the satellite, the RAN node needs to establish a connection with the ground core network in the area passed by the orbit as it moves, and broadcast the air interface broadcast according to the configuration information sent by the ground core network. Since the satellite flies at a relatively high speed, the TA list supported by the RAN node deployed on the satellite will change continuously. Therefore, a method for managing the TA list supported by the RAN node is required.
[0073] In the process of establishing an interface between a RAN node and the core network, the interface establishment request sent by the RAN node to the core network must include the TA list supported by the RAN node. Moreover, in the process of the RAN node initiating configuration update, the RAN node must send the supported TA list to the core network. However, since the RAN node does not have a mechanism to update the TA list periodically and the core network cannot actively request the supported TA list from the RAN node, there is easily a problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network.
[0074] The embodiments of the present application provide a TA management method, apparatus, device, and storage medium. In the process of establishing an interface between the core network and the RAN node, the update period of the TA list can be negotiated. The RAN node updates the TA list according to the negotiated update period. The RAN node can actively send the updated TA list to the core network, or when the core network actively requests the supported TA list, the RAN node sends the supported TA list to the core network. Therefore, the technical solution provided by the present application can not only solve the problem that the TA list changes as the RAN node moves, but also solve the problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network.
[0075] Among them, the method and the apparatus are based on the same inventive concept. Since the principles of solving problems by the method and the apparatus are similar, the embodiments of the apparatus and the method can be referred to each other, and the repeated parts will not be elaborated.
[0076] The technical solutions provided by the embodiments of the present application can be applicable to a variety of systems. For example, the applicable systems can be Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5G New Radio (NR) systems and their evolved communication systems, etc. These various systems may include terminal devices and network devices. The systems may also include a core network part, such as an Evolved Packet System (EPS), 5G System (5GS), etc.
[0077] The terminal device involved in the embodiments of the present application can be a device that provides voice and / or data connectivity to users, such as a handheld device with wireless connection capabilities, or other processing devices connected to a wireless modem, etc. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device can be called a user equipment (UE for short). The wireless terminal device can be a USB storage device, other personal computer memory devices, and dongles, and can also communicate with one or more core networks (CN for short) via the RAN. The wireless terminal device can be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it can be a portable, pocket-sized, handheld, computer-integrated, or vehicle-mounted mobile device that exchanges language and / or data with the radio access network. For example, personal communication service (PCS) phones, cordless phones, session initiated protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDA), personal computers, tablets, machine-type communication (MTC) terminal devices, etc. The wireless terminal device can also be called a system, subscriber unit, subscriber station, mobile station, mobile, remote station, access point, remote terminal, access terminal, user terminal, user agent, user device, and wireless access points and routers / modems that meet the limitations of this definition, etc., which are not limited in the embodiments of the present application.
[0078] The network device involved in the embodiments of the present application can be a base station, which can include multiple cells that provide services to terminals. Depending on the specific application scenarios, the base station can also be referred to as an access point, or can be a device in the access network that communicates with wireless terminal devices through one or more sectors over the air interface, or other names. The network device can be used to mutually replace the received air frames and Internet Protocol (IP) packets, and act as a router between the wireless terminal device and the rest of the access network, where the rest of the access network can include an IP communication network. The network device can also coordinate the management of the attributes of the air interface. For example, the network device involved in the embodiments of the present application can be an evolved network device (evolutional Node B, abbreviated as eNB or e-NodeB) in a Long Term Evolution (LTE) system, a 5G base station (gNB) in a 5G network architecture (next generation system), etc., or can also be a Home evolved Node B (HeNB), a relay node, a femto, a pico, a network test device, etc. The embodiments of the present application do not limit this. In some network architectures, the network device can include a CU node and a DU node, and the CU node and the DU node can also be geographically separated.
[0079] The network device and the terminal device can each use one or more antennas for multi-input multi-output (MIMO) transmission. The MIMO transmission can be single-user MIMO or multi-user MIMO. Depending on the form and quantity of the antenna combination, the MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, or can also be diversity transmission, precoding transmission, beamforming transmission, etc.
[0080] In the embodiments of the present application, the terminal device sends relevant information or similar descriptions to the network-side device, which only indicates that the relevant information is sent in the form of a wireless signal, and its intended recipient is the network device. The network device can obtain the relevant information by receiving the wireless signal.
[0081] In some embodiments, a TA management method is provided, which is applied to a RAN node. Figure 1 It is a schematic flowchart of a TA management method provided by the embodiments of the present application. As Figure 1 shown, the method mainly includes the following steps:
[0082] S101: Receive the first information from the core network.
[0083] In this step, the first information includes the update period of the TA list and / or the second information, and the second information includes the indication information for requesting the TA list supported by the RAN node and / or the indication information for updating the ephemeris information of the RAN node.
[0084] Specifically, the core network determines the update period of the TA list, and the RAN node can update the TA list periodically according to the received update period. If the core network sends the second information to the RAN node, the core network actively requests the TA list supported by the RAN node, and the RAN node updates the TA list according to the second information sent by the core network.
[0085] S102: Send the third information to the core network.
[0086] In this step, the third information includes the TA list supported by the core network requesting the RAN node.
[0087] Specifically, after the RAN node updates the TA list periodically, it can actively send the updated TA list to the core network. After the core network actively requests the TA list supported by the RAN node, the RAN node sends the supported TA list to the core network.
[0088] In the TA management method provided by the embodiments of the present application, during the process of establishing an interface between the core network and the RAN node, the update period of the TA list can be negotiated. The RAN node updates the TA list according to the negotiated update period, and can actively send the updated TA list to the core network, or send the supported TA list to the core network when the core network actively requests the supported TA list. This can not only solve the problem that the TA list changes as the RAN node moves, but also solve the problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network.
[0089] In some embodiments, the triggering conditions for sending the third information to the core network include at least one of the following: the expiration of the update period indicated by the core network; the expiration of the pre-configured update period on the RAN node; there is no intersection between the TA list currently supported by the RAN node and the TA list last sent by the RAN node to the core network, and the RAN node is mobile; receiving the second information.
[0090] In this embodiment, the RAN node will actively send the updated TA list to the core network, and will also send the supported TA list to the core network when the core network requests the supported TA list from the RAN node. To solve the problem that the TA list changes as the RAN node moves while also solving the problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network.
[0091] Optionally, when the update period indicated by the core network expires, the RAN node periodically updates the TA list; the update period can also be pre-configured on the RAN node, and when the pre-configured update period expires, the TA list is periodically updated, so that the updated TA list can be actively sent to the core network. The RAN node can also actively send the updated TA list to the core network when there is no intersection between the currently supported TA list and the TA list last sent by the RAN node to the core network. When the RAN node receives the second information sent by the core network, it determines the TA list that the core network actively requests to support, and thus sends the supported TA list to the core network.
[0092] In an alternative embodiment, when the RAN node is set on a satellite, the movement of the satellite causes the movement of the RAN node, resulting in a situation where there is no intersection between the currently supported TA list of the RAN node and the TA list last sent by the RAN node to the core network; if the RAN node is set on the ground, the movement of the RAN node on the ground may also cause a situation where there is no intersection between the currently supported TA list of the RAN node and the TA list last sent by the RAN node to the core network.
[0093] In some embodiments, when receiving the second information, sending the third information to the core network includes: sending a satellite ephemeris information update request to a network management system or other network elements; receiving the updated satellite ephemeris information from the network management system or other network elements; generating the third information according to the updated satellite ephemeris information, and sending the third information to the core network.
[0094] In this embodiment, if the first information sent by the core network to the RAN node includes the second information, the RAN node determines the TA list that the core network actively requests to support. Therefore, the RAN node can send a satellite ephemeris information update request to a network management system or other network elements, such as O&M. After receiving the satellite ephemeris information update request from the RAN node, the network management system or other network elements return the updated satellite ephemeris information to the RAN node. Thus, the RAN node can update the supported TA list according to the updated satellite ephemeris information and send the supported TA list to the core network. This can solve the problem that the TA list changes as the RAN node moves, and at the same time, it can also solve the problem of inconsistency between the actually supported TA list of the RAN node and the TA list supported by the RAN node reported to the core network, as well as the inconsistency between the TA list calculated by the core network based on the stored satellite ephemeris information and the TA list sent by the RAN node.
[0095] In an alternative embodiment, Figure 2 is a schematic flowchart of a process for a RAN node to send the third information to the core network provided by an embodiment of the present application. As Figure 2 shown, it mainly includes the following steps:
[0096] S201: The core network sends the second information to the RAN node;
[0097] S202: The RAN node sends an ephemeris information update request to the network management or other network elements;
[0098] S203: The RAN node receives the updated ephemeris information from the network management or other network elements;
[0099] S204: The RAN node generates the third information according to the updated ephemeris information.
[0100] S205: The RAN node sends the third information to the core network.
[0101] In some embodiments, the third information further includes at least one of the following: the time when the RAN node sends the third information; the valid duration of the TA list that the core network requests the RAN node to support.
[0102] In this embodiment, the core network can monitor whether the received TA list is valid through the time when the RAN node sends the third information and / or the valid duration of the TA list that the core network requests the RAN node to support, so that after the TA list expires, the core network can request the RAN node for a supported TA list again. Therefore, in addition to including the updated TA list, the third information sent by the RAN node to the core network can further include the time when the RAN node sends the third information and / or the valid duration of the TA list that the core network requests the RAN node to support.
[0103] In some embodiments, when the first information includes the update period of the TA list, after receiving the first information from the core network, it further includes: adjusting the original update period of the RAN node by using the received update period; sending a response message indicating successful update period adjustment to the core network.
[0104] In this embodiment, after the RAN node and the core network negotiate the update period of the TA list, the RAN node will overwrite the original update period with the received new update period and send a response message indicating successful update period adjustment to the core network. Thus, the RAN node can update the TA list periodically according to the new update period to solve the problem that the TA list changes as the RAN node moves and the problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network.
[0105] In an alternative implementation manner, Figure 3 is a schematic flowchart of a process for a RAN node to adjust the update period provided by an embodiment of the present application. As Figure 3 shown, it mainly includes the following steps:
[0106] S301: The RAN node receives the update period of the TA list from the core network;
[0107] S302: The RAN node adjusts the original update period of the RAN node by using the received update period;
[0108] S303: The RAN node sends a response message indicating successful adjustment of the update period to the core network.
[0109] In some embodiments, after sending the third information to the core network, it further includes: receiving a response message indicating that the TA list configuration is completed from the core network.
[0110] In this embodiment, after the RAN node sends the third information to the core network, the core network can complete the configuration of the TA list according to the received third information and send a response message to the RAN node to inform the RAN node that the TA list has been configured.
[0111] In some embodiments, the RAN node determines the currently supported TA list in the following ways: obtaining the TA list sent by the network management; and / or calculating the TA list according to the configuration information sent by the network management.
[0112] In this embodiment, the network management can periodically send the TA list to the RAN node; or can also periodically send the configuration information to the RAN node, and the RAN node can calculate the TA list according to the configuration information. After the RAN node obtains the TA list, it will send the currently supported TA list to the core network.
[0113] In some alternative embodiments, during the process of the RAN node negotiating the update period of the TA list with the core network, the RAN node can send the fourth information to the core network to request to establish an interface with the core network. The fourth information includes the currently supported TA list of the RAN node, and further includes at least one of the following: the access type of the RAN node; the valid duration of the currently supported TA list of the RAN node; the time when the RAN node sends the fourth information. After receiving the fourth information sent by the RAN node, the core network can negotiate the update period of the TA list with the RAN node and send the negotiated update period to the RAN node. In this way, the RAN node can update the supported TA list according to the negotiated update period.
[0114] In this embodiment, the core network may be an Access and Mobility Management Function (AMF) entity or a Mobility Management Entity (MME). Therefore, the fourth information sent by the RAN node to the core network may be the NG interface establishment request message NG SETUP REQUEST sent by the RAN node to the AMF, or the S1 interface establishment request message S1 SETUP REQUEST sent by the RAN node to the MME.
[0115] Optionally, the access type of the RAN node may be a regenerative-based satellite access type. The access type of the RAN node can be directly indicated by an indication message, or the access type of the RAN node can be configured as a regenerative-based satellite access type through the Global RAN Node ID and O&M.
[0116] In an alternative embodiment, Figure 4 FIG. is a schematic diagram of a regenerative satellite access architecture provided by an embodiment of the present application. As Figure 4 shown, the regenerative satellite access architecture can deploy the base station gNB / eNB, that is, the RAN node, on the satellite. The base station gNB / eNB needs to establish a connection with the ground core network in the area passed by the orbit through a satellite antenna as it moves, and the UE communicates with the core network through the base station gNB / eNB.
[0117] In some embodiments, a TA management method is provided, which is applied to the core network. Figure 5 FIG. is a flowchart of another TA management method provided by an embodiment of the present application. As Figure 5 shown, the method mainly includes the following steps:
[0118] S501: Send the first information to the RAN node.
[0119] In this step, the first information includes the update period of the TA list and / or the second information. The second information includes the indication information for requesting the TA list supported by the RAN node and / or the indication information for updating the ephemeris information of the RAN node.
[0120] Specifically, after the core network negotiates the update period of the TA list with the RAN node, the core network sends the update period of the TA list to the RAN node. The RAN node can update the TA list periodically according to the received update period. If the core network sends the second information to the RAN node, the core network actively requests the TA list supported by the RAN node, and the RAN node updates the TA list according to the second information sent by the core network.
[0121] S502: Receive the third information from the RAN node.
[0122] In this step, the third information includes the TA list supported by the core network requesting the RAN node.
[0123] Specifically, after the RAN node updates the TA list periodically, it can actively send the updated TA list to the core network. After the core network actively requests the TA list supported by the RAN node, the RAN node sends the supported TA list to the core network.
[0124] In the TA management method provided by the embodiments of the present application, during the process of establishing an interface between the core network and the RAN node, the update period of the TA list can be negotiated. The RAN node updates the TA list according to the negotiated update period, and can actively send the updated TA list to the core network, or send the supported TA list to the core network when the core network actively requests the supported TA list. This can not only solve the problem that the TA list changes as the RAN node moves, but also solve the problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network.
[0125] In some embodiments, the third information further includes at least one of the following: the time when the RAN node sends the third information; the effective duration of the TA list supported by the core network requesting the RAN node.
[0126] In this embodiment, the core network can monitor whether the received TA list is valid through the time when the RAN node sends the third information and / or the effective duration of the TA list supported by the core network requesting the RAN node, so that after the TA list becomes invalid, it can request the supported TA list from the RAN node again. Therefore, in addition to including the updated TA list, the third information sent by the RAN node to the core network can also include the time when the RAN node sends the third information and / or the effective duration of the TA list supported by the core network requesting the RAN node.
[0127] In some embodiments, before sending the first information to the RAN node, it further includes: receiving the fourth information from the RAN node, where the fourth information includes the TA list currently supported by the RAN node; determining the update period of the TA list according to the fourth information.
[0128] In this embodiment, during the process of the RAN node negotiating the update period of the TA list with the core network, the RAN node may send fourth information to the core network to request to establish an interface with the core network. After receiving the fourth information sent by the RAN node, the core network may negotiate the update period of the TA list with the RAN node and send the negotiated update period to the RAN node. In this way, the RAN node can update the TA list supported by the RAN node according to the negotiated update period. Thus, the problem that the TA list changes as the RAN node moves is solved, and the problem that there is an inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network is solved.
[0129] Optionally, the core network may be an Access and Mobility Management Function (AMF) entity or a Mobility Management Entity (MME). Therefore, the fourth information sent by the RAN node to the core network may be the NG interface establishment request message NG SETUP REQUEST sent by the RAN node to the AMF, or the S1 interface establishment request message S1 SETUP REQUEST sent by the RAN node to the MME.
[0130] In some embodiments, the fourth information further includes at least one of the following: the effective duration of the TA list currently supported by the RAN node; the time when the RAN node sends the fourth information.
[0131] In this embodiment, the fourth information may further include the access type of the RAN node. The access type of the RAN node may be a regenerative satellite access type. The access type of the RAN node as a regenerative satellite access type may be directly indicated by an indication message, or the access type of the RAN node may be configured as a regenerative satellite access type through the global RAN node identifier and network element. After receiving the fourth information, the core network may, when supporting the regenerative satellite access type, determine the update period of the TA list according to information such as the TA list currently supported by the RAN node, the effective duration of the TA list currently supported by the RAN node, and the time when the RAN node sends the fourth information.
[0132] Optionally, the RAN node may update the TA list according to the update period sent by the core network, thus solving the problem that the TA list changes as the RAN node moves, and solving the problem that there is an inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network.
[0133] In some embodiments, determining the update period of the TA list according to the fourth information includes: determining the update period of the TA list according to the load information of the core network and / or RAN node, the energy-saving information of the RAN node, and the fourth information.
[0134] In this embodiment, the core network may pre-store the ephemeris information of the RAN node to predict the changing TA list. If the ephemeris information of the RAN node is not stored in the core network, the core network cannot predict the TA list. Therefore, after receiving the fourth information, the core network can store the fourth information. When it is necessary to negotiate the update period of the TA list with the RAN node, the update period of the TA list is determined according to the load information of the core network and / or RAN node, the energy-saving information of the RAN node, and the fourth information sent by the RAN node. Therefore, it can not only solve the problem that the TA list changes as the RAN node moves, but also solve the problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network.
[0135] Optionally, after determining the update period of the TA list, the core network may carry the update period in the SETUP RESPONSE message of the interface establishment completion response and send it to the RAN node.
[0136] In some embodiments, determining the update period of the TA list according to the fourth information includes: if the core network has stored the ephemeris information of the RAN node, calculating the TA list supported by the RAN node according to the ephemeris information of the RAN node; if the TA list included in the fourth information is consistent with the TA list calculated by the core network according to the stored ephemeris information, determining the update period of the TA list according to the load information, the energy-saving information of the RAN node, the ephemeris information stored in the core network, and the valid duration of the TA list; if the TA list included in the fourth information is inconsistent with the TA list calculated by the core network according to the stored ephemeris information, determining the target TA list; determining the update period of the TA list according to the load information, the energy-saving information of the RAN node, the ephemeris information corresponding to the target TA list, and the valid duration of the target TA list.
[0137] In this embodiment, the core network has stored the ephemeris information of the RAN node, which may be the ephemeris information of the RAN node re-requested by the core network from the network management or other network elements. If the core network has stored the ephemeris information of the RAN node, the core network can calculate the TA list supported by the RAN node according to the stored ephemeris information, and compare the TA list included in the fourth information with the TA list calculated by the core network according to the stored ephemeris information. If the TA list included in the fourth information is consistent with the TA list calculated by the core network according to the stored ephemeris information, the update period of the TA list can be directly determined according to the load information of the core network and / or RAN node, the energy-saving information of the RAN node, the ephemeris information stored by the core network, and the effective duration of the TA list (since the TA list included in the fourth information is consistent with the TA list calculated by the core network according to the stored ephemeris information, this TA list can be the TA list included in the fourth information or the TA list calculated by the core network according to the stored ephemeris information).
[0138] In the above embodiment, if the TA list included in the fourth information is inconsistent with the TA list calculated by the core network according to the stored ephemeris information, it is necessary to determine the target TA list, and the target TA list can be selected according to the actual application scenario. After determining the target TA list, the update period of the TA list is determined according to the load information of the core network and / or RAN node, the energy-saving information of the RAN node, the ephemeris information corresponding to the target TA list (the ephemeris information used to calculate the target TA list), and the effective duration of the target TA list.
[0139] Optionally, the update period of the TA list is obtained through negotiation between the core network and the RAN node, which can not only solve the problem that the TA list changes as the RAN node moves, but also solve the problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network, and can also solve the problem of inconsistency between the TA list calculated by the core network based on the stored ephemeris information and the TA list sent by the RAN node.
[0140] In some embodiments, determining the target TA list includes: obtaining the updated ephemeris information of the RAN node from the network management or other network elements; calculating the target TA list according to the updated ephemeris information; or, determining the TA list calculated by the core network as the target TA list; or, sending the second information to the RAN node; obtaining the updated TA list from the RAN node; determining the updated TA list of the RAN node as the target TA list; or, adjusting the ephemeris information stored by the core network according to the TA list included in the fourth information; calculating the target TA list according to the adjusted ephemeris information.
[0141] In this embodiment, if the TA list included in the fourth information is inconsistent with the TA list calculated by the core network based on the stored ephemeris information, the core network may request the ephemeris information of the RAN node from the network management or other network elements, such as O&M, again. After receiving the updated ephemeris information, the core network may recalculate the TA list based on the updated ephemeris information and use this TA list as the target TA list. Correspondingly, the ephemeris information corresponding to the target TA list is the updated ephemeris information received by the core network.
[0142] In the above embodiment, if the TA list included in the fourth information is inconsistent with the TA list calculated by the core network based on the stored ephemeris information, since the RAN node is constantly moving, the accuracy of the TA list calculated by the core network based on the stored ephemeris information is higher than that of the TA list sent by the RAN node. Therefore, the core network may also directly use the TA list calculated by the core network based on the stored ephemeris information as the target TA list according to the actual scenario. Correspondingly, the ephemeris information corresponding to the target TA list is the ephemeris information stored by the core network.
[0143] In the above embodiment, if the TA list included in the fourth information is inconsistent with the TA list calculated by the core network based on the stored ephemeris information, the core network may also notify the RAN node to update the ephemeris information and the TA list. Therefore, the core network may send the second information to the RAN node. After receiving the second information, the RAN node requests the network management or other network elements to update the ephemeris information and determines the updated TA list based on the updated ephemeris information. In this way, after the core network obtains the updated TA list from the RAN node, it may determine the updated TA list of the RAN node as the target TA list. Correspondingly, the ephemeris information corresponding to the target TA list is the updated ephemeris information of the RAN node.
[0144] In the above embodiment, if the TA list included in the fourth information is inconsistent with the TA list calculated by the core network based on the stored ephemeris information, the core network may also adjust the ephemeris information of the RAN node stored by the core network according to the TA list included in the fourth information, and then recalculate the TA list based on the adjusted ephemeris information and use this TA list as the target TA list. Correspondingly, the ephemeris information corresponding to the target TA list is the adjusted ephemeris information of the core network.
[0145] Optionally, the update period of the TA list is negotiated with the RAN node through the core network, which can not only solve the problem that the TA list changes as the RAN node moves, but also solve the problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network, and can also solve the problem of inconsistency between the TA list calculated by the core network based on the stored ephemeris information and the TA list sent by the RAN node.
[0146] In some alternative embodiments, after receiving the third information from the RAN node, it further includes: storing the third information.
[0147] In this embodiment, after the core network receives the third information, if the core network does not store the ephemeris information of the RAN node, it can directly store the third information, so as to use the updated TA list included in the third information to overwrite the original TA list, and use the time information included in the third information (the moment when the RAN node sends the third information and / or the effective duration of the TA list supported by the core network's request for the RAN node) to overwrite the original time information.
[0148] In the above embodiment, if the core network has stored the ephemeris information of the RAN node, since the core network can calculate the TA list supported by the RAN node according to the stored ephemeris information, and there are two cases of consistency or inconsistency between the TA list calculated by the core network based on the stored ephemeris information and the TA list included in the third information, therefore, the core network can also select to store the third information according to the actual application scenario, so as to use the updated TA list included in the third information to overwrite the original TA list, and use the time information included in the third information to overwrite the original time information.
[0149] Optionally, after the RAN node updates the TA list, it is necessary to inform the core network of the supported TA list, so that the core network can perform TA configuration according to the supported TA list. Therefore, it can not only solve the problem that the TA list changes as the RAN node moves, but also solve the problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network, and can also solve the problem of inconsistency between the TA list calculated by the core network based on the stored ephemeris information and the TA list sent by the RAN node.
[0150] In some embodiments, after receiving the third information from the RAN node, it further includes: if the core network has stored the ephemeris information of the RAN node, then according to the ephemeris information of the RAN node, calculate the TA list supported by the RAN node, and perform the following operations: if the TA list calculated by the core network based on the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network obtains the updated ephemeris information of the RAN node from the network management or other network elements, then according to the updated ephemeris information, calculate and store the TA list supported by the RAN node; or, if the TA list calculated by the core network based on the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network sends the second information to the RAN node, then wait for the updated TA list from the RAN node, or store the TA list calculated by the core network based on the stored ephemeris information.
[0151] In this embodiment, if the core network has stored the ephemeris information of the RAN node, since the core network can calculate the TA list supported by the RAN node according to the stored ephemeris information, and there are two cases of consistency or inconsistency between the TA list calculated by the core network based on the stored ephemeris information and the TA list included in the third information. Therefore, when the TA list calculated by the core network based on the stored ephemeris information is inconsistent with the TA list included in the third information, the updated TA list included in the third information may not be used to overwrite the original TA list, but other methods may be used to recalculate the TA list. Thus, it can not only solve the problem that the TA list changes as the RAN node moves, but also solve the problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network, and can also solve the problem of inconsistency between the TA list calculated by the core network based on the stored ephemeris information and the TA list sent by the RAN node.
[0152] The first method is that the core network can obtain the updated ephemeris information of the RAN node from the network management or other network elements, and according to the updated ephemeris information, recalculate the TA list supported by the RAN node, and then store the recalculated TA list and the valid duration of this TA list.
[0153] In the second method, the core network can notify the RAN node to request the network management or other network elements to update the ephemeris information. Therefore, the core network can send a second message to the RAN node. After receiving the second message, the RAN node requests the network management or other network elements to update the ephemeris information, and determines the supported TA list according to the updated ephemeris information. The core network can wait for the supported TA list from the RAN node. After receiving the supported TA list sent by the RAN node, it stores the supported TA list, the moment when the supported TA list is received, and the valid duration of the supported TA list. The core network can also directly store the TA list calculated by the core network according to the stored ephemeris information and the valid duration of the TA list.
[0154] In some embodiments, it further includes: sending a response message indicating that the TA list configuration is completed to the RAN node.
[0155] In this embodiment, after the RAN node sends the third message to the core network, the core network can complete the configuration of the TA list according to the received third message and send a response message to the RAN node to inform the RAN node that the TA list has been configured.
[0156] In some embodiments, the triggering conditions for receiving the second message include at least one of the following: there is no intersection between the TA list supported by the RAN node calculated by the core network and the TA list last sent by the RAN node to the core network; the valid duration of the TA list stored by the core network expires; the core network needs to notify the RAN node to request the network management or other network elements to update the ephemeris information.
[0157] In this embodiment, if the second message is received, it can be determined that the core network actively requests the supported TA list from the RAN node. Thus, the problem that the TA list changes as the RAN node moves can be solved, the problem of inconsistency between the TA list calculated by the core network based on the stored ephemeris information and the TA list sent by the RAN node can be solved, and the problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network can also be solved. The core network actively requesting the supported TA list from the RAN node mainly includes the following situations:
[0158] In the first situation, when the TA list supported by the RAN node calculated by the core network is about to have no intersection with the TA list last sent by the RAN node to the core network, the core network can actively request the supported TA list from the RAN node; the RAN node sends the supported TA list and time information (the moment when the RAN node sends the supported TA list and / or the valid duration of the TA list requested by the core network from the RAN node) to the core network.
[0159] In the second case, when the expiration time of the valid duration of the stored TA list in the core network arrives, the core network can also actively request the TA list supported by the RAN node; the RAN node sends the supported TA list and time information (the moment when the RAN node sends the updated TA list and / or the valid duration of the TA list supported by the RAN node requested by the core network) to the core network.
[0160] In the third case, when the core network needs to notify the RAN node to request updated ephemeris information from the network management or other network elements, the core network can also actively request the TA list supported by the RAN node; the RAN node first requests updated ephemeris information from the network management or other network elements. After the RAN node receives the updated ephemeris information, it updates the supported TA list and sends the supported TA list and time information (the moment when the RAN node sends the updated TA list and / or the valid duration of the TA list supported by the RAN node requested by the core network) to the core network.
[0161] The TA management method provided in this application can solve the problem of changes in the supported TA list caused by the movement of the RAN node by reporting the supported TA list and time information from the RAN node to the core network; through the mechanism of negotiating the TA list between the core network and the RAN node, the RAN node can actively update the supported TA list periodically, and the core network can also actively request the TA list supported by the RAN node, thereby solving the problem of inconsistency between the TA list calculated by the core network based on the stored ephemeris information and the TA list sent by the RAN node, and solving the problem of inconsistency between the TA list actually supported by the RAN node and the TA list supported by the RAN node reported to the core network.
[0162] In some embodiments, a TA management device is provided, which is applied to the RAN node. Figure 6 The following is a schematic structural diagram of a TA management device provided in an embodiment of this application, as Figure 6 shown. The TA management device 600 mainly includes:
[0163] A receiving module 601, configured to receive first information from the core network. The first information includes the update period of the TA list and / or second information. The second information includes indication information for requesting the TA list supported by the RAN node and / or indication information for updating the ephemeris information of the RAN node.
[0164] A sending module 602, configured to send third information to the core network. The third information includes the TA list supported by the RAN node requested by the core network.
[0165] In some embodiments, the trigger conditions for sending the third information to the core network include at least one of the following: the expiration of the update period indicated by the core network; the expiration of the pre-configured update period on the RAN node; there is no intersection between the TA list currently supported by the RAN node and the TA list last sent by the RAN node to the core network, and the RAN node is mobile; receiving the second information.
[0166] In some embodiments, when receiving the second information, when the sending module 602 sends the third information to the core network, it is specifically configured to: send a request for ephemeris information update to the network management or other network elements; receive the updated ephemeris information from the network management or other network elements; generate the third information according to the updated ephemeris information, and send the third information to the core network.
[0167] In some embodiments, the third information further includes at least one of the following: the time when the RAN node sends the third information; the effective duration of the TA list supported by the core network's request for the RAN node.
[0168] In some embodiments, when the first information includes the update period of the TA list, it further includes: a processing module (not shown), configured to, after receiving the first information from the core network, adjust the original update period of the RAN node using the received update period; send a response message indicating the successful adjustment of the update period to the core network.
[0169] In some embodiments, the receiving module 601 is further configured to, after sending the third information to the core network, receive a response message indicating the completion of the TA list configuration from the core network.
[0170] In some embodiments, the RAN node determines the currently supported TA list in the following manner: obtaining the TA list sent by the network management; and / or calculating the TA list according to the configuration information sent by the network management.
[0171] In some embodiments, a TA management device is provided, which is applied to the core network. Figure 7 For another structural schematic diagram of the TA management device provided by the embodiments of the present application, as Figure 7 shown, the TA management device 700 mainly includes:
[0172] A sending module 701, configured to send the first information to the RAN node, where the first information includes the update period of the TA list and / or the second information, and the second information includes an indication information for requesting the TA list supported by the RAN node and / or an indication information for updating the ephemeris information of the RAN node.
[0173] A receiving module 702, configured to receive the third information from the RAN node, where the third information includes the TA list supported by the core network's request for the RAN node.
[0174] In some embodiments, the third information further includes at least one of the following: the time when the RAN node sends the third information; the valid duration of the TA list that the core network requests the RAN node to support.
[0175] In some embodiments, it further includes: a processing module (not shown), configured to, before sending the first information to the RAN node, receive fourth information from the RAN node, where the fourth information includes the TA list currently supported by the RAN node; and determine the update period of the TA list according to the fourth information.
[0176] In some embodiments, the fourth information further includes at least one of the following: the valid duration of the TA list currently supported by the RAN node; the time when the RAN node sends the fourth information.
[0177] In some embodiments, when determining the update period of the TA list according to the fourth information, the processing module is specifically configured to: determine the update period of the TA list according to the load information of the core network and / or the RAN node, the energy-saving information of the RAN node, and the fourth information.
[0178] In some embodiments, when determining the update period of the TA list according to the fourth information, the processing module is specifically configured to: if the core network has stored the ephemeris information of the RAN node, calculate the TA list supported by the RAN node according to the ephemeris information of the RAN node; if the TA list included in the fourth information is consistent with the TA list calculated by the core network according to the stored ephemeris information, determine the update period of the TA list according to the load information, the energy-saving information of the RAN node, the ephemeris information stored in the core network, and the valid duration of the TA list; if the TA list included in the fourth information is inconsistent with the TA list calculated by the core network according to the stored ephemeris information, determine the target TA list; and determine the update period of the TA list according to the load information, the energy-saving information of the RAN node, the ephemeris information corresponding to the target TA list, and the valid duration of the target TA list.
[0179] In some embodiments, when determining the target TA list, the processing module is specifically configured to: obtain the updated ephemeris information of the RAN node from the network management or other network elements; calculate the target TA list according to the updated ephemeris information; or, determine the TA list calculated by the core network as the target TA list; or, send the second information to the RAN node; obtain the updated TA list from the RAN node; and determine the updated TA list of the RAN node as the target TA list; or, adjust the ephemeris information stored in the core network according to the TA list included in the fourth information; and calculate the target TA list according to the adjusted ephemeris information.
[0180] In some embodiments, the processing module is further configured to, after receiving the third information from the RAN node, if the core network has stored the ephemeris information of the RAN node, calculate the TA list supported by the RAN node according to the ephemeris information of the RAN node, and perform the following operations: if the TA list calculated by the core network according to the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network obtains the updated ephemeris information of the RAN node from the network management or other network elements, calculate and store the TA list supported by the RAN node according to the updated ephemeris information; or, if the TA list calculated by the core network according to the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network sends the second information to the RAN node, wait for the updated TA list from the RAN node, or store the TA list calculated by the core network according to the stored ephemeris information.
[0181] In some embodiments, the sending module 701 is further configured to send a response message indicating that the TA list configuration is completed to the RAN node.
[0182] In some embodiments, the triggering conditions for receiving the second information include at least one of the following: there is no intersection between the TA list supported by the RAN node calculated by the core network and the TA list last sent by the RAN node to the core network; the valid duration of the TA list stored in the core network expires; the core network needs to notify the RAN node to request updated ephemeris information from the network management or other network elements.
[0183] It should be noted that the division of units in the embodiments of the present application is illustrative only, and is only a logical function division. In actual implementation, there may be other division methods. In addition, in each embodiment of the present application, the functional units may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above integrated units may be implemented in the form of hardware or in the form of software functional units.
[0184] If the above integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a processor-readable storage medium. Based on such an understanding, the technical solution of the present application essentially or the part that contributes to the prior art or all or part of the technical solution may be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods in the various embodiments of the present application.
[0185] It should be noted here that the above device provided by the embodiments of the present invention can implement all the method steps implemented by the above method embodiments and can achieve the same technical effects. Therefore, the same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.
[0186] In some embodiments, a TA management device is further provided.
[0187] Figure 8 As shown in the structure schematic diagram of a TA management device provided by an embodiment of the present application, Figure 8 as shown, the TA management device includes: a memory 8011, a transceiver 8012, and a processor 8013.
[0188] The memory 8011 is used to store computer programs;
[0189] The transceiver 8012 is used to receive and send data under the control of the processor 8013.
[0190] Among them, in Figure 8 the bus architecture may include any number of interconnected buses and bridges. Specifically, various circuits of one or more processors represented by the processor and the memory represented by the memory are linked together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art. Therefore, they will not be further described herein. The bus interface provides an interface. The transceiver can be multiple components, that is, including a transmitter and a receiver, and provides a unit for communicating with various other devices on the transmission medium, and these transmission mediums include wireless channels, wired channels, optical fiber cables, etc. The processor is responsible for managing the bus architecture and general processing, and the memory can store the data used by the processor... when performing operations.
[0191] The processor can be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD). The processor can also adopt a multi-core architecture.
[0192] The processor 8013 reads the computer program in the memory 8011 and performs the following operations:
[0193] Receive the first information from the core network, where the first information includes the update period of the TA list and / or the second information, and the second information includes the indication information for requesting the TA list supported by the RAN node and / or the indication information for updating the ephemeris information of the RAN node;
[0194] Send the third information to the core network, where the third information includes the TA list supported by the core network requesting the RAN node.
[0195] In some embodiments, the triggering conditions for sending the third information to the core network include at least one of the following: the expiration of the update period indicated by the core network; the expiration of the pre-configured update period on the RAN node; there is no intersection between the TA list currently supported by the RAN node and the TA list last sent by the RAN node to the core network, and the RAN node is mobile; receiving the second information.
[0196] In some embodiments, when receiving the second information, sending the third information to the core network includes: sending an ephemeris information update request to the network management or other network elements; receiving the updated ephemeris information from the network management or other network elements; generating the third information according to the updated ephemeris information, and sending the third information to the core network.
[0197] In some embodiments, the third information further includes at least one of the following: the moment when the RAN node sends the third information; the valid duration of the TA list supported by the core network requesting the RAN node.
[0198] In some embodiments, when the first information includes the update period of the TA list, after receiving the first information from the core network, it further includes: adjusting the original update period of the RAN node by using the received update period; sending a response message indicating the successful adjustment of the update period to the core network.
[0199] In some embodiments, after sending the third information to the core network, it further includes: receiving a response message indicating the completion of the TA list configuration from the core network.
[0200] In some embodiments, the RAN node determines the currently supported TA list in the following ways: obtaining the TA list sent by the network management; and / or calculating the TA list according to the configuration information sent by the network management.
[0201] In some embodiments, a TA management device is further provided.
[0202] Figure 9 For another structural schematic diagram of the TA management device provided by the embodiments of the present application, as Figure 9 shown, the TA management device includes: a memory 9011, a transceiver 9012, and a processor 9013.
[0203] The memory 9011 is used to store computer programs;
[0204] A transceiver 9012 for receiving and sending data under the control of a processor 9013.
[0205] Among them, in Figure 9 , the bus architecture may include any number of interconnected buses and bridges, specifically, various circuits represented by one or more processors and memories represented by memories are linked together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art, and therefore, they will not be further described herein. The bus interface provides an interface. The transceiver can be multiple components, that is, including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, and these transmission mediums include wireless channels, wired channels, optical fiber cables, and other transmission mediums. The processor is responsible for managing the bus architecture and general processing, and the memory can store the data used by the processor... when performing operations.
[0206] The processor can be a CPU, ASIC, FPGA, or CPLD, and the processor can also adopt a multi-core architecture.
[0207] The processor 9013 reads the computer program in the memory 9011 and performs the following operations:
[0208] Sending first information to the RAN node, the first information includes the update period of the TA list and / or second information, and the second information includes indication information for requesting the TA list supported by the RAN node and / or indication information for updating the ephemeris information of the RAN node;
[0209] Receiving third information from the RAN node, the third information includes the TA list supported by the core network requesting the RAN node.
[0210] In some embodiments, the third information further includes at least one of the following: the moment when the RAN node sends the third information; the valid duration of the TA list supported by the core network requesting the RAN node.
[0211] In some embodiments, before sending the first information to the RAN node, it further includes: receiving fourth information from the RAN node, the fourth information includes the TA list currently supported by the RAN node; determining the update period of the TA list according to the fourth information.
[0212] In some embodiments, the fourth information further includes at least one of the following: the valid duration of the TA list currently supported by the RAN node; the moment when the RAN node sends the fourth information.
[0213] In some embodiments, determining the update period of the TA list according to the fourth information includes: determining the update period of the TA list according to the load information of the core network and / or RAN node, the energy saving information of the RAN node, and the fourth information.
[0214] In some embodiments, determining the update period of the TA list according to the fourth information includes: if the core network has stored the ephemeris information of the RAN node, calculating the TA list supported by the RAN node according to the ephemeris information of the RAN node; if the TA list included in the fourth information is consistent with the TA list calculated by the core network according to the stored ephemeris information, determining the update period of the TA list according to the load information, the energy saving information of the RAN node, the ephemeris information stored in the core network, and the valid duration of the TA list; if the TA list included in the fourth information is inconsistent with the TA list calculated by the core network according to the stored ephemeris information, determining the target TA list; determining the update period of the TA list according to the load information, the energy saving information of the RAN node, the ephemeris information corresponding to the target TA list, and the valid duration of the target TA list.
[0215] In some embodiments, determining the target TA list includes: obtaining the updated ephemeris information of the RAN node from the network management or other network elements; calculating the target TA list according to the updated ephemeris information; or, determining the TA list calculated by the core network as the target TA list; or, sending the second information to the RAN node; obtaining the updated TA list from the RAN node; determining the updated TA list of the RAN node as the target TA list; or, adjusting the ephemeris information stored in the core network according to the TA list included in the fourth information; calculating the target TA list according to the adjusted ephemeris information.
[0216] In some embodiments, after receiving the third information from the RAN node, it further includes: if the core network has stored the ephemeris information of the RAN node, calculating the TA list supported by the RAN node according to the ephemeris information of the RAN node, and performing the following operations: if the TA list calculated by the core network according to the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network obtains the updated ephemeris information of the RAN node from the network management or other network elements, calculating and storing the TA list supported by the RAN node according to the updated ephemeris information; or, if the TA list calculated by the core network according to the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network sends the second information to the RAN node, waiting for the updated TA list from the RAN node, or storing the TA list calculated by the core network according to the stored ephemeris information.
[0217] In some embodiments, it further includes: sending a response message indicating that the TA list configuration is completed to the RAN node.
[0218] In some embodiments, the triggering conditions for receiving the second information include at least one of the following: there is no intersection between the TA list supported by the RAN node calculated by the core network and the TA list last sent by the RAN node to the core network; the valid duration of the TA list stored in the core network expires; the core network needs to notify the RAN node to request ephemeris information update from the network management or other network elements.
[0219] It should be noted here that the above device provided in the embodiments of the present invention can implement all the method steps implemented in the above method embodiments, and can achieve the same technical effects. The same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.
[0220] In some embodiments, a processor-readable storage medium is further provided. The processor-readable storage medium stores a computer program, and the computer program is used to cause the processor to execute the method according to any one of the method embodiments.
[0221] The processor-readable storage medium can be any available medium or data storage device accessible by the processor, including but not limited to magnetic memories (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical memories (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor memories (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drives (SSD)).
[0222] In some embodiments, a computer program product is provided, including a computer program, and the computer program is used to cause the processor to execute the method according to any one of the method embodiments.
[0223] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories and optical memories, etc.) containing computer-usable program code.
[0224] This application is described with reference to the flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as combinations of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to the processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a means for implementing the functions specified in the Figure 1 one or more flows and / or blocks Figure 1 one or more blocks.
[0225] These processor-executable instructions can also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the processor-readable memory produce a manufactured article including instruction means that implement the functions specified in the Figure 1 one or more flows and / or blocks Figure 1 one or more blocks.
[0226] Obviously, those skilled in the art can make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to include these changes and modifications.
Claims
1. A tracking area TA management method, characterized in that, Applied to a Radio Access Network (RAN) node, the TA management method includes: Receiving first information from the core network, where the first information includes the update period of the TA list and / or second information, and the second information includes indication information for requesting the TA list supported by the RAN node and / or indication information for updating the ephemeris information of the RAN node; Sending third information to the core network, where the third information includes the TA list that the core network requests the RAN node to support.
2. The TA management method according to claim 1, wherein The triggering conditions for sending the third information to the core network include at least one of the following: The update period indicated by the core network expires; The pre-configured update period on the RAN node expires; There is no intersection between the TA list currently supported by the RAN node and the TA list that the RAN node last sent to the core network, and the RAN node is mobile; Receiving the second information.
3. The TA management method according to claim 1 or 2, characterized in that, When receiving the second information, the sending the third information to the core network includes: Sending an ephemeris information update request to the network management or other network elements; Receiving the updated ephemeris information from the network management or other network elements; Generating the third information according to the updated ephemeris information, and sending the third information to the core network.
4. The TA management method according to any one of claims 1 to 3, characterized in that, The third information further includes at least one of the following: The time when the RAN node sends the third information; The valid duration of the TA list that the core network requests the RAN node to support.
5. The TA management method according to any one of claims 1 to 3, characterized in that, When the first information includes the update period of the TA list, after receiving the first information from the core network, it further includes: Adjusting the original update period of the RAN node using the received update period; Sending a response message indicating successful update period adjustment to the core network.
6. The TA management method according to any one of claims 1 to 3, characterized in that After sending the third information to the core network, it further includes: Receiving a response message indicating that the TA list configuration by the core network is completed.
7. The TA management method according to any one of claims 1 to 3, characterized in that, The RAN node determines the currently supported TA list in the following ways: Obtaining the TA list sent by the network management; and / or, Or calculating the TA list according to the configuration information sent by the network management.
8. A TA management method, characterized in that, Applied to the core network, the TA management method includes: Sending first information to the RAN node, where the first information includes the update period of the TA list and / or second information, and the second information includes indication information for requesting the TA list supported by the RAN node and / or indication information for updating the ephemeris information of the RAN node; Receiving third information from the RAN node, where the third information includes the TA list that the core network requests the RAN node to support.
9. The TA management method according to claim 8, wherein The third information further includes at least one of the following: The time when the RAN node sends the third information; The valid duration of the TA list that the core network requests the RAN node to support.
10. The TA management method according to claim 8, characterized in that, Before sending the first information to the RAN node, it further includes: Receiving fourth information from the RAN node, where the fourth information includes the TA list currently supported by the RAN node; Determining the update period of the TA list according to the fourth information.
11. The TA management method according to claim 10, wherein The fourth information further includes at least one of the following: The valid duration of the TA list currently supported by the RAN node; The time when the RAN node sends the fourth information.
12. The TA management method according to claim 10 or 11, characterized in that, Determining the update period of the TA list according to the fourth information includes: Determining the update period of the TA list according to the load information of the core network and / or the RAN node, the energy saving information of the RAN node, and the fourth information.
13. The TA management method according to claim 12, characterized in that Determining the update period of the TA list according to the fourth information includes: If the core network has stored the ephemeris information of the RAN node, calculating the TA list supported by the RAN node according to the ephemeris information of the RAN node; If the TA list included in the fourth information is consistent with the TA list calculated by the core network according to the stored ephemeris information, determining the update period of the TA list according to the load information, the energy saving information of the RAN node, the ephemeris information stored in the core network, and the effective duration of the TA list; If the TA list included in the fourth information is inconsistent with the TA list calculated by the core network according to the stored ephemeris information, determining the target TA list; determining the update period of the TA list according to the load information, the energy saving information of the RAN node, the ephemeris information corresponding to the target TA list, and the effective duration of the target TA list.
14. The TA management method according to claim 13, characterized in that, Determining the target TA list includes: Obtaining the updated ephemeris information of the RAN node from the network management or other network elements; calculating the target TA list according to the updated ephemeris information; or, Determining the TA list calculated by the core network as the target TA list; or, Sending the second information to the RAN node; obtaining the updated TA list from the RAN node; determining the updated TA list of the RAN node as the target TA list; or, Adjusting the ephemeris information stored in the core network according to the TA list included in the fourth information; calculating the target TA list according to the adjusted ephemeris information.
15. The TA management method according to any one of claims 8 to 14, characterized in that, After receiving the third information from the RAN node, it further includes: If the core network has stored the ephemeris information of the RAN node, calculating the TA list supported by the RAN node according to the ephemeris information of the RAN node, and performing the following operations: If the TA list calculated by the core network according to the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network obtains the updated ephemeris information of the RAN node from the network management or other network elements, calculating and storing the TA list supported by the RAN node according to the updated ephemeris information; or, If the TA list calculated by the core network according to the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network sends the second information to the RAN node, waiting for the updated TA list from the RAN node, or storing the TA list calculated by the core network according to the stored ephemeris information.
16. The TA management method according to claim 15, wherein, It further includes: Sending a response message indicating that the TA list configuration is completed to the RAN node.
17. The TA management method according to any one of claims 8 to 14, characterized in that, The triggering conditions for receiving the second information include at least one of the following: There is no intersection between the TA list supported by the RAN node calculated by the core network and the TA list last sent by the RAN node to the core network; The valid duration of the TA list stored in the core network expires; The core network needs to notify the RAN node to request updated ephemeris information from the network management or other network elements.
18. A TA management device, characterized in that, Applied to the RAN node, the TA management device includes: A receiving module, configured to receive first information from the core network, where the first information includes the update period of the TA list and / or second information, and the second information includes indication information for requesting the TA list supported by the RAN node and / or indication information for updating the ephemeris information of the RAN node; A sending module, configured to send third information to the core network, where the third information includes the TA list supported by the core network and requested by the RAN node.
19. A TA management device, characterized in that, Applied to the core network, the TA management device includes: A sending module, configured to send first information to the RAN node, where the first information includes the update period of the TA list and / or second information, and the second information includes indication information for requesting the TA list supported by the RAN node and / or indication information for updating the ephemeris information of the RAN node; A receiving module, configured to receive third information from the RAN node, where the third information includes the TA list supported by the core network and requested by the RAN node.
20. A TA management device, characterized in that, Including: a memory, a transceiver, a processor: The memory is used to store computer programs; The transceiver is used to transmit and receive data under the control of the processor; The processor is used to read the computer program in the memory and perform the following operations: Receive first information from the core network, where the first information includes the update period of the TA list and / or second information, and the second information includes indication information for requesting the TA list supported by the RAN node and / or indication information for updating the ephemeris information of the RAN node; Send third information to the core network, where the third information includes the TA list supported by the core network and requested by the RAN node.
21. The TA management device according to claim 20, characterized in that, The triggering conditions for sending the third information to the core network include at least one of the following: The update period indicated by the core network expires; The pre-configured update period on the RAN node expires; There is no intersection between the TA list currently supported by the RAN node and the TA list last sent by the RAN node to the core network, and the RAN node is mobile; Receive the second information.
22. The TA management device according to claim 20 or 21, characterized in that, When receiving the second information, sending the third information to the core network includes: Send an ephemeris information update request to the network management or other network elements; Receive the updated ephemeris information from the network management or other network elements; Generate the third information according to the updated ephemeris information, and send the third information to the core network.
23. The TA management device according to any one of claims 20 to 22, characterized in that, The third information further includes at least one of the following: The time when the RAN node sends the third information; The valid duration of the TA list supported by the core network and requested by the RAN node.
24. The TA management device according to any one of claims 20 to 22, characterized in that, When the first information includes the update period of the TA list, after receiving the first information from the core network, it further includes: Adjust the original update period of the RAN node by using the received update period; Send a response message indicating successful update period adjustment to the core network.
25. The TA management device according to any one of claims 20 to 22, characterized in that, After sending the third information to the core network, it further includes: Receive a response message indicating that the TA list configuration by the core network is completed.
26. The TA management method according to any one of claims 20 to 22, characterized in that, The RAN node determines the currently supported TA list in the following manner: Obtain the TA list sent by the network management; and / or, Or calculate the TA list according to the configuration information sent by the network management.
27. A TA management device, characterized in that, It includes: A memory, a transceiver, and a processor: The memory is used to store computer programs; The transceiver is used to send and receive data under the control of the processor; The processor is used to read the computer program in the memory and perform the following operations: Send the first information to the RAN node, where the first information includes the update period of the TA list and / or the second information, and the second information includes the indication information for requesting the TA list supported by the RAN node and / or the indication information for updating the ephemeris information of the RAN node; Receive the third information from the RAN node, where the third information includes the TA list that the core network requests the RAN node to support.
28. The TA management device according to claim 27, wherein The third information further includes at least one of the following: The time when the RAN node sends the third information; The effective duration of the TA list that the core network requests the RAN node to support.
29. The TA management device according to claim 27, characterized in that, Before sending the first information to the RAN node, it further includes: Receive the fourth information from the RAN node, where the fourth information includes the TA list currently supported by the RAN node; Determine the update period of the TA list according to the fourth information.
30. The TA management device according to claim 29, characterized in that, The fourth information further includes at least one of the following: The effective duration of the TA list currently supported by the RAN node; The time when the RAN node sends the fourth information.
31. The TA management device according to claim 29 or 30, characterized in that, The determining the update period of the TA list according to the fourth information includes: Determine the update period of the TA list according to the load information of the core network and / or the RAN node, the energy-saving information of the RAN node, and the fourth information.
32. The TA management device according to claim 31, wherein The determining the update period of the TA list according to the fourth information includes: If the core network has stored the ephemeris information of the RAN node, calculate the TA list supported by the RAN node according to the ephemeris information of the RAN node; If the TA list included in the fourth information is consistent with the TA list calculated by the core network according to the stored ephemeris information, determine the update period of the TA list according to the load information, the energy-saving information of the RAN node, the ephemeris information stored by the core network, and the effective duration of the TA list; If the TA list included in the fourth information is inconsistent with the TA list calculated by the core network according to the stored ephemeris information, determine the target TA list; determine the update period of the TA list according to the load information, the energy-saving information of the RAN node, the ephemeris information corresponding to the target TA list, and the effective duration of the target TA list.
33. The TA management device according to claim 32, wherein The determining the target TA list includes: Obtain the updated ephemeris information of the RAN node from the network management or other network elements; calculate the target TA list according to the updated ephemeris information; or, Determine the TA list calculated by the core network as the target TA list; or, Send the second information to the RAN node; obtain the updated TA list from the RAN node; determine the updated TA list of the RAN node as the target TA list; or, Adjust the ephemeris information stored in the core network according to the TA list included in the fourth information; calculate the target TA list according to the adjusted ephemeris information.
34. The TA management device according to any one of claims 27 to 33, characterized in that, After receiving the third information from the RAN node, it further includes: If the core network has stored the ephemeris information of the RAN node, calculate the TA list supported by the RAN node according to the ephemeris information of the RAN node, and perform the following operations: If the TA list calculated by the core network according to the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network obtains the updated ephemeris information of the RAN node from the network management or other network elements, calculate and store the TA list supported by the RAN node according to the updated ephemeris information; or, If the TA list calculated by the core network according to the stored ephemeris information is inconsistent with the TA list included in the third information, and the core network sends the second information to the RAN node, wait for the updated TA list from the RAN node, or store the TA list calculated by the core network according to the stored ephemeris information.
35. The TA management device according to claim 34, characterized in that, It further includes: Send a response message indicating that the TA list configuration is completed to the RAN node.
36. The TA management device according to any one of claims 27 to 33, characterized in that, The triggering conditions for receiving the second information include at least one of the following: There is no intersection between the TA list supported by the RAN node calculated by the core network and the TA list last sent by the RAN node to the core network; The valid duration of the TA list stored in the core network expires; The core network needs to notify the RAN node to request updated ephemeris information from the network management or other network elements.
37. A non-transitory readable storage medium, characterized in that, The non-transitory readable storage medium stores a computer program, and the computer program is used to cause the processor to execute the method according to any one of claims 1 to 17.