Communication method and communication device

Abstract

The invention provides a synchronization method. The synchronization method comprises the steps that first network equipment determines that terminal equipment is interested in clock-related information; when the terminal device is in an inactive state, the first network device sends a first message to the second network device, and the first message indicates that the terminal device sends clock related information in the coverage range of the second network device. The situation that the second network device cannot sense the terminal device in the inactive state and cannot provide clock related information for the terminal device is avoided, the second network device is indicated to be the terminal device through the first message, and the clock related information is sent in the coverage range of the second network device. Even if the terminal device which is in the inactive state and interested in the clock-related information moves out of the coverage range of the first network device (for example, the coverage range of the second network device), the terminal device can still obtain the clock-related information, so that related applications / services can run normally.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly, to a communication method and a communication device. Background Art

[0002] The current 5th generation (5G) system defined in the 3rd generation partnership project (3GPP) standard supports high-precision timing services over the air interface. The network device can provide 5G high-precision time to the terminal device through air interface messages, so as to achieve high-precision clock synchronization between the terminal device and the network device.

[0003] Currently, the radio access network notification area (RNA) configured for an Inactive terminal device contains cells corresponding to multiple network devices. Among them, when the terminal device enters the Inactive state, only the network device that provides services to the terminal device (or called the last serving gNB) can sense whether the terminal device needs to obtain clock-related information, and other network devices within the coverage of the RNA cannot sense whether the terminal device needs to obtain clock-related information. If the Inactive terminal device moves out of the coverage of the last serving gNB, the last serving gNB cannot provide clock-related information to the terminal device, and other network devices cannot sense whether the terminal device needs to obtain clock-related information, resulting in the terminal device being unable to obtain clock-related information or unable to sense whether the clock-related information has changed, causing the related applications of the terminal device to malfunction due to the loss of clock-related information. Summary of the Invention

[0004] This application provides a communication method and a communication device, enabling an Inactive terminal device interested in clock-related information to obtain clock-related information and ensuring the normal operation of related applications / services of the terminal device.

[0005] In a first aspect, a communication method is provided. This method can be executed by a first network device. Here, the first network device can refer to the first network device itself, or a processor, module, chip, or chip system in the first network device that implements this method. This application makes no limitation in this regard. The method includes:

[0006] The first network device determines that the terminal device is interested in clock-related information; when the terminal device is in the inactive state, the first network device sends a first message to the second network device, and the first message instructs to send clock-related information for the terminal device within the coverage area of the second network device.

[0007] It should be understood that the terminal device being interested in clock-related information can be understood as that the relevant applications or relevant services of the terminal device require clock-related information for normal operation, or that the terminal device has a need for clock-related information, or that the terminal device needs to obtain clock-related information.

[0008] It should be understood that the first network device sends the first message to the second network device. Here, whether the inactive terminal device is within the coverage area of the second network device is not limited in this application.

[0009] According to the method provided in this application, the first network device determines that the terminal device is a terminal device interested in clock-related information. When the terminal device is in the inactive state, the first network device sends the first message to the second network device. When the terminal device interested in clock-related information is in the inactive state, the first network device instructs the second network device through the first message to send clock-related information for the terminal device within the coverage area of the second network device. Thus, it is avoided that when the inactive terminal device moves into the coverage area of the second network device, the second network device cannot perceive the terminal device and cannot provide clock-related information for the terminal device in a timely manner, ensuring that the inactive terminal device interested in clock-related information can still obtain clock-related information even if it moves outside the coverage area of the serving network device, and ensuring the normal operation of the relevant applications / services of the terminal device.

[0010] In combination with the first aspect, in some possible implementation manners, the first network device determining that the terminal device is interested in clock-related information includes:

[0011] The first network device receives first indication information from a third network device, where the first indication information is used to indicate that the terminal device is interested in the clock-related information, and the third network device is the network device that provided services for the terminal device before the terminal device accessed the first network device; the first network device determines that the terminal device is interested in the clock-related information according to the first indication information.

[0012] It should be understood that the first network device receives the first indication information from the previous network device (such as the third network device) that provided coverage for the terminal device, and determines that the terminal device is interested in clock-related information.

[0013] In combination with the first aspect, in some possible implementation manners, the first network device receives second indication information of the terminal device in the connected state, where the second indication information is used to indicate that the terminal device is interested in the clock-related information; the first network device determines that the terminal device is interested in the clock information according to the second indication information.

[0014] It should be understood that when the terminal device is in the connected state, the terminal device may indicate to the first network device that the terminal device is interested in the clock-related information.

[0015] In combination with the first aspect, in some possible implementation manners, the method further includes: the first network device sends a second message to the terminal device, where the second message instructs the terminal device to enter the inactive state from the connected state, and the second message includes information indicating a first RNA, and the first RNA includes the coverage range of the second network device.

[0016] It should be understood that the first RNA includes the coverage range of the second network device, and the first RNA includes all or part of the coverage range of the second network device. Or it can be understood that the first RNA includes one or more cells managed by the second network device.

[0017] It should be understood that when the first network device sends a first message to the second network device, the first network device also sends a second message to the terminal device, and the second message is used to instruct the terminal device to enter the inactive state from the connected state. The second message may further include information indicating the first RNA configured by the first network device for the terminal device.

[0018] It should be further understood that the second message may be carried in a radio resource control (RRC) release message sent by the first network device to the terminal device, or sent through a separate signaling.

[0019] In combination with the first aspect, in some possible implementation manners, the first message includes the first identification information of the terminal device and / or information about the coverage range of the second network device.

[0020] Optionally, the first message may include the first identification information of the terminal device and / or information indicating the first RNA (for example, range information of the first RNA).

[0021] In combination with the first aspect, in some possible implementation manners, the first message includes the clock-related information and / or duration information of a timer, and the duration information of the timer is used to indicate the duration for maintaining the terminal device interested in the clock-related information.

[0022] In combination with the first aspect, in some possible implementations, the clock-related information includes clock information and / or clock synchronization status information.

[0023] It should be understood that the clock-related information can be used to achieve high-precision clock synchronization between the terminal device and the network device (the first network device or the second network device). The clock information in this application can indicate 5G clock information or 6G clock information, and the clock synchronization status information can refer to 5G clock synchronization status information or 6G clock synchronization status information. This application does not make any limitations in this regard.

[0024] It should be understood that the clock synchronization status information can include one or more of the following: synchronization status, whether the time can be continuously traced back to Coordinated Universal Time (UTC), whether the time can be traced back to the time of the Global Navigation Satellite System (GNSS), clock frequency stability, clock accuracy, and clock source.

[0025] In combination with the first aspect, in some possible implementations, the method further includes: the first network device updates the terminal devices that are interested in the clock-related information and are managed by the first network device.

[0026] In combination with the first aspect, in some possible implementations, when the first network device determines that there are terminal devices that are interested in the clock-related information and are managed by the first network device, the first network device sends the clock-related information.

[0027] It should be understood that when the first network device determines that there are terminal devices that are interested in the clock-related information and are managed by the first network device, the first network device can determine that the terminal device is a terminal device interested in the clock-related information based on the context information of the terminal device. The terminal device is within the coverage area of the first network device, that is, the terminal device belongs to the terminal devices that are interested in the clock-related information and are managed by the first network device.

[0028] In combination with the first aspect, in some possible implementations, when the RNA of the terminal device is updated, the method further includes: the first network device sends a third message to the network devices whose coverage areas belong to the first RNA. The third message is used to indicate that the terminal device interested in the clock-related information leaves the first RNA.

[0029] It should be understood that the third message can include the first identification information of the terminal device and / or the range information of the first RNA.

[0030] It should also be understood that the coverage area in the present application that belongs to the first RNA for a network device may mean that the entire coverage area corresponding to the network device is within the first RNA, or that part of the coverage area corresponding to the network device is within the first RNA.

[0031] It should also be understood that the third message is used to indicate that a terminal device interested in clock-related information leaves the first RNA. It can be understood that: the third message is used to indicate that a terminal device interested in clock-related information leaves the area corresponding to the first RNA; or the third message can be used to indicate that the terminal device interested in the clock-related information leaves the coverage area of a certain network device whose coverage area belongs to the first RNA. Among them, a certain network device can be the network device within the first RNA as described above.

[0032] It should also be understood that a terminal device interested in clock-related information leaving the first RNA may mean that the RNA configured by the network device for the non-active terminal device interested in clock-related information does not include the first RNA, or that the terminal device is no longer in the non-active state (for example, the terminal device changes from the non-active state to the connected state).

[0033] Based on the above technical solution, when the RNA of the terminal device is updated, assuming that the terminal device moves from the first RNA configured by the first network device to the second RNA, the first network device may send a third message to the network device whose coverage area belongs to the first RNA. The third message is used to indicate that the terminal device leaves the first RNA. Among them, there may be the same area between the first RNA and the second RNA, or the first RNA and the second RNA are completely different, which is not limited in the present application. When the RNA of the terminal device is updated and the first network device sends the third message to the network device whose coverage area belongs to the first RNA, it can enable the network device whose coverage area belongs to the first RNA to sense the departure of the terminal device, so that it can update the terminal devices interested in clock-related information managed by itself, enabling the network device to send clock-related information as needed, and avoiding the situation that the network device does not sense the departure of the terminal device after the RNA of the terminal device is updated and still continuously sends clock-related information, resulting in waste of resources and unnecessary interference between network devices.

[0034] Combined with the first aspect, in some possible implementation manners, when the RNA of the terminal device is updated, the method further includes: the first network device sends a fourth message to the network device within the coverage area of the second RNA. The fourth message is used to indicate that the terminal device interested in the clock-related information joins the second RNA.

[0035] It should be understood that the fourth message may include the second identification information of the terminal device and / or the range information of the second RNA.

[0036] It should also be understood that the coverage area in the present application belonging to the network device within the second RNA may mean that the entire coverage area corresponding to the network device is within the second RNA, or that a part of the coverage area corresponding to the network device is within the second RNA.

[0037] It should also be understood that a terminal device interested in clock-related information joining the first RNA may mean that the RNA configured by the network device for the non-active terminal device interested in clock-related information includes the second RNA.

[0038] It should also be understood that the fourth message is used to instruct a terminal device interested in clock-related information to join the second RNA, which can be understood as the fourth message being used to instruct to send clock-related information for the terminal device within the coverage area of a certain network device, or to indicate that there is an overlapping area between the coverage area corresponding to the certain network device and the second RNA. Among them, the certain network device may be the network device within the second RNA as described above.

[0039] Based on the above technical solution, when the RNA of the terminal device is updated, assuming that the terminal device moves from the first RNA configured by the first network device to the second RNA, the first network device may send a fourth message to the network device whose coverage area belongs to the second RNA, and the fourth message is used to instruct the terminal device to join the second RNA. When the RNA of the terminal device is updated and the first network device sends the fourth message to the network device whose coverage area belongs to the second RNA, it can enable the network device whose coverage area belongs to the second RNA to timely learn that the terminal device interested in clock-related information joins the second RNA, ensure the second network device to send clock-related information, and ensure the normal operation of the relevant services / applications of the terminal device.

[0040] Combined with the first aspect, in some possible implementation manners, when the RNA of the terminal device is updated, the method further includes: the first network device sends a fifth message to the network device whose coverage area belongs to the first RNA, and the fifth message is used to indicate that the information of the terminal device interested in the clock-related information has changed.

[0041] Based on the above technical solution, when the RNA of the terminal device is updated, the first network device may send a fifth message to the network device whose coverage area belongs to the first RNA, and the fifth message is used to indicate that the information of the terminal device has changed, so that the network device whose coverage area belongs to the first RNA can update the relevant information of the non-active terminal device it manages and interested in clock-related information (for example, update the identification information and duration), and ensure the normal operation of the relevant services / applications of the terminal device.

[0042] In combination with the first aspect, in some possible implementations, the fifth message includes the first identification information of the terminal device.

[0043] In combination with the first aspect, in some possible implementations, the fifth message further includes one or more of the following: the second identification information of the terminal device, the range information of the first RNA, the clock-related information, and the duration information of the timer.

[0044] In combination with the first aspect, in some possible implementations, the method further includes: the first network device determines that the RNA of the terminal device has been updated according to one or more of the following: the context information of the terminal device, the change of the terminal device from the inactive state to the connected state, and the small data transmission (SDT) process of the terminal device.

[0045] It should be understood that the first network device can determine that the RNA of the terminal device has been updated according to one or more of the context information of the terminal device, the change of the terminal device from the inactive state to the connected state, and the SDT process of the terminal device.

