Communication method and device

Abstract

The invention provides a communication method and device, and relates to the technical field of communication. The method comprises: a first network device sending first information to a terminal device interested in clock-related information, the first information indicating an RNA, the RNA comprising 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 indicates the second network device to send the clock-related information within the coverage range of the second network device. And the anchor base station can send second information to the neighbor base station under the condition that the RNA of the terminal equipment which is maintained by the anchor base station and is interested in the clock-related information comprises the coverage range of other neighbor base stations. The neighbor base station can send the clock related information according to the second information, so that the situation that an application needing the clock related information cannot normally work due to the fact that the application cannot obtain the clock related information in time is avoided, and the continuity of clock related services is guaranteed.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a communication method and device. Background Art

[0002] 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 I-RNTI of the UE. 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 inability of applications that require clock-related information to work normally due to the inability to obtain clock-related information in a timely manner.

[0003] Therefore, how to ensure the continuity of clock-related businesses is an urgent problem to be solved. Summary of the invention

[0004] The present application provides a communication method and device, which can ensure the continuity of clock-related services.

[0005] In a first aspect, a communication method is provided, comprising: a first network device sends first information to a terminal device that is 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 indicating that the second network device sends the clock-related information within the coverage range of the second network device.

[0006] 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 can implement all or part of the functions of the first network device. Exemplarily, the first network element device may be called an anchor network device, a last serving network device accessed by a terminal device, or have other names.

[0007] Through the above embodiments, when the RNA of the terminal devices interested in clock-related information maintained by the anchor base station includes the coverage ranges of other neighbor base stations, the anchor base station may send the second information to the neighbor base stations. The neighbor base stations may send the clock-related information according to the second information, so that the terminal devices can also receive the clock-related information within the coverage ranges of the neighbor base stations, avoiding that applications in need of the clock-related information cannot work properly due to the failure to obtain the clock-related information in time, and thus ensuring the continuity of clock-related services.

[0008] In combination with the first aspect, in some implementation manners of the first aspect, the second information includes the identifier of the first network device and / or the 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.

[0009] Through the above embodiments, the second network device may determine the source of the second information according to the second information. Alternatively, the second network device may determine to send the clock-related information within the coverage range of the second network device according to the second information, ensuring the continuity of clock-related services of the terminal devices within the coverage range of the second network device.

[0010] In combination with the first aspect, in some implementation manners of the first aspect, the first information is further used to release the terminal device, so that the terminal device enters the inactive state.

[0011] In combination with the first aspect, in some implementation manners 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.

[0012] Through the above embodiments, when the RNA of the terminal devices interested in clock-related information maintained by the anchor base station does not include the coverage ranges of other neighbor base stations, the anchor base station may send the third information to the neighbor base stations. The third information may indicate that the second network device does not send the clock-related information within the coverage range of the second network device, thereby saving overhead.

[0013] In combination with the first aspect, in some implementation manners of the first aspect, the third information includes the identifier of the first network device and / or the identifier of the coverage range of the second network device.

[0014] Through the above embodiments, the second network device may determine the source of the third information according to the third information, so as to determine whether to stop sending the clock-related information within the coverage range of the second network device. Alternatively, the second network device may determine to stop sending the clock-related information within the coverage range of the second network device according to the third information, thereby saving overhead.

[0015] In combination with the first aspect, in some implementations of the first aspect, the first network device sends third information to the second network device, including: after the terminal device enters the connected state or the 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 area of the first network device, the first network device sends the third information to the second network device.

[0016] In combination with the first aspect, in some implementations of the first aspect, the method further includes: the first network device determines that the terminal device is within the coverage area 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, and the location information indicates that the terminal device is within the coverage area of the first network device.

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

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

[0019] This method may be executed by the second network device, or by a component in the second network device (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can implement all or part of the functions of the second network device.

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

[0021] 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 area of the second network device in the notification area.

[0022] In combination with the second aspect, in some implementations of the second aspect, the method further includes: the second network device receives third information from the first 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 area of the second network device in the RNA.

[0023] In combination with the second aspect, in some implementations of the second aspect, 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.

[0024] In combination with the second aspect, in some implementations of the second aspect, the method 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.

[0025] Through the above embodiments, the second network device can flexibly determine whether to send the clock-related information within the coverage area of the second network device in the RNA according to the third information, which can ensure the continuity of the clock-related services of the terminal device with an RNA including the coverage area of the second network device, or can save costs.

[0026] In combination with the second aspect, in some implementations of the second aspect, the second network device receiving the second information from the first network device includes: the second network device receives N second information from N first network devices respectively, where N is a positive integer; among them, the second network device receiving the third information from the first network device includes: the second network device receives M 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 determining whether to send the clock-related information within the coverage area of the second network device in the RNA according to the third information includes: 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.

[0027] Through the above embodiments, when each network device that has sent the second information has sent the third information to the second network device, the second network device stops sending the clock-related information within the coverage area of the second network device in the RNA, thereby saving costs.

[0028] In combination with the second aspect, in some implementations of the second aspect, the second network device determining whether to send the clock-related information within the coverage area of the second network device in the RNA according to the third information 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.

[0029] Through the above embodiments, in the case where 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 area of the second network device in the RNA, so as to ensure the continuity of the clock-related services of the terminal device having an RNA including the coverage area of the second network device.

[0030] In a third aspect, a communication device is provided, including a processing circuit (which may also be referred to as a processor) and an input / output interface (which may also be referred to as an interface circuit). The input / output interface is used for inputting and / or outputting signals, and the processing circuit is used to execute the first aspect and any possible method of the first aspect, or the processing circuit is used to execute the second aspect and any possible method of the second aspect.

[0031] In combination with the third aspect, in some implementation manners of the third aspect, the processor is used to communicate with other devices through the 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.

[0032] In a fourth aspect, a communication device is provided. The communication device may include devices or modules for performing communication device functions, etc.

[0033] In combination with the fourth aspect, in some implementation manners of the fourth aspect, the communication device may include modules or units corresponding one by one to the methods / operations / steps / actions described in the first aspect and any possible implementation manner of the first aspect. The module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software.

[0034] In combination with the fourth aspect, in some implementation manners of the fourth aspect, the communication device may include modules or units corresponding one by one to the methods / operations / steps / actions described in the second aspect and any possible implementation manner of the second aspect. The module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software.

[0035] In a fifth aspect, a computer-readable storage medium is provided. A computer program or instruction is stored on the computer-readable storage medium. When the computer program or the instruction runs 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.

[0036] In a sixth aspect, a computer program product is provided, including a computer program or instructions, which, when running on a computer, cause the first aspect and any possible method of the first aspect to be executed, or cause the second aspect and any possible method of the second aspect to be executed.

[0037] In a seventh aspect, a communication device is provided, including 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 above, or to execute any possible method of the second aspect above. The memory may be located inside or outside the communication device. And the processor includes one or more.

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

[0039] In an eighth aspect, a chip device is provided, including a processor configured to call a computer program or computer instructions in a memory to cause the processor to execute any implementation of the first aspect above, or to cause the processor to execute any implementation of the second aspect above.

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

[0041] In a ninth aspect, a communication system is provided, including a first network device and a second network device. The first network device is configured to execute the first aspect and any possible implementation of the first aspect above, and the second network device is configured to execute the second aspect and any possible implementation of the second aspect above.

[0042] For the description of the beneficial effects of any one of the second to ninth aspects and the like, reference may be made to the description of the beneficial effects of the first aspect. Description of the Drawings

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

[0044] Figure 2 FIG. is a schematic diagram of another communication system applicable to an embodiment of the present application.

[0045] Figure 3 FIG. is a schematic flowchart of a communication method provided by an embodiment of the present application.

[0046] Figure 4 FIG. is a schematic flowchart of another communication method provided by an embodiment of the present application.

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

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

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

[0050] Figure 8 It is a schematic block diagram of a communication device provided by an embodiment of the present application.

[0051] Figure 9 It is a schematic block diagram of another communication device provided by an embodiment of the present application. Detailed implementation manners

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

[0053] The present application will present various aspects, embodiments or features around a system 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 the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. In addition, combinations of these solutions may also be used.

[0054] The term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this article generally represents an "or" relationship between the associated objects before and after.

[0055] In addition, in the embodiments of the present application, words such as "exemplary" and "for example" are used to give examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly speaking, the use of the word "exemplary" is intended to present concepts in a specific manner.

[0056] The business scenarios described in the embodiments of the present application are for more clearly explaining the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those of ordinary skill in the art know that with the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0057] Reference to "one embodiment" or "some embodiments" etc. described in this specification means that a particular feature, structure, or characteristic described in connection with that embodiment is included in one or more embodiments of the present application. Thus, statements such as "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments", etc. that appear in different places in this specification are not necessarily all referring to the same embodiment, but mean "one or more but not all of the embodiments", unless otherwise specifically emphasized. The terms "comprising", "including", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.

