Communication method and apparatus

Abstract

The present application relates to the technical field of communications, and provides a communication method and apparatus. The method comprises: a first network device sends first information to a terminal device interested in clock-related information, wherein the first information indicates an RNA, and the RNA comprises a coverage range of the first network device and a coverage range of a second network device; and the first network device sends second information to the second network device, wherein the second information instructs the second network device to send the clock-related information within the coverage range of the second network device. When an RNA of a terminal device interested in clock-related information and maintained by an anchor base station comprises a coverage range of another neighbor base station, the anchor base station can send second information to the neighbor base station. The neighbor base station can send the clock-related information on the basis of the second information, so that the situation that an application requiring clock-related information cannot normally work due to the fact that the clock-related information cannot be acquired in time is avoided, guaranteeing the continuity of clock-related services.

Description

Communication method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 29, 2023, with application number 202311867129.8 and application name “Communication Method and Device,” the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and more particularly, to a communication method and apparatus. Background Art

[0003] Third Generation Partnership Project (3 rd The fifth generation (5G) defined by the 3GPP standardization organization th The 5G generation (5G) system supports the ResumeRequest message, in which the RRC resume request message carries the UE's I-RNTI. The currently resident base air interface high-precision timing service, that is, the network device can provide 5G high-precision time to the terminal device through the air interface message, thereby realizing high-precision clock synchronization between the terminal device and the network device. However, after the terminal device moves from the coverage of one network device to the coverage of another network device, the other network device cannot effectively provide clock-related information, resulting in the application that requires clock-related information being unable to work normally due to the inability to obtain clock-related information in a timely manner.

[0004] Therefore, how to ensure the continuity of clock-related services is an urgent problem to be solved. Summary of the Invention

[0005] The present application provides a communication method and apparatus that can ensure the continuity of clock-related services.

[0006] In a first aspect, a communication method is provided, including: a first network device sends first information to a terminal device interested in clock-related information, the first information indicating a radio access network notification area (RNA), the RNA including a coverage range of the first network device and a coverage range of a second network device; the first network device sends second information to the second network device, the second information instructing the second network device to send the clock-related information within the coverage range of the second network device.

[0007] The method may be executed by the first network device, or by a component (e.g., a processor, a chip, or a chip system) in the first network device, or by a logic module or software that implements all or part of the functions of the first network device. For example, the first network element device may be referred to as an anchor network device, the last serving network device accessed by the terminal device, or other names.

[0008] Through the above embodiment, when the RNA of the terminal device that is interested in clock-related information maintained by the anchor base station includes the coverage of other neighboring base stations, the anchor base station can send the second information to the neighboring base station. The neighboring base station can send the clock-related information based on the second information, so that the terminal device can also receive the clock-related information within the coverage of the neighboring base station, thereby avoiding the application that requires clock-related information from being unable to work normally due to the inability to obtain the clock-related information in a timely manner, thereby ensuring the continuity of clock-related services.

[0009] In combination with the first aspect, in certain implementations of the first aspect, the second information includes an identifier of the first network device and / or an identifier of the coverage range of the second network device, wherein the identifier of the first network device is used to indicate that the coverage range of the second network device corresponds to the first network device.

[0010] Through the above embodiment, the second network device can determine the source of the second information based on the second information. Alternatively, the second network device can determine to send clock-related information within the coverage area of ​​the second network device based on the second information, thereby ensuring the continuity of clock-related services of terminal devices within the coverage area of ​​the second network device.

[0011] In combination with the first aspect, in some implementations of the first aspect, the first information is further used to release the terminal device, causing the terminal device to enter an inactive state.

[0012] In combination with the first aspect, in some implementations of the first aspect, the method further includes: the first network device sends third information to the second network device, and the third information is used to indicate that the second network device does not send the clock-related information within the coverage range of the second network device.

[0013] Through the above embodiment, when the RNA of the terminal device interested in clock-related information maintained by the anchor base station does not include the coverage of other neighboring base stations, the anchor base station can send third information to the neighboring base station. The third information can instruct the second network device not to send the clock-related information within the coverage of the second network device, thereby saving overhead.

[0014] In combination with the first aspect, in some implementations of the first aspect, the third information includes an identifier of the first network device and / or an identifier of a coverage range of the second network device.

[0015] Through the above embodiment, the second network device can determine the source of the third information based on the third information, thereby determining whether to stop sending clock-related information within the coverage area of ​​the second network device. Alternatively, the second network device can determine to stop sending clock-related information within the coverage area of ​​the second network device based on the third information, thereby saving overhead.

[0016] In combination with the first aspect, in certain implementations of the first aspect, the first network device sends the third information to the second network device, including: after the terminal device enters a connected state or an idle state, or after the first network device deletes or migrates the context of the terminal device, or after the first network device learns that the terminal device is within the coverage of the first network device, the first network device sends the third information to the second network device.

[0017] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: the first network device determines that the terminal device is within the coverage of the first network device based on at least one of the following: the first network device performs small data packet transmission with the terminal device; or, the first network device receives location information of the terminal device, and the location information indicates that the terminal device is within the coverage of the first network device.

[0018] In combination with the first aspect, in certain implementations of the first aspect, the first network device sends the second information to the second network device, including: after the first network device terminates the transmission of the small data packet of the terminal device, the first network device sends the second information to the second network device.

[0019] In a second aspect, a communication method is provided, including: a second network device receives second information from a first network device, the second information being used to instruct the second network device to send clock-related information to the coverage range of the second network device in RNA; the second network device sends the clock-related information according to the second information.

[0020] The method can be executed by the second network device, or by a component in the second network device (e.g., a processor, chip, or chip system, etc.), or by a logic module or software that can implement all or part of the functions of the second network device.

[0021] In combination with the second aspect, in certain implementations of the second aspect, the second information includes an identifier of the first network device and / or an identifier of the coverage range of the second network device in the RNA, and the identifier of the first network device is used to indicate that the coverage range of the second network device corresponds to the first network device.

[0022] In combination with the second aspect, in some implementations of the second aspect, the second network device sends the clock-related information according to the second information, including: the second network device sends the clock-related information within the coverage range of the second network device in the notification area.

[0023] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: the second network device receives third information from the first network device, and the third information is used to indicate that the second network device does not send the clock-related information within the coverage range of the second network device in the RNA.

[0024] In combination with the second aspect, in some implementations of the second aspect, the third information includes an identifier of the first network device and / or an identifier of the coverage range of the second network device in the RNA.

[0025] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: the second network device determines, based on the third information, whether to send the clock-related information within the coverage range of the second network device in the RNA.

[0026] Through the above embodiments, the second network device can flexibly determine whether to send the clock-related information within the coverage of the second network device in the RNA based on the third information, thereby ensuring the continuity of the clock-related services of the terminal device having the RNA including the coverage of the second network device, or saving overhead.

[0027] In combination with the second aspect, in certain implementations of the second aspect, the second network device receives second information from the first network device, including: the second network device receives N second information respectively from N first network devices, where N is a positive integer; wherein the second network device receives third information from the first network device, including: the second network device receives M third information respectively from M first network devices, where M is a positive integer, and the M first network devices belong to the N first network devices; wherein the second network device determines, based on the third information, whether to send the clock-related information within the coverage of the second network device in the RNA, including: when M is equal to N, the second network device does not send the clock-related information within the coverage of the second network device in the RNA based on the third information.

[0028] Through the above embodiment, when each network device that has sent the second information sends the third information to the second network device, the second network device stops sending the clock-related information within the coverage range of the second network device in the RNA, thereby saving overhead.

[0029] In combination with the second aspect, in certain implementations of the second aspect, the second network device determines whether to send the clock-related information within the coverage of the second network device in the RNA based on the third information, and also includes: when M is less than N, the second network device sends the clock-related information within the coverage of the second network device in the RNA.

[0030] Through the above embodiment, when at least one network device that has sent the second information does not send the third information to the second network device, the second network device continues to send the clock-related information within the coverage of the second network device in the RNA, thereby ensuring the continuity of the clock-related services of the terminal device having the RNA including the coverage of the second network device.

[0031] In a third aspect, a communication device is provided, comprising a processing circuit (also referred to as a processor) and an input / output interface (also referred to as an interface circuit), the input / output interface being used to input and / or output signals, the processing circuit being used to execute the first aspect and any possible method of the first aspect, or the processing circuit being used to execute the second aspect and any possible method of the second aspect.

[0032] In conjunction with the third aspect, in certain implementations of the third aspect, the processor is configured to communicate with other devices via an interface circuit and execute the first aspect and any possible method of the first aspect, or execute the second aspect and any possible method of the second aspect. The processor includes one or more.

[0033] In a fourth aspect, a communication device is provided, which may include a device or module for performing the functions of the communication device.

[0034] In combination with the fourth aspect, in certain implementations of the fourth aspect, the communication device may include a module or unit corresponding to the method / operation / step / action described in the first aspect and any possible implementation of the first aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.

[0035] In combination with the fourth aspect, in certain implementations of the fourth aspect, the communication device may include a module or unit corresponding to the method / operation / step / action described in the second aspect and any possible implementation of the second aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.

[0036] In a fifth aspect, a computer-readable storage medium is provided, on which a computer program or instruction is stored. When the computer program or the instruction is run on a computer, the first aspect and any possible method of the first aspect are executed, or the second aspect and any possible method of the second aspect are executed.

[0037] In a sixth aspect, a computer program product is provided, comprising a computer program or instructions, which, when run on a computer, causes the first aspect and any possible method of the first aspect to be executed, or causes the second aspect and any possible method of the second aspect to be executed.

[0038] In a seventh aspect, a communication device is provided, comprising a processor connected to a memory and configured to call a program stored in the memory to execute any possible method of the first aspect, or to execute any possible method of the second aspect. The memory may be located within or outside the communication device. The processor may include one or more processors.

[0039] In one implementation, the communication device of the second, third, fourth or seventh aspect may be a chip or a chip system.

[0040] In an eighth aspect, a chip device is provided, comprising a processor for calling a computer program or computer instruction in a memory so that the processor executes any one of the implementation methods of the above-mentioned first aspect, or so that the processor executes any one of the implementation methods of the above-mentioned second aspect.

[0041] In combination with the eighth aspect, in certain implementations of the eighth aspect, the processor is coupled to the memory through an interface.

[0042] In the ninth aspect, a communication system is provided, comprising a first network device and a second network device, wherein the first network device is used to execute the above-mentioned first aspect and any possible implementation method of the first aspect, and the second network device is used to execute the above-mentioned second aspect and any possible implementation method of the second aspect.

[0043] The description of the advantageous effects of any of the second to ninth aspects etc. may refer to the description of the advantageous effects of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] FIG1 is a schematic diagram of a communication system applicable to an embodiment of the present application.