[0046] It should also be understood that the RNA of the terminal device has been updated, and the triggering factor or the reason for the update is related to one or more of the context information of the terminal device, the change of the terminal device from the inactive state to the connected state, and the SDT process of the terminal device.

[0047] In a second aspect, a communication method is provided. This method can be executed by a second network device. Here, the second network device can refer to the second network device itself, or a processor, module, chip, or chip system in the second network device that implements this method. This application does not make any limitations in this regard. The method includes:

[0048] The second network device receives a first message from the first network device. The first message instructs a terminal device in the inactive state to send clock-related information within the coverage area of the second network device. The second network device, according to the first message, sends the clock-related information within the coverage area of the second network device indicated by the first message.

[0049] It should be understood that the coverage area of the second network device indicated by the first message can be one or more cells managed by the second network device.

[0050] According to the method provided in this application, the second network device receives the first message and sends clock-related information within the coverage area of the second network device indicated by the first message. This avoids the problem that when a non-active terminal device moves into the coverage area of the second network device, the second network device cannot detect the terminal device and cannot provide clock-related information to the terminal device in a timely manner, ensuring that non-active terminal devices interested in clock-related information can still obtain clock-related information even if they move outside the coverage area of the serving network device, and ensuring the normal operation of related applications / services of the terminal device.

[0051] In combination with the second aspect, in some possible implementation manners, the first message includes the first identification information of the terminal device and the coverage area of the second network device.

[0052] Optionally, the first message may further include information indicating the first RNA.

[0053] In combination with the second aspect, in some possible implementation manners, the first message includes the clock-related information and / or the duration information of the timer, and the duration information of the timer is used to indicate the duration for maintaining the terminal device interested in the clock-related information.

[0054] In combination with the second aspect, in some possible implementation manners, the clock-related information includes clock information and / or clock synchronization status information.

[0055] In combination with the second aspect, in some possible implementation manners, the method further includes that the second network device sends the clock-related information.

[0056] In combination with the second aspect, in some possible implementation manners, the method further includes:

[0057] The second network device updates the terminal devices managed by the second network device that are interested in the clock-related information according to the first message.

[0058] In combination with the second aspect, in some possible implementation manners, when the RNA of the terminal device is updated, the method further includes: the second network device receives a third message from the first network device, and the third message is used to indicate that the terminal device interested in the clock-related information leaves the first RNA.

[0059] It should be understood that the third message may include the first identification information of the terminal device and / or the information indicating the first RNA. Among them, the information indicating the first RNA in this application may be the range information of the first RNA, or the area identification information of the first RNA, etc., which is not limited in this application.

[0060] It should also be understood that the departure of a terminal device interested in clock-related information from the first RNA may mean that the RNA configured by a network device (e.g., the first network device, the second network device) for a non-active terminal device interested in clock-related information does not include the first RNA, or that the terminal device is no longer in the non-active state (e.g., the terminal device changes from the non-active state to the connected state).

[0061] Based on the above technical solution, when the RNA of the terminal device is updated, assuming that the terminal device moves from the first RNA configured by the first network device to the second RNA, the first network device may send a third message to a network device (e.g., the second network device) whose coverage area belongs to the first RNA. Correspondingly, the second network device receives the third message from the first network device. When the RNA of the terminal device is updated and the second network device receives the third message from the first network device, the second network device determines, based on the third message, that a non-active terminal device interested in clock-related information located within the first RNA has left the area. Thus, the second network device can timely update the terminal devices interested in clock-related information that it manages itself, avoiding the situation where the second network device fails to perceive the departure of the terminal device and still continuously sends clock-related information, resulting in resource waste and unnecessary interference between network devices.

[0062] Combined with the second aspect, in some possible implementation manners, when the RNA of the terminal device is updated, the method further includes: the second network device receives a fourth message from the first network device, where the fourth message is used to indicate that the terminal device interested in the clock-related information joins the second RNA.

[0063] It should be understood that the fourth message may include second identification information of the terminal device and / or range information of the second RNA.

[0064] It should also be understood that when the coverage area of the second network device belongs to both the first RNA and the second RNA, that is, the second network device receives the third message and the fourth message from the first network device, the third message and the fourth message may be carried in the same signaling and sent by the first network device to the second network device, or the third message and the fourth message are respectively carried in different signaling and sent by the first network device to the second network device. This application does not make any limitation in this regard.

[0065] It should also be understood that the joining of a terminal device interested in clock-related information to the first RNA may mean that the RNA configured by (e.g., the first network device, the second network device) for a non-active terminal device interested in clock-related information includes the second RNA.

[0066] Based on the above technical solution, the RNA of the terminal device is updated. Assume that the terminal device moves from the first RNA configured by the first network device to the second RNA. The first network device may send a fourth message to a network device (such as the second network device) whose coverage area belongs to the second RNA. The fourth message is used to indicate that the terminal device joins the second RNA. Since the RNA of the terminal device is updated and the first network device sends the fourth message to the second network device, network devices whose coverage area belongs to the second RNA can be informed in a timely manner that the terminal device interested in clock-related information joins the second RNA, ensuring that the second network device sends clock-related information and ensuring the normal operation of services / applications related to the terminal device.

[0067] In combination with the second aspect, in some possible implementation manners, when the RNA of the terminal device is updated, the method further includes: the second network device sends a third message to a network device whose coverage area belongs to the first RNA. The third message is used to indicate that the terminal device interested in the clock-related information leaves the first RNA.

[0068] It should be understood that assume that the RNA of the terminal device is updated, and the second network device is a new service network device that provides services for the terminal device. The second network device obtains the context of the terminal device, that is, the second network device can send a third message to a network device whose coverage area belongs to the first RNA, for indicating that the terminal device leaves the first RNA.

[0069] In combination with the second aspect, in some possible implementation manners, when the RNA of the terminal device is updated, the method further includes: the second network device sends a fourth message to a network device whose coverage area belongs to the second RNA. The fourth message is used to indicate that the terminal device interested in the clock-related information joins the second RNA.

[0070] It should be understood that assume that the RNA of the terminal device is updated, and the second network device is a new service network device that provides services for the terminal device. The second network device obtains the context of the terminal device, that is, the second network device can send a fourth message to a network device whose coverage area belongs to the second RNA, for indicating that the terminal device joins the second RNA.

[0071] In combination with the second aspect, in some possible implementation manners, when the RNA of the terminal device is updated, the reason for the update is related to one or more of the following: the context information of the terminal device, the change of the terminal device from the inactive state to the connected state, and the small data transfer (SDT) process of the terminal device.

[0072] It should be understood that when the second network device sends a third message to a network device whose coverage area belongs to the first RNA, and / or when the second network device sends a fourth message to a network device whose coverage area belongs to the second RNA, the second network device may determine that the RNA of the terminal device has been updated according to one or more of the following: the context information of the terminal device, the change of the terminal device from the inactive state to the connected state, and the small data transfer (SDT) process of the terminal device.

[0073] In a third aspect, a communication device is provided. The device includes: a processing unit, configured to determine that a terminal device is interested in clock-related information; and a transceiver unit, configured to send a first message to the second network device when the terminal device is in the inactive state, where the first message indicates to send the clock-related information within the coverage area of the second network device for the terminal device.

[0074] The transceiver unit may perform the receiving and sending processes in the foregoing first aspect, and the processing unit may also perform other processing operations in the foregoing first aspect except for receiving and sending.

[0075] In a fourth aspect, a communication device is provided. The device includes: a transceiver unit, configured to receive a first message from a first network device, where the first message indicates to send the clock-related information within the coverage area of a second network device for the terminal device; and a transceiver unit, configured to send the clock-related information to the coverage area of the second network device indicated by the first message.

[0076] The transceiver unit may perform the receiving and sending processes in the foregoing second aspect.

[0077] In a possible implementation manner, the processing unit may also perform other processing operations in the foregoing second aspect except for receiving and sending.

[0078] In a fifth aspect, the present application provides a communication device. The communication device includes a processor, configured to implement the method in any implementation manner of the foregoing first aspect to the second aspect. The processor is coupled to a memory, and the memory is used to store instructions and data. When the processor executes the instructions stored in the memory, the method in any implementation manner of the foregoing first aspect to the second aspect can be implemented.

[0079] Optionally, the communication device may further include a memory. Optionally, the memory may be coupled to the processor. Optionally, the communication device may further include a communication interface, and the communication interface is used for the device to communicate with other devices. Exemplarily, the communication interface may be a transceiver, a hardware circuit, a bus, a module, a pin, or other types of communication interfaces.

[0080] In one example, the communication device may be a network device, such as an access network device, or a device, module, or chip disposed in the network device, or a device that can be used in combination with the network device.

[0081] In another example, the communication device may be a terminal device, or a device, module, or chip disposed in the terminal device, or a device that can be used in combination with the terminal device.

[0082] In a sixth aspect, the present application provides a communication system, including at least one of a terminal device and a first network device. The terminal device is configured to execute the method provided in any one of the implementation manners of the first aspect, and the first network device is configured to execute the method provided in any one of the implementation manners of the second aspect as described above.

[0083] In a seventh aspect, the present application further provides a computer program, which, when running on a computer, causes the computer to execute the method described in any one of the implementation manners of the first aspect and the second aspect.

[0084] In an eighth aspect, the present application further provides a computer program product, including instructions, which, when running on a computer, cause the computer to execute the method described in any one of the implementation manners of the first aspect and the second aspect.

[0085] In a ninth aspect, the present application further provides a computer-readable storage medium, in which a computer program or instructions are stored, which, when running on a computer, cause the computer to execute the method described in any one of the implementation manners of the first aspect and the second aspect.

[0086] In a tenth aspect, the present application further provides a chip, which is configured to read a computer program stored in a memory and execute the method described in any one of the implementation manners of the first aspect and the second aspect; or the chip includes a component for executing the method described in any one of the implementation manners of the first aspect and the second aspect.

[0087] In an eleventh aspect, the present application further provides a chip system, which includes a processor for supporting a device to implement the method described in any one of the implementation manners of the first aspect and the second aspect. In a possible design, the chip system further includes a memory for storing necessary programs and data of the device. The chip system may be composed of chips or may include chips and other discrete devices.

[0088] In a twelfth aspect, a communication device is provided, which is used to execute the method provided in any one of the first aspect to the second aspect above. Specifically, the device may include units and / or modules for executing the method provided in any one of the above implementations of the first aspect to the second aspect, such as a processing unit and / or a communication unit.

[0089] In one implementation, the device is a communication device (such as a terminal device, or a first network device). When the device is a communication device, the communication unit may be a transceiver, or an input / output interface; the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0090] In another implementation, the device is a chip, a chip system or a circuit used in a communication device. When the device is a chip, a chip system or a circuit used in a device, the communication unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc. on the chip, the chip system or the circuit; the processing unit may be at least one processor, a processing circuit or a logic circuit, etc. Description of the Drawings

[0091] Figure 1 is a schematic diagram of a communication system 100 applicable to an embodiment of the present application.

[0092] Figure 2 is a schematic diagram of an application architecture applicable to an embodiment of the present application.

[0093] Figure 3 is a schematic diagram of a base station indicating 5G time to a terminal device by broadcasting.

[0094] Figure 4 is a schematic diagram of a base station indicating 5G time to a terminal device by unicasting.

[0095] Figure 5 is a schematic flow chart of a process for a terminal device to obtain 5G clock synchronization status information.

[0096] Figure 6 is a schematic diagram of a scenario.

[0097] Figure 7 is a schematic flow chart of a communication method provided by an embodiment of the present application.

[0098] Figure 8 is a schematic flow chart of another communication method provided by an embodiment of the present application.

[0099] Figure 9 is a schematic flow chart of another communication method provided by an embodiment of the present application.

[0100] Figure 10 It is a schematic flowchart of another communication method provided by an embodiment of the present application.

[0101] Figure 11 It is a schematic flowchart of another communication method provided by an embodiment of the present application.

[0102] Figure 12 It is a schematic structural diagram of a communication device 1200 provided by an embodiment of the present application.

[0103] Figure 13 It is a schematic structural diagram of a communication device 1300 provided by an embodiment of the present application. Detailed implementation manners

[0104] Next, the technical solutions in the present application will be described with reference to the accompanying drawings.

[0105] The technical solutions provided by the present application can be applied to various communication systems, such as: the fifth generation (5G) or new radio (NR) system, the long term evolution (LTE) system, the LTE frequency division duplex (FDD) system, the LTE time division duplex (TDD) system, etc. The technical solutions provided by the present application can also be applied to future communication systems, such as the sixth generation mobile communication system. The technical solutions provided by the present application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine type communication (MTC), and the Internet of Things (IoT) communication system or other communication systems. Hereinafter, the 5G system will be taken as an example for illustrative purposes.