[0058] The technical solutions of the embodiments of this 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) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5G mobile communication system or New Radio (NR) system, Narrow Band Internet of Things (NB-IoT) system, Enhanced Machine-Type Communication (eMTC) system, Enhanced Mobile Broadband (eMBB) system, Ultra Reliable Low Latency Communications (URLLC) system, satellite communication system or LTE-Machine-to-Machine (LTE-M) system, and future sixth-generation (6 th Generation, 6G) mobile communication system, etc.

[0059] 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", etc. In the embodiments of this application, transmission can include sending or receiving. Exemplarily, the transmission can be an uplink transmission. For example, it can be that a terminal device sends a signal to a network device; the transmission can also be a downlink transmission. For example, it can be that a network device sends a signal to a terminal device.

[0060] Figure 1 It is a schematic diagram of a communication system applicable to an embodiment of the present application. As Figure 1 shown, the communication system may include multiple communication devices, and the multiple communication devices may perform wireless communication through radio interface resources. Exemplarily, the communication devices may include network device 111, network device 112, network device 113, and terminal device 120.

[0061] Network device 111, network device 112, and network device 113 may communicate with each other through the Xn interface.

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

[0063] In some deployments, a 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, implementing radio resource control (RRC), and the functions of the packet data convergence protocol (PDCP) layer. The DU is responsible for processing physical layer protocols and real-time services, 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 for short). 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 ultimately become the information of the PHY layer, or is transformed from the information of the PHY layer, therefore, in this architecture, high-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or sent by the DU + AAU. It can be understood that the network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU can be classified as a network device in the radio access network (RAN), or the CU can be classified as a network device in the core network (CN), and this application does not limit this. The network device may adopt a CU-DU separation architecture or may not adopt a CU-DU separation architecture, and this application does not limit this.

[0064] In the embodiments of this application, the device for implementing the functions of the network device may be the network device, or may be a device capable of supporting the network device to implement such functions, such as a chip system, and this device may be installed in the network device. In the technical solutions of the embodiments of this application, taking the device for implementing the functions of the network device as the network device and taking the network device as a base station as an example, the technical solutions provided by the embodiments of this application are described.

[0065] The terminal device 120 can be any device with wireless transceiver capabilities. In other words, the terminal device 120 can be a device that provides voice and / or data connectivity to users. The terminal device 120 can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as on a ship); or it can be deployed in the air (such as on an airplane, a balloon, a satellite, etc.). The terminal device 120 can also be referred to as a user equipment (UE), an access terminal, a terminal, a subscriber unit, a user station, a mobile station (MS), a remote station, a remote terminal, a mobile device, a mobile terminal (MT), a user terminal, a wireless network device, a user agent, or a user device. In the embodiments of this application, the terminal device 120 includes but is not limited to: cellular phones, mobile phones, wireless data cards, wireless modems, tablet computers, laptop computers, cordless phones, session initiation protocol (SIP) phones, smart phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices, or other devices connected to a wireless modem, vehicle-mounted devices, wearable devices, drone devices, terminal devices in the Internet of Things or the Internet of Vehicles, and terminals in any form in future networks, relay user equipment, or terminals in a future evolved public land mobile network (PLMN), etc. The terminal device 120 can 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. The embodiments of this application do not limit this.

[0066] In the embodiments of the present application, the device for implementing the functions of the terminal device may be the terminal device or a device capable of supporting the terminal device to implement such functions, such as a chip system, which may be installed in the terminal. The chip system may be composed of chips or may include chips and other discrete devices. In the technical solutions of the embodiments of the present application, the device for implementing the functions of the terminal device is the terminal device, which may also be referred to as a terminal, and hereinafter, the terminal device being a UE will be taken as an example to describe the technical solutions provided by the embodiments of the present application.

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

[0068] The network device and the terminal device 120 may communicate through a wireless link. The transmission link from the network device to the terminal device 120 may be referred to as a downlink (DL) or a downlink channel for transmitting downlink signals. The transmission link from the terminal device 120 to the network device may be referred to as an uplink (UL) or an uplink channel for transmitting uplink signals. The network device and the terminal device 120 may also perform downlink data transmission through the downlink channel and uplink data transmission through the uplink channel. The terminal device 120 and other terminal devices may perform wireless communication. The transmission link from the terminal device 120 to other terminal devices may be referred to as a sidelink (SL) or a sidelink channel for transmitting sidelink signals. The terminal device 120 and other terminal devices may also perform sidelink data transmission through the sidelink channel.

[0069] Figure 2 is a schematic diagram of another communication system applicable to the embodiments of the present application. Exemplarily, Figure 2 the UE in the figure may be the above-mentioned terminal device 120, Figure 2 and the RAN in the figure may be any one of the above-mentioned network devices 111 to 113. Hereinafter, in combination with Figure 2 some core network elements that may be involved will be introduced.

[0070] The access and mobility management network element is mainly used for the attachment and tracking area update process of the terminal in the mobile network. The access and mobility management network element can provide non-access stratum (NAS) messages, complete registration management, connection management, reachability management, assign 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.

[0071] 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 may be a session management function (SMF). In future communication systems (such as 6G communication systems), the session management network element may still be an SMF network element, or it may have other names, which is not limited in this application.

[0072] 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 may also be called a PDU session anchor (PSA). In a 5G communication system, the user plane function network element may be a UPF. In future communication systems (such as 6G communication systems), the user plane function network element may still be a UPF network element, or may have other names, which is not limited in this application.

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

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

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

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

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

[0078] The unified data management network element is mainly used to manage the subscription information of terminal devices. In a 5G communication system, the unified data management network element can be the 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 also have other names, which are not limited in this application.

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

[0080] The authentication service function network element is mainly used to perform security authentication on terminal devices. In a 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 also have other names, which are not limited in this application.

[0081] The network capability open network element can expose some functions of the network to applications in a controlled manner. In a 5G communication system, the network capability open network element can be the network exposure function (NEF). In future communication systems (such as 6G communication systems), the network capability open network element can still be the NEF network element, or it can also have other names, which are not limited in this application.

[0082] The application function network element can provide service data of various applications to the control plane network element of the operator's communication network, or obtain network data information and control information from the control plane network element of the communication network. In a 5G communication system, the application function network element can be the application function (AF). In future communication systems (such as 6G communication systems), the application function network element can still be the AF network element, or it can also have other names, which are not limited in 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 by the operator network or by a third party.

[0083] A data network is mainly used to provide data transmission services for terminal devices. The data network can be a private network, such as a local area network, or a public data network (PDN), such as the Internet, or a proprietary network jointly deployed by operators, such as a configured IP multimedia core network subsystem (IMS) service. The data network can also come from a third party.