[0045] FIG2 is a schematic diagram of another communication system applicable to an embodiment of the present application.

[0046] FIG3 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0047] FIG4 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0048] FIG5 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0049] FIG6 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0050] FIG7 is a schematic flowchart of another communication method provided in an embodiment of the present application.

[0051] FIG8 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0052] FIG9 is a schematic block diagram of another communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0053] The technical solution in this application will be described below with reference to the accompanying drawings.

[0054] This application will present various aspects, embodiments, or features in the context of systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Furthermore, combinations of these aspects may also be used.

[0055] The term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. Additionally, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0056] Additionally, in the embodiments of this application, words such as "exemplary" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete manner.

[0057] The business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0058] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically stated. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise specifically stated.

[0059] The technical solutions of the embodiments of the present application can be applied to various communication systems, including but not limited to: global system for mobile communications (GSM), enhanced data rate for GSM evolution (EDGE), wideband code division multiple access (WCDMA), code division multiple access 2000 (CDMA2000), time division-synchronization code division multiple access (TD-SCDMA), long term evolution (LTE), LTE frequency division duplex (FDD), LTE time division duplex (TDD), world wide interoperability for microwave access (WiMAX) communication system, 5G mobile communication system or new radio (NR) system, narrowband Internet of Things (NB-IoT) system, enhanced machine-type communication (eMTC) system, enhanced mobile broadband (EMB) system. broadband (eMBB) systems, ultra reliable low latency communications (URLLC) systems, satellite communication systems or LTE-machine-to-machine (LTE-M) systems, and future sixth generation (6G) th generation, 6G) mobile communication systems, etc.

[0060] It should be noted that in the embodiments of this application, the term "communication" can also be described as "data transmission," "signal transmission," "information transmission," or "transmission." In the embodiments of this application, transmission can include sending or receiving. For example, transmission can be uplink transmission, such as a terminal device sending a signal to a network device; transmission can also be downlink transmission, such as a network device sending a signal to a terminal device.

[0061] Figure 1 is a schematic diagram of a communication system applicable to embodiments of the present application. As shown in Figure 1 , the communication system may include multiple communication devices, which can wirelessly communicate with each other using air interface resources. For example, the communication devices may include network device 111, network device 112, network device 113, and terminal device 120.

[0062] The network device 111 , the network device 112 , and the network device 113 can communicate with each other through the Xn interface.

[0063] Network device 111, network device 112 and network device 113 can communicate with terminal device 120. Among them, network device 112 can be a base station that connects terminal device 120 to a radio access network (RAN). Base stations are sometimes also referred to as access network devices or access network nodes. It is understandable that in systems using different wireless access technologies, the names of devices with base station functions may be different. For the convenience of description, the embodiments of the present application will collectively refer to devices that provide wireless communication access functions for terminal devices as base stations. In the embodiments of the present application, network devices include but are not limited to: various forms of macro base stations, micro base stations (also called small stations), relay stations, access points, etc. Network equipment includes the evolved node B (eNB or eNodeB) in LTE, the radio network controller (RNC), the node B (NB), the base station controller (BSC), the base transceiver station (BTS), the home evolved node B (or home node B, HNB), and the base band unit (BBU) in wireless fidelity (WIFI) systems; access points, wireless relay nodes, wireless backhaul nodes, transmission points (TP), or transmission and reception points (TRP) in wireless fidelity (WIFI) systems; and the next generation node base station (gNB) or transmission point (TRP or TP) in 5G systems; one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system; network nodes constituting a gNB or transmission point, such as a baseband unit (BBU) or distributed unit (DU); and network equipment in future 6G networks.

[0064] In some deployments, the network device may include a centralized unit (CU) and a DU. The CU implements some functions of the network device, and the DU implements some functions of the network device. For example, the CU is responsible for processing non-real-time protocols and services, and implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The network device may also include an active antenna unit (AAU). The AAU implements some physical layer processing functions, radio frequency processing, and related functions of the active antenna. Since the information of the RRC layer will eventually become the information of the PHY layer, or be converted from the information of the PHY layer, in this architecture, high-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by the DU+AAU. It can be understood that the network device can be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU can be divided into a network device in the access network (radio access network, RAN), or a network device in the core network (core network, CN), which is not limited in this application. The network device can adopt a CU-DU separation architecture, or not adopt a CU-DU separation architecture, which is not limited in this application.

[0065] In the embodiments of the present application, the apparatus for implementing the function of the network device may be the network device, or may be a device capable of supporting the network device in implementing the function, such as a chip system, which may be installed in the network device. In the technical solutions of the embodiments of the present application, the technical solutions provided in the embodiments of the present application are described by assuming that the apparatus for implementing the function of the network device is the network device, and the network device is a base station as an example.

[0066] The terminal device 120 can be any device with wireless transceiver capabilities, or in other words, the terminal device 120 can be a device that provides voice and / or data connectivity to the user. The terminal device 120 can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water (such as a ship); it can also be deployed in the air (for example, on an airplane, a balloon, and a satellite). The terminal device 120 can also be called user equipment (UE), access terminal, terminal, subscriber unit (subscriber unit), user station, mobile station, mobile station (MS), remote station, remote terminal, mobile device, mobile terminal (MT), user terminal, wireless network device, user agent, or user device. In the embodiment of the present application, the terminal device 120 includes, but is not limited to, a cellular phone, a mobile phone, a wireless data card, a wireless modem, a tablet computer, a laptop computer, a cordless phone, a Session Initiation Protocol (SIP) phone, a smart phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handset with wireless communication capabilities, a computing device or other device connected to a wireless modem, an in-vehicle device, a wearable device, an unmanned aerial vehicle device, a terminal device in the Internet of Things or the Internet of Vehicles, and any form of terminal in a future network, a relay user device, or a terminal in a future evolved public land mobile network (PLMN). The terminal device 120 may also be a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a machine type communication (MTC) terminal, a terminal device in industrial control, a terminal device in self-driving, a terminal device in remote medical, a terminal device in a smart grid, a terminal device in a smart city, a terminal device in a smart home, etc., and the embodiments of the present application are not limited to this.

[0067] In the embodiments of the present application, the device for realizing the function of the terminal device may be a terminal device, or a device capable of supporting the terminal device to realize the function, such as a chip system, which may be installed in the terminal. The chip system may be composed of a chip, or may include a chip and other discrete devices. In the technical solution of the embodiments of the present application, the device for realizing the function of the terminal device is a terminal device, which may also be referred to as a terminal. The following may take the terminal device as an example to describe the technical solution provided by the embodiments of the present application.

[0068] It should be understood that FIG1 is only a simplified schematic diagram for ease of understanding, and the communication system 100 may further include other network devices or other terminal devices, which are not shown in FIG1 .

[0069] The network device and the terminal device 120 can communicate through a wireless link. The transmission link from the network device to the terminal device 120 can be called a downlink (DL) or a downlink channel, which is used to transmit downlink signals. The transmission link from the terminal device 120 to the network device can be called an uplink (UL) or an uplink channel, which is used to transmit uplink signals. The network device and the terminal device 120 can also transmit downlink data through the downlink channel and transmit uplink data through the uplink channel. Wireless communication can be carried out between the terminal device 120 and other terminal devices. The transmission link from the terminal device 120 to other terminal devices can be called a sidelink (SL) or a side channel, which is used to transmit side signals. The terminal device 120 and other terminal devices can also transmit side data through the side channel.

[0070] Figure 2 is a schematic diagram of another communication system applicable to embodiments of the present application. For example, the UE in Figure 2 may be the aforementioned terminal device 120, and the RAN in Figure 2 may be any of the aforementioned network devices 111 through 113. The following describes some core network elements that may be involved, in conjunction with Figure 2.

[0071] The access and mobility management network element is mainly used for the attachment and tracking area update processes of terminals in mobile networks. The access and mobility management network element can provide non-access stratum (NAS) messages, complete registration management, connection management, reachability management, allocation of tracking area list (TA list), legal monitoring, access authorization, authentication and mobility management, etc., and transparently route session management (SM) messages to the session management network element. In the fifth generation (5G) communication system, the access and mobility management network element can be the access and mobility management function (AMF). In future communication systems (such as 6G communication systems), the mobility management network element can still be the AMF network element, or it can have other names, which is not limited in this application.

[0072] The session management network element is mainly used for session and bearer management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating Internet Protocol (IP) addresses to terminals, selecting user plane function network elements that provide message forwarding functions, etc. The session management network element can issue data packet forwarding policies, QoS policies, etc. to user plane function network elements based on the NG4 interface. In a 5G communication system, the session management network element can be a session management function (SMF). In future communication systems (such as 6G communication systems), the session management network element can still be an SMF network element, or it can have other names, which is not limited in this application.

[0073] The user plane function network element is mainly used to process user messages, such as forwarding, billing, legal monitoring, etc. In addition, the user plane function network element can be used for routing forwarding, threshold control, traffic monitoring, verification and other functions of user plane data. The user plane function network element can also be used for the management of UE IP addresses, the management of core network (CN) tunnel information, etc. The user plane function network element can also be called a PDU session anchor (PSA). In a 5G communication system, the user plane function network element can be a UPF. In future communication systems (such as a 6G communication system), the user plane function network element can still be a UPF network element, or it can have other names, which is not limited in this application.

[0074] Corresponding to the user plane function network element may be a control plane function network element (CP), which may include the above-mentioned access and mobility management network element and session management network element.

[0075] The policy control network element includes user subscription data management functions, policy control functions, billing policy control functions, QoS control, etc. In the 5G communication system, the policy control network element can be a policy control function (PCF). In future communication systems (such as 6G communication systems), the policy control network element can still be a PCF network element, or it can have other names, which is not limited in this application.

[0076] The network slice selection function network element is mainly used to select a suitable network slice for the service of the terminal device. In the 5G communication system, the network slice selection network element can be a network slice selection function (NSSF) network element. In future communication systems (such as 6G communication systems), the network slice selection network element can still be an NSSF network element, or it can have other names, which is not limited by this application.

[0077] The network repository function network element is mainly used to provide registration and discovery functions for network elements or services provided by network elements. In 5G communication systems, the network repository function network element can be a network repository function (NRF). In future communication systems (such as 6G communication systems), the network repository function network element can still be an NRF network element, or it can have other names, which is not limited by this application.

[0078] The network data analysis network element can collect data from various network functions (NFs), such as policy control network elements, session management network elements, user plane function network elements, access and mobility management network elements, and application function network elements (through network capability exposure function network elements), and perform analysis and prediction. In a 5G communication system, the network data analysis network element can be a network data analysis function (NWDAF). In future communication systems (such as 6G communication systems), the network data analysis network element can still be an NWDAF network element, or it can have other names, which is not limited by this application.