[0106] Figure 1 It is a schematic diagram of an example of a communication system applicable to the present application. The communication system 100 may include at least one network device, such as Figure 1 the network device 110 shown. The communication system 100 may further include at least one terminal device, such as Figure 1 the terminal device 120 shown. Among them, the network device 110 and the terminal device 120 can determine the propagation delay between the network device 110 and the terminal device 120 by sending reference signals to each other.

[0107] The technical solution provided by this application can also be applicable to the sidelink (SL) communication scenario. At this time, Figure 1 the network device 110 in Figure 2 can also be replaced by another terminal device, as

[0108] Figure 2 shown. Figure 2 Figure 8 is another schematic diagram of a communication system applicable to this application. The communication system 200 may include at least two terminal devices, such as

[0109] shown in the terminal device 210 and the terminal device 220. Among them, the terminal device 210 and the terminal device 220 can determine the propagation delay between the terminal device 210 and the terminal device 220 by sending reference signals to each other.

[0109] To facilitate the understanding of the embodiments of this application, the technical solution of this application will be mainly introduced below by taking the Figure 1 shown communication system as an example.

[0110] The terminal device in the embodiments of this application can also be referred to as a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile platform, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.

[0111] The terminal device can be a device that provides voice / data to users. For example, it can be a handheld device with wireless connection function, a vehicle-mounted device, etc. Currently, some examples of terminals are: mobile phone, tablet computer, laptop computer, palmtop computer, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing devices connected to a wireless modem, wearable device, terminal device in a 5G network or terminal device in a future evolved public land mobile network (PLMN), etc. The embodiments of the present application are not limited thereto.

[0112] By way of example and not limitation, in the embodiments of the present application, the terminal device can also be a wearable device. A wearable device can also be called a wearable intelligent device, which is a general term for devices developed by applying wearable technology to the intelligent design of daily wear, such as glasses, gloves, watches, clothing, shoes, etc. A wearable device is a portable device that is either directly worn on the body or integrated into the user's clothes or accessories. A wearable device is not just a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can achieve complete or partial functions without relying on a smartphone, such as smart watches or smart glasses, etc., and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones, such as various smart bracelets and smart jewelry for physical sign monitoring.

[0113] In the embodiments of the present application, the device for implementing the functions of the terminal device may be the terminal device itself, or a device capable of supporting the terminal device to implement such functions, such as a chip system or a chip, and this device may be installed in the terminal device. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.

[0114] In the embodiments of the present application, the network device may be a device for communicating with the terminal device. This network device may be a macro base station, a micro base station (also known as a small station), a satellite, a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), an access point (AP) in a wireless fidelity (WiFi) system, a wireless relay node, a wireless backhaul node, a transmission point (TP), or a transmission and reception point (TRP), etc. It may also be a gNB or a transmission point (TRP or TP) in a 5G (such as NR) system, one or a group (including multiple antenna panels) of antenna panels of a base station in a 5G system, or, alternatively, a network node constituting a gNB or a transmission point, such as a distributed unit (DU). Or this network device may be a relay station, an access point, and a network device in a future 6G network or a network device in a future evolved PLMN network, etc. The embodiments of the present application do not limit this. The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the network device.

[0115] In a network structure, the network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a radio access network (RAN) device including a CU node and a DU node, or a RAN device including a control plane CU node (CU-CP node) and a user plane CU node (CU-UP node) and a DU node.

[0116] A network device can provide services for a cell. A terminal device can communicate with the cell through transmission resources allocated by the network device (e.g., frequency-domain resources, or in other words, spectrum resources). The cell can belong to a macro base station (e.g., macro eNB or macro gNB, etc.), or can belong to a base station corresponding to a small cell. Here, small cells can include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage range and low transmission power, and are suitable for providing high-rate data transmission services.

[0117] The network device and the terminal device can be in fixed positions or movable. In the embodiments of this application, the network device and the terminal device can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; they can also be deployed on water; and can also be deployed on airplanes, balloons, and satellites in the air. In the embodiments of this application, the scenarios where the network device and the terminal device are located are not limited.

[0118] It should be understood that in the embodiments of this application, there are no special restrictions on the specific forms of the terminal device and the network device, and only exemplary descriptions are given here.

[0119] It should be understood that Figure 1 and Figure 2 are only simplified schematic diagrams for easy understanding by way of example. Other network devices and / or terminal devices may also be included in this communication system, Figure 1 and Figure 2 which are not drawn in the figure.

[0120] To facilitate the understanding of the embodiments of this application, the following briefly describes the terms or technologies involved in this application.

[0121] 1. 5G air interface time synchronization

[0122] In the R16 standard, 5G air interface time synchronization is achieved by the base station indicating the 5G time of a reference point to the UE. The base station can perform 5G timing to the UE through broadcast (system information) or unicast (radio resource control (RRC) signaling).

[0123] The following takes the broadcast method as an example for illustration.

[0124] Figure 3Shows an example schematic diagram of a base station indicating the 5G time to a UE in a broadcast manner (system information SIB9). A specific 5G time T is carried in the SIB9 sent by the base station to the UE. The protocol defines the reference point of this time as the radio frame boundary where the system message window (SI window) containing SIB9 ends, or the radio frame boundary immediately following the end position. As Figure 3 shown in (1) of Figure 3 , if the end position of the SI window where SIB9 is located is exactly the radio frame boundary with a system frame number (SFN) of x, then the time indicated in SIB9 is the 5G time at the end position of the radio frame corresponding to SFN x; as

[0125] The following takes the unicast method as an example for illustration.

[0126] Figure 4 Shows an example schematic diagram of a base station indicating the 5G time in a unicast manner. As Figure 4 shown, the base station sends a DLInformationTransfer message to the UE in a unicast manner in a certain time slot with a system frame number (SFN) of x - 3. The message contains a specific 5G time (denoted as time T) and the corresponding reference point SFN = x. After receiving this unicast message, the UE can perform 5G time synchronization based on the 5G time T corresponding to the end position of the radio frame with SFN = x.

[0127] Since the signal sent by the base station experiences a certain propagation delay (denoted as Tp for example) when reaching the UE through air propagation, when the UE performs 5G time synchronization based on the unicast message, after determining the 5G time T corresponding to the end position of the radio frame with SFN = x, an additional Tp needs to be added to the time T indicated by the base station to obtain the actual 5G synchronization time, that is, the UE needs to perform propagation delay compensation.

[0128] 2. Timing Resilience System (TRS)

[0129] On the basis of the base station in the radio access network providing the 5G clock to the UE, the TRS feature is defined in the current relevant standards. Among them, when the UE accesses the 5G core network, the 5G core network can indicate to the base station which 5G clock synchronization states the UE is interested in, and the base station provides the corresponding 5G clock synchronization state information to the UE according to the UE's requirements.

[0130] For example, the 5G clock synchronization status information includes one or more of the following:

[0131] 1) Synchronization status: locked, holdover, or free run;

[0132] Among them, locked indicates that the 5G clock is locked with the clock source, holdover indicates that the 5G clock is not locked with the clock source but is in a state of maintaining a certain clock accuracy, and free run indicates that the 5G clock is not locked with the clock source and is not in a state of maintaining clock accuracy.

[0133] 2) Whether it can be traced back to the time of Coordinated Universal Time (UTC);

[0134] 3) Whether it can be traced back to the time of the Global Navigation Satellite System (GNSS);

[0135] 4) Clock frequency stability;

[0136] 5) Clock accuracy;

[0137] 6) Clock source.

[0138] For a connected UE, the base station can directly provide the above clock synchronization status information to the UE through the RRC unicast message DLInformationTransfer.

[0139] For an Inactive / Idle UE, the base station needs to first notify the UE that the 5G clock synchronization status has changed. After the UE transitions to the connected state, the base station then provides the 5G clock synchronization status information to the UE through the DLInformationTransfer message.

[0140] Figure 5 Shows a flowchart of the process for an Inactive / Idle UE to obtain 5G clock synchronization status information. Specifically, when the base station side senses a change in the clock synchronization status, it carries a new Event ID in the SIB9 message; after the Inactive / Idle UE reads the Event ID included in the SIB9, if it finds that the Event ID has changed, or the UE finds that the serving base station has changed, it can initiate an RRC connection establishment process or an RRC connection restoration process; when the base station discovers that the UE has transitioned to the connected state and the UE is interested in the clock quality information, it sends the 5G clock synchronization status information to the UE.

[0141] 3. Radio Access Network Notification Area Update (RNA-U)

[0142] The base station transfers the UE to the Inactive state by sending an RRC Release message to the connected UE. The RRC Release message includes a suspendConfig cell, in which the base station configures the following information:

[0143] 1) Radio Access Network Notification Area (RNA): The RNA area can include one or more cells within the coverage of the base station.

[0144] 2) Inactive-radio network temporary identifier (I-RNTI): The Inactive state user identifier assigned by the base station to the UE.

[0145] 3) PeriodicRNAU-TimerValue: Controls the timing length of timer t380 that initiates the periodic RNA-U process.

[0146] Among them, when the UE enters the Inactive state, timer t380 is started.

[0147] When the Inactive UE is moving, under the following conditions, the UE will initiate the RNA-U process:

[0148] 1) Timer t380 expires, and the UE initiates a periodic RNA-U process.

[0149] 2) The UE reselects to a cell that does not belong to the configured RNA range, and the UE initiates a periodic RNA-U process.

[0150] When an Inactive UE initiates the RNA-U process, it needs to execute the RRC connection restoration process: The UE sends an RRC Resume Request message to the currently resident base station (referred to as: new serving gNB, or new gNB), which carries the UE's I-RNTI. The new gNB identifies the serving base station of the UE (referred to as last serving gNB, or anchor base station) based on the UE's I-RNTI. This serving base station is the base station that released the UE into the Inactive state; when the new gNB and the last serving gNB are not the same base station, the new serving gNB initiates a RETRIEVE UE CONTEXT process to the last serving gNB to request the UE context from the last serving gNB. The last serving gNB decides whether to perform anchor relocation, that is, the last serving gNB determines whether to migrate the context of this UE to the new gNB, and the new gNB maintains the Inactive UE. If the last serving gNB determines not to migrate the UE context, it can send an RRC Release message to the UE to transfer the UE to the Inactive state or the Idle state; if the last serving gNB determines to migrate the UE context to the new gNB, after the new gNB obtains the UE context, it can decide to transfer the UE to the connected state, or continue to stay in the Inactive state, or transfer to the Idle state.

[0151] It should be understood that among the cells of multiple base stations included in the RNA area configured by the Inactive UE, only the last serving gNB of the UE can sense whether the UE is interested in clock-related information, and other base stations within the RNA cannot sense whether the UE is interested in clock information and / or clock state synchronization information.

[0152] Figure 6A scenario schematic diagram is shown. When gNB1 transfers the UE to the Inactive state, gNB1 can be referred to as the last serving gNB of the UE. If the UE is interested in clock information, gNB1 can broadcast SIB9 to provide the UE with clock information or indicate whether the clock quality has changed through SIB9. If the Inactive UE moves and moves out of the coverage area of the last serving gNB and into the coverage area of a new base station (such as gNB2), gNB2 cannot know that there is an interested Inactive UE in its coverage area, that is, gNB2 may not broadcast SIB9. In this case, the UE may not be able to receive the clock information or perceive whether the clock quality has changed, which may cause the related applications of the UE to malfunction due to the loss of clock information.

[0153] Regarding the above problems, the current solution is that all base stations broadcast SIB9 to provide clock information. However, since there may be no UE interested in the clock within the coverage area of the base station, the base station still broadcasts SIB9, resulting in unnecessary resource waste for the base station and introducing unnecessary inter-station interference.

[0154] In view of the above problems, the present application provides a communication method and a communication device. The method enables a non-active terminal device interested in clock-related information to obtain the clock-related information, ensuring the normal operation of the related applications / services of the terminal device.

[0155] Figure 7 It is a flowchart schematic diagram of a synchronization method provided by an embodiment of the present application.

[0156] It should be understood that in the embodiments of the present application, the first network device can be understood as the last serving gNB of the terminal device, and the second network device can be understood as the new gNB of the terminal device. As Figure 7 shown, the method may include the following steps:

[0157] 701, the first network device determines that the terminal device is interested in clock-related information.

[0158] Among them, the terminal device being interested in clock-related information can be understood as that the related applications or services of the terminal device require clock-related information for normal operation or work, or that the terminal device has a demand for clock-related information, or that the terminal device needs to obtain clock-related information.