[0084] In Figure 1 the architecture shown below, the interface names and functions between each network element are as follows:

[0085] 1. N1: The interface between the AMF and the UE, which can be used to transfer QoS control rules, etc. to the UE.

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

[0087] 3. N3: The interface between the RAN and the UPF, which is used to transfer uplink or downlink user plane data between the RAN and the UPF.

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

[0089] 5. N6: The interface between the UPF and the DN, which is used to transfer uplink or downlink user data streams between the UPF and the DN.

[0090] 6. The service-based interfaces Nnssf, Nnef, Nausf, Nnrf, Namf, Npcf, Nsmf, and Nudm are service-based interfaces 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 respectively, and are used to call corresponding service-based operations.

[0091] It should be understood that the above-mentioned network elements or functions can be either network components in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (such as a cloud platform). Optionally, the above-mentioned network elements or functions can be implemented by one device, or jointly implemented by multiple devices, or can also be a functional module within one device. The embodiments of the present application do not make specific limitations in this regard.

[0092] It should be noted that the network device can also interact with the SMF for information.

[0093] The 5G system defined by the 3GPP standardization organization supports high-precision timing service over the air interface, that is, network devices can provide 5G high-precision time to terminal devices through air interface messages, so as to achieve high-precision clock synchronization between terminal devices and network devices. For example, 5G air interface time synchronization can be achieved by the gNB indicating the 5G time of a reference point to the UE. The gNB can perform 5G timing to the UE in a broadcast manner (for example, broadcasting system information) or a unicast manner (for example, sending RRC signaling).

[0094] The network device can broadcast 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, and the protocol defines the reference point of the time T as the rear boundary of the radio frame where the end position of the system information (SI) window containing the SIB9 is located, or the rear boundary of the radio frame immediately following the end position. For example, if the end position of the SI window where SIB9 is located is exactly the rear boundary of the radio frame with a system frame number (SFN) of x, then the 5G time indicated in SIB9 is the 5G time at the end position of the radio frame corresponding to SFN x. Another example, if the end position of the SI window where SIB9 is located falls in the middle of the radio frame with SFN x, then the 5G time indicated in SIB9 is the 5G time at the end position of the radio frame corresponding to SFN x.

[0095] The network device can send an RRC unicast message to the terminal device in a certain slot of SNF x-3. For example, the RRC unicast message can be a downlink information transfer (DLInformationTransfer) message. Among them, the RRC unicast message contains the 5G time T and the time reference point SFN x. After receiving the RRC unicast message, the terminal device can determine that the 5G time corresponding to the end position of the radio frame of SFN x is the time T, where the above SNF x is the SNF x within the SFN period closest to the moment when the RRC unicast message is received.

[0096] Based on the base station providing 5G clocks to the UE, 3GPP Release (R) 18 further defines the Timing Resilience System (TRS) feature. When the UE accesses the 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 state information (or clock quality information) to the interested UE. Among them, the 5G clock synchronization state information includes at least one of the following.

[0097] (1) Synchronization state. The synchronization state can include locked, holdover, or free run. Among them, locked indicates that the 5G clock is locked to the clock source; holdover indicates that the 5G clock is not locked to the clock source but is in a state of maintaining a certain clock accuracy; free run indicates that the 5G clock is not locked to the clock source and is not in a state of maintaining clock accuracy.

[0098] (2) Whether it can be traced back to Coordinated Universal Time (UTC).

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

[0100] (4) Clock frequency stability.

[0101] (5) Clock accuracy.

[0102] (6) Clock source.

[0103] For connected UEs, the base station can directly provide the above clock synchronization state information to the UE through an RRC unicast message. However, for Inactive or idle UEs, the base station needs to first notify the UE that the 5G clock synchronization state has changed. After the UE transitions to the connected state, the base station then provides the 5G clock synchronization state information to the UE through an RRC unicast message. Specifically, when the base station side senses a change in the clock synchronization state, it carries a new event ID in the broadcast SIB9 message; when an Inactive or idle UE reads the event ID contained in SIB9 and finds that the event ID has changed, or the UE finds that the base station where the UE is camped has changed, then the UE can initiate an RRC connection establishment process or an RRC connection recovery process; when the base station discovers that the UE has transitioned to the connected state and the UE is interested in the clock synchronization state information, it sends the 5G clock synchronization state information to the UE.

[0104] The base station transfers the UE to the Inactive state by sending an RRC release message to the connected UE. Among them, the RRC release message may include a suspendConfig cell, and in the suspendConfig cell, the base station configures the following information.

[0105] (1) Information of the RNA, which may include cell identifiers under one or more base stations, or one or more RAN area identifiers.

[0106] (2) Inactive radio network temporary identifier (I-RNTI), which may be an identifier for an Inactive state user assigned by the base station to the UE.

[0107] (3) Periodic RNA update - TimerValue, which can be used to control the timing length of the timer t380 that initiates the periodic RNA update (RNA-U) process. When the UE enters the Inactive state, the timer t380 is started.

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

[0109] (1) The timer t380 times out, and the UE initiates a periodic RNA-U process.

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

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

[0112] When an Inactive UE initiates the RNA-U process, it needs to perform the RRC connection restoration process. Specifically, the UE can send a RRC Resume Request message to the currently resident base station (or the new serving gNB), where the RRC Resume Request message carries the UE's I-RNTI. The currently resident base station identifies the last serving gNB (or the anchor base station, i.e., the base station that released the UE into the Inactive state) of the UE based on the UE's I-RNTI. When the currently resident base station and the most recent serving base station are not the same base station, the currently resident base station can initiate a RETRIEVE UECONTEXT process to the last serving gNB of the UE to request the UE context. The last serving gNB of the UE can decide whether to perform an anchor relocation, that is, whether to migrate the context of this UE to the new serving base station. If the last serving gNB of the UE does not migrate the UE context, it can send an RRC Release message to the UE through the new serving base station to transfer the UE to the Inactive state or the Idle state; if the last serving gNB of the UE migrates the UE context to the new serving base station, after the new serving base station obtains the UE context, it can decide to transfer the UE to the connected state, or continue to stay in the Inactive state, or transfer to the Idle state.

[0113] If the RNA region configured for the Inactive UE contains cells of multiple base stations, then only the anchor base station of the UE can sense whether the UE is interested in 5G clock information and / or 5G clock status information, and other base stations within the RNA do not sense this information. For example, when gNB1 transfers the 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, when the Inactive UE is moving, if it moves out of the coverage area of gNB1 and into the coverage area of another base station within the RNA, such as gNB2, gNB2 does not know that there is an Inactive UE interested in clock information and / or clock status information under its coverage area and may not broadcast SIB9. At this time, the UE may not be able to receive 5G clock information or sense whether the 5G clock quality has changed, so applications that require clock-related information may not work properly because they cannot obtain clock-related information in a timely manner.

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

[0115] Figure 3 This is a schematic flowchart of a communication method 300 provided by an embodiment of the present application. The method 300 can ensure the continuity of clock-related services. The following will introduce the method 300 in combination with Figure 3 introduce the method 300.

[0116] S310, the first network device sends the first information to the terminal device interested in the clock-related information.

[0117] Among them, the first information can indicate the RNA, and the RNA can include the coverage range of the first network device and the coverage range of the second network device.

[0118] The first network device can also be referred to as an anchor network device, the last serving base station, or have other names. Those skilled in the art can understand that the first network device starts as the anchor base station of the terminal device interested in the clock-related information. In some optional embodiments, before S310, the method 300 further includes: the first network device receives the context of the terminal device from the third network device. It can be understood that the third network device is the previous (or the last) anchor base station of the terminal device, and the first network device is the new anchor base station of the terminal device.