[0079] The unified data management network element is mainly used to manage the contract information of terminal devices. In the 5G communication system, the unified data management network element can be unified data management (UDM). In future communication systems (such as 6G communication systems), the unified data management network element can still be the UDM network element, or it can have other names, which is not limited by this application.

[0080] The unified data storage network element is mainly used to store structured data information, including contract information, policy information, and network data or business data defined in a standard format. In the 5G communication system, the unified data storage network element can be a unified data repository (UDR). In future communication systems (such as 6G communication systems), the unified data storage network element can still be a UDR network element, or it can have other names, which is not limited by this application.

[0081] The authentication service function network element is mainly used to perform security authentication on the terminal device. In the 5G communication system, the authentication service function network element can be the authentication server function (AUSF). In future communication systems (such as 6G communication systems), the authentication service function network element can still be the AUSF network element, or it can have other names, which is not limited by this application.

[0082] A network capability exposure network element can controllably expose some network functions to applications. In a 5G communication system, a network capability exposure network element can be a network exposure function (NEF). In future communication systems (such as a 6G communication system), the network capability exposure network element can still be an NEF network element, or it can have other names, which are not limited by this application.

[0083] The application function network element can provide service data of various applications to the control plane network elements of the operator's communication network, or obtain network data information and control information from the control plane network elements of the communication network. In the 5G communication system, the application function network element can be an application function (AF). In future communication systems (such as 6G communication systems), the application function network element can still be an AF network element, or it can have other names, which is not limited by this application. For example, the application function network element can also be called an application server or a service server. In addition, the application function network element can be deployed in the operator network or by a third party.

[0084] Data networks are primarily used to provide data transmission services to terminal devices. Data networks can be private networks, such as local area networks (LANs), public data networks (PDNs), such as the Internet, or proprietary networks deployed jointly by operators, such as those configured with IP multimedia core network subsystem (IMS) services. Data networks can also be provided by third parties.

[0085] In the architecture shown in Figure 1, the interface names and functions between the various network elements are as follows:

[0086] 1. N1: The interface between AMF and UE, which can be used to deliver QoS control rules to UE.

[0087] 2. N2: The interface between AMF and (R)AN, which can be used to transmit radio bearer control information from the core network side to the RAN.

[0088] 3. N3: Interface between RAN and UPF, used to transfer uplink or downlink user plane data between RAN and UPF.

[0089] 4. N4: The interface between SMF and UPF, which can be used to transmit information between the control plane and the user plane, including the control of the forwarding rules, QoS control rules, traffic statistics rules, etc. for the user plane and the reporting of information on the user plane.

[0090] 5. N6: Interface between UPF and DN, used to transmit uplink or downlink user data flow between UPF and DN.

[0091] 6. The service-oriented interfaces Nnssf, Nnef, Nausf, Nnrf, Namf, Npcf, Nsmf, and Nudm are respectively provided by the above-mentioned NSSF network element, NEF network element, AUSF network element, NRF network element, AMF network element, PCF network element, SMF network element, and UDM network element, and are used to call corresponding service-oriented operations.

[0092] It should be understood that the above-mentioned network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above-mentioned network element or function can be implemented by a single device, or by multiple devices, or as a functional module within a single device, which is not specifically limited in the embodiments of the present application.

[0093] It should be noted that network devices can also exchange information with SMF.

[0094] The 5G system, defined by the 3GPP standardization organization, supports high-precision over-the-air timing services. This means that network devices can provide 5G high-precision time to terminal devices via over-the-air messages, thereby achieving high-precision clock synchronization between the terminal and network devices. For example, 5G over-the-air time synchronization can be achieved by the gNB indicating a reference point, 5G time, to the UE. The gNB can provide 5G timing to the UE via broadcast (e.g., broadcasting system information) or unicast (e.g., sending RRC signaling).

[0095] The network device can broadcast a system information block (SIB) 9 to achieve time synchronization between the network device and the terminal device. Exemplarily, the SIB9 broadcast by the network device may include a specific time T. The protocol defines the reference point of the time T as the rear boundary of the radio frame where the system information (SI) window containing the SIB9 ends, or the rear boundary of the radio frame immediately following the end position. For example, if the end position of the SI window where the SIB9 is located is exactly the rear boundary of the radio frame with the system frame number (SFN) x, then the time T indicated in the SIB9 is the 5G time of the end position of the radio frame corresponding to SFN x. For another example, if the end position of the SI window where the SIB9 is located falls in the middle of the radio frame of SFN x, then the time T indicated in the SIB9 is the 5G time of the end position of the radio frame corresponding to SFN x.

[0096] The network device may send an RRC unicast message to the terminal device within a time slot of SNF x-3. For example, the RRC unicast message may be a downlink information transfer (DLInformationTransfer) message. The RRC unicast message includes the 5G time T and the time reference point SFN x. After receiving the RRC unicast message, the terminal device may determine that the 5G time corresponding to the end position of the radio frame of SFN x is time T. The SNF x is the SNF x within the SFN cycle closest to the time when the RRC unicast message was received.

[0097] Based on the base station providing 5G clocks to the UE, 3GPP Release (R) 18 further defines the Timing Resilience System (TRS) feature. When a UE accesses the 5G system (5G system, 5GS), the 5G core network can indicate to the base station which 5G clock synchronization states the UE is interested in, and the base station can provide 5G clock synchronization status information (or clock quality information) to the interested UE. The 5G clock synchronization status information includes at least one of the following:

[0098] (1) Synchronization status. The synchronization status can be locked, holdover, or free run. 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; free run indicates that the 5G clock is not locked with the clock source, nor is it in a state of maintaining clock accuracy.

[0099] (2) Whether it can be traced back to the time of universal time coordinated (UTC).

[0100] (3) Whether it can be traced back to the time of the global navigation satellite system (GNSS).

[0101] (4) Clock frequency stability.

[0102] (5)Clock accuracy.

[0103] (6)Clock source.

[0104] For connected UEs, the base station can provide the above-mentioned clock synchronization status information directly to the UE through RRC unicast messages. However, for inactive or idle UEs, the base station must first notify the UE of the change in 5G clock synchronization status. After the UE enters the connected state, the base station will provide the UE with 5G clock synchronization status information through RRC unicast messages. Specifically, when the base station side perceives a change in the clock synchronization status, it carries a new event identifier (event ID) in the broadcast SIB9 message; after the inactive or idle UE reads the event identifier contained in the SIB9, if it finds that the event identifier has changed, or the UE finds that the base station where the UE resides has changed, then the UE can initiate an RRC connection establishment process or an RRC connection recovery process; when the base station finds that the UE has entered the connected state and the UE is interested in the clock synchronization status information, it sends the 5G clock synchronization status information to the UE.

[0105] The base station switches the connected UE to the inactive state by sending an RRC release message to the UE. The RRC release message may include a suspendConfig information element, in which the base station configures the following information.

[0106] (1) RNA information may include cell identifiers of one or more base stations, or one or more RAN area identifiers.

[0107] (2) Inactive radio network temporary identifier (I-RNTI), which may be an identifier of an Inactive user allocated by the base station to the UE.

[0108] (3) Periodic RNA update-timer value (PeriodicRNA update-TimerValue) can be used to control the timing length of timer t380 for initiating the periodic RNA update (RNA-U) process. When the UE enters the Inactive state, timer t380 is started.

[0109] When an Inactive UE is moving, the RNA-U process is initiated under the following conditions.

[0110] (1) When timer t380 expires, the UE initiates the periodic RNA-U process.

[0111] (2) The UE reselects to a cell that does not belong to the configured RNA range.

[0112] In other words, when an Inactive UE moves within an RNA, it may not notify the base stations in the RNA. For example, if the RNA includes base stations 1 and 2, and an Inactive UE moves from the coverage of base station 1 to the coverage of base station 2, the UE may not notify base stations 1 or 2 of the change in its location.

[0113] When an Inactive UE initiates the RNA-U process, it is necessary to perform the RRC connection recovery process. Specifically, the UE can send an RRC recovery request (ResumeRequest) message to the currently resident base station (or called a new serving gNB), where the RRC recovery request message carries the UE's I-RNTI. The currently resident base station identifies the serving base station (last serving gNB) that the UE last accessed (or called an anchor base station, that is, the base station that released the UE into the Inactive state) based on the UE's I-RNTI. In the case that the currently resident base station and the nearest serving base station are not the same base station, the currently resident base station can initiate a retrieval UE context (RETRIEVE UE CONTEXT) process to the serving base station that the UE last accessed to request the UE context. The serving base station that the UE last accessed can decide whether to perform anchor relocation, that is, whether to migrate the UE's context to the new serving base station. If the service base station that the UE accessed last time does not migrate the UE context, an RRCRelease message can be sent to the UE through the new service base station to transfer the UE to the Inactive state or the Idle state; if the service base station that the UE accessed last time migrates the UE context to the new service base station, the new service base station can decide to transfer the UE to the Connected state, or continue to stay in the Inactive state, or transfer it to the Idle state after obtaining the UE context.

[0114] If the RNA area configured for an Inactive UE includes cells of multiple base stations, only the UE's anchor base station can detect whether the UE is interested in 5G clock information and / or 5G clock status information; other base stations within the RNA are unaware of this information. For example, when gNB1 transitions a UE to the Inactive state, if the UE is interested in 5G clock information and / or 5G clock status information, gNB1 can broadcast SIB9 to provide the UE with 5G clock information or indicate whether the 5G clock quality has changed. However, if the Inactive UE moves out of gNB1's coverage area and into the coverage area of ​​another base station within the RNA, such as gNB2, gNB2 is unaware of the presence of an Inactive UE interested in clock information and / or clock status information within its coverage area and may not broadcast SIB9. In this case, the UE may not receive 5G clock information or detect changes in 5G clock quality. This may cause applications that require clock-related information to not be able to obtain it in a timely manner, causing them to malfunction.

[0115] Therefore, how to ensure the continuity of clock-related services is an urgent problem to be solved.

[0116] FIG3 is a schematic flow chart of a communication method 300 provided in an embodiment of the present application. Method 300 can ensure the continuity of clock-related services. Method 300 is described below with reference to FIG3.

[0117] S310: A first network device sends first information to a terminal device that is interested in clock-related information.

[0118] The first information may indicate RNA, and the RNA may include the coverage of the first network device and the coverage of the second network device.