[0159] It should be understood that the first network device can determine that the terminal device is a terminal device interested in clock-related information through the following several ways:

[0160] 1) The 5G core network node (such as the session management function (SMF)) indicates to the first network device that the terminal device is a terminal device interested in clock-related information.

[0161] For example, when a terminal device in the idle state accesses the first network device and enters the connected state, the SMF indicates to the first network device that the terminal device is interested in clock-related information.

[0162] 2) The third network device sends first indication information to the first network device, and the first indication information is used to indicate that the terminal device is interested in clock-related information. Correspondingly, the first network device receives the first indication information from the third network device.

[0163] Wherein, the third network device is the network device that provides services to the terminal device before the terminal device accesses the first network device.

[0164] For example, during the process of the terminal device switching from the third network device to the first network device, the third network device sends first indication information to the first network device. Correspondingly, the first network device receives the first indication information from the third network device, and the first indication information is used to indicate that the terminal device is a terminal device interested in clock-related information.

[0165] 3) The terminal device sends second indication information to the first network device, and the second indication information is used to indicate that the terminal device is interested in clock-related information. Correspondingly, the first network device receives the second indication information from the terminal device.

[0166] For example, during the process of the terminal device accessing the first network device, when the terminal device is in the connected state, the terminal device can send second indication information to the first network device, and the second indication information is used to indicate that the terminal device is interested in clock-related information.

[0167] Wherein, the second indication information may be carried in the RRC message exchanged between the terminal device and the first network device, which is not limited in this application.

[0168] It should be understood that when the terminal device is in the connected state, the first network device can send clock-related information to the terminal device in the unicast manner shown above Figure 4 to the terminal device.

[0169] It should also be understood that the first network device may determine that the terminal device is a terminal device interested in clock-related information through any one or more of the above-mentioned 1), 2), and 3) methods. Among them, in the process of indicating to the first network device that the terminal device is a terminal device interested in clock-related information in the above-mentioned 1), 2), and 3) methods, the specific content of the clock-related information that the terminal device is interested in may also be indicated to the first network device.

[0170] In a possible implementation manner, the clock-related information includes clock information and / or clock synchronization status information.

[0171] It should be understood that the clock information in the embodiments of the present application may be used to indicate 5G clock information and / or sixth-generation (6G) communication system clock information, and the clock synchronization status information may be used to indicate 5G clock synchronization status information and / or 6G clock synchronization status information. The present application does not make any limitations in this regard. Among them, the specific content of the clock information and clock synchronization status information in the present application is similar to the specific content of the clock information and clock synchronization status information introduced above, and will not be introduced one by one here.

[0172] 702, the first network device sends a first message to the second network device.

[0173] Correspondingly, the second network device receives the first message from the first network device.

[0174] It should be understood that the first message is used to indicate to send clock-related information for the terminal device within the coverage area of the second network device. Regarding whether the terminal device is within the coverage area of the second network device, the present application does not make any limitations.

[0175] In a possible implementation manner, the first message may include the first identification information of the terminal device and / or information about the coverage area of the second network device.

[0176] In another possible implementation manner, the first message may include the first identification information of the terminal device and / or information indicating the first RNA. For example, the information indicating the first RNA may be the range information of the first RNA.

[0177] Among them, the first RNA includes the coverage area of the second network device, that is, part or all of the coverage area corresponding to the second network device belongs to the first RNA configured by the first network device for the terminal device, or the first RNA includes one or more cells managed by the second network device.

[0178] It should be understood that the first identification information of the terminal device may be an inactive-radio network temporary identifier (I-RNTI) configured by the first network device for the terminal device. The I-RNTI may be a full I-RNTI or a short I-RNTI. Alternatively, the first identification information may be the identifier (ID) of the terminal device.

[0179] It should also be understood that the information about the coverage area of the second network device may be the coverage area of the second network device included in the first RNA configured by the first network device for the terminal device, or the overlapping part between the first RNA and the entire coverage area corresponding to the second network device.

[0180] It should also be understood that the range information of the first RNA may be: the cell corresponding to the coverage area of the second network device whose coverage area belongs to the first RNA within the first RNA. The range information of the first RNA may be the identification information of one or more cells, or the area identification information of one or more RNAs.

[0181] In a possible implementation manner, the first message may further include clock-related information that the terminal device is interested in and / or the duration information of a timer.

[0182] Among them, the clock-related information that the terminal device is interested in may be the detailed content of the clock-related information that the terminal device is actually interested in, or one or more items of the clock-related information that the terminal device is interested in.

[0183] Among them, the duration information of the timer is used to indicate the duration for maintaining the terminal device that is interested in the clock-related information.

[0184] It should be understood that maintaining the terminal device that is interested in the clock-related information can be understood as the second network device taking the terminal device as a terminal device that is interested in the clock-related information and managed by itself, and sending the clock-related information within the coverage area determined by the first message associated with the terminal device.

[0185] For example, the duration information of the timer may indicate the maintenance / management duration corresponding to the terminal device among the inactive terminal devices that are interested in the clock-related information and managed by the second network device itself.

[0186] According to Figure 7 the method shown, the method may further include step 703:

[0187] 703. The second network device updates the inactive terminal devices that are interested in clock-related information and are managed by the second network device according to the first message.

[0188] For example, after the second network device receives the first message from the first network device, the second network device updates the inactive terminal devices that are interested in clock-related information and are managed by the second network device according to the first message.

[0189] As an example, assume that the terminal device is among the inactive terminal devices that are interested in clock-related information and are managed by the second network device. The second network device restarts the maintenance duration corresponding to the terminal device according to the first message.

[0190] As another example, assume that the terminal device is not among the inactive terminal devices that are interested in clock-related information and are managed by the second network device. The second network device adds the terminal device to the inactive terminal devices that are interested in clock-related information and are managed by the second network device according to the first message, and starts the maintenance duration corresponding to the terminal device.

[0191] It should be understood that in the inactive terminal devices that are interested in clock-related information and are managed by the second network device, each terminal device may correspond to a timer (such as a validity timer), and the timing duration of this timer is the above-mentioned maintenance duration. When the second network device adds the terminal device to the inactive terminal devices that are interested in clock-related information and are managed by the second network device according to the first message, the timer corresponding to the terminal device is started. When the timer corresponding to the terminal device times out, the second network device deletes the terminal device from the inactive terminal devices that are interested in clock-related information and are managed; when the timer corresponding to the terminal device does not time out and the second network device receives the first message, which is used to indicate that the terminal device is interested in clock-related information within the first RNA, the second network device restarts the timer corresponding to the terminal device among the inactive terminal devices that are interested in clock-related information and are managed.

[0192] It should also be understood that the duration information of this timer may be predefined by the protocol, or determined by the first network device and carried in the first message (for example, the first network device configures the periodic radio access network notification area update effective duration RNAU-timer value for the terminal device), or the duration information of the timer is not carried in the first message and is determined by the second network device. This application does not make any limitations in this regard.

[0193] In a possible implementation, the second network device updates the inactive terminal devices that are interested in clock-related information and are managed by the second network device according to the first message. Wherein, the second network device may manage the inactive terminal devices that are interested in clock-related information on a cell granularity.

[0194] For example, the coverage area corresponding to the second network device corresponds to multiple cells. The cells within the coverage area corresponding to the second network device and belonging to the coverage area of the first RNA are cell #1 and cell #2. That is, the second network device updates the list of inactive terminal devices corresponding to cell #1 and cell #2 that are interested in clock-related information according to the first message.

[0195] It should be understood that this step 703 is an internal implementation operation of the second network device and is an optional step.

[0196] 704. The second network device sends clock-related information.

[0197] For example, the second network device sends clock-related information to the coverage area of the second network device indicated in the first message according to the first message.

[0198] Wherein, when the first message includes information indicating the coverage area of the second network device, the second network device may determine to send clock-related information to the coverage area of the second network device indicated in the first message according to the information indicating the coverage area of the second network device in the first message.

[0199] Wherein, when the first message includes information indicating the first RNA, the second network device can learn that the area it manages overlaps with the first RNA according to the information indicating the first RNA, and further determine the area for sending the clock-related information and send the clock-related information.

[0200] It should be understood that the second network device sending the clock-related information can be understood as the second network device performing clock synchronization on the inactive terminal devices within the coverage area that are interested in the clock-related information.

[0201] It should also be understood that the clock-related information may be carried in the SIB9 message of the second network device and sent, or the clock-related information may be sent through a separate signaling. This application does not make any limitations in this regard.

[0202] It should also be understood that this step 704 is an optional step. In the specific operation process, this step 704 is decoupled from the above step 702, that is, this application does not limit that the second network device must perform step 704 to send clock-related information after receiving the first message according to step 702.

[0203] In a possible implementation manner, in combination with step 703 above, the second network device may update the inactive terminal devices that are interested in clock-related information and are managed by the second network device according to the first message, that is, the terminal device is included in the inactive terminal devices that are interested in clock-related information and are managed by the second network device, and the second network device sends clock-related information.

[0204] It should be understood that steps 703 and 704 above take the second network device as an example, and the content of the network device updating the inactive terminal devices that are interested in clock-related information and are managed by itself and sending clock-related information is introduced exemplarily. Of course, the first network device may update the inactive terminal devices that are interested in clock-related information and are managed by the first network device, and determine whether to send clock-related information according to whether there are inactive terminal devices that are interested in clock-related information managed by the first network device. The detailed process is similar to that of the second network device in steps 703 and 704 above, and will not be elaborated here.

[0205] Among them, when the first network device updates the inactive terminal devices that are interested in clock-related information and are managed by the first network device, it does not need to be executed after step 702, that is, after the first network device instructs the terminal device to enter the inactive state from the connected state, the first network device may perform the relevant operations of updating the inactive terminal devices that are interested in clock-related information and are managed by the first network device.

[0206] According to the above Figure 7 shown method, the first network device determines that the terminal device is a terminal device interested in clock-related information. When the terminal device is in the inactive state, the first network device sends a first message to a network device (such as the second network device) whose coverage area belongs to the first RNA. The first message instructs to send clock-related information for the terminal device within the coverage area of the second network device. When the terminal device interested in clock-related information is in the inactive state, the second network device is instructed to send clock-related information through the first message, so as to prevent the second network device from being unable to perceive that the terminal device is a terminal device interested in clock-related information, and ensure that the inactive terminal device interested in clock-related information can still obtain clock-related information even if it moves to the coverage area of other network devices, so that the relevant applications / services can run normally.

[0207] At the same time, network devices (such as the first network device and the second network device) can send clock-related information on demand according to the inactive terminal devices that are interested in clock-related information and are managed by themselves, which can avoid resource waste and unnecessary interference caused by the network device broadcasting clock-related information for a long time, thereby saving resource overhead.

[0208] Based on the above Figure 7 For the method shown above, before step 702, the method may further include the following steps:

[0209] 705. The first network device sends a second message to the terminal device.

[0210] Correspondingly, the terminal device receives the second message from the first network device.

[0211] Wherein, the second message instructs the terminal device to enter the inactive state from the connected state. The second message includes information indicating a first RNA, and the first RNA includes the coverage area of the second network device.

[0212] It should be understood that the first RNA is configured by the first network device for the terminal device.

[0213] It should be understood that the first RNA may include all or part of the coverage area / management area corresponding to one or more network devices. In the embodiments of the present application, the second network device is taken as an example for introduction, which does not have any limiting effect on the method in the present application.

[0214] It should also be understood that the second message may be carried in a release message (RRC release) sent by the first network device to the terminal device, for instructing the terminal device to enter the inactive state from the connected state.

[0215] It should also be understood that when the first network device sends second information to the terminal device and the terminal device enters the inactive state from the connected state, the first network device performs step 702 as described in Figure 7 below.

[0216] Wherein, when the first network device updates an inactive state terminal device that is interested in clock-related information and is managed by the first network device, after the first network device instructs the terminal device to enter the inactive state from the connected state, the first network device may perform operations similar to steps 703 and 704 above. For example, the first network device updates an inactive state terminal device that is interested in clock-related information and is managed by the first network device; when the first network device determines that it manages an inactive state terminal device that is interested in clock-related information, the first network device sends clock-related information.

[0217] Next, the communication method provided by the embodiments of the present application will be introduced exemplarily in combination with different scenarios.

[0218] Scenario 1

[0219] During the RNA-U process of the terminal device, the first network device configures a new RNA (for example, a second RNA) for the terminal device. The following will be combined withFigure 8 and Figure 9 An exemplary introduction is provided to a communication method provided by an embodiment of the present application.

[0220] Figure 8 It is a schematic flowchart of another communication method provided by an embodiment of the present application.