[0119] The clock-related information can include clock information and / or clock status information. The clock information can be 5G clock information or 6G clock information, and the present application is not limited. The clock status information can be 5G clock status information or 6G clock status information, and the present application is not limited. For example, the clock information can be the time T in the above SIB9 message for clock synchronization between the terminal device and the second network device. For another example, the clock status information can be the event identifier in the above 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 the clock-related information can be understood as broadcasting the clock-related information.

[0120] The terminal device in the above S310 is the terminal device interested in the clock-related information. In some optional embodiments, the method 300 further includes: the first network device obtains the terminal device interested in the clock-related information. The above terminal device can be one or more.

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

[0122] As another example, a neighboring network device of the first network device may send indication information to the first network device, and 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 process, a source base station may send the above indication information to a target base station.

[0123] As yet another example, the terminal device may send indication information to the first network device, and the indication information may indicate that the terminal device is interested in clock information and / or clock status information. For example, when the terminal device accesses the first network device, it may send the above indication information to the first network device through an RRC message.

[0124] The terminal device being interested in clock-related information may include that the terminal device needs to obtain or receive clock-related information.

[0125] The first information may be carried in an RRCRelease message, but this application does not limit the message in which the first information is carried. The first information may also be carried in other messages.

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

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

[0128] The RNA may include the coverage area of the first network device and the coverage area of the second network device. It should be noted that the coverage area of the first network device above may be the entire coverage area of the first network device, or a partial coverage area within the entire coverage area of the first network device. For example, if the first network device can cover three cells, the coverage area of the first network device above may be one cell, two cells, or three cells among the three cells. Similarly, the coverage area of the second network device above may be the entire coverage area of the second network device, or a partial coverage area within the entire coverage area of the first network device. For example, if the second network device can cover four RAN areas, the coverage area of the second network device above may be one RAN area, two RAN areas, three RAN areas, or four RAN areas among the four RAN areas. For ease of description, if not specifically indicated, the coverage area of the first network device mentioned below refers to the area covered by the first network device in the RNA, and the coverage area of the second network device refers to the area covered by the second network device in the RNA.

[0129] Among them, the coverage area of the first network device and the coverage area of the second network device in the RNA may be different. The coverage area of the second network device may not be within the coverage area of the first network device, or rather, the coverage area of the second network device is not within the scope maintained by the first network device. For example, if the RNA includes Cell 1 and Cell 2, the first network device can cover Cell 1 but not Cell 2, and the second network device can cover Cell 2. Or rather, the coverage area of the first network device includes Cell 1, the coverage area of the first network device does not include Cell 2, and the coverage area of the second network device includes Cell 2.

[0130] It should be noted that the second network device above may be one or more.

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

[0132] The first information may be referred to as an RRCRelease message or have other names. It can be understood that before the first information releases the terminal device, the terminal device may be in the connected state; after the first information releases the terminal device, the terminal device may be in the inactive state.

[0133] 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.

[0134] Among them, the second information may instruct the second network device to send the clock-related information within the coverage area of the second network device.

[0135] The second information can be sent to the second network device through the Xn interface. This application does not limit the message carried by the second information, and the second information can also 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 have other names.

[0136] It can be understood that the second information can indicate that there may be terminal devices interested in clock-related information 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 are terminal devices interested in clock-related information maintained by the first network device.

[0137] It should be noted that the second information indicating that the second network device sends the clock-related information within the coverage area of the second network device does not mean that the second network device will definitely send the clock-related information within the coverage area of the second network device according to the indication 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 send the clock-related information within the coverage area of the second network device. That is, the second network device can determine whether to send the clock-related information within the coverage area of the second network device based on its own implementation.

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

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

[0140] Those skilled in the art can understand that the above method 300 can be executed multiple times. For other non-active 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 received the second information. Therefore, when the first network device determines that the coverage range of the newly emerged second network device is not within the RNA of other non-active terminal devices that are already maintained by the first network device and are interested in clock-related information, it can avoid the first network device from repeatedly sending the second information to the network devices that have already received the second information.

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

[0142] Optionally, in another implementation scenario of the above embodiment, the second information includes the identifier of the first network device and / or the 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. That is, the RNA range of the non-active terminal devices maintained by the first network device that are interested in clock-related information includes the above coverage range of the second network device.

[0143] Exemplarily, the identifier of the coverage range of the second network device may include the identifier of at least one cell (cell identity) and / or at least one RAN area identifier (RAN area ID). Among them, 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 have other names. Among them, "affected" means that the range of the second network device is within the RNA of non-active terminal devices that are interested in clock-related information and are maintained by another first network device acting as an anchor base station.

[0144] Through the above embodiments, the second network device can determine the source of the second information according to the second information. Alternatively, the second network device can determine to send clock-related information within the coverage range of the second network device according to the second information, ensuring the continuity of clock-related services of terminal devices within the coverage range of the second network device.

[0145] In some alternative embodiments, the second information further includes a first flag, which indicates that the coverage area of the second network device is a newly added area, that is, the coverage area of the second network device is the RNA of the inactive terminal devices interested in clock-related information configured under the first network device.

[0146] S330, the second network device sends the clock-related information according to the second information.

[0147] The second network device may send the clock-related information by broadcasting an SIB9 message.

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

[0149] In another alternative embodiment, S330 includes: the second network device does not send the clock-related information within the coverage area of the second network device in the notification area. That is to say, even if the second network device receives the second information, it may not send the clock-related information. For example, based on some privacy policies configured by the operator and other factors, the second network device does not provide the clock-related information to the inactive terminal devices within the coverage area.

[0150] Through the above embodiments, when the RNA of the terminal devices interested in clock-related information maintained by the anchor base station includes the coverage areas of other neighbor base stations, the anchor base station may send the second information to the neighbor base stations. The neighbor base stations may send the clock-related information according to the second information, so that the terminal devices can also receive the clock-related information within the coverage areas of the neighbor base stations, avoiding the applications that require clock-related information from failing to work properly due to the inability to obtain the clock-related information in time, thus ensuring the continuity of clock-related services.

[0151] Optionally, in another implementation scenario of the above embodiment, the method 300 further includes: the first network device sends third information to the second network device, and the third information may be used to indicate that the second network device does not 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.

[0152] The third information may be sent to the second network device through the Xn interface. The present application does not limit the message carried by the third information, and the third information may also be carried in any message. The present application does not limit the name of the third information. For example, the third information may be called indication information, message 2, reduction information, stop synchronization information or have other names.

[0153] It can be understood that when the first network device is no longer the anchor base station of the terminal device interested in clock-related information, it can send third information to the second network device. The third information can indicate that there is no terminal device interested in clock-related information maintained by the first network device within the coverage of the second network device. Based on the second information, the second network device can learn that there is no terminal device interested in clock-related information maintained by the first network device within the coverage of the second network device in the RNA.

[0154] It should be noted that the third information indicating that the second network device does not send the clock-related information within the coverage of the second network device does not necessarily mean that the second network device will definitely not send the clock-related information within the coverage of the second network device according to the indication of 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 continue to send the clock-related information within the coverage of the second network device.

[0155] For example, in addition to the first network device sending second information to the second network device to indicate that the second network device sends clock-related information within cell 1 covered by the second network device, there is another network device sending second information to the second network device to indicate that the second network device sends clock-related information within cell 1, and the second network device does not receive the third information from the above-mentioned another network device. Then, there may be an inactive terminal device interested in clock-related information maintained by the above-mentioned another network device within cell 1, and the second network device can still send clock-related information within cell 1 so that the inactive terminal device interested in clock-related information maintained by the above-mentioned another network device can perform clock synchronization.

[0156] 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.

[0157] 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.

[0158] For another example, the first network device determines that the terminal device enters the connected state or the idle state. It can be understood that if the terminal device enters the connected state or the idle state, then the configured RNA of the terminal device will become invalid, which is equivalent to the effective RNA of the terminal device not including the coverage of the second network device, or equivalent to the first network device no longer being the anchor base station of the terminal device.