[0119] The first network device may also be referred to as an anchor network device, the last serving base station, or by other names. Those skilled in the art will appreciate that the first network device begins serving as the anchor base station for the terminal device interested in clock-related information. In some optional embodiments, prior to S310, method 300 further includes: the first network device receiving the context of the terminal device from a third network device. It is understood that the third network device is the previous (or preceding) anchor base station for the terminal device, and the first network device is the new anchor base station for the terminal device.

[0120] Clock-related information may include clock information and / or clock status information. The clock information may be 5G clock information or 6G clock information, which is not limited in this application. The clock status information may be 5G clock status information or 6G clock status information, which is not limited in this application. For example, the clock information may be the time T in the above-mentioned SIB9 message, which is used for clock synchronization between the terminal device and the second network device. For another example, the clock status information may be an event identifier in the above-mentioned SIB9 message, which is used to indicate that the clock synchronization status has changed, thereby triggering the RRC connection establishment process or the RRC connection recovery process of the terminal device, so that the terminal device can obtain new clock synchronization status information. Sending clock-related information can be understood as broadcasting clock-related information.

[0121] The terminal device in S310 is a terminal device that is interested in clock-related information. In some optional embodiments, the method 300 further includes: the first network device acquires a terminal device that is interested in clock-related information. The terminal device may be one or more.

[0122] As an example, the first network device may receive indication information from a core network element (e.g., SMF), which may indicate that the terminal device is interested in clock information and / or clock status information. For example, when an idle state UE accesses the first network device and enters a connected state, the core network element may send the above indication information to the first network device.

[0123] As another example, a neighboring network device of the first network device may send indication information to the first network device, where the indication information may indicate that the terminal device is interested in clock information and / or clock status information. For example, during a base station handover, a source base station may send the indication information to a target base station.

[0124] As another example, the terminal device may send indication information to the first network device, where the indication information may indicate that the terminal device is interested in clock information and / or clock status information. For example, when accessing the first network device, the terminal device may send the indication information to the first network device via an RRC message.

[0125] The terminal device is interested in clock-related information, which may include that the terminal device needs to obtain or receive clock-related information.

[0126] The first information can be carried in the RRCRelease message, but this application does not limit the message carried by the first information, and the first information can also be carried in other messages.

[0127] The first information may indicate RNA. For example, the first information may include cell identifiers of one or more base stations, or one or more RAN area identifiers. Alternatively, the first information may carry or include an RNA identifier. This application does not limit the name of the first information. For example, the first information may be called RNA information, RRCRelease message, or have other names.

[0128] This application does not limit the name of RNA. For example, RNA can be called a wireless access network notification area or have other names. If a terminal device configured with RNA moves outside the RNA, the terminal device needs to initiate an RNA-U process. In other words, a terminal device configured with RNA can move within the RNA without notifying the network devices in the RNA. If a terminal device configured with RNA exceeds a preset duration (for example, the timing length of timer t380) and is still within the RNA, the terminal device may not notify the network devices in the RNA. In other words, a terminal device configured with RNA may not notify the network devices in the RNA within a preset duration.

[0129] RNA may include the coverage of the first network device and the coverage of the second network device. It should be noted that the coverage of the first network device may be the entire coverage of the first network device, or a partial coverage of the entire coverage of the first network device. For example, the first network device is capable of covering three cells, and the coverage of the first network device may be one cell, two cells, or three cells of the three cells. Similarly, the coverage of the second network device may be the entire coverage of the second network device, or a partial coverage of the entire coverage of the first network device. For example, the second network device is capable of covering four RAN areas, and the coverage of the second network device may be one RAN area, two RAN areas, three RAN areas, or four RAN areas of the four RAN areas. For the sake of convenience of description, unless otherwise specified, the coverage of the first network device mentioned below refers to the range covered by the first network device in RNA, and the coverage of the second network device refers to the range covered by the second network device in RNA.

[0130] The coverage range of the first network device and the coverage range of the second network device in the RNA may be different. The coverage range of the second network device may not be within the coverage range of the first network device, or in other words, the coverage range of the second network device is not within the range maintained by the first network device. For example, the RNA includes cell 1 and cell 2. The first network device can cover cell 1 but not cell 2, while the second network device can cover cell 2. In other words, the coverage range of the first network device includes cell 1, the coverage range of the first network device does not include cell 2, and the coverage range of the second network device includes cell 2.

[0131] It should be noted that the above-mentioned second network device can be one or more.

[0132] Optionally, in another implementation scenario of the above embodiment, the first information is also used to release the terminal device, so that the terminal device enters an inactive state.

[0133] The first message may be called an RRCRelease message or have other names. It is understandable that before the first message releases the terminal device, the terminal device may be in a connected state; after the first message releases the terminal device, the terminal device may be in an inactive state.

[0134] S320: The first network device sends second information to the second network device. Correspondingly, the second network device receives the second information from the first network device.

[0135] The second information may instruct the second network device to send the clock-related information within the coverage area of ​​the second network device.

[0136] The second information can be sent to the second network device via the Xn interface. This application does not limit the message carried by the second information, and the second information can be carried in any message. This application does not limit the name of the second information. For example, the second information can be called indication information, message 1, new information, start synchronization information, or other names.

[0137] It is understandable that the second information may indicate that a terminal device that is interested in clock-related information may exist within the coverage area of ​​the second network device. Based on the second information, the second network device can learn that within the coverage area of ​​the second network device in the RNA, there is a terminal device that is interested in clock-related information and is maintained by the first network device.

[0138] It should be noted that while the second information instructs the second network device to transmit the clock-related information within the coverage area of ​​the second network device, it does not necessarily mean that the second network device will transmit the clock-related information within the coverage area of ​​the second network device in accordance with the instruction of the second information. On the one hand, the second network device may not receive the second information; on the other hand, even if the second network device receives the second information, it may not transmit the clock-related information within the coverage area of ​​the second network device. In other words, the second network device can determine whether to transmit the clock-related information within the coverage area of ​​the second network device based on its own implementation.

[0139] In some optional embodiments, before S320, method 300 includes: the first network device determining that the RNA includes the coverage of the second network device. In other words, the first network device determines that the RNA configured by the terminal device includes the coverage of other network devices (or network devices other than the first network device).

[0140] Furthermore, method 300 may include: the first network device may determine that the coverage range of the second network device is not within the RNA of other existing inactive terminal devices that are interested in clock-related information and maintained by the first network device (or inactive terminal devices that are interested in clock-related information other than the terminal device in S310). The inactive terminal devices that are interested in clock-related information and maintained by the first network device can be understood as the inactive terminal devices that are interested in clock-related information and served by the first network device, or the inactive terminal devices that are interested in clock-related information under the first network device. In other words, the anchor base station of these inactive terminal devices that are interested in clock-related information is the first network device.

[0141] Those skilled in the art will appreciate that the above method 300 can be executed multiple times. For other inactive terminal devices that are already maintained by the first network device and are interested in clock-related information, if the above method 300 has been executed, then the network devices other than the first network device included in the RNA configured by these terminal devices may have already received the second information. Therefore, the first network device determines that the coverage range of the newly appeared second network device is not within the RNA of other inactive terminal devices that are already maintained by the first network device and are interested in clock-related information, which can avoid the first network device repeatedly sending the second information to the network devices that have already received the second information.

[0142] In some optional embodiments, method 300 includes: the first network device determining whether the RNA includes the coverage of the second network device, and whether the coverage of the second network device is not within the RNA of other inactive terminal devices (or inactive terminal devices other than the terminal device in S310) that are already interested in clock-related information and maintained by the first network device. If so, S320 may be executed. If not, S320 may not be executed.

[0143] Optionally, in another implementation scenario of the above embodiment, the second information includes an identifier of the first network device and / or an identifier of a coverage range of the second network device, wherein the identifier of the first network device is used to indicate that the coverage range of the second network device corresponds to the first network device. That is, the RNA range configured for inactive terminal devices interested in clock-related information maintained by the first network device includes the above-mentioned coverage range of the second network device.

[0144] Exemplarily, the identifier of the coverage range of the second network device may include at least one cell identity and / or at least one RAN area ID. The coverage range of the second network device may also be referred to as the affected range of the second network device, the affected RNA range, or other names. "Affected" means that the range of the second network device is within the RNA of an inactive terminal device that is interested in clock-related information and maintained by another first network device serving as an anchor base station.

[0145] Through the above embodiment, the second network device can determine the source of the second information based on the second information. Alternatively, the second network device can determine to send clock-related information within the coverage area of ​​the second network device based on the second information, thereby ensuring the continuity of clock-related services of terminal devices within the coverage area of ​​the second network device.

[0146] In some optional embodiments, the second information also includes a first flag, which indicates that the coverage range of the second network device is a newly added range, that is, the coverage range of the second network device is the RNA of inactive terminal devices configured under the first network device that are interested in clock-related information.

[0147] S330: The second network device sends the clock-related information according to the second information.

[0148] The second network device may send the clock related information by broadcasting a SIB9 message.

[0149] Optionally, in another implementation scenario of the above embodiment, S330 includes: the second network device sends the clock-related information within the coverage range of the second network device in the notification area.

[0150] In another optional embodiment, S330 includes: the second network device not transmitting the clock-related information within the coverage area of ​​the second network device in the notification area. In other words, even if the second network device receives the second information, it may not transmit the clock-related information. For example, based on factors such as privacy policies configured by an operator, the second network device may not provide clock-related information to inactive terminal devices within its coverage area.

[0151] Through the above embodiment, when the RNA of the terminal device that is interested in clock-related information maintained by the anchor base station includes the coverage of other neighboring base stations, the anchor base station can send the second information to the neighboring base station. The neighboring base station can send the clock-related information based on the second information, so that the terminal device can also receive the clock-related information within the coverage of the neighboring base station, thereby avoiding the application that requires clock-related information from being unable to work normally due to the inability to obtain the clock-related information in a timely manner, thereby ensuring the continuity of clock-related services.

[0152] Optionally, in another implementation scenario of the above embodiment, the method 300 further includes: the first network device sending third information to the second network device, where the third information may be used to instruct the second network device not to send the clock-related information within the coverage area of ​​the second network device. Correspondingly, the second network device receives the third information from the first network device.

[0153] The third information can be sent to the second network device via the Xn interface. This application does not limit the message carried by the third information, and the third information can be carried in any message. This application does not limit the name of the third information. For example, the third information can be called indication information, message 2, reduction information, stop synchronization information, or other names.

[0154] It is understandable that when the first network device no longer serves as an anchor base station for terminal devices interested in clock-related information, it can send third information to the second network device. The third information can indicate that there are no terminal devices interested in clock-related information maintained by the first network device within the coverage range of the second network device. Based on the second information, the second network device can know that there are no terminal devices interested in clock-related information maintained by the first network device within the coverage range of the second network device in the RNA.