[0221] It should be understood that in the process of the RNA-U initiated by a non-active state terminal device interested in clock-related information within the old RNA (such as the first RNA) configured by the first network device, taking the first network device as gNB1 as an example, the second network device as gNB2 as an example, the network devices within the coverage of the first RNA as gNB1 and gNB2 as an example, and the network devices within the coverage of the second RNA as gNB1, gNB2, and gNB3 as an example, an exemplary introduction is made to Figure 8 the method shown.

[0222] As Figure 8 shown, the method may include the following steps:

[0223] 801. The terminal device sends RRC connection restoration request information to gNB2. Correspondingly, gNB2 receives the RRC connection restoration request information from the terminal device.

[0224] It should be understood that during the RNA-U process, the non-active state terminal device sends RRC connection restoration request information to gNB2. This RRC connection restoration request information is used for the terminal device to request access to gNB2.

[0225] 802. gNB2 sends the first request information to gNB1. Correspondingly, gNB1 receives the first request information from gNB2.

[0226] Wherein, the first request information is used to request the context information of the terminal device from gNB1.

[0227] It should be understood that in the embodiments of the present application, without special instructions, the context information of the terminal device can generally be understood as the complete context information of the terminal device.

[0228] 803. gNB1 determines not to migrate the context information of the terminal device to gNB2.

[0229] For example, after receiving the first request information, gNB1 determines not to migrate the context information of the terminal device to gNB2. It can be understood that gNB1 determines that gNB1 continues to maintain the terminal device.

[0230] It should be understood that step 803 is an internal implementation process of gNB1, that is, this step 803 may not be reflected in the operation process.

[0231] 804. gNB1 sends a UE context retrieval failure message to gNB2. Correspondingly, gNB2 receives the UE context retrieval failure message from gNB1.

[0232] It should be understood that the UE context retrieval failure message (e.g., Retrieve UE Context Failure message) includes a second message. The second message includes a second RNA configured by gNB1 for the UE, and / or second identification information configured by gNB1 for the UE. For example, the second RNA and / or the second identification information are determined by gNB1 based on the UE RNA-U.

[0233] It should be understood that the second message may be carried in the UE context retrieval failure information sent by gNB1 to gNB2, or the second message may be sent by gNB1 to gNB2 through other signaling (e.g., RRCRelease message) or through a separate signaling.

[0234] 805. gNB2 sends the second message to the UE. Correspondingly, the UE receives the second message from gNB2.

[0235] For example, after gNB2 receives the UE context retrieval failure message from gNB1, gNB2 forwards the second message in the UE context retrieval failure message to the UE. The second message is used to instruct the UE to remain in the inactive state. The second message includes information indicating the first RNA.

[0236] It should be understood that gNB1 determines not to migrate the UE context to gNB2. gNB1 configures a second RNA and / or second identification information for the UE. gNB1 further notifies the network devices within the coverage area of the first RNA / second RNA to update the inactive UEs that are interested in the clock-related information managed by themselves. As Figure 8 shown, the network devices within the coverage area of the first RNA / second RNA can be instructed to update the inactive UEs that are interested in the clock-related information managed by themselves in the following manner:

[0237] Method 1

[0238] 806. gNB1 sends a third message to the network devices within the coverage area of the first RNA.

[0239] Correspondingly, the network devices within the coverage area of the first RNA receive the third message from gNB1.

[0240] For example, gNB1 sends the third message to gNB2.

[0241] Wherein, the third message is used to indicate that a terminal device interested in clock-related information leaves the first RNA.

[0242] It should be understood that the third message is used to indicate that a terminal device interested in clock-related information leaves the first RNA. It can be understood that: the third message is used to indicate that a terminal device interested in clock-related information leaves the area corresponding to the first RNA; or the third message can be used to indicate that the terminal device interested in the clock-related information leaves the coverage area of a certain network device whose coverage belongs to the first RNA. A certain network device can be a network device within the above-mentioned first RNA.

[0243] It should be understood that the third message includes the first identification information of the terminal device. Optionally, the third message may further include the range information of the first RNA.

[0244] It should be understood that gNB1 sends a third message to a network device whose coverage is within the range of the first RNA configured by gNB1 for the terminal device. The third message is used to indicate that an inactive terminal device interested in clock-related information has left the coverage range of the network device. Accordingly, the network device whose coverage is within the range of the first RNA deletes the terminal device from the inactive terminal devices interested in clock-related information managed by itself according to the third message.

[0245] 807, gNB1 sends a fourth message to a network device within the coverage of the second RNA.

[0246] Accordingly, the network device within the coverage of the second RNA receives the fourth message from gNB1.

[0247] For example, gNB1 sends the fourth message to gNB2 and gNB3.

[0248] Wherein, the fourth message is used to indicate that an inactive terminal device interested in clock-related information joins the second RNA.

[0249] It should be understood that the fourth message is used to indicate that a terminal device interested in clock-related information joins the second RNA. It can be understood that the fourth message is used to indicate sending clock-related information for the terminal device within the coverage of a certain network device, or indicating that the coverage area corresponding to the certain network device overlaps with the second RNA. Wherein, a certain network device can be a network device within the above-mentioned second RNA.

[0250] It should be understood that the fourth message includes the second identification information of the terminal device and the coverage of the second RNA. Optionally, the fourth message may further include the specific content of the clock-related information interested by the terminal device and the duration information of the timer.

[0251] It should be understood that gNB1 sends a fourth message to a network device whose coverage area is within the range of the second RNA configured by gNB1 for the terminal device. This fourth message is used to indicate that a non-active state terminal device interested in clock-related information has joined the coverage area of this network device. Accordingly, based on the fourth message, this network device adds this terminal device to the non-active state terminal devices interested in clock-related information that it manages.

[0252] It should be understood that when the coverage area of a network device (such as gNB2) belongs to both the range of the first RNA and the range of the second RNA. This gNB2 can receive both the third message from gNB1 and the fourth message from gNB1. The third message and the fourth message can be carried in the same message and sent to gNB2. Accordingly, gNB2 can delete the terminal device from the non-active state terminal devices interested in clock-related information that it manages according to the third message, and add the terminal device to the non-active state terminal devices interested in clock-related information that it manages according to the fourth message.

[0253] Method 2

[0254] 808, gNB1 sends a fifth message to a network device whose coverage area belongs to the range of the first RNA.

[0255] Accordingly, a network device whose coverage area belongs to the range of the first RNA receives the fifth message from gNB1.

[0256] For example, gNB1 sends this fifth message to gNB2. Accordingly, gNB2 receives the fifth message from gNB1.

[0257] Among them, this fifth message is used to indicate that the information of a terminal device interested in clock-related information has changed. This fifth message includes the first identification information of the terminal device.

[0258] It should be understood that after a network device whose coverage area belongs to the range of the first RNA receives the fifth message, according to the first identification information of the terminal device in the fifth message, it restarts the timer corresponding to this terminal device among the non-active state terminal devices interested in clock-related information that it manages.

[0259] Optionally, this fifth message may further include the second identification information of the terminal device, the range information of the first RNA, the clock-related information that the terminal device is interested in, and the duration information of the timer.

[0260] It should be understood that after a network device within the coverage range of the first RNA receives the fifth message, the network device replaces the first identification information of the terminal device with the second identification information and updates the effective duration corresponding to the terminal device according to the duration information of the timer. The network device may also update the specific content of the clock-related information corresponding to the terminal device according to the clock-related information of interest to the terminal device in the fifth message.

[0261] It should be understood that the steps in the above method 1 and method 2 can be executed after step 803 or after step 804, and this application does not make any limitations in this regard.

[0262] 809. gNB1, gNB2, and gNB3 update the non-active terminal devices that are interested in the clock-related information they manage.

[0263] Among them, after step 803, gNB1 can execute step 809. gNB2 and gNB3 execute step 809 respectively after receiving one or more of the third message, the fourth message, and the fifth message from gNB1.

[0264] It should be understood that step 809 is an optional step. Step 809 is similar to step 703 in the above Figure 7 For details, please refer to the detailed introduction in step 703 above, and will not be elaborated here.

[0265] 810. gNB1, gNB2, and gNB3 send the clock-related information as needed.

[0266] For example, when one or more of gNB1, gNB2, and gNB3 determine that there are terminal devices among the non-active terminal devices that are interested in the clock-related information they manage, the network device that determines that there are terminal devices among the non-active terminal devices that are interested in the clock-related information it manages sends the clock-related information.

[0267] It should be understood that step 810 is similar to step 704 in the above Figure 7 For details, please refer to the detailed introduction in step 704 above, and will not be elaborated here.

[0268] It should be understood that both step 809 and step 810 described above are optional steps. Among them, step 809 is an internal implementation operation of gNB1, gNB2, and gNB3. In the specific operation process, this step 809 is an optional step; in step 810, when gNB1, gNB2, and gNB3 each manage inactive terminal devices interested in clock-related information, step 810 is executed; when gNB1, gNB2, and gNB3 each do not manage inactive terminal devices interested in clock-related information, step 810 does not need to be executed. Among them, this step 810 is decoupled from any of the steps 801 to 809 described above.

[0269] According to the above Figure 8 In the method shown, during the RNA-U process of the terminal device in the first RNA, the first network device sends a third message to the network devices within the coverage area belonging to the first RNA to indicate that the terminal device leaves the first RNA, that is, the network devices within the coverage area belonging to the first RNA remove the terminal device from the inactive terminal devices they manage that are interested in clock-related information; the first network device sends a fourth message to the network devices within the coverage area belonging to the second RNA to indicate that the terminal device joins the second RNA, that is, the network devices within the coverage area belonging to the second RNA add the terminal device to the inactive terminal devices they manage that are interested in clock-related information, ensuring that during the RNA-U process of the inactive terminal device, the network device can still timely sense the terminal device and provide clock-related information to the terminal device, ensuring the normal operation of relevant services / data.

[0270] At the same time, network devices (such as gNB1, gNB2, and gNB3) can send clock-related information on demand according to the inactive terminal devices they manage that are interested in clock-related information, thereby avoiding the problem of waste of resources caused by the network device sending unnecessary clock-related information and introducing inter-station interference, and saving resource overhead.

[0271] Figure 9 It is a schematic flowchart of another communication method provided by an embodiment of this application.

[0272] It should be understood that in the process of the inactive terminal device interested in clock-related information initiating RNA-U within the old RNA (such as the first RNA) configured by the first network device, taking the first network device as gNB1 as an example, the second network device as gNB2 as an example, the network devices within the coverage area of the first RNA as gNB1 and gNB2 as an example, and the network devices within the coverage area of the second RNA as gNB1, gNB2, and gNB3 as an example, the Figure 9 shown method is introduced exemplarily.

[0273] As Figure 9 shown, the method may include the following steps:

[0274] 901. The terminal device sends an RRC connection restoration request message to gNB2. Correspondingly, gNB2 receives the RRC connection restoration request message from the terminal device.

[0275] It should be understood that during the RNA-U process, the inactive terminal device sends an RRC connection restoration request message to gNB2. This RRC connection restoration request message is used by the terminal device to request access to gNB2.

[0276] 902. gNB2 sends a first request message to gNB1. Correspondingly, gNB1 receives the first request message from gNB2.

[0277] Among them, this first request message is used to request the context information of the terminal device from gNB1.

[0278] 903. gNB1 determines to migrate the context information of the terminal device to gNB2.

[0279] For example, after gNB1 receives the first request message, gNB1 determines to migrate the context information of the terminal device to gNB2. It can be understood that gNB1 determines that gNB2 will maintain the terminal device.

[0280] It should be understood that step 903 is an internal implementation process of gNB1, that is, this step 903 may not be reflected in the operation process.

[0281] 904. gNB1 sends a retrieve UE context feedback message to gNB2. Correspondingly, gNB2 receives the retrieve UE context feedback message from gNB1.

[0282] It should be understood that this retrieve UE context feedback message (such as a Retrieve UE Context Response message) includes the context information of the terminal device.

[0283] It should also be understood that this retrieve UE context feedback message may include information indicating the first RNA (for example, the range information of the first RNA).

[0284] 905. gNB2 sends a second message to the terminal device. Correspondingly, the terminal device receives the second message from gNB2.

[0285] For example, after gNB2 receives the retrieve UE context feedback message from gNB1, gNB2 determines the second message and sends the second message to the terminal device. This second message instructs the terminal device to remain in the inactive state.

[0286] It should be understood that gNB1 determines to migrate the context information of the terminal device to gNB2. gNB2 configures the second RNA and / or the second identification information for the terminal device, and gNB1 / gNB2 needs to notify the network devices within the coverage of the first RNA / second RNA to update the non-active terminal devices that are interested in the clock-related information managed by themselves. As Figure 9 shown, the network devices within the coverage of the first RNA / second RNA can be instructed to update the non-active terminal devices that are interested in the clock-related information managed by themselves in the following manner:

[0287] Method 3

[0288] 906. gNB1 sends a third message to the network devices within the coverage of the first RNA.

[0289] Correspondingly, the network devices within the coverage of the first RNA receive the third message from gNB1.

[0290] For example, gNB1 sends the third message to gNB2.

[0291] It should be understood that since gNB1 migrates the context information of the terminal device to gNB2, gNB2 knows one or more of the first RNA, the second RNA, the first identification information, and the second identification information corresponding to the terminal device. gNB1 sends a third message to the network devices within the coverage of the first RNA, where gNB1 sends the third message to other network devices within the coverage of the first RNA except gNB2.

[0292] 907. gNB2 sends a fourth message to the network devices within the coverage of the second RNA.

[0293] Correspondingly, the network devices within the coverage of the second RNA receive the fourth message from gNB2.

[0294] For example, gNB2 sends the fourth message to gNB3 and gNB1.

[0295] It should be understood that the specific content and function of the fourth message are similar to those in step 807 above Figure 8 and will not be elaborated here.

[0296] It should also be understood that the above step 906 and step 907 are similar to step 806 and step 807 above Figure 8 and for specific details, please refer to the description above Figure 8 and will not be elaborated here.

[0297] Method 4

[0298] 908, gNB2 sends a fifth message to network devices whose coverage areas fall within the range of the first RNA.

[0299] Correspondingly, network devices whose coverage areas fall within the range of the first RNA receive the fifth message from gNB2.

[0300] Among them, gNB2 receives a retrieved UE context feedback message from gNB1. The retrieved UE context feedback message includes information indicating the first RNA (such as the range information of the first RNA). gNB2 determines the range of the first RNA based on the information indicating the first RNA and sends a fifth message to network devices whose coverage areas fall within the range of the first RNA.

[0301] It should be understood that the specific content and detailed functions of this fifth message are similar to those in step 808 above. For specific details, please refer to the detailed introduction in the above Figure 8 and specifically refer to the detailed introduction in the above Figure 8 for details.

[0302] 909, gNB1, gNB2, and gNB3 update the inactive terminal devices that are interested in clock-related information and are managed by them respectively.

[0303] Among them, after step 903, gNB1 can execute step 909. gNB2 and gNB3 execute step 909 respectively after receiving one or more of the third message, fourth message, and fifth message from gNB1.

[0304] It should be understood that step 909 is similar to step 703 in the above Figure 7 For specific details, please refer to the detailed introduction in step 703 above and will not be elaborated here.

[0305] 910, gNB1, gNB2, and gNB3 send clock-related information as needed.

[0306] For example, when one or more of gNB1, gNB2, and gNB3 determine that there are terminal devices among the inactive terminal devices that are interested in clock-related information and are managed by them respectively, the network device that determines that there are terminal devices among the inactive terminal devices that are interested in clock-related information and are managed by it sends clock-related information.

[0307] It should be understood that step 910 is similar to step 810 in the above Figure 8 For specific details, please refer to the detailed introduction in step 810 above and will not be elaborated here.

[0308] According to the above Figure 9In the method shown, during the RNA-U process of the terminal device, the first network device sends a third message to the network devices within the coverage area of the first RNA to indicate that the terminal device leaves the first RNA. That is, the network devices within the coverage area of the first RNA delete the terminal device from the non-active terminal devices interested in clock-related information managed by themselves. The second network device sends a fourth message to the network devices within the coverage area of the second RNA to indicate that the terminal device joins the second RNA. That is, the network devices within the coverage area of the second RNA add the terminal device to the non-active terminal devices interested in clock-related information managed by themselves, ensuring that when the non-active terminal device moves to the coverage area of the network device within the coverage area of the second RNA, the network device can promptly sense the terminal device and provide clock-related information to the terminal device, ensuring the relevant application / service requirements of the non-active terminal device and improving the user experience.

[0309] Meanwhile, network devices (such as gNB1, gNB2, and gNB3) can send clock-related information on demand according to the non-active terminal devices interested in clock-related information managed by themselves, thereby avoiding the problem of network devices sending unnecessary clock-related information, which may lead to resource waste and introduce inter-station interference, and saving resource overhead.

[0310] Scenario 2

[0311] During the RNA-U process of the terminal device, when the terminal device changes from the non-active state to the connected state, the first network device / second network device instructs the network devices within the coverage area of the first RNA to delete the terminal device from the non-active terminal devices interested in clock-related information managed by themselves. The following will be combined with Figure 10 to exemplarily introduce a communication method provided in an embodiment of the present application.

[0312] Figure 10 It is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0313] It should be understood that in the process of the non-active terminal device interested in clock-related information initiating RNA-U within the old RNA (such as the first RNA) configured by the first network device, taking the first network device as gNB1, the second network device as gNB2, the network devices within the coverage area of the first RNA as gNB1 and gNB2, and the network devices within the coverage area of the second RNA as gNB1, gNB2, and gNB3 as examples, Figure 10 the method shown is exemplarily introduced.

[0314] 1001. The terminal device sends an RRC connection resume request message to gNB2. Correspondingly, gNB2 receives the RRC connection resume request message from the terminal device.

[0315] It should be understood that during the RNA-U process, the inactive terminal device sends an RRC connection resume request message to gNB2. This RRC connection resume request message is used by the terminal device to request access to gNB2.

[0316] 1002. gNB2 sends a first request message to gNB1. Correspondingly, gNB1 receives the first request message from gNB2.

[0317] Wherein, this first request message is used to request the context information of the terminal device from gNB1.

[0318] 1003. gNB1 determines to migrate the context information of the terminal device to gNB2.

[0319] For example, after gNB1 receives the first request message, gNB1 determines to migrate the context information of the terminal device to gNB2. It can be understood that gNB1 determines that gNB2 will maintain the terminal device.

[0320] It should be understood that step 1003 is an internal implementation process of gNB1, that is, this step 1003 may not be reflected in the operation process.

[0321] 1004. gNB1 sends a retrieve UE context feedback message to gNB2. Correspondingly, gNB2 receives the retrieve UE context feedback message from gNB1.

[0322] It should be understood that this retrieve UE context feedback message (such as a Retrieve UE Context Response message) includes the context information of the terminal device.

[0323] It should also be understood that this retrieve UE context feedback message may include information indicating the first RNA (for example, the range information of the first RNA).

[0324] 1005. gNB2 sends an RRC resume message to the terminal device. Correspondingly, the terminal device receives the RRC resume message from gNB2.

[0325] For example, after gNB2 receives the retrieve UE context feedback message from gNB1, gNB2 sends the RRC resume message to the terminal device. This RRC resume message indicates that the terminal device updates from the inactive state to the connected state.

[0326] It should be understood that gNB1 determines to migrate the context information of the terminal device to gNB2. After receiving the context information of the terminal device, gNB2 changes the terminal device from the inactive state to the connected state through an RRC resume message.

[0327] After the terminal device transitions to the connected state, network devices within the coverage of the first RNA do not need to maintain the terminal device in the inactive terminal devices interested in clock-related information under their own management. For example, Figure 10 As shown, the network devices within the coverage of the first RNA can be instructed to update the inactive terminal devices interested in clock-related information under their own management in the following manner:

[0328] Method 5

[0329] 1006. gNB1 sends a third message to network devices within the coverage of the first RNA.

[0330] Correspondingly, network devices within the coverage of the first RNA receive the third message from gNB1.

[0331] For example, gNB1 sends the third message to gNB2.

[0332] It should be understood that since gNB1 migrates the context information of the terminal device to gNB2, gNB2 knows one or more of the first RNA, the second RNA, the first identification information, and the second identification information corresponding to the terminal device. gNB1 sends a third message to network devices within the first RNA coverage, where gNB1 sends the third message to other network devices within the first RNA coverage except gNB2.

[0333] It should also be understood that step 1006 above is similar to step 806 in the above Figure 8 and step 906 in the above Figure 9 For specific details, please refer to the descriptions in the above Figure 8 and Figure 9 and will not be elaborated here.

[0334] Method 6

[0335] 1007. gNB2 sends a third message to network devices within the coverage of the first RNA.

[0336] Correspondingly, network devices within the coverage of the first RNA receive the third message from gNB2.

[0337] For example, gNB2 sends the third message to gNB1.

[0338] Among them, gNB2 receives a UE context retrieval feedback message from gNB1. The UE context retrieval feedback message includes information indicating the first RNA (such as the range information of the first RNA). gNB2 determines the range of the first RNA according to the information indicating the first RNA, and sends a third message to network devices whose coverage ranges belong to the range of the first RNA.

[0339] It should also be understood that step 1007 above is similar to step 806 in Figure 8 above, Figure 9 and step 906 in Figure 8 and Figure 9 above. For specific details, please refer to the descriptions in

[0340] 1008, gNB1 and gNB2 update the inactive terminal devices that are interested in clock-related information and are managed by them respectively.

[0341] Among them, after step 1003, gNB1 may execute step 1008. gNB2 may execute step 1008 after step 1004 or after step 1006.

[0342] It should be understood that step 1008 is similar to step 703 in Figure 7 above. For specific details, please refer to the detailed introduction in step 703 above, and details are not elaborated here.

[0343] 1009, gNB1 and gNB2 send clock-related information as needed.

[0344] For example, when gNB1 and gNB2 determine that there are terminal devices among the inactive terminal devices that are interested in clock-related information and are managed by them respectively, they determine to send clock-related information to the network device where there are terminal devices among the inactive terminal devices that are interested in clock-related information and are managed by them.

[0345] It should be understood that step 1009 is similar to step 810 in Figure 8 above. For specific details, please refer to the detailed introduction in step 810 above, and details are not elaborated here.

[0346] It should also be understood that the method shown above Figure 10 also applies to the case where the terminal device changes from the inactive state to the idle state, and details are not elaborated here one by one.

[0347] According to the above Figure 10In the method shown, when the terminal device transitions from the inactive state to the connected state or the idle state, that is, when the terminal device in the inactive state leaves the inactive state, gNB1 / gNB2 can promptly notify the network devices within the coverage area of the first RNA. The network devices within the coverage area of the first RNA can promptly update the terminal devices in the inactive state that are interested in clock-related information under their management, and send clock-related information as needed, avoiding unnecessary resource waste by the network devices and reducing interference between stations.

[0348] Scenario Three

[0349] During the SDT process of the terminal device, the terminal device remains in the inactive state. The first network device / second network device instructs the terminal device among the terminal devices in the inactive state that are interested in clock-related information and are under its management within the coverage area of the first RNA / second RNA to be updated. The following will be combined with Figure 11 to provide an exemplary introduction to a communication method provided by an embodiment of the present application.

[0350] Figure 11 It is a schematic flowchart of another communication method provided by an embodiment of the present application.

[0351] It should be understood that in the process where the terminal device in the inactive state that is interested in clock-related information initiates an SDT process to the second network device, where the first network device takes gNB1 as an example, the second network device takes gNB2 as an example, the network devices within the coverage area of the first RNA take gNB1 and gNB2 as examples, and the network devices within the coverage area of the second RNA take gNB1, gNB2, and gNB3 as examples, an exemplary introduction to Figure 11 the method shown is provided.

[0352] 1101. The terminal device performs small data transmission (SDT) to gNB2.

[0353] It should be understood that the process of the terminal device in the inactive state initiating an SDT process to gNB2 is similar to the prior art and will not be elaborated here.

[0354] 1102. gNB2 sends a second request message to gNB1.

[0355] Correspondingly, gNB2 receives the second request message from gNB1.

[0356] Among them, the second request message is used to request the context information of the terminal device. The second request message includes SDT indication information.

[0357] It should be understood that after gNB1 receives the second request message, gNB1 determines whether to migrate the context information of the terminal device to gNB2. Wherein gNB1 determines not to migrate the context information of the terminal device to gNB2, as shown in Case 1 of Figure 11 ; gNB1 determines to migrate the context information of the terminal device to gNB2, as shown in Case 2 of Figure 11 .

[0358] Case 1

[0359] 1103, gNB1 determines not to migrate the context information of the terminal device to gNB2.

[0360] For example, after gNB1 receives the second request message, gNB1 determines not to migrate the context information of the terminal device to gNB2. It can be understood that gNB1 determines that gNB1 continues to maintain the terminal device.