[0159] 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 can be understood 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 of the terminal device, and thus the effective RNA of the terminal device does not include the coverage area of the second network device.

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

[0161] Those skilled in the art can understand that if the coverage area of the second network device is within the RNA of other non-active terminal devices that are interested in clock-related information and are maintained by the first network device, it can be indicated that there are still other non-active terminal devices that are interested in clock-related information and are maintained by the first network device within the coverage area of the second network device. For example, there are non-active UEs UE1 and UE2 that are interested in clock-related information under the first network device. The RNA1 of UE1 includes cell 1, and the RNA2 of UE2 includes cell 1. When the first network device reconfigures RNA1 of UE1 not to include cell 1, or UE1 enters the connected state or the 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, then UE2 cannot perform clock synchronization.

[0162] In some alternative embodiments, method 300 includes: the first network device determines whether the RNA does not include the coverage area of the second network device, and the coverage area of the second network device is not within the RNA of other non-active terminal devices that are interested in clock-related information and are maintained by the first network device (or non-active 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 area of the second network device, and the coverage area of the second network device is not within the RNA of other non-active terminal devices that are interested in clock-related information and are maintained by the first network device), then the third information may be sent to the second network device. If not, the third information is not sent to the second network device.

[0163] Through the above embodiments, when the RNA of the terminal devices interested in clock-related information maintained by the anchor base station does not include the coverage ranges of other neighbor base stations, the anchor base station may send third information to the neighbor base stations. The third information may indicate that the second network device does not send the clock-related information within the coverage range of the second network device, thereby saving overhead.

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

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

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

[0167] The second network device may receive second information and third information from multiple networks. The second network device may determine whether to stop sending clock-related information within the coverage range of the second network device according to whether the network devices associated with the coverage range of the second network device have all sent the third information. Exemplarily, the second network device receives a piece of second information, which includes the identifier of the first network device and the identifier of cell 1. Then, the second network device may send the clock-related information within cell 1 according to this second information. After that, if the second network device receives another piece of second information, which includes the identifier of the first network device and the identifier of cell 1, and at this time the first network device has already sent the clock-related information within cell 1, there is no need to process it repeatedly. After that, if the second network device receives a piece of third information, which includes the identifier of the first network device and the identifier of cell 1. Since among the identifiers associated with cell 1, in addition to the identifier of the first network device, there is also the identifier of the second network device, the second network device may not stop sending the clock-related information within cell 1. In other words, the second network device may continue to send the clock-related information within cell 1. After that, if the second network device receives another piece of third information, which includes the identifier of the second network device and the identifier of cell 1. At this time, the second network device may stop sending the clock-related information within cell 1.

[0168] Through the above embodiments, the second network device can determine the source of the third information based on the third information, so as to determine 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.

[0169] In some alternative embodiments, the second information further includes a second flag, and the second flag indicates that the coverage area of the second network device is a reduced area, that is, the coverage area of the second network device is the RNA of the terminal device not configured under the first network device.

[0170] Optionally, in another implementation scenario of the above embodiment, the method 300 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.

[0171] For example, the second network device can determine to continue to send the clock-related information within the coverage area of the second network device in the RNA according to the third information, so as to ensure the continuity of the clock-related services of the terminal device having the RNA including the coverage area of the second network device.

[0172] For another example, the second network device can determine to stop sending the clock-related information within the coverage area of the second network device in the RNA according to the third information, thereby saving overhead.

[0173] Through the above embodiments, the second network device can flexibly determine whether to send the clock-related information within the coverage area of the second network device in the RNA according to the third information, which can ensure the continuity of the clock-related services of the terminal device having the RNA including the coverage area of the second network device, or can save overhead.

[0174] Optionally, in another implementation scenario of the above embodiment, the second network device receiving the second information from the first network device includes: the second network device receives N second information from N first network devices respectively, where N is a positive integer; wherein, the second network device receiving the third information from the first network device includes: the second network device receives M 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; wherein, the second network device determining whether to send the clock-related information within the coverage area of the second network device in the RNA according to the third information includes: 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.

[0175] The above solution can be understood as follows: when each network device that has sent the second information has sent the third information to the second network device, the second network device stops sending the clock-related information within the coverage area of the second network device in the RNA. In other words, if there is at least one network device that has sent the second information and has not sent the third information to the second network device, then the second network device continues to send the clock-related information within the coverage area of the second network device in the RNA.

[0176] Among them, the M first network devices belong to the N first network devices, which can be understood as the N first network devices include the M first network devices. In some optional embodiments, the N second information respectively includes the identifiers of the N first network devices and the identifiers of the coverage areas of the N second network devices, and the M third information respectively includes the identifiers of the M first network devices and the identifiers of the coverage areas of the M second 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 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 area of the second network device in the RNA according to the third information.

[0177] That is to say, the process by which the second network device determines whether to send the clock-related information within the coverage area of the second network device in the RNA can be achieved by carrying the identifier of the sending end and the identifier of the influence range in the second information, and by carrying the identifier of the sending end and the identifier of the influence range in the third information.

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

[0179] Optionally, in another implementation scenario of the above embodiment, 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.

[0180] M being less than N can be understood as that there is at least one network device that has sent the second information and has not sent the third information to the second network device.

[0181] Through the above embodiments, in the case where 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 area of the second network device in the RNA, so as to ensure the continuity of the clock-related services of the terminal device having an RNA including the coverage area of the second network device.

[0182] Optionally, in another implementation scenario of the above embodiments, 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: in the case where the RNA of the terminal device interested in the clock-related information maintained by the second network device includes the coverage area of the second network device, the second network device sends the clock-related information within the coverage area of the second network device in the RNA.

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

[0184] Optionally, in another implementation scenario of the above embodiments, the second network device receives the second information from the first network device, including: the second network device receives at least N second information from N first network devices respectively, 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 at least M 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; wherein, 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: in the case where M is equal to N, and after the second network device receives the target third information among at least M third information, and in the case where the second network device receives the target second information among at least N second information, the second network device sends the clock-related information within the coverage area of the second network device in the RNA according to the third information, where the target third information and the target second information come from the same first network device.

[0185] The above solution can be understood as follows: If a network device sequentially sends a second piece of information, a third piece of information, and then the second piece of information to a second network device, then the second network device can continue to send the clock-related information within the coverage range of the second network device in the RNA. On the other hand, if each network device that has sent the second piece of information has sent the third piece of information and has not sent the second piece of information again after sending the third piece of information, the second network device can stop sending the clock-related information within the coverage range of the second network device in the RNA.

[0186] Optionally, in another implementation scenario of the above embodiment, when the second network device receives the second piece of information from the first network device, the first network device is in the first state; when the second network device receives the third piece of 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 range of the second network device in the RNA according to the third piece of information, including: when all the first network devices are in the second state, the second network device does not send the clock-related information within the coverage range 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 range of the second network device in the RNA.

[0187] Among them, the first state can be understood as that the RNA range configured for the non-active terminal devices interested in the 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 that the RNA range configured for the non-active terminal devices interested in the clock-related information maintained by the first network device does not include the above-mentioned coverage range of the second network device.

[0188] Optionally, in another implementation scenario of the above embodiment, the first network device sends the third piece of information to the second network device, including: after the terminal device enters the connected state or the 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 piece of information to the second network device.

[0189] The first network device can transfer the terminal device to the connected state or the idle state. When the terminal device is transferred to the connected state, if the terminal device wants to leave the coverage area of the first network device and enter the coverage area of another network device, a handover process will be performed, and the network device of the new serving cell will provide clock-related information, so that the terminal device will not enter the coverage area of the second network device without the knowledge of the second network device. When the terminal device is transferred to the idle state, the terminal device can move within the coverage areas of various network devices, and the probability of appearing in the coverage area of the second network device is relatively small. Therefore, after the terminal device enters the connected state or the idle state, the first network device sending the third information to the second network device can save the overhead of the second network device.