[0155] It should be noted that while the third information instructs the second network device not to transmit the clock-related information within its coverage, it does not necessarily mean that the second network device will not transmit the clock-related information within its coverage according to the third information. On the one hand, the second network device may not receive the third information; on the other hand, even if the second network device receives the third information from the first network device, it can still transmit the clock-related information within its coverage.

[0156] For example, in addition to the first network device sending second information to the second network device, instructing the second network device to send clock-related information within cell 1 covered by the second network device, another network device also sends second information to the second network device, instructing the second network device to send clock-related information within cell 1, and the second network device does not receive third information from the aforementioned another network device. In this case, there may be inactive terminal devices in cell 1 that are maintained by the aforementioned another network device and are interested in clock-related information. The second network device can still send clock-related information within cell 1 to enable clock synchronization for the inactive terminal devices maintained by the aforementioned another network device that are interested in clock-related information.

[0157] In some optional embodiments, before S320, method 300 includes: the first network device determines that the RNA of the terminal device does not include the coverage of the second network device.

[0158] For example, the first network device reconfigures the RNA, and the new RNA of the terminal device does not include the coverage of the second network device.

[0159] For another example, the first network device determines that the terminal device enters a connected state or an idle state. It is understandable that if the terminal device enters a connected state or an idle state, the RNA configured for the terminal device will become invalid, which is equivalent to the terminal device's valid RNA not including the coverage of the second network device, or the first network device no longer serving as the anchor base station for the terminal device.

[0160] For another example, the first network device deletes the context of the terminal device or migrates the context of the terminal device to another network device. It is understandable that if the first network device does not have the context of the terminal device, then the first network device no longer serves as the anchor base station for the terminal device, and thus the effective RNA of the terminal device does not include the coverage of the second network device.

[0161] Further, method 300 may include: the first network device may determine that the coverage range of the second network device is not within the RNA of other inactive terminal devices that are already interested in clock-related information maintained by the first network device (or inactive terminal devices that are interested in clock-related information other than the terminal device in S310).

[0162] Those skilled in the art can understand that if the coverage of the second network device is within the RNA of other inactive terminal devices that are already interested in clock-related information maintained by the first network device, then it can be indicated that other inactive terminal devices that are interested in clock-related information maintained by the first network device still exist in the coverage of the second network device. For example, the first network device has inactive UE1 and UE2 that are interested in clock-related information, UE1's RNA1 includes cell 1, and UE2's RNA2 includes cell 1. When the first network device reconfigures RNA1 that does not include cell 1 for UE1, or UE1 enters a connected state or an idle state, or the first network device deletes or migrates the context of UE1, the first network device may not send the third message to the second network device. The reason is that UE2 may still be in cell 1. If the second network device stops sending clock-related information in cell 1 at this time, UE2 cannot synchronize its clock.

[0163] In some optional embodiments, method 300 includes: the first network device determines whether the RNA does not include the coverage of the second network device, and the coverage of the second network device is not within the RNA of other inactive terminal devices that are already interested in clock-related information maintained by the first network device (or inactive terminal devices that are interested in clock-related information other than the terminal device in S310). If so (that is, the RNA does not include the coverage of the second network device, and the coverage of the second network device is not within the RNA of other inactive terminal devices that are already interested in clock-related information maintained by the first network device), the third information can be sent to the second network device. If not, the third information is not sent to the second network device.

[0164] Through the above embodiment, when the RNA of the terminal device interested in clock-related information maintained by the anchor base station does not include the coverage of other neighboring base stations, the anchor base station can send third information to the neighboring base station. The third information can instruct the second network device not to send the clock-related information within the coverage of the second network device, thereby saving overhead.

[0165] Optionally, in another implementation scenario of the above embodiment, the third information includes an identifier of the first network device and / or an identifier of the coverage range of the second network device.

[0166] Exemplarily, the coverage identifier of the second network device may include at least one cell identifier and / or at least one RAN area identifier. The coverage identifier of the second network device in the third information may be the same as the coverage identifier of the second network device in the first information.

[0167] The identifier of the first network device may be associated with the identifier of the coverage area of ​​the second network device. In other words, the first network device may be associated with the coverage area of ​​the second network device.

[0168] A second network device may receive second and third information from multiple networks. The second network device can determine whether to stop transmitting clock-related information within its coverage area based on whether all network devices associated with its coverage area have transmitted the third information. For example, if the second network device receives a second message that includes the identifier of the first network device and the identifier of cell 1, the second network device may transmit clock-related information within cell 1 based on the second message. Subsequently, if the second network device receives another second message that includes the identifier of the first network device and the identifier of cell 1, the first network device has already transmitted clock-related information within cell 1 and therefore does not need to process the information repeatedly. Subsequently, if the second network device receives a third message that includes the identifier of the first network device and the identifier of cell 1, since the identifiers associated with cell 1 include both the identifier of the first network device and the identifier of the second network device, the second network device may continue transmitting clock-related information within cell 1. In other words, the second network device may continue transmitting clock-related information within cell 1. Subsequently, if the second network device receives another third message that includes the identifier of the second network device and the identifier of cell 1, At this time, the second network device may stop sending clock-related information in cell 1 .

[0169] Through the above embodiment, the second network device can determine the source of the third information based on the third information, thereby determining whether to stop sending clock-related information within the coverage area of ​​the second network device. Alternatively, the second network device can determine to stop sending clock-related information within the coverage area of ​​the second network device based on the third information, thereby saving overhead.

[0170] In some optional embodiments, the second information further includes a second flag, which indicates that the coverage range of the second network device is a reduced range, that is, the coverage range of the second network device is the RNA of the terminal device that is not configured under the first network device.

[0171] Optionally, in another implementation scenario of the above embodiment, the method 300 further includes: the second network device determines, based on the third information, whether to send the clock-related information within the coverage of the second network device in the RNA.

[0172] For example, the second network device can determine, based on the third information, to continue sending the clock-related information within the coverage of the second network device in the RNA, thereby ensuring the continuity of the clock-related services of the terminal device having the RNA including the coverage of the second network device.

[0173] For another example, the second network device may determine, based on the third information, to stop sending the clock-related information within the coverage range of the second network device in the RNA, thereby saving overhead.

[0174] Through the above embodiments, the second network device can flexibly determine whether to send the clock-related information within the coverage of the second network device in the RNA based on the third information, thereby ensuring the continuity of the clock-related services of the terminal device having the RNA including the coverage of the second network device, or saving overhead.

[0175] Optionally, in another implementation scenario of the above embodiment, the second network device receives the second information from the first network device, including: the second network device receives N second information respectively from N first network devices, where N is a positive integer; wherein the second network device receives the third information from the first network device, including: the second network device receives M third information respectively from M first network devices, where M is a positive integer, and the M first network devices belong to the N first network devices; wherein the second network device determines whether to send the clock-related information within the coverage of the second network device in the RNA based on the third information, including: when M is equal to N, the second network device does not send the clock-related information within the coverage of the second network device in the RNA based on the third information.

[0176] The above solution can be understood as follows: if every network device that has sent the second information has sent the third information to the second network device, the second network device will stop sending the clock-related information within the coverage area of ​​the second network device in the RNA. In other words, if at least one network device that has sent the second information has not sent the third information to the second network device, then the second network device will continue to send the clock-related information within the coverage area of ​​the second network device in the RNA.

[0177] The M first network devices belong to the N first network devices, which can be understood as the N first network devices including the M first network devices. In some optional embodiments, the N second information respectively include the identifiers of the N first network devices and the identifiers of the coverage ranges of the N second network devices, and the M third information respectively include the identifiers of the M first network devices and the identifiers of the coverage ranges of the M second network devices, wherein the second network device determines whether to send the clock-related information within the coverage range of the second network device in the RNA based on the third information, including: when the identifiers of the N first network devices are all carried in the M third information, the second network device does not send the clock-related information within the coverage range of the second network device in the RNA based on the third information.

[0178] That is to say, the process of the second network device determining whether to send the clock-related information within the coverage range of the second network device in the RNA can be achieved by carrying the identifier of the sending end and the identifier of the affected range through the second information, and carrying the identifier of the sending end and the identifier of the affected range through the third information.

[0179] Through the above embodiment, when each network device that has sent the second information sends the third information to the second network device, the second network device stops sending the clock-related information within the coverage range of the second network device in the RNA, thereby saving overhead.

[0180] Optionally, in another implementation scenario of the above embodiment, the second network device determines whether to send the clock-related information within the coverage of the second network device in the RNA based on the third information, and also includes: when M is less than N, the second network device sends the clock-related information within the coverage of the second network device in the RNA.

[0181] M being smaller than N can be understood as at least one network device that has sent the second information not sending the third information to the second network device.

[0182] Through the above embodiment, when at least one network device that has sent the second information does not send the third information to the second network device, the second network device continues to send the clock-related information within the coverage of the second network device in the RNA, thereby ensuring the continuity of the clock-related services of the terminal device having the RNA including the coverage of the second network device.

[0183] Optionally, in another implementation scenario of the above embodiment, the second network device determines whether to send the clock-related information within the coverage of the second network device in the RNA based on the third information, including: when the RNA of the terminal device interested in clock-related information maintained by the second network device includes the coverage of the second network device, the second network device sends the clock-related information within the coverage of the second network device in the RNA.

[0184] That is to say, if the RNA of the terminal device maintained by the second network device includes cell 1, the second network device still sends the clock-related information within the coverage range of the second network device in the RNA to ensure the continuity of the clock-related services of the terminal device maintained by itself.

[0185] Optionally, in another implementation scenario of the above embodiment, the second network device receives the second information from the first network device, including: the second network device receives at least N second information respectively from N first network devices, N is a positive integer; wherein, the second network device receives the third information from the first network device, including: the second network device receives at least M third information respectively from M first network devices, M is a positive integer, and the M first network devices belong to the N first network devices; wherein, the second network device determines whether to send the clock-related information within the coverage of the second network device in the RNA based on the third information, including: when M is equal to N, and after the second network device receives the target third information in at least M third information, when the second network device receives the target second information in at least N second information, the second network device sends the clock-related information within the coverage of the second network device in the RNA based on the third information, wherein the target third information and the target second information come from the same first network device.

[0186] The above solution can be understood as follows: if a network device sends the second information, the third information, and the second information to a second network device in sequence, the second network device can continue to send the clock-related information within the coverage area of ​​the second network device in the RNA. On the other hand, if each network device that sent the second information sends the third information and does not send the second information again after sending the third information, the second network device can stop sending the clock-related information within the coverage area of ​​the second network device in the RNA.