[0361] It should be understood that during the SDT process between the terminal device and gNB2, gNB1 will migrate part of the context information of the terminal device to gNB2, and part of the context information of the terminal device is to ensure the smooth progress of the SDT process between the terminal device and gNB2. However, whether gNB1 determines to migrate the context information of the terminal device to gNB2, that is, whether to migrate the complete context information of the terminal device, is determined by the gNB.

[0362] 1104, gNB1 sends a third message to the network device within the coverage of the first RNA.

[0363] Correspondingly, the network device within the coverage of the first RNA receives the third message from gNB1.

[0364] For example, gNB1 sends the third message to gNB2.

[0365] Wherein, the third message is used to indicate that the terminal device interested in the clock-related information leaves the first RNA.

[0366] It should be understood that the second message includes the first identification information of the terminal device. Optionally, the second message may further include the range information of the first RNA.

[0367] It should be understood that the terminal device performs SDT transmission with gNB2, that is, gNB2 can provide clock-related information to the terminal device. gNB1 sends a third message to a network device whose coverage range is within the first RNA configured by gNB1 for the terminal device. This third message is used to indicate that an inactive terminal device interested in clock-related information has left the coverage range of this network device. Accordingly, the network device within the coverage range of this first RNA deletes this terminal device from the inactive terminal devices interested in clock-related information managed by itself according to the third message.

[0368] It should also be understood that when gNB2 is a network device within the coverage range of the first RNA, since the terminal device performs SDT transmission with gNB2, the gNB1 sending the third message to the network device within the coverage range of the first RNA may include: the gNB1 sending the third message to other network devices within the coverage range of the first RNA except gNB2.

[0369] It should also be understood that gNB1 sends the specific content of the clock-related information interested by the terminal device to gNB2. The specific content of the clock-related information interested by the terminal device can be carried in the third message and sent to gNB2, or sent to gNB2 through other signaling bearers.

[0370] It should be understood that when gNB1 determines not to migrate the context information of the terminal device to gNB2, the gNB1 terminates the SDT process of the terminal device. This method may further include:

[0371] 1105, gNB1 sends a message indicating failure to retrieve the terminal device context to gNB2. Accordingly, gNB2 receives the message indicating failure to retrieve the terminal device context from gNB1.

[0372] It should be understood that this message indicating failure to retrieve the terminal device context (such as Retrieve UE Context Failure message) includes a second message. This second message includes the second RNA configured by gNB1 for the terminal device, and / or the second identification information configured by gNB1 for the terminal device. For example, this second RNA and / or second identification information is determined by gNB1 according to the terminal device RNA-U.

[0373] It should be understood that this second message can be carried in the information indicating failure to retrieve the UE context and sent by gNB1 to gNB2, or this second message can be sent by gNB1 to gNB2 through other signaling (such as RRCRelease message) or through a separate signaling.

[0374] It should also be understood that this second message may include a message for indicating termination of the SDT process.

[0375] 1106, gNB2 sends a message to the terminal device to indicate the termination of the SDT process.

[0376] Correspondingly, the terminal device receives the message from gNB2 for terminating the SDT process.

[0377] For example, gNB2 receives a message indicating failure to retrieve the terminal device context from gNB1, and this message for terminating the SDT process is included in the message indicating failure to retrieve the terminal device context. Then gNB2 sends the message for terminating the SDT process to the terminal device.

[0378] It should be understood that the message for terminating the SDT process can be carried in a second message and sent to the terminal device. For example, gNB2 sends an RRCRelease message to the terminal device, and this RRCRelease message is used to indicate the termination of the SDT process. Correspondingly, the terminal device receives this RRCRelease message and terminates the SDT process with gNB2.

[0379] 1107, gNB1 sends a fourth message to a network device whose coverage is within the second RNA.

[0380] Correspondingly, the network device whose coverage is within the second RNA receives the fourth message from gNB1.

[0381] Wherein, the fourth message is used to indicate that a non-active state terminal device interested in clock-related information joins the second RNA.

[0382] It should be understood that gNB1 terminates the SDT process of the terminal device, that is, gNB2 cannot sense whether the terminal device is interested in clock-related information. That is, gNB1 configures the second RNA for the terminal device and sends the fourth message to the network device whose coverage belongs to the second RNA range. The fourth message is used to indicate that a non-active state terminal device interested in clock-related information within the coverage of the second RNA has joined the coverage of the second RNA. Correspondingly, the network device within the coverage of the second RNA adds the terminal device to the non-active state terminal devices interested in clock-related information that it manages according to the fourth message.

[0383] It should be understood that the specific content and functions of the above third message and fourth message are similar to those of the Figures 8 to 10 third message and fourth message in, and for details, please refer to the detailed introduction in the above Figures 8 to 10 .

[0384] Case two

[0385] 1103’, gNB1 determines to migrate the context information of the terminal device.

[0386] For example, after gNB1 receives the second request message, gNB1 determines to migrate the context information of the terminal device to gNB2. It can be understood that gNB2 maintains the terminal device.

[0387] At 1104’, gNB1 sends a UE context retrieval feedback message to gNB2. Correspondingly, gNB2 receives the UE context retrieval feedback message from gNB1.

[0388] It should be understood that the UE context retrieval feedback message includes UE context information.

[0389] At 1105’, gNB1 or gNB2 sends a third message to the network device whose coverage belongs to the first RNA range. Correspondingly, the network device whose coverage belongs to the first RNA range receives the third message from gNB1 or gNB2.

[0390] It should be understood that the third message is similar to the third message above Figures 8 to 10 and will not be elaborated here.

[0391] It should also be understood that after the network device whose coverage belongs to the first RNA range receives the third message, it deletes the terminal device from the non-active terminal devices interested in clock-related information managed by itself according to the third message.

[0392] At 1106’, gNB2 sends a message to the terminal device for indicating the termination of the SDT process.

[0393] Correspondingly, the terminal device receives the message from gNB2 for indicating the termination of the SDT process.

[0394] It should be understood that the terminal device terminates the SDT process according to the message from gNB2 for indicating the termination of the SDT process.

[0395] Optionally, the message for indicating the termination of the SDT process can be carried in an RRC Release message, or the message for indicating the termination of the SDT process can be sent through a separate signaling.

[0396] At 1107’, gNB2 sends a fourth message to the network device whose coverage belongs to the second RNA.

[0397] Correspondingly, the network device within the coverage of the second RNA receives the fourth message from gNB2.

[0398] Wherein, the fourth message is used to indicate that the terminal device interested in clock-related information joins the second RNA.

[0399] It should be understood that gNB1 determines to migrate the context information of the terminal device to gNB2, that is, gNB2 can terminate the SDT process of the terminal device. When gNB2 terminates the SDT process of the terminal device, network devices within the coverage of the second RNA cannot sense whether the terminal device is interested in clock-related information. That is, gNB2 sends the fourth message to network devices within the coverage of the second RNA, which is used to indicate that a non-active terminal device interested in clock-related information has joined the coverage of the network device. Accordingly, the network device within the coverage of the second RNA adds the terminal device to the non-active terminal devices it manages that are interested in clock-related information according to the fourth message.

[0400] It should be understood that the specific content and functions of the above third message and fourth message are similar to those of Figures 8 to 10 the third message and fourth message in Figures 8 to 10 . For details, please refer to the detailed introduction in the above

[0401] 1108, gNB1, gNB2, and gNB3 update the non-active terminal devices they manage that are interested in clock-related information.

[0402] Among them, after step 1106, gNB1 can execute step 1108. After step 1106', or after step 1104', gNB2 can execute step 1108. After step 1107, gNB3 can execute step 1108.

[0403] It should be understood that step 1108 is similar to step 703 in the above Figure 7 . For details, please refer to the detailed introduction in step 703 above and will not be elaborated here.

[0404] 1109, gNB1, gNB2, and gNB3 send clock-related information as needed.

[0405] For example, when gNB1, gNB2, and gNB3 determine that there are terminal devices among the non-active terminal devices they manage that are interested in clock-related information, they determine to send clock-related information to the network device that manages the non-active terminal device in which there is a terminal device and is interested in clock-related information.

[0406] It should be understood that step 1109 is similar to step 810 in the above Figure 8 . For details, please refer to the detailed introduction in step 810 above and will not be elaborated here.

[0407] According to the above Figure 11In the method shown, when the terminal device is in the inactive state, the terminal device initiates the SDT process. The network device (such as gNB2) that performs SDT with the terminal device can sense whether the inactive terminal device is interested in clock-related information. Thus, gNB1 / gNB2 sends a third message to the network devices within the coverage range of the first RNA, which is used to delete the terminal device from the inactive terminal devices interested in clock-related information managed by itself, avoiding unnecessary resource waste of the network device and reducing interference between stations. When gNB1 / gNB2 terminates the SDT process of the terminal device, gNB1 / gNB2 sends a fourth message to the network devices within the coverage range of the second RNA, which is used to add the inactive terminal device interested in clock-related information to the inactive terminal devices interested in clock-related information managed by itself, avoiding the situation where the terminal device cannot obtain clock-related information and ensuring the normal operation of related applications of the terminal device.

[0408] Based on the introduction of the above Scenario 1, Scenario 2, and Scenario 3, during the RNA-U process of the terminal device, gNB1 and / or gNB2 can send a third message to the network devices within the coverage range of the first RNA, and / or send a fourth message to the network devices within the coverage range of the second RNA, etc. These operations enable the inactive terminal device to obtain clock-related information during the RNA update process and ensure its normal operation. At the same time, it enables the network device to update the inactive terminal devices interested in clock-related information managed by itself in a timely manner, avoiding the network device from sending unnecessary clock-related information, reducing resource waste and interference between stations.

[0409] It should be understood that based on the above Figures 8 to 11 introduction, gNB1 can determine the RNA update of the terminal device according to one or more of the following, or the terminal device has performed an RNA update, and the reasons for this update can include one or more of the following: the context information of the terminal device, the change of the terminal device from the inactive state to the connected state, the SDT process of the terminal device. Among them, combined with the above Figure 8 and Figure 9 description, gNB2 requests the context information of the terminal device from gNB1, and gNB1 determines that the terminal device has performed an RNA update; combined with the above Figure 10 description, gNB2 requests and obtains the context information of the terminal device from gNB1, and gNB2 instructs to change the terminal device from the inactive state to the connected state, and gNB1 determines that the terminal device has performed an RNA update; combined with the above Figure 11 description, SDT is performed between the terminal device and gNB2, gNB2 requests the context information of the terminal device from gNB1, and gNB1 determines that the terminal device has performed an RNA update.

[0410] The method embodiments of the present application have been described above in conjunction with the accompanying drawings. Next, the apparatus embodiments of the present application will be described. It can be understood that the descriptions of the method embodiments and the apparatus embodiments can correspond to each other. Therefore, for the parts not described, reference can be made to the previous method embodiments.

[0411] It can be understood that in each of the above method embodiments, the methods and operations implemented by the terminal device can also be implemented by components (such as chips or circuits) applicable to the terminal device, and the methods and operations implemented by the network device can also be implemented by components (such as chips or circuits) applicable to the network device.

[0412] It can be understood that if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0413] It can be understood that in the present application, "first", "second" and various numerical numbers (such as #1, #2, etc.) are used for distinction for the convenience of description, and are not used to limit the scope of the embodiments of the present application. For example, to distinguish different messages, etc., rather than for describing a specific order or sequence. It should be understood that the objects described in this way can be interchanged under appropriate circumstances so as to be able to describe solutions other than the embodiments of the present application.

[0414] It can be understood that in the present application, "protocol" may refer to standard protocols in the communication field, for example, it may include 5G protocols, NR protocols, and related protocols applied to future communication systems. The present application does not limit this. "Pre-defined" may include pre-definition. For example, protocol definition. "Pre-configuration" can be achieved by pre-saving corresponding codes, tables or other means that can be used to indicate relevant information in the device. The present application does not limit its specific implementation manner.

[0415] The above mainly introduces the solutions provided by the embodiments of the present application from the perspective of the interaction between each network element. It can be understood that each network element, such as a transmitting end device or a receiving end device, includes corresponding hardware structures and / or software modules for performing each function in order to implement the above functions. Those skilled in the art should be able to realize that the present application can be implemented in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0416] In the embodiments of the present application, the functional modules of the transmitting device or the receiving device can be divided according to the above method examples. For example, each functional module can be corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiments of the present application is illustrative, only a logical function division, and there can be other division methods in actual implementation. The following will take the example of dividing each functional module corresponding to each function for illustration.

[0417] Figure 12 It is a schematic structural diagram of a communication device provided by the embodiments of the present application.

[0418] The device 1200 includes a transceiver unit 1210 and a processing unit 1220. Among them, the transceiver unit 1210 can be used to implement corresponding communication functions, and the processing unit 1220 can be used to perform data processing.