[0190] The first network device can delete the context of the terminal device when it determines that an abnormal situation has occurred (for example, the terminal device has not initiated the periodic RNA-U process for a long time). In this case, even if the second network device sends clock-related information within the coverage area 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.

[0191] The first network device can migrate the context of the terminal device to other network devices. It can be understood that after that, the first network device is no longer the anchor base station of the terminal device, and the network device that receives the context of the terminal device becomes the new anchor base station. The new anchor base station will determine a new RNA, and the new RNA may not include the coverage area of the second network device. Or, the new anchor base station can execute the method provided in this application. When the new RNA also includes the coverage area of the second network device, it will send the second information to 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 area of the second network device, or whether the second network device sends clock-related information can be indicated by another network device.

[0192] The first network device learns that the terminal device is within the coverage area of the first network device, indicating that the terminal device is not within the coverage area 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 area.

[0193] Optionally, in another implementation scenario of the above embodiments, the method 300 further includes: the first network device determines that the terminal device is within the coverage of the first network device according to at least one of the following: the first network device and the terminal device perform small data transmission (SDT); or, the first network device receives the location information of the terminal device, and the location information indicates that the terminal device is within the coverage of the first network device.

[0194] In the case where the first network device and the terminal device perform the SDT process, the first network device may determine that the terminal device is within the coverage of the first network device.

[0195] Further, if the first network device determines that all terminal devices interested in clock-related information in the RNA including the coverage of the second network device have initiated the SDT process, then the first network device may determine that the above terminal devices do not reside within the coverage of the second network device. Therefore, the first network device may indicate to the second network device not to send clock-related information outside the coverage of the second network device through the third information.

[0196] This application does not limit the message carrying the location information, and the location information may be carried in any message. This application does not limit the name of the location information, and the location information may also be referred to as indication information or have other names.

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

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

[0199] Figure 4 It is a schematic flowchart of another communication method 400 provided by the embodiments of this application. In method 400, when the base station maintains the addition or reduction of interested Inactive UEs, the base station may send an indication message to the neighbor base station, indicating that the RNA with interested Inactive UEs includes the neighbor base station (corresponding to the second information), or the RNA without interested Inactive UEs includes the neighbor base station (corresponding to the third information). Method 400 may be combined with method 300, and the following combination Figure 4Introduce method 400.

[0200] S410, gNB1 obtains information about UEs interested in clock-related information.

[0201] gNB1 can obtain that connected UEs are interested in clock-related information. Among them, the clock-related information includes clock information and / or clock synchronization status information. Exemplarily, gNB1 can obtain from a core network element (or referred to as a core network node), a neighboring gNB, or a UE whether a connected UE is interested in clock-related information. For specific details, refer to the relevant description in S310, which will not be elaborated here.

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

[0203] S420, gNB1 sends a first message to the UE.

[0204] The first message can indicate the RNA. The first message can indicate that the UE enters the Inactive state. For other descriptions of the first message, refer to the previous text, which will not be elaborated here. Below, taking the RNA including the coverage areas of gNB1, gNB2, and gNB3 as an example, a description will be given.

[0205] S430, gNB1 sends a second message to gNB2 and gNB3.

[0206] Below, taking gNB2 as an example for description, the description of gNB3 is similar to that of gNB2. The description of gNB3 can refer to the description of gNB2 and will not be elaborated further.

[0207] When gNB1 starts to be an anchor base station for an Inactive UE interested in clock-related information, gNB1 can determine whether the RNA configured for the Inactive UE contains at least one cell of gNB2, and this cell is not within the RNA of the existing Inactive UEs interested in clock-related information maintained by gNB1. If so (that is, the RNA configured for the Inactive UE contains at least one cell of gNB2, and this cell is not within the RNA of the existing Inactive UEs interested in clock-related information maintained by gNB1), then gNB1 sends a second message to the above-mentioned gNB2, used to indicate that the RNA of at least one Inactive UE interested in clock-related information with gNB1 as the anchor base station includes the (partial) coverage area of gNB2.

[0208] The second information may include the identifier of gNB1 and the affected range of gNB2 (or referred to as the RNA range). Among them, the affected range of gNB2 includes the information of the cells under gNB2 included in the RNA range of the 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 the identifier of at least one RAN area.

[0209] Optionally, the second information may further include a first flag and / or a first identifier. Among them, the first flag may be referred to as flag field 1, indicating that the affected range of gNB2 is a newly added range, that is, indicating that the affected range of gNB2 is configured within the RNA of the Inactive UEs interested under gNB1. Among them, the first identifier may indicate the clock information that the UE is interested in. For other descriptions of the second information and the information included in the second information, reference may be made to the foregoing, and details are not described here.

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

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

[0212] (2) gNB1 obtains the context of an Inactive UE from another gNB, and gNB1 sends an RRC Release message to this UE to keep it in the Inactive state, and this Inactive UE is interested in clock-related information.

[0213] S440, gNB1 sends the third information to gNB2 and gNB3.

[0214] The following takes gNB2 as an example for description. The description of gNB3 is similar to that of gNB2. For the description of gNB3, reference may be made to the description of gNB2, and details are not described again.

[0215] When gNB1 no longer serves as the anchor base station for an Inactive UE interested in clock-related information, gNB1 can determine whether the RNA configured for the Inactive UE does not include at least one cell of gNB2 that is not within the RNA of the existing Inactive UEs interested in clock-related information maintained by gNB1. If so (i.e., the RNA configured for the Inactive UE does not include at least one cell of gNB2 that is not within the RNA of the existing Inactive UEs interested in clock-related information maintained by gNB1), then gNB1 sends third information to the above-mentioned gNB2 to indicate that the (partial) coverage area of gNB2 no longer belongs to the RNA of the Inactive UEs interested in clock-related information maintained by gNB1.

[0216] The third information may include the identifier of gNB1 and the affected range of gNB2 (or referred to as the RNA range). Among them, the affected range of gNB2 includes cell information of gNB2 that no longer belongs to the RNA of the Inactive UEs interested in clock-related information maintained by gNB1. For example, it may be the identifier of at least one cell, or the identifier of at least one RAN area. Optionally, the third information may further include a second flag. Among them, the second flag may become flag field 2, indicating that the affected range of gNB2 is a reduced range, that is, the indicated affected range of gNB2 is no longer configured within the RNA of the Inactive UEs interested in clock-related information under gNB1. Other descriptions of the third information and the information included in the third information can be found in the previous text and will not be elaborated here.

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

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

[0219] (2) gNB1 transfers the Inactive UE to the connected state or the idle state.

[0220] (3) gNB1 deletes the UE context, for example, in case of some abnormal situations (such as the UE does not initiate a periodic RNA-U process for a long time, etc.).

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

[0222] It should be noted that S450 is an optional step in method 400. That is to say, method 400 may not include S450. The following describes by taking gNB2 as an example. The description of gNB3 is similar to that of gNB2. For the description of gNB3, reference can be made to the description of gNB2 and will not be elaborated here.

[0223] In some optional embodiments, gNB2 maintains, at the granularity of cells, whether a cell belongs to the RNA of an Inactive UE interested in clock-related information. For example, gNB2 may determine whether a cell under gNB2 belongs to the RNA of an Inactive UE interested in clock-related information based on the received second information and third information from neighboring gNBs, as well as the RNA of Inactive UEs interested in clock-related information maintained by gNB2 itself.

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