[0187] Optionally, in another implementation scenario of the above embodiment, when the second network device receives the second information from the first network device, the first network device is in the first state; when the second network device receives the third information from the first network device, the first network device is in the second state; wherein, the second network device determines whether to send the clock-related information within the coverage of the second network device in the RNA based on the third information, including: when all first network devices are in the second state, the second network device does not send the clock-related information within the coverage of the second network device in the RNA; when at least one first network device is in the first state, the second network device sends the clock-related information within the coverage of the second network device in the RNA.

[0188] Among them, the first state can be understood as the RNA range configured for the non-activated terminal devices that are interested in clock-related information maintained by the first network device includes the coverage range of the second network device; the second state can be understood as the RNA range configured for the non-activated terminal devices that are interested in clock-related information maintained by the first network device does not include the above-mentioned coverage range of the second network device.

[0189] Optionally, in another implementation scenario of the above embodiment, the first network device sends the third information to the second network device, including: after the terminal device enters a connected state or an idle state, or after the first network device deletes or migrates the context of the terminal device, or after the first network device learns that the terminal device is within the coverage of the first network device, the first network device sends the third information to the second network device.

[0190] The first network device can switch the terminal device into a connected state or an idle state. When the terminal device switches to the connected state, if the terminal device wants to leave the coverage of the first network device and enter the coverage of other network devices, a switching process will be performed, and the network device of the new service cell will provide clock-related information, so that it will not enter the coverage of the second network device without the knowledge of the second network device. When the terminal device switches to the idle state, the terminal device can move within the coverage of each network device, and the probability of appearing in the coverage of the second network device is small. Therefore, after the terminal device enters the connected state or the idle state, the first network device sends the third information to the second network device, which can save the overhead of the second network device.

[0191] The first network device can delete the context of the terminal device if it determines that an abnormal situation has occurred (for example, the terminal device has not initiated a periodic RNA-U process for a long time). In this case, even if the second network device sends clock-related information within the coverage of the second network device, clock synchronization may not be possible due to the abnormality of the terminal device. Therefore, after the first network device deletes the context of the terminal device, it can send the third information to the second network device to save the overhead of the second network device.

[0192] The first network device can migrate the context of the terminal device to other network devices. It is understandable that after this, the first network device no longer serves as the anchor base station for the terminal device, and the network device that receives the context of the terminal device serves as the new anchor base station. The new anchor base station will determine a new RNA, and the new RNA may not include the coverage of the second network device. Alternatively, the new anchor base station can execute the method provided in the present application, and send the second information to the second network device when the new RNA also includes the coverage of the second network device. Therefore, after the first network device migrates the context of the terminal device to other network devices, the terminal device may not exist within the coverage of the second network device, or whether the second network device sends clock-related information can be indicated by another network device.

[0193] The first network device learns that the terminal device is within the coverage of the first network device, indicating that the terminal device is not within the coverage of the second network device. The second network device does not need to send clock-related information to the terminal device that cannot exist within its coverage.

[0194] Optionally, in another implementation scenario of the above embodiment, the method 300 also includes: the first network device determines that the terminal device is within the coverage of the first network device based on at least one of the following: the first network device performs small data packet transmission (SDT) with the terminal device; or, the first network device receives location information of the terminal device, and the location information indicates that the terminal device is within the coverage of the first network device.

[0195] When the first network device and the terminal device perform the SDT process, the first network device can determine that the terminal device is within the coverage of the first network device.

[0196] Furthermore, the first network device may determine that all terminal devices interested in clock-related information within an RNA including the coverage of the second network device have initiated an SDT process. Therefore, the first network device may determine that none of the above-mentioned terminal devices reside within the coverage of the second network device. Therefore, the first network device may instruct the second network device through the third information not to send clock-related information within the coverage of the second network device.

[0197] This application does not limit the message that the location information carries, and the location information can be carried in any message. This application does not limit the name of the location information, and the location information can also be called indication information or have other names.

[0198] Optionally, in another implementation scenario of the above embodiment, S220 includes: after the first network device terminates the transmission of the small data packet of the terminal device, the first network device sends the second information to the second network device.

[0199] After the SDT process is terminated, the first network device may determine that not all terminal devices interested in clock-related information whose RNA includes the coverage of the second network device reside under the first network device. In other words, the first network device may determine that all terminal devices interested in clock-related information whose RNA includes the coverage of the second network device do not reside under the first network device.

[0200] Figure 4 is a schematic flow chart of another communication method 400 provided in an embodiment of the present application. In method 400, when the number of Inactive UEs of interest maintained by a base station is increased or decreased, the base station can send an indication message to a neighboring base station, indicating that the RNA of the Inactive UE of interest includes the neighboring base station (corresponding to the second information), or that the RNA of the Inactive UE of interest does not include the neighboring base station (corresponding to the third information). Method 400 can be combined with method 300, and method 400 is described below in conjunction with Figure 4.

[0201] S410: gNB1 obtains information about UEs that are interested in clock-related information.

[0202] gNB1 can obtain information indicating that the connected UE is interested in clock-related information. The clock-related information includes clock information and / or clock synchronization status information. For example, gNB1 can obtain information indicating whether the connected UE is interested in clock-related information from a core network element (or core network node), a neighboring gNB, or a UE. For details, see the description of S310 and are not repeated here.

[0203] It should be noted that when the UE is in a connected state, the serving base station provides the UE with clock-related information.

[0204] S420, gNB1 sends first information to UE.

[0205] The first information may indicate an RNA. The first information may indicate that the UE enters the Inactive state. For other descriptions of the first information, see above and are not repeated here. The following description uses the example of an RNA covering the coverage of gNB1, gNB2, and gNB3.

[0206] S430, gNB1 sends second information to gNB2 and gNB3.

[0207] The following description uses gNB2 as an example. The description of gNB3 is similar to that of gNB2. The description of gNB3 can be found in the description of gNB2 and is not repeated here.

[0208] When gNB1 begins serving as an anchor base station for an Inactive UE interested in clock-related information, gNB1 may determine whether the RNA configured for the Inactive UE includes at least one cell of gNB2, and such cell is not included in the existing RNAs of Inactive UEs interested in clock-related information maintained by gNB1. If so (i.e., the RNA configured for the Inactive UE includes at least one cell of gNB2, and such cell is not included in the existing RNAs of Inactive UEs interested in clock-related information maintained by gNB1), gNB1 sends a second message to gNB2, indicating that the RNA of at least one Inactive UE interested in clock-related information with gNB1 as the anchor base station includes (partial) coverage of gNB2.

[0209] The second information may include the identifier of gNB1 and the affected range (also called RNA range) of gNB2. The affected range of gNB2 includes information about cells under gNB2 included in the RNA range of Inactive UEs interested in clock-related information maintained by gNB1. For example, the affected range of gNB2 may be the identifier of at least one cell or at least one RAN area identifier.

[0210] Optionally, the second information may further include a first flag and / or a first identifier. The first flag may be referred to as flag field 1, indicating that the affected range of gNB2 is a newly added range, i.e., indicating that the affected range of gNB2 is within the RNA of the inactive UE of interest under gNB1. The first identifier may indicate the clock information of interest to the UE. For further description of the second information and the information contained in the second information, please refer to the previous text and are not repeated here.

[0211] When at least one of the following events occurs, gNB1 starts acting as an anchor base station for an Inactive UE that is interested in clock-related information.

[0212] (1) gNB1 releases a connected UE into the inactive state, and the connected UE is interested in clock-related information.

[0213] (2) gNB1 obtains the context of an Inactive UE from another gNB and sends an RRCRelease message to the UE to keep it in the Inactive state. The Inactive UE is interested in clock-related information.

[0214] S440. gNB1 sends third information to gNB2 and gNB3.

[0215] The following description uses gNB2 as an example. The description of gNB3 is similar to that of gNB2. The description of gNB3 can be found in the description of gNB2 and is not repeated here.

[0216] When gNB1 ceases to serve as an anchor base station for an Inactive UE interested in clock-related information, gNB1 may determine whether the RNA configured for the Inactive UE does not include at least one cell of gNB2, which is not within the RNAs of existing Inactive UEs of interest maintained by gNB1. If so (i.e., the RNA configured for the Inactive UE does not include at least one cell of gNB2, which is not within the RNAs of existing Inactive UEs of interest maintained by gNB1), gNB1 sends a third message to gNB2, indicating that (part of) gNB2's coverage area no longer falls within the RNAs of Inactive UEs of interest maintained by gNB1.

[0217] The third information may include the identifier of gNB1 and the affected range (or RNA range) of gNB2. The affected range of gNB2 includes information about cells under gNB2 that are no longer part of the RNA of the Inactive UEs interested in clock-related information maintained by gNB1. For example, this may be the identifier of at least one cell or at least one RAN area identifier. Optionally, the third information may also include a second flag. The second flag may be Flag Field 2, indicating that the affected range of gNB2 is reduced, i.e., the affected range of gNB2 is no longer configured within the RNA of the Inactive UEs interested in clock-related information maintained by gNB1. For further description of the third information and the information contained therein, please refer to the previous text and will not be repeated here.

[0218] When at least one of the following events occurs, gNB1 no longer serves as an anchor base station for Inactive UEs interested in clock-related information.

[0219] (1) gNB1 migrates the UE context to another gNB.

[0220] (2) gNB1 switches the Inactive UE to the Connected or Idle state.

[0221] (3) gNB1 deletes the context of the UE, for example, due to some abnormal situation (such as the UE does not initiate the periodic RNA-U process for a long time).

[0222] At S450, gNB2 and gNB3 determine whether to send clock-related information.

[0223] It should be noted that S450 is an optional step in method 400. That is, method 400 may not include S450. The following description uses gNB2 as an example. The description of gNB3 is similar to that of gNB2. The description of gNB3 can refer to the description of gNB2 and is not repeated here.

[0224] In some optional embodiments, gNB2 maintains information on a per-cell basis regarding whether a cell belongs to an RNA of an Inactive UE interested in clock-related information. For example, gNB2 may determine whether a cell under gNB2 belongs to an RNA of an Inactive UE interested in clock-related information based on the second information and third information received from a neighboring gNB and the RNA of an Inactive UE interested in clock-related information maintained by gNB2 itself.

[0225] If a cell belongs to the RNA of an interested Inactive UE, gNB2 may broadcast SIB9 in the cell to indicate 5G clock information and / or clock status synchronization indication information (e.g., via an indication event identifier).

[0226] FIG5 is a schematic flow chart of another communication method 500 provided in an embodiment of the present application. Method 500 is an example of method 300 and method 400 and does not constitute a limitation of the present application. Method 500 includes cases (1) to (5). Method 500 is described below in conjunction with FIG5.