[0419] Optionally, the transceiver unit 1210 can also be referred to as a communication interface or a communication unit, and it includes a sending unit and / or a receiving unit. The transceiver unit 1210 can be a transceiver (including a transmitter and / or a receiver), an input / output interface (including an input and / or an output interface), a pin or a circuit, etc. The transceiver unit 1210 can be used to execute the sending and / or receiving steps in the above method embodiments.

[0420] Optionally, the processing unit 1220 can be a processor (which can include one or more), a processing circuit with processor functions, etc., and can be used to execute other steps in the above method embodiments except for sending and receiving.

[0421] Optionally, the device 1200 further includes a storage unit, and the storage unit can be a memory, an internal storage unit (such as a register, a cache, etc.), an external storage unit (such as a read-only memory, a random access memory, etc.). The storage unit is used to store instructions, and the above processing unit 1220 executes the instructions stored in the storage unit so that the communication device executes the above method.

[0422] In one design, the device 1200 can correspond to the network device (such as the first network device or the second network device) in the above method embodiments, or a component (such as a chip) of the network device.

[0423] In another design, the device 1200 can correspond to the terminal device in the above method embodiments, or a component (such as a chip) of the terminal device.

[0424] The apparatus 1200 can implement the steps or processes corresponding to those executed by the terminal device in the above method embodiments. Among them, the transceiver unit 1210 can be used to perform the operations related to the transceiver of the terminal device in the above method embodiments, and the processing unit 1220 can be used to perform the internal operations of the device other than transceiver information in the above method embodiments of the terminal device.

[0425] In a possible implementation, the processing unit 1220 is configured to determine that the terminal device is interested in clock-related information; when the terminal device is in an inactive state, the transceiver unit 1210 is configured to send a first message to a second network device, where the first message indicates that the terminal device sends clock-related information within the coverage of the second network device.

[0426] The apparatus 1200 can implement the steps or processes corresponding to those executed by the first network device in the above method embodiments. Among them, the transceiver unit 1210 can be used to perform the operations related to the transceiver of the first network device in the above method embodiments, and the processing unit 1220 can be used to perform the internal operations of the device other than transceiver information in the above method embodiments of the first network device.

[0427] In a possible implementation, the transceiver unit 1210 is configured to receive a first message from a first network device, where the first message indicates that an inactive terminal device sends clock-related information within the coverage of a second network device; the transceiver unit 1210 is configured to send clock-related information within the coverage of the second network device indicated by the first message.

[0428] Where, when the apparatus 1200 is used to execute Figures 7 to 11 the method in, the transceiver unit 1210 can be used to execute the step of transceiver information in the method; the processing unit 1220 can be used to execute the internal steps of the device other than transceiver information in the method.

[0429] It should be understood that the specific processes of each unit executing the above corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they will not be elaborated here.

[0430] It should also be understood that the device 1200 herein is embodied in the form of functional units. The term "unit" herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor or a group of processors, etc.) for executing one or more software or firmware programs, and a memory, a combined logic circuit and / or other suitable components that support the described functions. In an alternative example, those skilled in the art can understand that the device 1200 may specifically be the network device in the above embodiments, and can be used to execute the respective processes and / or steps corresponding to the network device in the above method embodiments. To avoid repetition, it will not be elaborated herein.

[0431] The device 1200 in each of the above solutions has the function of implementing the corresponding steps executed by the devices (such as terminal devices and network devices) in the above methods. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, etc., can be replaced by a processor to respectively execute the transceiver operations and related processing operations in each method embodiment.

[0432] In addition, the above transceiver unit 1210 may also be a transceiver circuit (for example, it may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit.

[0433] It should be noted that Figure 12 the device in may be the network element or device in the foregoing embodiments, or may be a chip or a chip system, for example: a system on chip (SoC). Among them, the transceiver unit may be an input / output circuit, a communication interface; the processing unit is a processor, a microprocessor or an integrated circuit integrated on the chip. It is not limited herein.

[0434] Figure 13 is a schematic structural diagram of a communication device 1300 provided by an embodiment of the present application. Figure 13 The shown communication device 1300 includes: a processor 1310, a memory 1320, and a transceiver 1330. The processor 1310 is coupled to the memory 1320 and is used to execute the instructions stored in the memory 1320 to control the transceiver 1330 to send signals and / or receive signals.

[0435] It should be understood that the above-mentioned processor 1310 and memory 1320 can be combined into a processing device. The processor 1310 is used to execute the program code stored in the memory 1320 to implement the above functions. Specifically, in implementation, the memory 1320 can also be integrated in the processor 1310 or be independent of the processor 1310. It should be understood that the processor 1310 can also correspond to each processing unit in the previous communication device, and the transceiver 1330 can correspond to each receiving unit and sending unit in the previous communication device.

[0436] It should also be understood that the transceiver 1330 can include a receiver (or, a receiver) and a transmitter (or, a transmitter). The transceiver can further include an antenna, and the number of antennas can be one or more. The transceiver can also be a communication interface or an interface circuit.

[0437] Specifically, the communication device 1300 can correspond to the Figures 7 to 11 devices (terminal device, first network device, second network device) in the embodiments of the present application. The communication device 1300 can include Figures 7 to 11 the units of the method executed by the terminal device, or the units of the method executed by the first network device, or the units of the method executed by the second network device in the embodiments of the present application. It should be understood that the specific processes of each unit executing the above corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they will not be repeated here.

[0438] When the communication device 1300 is a chip, the chip includes an interface unit and a processing unit. Among them, the interface unit can be an input / output circuit or a communication interface; the processing unit can be a processor, a microprocessor, or an integrated circuit integrated on the chip.

[0439] In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the processor or the instructions in the form of software. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware processor, or be executed and completed by the combination of the hardware and software modules in the processor. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.

[0440] It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the above method embodiments can be completed by the integrated logic circuit in the hardware of the processor or the instructions in the form of software. The above processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by the combination of the hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0441] The present application also provides a computer-readable medium, on which a computer program is stored, and when the computer program is executed by the computer, it realizes the functions of any one of the above method embodiments.

[0442] The present application also provides a computer program product, and when the computer program product is executed by the computer, it realizes the functions of any one of the above method embodiments.

[0443] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that the computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available media can be magnetic media (such as floppy disks, hard disks, magnetic tapes), optical media (such as high-density digital video discs (DVDs)), or semiconductor media (such as solid state disks (SSDs)), etc.

[0444] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. A professional technician can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of the present application.

[0445] Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0446] In several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

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

[0448] In addition, in each embodiment of the present application, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

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

[0450] As described above, it is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0451] As used in this specification, the terms "component", "module", "system", etc. are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable, an execution thread, a program, and / or a computer. By way of illustration, both an application running on a computing device and the computing device can be components. One or more components can reside in a process and / or an execution thread, and a component can be located on one computer and / or distributed between two or more computers. In addition, these components can execute from various computer-readable media having various data structures stored thereon. A component can communicate, for example, by signals according to one or more data packets (e.g., data from two components interacting with another component in a local system, a distributed system, and / or a network, e.g., the Internet interacting with other systems via signals).

[0452] Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends upon the particular application and design constraints of the technical solution. Skilled artisans may implement the described functions in different ways for each particular application, but such implementation should not be regarded as exceeding the scope of this application.

Claims

1. A communication method, characterized in that, Including: The first network device determines that the terminal device is interested in clock-related information; When the terminal device is in the inactive state, the first network device sends a first message to the second network device, and the first message instructs to send the clock-related information for the terminal device within the coverage area of the second network device.

2. The method according to claim 1, wherein The method further includes: The first network device sends a second message to the terminal device, the second message instructs the terminal device to enter the inactive state from the connected state, and the second message includes information indicating a first radio access network notification area RNA, and the first RNA includes the coverage area of the second network device.

3. The method according to claim 1 or 2, characterized in that, The first message includes the first identification information of the terminal device and / or the information of the coverage area of the second network device.

4. The method according to any one of claims 1 to 3, characterized in that, The first message includes the clock-related information and / or the duration information of a timer, and the duration information of the timer is used to indicate the duration for maintaining the terminal device interested in the clock-related information.

5. The method according to claim 4, wherein The clock-related information includes clock information and / or clock synchronization status information.

6. The method according to any one of claims 1 to 5, characterized in that When the RNA of the terminal device is updated, the method further includes: The first network device sends a third message to the network device whose coverage area belongs to the first RNA, and the third message is used to indicate that the terminal device interested in the clock-related information leaves the first RNA.

7. The method according to any one of claims 1 to 6, characterized in that When the RNA of the terminal device is updated, the method further includes: The first network device sends a fourth message to the network device whose coverage area belongs to the second RNA, and the fourth message is used to indicate that the terminal device interested in the clock-related information joins the second RNA.

8. The method according to any one of claims 1 to 5, characterized in that When the RNA of the terminal device is updated, the method further includes: The first network device sends a fifth message to the network device whose coverage area belongs to the first RNA, and the fifth message is used to indicate that the information of the terminal device interested in the clock-related information has changed.

9. The method according to claim 8, wherein The fifth message includes the first identification information of the terminal device.

10. The method according to any one of claims 6 to 9, characterized in that When the RNA of the terminal device is updated, the reason for the update is related to one or more of the following: The context information of the terminal device, the change of the terminal device from the inactive state to the connected state, the small data transfer SDT process of the terminal device.

11. A communication method, characterized in that, Including: The second network device receives a first message from the first network device, and the first message instructs to send clock-related information for the inactive terminal device within the coverage area of the second network device; The second network device sends the clock-related information within the coverage area of the second network device indicated by the first message according to the first message.

12. The method according to claim 11, wherein The first message includes the first identification information of the terminal device and / or the coverage area of the second network device.

13. The method according to claim 11 or 12, characterized in that, The first message further includes the clock-related information and / or the duration information of a timer, and the duration information of the timer is used to maintain the duration of the terminal device interested in the clock-related information.

14. The method according to claim 13, wherein The clock-related information includes clock information and / or clock synchronization status information.

15. The method according to any one of claims 11 to 14, characterized in that The method further includes: The second network device updates the inactive terminal devices interested in the clock-related information and managed by the second network device according to the first message.

16. The method according to any one of claims 11 to 15, characterized in that, The radio access network notification area RNA of the terminal device is updated, and the method further includes: The second network device receives a third message from the first network device, where the third message is used to indicate that the terminal device interested in the clock-related information leaves the first RNA, and the first RNA includes the coverage area of the second network device.

17. The method according to any one of claims 11 to 16, characterized in that, The RNA of the terminal device is updated, and the method further includes: The second network device receives a fourth message from the first network device, where the fourth message is used to indicate that the terminal device interested in the clock-related information joins the second RNA, and the second RNA includes the coverage area of the second network device.

18. The method according to any one of claims 11 to 15, characterized in that, The RNA of the terminal device is updated, and the method further includes: The second network device sends a third message to the network devices whose coverage areas belong to the first RNA, where the third message is used to indicate that the terminal device interested in the clock-related information leaves the first RNA.

19. The method according to any one of claims 11 to 16 and 18, characterized in that, The RNA of the terminal device is updated, and the method further includes: The second network device sends a fourth message to the network devices whose coverage areas belong to the second RNA, where the fourth message is used to indicate that the terminal device interested in the clock-related information joins the second RNA.

20. The method according to any one of claims 16 to 19, characterized in that, The RNA of the terminal device is updated, and the reason for the update is related to one or more of the following: The context information of the terminal device, the change of the terminal device from the inactive state to the connected state, and the small data transmission SDT process of the terminal device.

21. A communication device, characterized in that, The communication device includes a unit or module for executing the method according to any one of claims 1-10, 11-20.

22. A communication device, characterized in that, including: A processor, the processor is coupled to a memory, and the processor is used to call the computer program instructions stored in the memory to execute the method according to any one of claims 1-10, or the method according to any one of claims 11-20.

23. A chip, characterized in that, including a processor and a communication interface, the communication interface is used to receive data and / or information, and transmit the received data and / or information to the processor, and the processor processes the data and / or information to execute the method according to any one of claims 1-10, or the method according to any one of claims 11-20.

24. A computer-readable storage medium, characterized in that, Instructions are stored on the computer-readable storage medium, and when the instructions run on the computer, the computer is caused to execute the method according to any one of claims 1-10, or the computer is caused to execute the method according to any one of claims 11-20.

25. A computer program product, characterized in that, Instructions are stored on the computer-readable storage medium, and when the instructions run on the computer, the computer is caused to execute the method according to any one of claims 1-10, or the computer is caused to execute the method according to any one of claims 11-20.

Images