[0225] Figure 5 It is a schematic flowchart of another communication method 500 provided by an embodiment of the present application. Method 500 is an example of method 300 and method 400 and does not limit the present application. Method 500 includes cases (1) to (5), and the following combines Figure 5 to introduce method 500.

[0226] Before case (1) occurs, it is assumed that none of gNB1 to gNB3 maintains an Inactive UE interested in clock-related information. The connected-state UEs UE1, UE2, and UE3 served by gNB1 are interested in clock-related information.

[0227] Case (1): gNB1 releases UE1 to the Inactive state. The configured RNA for UE1 includes the coverage area of gNB1 and does not include the coverage areas of gNB2 and gNB3. gNB1 does not need to send the second information or the third information to neighboring gNBs.

[0228] In case (1), gNB1 may broadcast an SIB9 message to provide clock-related information. gNB2 and gNB3 do not maintain an Inactive UE interested in clock-related information, and there is no RNA of an Inactive UE interested in clock-related information maintained by other gNBs that includes its own (gNB2 or gNB3) coverage area. Therefore, gNB2 and gNB3 do not need to broadcast the SIB9 message.

[0229] Scenario (2): gNB1 releases UE2 to the Inactive state. The RNA configured for UE1 includes the coverage areas of gNB1 and gNB2, and does not include the coverage area of gNB3. gNB1 can determine that the coverage area of gNB2 does not belong to the RNA of the existing Inactive UEs interested in clock-related information. Thus, gNB1 sends a second message to gNB2.

[0230] In scenario (2), gNB1 and gNB2 broadcast the SIB9 message to provide clock-related information. gNB3 does not need to broadcast the SIB9.

[0231] Scenario (3): gNB1 releases UE3 to 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 RNA of the existing Inactive UEs interested in clock-related information. Thus, gNB1 does not send a second message to gNB2. gNB1 can determine that the coverage area of gNB3 does not belong to the RNA of the existing Inactive UEs interested in clock-related information. Thus, gNB1 sends a second message to gNB3.

[0232] In scenario (3), gNB, gNB2, and gNB3 broadcast the SIB9 message to provide clock-related information.

[0233] Scenario (4): UE2 transitions to the connected state ( Figure 5 shown in shadow), and gNB1 determines that the RNA of the existing Inactive UEs interested in clock-related information (i.e., UE1 and UE3) includes the original RNA range of UE2. Thus, gNB1 does not need to send a third message to gNB2 or gNB3. Alternatively, gNB1 determines that the coverage areas of gNB2 and gNB3 are within the RNA of other existing terminal devices (i.e., UE1 and UE3) maintained by gNB1, for example, within the RNA of UE3. Thus, gNB1 does not need to send a third message to gNB2 or gNB3.

[0234] In scenario (4), gNB, gNB2, and gNB3 broadcast the SIB9 message to provide clock-related information.

[0235] Scenario (5): UE3 transitions to the connected state, and gNB1 determines that the coverage areas of gNB2 and gNB3 no longer belong to the RNA of the Inactive UEs interested in clock-related information maintained by gNB1. gNB1 sends a third message to gNB2 and gNB3.

[0236] In case (5), gNB1 broadcasts the SIB9 message to provide clock-related information. gNB2 and gNB3 do not maintain Inactive UEs interested in clock-related information, and the RNA of Inactive UEs interested in clock-related information maintained by other gNBs does not cover their own coverage areas. Therefore, gNB2 and gNB3 do not need to broadcast the SIB9 message.

[0237] This application also provides another communication method. The method includes: when a network device starts broadcasting clock-related information, the network device sends first indication information to a neighboring network device, and the first indication information can be used to indicate that the network device starts 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, and the second indication information can be used to indicate that the network device stops broadcasting clock-related information. In this way, when the network device determines that a neighboring network device is affected, that is, when the RNA of Inactive terminal devices maintained by the network device and interested in clock-related information includes the coverage area of the neighboring network device, the network device can determine, based on the first indication information, that the neighboring network device has started broadcasting clock-related information, and thus does not need to send the second information to the neighboring network device. For example, when gNB1 sends the second information to an affected gNB, it excludes gNBs that are known to be broadcasting clock-related information.

[0238] Figure 6 It is a schematic flowchart of yet another communication method 600 provided by an embodiment of this application. In method 600, if the base station determines that all Inactive UEs interested in clock-related information within the coverage area of a neighboring base station included in the RNA configured by the base station have initiated the SDT process, the base station can send a third message to the neighboring base station. Method 600 can be combined with method 300, 400, or 500. The following combines Figure 6 to introduce method 600.

[0239] Before method 600 is executed, assume that the RNAs of Inactive UE1 and Inactive UE2 maintained by gNB1 and interested in clock-related information both cover the coverage area of gNB2, and there is no other RNA of Inactive UE interested in clock-related information under gNB1 that covers the coverage area of gNB2. gNB1 has sent the second information to gNB2, instructing gNB2 to send clock-related information within its coverage area.

[0240] S610, Inactive UE1 and Inactive UE2 initiate the SDT process to gNB1.

[0241] S620, gNB1 sends the third information to gNB2.

[0242] 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 process or are in the SDT process. Thus, gNB1 may determine that all Inactive UEs interested in clock-related information whose RNA includes the coverage of gNB2 are not located within the coverage of gNB2. Therefore, gNB1 may send third information to gNB2. The third information may indicate that none of the Inactive UEs interested in clock-related information maintained by gNB1 are located within the coverage of gNB2. Thus, gNB2 may not send clock-related information within its coverage.

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

[0244] S640, gNB1 sends second information to gNB2.

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

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

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

[0248] S710, UE initiates RRC setup to gNB1.

[0249] After the UE initiates the RRC setup, the UE is a connected UE.

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

[0251] Among them, 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 to say, method 700 may not include S720.

[0252] S730, the 5GC sends the TSA information to gNB1.

[0253] The above S730 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 where the UE needs to obtain clock-related information. The TSA may include the coverage range of at least one cell under at least one base station.

[0254] In some alternative 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.

[0255] In some alternative embodiments, only when the core network element learns that the UE has a requirement to configure TSA, will it configure the TSA information for the base station side.

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

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

[0258] S750, the UE may initiate a TSA update process to gNB2.

[0259] For example, when the UE moves out of the TSA range configured by gNB1, the UE may initiate a TSA update process to the new serving base station (i.e., gNB2). Or, when the UE initiates an RRC resume process in the resident cell to notify the new serving base station that the UE has moved out of the TSA range. The RRCResumeRequest message may include a cause value, and the cause value may indicate that the UE initiates a TSA update process.

[0260] S760, gNB2 notifies gNB1 that the UE initiates a TSA update process.

[0261] In other words, the new serving base station may send indication information to the serving base station to which the UE was last connected, and the indication information indicates that the UE has initiated a TSA update process. Further, in some alternative embodiments, the serving base station to which the UE was last connected (i.e., gNB1) may migrate the context of the UE to the new serving base station (i.e., gNB2).

[0262] It should be noted that the foregoing method can be combined with Method 700. For example, the RNA in the foregoing method can be replaced with TSA.

[0263] Through the above embodiments, 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.

[0264] The device embodiments corresponding to the method embodiments of the present application are introduced below. Only a brief introduction to the device is given below. For the specific implementation steps and details of the solution, reference can be made to the foregoing method embodiments.

[0265] To implement the various functions in the method provided by the present application, the communication device may include a hardware structure and / or a software module, and implement the above various functions in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module. Whether a certain function among the above various functions is executed in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module depends on the specific application and design constraints of the technical solution.

[0266] Figure 8 It 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, and the processor 810 and the communication interface 820 can be connected to each other through a bus 830. The communication device 800 can be a first network device or a second network device.

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