[0227] Before situation (1) occurs, assume that none of gNB1 to gNB3 maintains any Inactive UEs that are interested in clock-related information. Connected UE1, UE2, and UE3 served by gNB1 are interested in clock-related information.

[0228] Case (1): gNB1 releases UE1 and puts it into the Inactive state. The RNA configured for UE1 includes the coverage of gNB1 but not the coverage of gNB2 and gNB3. gNB1 does not need to send the second or third information to neighboring gNBs.

[0229] In case (1), gNB1 can broadcast SIB9 messages to provide clock-related information. gNB2 and gNB3 do not maintain Inactive UEs that are interested in clock-related information, nor do other gNBs maintain RNAs for Inactive UEs that are interested in clock-related information that include their own (gNB2 or gNB3) coverage. Therefore, gNB2 and gNB3 do not need to broadcast SIB9 messages.

[0230] Case (2): gNB1 releases UE2 and puts it into the Inactive state. The RNA configured for UE1 includes the coverage areas of gNB1 and gNB2, but not gNB3. gNB1 can determine that the coverage area of ​​gNB2 does not belong to the existing RNA for Inactive UEs interested in clock-related information. Therefore, gNB1 sends a second message to gNB2.

[0231] In case (2), gNB1 and gNB2 broadcast SIB9 messages to provide clock-related information. gNB3 does not need to broadcast SIB9.

[0232] Case (3): gNB1 releases UE3 and enters the Inactive state. The RNA configured for UE1 includes the coverage areas of gNB1, gNB2, and gNB3. gNB1 can determine that the coverage area of ​​gNB2 belongs to the existing RNA of the Inactive UE that is interested in clock-related information. Therefore, gNB1 does not send the second message to gNB2. gNB1 can determine that the coverage area of ​​gNB3 does not belong to the existing RNA of the Inactive UE that is interested in clock-related information. Therefore, gNB1 sends the second message to gNB3.

[0233] In case (3), gNB, gNB2, and gNB3 broadcast SIB9 messages to provide clock-related information.

[0234] Case (4): UE2 enters the Connected state (shaded in Figure 5). gNB1 determines that the RNAs of existing Inactive UEs (i.e., UE1 and UE3) that are interested in clock-related information include UE2's original RNA range, so gNB1 does not need to send the third message to gNB2 or gNB3. Alternatively, gNB1 determines that the coverage ranges of gNB2 and gNB3 are within the RNAs of other existing UEs (i.e., UE1 and UE3) maintained by gNB1, for example, UE3's RNA, so gNB1 does not need to send the third message to gNB2 or gNB3.

[0235] In case (4), gNB, gNB2, and gNB3 broadcast SIB9 messages to provide clock-related information.

[0236] Case (5): UE3 enters the connected state. gNB1 determines that the coverage areas of gNB2 and gNB3 no longer belong to the RNA of the Inactive UE that is interested in clock-related information maintained by gNB1. gNB1 sends a third message to gNB2 and gNB3.

[0237] In case (5), gNB1 broadcasts SIB9 messages to provide clock-related information. gNB2 and gNB3 do not maintain Inactive UEs that are interested in clock-related information, nor do any other gNB maintain RNAs for Inactive UEs that are interested in clock-related information that include their own coverage. Therefore, gNB2 and gNB3 do not need to broadcast SIB9.

[0238] The present application also provides another communication method, comprising: when a network device begins broadcasting clock-related information, the network device sends first indication information to a neighboring network device, the first indication information being used to instruct the network device to begin broadcasting clock-related information. When the network device stops broadcasting clock-related information, the network device sends second indication information to the neighboring network device, the second indication information being used to instruct the network device to stop broadcasting clock-related information. Thus, when the network device determines that a neighboring network device is affected, i.e., when the RNA of inactive terminal devices maintained by the network device that are interested in clock-related information includes the coverage range of the neighboring network device, the network device can determine, based on the first indication information, that the neighboring network device has begun broadcasting clock-related information, thereby eliminating the need to send second information to the neighboring network device. For example, when gNB1 sends the second information to the affected gNBs, it excludes gNBs known to be broadcasting clock-related information.

[0239] Figure 6 is a schematic flow chart of another communication method 600 provided in an embodiment of the present application. In method 600, if a base station determines that all inactive UEs interested in clock-related information within the coverage area of ​​a neighboring base station included in its configured RNA have initiated an SDT process, the base station may send a third message to the neighboring base station. Method 600 can be combined with method 300, 400, or 500. Method 600 is described below in conjunction with Figure 6.

[0240] Before executing method 600, assume that the RNAs maintained by gNB1 for Inactive UE1 and Inactive UE2, both of which are interested in clock-related information, include the coverage area of ​​gNB2, and that no RNAs for other interested Inactive UEs under gNB1 include the coverage area of ​​gNB2. gNB1 has already sent a second message to gNB2, instructing gNB2 to send clock-related information within its coverage area.

[0241] S610: Inactive UE1 and Inactive UE2 initiate an SDT process to gNB1.

[0242] S620: gNB1 sends third information to gNB2.

[0243] In some embodiments, gNB1 may determine that all Inactive UEs interested in clock-related information whose RNA includes the coverage of gNB2 have initiated an SDT procedure or are in the SDT procedure. Consequently, gNB1 may determine that all Inactive UEs interested in clock-related information whose RNA includes the coverage of gNB2 are not within the coverage of gNB2. Therefore, gNB1 may send third information to gNB2. This third information may indicate that none of the Inactive UEs interested in clock-related information maintained by gNB1 are within the coverage of gNB2. Consequently, gNB2 may not send clock-related information within its coverage.

[0244] S630: Inactive UE1 terminates the SDT process.

[0245] S640: gNB1 sends second information to gNB2.

[0246] In some embodiments, gNB1 may determine that not all of gNB2's Inactive UEs interested in clock-related information whose RNA contains information are in the SDT process (UE1 has terminated the SDT process and is not in the SDT process). Therefore, gNB1 may send second information to gNB2 to indicate that the Inactive UEs interested in clock-related information maintained by gNB1 may reside under gNB2. As a result, gNB2 may send clock-related information within its coverage area.

[0247] Optionally, in method 600, gNB2 is not a new serving gNB for the Inactive UE to initiate the SDT process.

[0248] Figure 7 is a schematic flow chart of another communication method 700 provided in an embodiment of the present application. In method 700, a base station may configure a time synchronization coverage area (TSA) for a UE and introduce a TSA update process. Method 700 can be combined with any of the aforementioned methods. Method 700 is described below in conjunction with Figure 7.

[0249] S710: The UE initiates RRC setup to gNB1.

[0250] After the UE initiates the RRC setup, the UE is in a connected state.

[0251] S720, the UE sends demand information to the 5G core network (5G core network, 5GC).

[0252] The requirement information may indicate whether the UE has a requirement to configure TSA. The requirement information may also be referred to as indication information or have other names. It should be noted that S720 is an optional step in method 700, that is, method 700 may not include S720.

[0253] At S730, 5GC sends TSA information to gNB1.

[0254] S730 described above can also be understood as the base station (gNB1) obtaining the TSA information of the UE from the core network element. The TSA may indicate the RAN area for which the UE needs to obtain clock-related information. The TSA may include the coverage of at least one cell under at least one base station.

[0255] In some optional embodiments, when the UE is handed over, the source station may forward the TSA information to the target station, or the core network element may send the TSA information to the target station.

[0256] In some optional embodiments, the core network element configures TSA information to the base station side only when it learns that the UE has a need to configure TSA.

[0257] S740, gNB1 configures TSA for the UE.

[0258] For example, when gNB1 transfers the UE to the inactive state, it can configure TSA in the RRCRelease message. The TSA can be different from the configured RNA.

[0259] S750: The UE may initiate a TSA update process to gNB2.

[0260] For example, when a UE moves out of the TSA range configured by gNB1, it can initiate a TSA update procedure with the new serving eNB (i.e., gNB2). Alternatively, it can initiate an RRC recovery procedure in the resident cell to notify the new serving eNB that the UE has moved out of the TSA range. The RRCResumeRequest message can include a cause value, which can indicate that the UE is initiating a TSA update procedure.

[0261] S760: gNB2 notifies gNB1 that the UE initiates the TSA update process.

[0262] In other words, the new serving base station may send an indication to the UE's last serving base station, indicating that the UE has initiated a TSA update procedure. Furthermore, in some optional embodiments, the UE's last serving base station (i.e., gNB1) may migrate the UE's context to the new serving base station (i.e., gNB2).

[0263] It should be noted that the aforementioned method can be combined with method 700. For example, the RNA in the aforementioned method can be replaced by TSA.

[0264] Through the above embodiment, TSA and RNA can be decoupled on the air interface side, and the RAN network can set RNA and TSA as needed, thereby improving the flexibility of RAN side configuration.

[0265] The following is an introduction to the device embodiment corresponding to the method embodiment of the present application. The following is only a brief introduction to the device, and the specific implementation steps and details of the solution can be referred to the method embodiment above.

[0266] To implement the various functions of the method provided herein, the communication device may include hardware structures and / or software modules, and the aforementioned functions may be implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular one of the aforementioned functions is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0267] Figure 8 is a schematic block diagram of a communication device 800 according to an embodiment of the present application. The communication device 800 includes a processor 810 and a communication interface 820, which may be interconnected via a bus 830. The communication device 800 may be a first network device or a second network device.

[0268] Optionally, the communication device 800 may further include a memory 840. The memory 840 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM). The memory 840 is used for related instructions and data. The memory 840 may be integrated with the processor 810 or provided separately.

[0269] The processor 810 may be one or more central processing units (CPUs). In the case where the processor 810 is a CPU, the CPU may be a single-core CPU or a multi-core CPU. The processor 810 may be a signal processor, a chip, or other integrated circuit that can implement the method of the present application, or a portion of the circuitry used for processing functions in the aforementioned processor, chip, or integrated circuit. In addition, the communication interface 820 may also be an input / output interface, which is used for inputting or outputting signals or data, or may be an input / output circuit.

[0270] Exemplarily, when the communication apparatus 800 is a first network device, the processor 810 is configured to perform the following operations: sending first information to a terminal device that is interested in clock-related information; and sending second information to the second network device.

[0271] The above contents are merely exemplary descriptions. The communication device 800 is responsible for executing the methods or steps related to the first network device in the above method embodiment.

[0272] Exemplarily, when the communication apparatus 800 is a second network device, the processor 810 is configured to perform the following operations: receive second information from a first network device; and send the clock-related information according to the second information.

[0273] The above contents are merely exemplary descriptions. The communication device 800 is responsible for executing the methods or steps related to the second network device in the above method embodiment.

[0274] It is understood that the communication interface 820 may also be referred to as a transceiver. The transceiver may include a transmitter and a receiver, where the transmitter is used to perform a transmission operation and the receiver is used to perform a reception operation. For example, the processor 810 is used to control the transceiver to receive and / or transmit signals.

[0275] It should be noted that the communication device 800 may include a transmitter but not a receiver. Alternatively, the communication device 800 may include a receiver but not a transmitter. The specific implementation depends on whether the above solution executed by the communication device 800 includes a sending action and a receiving action.

[0276] The above description is merely exemplary. For details, please refer to the contents of the above method embodiments. The implementation of each operation in FIG8 may also correspond to the corresponding description of the method embodiments shown in FIG3 to FIG7.

[0277] For example, the communication device 800 may be used to implement the solutions shown in FIG. 3 to FIG. 7 .

[0278] In the case where the communication apparatus 800 is a first network device, the communication interface 820 may be configured to send the first information to a terminal device that is interested in clock-related information, and to send the second information to the second network device.

[0279] In the case where the communication apparatus 800 is a second network device, the communication interface 820 may be configured to receive second information from the first network device and send the clock-related information according to the second information.

[0280] For other implementations, please refer to the detailed description of the embodiments shown in Figures 3 to 7 above, which will not be repeated here. It should be understood that the specific process of each component performing the above corresponding process has been detailed in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0281] Figure 9 is a schematic block diagram of another communication device 900 according to an embodiment of the present application. Communication device 900 can be a first network device or a second network device, or a chip or module within the first network device or the second network device, and is configured to implement the methods described in the embodiments of Figures 3 to 7. For details, please refer to the relevant descriptions of the aforementioned method embodiments.

[0282] The communication device 900 includes a transceiver unit 910. The transceiver unit 910 is described below by way of example.

[0283] The transceiver unit 910 may include a transmitting unit and a receiving unit. The transmitting unit is used to execute the transmitting action of the communication device 900, and the receiving unit is used to execute the receiving action of the communication device 900. For ease of description, the embodiment of the present application combines the transmitting unit and the receiving unit into a single transceiver unit. This is described here as a unified description and will not be repeated later. The transceiver unit 910 can implement corresponding communication functions. The transceiver unit 910 can also be referred to as a communication interface or communication module.

[0284] It should be noted that the communication device 900 may include a sending unit but not a receiving unit. Alternatively, the communication device 900 may include a receiving unit but not a sending unit. The specific implementation depends on whether the above solution executed by the communication device 900 includes a sending action and a receiving action.

[0285] Exemplarily, the transceiver unit 910 is configured to send first information, etc. to a terminal device that is interested in clock-related information.

[0286] Optionally, the communication apparatus 900 may further include a processing unit 920 configured to execute steps such as processing and coordination of the first network device.

[0287] Exemplarily, the transceiver unit 910 is configured to receive second information from a first network device, etc.

[0288] Optionally, the communication apparatus 900 may further include a processing unit 920 configured to execute steps such as processing and coordination of the second network device.

[0289] The above contents are merely exemplary descriptions. The communication device 900 is responsible for executing the methods or steps related to the first network device or the second network device in the above method embodiments.

[0290] Optionally, the communication device 900 further includes a storage unit 930, which is configured to store a program or code for executing the aforementioned method. Alternatively, the storage unit 930 may be configured to store instructions and / or data, and the processing unit 920 may read the instructions and / or data in the storage unit 930 to enable the communication device 900 to implement the aforementioned method embodiments. For example, the communication device 900 may be configured to execute the schemes illustrated in Figures 3 to 7.

[0291] In the case where the communication apparatus 900 is a first network device, the processing unit 920 may be configured to send first information to a terminal device that is interested in clock-related information; and send second information to the second network device.

[0292] In the case where the communication apparatus 900 is a second network device, the processing unit 920 may be configured to receive second information from a first network device; and send the clock-related information according to the second information.

[0293] For other implementations, please refer to the detailed description of the embodiments shown in Figures 3 to 7 above, which will not be repeated here. It should be understood that the specific process of each component performing the above corresponding process has been detailed in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0294] The device embodiments shown in Figures 8 and 9 are used to implement the contents described in Figures 3 to 7. The specific execution steps and methods of the devices shown in Figures 8 and 9 can refer to the contents described in the above method embodiments.

[0295] The present application also provides a communication device, including a processor and a memory, wherein the memory is used to store instructions, and the processor is used to call and execute the instructions stored in the memory, so that the communication device executes the methods in the above embodiments.

[0296] The present application also provides a chip, including a processor, for calling and executing instructions stored in a memory from the memory, so that a communication device equipped with the chip executes the methods in the above embodiments.

[0297] The present application also provides another chip, comprising: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is configured to execute code in a memory. When the code is executed, the processor is configured to perform the methods described in each of the above embodiments. Optionally, the chip also includes a memory configured to store computer programs or code.

[0298] The present application also provides a processor, which is coupled to a memory and is used to execute the methods and functions related to the communication device in any of the above embodiments.

[0299] In another embodiment of the present application, a computer program product including a computer program or instructions is provided. When the computer program or instructions are executed on a computer, the method of the aforementioned embodiment is implemented.

[0300] The present application also provides a computer program. When the computer program is executed in a computer, the methods of the aforementioned embodiments are implemented.

[0301] In another embodiment of the present application, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program. When the computer program is executed by a computer, the methods of the aforementioned embodiments are implemented.

[0302] The present application also provides a communication system, including a first network device and a second network device, wherein the first network device is used to execute the action executed by the first network device in the aforementioned method, and the second network device is used to execute the action executed by the second network device in the aforementioned method.

[0303] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0304] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0305] In the several embodiments provided in this 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 schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as 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 mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0306] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0307] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0308] 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 this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling 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 method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0309] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that, Including: A first network device sends first information to a terminal device interested in clock-related information, where the first information indicates a radio access network notification area (RNA), and the RNA includes the coverage range of the first network device and the coverage range of a second network device; The first network device sends second information to the second network device, where the second information indicates that the second network device sends the clock-related information within the coverage range of the second network device.

2. The method according to claim 1, wherein The second information includes an identifier of the first network device and / or an identifier of the coverage range of the second network device, where the identifier of the first network device is used to indicate that the coverage range of the second network device corresponds to the first network device.

3. The method according to claim 1 or 2, characterized in that, The first information is further used to release the terminal device, such that the terminal device enters an inactive state.

4. The method according to any one of claims 1 to 3, characterized in that, Also including: The first network device sends third information to the second network device, where the third information is used to indicate that the second network device does not send the clock-related information within the coverage range of the second network device.

5. The method according to claim 4, wherein The third information includes an identifier of the first network device and / or an identifier of the coverage range of the second network device.

6. The method according to claim 4 or 5, characterized in that The first network device sending the third information to the second network device includes: After the terminal device enters a connected state or an idle state, or after the first network device deletes or migrates the context of the terminal device, or after the first network device learns that the terminal device is within the coverage range of the first network device, the first network device sends the third information to the second network device.

7. The method according to claim 6, wherein Also including: The first network device determines that the terminal device is within the coverage range of the first network device according to at least one of the following: The first network device performs small packet transmission with the terminal device; or The first network device receives location information of the terminal device, where the location information indicates that the terminal device is within the coverage range of the first network device.

8. The method according to any one of claims 1 to 7, characterized in that, The first network device sending the second information to the second network device includes: After the first network device terminates small packet transmission with the terminal device, the first network device sends the second information to the second network device.

9. A communication method, characterized in that, Including: A second network device receives second information from a first network device, where the second information is used to indicate that the second network device sends clock-related information for the coverage range of the second network device in a radio network notification area (RNA); The second network device sends the clock-related information according to the second information.

10. The method according to claim 9, characterized in that, The second information includes an identifier of the first network device and / or an identifier of the coverage range of the second network device in the RNA, and the identifier of the first network device is used to indicate that the coverage range of the second network device corresponds to the first network device.

11. The method according to claim 9 or 10, characterized in that, The second network device sending the clock-related information according to the second information includes: The second network device sends the clock-related information within the coverage range of the second network device in the notification area.

12. The method according to any one of claims 9 to 11, characterized in that, Also including: The second network device receives third information from the first network device, where the third information is used to instruct the second network device not to send the clock-related information within the coverage area of the second network device in the RNA.

13. The method according to claim 12, characterized in that, The third information includes the identifier of the first network device, and / or, the identifier of the coverage area of the second network device in the RNA.

14. The method according to claim 12 or 13, characterized in that, It further includes: The second network device determines whether to send the clock-related information within the coverage area of the second network device in the RNA according to the third information.

15. The method according to claim 14, characterized in that, The second network device receives second information from the first network device, including: The second network device receives N pieces of second information from N first network devices respectively, where N is a positive integer; among them, The second network device receives third information from the first network device, including: The second network device receives M pieces of third information from M first network devices respectively, where M is a positive integer, and the M first network devices belong to the N first network devices; among them, The second network device determines whether to send the clock-related information within the coverage area of the second network device in the RNA according to the third information, including: When M is equal to N, the second network device does not send the clock-related information within the coverage area of the second network device in the RNA according to the third information.

16. The method according to claim 15, characterized in that, The second network device determines whether to send the clock-related information within the coverage area of the second network device in the RNA according to the third information, and further includes: When M is less than N, the second network device sends the clock-related information within the coverage area of the second network device in the RNA.

17. A communication device, characterized in that, It includes a processing circuit and an input / output interface. The input / output interface is used for inputting and / or outputting signals. The processing circuit is used to execute the method according to any one of claims 1 to 8, or the processing circuit is used to execute the method according to any one of claims 9 to 16.

18. A communication device, characterized in that, It includes: A processor and a memory. A computer program or instruction is stored in the memory. The processor is used to execute the computer program or instruction, or cause the communication device to execute the method according to any one of claims 9 to 16.

19. A computer-readable storage medium, characterized in that, A computer program or instruction is stored on the computer-readable storage medium. When the computer program or the instruction runs on the computer, the method according to any one of claims 1 to 8 is caused to be executed, or the method according to any one of claims 9 to 16 is caused to be executed.

20. A computer program product, characterized in that, It includes a computer program or instruction. When the computer program or instruction runs, the method according to any one of claims 1 to 8 is implemented, or the method according to any one of claims 9 to 16 is implemented.

21. A communication system, characterized in that, It includes a first network device and a second network device. The first network device is used to execute the method according to any one of claims 1 to 8, and the second network device is used to execute the method according to any one of claims 9 to 16.

Images