[0268] The processor 810 may be one or more central processing units (CPUs). When the processor 810 is a single CPU, it may be a single-core CPU or a multi-core CPU. Among them, the processor 810 may be a signal processor, a chip, or other integrated circuits that can implement the method of this application, or a partial circuit for processing functions in the foregoing processor, chip, or integrated circuit. In addition, the communication interface 820 may also be an input / output interface. The input / output interface is used for input or output of signals or data and may also be an input / output circuit.

[0269] Exemplarily, when the communication device 800 is a first network device, the processor 810 is used to perform the following operations: sending a first piece of information to a terminal device interested in clock-related information; sending a second piece of information to the second network device.

[0270] The above content is only for exemplary description. The communication device 800 is responsible for executing the methods or steps related to the first network device in the foregoing method embodiments.

[0271] Exemplarily, when the communication device 800 is a second network device, the processor 810 is used to perform the following operations: receiving the second piece of information from the first network device; sending the clock-related information according to the second piece of information.

[0272] The above content is only for exemplary description. The communication device 800 is responsible for executing the methods or steps related to the second network device in the foregoing method embodiments.

[0273] It can be understood that the communication interface 820 may also be referred to as a transceiver. The transceiver may include a transmitter and a receiver. The transmitter is used to perform sending operations, and the receiver is used to perform receiving operations. For example, the processor 810 is used to control the transceiver to receive and / or send signals.

[0274] It should be noted that the communication device 800 may include a transmitter but not a receiver. Or, the communication device 800 may include a receiver but not a transmitter. Specifically, it depends on whether the above-mentioned scheme executed by the communication device 800 includes sending actions and receiving actions.

[0275] The above description is only for exemplary description. For specific content, reference may be made to the content shown in the foregoing method embodiments. Figure 8 The implementation of each operation in Figures 3 to 7 may also correspond to the corresponding description in the method embodiment shown.

[0276] For example, the communication device 800 may be used to execute Figures 3 to 7 the scheme shown.

[0277] When the communication device 800 is the first network device, the communication interface 820 can be used to send the first information to the terminal device interested in the clock-related information, and send the second information to the second network device.

[0278] When the communication device 800 is the second network device, the communication interface 820 can be used to receive the second information from the first network device, and send the clock-related information according to the second information.

[0279] For other implementation manners, reference can be specifically made to the detailed introduction of the foregoing Figures 3 to 7 illustrated embodiments, which will not be elaborated here. It should be understood that the specific processes for each component to execute the corresponding processes have been described in detail in the foregoing method embodiments. For the sake of brevity, they will not be elaborated here.

[0280] Figure 9 is a schematic block diagram of another communication device 900 according to an embodiment of the present application. The communication device 900 can be the first network device or the second network device, or can be a chip or module in the first network device or the second network device, and is used to implement Figures 3 to 7 the method involved in the illustrated embodiment. For details, please refer to the relevant introduction in the foregoing method embodiments.

[0281] The communication device 900 includes a transceiver unit 910. The transceiver unit 910 will be introduced exemplarily below.

[0282] The transceiver unit 910 can include a sending unit and a receiving unit. The sending unit is used to perform the sending action of the communication device 900, and the receiving unit is used to perform the receiving action of the communication device 900. For the convenience of description, in the embodiments of the present application, the sending unit and the receiving unit are combined into one transceiver unit. A unified description is made here and will not be elaborated later. The transceiver unit 910 can implement the corresponding communication function. The transceiver unit 910 can also be referred to as a communication interface or a communication module.

[0283] It should be noted that the communication device 900 can include a sending unit but not a receiving unit. Or, the communication device 900 can include a receiving unit but not a sending unit. Specifically, it depends on whether the above-mentioned scheme executed by the communication device 900 includes a sending action and a receiving action.

[0284] Exemplarily, the transceiver unit 910 is used to send the first information, etc. to the terminal device interested in the clock-related information.

[0285] Optionally, the communication device 900 can further include a processing unit 920, which is used to execute the content related to the processing, coordination, etc. steps involved in the first network device.

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

[0287] Optionally, the communication device 900 may further include a processing unit 920, which is configured to execute the content related to the processing, coordination, etc. steps of the second network device.

[0288] The above content is only for exemplary description. The communication device 900 will be responsible for executing the methods or steps related to the first network device or the second network device in the foregoing method embodiments.

[0289] Optionally, the communication device 900 further includes a storage unit 930, which is used to store programs or codes for executing the foregoing methods. Or rather, the storage unit 930 can be used to store instructions and / or data, and the processing unit 920 can read the instructions and / or data in the storage unit 930 so that the communication device 900 can implement the foregoing method embodiments. For example, the communication device 900 can be used to execute Figures 3 to 7 the shown solution.

[0290] When the communication device 900 is the first network device, the processing unit 920 can be used to send first information to a terminal device interested in clock-related information; send second information to the second network device.

[0291] When the communication device 900 is the second network device, the processing unit 920 can be used to receive second information from the first network device; send the clock-related information according to the second information.

[0292] For other implementation manners, specific references can be made to the detailed introduction of the foregoing Figures 3 to 7 shown embodiments, which will not be elaborated here. It should be understood that the specific processes of each component executing the above corresponding processes have been described in detail in the foregoing method embodiments. For the sake of brevity, they will not be repeated here.

[0293] Figure 8 and Figure 9 The shown device embodiments are used to implement Figures 3 to 7 the content described above. Figure 8 and Figure 9 The specific execution steps and methods of the shown device can be referred to the content described in the foregoing method embodiments.

[0294] This application also provides a communication device, including a processor and a memory. Among them, the memory is used to store instructions, and the processor is used to call and run the instructions stored in the memory, so that the communication device executes the methods in the above embodiments.

[0295] The present application also provides a chip, including a processor configured to call and run instructions stored in a memory, such that a communication device installed with the chip executes the methods in the above respective embodiments.

[0296] The present application also provides another chip, including: an input interface, an output interface, and a processor, where the input interface, the output interface, and the processor are connected through 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 execute the methods in the above respective embodiments. Optionally, the chip further includes a memory configured to store a computer program or code.

[0297] The present application also provides a processor configured to be coupled with a memory and execute the methods and functions related to a communication device in any one of the above respective embodiments.

[0298] In another embodiment of the present application, there is provided a computer program product including a computer program or instructions. When the computer program or instructions run on a computer, the methods in the foregoing embodiments are implemented.

[0299] The present application also provides a computer program. When the computer program runs in a computer, the methods in the above respective embodiments are implemented.

[0300] In another embodiment of the present application, there is provided a computer-readable storage medium storing a computer program, and when the computer program is executed by a computer, the methods in the above respective embodiments are implemented.

[0301] The present application also provides a communication system, including a first network device and a second network device. Among them, the first network device is configured to perform the actions performed by the first network device in the foregoing method, and the second network device is configured to perform the actions performed by the second network device in the foregoing method.

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

[0303] Those skilled in the art can 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 foregoing method embodiments and will not be elaborated herein.

[0304] In 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 illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections between each other can be through some interfaces. The indirect couplings or communication connections of devices or units can be in electrical, mechanical, or other forms.

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

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

[0307] If the functions are implemented in the form of software function 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 this application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of this application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0308] The above is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application, and all should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claimed rights.

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 area of the first network device and the coverage area 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 area 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 area of the second network device, where the identifier of the first network device is used to indicate that the coverage area 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 area of the second network device.

5. The method according to claim 4, characterized in that, The third information includes an identifier of the first network device and / or an identifier of the coverage area 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 area 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, characterized in that, Also including: The first network device determines that the terminal device is within the coverage area of the first network device based on 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 area 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 within the coverage area 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 area of the second network device in the RNA, and the identifier of the first network device is used to indicate that the coverage area 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 area 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, Further included is: 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, Included is: A processor and a memory. A computer program or instruction is stored in the memory. The processor is used to, by executing 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 a 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, Included is 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, Included are 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