Wireless communication method, terminal device and network device

Abstract

Provided are a wireless communication method, a terminal device, and a network device. The method comprises: a first terminal device receives first information sent by a second terminal device, the first information comprising one or more of the following: a first paging message used for paging the first terminal device and the second terminal device; a second paging message used for paging the first terminal device; and downlink information to be transmitted to the first terminal device, wherein the first terminal device and the second terminal device are multi-access devices. The present application facilitates improvement of the success rate of paging a terminal device, thereby improving the efficiency of transmitting downlink data / downlink signaling.

Description

Wireless communication method, terminal device and network device Technical Field

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

[0002] In the traditional solution, if the terminal device is in the connection management (CM) idle state or the CM inactive state, there is no connection between the terminal device and the network device. At this time, if the network device has downlink data (for example, mobile terminal (MT) data) or downlink signaling to be transmitted, it is necessary to re-paging the terminal device. If the terminal device cannot be paged, the downlink data or downlink signaling transmission fails. However, for multi-access scenarios, there are multiple associated terminal devices serving the user at the same time. If the traditional paging method is used, only when a terminal device cannot be paged, the multi-access device corresponding to the terminal device is considered unreachable, and downlink data or downlink signaling is no longer sent to the multi-access device, which may result in low efficiency in transmitting downlink data / downlink signaling and reduce user experience.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method, terminal device, and network device. The following introduces various aspects of the present application.

[0005] In a first aspect, a method for wireless communication is provided, including: a first terminal device receives first information sent by a second terminal device, the first information including one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; downlink information to be transmitted to the first terminal device; wherein the first terminal device and the second terminal device are multi-access devices.

[0006] In a second aspect, a method for wireless communication is provided, including: a second terminal device receives first information sent by a second network device, the second terminal device and the first terminal device belong to the same multi-access device, wherein the first information includes one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; and downlink information to be transmitted to the first terminal device.

[0007] In a third aspect, a method for wireless communication is provided, including: a second network device sends first information to a second terminal device, where the second terminal device and the first terminal device belong to the same multi-access device, wherein the first information includes one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; and downlink information to be transmitted to the first terminal device.

[0008] In a fourth aspect, a method for wireless communication is provided, including: a first network device sends second information to a second network device, the second information being used to trigger the second network device to send first information, wherein the first information includes one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; downlink information to be transmitted to the first terminal device; wherein the first terminal device and the second terminal device are multi-access devices.

[0009] In a fifth aspect, a method for wireless communication is provided, including: a first terminal device receives first information sent by a second terminal device, the first information including one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; downlink information to be transmitted to the first terminal device; wherein the first terminal device and the second terminal device are multi-access devices.

[0010] In a sixth aspect, a method for wireless communication is provided, comprising: a first core network network element determines whether the second terminal device and the first terminal device belong to the same multi-access device based on a signing message of the second terminal device.

[0011] In the seventh aspect, a wireless communication method is provided, including: a second core network network element sends a signing message of a second terminal device to a first core network network element, and the signing information of the second terminal device is used to determine whether the second terminal device and the first terminal device belong to the same multi-access device.

[0012] In the eighth aspect, a method for wireless communication is provided, including: a first terminal device receives second information or third information sent by a first core network network element, wherein the second information is used to indicate a refusal to paging the second terminal device through the first terminal device, and the third information is used to indicate that paging the second terminal device through the first terminal device will be allowed, which is updated to a refusal to paging the second terminal device through the first terminal device.

[0013] In the ninth aspect, a method for wireless communication is provided, characterized in that it includes: a first core network network element sends a fifth information to a second terminal device, and the fifth information is used to request the second terminal device to confirm whether to allow or refuse to paging the first terminal device through the second terminal device, wherein the first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

[0014] In the tenth aspect, a method for wireless communication is provided, including: a second terminal device receives fifth information sent by a first core network network element, and the fifth information is used to request the second terminal device to confirm whether to allow or refuse to paging the first terminal device through the second terminal device, wherein the first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

[0015] In an eleventh aspect, a wireless communication method is provided, comprising: a first terminal device receiving sixth information sent by a first core network network element, the sixth information being used to instruct a second terminal device to allow or refuse paging the first terminal device through the second terminal device;

[0016] The first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

[0017] In the twelfth aspect, a method for wireless communication is provided, including: a first device sends a first identifier to a second device, where the first identifier is used to identify a multi-access device, and the multi-access device includes a first terminal device and a second terminal device.

[0018] In the thirteenth aspect, a method for wireless communication is provided, including: a second device receives a first identifier sent by a first device, the first identifier is used to identify a multi-access device, and the multi-access device includes a first terminal device and a second terminal device.

[0019] In the fourteenth aspect, a method for wireless communication is provided, including: a first device sends first capability information to a second device, the first capability information is used to indicate whether the second terminal device supports paging through the first terminal device, and the first terminal device and the second terminal device are multi-access devices.

[0020] In the fifteenth aspect, a method for wireless communication is provided, including: a second device receives first capability information sent by a first device, the first capability information is used to indicate whether the second terminal device supports paging through the first terminal device, and the first terminal device and the second terminal device are multi-access devices.

[0021] In the sixteenth aspect, a terminal device is provided, which is a first terminal device, including: a receiving unit for receiving first information sent by a second terminal device, the first information including one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; downlink information to be transmitted to the first terminal device; wherein the first terminal device and the second terminal device are multi-access devices.

[0022] In the seventeenth aspect, a terminal device is provided, which is a second terminal device, including: a receiving unit, used to receive first information sent by a second network device, the second terminal device and the first terminal device belong to the same multi-access device, wherein the first information includes one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; downlink information to be transmitted to the first terminal device.

[0023] In aspect 18, a network device is provided, which is a second network device, including: a sending unit, used to send first information to a second terminal device, the second terminal device and the first terminal device belong to the same multi-access device, wherein the first information includes one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; downlink information to be transmitted to the first terminal device.

[0024] In the nineteenth aspect, a network device is provided, which is a first network device, including: a sending unit, used to send second information to a second network device, the second information is used to trigger the second network device to send first information, wherein the first information includes one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; downlink information to be transmitted to the first terminal device; wherein the first terminal device and the second terminal device are multi-access devices.

[0025] In the twentieth aspect, a terminal device is provided, which is a first terminal device, including: a receiving unit for receiving first information sent by a second terminal device, the first information including one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; downlink information to be transmitted to the first terminal device; wherein the first terminal device and the second terminal device are multi-access devices.

[0026] In the twenty-first aspect, a network device is provided, which is a first core network network element, including: a processing unit, used to determine whether the second terminal device and the first terminal device belong to the same multi-access device based on the signing message of the second terminal device.

[0027] In the twenty-second aspect, a network device is provided, which is a second core network network element, including: a sending unit, used to send a signing message of a second terminal device to the first core network network element, and the signing information of the second terminal device is used to determine whether the second terminal device and the first terminal device belong to the same multi-access device.

[0028] In the twenty-third aspect, a terminal device is provided, which is a first terminal device, including: a receiving unit for receiving second information or third information sent by a first core network network element, wherein the second information is used to indicate a refusal to paging the second terminal device through the first terminal device, and the third information is used to indicate that paging the second terminal device through the first terminal device will be allowed, which is updated to a refusal to paging the second terminal device through the first terminal device.

[0029] In the twenty-fourth aspect, a network device is provided, which is a first core network network element, including: a sending unit, used to send fifth information to a second terminal device, and the fifth information is used to request the second terminal device to confirm whether to allow or refuse to paging the first terminal device through the second terminal device, wherein the first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

[0030] In the twenty-fifth aspect, a terminal device is provided, which is a second terminal device, including: a receiving unit, used to receive fifth information sent by a first core network network element, and the fifth information is used to request the second terminal device to confirm whether to allow or refuse to paging the first terminal device through the second terminal device, wherein the first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

[0031] In the twenty-sixth aspect, a terminal device is provided, which is a first terminal device, including: a receiving unit, used to receive sixth information sent by a first core network network element, and the sixth information is used to indicate to a second terminal device whether to allow or refuse to paging the first terminal device through the second terminal device, wherein the first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

[0032] In aspect 27, a communication device is provided, which is a first device and includes: a sending unit for sending a first identifier to a second device, wherein the first identifier is used to identify a multi-access device, and the multi-access device includes a first terminal device and a second terminal device.

[0033] In aspect 28, a communication device is provided, which is a second device and includes: a receiving unit for receiving a first identifier sent by a first device, the first identifier being used to identify a multi-access device, the multi-access device including a first terminal device and a second terminal device.

[0034] In the twenty-ninth aspect, a communication device is provided, which is a first device and includes: a sending unit for sending first capability information to a second device, the first capability information being used to indicate whether the second terminal device supports paging through the first terminal device, and the first terminal device and the second terminal device are multi-access devices.

[0035] In the thirtieth aspect, a communication device is provided, which is a second device, including: a receiving unit for receiving first capability information sent by a first device, the first capability information being used to indicate whether the second terminal device supports paging through the first terminal device, and the first terminal device and the second terminal device are multi-access devices.

[0036] In the thirty-first aspect, a terminal device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes part or all of the steps in the methods of the above aspects.

[0037] In aspect 32, a network device is provided, comprising a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the network device executes part or all of the steps in the methods of the above aspects.

[0038] In aspect 33, a communication device is provided, comprising a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the communication device executes part or all of the steps in the methods of the above aspects.

[0039] In a thirty-fourth aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal device and / or network device. In another possible design, the system may also include other devices that interact with the terminal device or network device in the solution provided in the embodiment of the present application.

[0040] In aspect 35, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a communication device (for example, a terminal device or a network device) to execute part or all of the steps in the methods of the above aspects.

[0041] In aspect 36, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a communication device (e.g., a terminal device or a network device) to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0042] In aspect thirty-seven, an embodiment of the present application provides a chip comprising a memory and a processor, wherein the processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0043] The embodiments of the present application provide a new paging solution, which helps to improve the success rate of paging terminal equipment and thus improve the efficiency of transmitting downlink data / downlink signaling. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0045] FIG2(a) and FIG2(b) are schematic diagrams of the transition process of two registration management (RM) states on a terminal device and an access and mobility management function (AMF) network element, respectively.

[0046] FIG3(a) and FIG3(b) show the transition process of the connection management (CM) state.

[0047] FIG4 and FIG5 are schematic diagrams of multi-access scenarios applicable to embodiments of the present application.

[0048] FIG6 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.

[0049] FIG7 is a schematic diagram of a solution for paging a first terminal device based on a second paging message in an embodiment of the present application.

[0050] FIG8 is a schematic diagram of the working mode of a traditional mobile reachable timer and an implicit deregistration timer.

[0051] FIG9 is a schematic diagram of the working modes of the second timer associated with the first terminal device and the second timer associated with the second terminal device in an embodiment of the present application.

[0052] FIG10 is a schematic diagram of the working modes of the second timer associated with the first terminal device and the second timer associated with the second terminal device in an embodiment of the present application.

[0053] FIG11 is a schematic diagram of a solution for paging a first terminal device and a second terminal device based on a first paging message in an embodiment of the present application.

[0054] FIG12 is a schematic diagram of a working mode of a second timer associated with a multi-access device in an embodiment of the present application.

[0055] FIG13 is a schematic diagram of a wireless communication method according to an embodiment of the present application.

[0056] FIG14 is a schematic diagram of a solution for executing a dual paging mode on a multi-access device according to an embodiment of the present application.

[0057] FIG15 is a schematic diagram of a wireless communication method according to an embodiment of the present application.

[0058] FIG16 is a schematic diagram of a method for determining by a second terminal device whether to authorize a dual paging mode in an embodiment of the present application.

[0059] FIG17 is a schematic diagram of a wireless communication method according to an embodiment of the present application.

[0060] FIG18 is a schematic diagram of a solution for paging a first terminal device and a second terminal device associated with a multi-access device based on a first identifier in an embodiment of the present application.

[0061] Figure 19 is a schematic diagram of the transmission method of the first capability information in an embodiment of the present application.

[0062] Figure 20 is a schematic diagram of a terminal device according to an embodiment of the present application.

[0063] Figure 21 is a schematic diagram of a terminal device according to an embodiment of the present application.

[0064] Figure 22 is a schematic diagram of a network device according to an embodiment of the present application.

[0065] FIG23 is a schematic diagram of a network device according to an embodiment of the present application;

[0066] Figure 24 is a schematic diagram of a terminal device according to an embodiment of the present application.

[0067] Figure 25 is a schematic diagram of a network device according to an embodiment of the present application.

[0068] Figure 26 is a schematic diagram of a network device according to an embodiment of the present application.

[0069] Figure 27 is a schematic diagram of a terminal device according to an embodiment of the present application.

[0070] Figure 28 is a schematic diagram of a network device according to an embodiment of the present application.

[0071] Figure 29 is a schematic diagram of a terminal device according to an embodiment of the present application.

[0072] Figure 30 is a schematic diagram of a terminal device according to an embodiment of the present application.

[0073] Figure 31 is a schematic diagram of a communication device according to an embodiment of the present application.

[0074] Figure 32 is a schematic diagram of a communication device according to an embodiment of the present application.

[0075] Figure 33 is a schematic diagram of a communication device according to an embodiment of the present application.

[0076] Figure 34 is a schematic diagram of a communication device according to an embodiment of the present application.

[0077] Figure 35 is a schematic structural diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

[0078] The technical solutions in this application will be described below in conjunction with the accompanying drawings. For ease of understanding, the following first introduces a schematic diagram of the communication system architecture of an embodiment of this application in conjunction with Figure 1. Figure 1 is a schematic diagram of a communication system architecture applicable to an embodiment of this application. The network architecture may include terminal devices, access network (AN) network elements, and core network network elements.

[0079] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0080] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), MT, remote station, remote terminal, mobile device, user terminal, terminal, wireless core network element, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a dispatching entity that provides sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D). For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through a base station.

[0081] An access network element can be an access network device. This device is used by terminals to wirelessly access the network architecture and is primarily responsible for radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. An access network device can also be referred to as a radio access network (RAN) device. For example, an access network device can be a base station. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station may also refer to a communication module, modem, or chip used to be set in the aforementioned device or apparatus. A base station may also be a mobile switching center and a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station may support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the access network device.

[0082] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0083] In some deployments, the access network device in the embodiments of the present application may refer to a CU or a DU, or the access network device may include a CU and a DU. The gNB may also include an AAU.

[0084] The types of core network elements may include user plane function (UPF) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, policy control function (PCF) network element, application function (AF), data network (DN), network slice selection function (NSSF), authentication server function (AUSF), unified data management function (UDM), network exposure function (NEF), network repository function (NRF), and network slice-specific authentication and authorization function (NSSAAF). Among them, the UPF network element is mainly responsible for the transmission of user data, and the other network elements can be called control plane function network elements, which are mainly responsible for authentication, authorization, registration management, session management, mobility management, and policy control, etc., to ensure reliable and stable transmission of user data.

[0085] The UPF network element can be used to forward and receive data from the terminal. For example, the UPF network element can receive service data from the data network and transmit it to the terminal through the access network device; the UPF network element can also receive user data from the terminal through the access network device and forward it to the data network. Among them, the transmission resources allocated and scheduled by the UPF network element for the terminal are managed and controlled by the SMF network element. The bearer between the terminal and the UPF network element may include: the user plane connection between the UPF network element and the access network device, and the establishment of a channel between the access network device and the terminal. Among them, the user plane connection is a QoS flow that can be established between the UPF network element and the access network device to transmit data.

[0086] The AMF network element can be used to manage the terminal's access to the core network, such as terminal location update, network registration, access control, terminal mobility management, terminal attachment and detachment, etc. The AMF network element can also provide control plane storage resources for the session while providing services for the terminal's session, to store the session identifier, the SMF network element identifier associated with the session identifier, etc.

[0087] The SMF network element can be used to select a user plane network element for the terminal, redirect the user plane network element for the terminal, allocate an Internet Protocol (IP) address to the terminal, establish a bearer (also called a session) between the terminal and the UPF network element, modify and release the session, and control QoS.

[0088] The PCF network element is used to provide policies to the AMF network element and the SMF network element, such as QoS policy and slice selection policy.

[0089] The AF network element is used to interact with the 3GPP core network elements to support application-affected data routing, access network exposure functions, and interact with the PCF network elements for policy control.

[0090] A DN can provide data services to users on networks such as IP Multimedia Service (IMS) and the Internet. A DN can contain multiple application servers (ASs) that provide different application services, such as carrier services, Internet access, or third-party services. The ASs can implement AF functions.

[0091] NSSF is used for network slice selection and supports the following functions: selecting a set of network slice implementation schemes to serve terminal devices; determining the allowed network slice selection assistance information (NSSAI) and, when necessary, determining the mapping to the contracted single network slice selection assistance information (Single-Network Slice Selection Assistance Information, S-NSSAI); determining the configured NSSAI and, when necessary, determining the mapping to the contracted S-NSSAI; determining the set of AMFs that may be used to query terminal devices, or determining a list of candidate AMFs based on the configuration.

[0092] AUSF is used to receive the request from AMF to authenticate the terminal, request the key from UDM, and then forward the issued key to AMF for authentication processing.

[0093] UDM includes functions such as the generation and storage of user contract data, management of authentication data, and supports interaction with external third-party servers.

[0094] NEF is used for capability exposure. That is, based on NEF, network capabilities can be exported to external networks. External, untrusted applications can access core network data through NEF to ensure network security. NEF can also provide external application QoS capability exposure, event subscription, and AF request distribution.

[0095] The NRF is used to register, manage, and monitor the status of core network elements, enabling automated management of these elements. Upon startup, a core network element must register with the NRF before it can provide services. Registration information may include the core network element's type, address, and service list.

[0096] In addition, some networks (such as 5G networks) have added a network data analytics function (NWDAF) to the core network. Based on NWDAF, data can be collected from various core network elements and network management systems, and big data statistics, analysis, or intelligent data analysis can be performed to obtain network-side analysis or prediction data, thereby assisting various network elements to more effectively control terminal device access based on the data analysis results.

[0097] In some communication systems (such as 5G systems), core network elements may also be referred to as network functions (NFs).

[0098] The network elements in Figure 1 can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions implemented on a platform (e.g., a cloud platform). It should be noted that the network architecture shown in the above figure is only an example of the network elements included in the entire network architecture. In the embodiments of the present application, the network elements included in the entire network architecture are not limited.

[0099] Those skilled in the art will appreciate that the network architecture shown in FIG1 does not limit the network architecture. In a specific implementation, the network architecture may include more or fewer network elements than shown, or may combine certain network elements. It should be understood that in FIG1 , the AN or RAN is represented by (R)AN.

[0100] In some scenarios, network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which network devices and terminal devices are located.

[0101] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. In some embodiments of the present application, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments of the present application, the network device may also be a base station set up in a location such as land or water.

[0102] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0103] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0104] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0105] The “configuration” in the embodiment of the present application may include configuration through at least one of system messages, radio resource control (RRC) signaling and media access control element (MAC CE).

[0106] In some embodiments of the present application, "predefined" or "preset" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device or a network device). This application does not limit the specific implementation method. For example, predefined may refer to information defined in a protocol.

[0107] In some embodiments of the present application, the "protocol" may refer to a standard protocol in the field of communications, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and this application does not limit this.

[0108] For ease of understanding, some relevant technical knowledge involved in the embodiments of this application is first introduced. The following related technologies can be combined with the technical solutions of the embodiments of this application as optional solutions, and they all fall within the scope of protection of the embodiments of this application. The embodiments of this application include at least part of the following contents.

[0109] Non-terrestrial network (NTN)

[0110] The Third Generation Partnership Project (3GPP) is currently researching NTN technology. NTN typically uses satellite communications to provide communication services to terrestrial users. Compared to terrestrial cellular networks, satellite communications offer many unique advantages.

[0111] First, satellite communications are not restricted by user geography. For example, conventional terrestrial communication networks cannot cover areas where network equipment cannot be deployed, such as oceans, mountains, and deserts. Similarly, terrestrial communication networks do not cover certain sparsely populated areas. However, because satellite communications can cover a large ground area and orbit the Earth, theoretically, every corner of the Earth can be covered by a satellite communication network.

[0112] Secondly, satellite communications have significant social value. They can provide low-cost coverage to remote, mountainous areas and impoverished countries and regions, enabling people in these areas to enjoy advanced voice communications and mobile internet technologies. From this perspective, satellite communications help narrow the digital divide with developed regions and promote their development.

[0113] Again, satellite communication has the advantage of long distance, and the increase in communication distance does not significantly increase the cost of communication.

[0114] Finally, satellite communications are highly stable and not affected by natural disasters.

[0115] Communication satellites are classified according to their orbital altitude into low Earth orbit (LEO), medium Earth orbit (MEO), geostationary Earth orbit (GEO), and high elliptical orbit (HEO). Currently, research focuses on LEO and GEO satellites.

[0116] LEO satellites typically operate at altitudes between 500 and 1500 km. Accordingly, their orbital period is approximately 1.5 to 2 hours. For LEO satellites, the signal propagation delay for single-hop communication between users is typically less than 20 milliseconds. The maximum satellite visibility time for LEO satellites is approximately 20 minutes. LEO satellites offer advantages such as short signal propagation distances, low link loss, and low transmit power requirements for user devices.

[0117] GEO satellites orbit at an altitude of 35,786 km. They orbit the Earth every 24 hours. For GEO satellites, the signal propagation delay for single-hop communication between users is typically about 250 milliseconds.

[0118] To ensure satellite coverage and increase the capacity of the entire satellite communication system, satellites typically use multiple beams to cover the ground. Therefore, a single satellite can form dozens or even hundreds of beams to cover the ground. A single satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[0119] Currently, the NTN system includes the NR-NTN system and the Internet of Things (IoT)-NTN system.

[0120] RM

[0121] There are two RM states for terminal devices: RM-DEREGISTERED state (also known as "deregistration state") and RM-REGISTERED state. When in the RM-DEREGISTERED state, the terminal device is not registered with the network, and the terminal device context saved by AMF does not contain valid location and routing information, so the terminal device is unreachable to AMF. However, some authentication-related terminal device contexts will be stored in the terminal device and AMF, which helps to avoid executing the authentication process for each registration process, thereby simplifying the registration process of the terminal device. When in the RM-REGISTERED state, the terminal device is registered with the network, and the terminal device can conduct normal business communications through the network. At this time, the terminal device mobility management context will be saved in AMF.

[0122] The following text introduces the conversion process of the two RM states on the terminal device and AMF respectively in combination with Figure 2(a) and Figure 2(b).

[0123] As shown in Figure 2(a), in the terminal device, if the RM registration is rejected (registration reject), the terminal device is in the RM deregistration state. Conversely, if the RM registration is accepted (registration accept), the terminal device transitions from the RM deregistration state to the RM registration state.

[0124] In the terminal device, if the RM registration update is accepted (registration reject), the terminal device is in the RM registration state.

[0125] In the terminal device, if the deregistration registration is rejected (deregistration registration reject), the terminal device is in the RM deregistration state.

[0126] As shown in Figure 2(b), in the AMF, if the RM registration is rejected (registration reject), the terminal device is in the RM deregistered state. Conversely, if the RM registration is accepted (registration accept), the terminal device transitions from the RM deregistered state to the RM registered state.

[0127] In AMF, if the RM registration update is received (registration reject), the terminal device is in the RM registration state.

[0128] In AMF, if the deregistration registration is rejected (deregistration registration reject), the terminal device is in the RM deregistration state.

[0129] CM

[0130] Connection management includes the functions of establishing and releasing the N1 non-access stratum (NAS) signaling connection between the terminal device and the AMF. The N1 NAS signaling connection is used to enable direct signaling interaction between the terminal device and core network elements. It includes the connection between the terminal device and the access network equipment and the N2 connection between the access network equipment and the AMF associated with the terminal device.

[0131] The connection states between the terminal device and the AMF include: CM-IDLE and CM-CONNECTED. When the terminal device is in CM-IDLE, there is no N1 connection, AN signaling connection, N2 connection, or N3 connection corresponding to the terminal device. When the terminal device is in both CM-IDLE and RM-REGISTERED states, the terminal device needs to initiate a service request process to respond to the paging, unless the terminal device is in 5G mobile initiated connection only (MICO) mode. Alternatively, when the terminal device has uplink signaling or data to send, a service request process is initiated. When the RM state of the terminal device in the AMF is RM-REGISTERED, the information required to initiate communication with the terminal device will be stored in the AMF, and the AMF can determine the above information of the terminal device through the (5G globally unique temporary identifier, 5G-GUTI).

[0132] In some scenarios, the terminal device will provide AN parameters such as 5G-S-TMSI during the AN signaling connection establishment process. As shown in Figure 3(a), whenever an AN signaling connection is established, the terminal device can transition from CM-idle state to CM-connected state. For example, if the initial NAS signaling connection (e.g., registration request, service request, and deregistration request) is established, the transition from CM-idle state to CM-connected state can be triggered. Conversely, whenever an AN signaling connection is released (e.g., initial NAS information), the transition from CM-connected state to CM-idle state can be triggered.

[0133] In some scenarios, when the terminal device state in the AMF is CM-IDLE and RM-REGISTRATION, and the AMF has signaling or data to send to the terminal device, it is necessary to initiate paging to the terminal device and obtain a response to execute the service request process initiated by the network side. As shown in Figure 3(b), when an N2 connection is established for a terminal device, the state of the terminal device in the AMF is converted from CM-IDLE to CM-CONNECTED. For example, the reception of the initial N2 message transmitted via the N2 connection can trigger the state of the terminal device in the AMF to change from CM-IDLE to CM-CONNECTED. In some scenarios, when the terminal device is in CM-IDLE state, it can enter MICO mode to reduce energy consumption and signaling overhead.

[0134] In some scenarios, when a terminal device is in the CM-CONNECTED state, an N1 NAS signaling connection exists between the terminal device and the AMF. This NAS signaling connection uses the RRC connection between the terminal device and the NG-RAN and the NGAP terminal device association between the AN and the AMF. A terminal device can be in the CM-CONNECTED state and the NGAP can also be unbound to any transport network layer. After the NAS signaling process is completed, the AMF can decide to release the NAS signaling connection between the terminal device and the AMF.

[0135] In some scenarios, when a terminal device is in CM-CONNECTED, it enters the CM-IDLE state whenever the AN signaling connection is released. The CM-IDLE state is entered whenever the logical NGAP signaling connection and the N3 user plane connection for this terminal device are released after the AN is released. The AMF may maintain the terminal device in the CM-CONNECTED state until the terminal device deregisters from the network.

[0136] In some scenarios, a terminal device in CM-CONNECTED can also be in the RRC_INACTIVE state. In this case, the RAN will release the AN connection between the terminal device and the terminal device. The terminal device is active in the area configured by the RAN, and the N2 connection still exists. The reachability of the terminal device is managed by the RAN based on the auxiliary information provided by the network side. The terminal device paging is managed by the RAN, and the terminal device listens for paging with the network identifier (5G S-TMSI) and RAN identifier corresponding to the terminal device. When the terminal device leaves the area configured by the RAN, it needs to notify the RAN.

[0137] Accessibility of terminal devices

[0138] Reachability management is responsible for detecting whether a terminal device is reachable and providing the network with the terminal device's location (i.e., access node) so that information sent by the network can reach the terminal device. This process is accomplished by paging the terminal device and tracking its location. Location tracking includes terminal device registration area tracking (i.e., terminal device registration area update) and terminal device reachability tracking (i.e., terminal device periodic registration area update). This function can be implemented by network elements in the 5GC (in the CM-IDLE state) or by network elements in the NG-RAN (in the CM-CONNECTED state).

[0139] In some scenarios, the terminal device and the AMF negotiate the terminal device reachability characteristics in the CM-IDLE state during the registration process. The terminal device and the AMF negotiate the following three terminal device reachability categories for the CM-IDLE state: reachability category 1 to reachability category 3.

[0140] For reachability category 1, this category is used to indicate the reachability category that allows data to be sent to the terminal device when the terminal device is in the CM-IDLE state.

[0141] In this reachability category, the network can understand the location of the terminal device at the granularity of the tracking area list. In this reachability category, paging procedures are applicable to this category. In addition, in this reachability category, terminal device-originated data and terminal device-terminated data are applicable to CM-CONNECTED and CM-IDLE states.

[0142] For reachability category 2, the connection mode is initiated only by the terminal device.

[0143] In this reachability category, end-device originated data is applicable in this category for both CM-CONNECTED and CM-IDLE states. In this reachability category, end-device terminated data is supported only when the end-device is in the CM-CONNECTED state.

[0144] For reachability category 3, the terminal equipment is in an unavailable period and cannot be reached.

[0145] In this reachability class, terminal-originated and terminal-terminated data are not supported. In addition, this reachability class does not apply to paging procedures.

[0146] Whenever a terminal device in the RM-REGISTERED state enters the CM-IDLE state, it starts a periodic registration timer according to the periodic registration timer assigned by the AMF during the registration process. The terminal device needs to perform periodic registration after the periodic registration timer expires. If the terminal device moves out of the network coverage when its periodic registration timer expires, the terminal device should perform the registration process the next time it returns to the coverage area.

[0147] The AMF runs the Mobile Reachable Timer for the terminal device. Whenever the CM state of a terminal device in the RM-REGISTERED state changes to CM-IDLE, the timer is started with a value longer than the terminal device's periodic registration timer. If the AMF receives an elapsed time from the RAN when the RAN initiates a terminal device context release indicating that the terminal device is unreachable, the AMF shall derive the Mobile Reachable Timer value based on the elapsed time received from the RAN and the normal Mobile Reachable Timer value. If the terminal device's CM state in the AMF transitions to the CM-CONNECTED state, the AMF stops the Mobile Reachable Timer. If the Mobile Reachable Timer expires, the AMF determines that the terminal device is unreachable. When the Mobile Reachable Timer expires, the AMF cannot determine whether the terminal device is only temporarily unreachable and therefore does not immediately deregister the terminal device. Only after the Mobile Reachable Timer expires will the AMF clear the Paging Handling Indication Bit and start the Implicit Deregistration Timer. If the terminal device changes to the CM-CONNECTED state before the timer expires, the AMF shall stop the Implicit Registration Timer and set the Performance and Reliability Prediction (PPF) flag. Otherwise, after the implicit registration timer expires, AMF initiates private deregistration of the terminal device.

[0148] If the terminal device indicates the duration of the unavailable period, the AMF will consider the terminal device unreachable and will not trigger the paging process (e.g. clear PPF) until the terminal device registers for normal services again (e.g. set PPF). Once the event that caused the terminal device to be unavailable is completed or canceled in the terminal device, the terminal device will initiate the registration process to resume normal service.

[0149] If the CM state of the terminal device in the AMF is CM-IDLE, the AMF considers the terminal device in RM-REGISTERED state to be reachable via CN paging unless the terminal device applies MICO mode or the terminal device has indicated the unavailable period duration.

[0150] Multi-access (also known as "Dualsteer") scenario

[0151] In some scenarios, a device that supports multi-access functionality may be referred to as a multi-access device (or dual-split device). In some scenarios, a multi-access device may be a device that supports traffic guidance and switching across multiple third-generation partnership project (3GPP) access networks (for example, two 3GPP access networks) for user data of different services. In the case of non-simultaneous data transmission on multiple networks, a multi-access device may be regarded as a terminal device. In the case of simultaneous data transmission on multiple networks, a multi-access device may be regarded as multiple separate UEs.

[0152] In some scenarios, multiple terminal devices can be deployed on the same physical entity, which is a multi-access device. As shown in Figure 4, the first terminal device (also known as UE-1) and the second terminal device (also known as UE-2) associated with the multi-access device are located in the same physical entity. Among them, UE-1 may include a universal subscriber identity module (USIM)-1, and UE-2 may include USIM-2. UE-1 can access core network 1 through access network 1, wherein access network 1 can be deployed on a satellite. UE-2 can access core network 2 through access network 2, wherein access network 2 can be deployed on the ground. The data flowing through core network 1 and core network 2 is finally input into the data network.

[0153] In other scenarios, multiple terminal devices can be deployed on different physical entities, and the multiple physical entities constitute a multi-access device. As shown in Figure 5, the first terminal device (also referred to as UE-1) and the second terminal device (also referred to as UE-2) associated with the multi-access device are respectively located in different physical entities. UE-1 may include USIM-1, and UE-2 may include USIM-2. UE-1 can access the core network through access network 1, where access network 1 can be deployed on a satellite. UE-2 can access the core network through access network 2, where access network 2 can be deployed on the ground. The data flowing through the core network is then finally input into the data network.

[0154] In some implementations, UE-1 and UE-2 may communicate via one or more of the following: PC5 interface; wireless fidelity (WiFi); Bluetooth; or a wired connection.

[0155] In the traditional solution, if the terminal device is in the CM-IDLE state or the CM-CONNECTED with RRC_INACTIVE state, there is no connection between the terminal device and the network device. At this time, if the network device has downlink data (for example, MT data) or downlink signaling to be transmitted, it is necessary to re-paging the terminal device. If the terminal device cannot be paged, the downlink data or downlink signaling transmission fails. However, for multi-access scenarios, there are multiple associated terminal devices serving the user at the same time. If the traditional paging method is used, only when a terminal device cannot be paged, the multi-access device corresponding to the terminal device is considered unreachable, and downlink data or downlink signaling is no longer sent to the multi-access device, which may result in low efficiency in transmitting downlink data / downlink signaling and reduce user experience.

[0156] Therefore, in response to the above-mentioned problems, an embodiment of the present application provides a new paging scheme, which helps to improve the success rate of paging terminal devices, so as to improve the efficiency of transmitting downlink data / downlink signaling. In some scenarios, the paging scheme of the embodiment of the present application is also called a dual paging mode. Assuming that the terminal devices associated with a multi-access device include a first terminal device and a second terminal device, in some implementations, the dual paging mode may include one or more of the following: paging the second terminal device through the first terminal device, and paging the first terminal device through the second terminal device; paging the first terminal device and the second terminal device at the same time. The following describes the wireless communication method of the embodiment of the present application in conjunction with Figure 6. The method shown in Figure 6 includes step S610.

[0157] In step S610, the second network device sends the first information to the second terminal device, where the second terminal device and the first terminal device belong to the same multi-access device, or in other words, the first terminal device and the second terminal device are associated with one multi-access device. For example, the first terminal device and the second terminal device are two independent terminal devices in the same multi-access device. For another example, the first terminal device and the second terminal device are two modules (e.g., USIM) in the same multi-access device. For details, please refer to the above description in conjunction with Figures 4 and 5.

[0158] In the embodiments of the present application, there is no limit on the number of terminal devices included in a multi-access device. For example, the multi-access device may include only two terminal devices, namely, a first terminal device and a second terminal device. In another example, the multi-access device may include at least three terminal devices, wherein the first terminal device and the second terminal device are only part of the terminal devices included in the multi-access device.

[0159] In some implementations, the first information may include downlink information to be transmitted to the first terminal device. That is, the second network device may send the downlink information to the second terminal device, and then the second terminal device forwards the downlink information to the first terminal device. The downlink information may include, for example, downlink data and / or downlink signaling.

[0160] For example, if the second terminal device is in the CM-CONNECTED state, the second network device can send the downlink information and / or downlink signaling of the first terminal device to the second terminal device.

[0161] In an embodiment of the present application, the downlink data / downlink signaling of the first terminal device can be received by the second terminal device, which helps to improve the timeliness of the downlink data / downlink signaling transmission to enhance the user experience.

[0162] In some implementations, the above-mentioned step S610 may include, when the paging of the first terminal device fails, the second network device sending the first information (i.e., the downlink information to be transmitted to the first terminal device) to the second terminal device, wherein the reason for the paging failure of the first terminal device can be referred to the introduction below.

[0163] In an embodiment of the present application, if the paging of the first terminal device fails, the downlink information to be transmitted to the first terminal device can be sent to the second terminal device, which helps to improve the timeliness of downlink data / downlink signaling transmission and enhance the user experience.

[0164] In some implementations, the first information may include a second paging message for paging the first terminal device.

[0165] In an embodiment of the present application, the first terminal device can be paged by sending a second paging message to the second terminal device, which helps to improve the success rate of paging the first terminal device.

[0166] It should be noted that the second network device can serve both the first terminal device and the second terminal device. For example, the second network device can include an AMF that serves both the first terminal device and the second terminal device. In other implementations, the second network device can serve the second terminal device, and the first network device can serve the first terminal device. Moreover, the first network device and the second network device are different network devices. In this case, the second paging message can be determined based on the second information sent by the first network device to the second network device, and sent by the second network device to the second terminal device.

[0167] In the embodiment of the present application, the second information may include information in the second paging message, such as the identifier of the second terminal device and / or the first indication information, etc. Of course, in the embodiment of the present application, the second information may be the same as the second paging message.

[0168] In the embodiments of the present application, there is no limitation on the manner in which the first network device obtains the second network device. In some implementations, the first network device may query the UDM for the subscription data of the first terminal device to determine the second terminal device and the serving AMF of the second terminal device (as an example of the second network device). In some implementations, the serving AMF of the second terminal device is carried in the registration message of the second terminal device.

[0169] It should also be noted that, if the second network device is an AMF, the second network device sending the first information to the second terminal device may include the second network device sending a second paging message to the second terminal device via the second access network device. Of course, in the embodiment of the present application, the second network device may also be an access network device.

[0170] In some scenarios, the second network device may be located on a satellite, and the first network device may be located on the ground. Accordingly, if the first network device is unable to page the first terminal device, the second terminal device may be paged through a second network device with a larger coverage area, thereby paging the first terminal device. In the above scenarios, the NTN and TN networks can be fully utilized as complements to avoid the unreachability of the multi-access device due to the movement of the multi-access device or the movement of the satellite, which helps to send downlink data / downlink signaling to the multi-access device in a timely manner. Of course, in an embodiment of the present application, the first network device and the second network device may both be located on the ground or on the satellite. Alternatively, the first network device may be located on the satellite, and the second network device may be located on the ground.

[0171] In some implementations, the above-mentioned step S610 may include that when the paging of the first terminal device fails, the second network device sends the first information (i.e., the second paging message) to the second terminal device, wherein the reason for the paging failure of the first terminal device can be referred to the introduction below.

[0172] In an embodiment of the present application, if the paging of the first terminal device fails, the first terminal device can be paged by sending a second paging message to the second terminal device. Compared with the traditional paging scheme, if the paging of the first terminal device fails, the first terminal device will no longer be paged, which helps to improve the success rate of paging the first terminal device.

[0173] In some implementations, the second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information; and second indication information.

[0174] Taking the identification of the first terminal device as an example, the identification of the first terminal device may include one or more of the following: subscription permanent identifier (SUPI), subscription concealed identifier (SUCI), permanent equipment identity (PEI), temporary mobile subscriber identity (TMSI), globally unique temporary identity (GUTI), 5G-S-temporary mobile subscriber identity (5G-S-TMSI), and global unique asset management identifier (GUAMI).

[0175] Taking the identifier of the second terminal device as an example, the identifier of the second terminal device may include one or more of the following: SUPI, SUCI, PEI, TMSI, GUTI, 5G-S-TMSI, and GUAMI.

[0176] Taking the first indication information as an example, the first indication information is used to instruct the network device to page the first terminal device through the second terminal device. In some scenarios, the paging method of paging the first terminal device through the second terminal device can also be called a dual paging mode. Accordingly, the first indication information can also be called a dual paging indication information. Accordingly, the first indication information can be used to instruct the network device to adopt the dual paging mode.

[0177] Taking the second indication information as an example, the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device, or in other words, the second indication information is used to indicate the reason for paging the first terminal device.

[0178] In some implementations, the reason for paging the first terminal device may include a failure in paging the first terminal device, that is, the second indication information is used to indicate a failure in paging the first terminal device.

[0179] In the embodiment of the present application, the reason for the failure of paging the first terminal device is not limited. In some implementations, the reason is associated with the mobility of the first terminal device, that is, the failure of paging the first terminal device is caused by the mobility of the first terminal device. For example, the first terminal device moves out of the coverage of the network device, resulting in the failure of paging the first terminal device. In other implementations, the reason is associated with the mobility of the network device serving the first terminal device, that is, the failure of paging the first terminal device is caused by the mobility of the network device. For example, as the network device moves, the first terminal device is no longer within the coverage of the network device, resulting in the failure of paging the first terminal device. The network device may include, for example, an access network device and / or a core network element. In other implementations, the reason may include that the service AMF of the first terminal device does not receive the response information sent by the first terminal device within a given time period (for example, through a time window identifier). In other implementations, the reason may include that the network device providing service to the first terminal device (for example, an AMF or an access network device) receives a rejection paging indication sent by the first terminal device. In other implementations, if the first terminal device accesses the network through the NTN, the reason may include that no satellite can cover the first terminal device in time period 1. For example, the service AMF of the first terminal device can compare the registration area of ​​the first terminal device with the satellite ephemeris information to conclude that no satellite can cover the first terminal device in time period 1, resulting in failure to page the first terminal device. In other implementations, the reason may include the access network device providing services to the first terminal device indicating to the service AMF of the first terminal device that the first terminal device is unreachable. For example, the service AMF of the first terminal device can subscribe to the reachability status of the first terminal device to the access network device providing services to the first terminal device. If the first terminal device is unreachable, the access network device providing services to the first terminal device can indicate to the service AMF of the first terminal device that the first terminal device is unreachable.

[0180] In some implementations, if the second terminal device is in the CM-CONNECTED state, the second network device may directly send the second paging message to the second terminal device.

[0181] In other implementations, if the second terminal device is in an RRC inactive state or a CM-IDLE state, the second network device may first page the second terminal device in order to send a second paging message to the second terminal device. Of course, in an embodiment of the present application, the second network device may page the second terminal device through the second paging message, or in other words, the second network device may reuse the second paging message to page the second terminal device to reduce the overhead of paging the second terminal device.

[0182] In some implementations, if the second terminal device sends a second paging message to the first terminal device, the first terminal device may attempt to establish a connection with the network device to receive downlink data or downlink signaling from the first terminal device.

[0183] In some implementations, if the second terminal device sends a second paging message to the first terminal device, the first terminal device may attempt to establish a connection with the network device to receive downlink data or downlink signaling from the first terminal device.

[0184] For ease of understanding, the following describes, in conjunction with Figure 7, a scheme for paging the first terminal device based on the second paging message in an embodiment of the present application. Assume that the first terminal device is UE-1, and the access network serving UE-1 is AN-1, and the AMF serving UE-1 is AMF-1. The second terminal device is UE-2, and the access network serving UE-2 is AN-2, and the AMF serving UE-2 is AMF-2. The method described in Figure 7 includes steps S710 to S770.

[0185] In step S710 , AMF-1 fails to page UE-1.

[0186] In some implementations, the above-mentioned scenarios of failure in paging UE-1 may include one or more of the following: AMF-1 does not receive a response message from UE-1 within a given time window; AN-1 fails to page the UE and notifies AMF-1 of the failure to paging UE-1, for example, AMF-1 subscribes to the reachability status of UE-1 to AN-1, and AN-1 will inform AMF-1 whether it is reachable or unreachable; AMF-1 or AN-1 receives a rejection of paging indication from UE-1; UE-1 accesses the network through NTN, and no satellite can cover UE-1 for a period of time, for example, AMF-1 can conclude that UE-1 cannot be paged for a period of time by comparing the registration area of ​​UE-1 with the satellite ephemeris information.

[0187] In step S720, AMF-1 can subscribe to UE-2's subscription data from UDM, and based on the data, determine that UE-1 has an associated UE-2, and obtain UE-2's registration information (i.e., AMF-2 serving UE-2).

[0188] In step S730, AMF-1 sends a paging message 2 to AMF-2 to page UE-1 by paging UE-2.

[0189] In some implementations, the paging message 2 may include one or more of the following: identification information of UE-2; identification information of UE-1; identification of the multi-access device to which UE-1 and UE-2 belong; dual paging indication information; address information of UE-1; AN-1 identification information; AMF-1 identification information; PAS UPF identification information; DNN; S-NSSAI.

[0190] In step S740, AMF-2 sends a paging message 3 to AN-2, where the paging message 3 carries dual paging indication information.

[0191] In step S750, AN-2 sends a paging message 4 to UE-2, where the paging message 4 carries dual paging indication information.

[0192] In some implementations, if UE-2 is in CM-CONNECTED, AN-2 can send a paging message directly to UE-2, which is forwarded by UE-2 to UE-1. If UE-2 is in RRC Inactive or CM-IDLE state, AN-2 can page UE-2 using Paging Message 4.

[0193] In step S760, the multi-access device establishes a connection with AN-1, and AN-1 can send downlink data and / or downlink signaling.

[0194] In some implementations, UE-2 sends a paging message 4 to UE-1, and then UE-1 establishes a connection with AN-1 to receive downlink data and / or downlink signaling.

[0195] In other implementations, UE-2 establishes a connection with AN-1, AN-1 sends downlink data and / or downlink signaling to UE-2, and then UE-2 forwards the received downlink data and / or downlink signaling to UE-1.

[0196] In an embodiment of the present application, UE-1 will be paged through UE-2 associated with UE-1 only after the first paging of UE-1 fails. This solution can be applicable to the scenario where the satellite serving UE-1 has left the location of UE-1. At this time, UE-1 can be prompted to establish a connection with the network by paging UE-2 associated with UE-1 that accesses the core network through the ground network.

[0197] Of course, this solution can also be applied to scenarios where UE-1 leaves the terrestrial network coverage area and UE-2, and thus UE-1, is paged via a satellite with wider coverage. In such scenarios, the NTN access network and the TN network can be fully utilized as a complement to avoid UE unreachability caused by multi-access device movement or satellite movement, and facilitate the timely delivery of downlink data or downlink signaling to multi-access devices.

[0198] In addition, this solution can also be applied to scenarios where UE-1 cannot or refuses to establish a connection with the network due to resource limitations. In this case, downlink data can be received by UE-2 and forwarded to UE-1, thereby enhancing user experience.

[0199] In some scenarios, as shown in Figure 8, if a registered terminal device is in an idle state, the AMF will start a mobile reachable timer for it. Accordingly, when the mobile reachable timer expires, the AMF will not page the terminal device, and will start a second timer for it (also known as an "implicit deregistration timer"), and perform the implicit deregistration process after the second timer expires. However, for multi-access devices, this setting method of the second timer may cause the terminal device originally associated with the multi-access device to be paged, but due to the expiration of the second timer associated with the terminal device, the paging fails.

[0200] Taking a multi-access device including a first terminal device and a second terminal device as an example, assume that after the network device fails to page the first terminal device, it then pages the first terminal device through the second terminal device. In this case, because the first terminal device is paged first and the paging fails, the second timer associated with the first terminal device starts first. If the second timer associated with the second terminal device expires, even if the network device can page the first terminal device through the second terminal device, the network device will perform an implicit deregistration process for the second terminal device, causing the paging of the second terminal device to fail.

[0201] Therefore, in response to the above problem, in an embodiment of the present application, a different second timer can be introduced for the first terminal device and the second terminal device, that is, the duration indicated by the second timer associated with the first terminal device is different from the duration indicated by the second timer associated with the second terminal device, and / or the start condition of the second timer associated with the first terminal device is different from the start condition of the second timer associated with the second terminal device.

[0202] In some implementations, the start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails. That is, after both the first terminal device and the second terminal device fail to paging, the second timer associated with the first terminal device starts. Correspondingly, the second timer associated with the second terminal device can be started after the paging of the second terminal device fails, which helps to ensure that the second timer associated with the first terminal device and the second timer associated with the second terminal device expire at the same time. In other words, the first terminal device and the second terminal device are implicitly deregistered at the same time.

[0203] In some implementations, the duration of the second timer associated with the first terminal device is the same as the duration of the timer associated with the second terminal device.

[0204] For ease of understanding, the second timer associated with the first terminal device and the second timer associated with the second terminal device in an embodiment of the present application are introduced below in conjunction with Figure 9. As shown in Figure 9, it is assumed that UE-1 and UE-2 are the first terminal device and the second terminal device associated with the multi-access device introduced above. At time t1, the first terminal device enters the idle state. At this time, the mobile reachable timer of UE-1 is started, and after the mobile reachable timer of UE-1 expires (that is, at time t2), UE-1 cannot be paged by AMF-1. Accordingly, at time t2, AMF-1 pages UE-2. If AMF-1 fails to page UE-2 by time t3, AMF-1 starts implicit deregistration timers for UE-1 and UE-2 respectively. The duration indicated by the implicit deregistration timers of UE-1 and UE-2 is the same.

[0205] In some implementations, the time period indicated by the second timer associated with the first terminal device can be determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device. That is, the start time of the second timer associated with the first terminal device can be determined based on the time when the paging of the first terminal device fails. For example, in response to the paging failure of the first terminal device, the second timer is started. Accordingly, the duration indicated by the second timer associated with the first terminal device can be determined based on the duration required for paging the second terminal device and the duration of the second timer associated with the second terminal device. For example, the duration indicated by the second timer associated with the first terminal device is the sum of the duration required for paging the second terminal device and the duration of the second timer associated with the second terminal device. In other words, the expiration time of the second timer associated with the first terminal device is the same as the expiration time of the second timer associated with the second terminal device.

[0206] For ease of understanding, the second timer associated with the first terminal device and the second timer associated with the second terminal device in an embodiment of the present application are introduced below in conjunction with Figure 10. As shown in Figure 10, it is assumed that UE-1 and UE-2 are the first terminal device and the second terminal device associated with the multi-access device introduced above. At time t1, the first terminal device enters the idle state. At this time, the mobile reachable timer of UE-1 is started, and after the mobile reachable timer of UE-1 expires (i.e., time t2), UE-1 cannot be paged by AMF-1. At this time, the implicit de-registration timer of UE-1 is started. Correspondingly, at time t2, AMF-1 can continue to page UE-2. If AMF-1 fails to page UE-2 by time t3, AMF-1 starts the implicit de-registration timer for UE-2. Among them, the expiration time of the implicit de-registration timer of UE-1 and the implicit de-registration timer of UE-2 are the same, i.e., time t4. That is, the time period indicated by the implicit deregistration timer of UE-1 includes the time period for paging UE-2 (i.e., time t2 to time t3) and the time period indicated by the implicit deregistration timer of UE-2 (i.e., time t3 to time t4).

[0207] In some implementations, the first information may include a first paging message for paging the first terminal device and the second terminal device. In other words, the network device may use the first information to simultaneously page the first terminal device and the second terminal device. Alternatively, the network device may use the first information to simultaneously page all terminal devices associated with the multi-access device.

[0208] In some implementations, the first paging message includes one or more of the following: identification information associated with the first terminal device; first indication information, wherein the first indication information is used to instruct the network device to page the first terminal device through the second terminal device. For details, please refer to the above introduction to the first indication information.

[0209] In some implementations, the identification information associated with the first terminal device includes an identification of the first terminal device and / or an identification of the multi-access device.

[0210] Taking the identifier of a multi-access device as an example, the identifier of the multi-access device can be called the dual-steer device identifier "dualsteer device ID". In some implementations, the identifier of the multi-access device can be used to identify the multi-access device, or the identifier of the multi-access device can be used to identify all terminal devices associated with the multi-access device.

[0211] In some implementations, the identifier of the multi-access device may be allocated by the network device to the multi-access device. Of course, in the embodiment of the present application, the identifier of the multi-access device may also be pre-configured.

[0212] In an embodiment of the present application, the second network device can page the first terminal device and the second terminal device at the same time by sending the first paging message, which helps to improve the success rate of paging the first terminal device.

[0213] It should be noted that the second network device can serve both the first terminal device and the second terminal device. For example, the second network device can include an AMF that serves both the first terminal device and the second terminal device. In other implementations, the second network device can serve the second terminal device, and the first network device can serve the first terminal device. Moreover, the first network device and the second network device are different network devices. In this case, the sending of the first paging message can be triggered by a paging message 3 (also called the second message) sent by the first network device to the second network device. In other words, the first network device can send a paging message 3 to the second network device to trigger the second network device to send the first paging message to the second terminal device.

[0214] In some implementations, paging message 3 may include one or more of the following: an identifier of the first terminal device, an identifier of the second terminal device; an identifier of a multi-access device; first indication information; address information of the first terminal device; identification information of an access network device providing services to the first terminal device; identification information of the serving AMF of the first terminal device; PAS UPF identification information; DNN; and S-NSSAI. For the introduction to the first indication information, the identifier of the multi-access device, the identifier of the first terminal device, and the identifier of the second terminal device, please refer to the above, and this embodiment of the present application does not limit this.

[0215] Taking the address information of the first terminal device as an example, this information is used to identify the PSA UPF that sends downlink data.

[0216] Taking the identification information of the access network device that provides services to the first terminal device as an example, this information is used to identify the identification of the access network device that sends downlink data / downlink signaling.

[0217] Taking the service AMF identifier of the first terminal device as an example, this information is used to identify the AMF identifier for sending downlink data / downlink signaling.

[0218] Taking the PAS UPF identification information as an example, this information is used to identify the PSA UPF that sends downlink data.

[0219] Taking DNN as an example, this information is used to identify the data network where the server sending downlink data is located.

[0220] Taking S-NSSAI as an example, this information is used to identify the slice where the server sending downlink data is located.

[0221] In the embodiments of the present application, there is no limitation on the manner in which the first network device obtains the second network device. In some implementations, the first network device may query the UDM for the subscription data of the first terminal device to determine the second terminal device and the serving AMF of the second terminal device (as an example of the second network device). In some implementations, the serving AMF of the second terminal device is carried in the registration message of the second terminal device.

[0222] In some implementations, if the second terminal device is in the CM-IDLE state or the CM-CONNECTED with RRC_INACTIVE state, the access network device serving the second terminal device may page the second terminal device via a first paging message.

[0223] In some implementations, if the second terminal device is in the CM-CONNECTED state, the access network device serving the second terminal device can directly send the first paging message to the second terminal device through the established connection.

[0224] In some implementations, after the second terminal device receives the first paging message, the first paging message may be forwarded to the first terminal device to improve the success rate of paging the first terminal device.

[0225] It should be noted that, before the first terminal device receives a paging message sent by the second terminal device, the first terminal device receives a paging message sent by the first network device and establishes a connection with the first network device, the first terminal device may ignore the paging message sent by the second terminal device. Conversely, before the first terminal device receives a paging message sent by the first network device, the first terminal device receives a paging message sent by the second terminal device and has established a connection with the first terminal device, the first terminal device may ignore the paging message sent by the first network device.

[0226] For ease of understanding, the following describes, in conjunction with Figure 11, a scheme for paging the first terminal device and the second terminal device based on the first paging message in an embodiment of the present application. Assume that the first terminal device is UE-1, and the access network serving UE-1 is AN-1, and the AMF serving UE-1 is AMF-1. The second terminal device is UE-2, and the access network serving UE-2 is AN-2, and the AMF serving UE-2 is AMF-2. The method described in Figure 11 includes steps S1110 to S1170.

[0227] In step S1110, AMF-1 sends a paging message 1 to UE-1 through the access network device AN-1. The paging message 1 includes the identification information of UE-1 and / or dual paging indication information.

[0228] In some implementations, the identification information of UE-1 may be GUTI-1, which is the identification of the multi-access device to which UE-1 belongs. Of course, the identification information of UE-1 may also be other UE identifications.

[0229] In some implementations, the dual paging indication information is used to indicate that the network side has adopted a dual paging mode (dual paging). The parameter may be carried in the paging message only when the network side decides to adopt dual paging.

[0230] In some implementations, if downlink data or downlink signaling needs to be sent to UE-1, AMF-1 can determine whether to use dual paging mode based on one or more of the following: local configuration, UE-1's subscription data, and capability negotiation results with UE-1.

[0231] In step S1120, AMF-1 needs to query the UDM for the subscription data of UE-1, find UE-2 associated with UE-1, and obtain the registration information of UE-2 (that is, the AMF-2 serving UE-2).

[0232] In step S1130, AMF-1 sends a paging message 2 to AMF-2, and the paging message 2 carries one or more of the following parameters: UE-2's identification information; UE-1's identification information; identification information of the multi-access device to which UE-1 and UE2 belong; dual paging indication information; UE-1's address information; AN-1 identification information; AMF-1 identification information; PAS UPF identification information; DNN; S-NSSAI.

[0233] In step S1140, AMF-2 sends a paging message 3 to AN-2, where the paging message 3 carries dual paging indication information.

[0234] In some implementations, if UE-2 is in CM-IDLE state or CM-CONNECTED with RRC_INACTIVE state, AN-2 pages UE-2.

[0235] In some implementations, if UE-2 is in the CM-CONNECTED state, AN-2 may directly send the paging message 3 to UE-2 through the established connection (see step S1150 ).

[0236] In step S1160 , UE- 1 establishes a connection with AN- 1 .

[0237] In some implementations, if UE-1 receives the paging message 1 in step S1110, it establishes a connection with AN-1 to receive downlink signaling or data. If UE-2 receives the paging message 3 in step S1150, it may forward the paging message 3 to UE-1. Accordingly, if UE-1 has already established a connection with the network side before receiving the paging message 3 forwarded by UE-2, UE-1 may ignore the paging message 3 forwarded by UE-2. Otherwise, if UE-1 has not established a connection with the network side before receiving the paging message 3 forwarded by UE-2, UE-1 may establish a connection with AN-1 based on the parameters in the paging message 3. If, after this connection is established, UE-1 receives the paging message 1 in step S1110 again, UE-1 may ignore the paging message 1.

[0238] In an embodiment of the present application, if all terminal devices associated with the multi-access device support dual paging mode, dual paging mode can be used during the first paging. This helps reduce the time wasted by failing to paging a terminal device associated with the multi-access device, allowing the paged terminal device to establish a connection with the network as quickly as possible to receive downlink data or downlink signaling. Therefore, the solution of the embodiment of the present application is applicable to scenarios where emergency services or delay-sensitive services are transmitted.

[0239] In some scenarios, as shown in Figure 8, if a registered terminal device is in an idle state, the AMF will start a mobile reachable timer for it. Accordingly, when the mobile reachable timer expires, the AMF will not page the terminal device, and will start a second timer for it (also known as an "implicit deregistration timer"), and perform the implicit deregistration process after the second timer expires. However, for multi-access devices, this setting method of the second timer may cause the terminal device originally associated with the multi-access device to be paged, but due to the expiration of the second timer associated with the terminal device, the paging fails.

[0240] Taking a multi-access device including a first terminal device and a second terminal device as an example, assume that after the network device fails to page the first terminal device, it then pages the first terminal device through the second terminal device. In this case, because the first terminal device is paged first and the paging fails, the second timer associated with the first terminal device starts first. If the second timer associated with the second terminal device expires, even if the network device can page the first terminal device through the second terminal device, the network device will perform an implicit deregistration process for the second terminal device, causing the paging of the second terminal device to fail.

[0241] Therefore, in response to the above-mentioned problem, in an embodiment of the present application, a second timer can be introduced for a multi-access device, or a multi-access device can be associated with a second timer, or the terminal devices associated with the multi-access device can be associated with the same second timer, or the second timer can be introduced with the multi-access device as the granularity. Taking the multi-access device associating a first terminal device and a second terminal device as an example, the first terminal device and the second terminal device can be associated with the same second timer, wherein the second timer is used to determine the time for implicit deregistration of the multi-access device. In some scenarios, the second timer can also be referred to as an "implicit deregistration timer."

[0242] It should be noted that when multiple terminal devices associated with a multi-access device are associated with the same second timer, it can be understood that the multiple terminal devices are each associated with an independent second timer, and the time periods indicated by these second timers are the same. Of course, in the embodiment of the present application, multiple terminal devices associated with the multi-access device are associated with one second timer, or in other words, the multiple terminal devices associated with the multi-access device share one second timer.

[0243] In some implementations, the value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

[0244] In some implementations, the value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device. The start time of the second timer associated with the first terminal device is the time when the paging of the first terminal device fails, and the start time of the second timer associated with the second terminal device is the time when the paging of the second terminal device fails. In other words, the second timer associated with the first terminal device and the second timer associated with the second terminal device are similar to traditional second timers.

[0245] In the embodiments of the present application, there is no limitation on the method for determining the value of the second timer associated with the multi-access device. In some implementations, the value of the second timer associated with the multi-access device can be set to the maximum value of the second timers of all terminal devices associated with the multi-access device. In other implementations, the value of the second timer associated with the multi-access device can be set to the minimum value of the second timers of all terminal devices associated with the multi-access device. In other implementations, the value of the second timer associated with the multi-access device can be set to the average value of the second timers of all terminal devices associated with the multi-access device.

[0246] In an embodiment of the present application, by introducing a second timer for a multi-access device, the terminal devices associated with the multi-access device can perform an implicit deregistration process based on the same second timer, which helps to avoid a terminal device being implicitly deregistered in advance, resulting in the inability to page the terminal device through other terminal devices, and helps to improve the success rate of paging terminal devices.

[0247] In some implementations, a multi-access device is associated with a first timer, which is used to determine whether the multi-access device is reachable. In other words, multiple terminal devices associated with the multi-access device can determine whether they are reachable based on the first timer. In some scenarios, the first timer can also be called a "mobility reachability timer."

[0248] In some implementations, the value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device. The start time of the first timer associated with the first terminal device is the time when the paging of the first terminal device fails, and the start time of the first timer associated with the second terminal device is the time when the paging of the second terminal device fails. In other words, the first timer associated with the first terminal device and the first timer associated with the second terminal device are similar to traditional first timers.

[0249] In the embodiments of the present application, there is no limitation on the method for determining the value of the first timer associated with the multi-access device. In some implementations, the value of the first timer associated with the multi-access device can be set to the maximum value of the first timers of all terminal devices associated with the multi-access device. In other implementations, the value of the first timer associated with the multi-access device can be set to the minimum value of the first timers of all terminal devices associated with the multi-access device. In other implementations, the value of the first timer associated with the multi-access device can be set to the average value of the first timers of all terminal devices associated with the multi-access device.

[0250] For ease of understanding, the second timer associated with the multi-access device in an embodiment of the present application is introduced below in conjunction with Figure 12. As shown in Figure 12, it is assumed that UE-1 and UE-2 are the first terminal device and the second terminal device associated with the multi-access device introduced above. At time t1, the multi-access device enters the idle state. At this time, the mobile reachable timer of the multi-access device is started, and when UE-1 and UE-2 cannot be paged, the implicit de-registration timer of the multi-access device is started. Afterwards, if the implicit de-registration timer of the multi-access device expires, UE-1 and UE-2 are de-registered.

[0251] In a multi-access scenario, data between terminal devices associated with a multi-access device can be transmitted between the associated terminal devices, which may cause the data of the terminal devices to be leaked, resulting in lower security. Taking the first terminal device and the second terminal device as an example, in a scenario where the paging of the second terminal device fails, the network device can send the downlink information of the second terminal device (for example, downlink data or downlink signaling) to the first terminal device, and the first terminal device forwards it to the second terminal device. In this scenario, the first terminal device may not actually belong to the same multi-access device as the second terminal device, which may cause the data of the second terminal device to be leaked.

[0252] For example, during air-interface communication between the second terminal device and the network device, the first terminal device may obtain the identifier of the second terminal device and apply to the network device to associate the second terminal device and the first terminal device as the same multi-access device. Afterwards, in a scenario where the paging of the second terminal device fails, the network device may send downlink information (e.g., downlink data or downlink signaling) of the second terminal device to the first terminal device, which will be forwarded by the first terminal device to the second terminal device, resulting in the leakage of data from the second terminal device to the first terminal device.

[0253] Therefore, to address the above issues, an embodiment of the present application provides a wireless communication method, in which a first core network element can determine whether a second terminal device and a first terminal device belong to the same multi-access device based on a subscription message from the second terminal device, thereby improving the security of data transmission in multi-access scenarios. The wireless communication method of an embodiment of the present application is described below in conjunction with Figure 13. The method shown in Figure 13 includes step S1310.

[0254] In step S1310, the first core network element determines whether the second terminal device and the first terminal device belong to the same multi-access device based on the subscription message of the second terminal device. The first core network element can be UDM or AMF.

[0255] In some implementations, the method further includes: the second core network element sending a subscription message of the second terminal device to the first core network element. For example, the first core network element is an AMF and the second core network element is a UDM.

[0256] In the embodiment of the present application, there is no limitation on how the first core network element obtains the subscription information of the second terminal device. In some implementations, the first core network element may subscribe to the subscription information of the second terminal device from the second core network element. That is, the first core network element sends a first request to the second core network element, where the first request is used to request subscription to the subscription information of the second terminal device.

[0257] In some implementations, the subscription information of the second terminal device may be determined based on the registration information of the second terminal device.

[0258] In some implementations, the subscription message of the second terminal device includes one or more of the following: information of the service AMF of the second terminal device; information of the multi-access device associated with the second terminal device; and information indicating whether the second terminal device supports being paged through other terminal devices.

[0259] Taking the service AMF information of the second terminal device as an example, that is, the information is used to indicate the service AMF of the second terminal device. For example, the information can be the identifier of the service AMF of the second terminal device.

[0260] Taking the information of the multi-access device associated with the second terminal device as an example, this information is used to indicate the multi-access device. For example, this information can be the identifier of the multi-access device. In some scenarios, this information can also be called a "dual steer device ID."

[0261] Taking information indicating whether the second terminal device supports paging via other terminal devices as an example, in some implementations, the other terminal devices are terminal devices other than the second terminal device in a multi-access device to which the second terminal device belongs. In other words, the information indicates whether the second terminal device supports paging via other terminal devices associated with the multi-access device to which it belongs.

[0262] In some scenarios, the above information can also be referred to as a dual paging capability indication. Of course, in the embodiment of the present application, the information is also used to indicate whether the second terminal device supports paging other terminal devices, or in other words, the information is used to indicate whether the second terminal device supports paging other terminal devices associated with the multi-access device to which it belongs.

[0263] In some implementations, if the second terminal device and the first terminal device belong to the same multi-access device, the above method also includes: the first core network network element sends third information to the first terminal device, and the third information is used to indicate that paging the second terminal device through the first terminal device is allowed.

[0264] In some implementations, if the second terminal device and the first terminal device do not belong to the same multi-access device, the above method also includes: the first core network network element sends third information to the first terminal device, and the third information is used to indicate a refusal to page the second terminal device through the first terminal device.

[0265] In some implementations, the third information is further used to indicate a reason for rejecting paging the second terminal device through the first terminal device.

[0266] In the embodiments of the present application, the above reasons are not limited. In some implementations, the reason may include that the first core network element does not support dual paging mode, where the dual paging mode may include simultaneously paging all terminal devices associated with the multi-access device and / or paging other terminal devices associated with the multi-access device by paging a terminal device of the multi-access device. In other implementations, the reason may include that the subscription message of the second terminal device is not authorized.

[0267] In some implementations, the third information is carried in a registration acceptance message of the second terminal device and / or a registration acceptance message of the first terminal device.

[0268] Taking the registration acceptance message in which the third information is carried by the second terminal device as an example, if the registration process of the first terminal device is performed before the registration process of the second terminal device, the first network device can first send a registration acceptance message to the first terminal device to reduce the time required for the first terminal device to register. At this time, the registration acceptance message of the first terminal device can indicate that paging the second terminal device through the first terminal device is allowed. Accordingly, the capability of the first terminal device is to support the dual paging mode. Afterwards, if the third information in the acceptance message of the second terminal device indicates that the first terminal device and the second terminal device belong to different multi-access devices, the first network device can update the capability of the first terminal device, that is, update the capability of the first terminal device from supporting the dual paging mode to not supporting the dual paging mode.

[0269] Of course, in this embodiment of the present application, the first terminal device may indicate in the registration acceptance message that it refuses to page the second terminal device through the first terminal device. Accordingly, the capability of the first terminal device is not to support the dual paging mode. Subsequently, if the third information in the acceptance message of the second terminal device indicates that the first terminal device and the second terminal device belong to the same multi-access device, the first network device may update the capability of the first terminal device, that is, update the capability of the first terminal device from not supporting the dual paging mode to supporting the dual paging mode.

[0270] In the embodiments of the present application, there is no limitation on how the first network device updates the capabilities of the first terminal device. In some implementations, the first network device may update the capabilities of the first terminal device through a UE configuration update process. For example, the first network device may send a UE configuration update message to the first terminal device to update the capabilities of the first terminal device.

[0271] In some implementations, if paging the second terminal device through the first terminal device is allowed, the above method also includes: in response to the occurrence of the first event, the first core network network element sends fourth information to the first terminal device, and the fourth information is used to indicate that paging the second terminal device through the first terminal device will be allowed, and is updated to deny paging the second terminal device through the first terminal device.

[0272] In the embodiments of the present application, the first event is not limited. In some implementations, the first event includes one or more of the following: the second terminal device is different from the multi-access device to which the first terminal device belongs; the third timer expires; the second terminal device does not support being paged through other terminal devices, where the other terminal devices are terminal devices other than the second terminal device in the multi-access device to which the second terminal device belongs.

[0273] In some implementations, if the second terminal device is a different multi-access device than the first terminal device, indicating that the first event has occurred, the first core network element may send fourth information to the first terminal device, indicating that the paging of the second terminal device via the first terminal device has been updated to denying paging of the second terminal device via the first terminal device. In other words, the capability of the first terminal device is updated from supporting dual paging mode to not supporting dual paging mode.

[0274] In some implementations, if the third timer times out, indicating that the first event has occurred, the first core network element may send fourth information to the first terminal device to indicate that paging the second terminal device through the first terminal device is allowed, and the paging capability of the second terminal device is updated to denying paging of the second terminal device through the first terminal device. In other words, the capability of the first terminal device is updated from supporting dual paging mode to not supporting dual paging mode.

[0275] In some implementations, the third timer is used to determine a waiting time for obtaining the subscription message from the second terminal device. Alternatively, the third timer indicates a waiting time for obtaining the subscription message from the second terminal device. For example, if the third timer times out, it indicates that obtaining the subscription message from the second terminal device has failed.

[0276] In some implementations, the start time of the third timer can be determined based on the sending time of the above-mentioned first request. For example, in response to the first core network network element sending the first request to the second core network network element, the third timer is started. That is to say, when the first core network network element requests to subscribe to the contract information of the second terminal device through the first request, the third timer can be started. In other implementations, the start time of the third timer can be determined based on the sending time of the registration request of the first terminal device. For example, in response to the first core network network element receiving the registration request of the first terminal device, the third timer is started.

[0277] In some implementations, if the second terminal device does not support being paged via other terminal devices, indicating that the first event has occurred, the first core network element may send fourth information to the first terminal device to indicate that paging the second terminal device via the first terminal device is allowed, and the permission is updated to denying paging the second terminal device via the first terminal device. In other words, the capability of the first terminal device is updated from supporting dual paging mode to not supporting dual paging mode.

[0278] In some implementations, the aforementioned other terminal devices may be other terminal devices other than the second terminal device in the multi-access device to which the second terminal device belongs.

[0279] For ease of understanding, the following describes a scheme for performing a dual paging mode on a multi-access device according to an embodiment of the present application in conjunction with Figure 14. Assume that the first terminal device is UE-1, and the access network serving UE-1 is AN-1, and the AMF serving UE-1 is AMF-1. The second terminal device is UE-2, and the access network serving UE-2 is AN-2, and the AMF serving UE-2 is AMF-2. The method shown in Figure 14 includes steps S1410 to S1480.

[0280] In step S1410, UE-1 sends a registration request 1 to AMF-1.

[0281] In some implementations, Registration Request 1 is sent to AMF-1 via AN-1.

[0282] In some implementations, registration request 1 includes one or more of the following: UE-1 identification information; identification information of UE-2 associated with UE-1; first capability information, wherein the first capability information is used to indicate the ability of UE-1 to support dual paging mode, for details, please refer to the introduction below.

[0283] In step S1420, AMF-1 interacts with UDM to obtain the subscription information of UE-1.

[0284] In some implementations, AMF-1 determines whether dual paging mode is supported for UE-1 and UE-2 based on local configuration and / or UE-1's subscription message. For example, AMF-1 queries the subscription message to determine whether UE-1 is associated with UE-2, and whether UE-1 and UE-2 support dual paging mode. If AMF-1 confirms that UE-1 is associated with UE-2, and that UE-1 and UE-2 support dual paging mode, then AMF-1 confirms that dual paging mode is supported for UE-1 and UE-2. At this time, one or more of the following information may be stored in the UDM: UE-1 identity, UE-2 identity, identity of the AMF-1 serving UE-1, and whether AMF-1 supports multi-paging mode.

[0285] In some implementations, AMF-1 subscribes to the UDM for the registration information of UE-2 and starts a third timer.

[0286] In some implementations, AMF-1 will also allocate an identity GUTI-1 for paging to UE-1.

[0287] In step S1430, AMF-1 sends a registration accept message to UE-1.

[0288] In some implementations, the registration accept message may include at least one of the following information: GUTI-1: identification information used to page UE-1; information used to indicate whether a dual paging mode is supported.

[0289] In some implementations, if the dual paging mode is not supported, the registration acceptance message may indicate the reason why the dual paging mode is not supported. For example, the reason may include unauthorized subscription message, unsupported AMF-1 function, etc.

[0290] In step S1440, UE-2 sends a Registration Request 2 to AMF-2.

[0291] In some implementations, Registration Request 2 is sent to AMF-2 via AN-2.

[0292] In some implementations, registration request 2 includes one or more of the following: UE-2 identification information; identification information of UE-1 associated with UE-2; first capability information, wherein the first capability information is used to indicate the ability of UE-2 to support dual paging mode, for details, please refer to the introduction below.

[0293] In step S1450, AMF-2 interacts with UDM to obtain the subscription information of UE-2.

[0294] In some implementations, AMF-2 queries the subscription message to determine whether UE-1 is associated with UE-2 and whether UE-1 and UE-2 support dual paging mode. If AMF-2 confirms that UE-1 is associated with UE-2 and that UE-1 and UE-2 support dual paging mode, then AMF-2 confirms that dual paging mode is supported for UE-1 and UE-2. At this time, one or more of the following information may be stored in the UDM: UE-1 identity, UE-2 identity, identity of the AMF-1 serving UE-1, and whether AMF-1 supports multi-paging mode.

[0295] In some implementations, since AMF-1 subscribes to UE-2's registration information, when UE-2 completes registration, UDM sends UE-2's registration message to AMF-1.

[0296] In some implementations, AMF-2 will also allocate an identifier GUTI-2 for paging to UE-2, where GUTI-1 and GUTI-2 can be the same identifier information.

[0297] In step S1460, AMF-2 sends a registration accept message to UE-2.

[0298] In some implementations, the registration accept message includes one or more of the following information: GUTI-2: identification information used to page UE-2; information used to indicate whether the dual paging mode is supported.

[0299] In some implementations, if the dual paging mode is not supported, the registration acceptance message may indicate the reason why the dual paging mode is not supported. For example, the reason may include unauthorized subscription message, unsupported AMF-2 function, etc.

[0300] In step S1470, since AMF-1 subscribes to the changes in UE-2 registration information in UDM, UDM notifies AMF-1 of UE-2's registration information (for example, UE-2's serving AMF-2 identifier, UE-2's dual paging mode capability indication, UE-2's associated UE identifier, etc.).

[0301] In step S1480, if the first event is met, AMF-1 sends a capability update message to UE-1 to update (or cancel) the dual paging capability configuration of UE-1. The capability update message can be executed by the UE configuration update process.

[0302] In some implementations, the first event includes one or more of the following: the notification message in step S1470 is not sent to AMF-1 before the third timer expires; the notification message in step S1470 indicates that UE-1 is not an associated UE of UE-2; UE-2 does not support dual paging mode.

[0303] It should be noted that UE-1 can be a primary UE in a multi-access device, and UE-2 can be a secondary UE in a multi-access device, that is, the primary UE initiates the registration process first. Of course, in the embodiment of the present application, the primary UE and the secondary UE may not be distinguished.

[0304] It should also be noted that Figure 14 describes the situation where UE-1 and UE-2 complete registration through different AMFs. In some scenarios, UE-1 and UE-2 can access the network through the same AMF (for example, AMF-1). In this case, AMF-1 does not need to subscribe to the registration status associated with UE-2 in the UDM, and AMF-1 can start a third timer locally to monitor whether UE-2 initiates registration and whether UE-2 supports dual paging mode capability indication.

[0305] It should also be noted that in the scheme shown in Figure 14, AMF-1 may not carry the information of supporting dual paging mode in the registration acceptance message of UE-1, wait for UE-2 to complete the registration, and carry the indication of UE-2's ability to support dual paging mode in the registration message, and then AMF-1 updates UE-1's dual paging mode capability to support dual paging mode through the UE configuration update process.

[0306] In an embodiment of the present application, the subscription data in the UDM is used to assist AMF-1 in confirming the association relationship between UE-1 and UE-2, and whether the dual paging mode is supported for UE-1 and UE-2. UE-1 and UE-2 respectively negotiate capabilities with the network side through the registration process, which can effectively avoid UE-1 obtaining the identification information of UE-2 by monitoring the information interaction between UE-2 and the network side, and carrying the identification of an unassociated UE-2 or the identification of UE-2 that does not support the dual paging mode in the registration message to negotiate with the network, ultimately causing UE-2 data leakage.

[0307] As described above, in a multi-access scenario, data between terminal devices associated with a multi-access device can be transmitted between the associated terminal devices, which may cause the data of the terminal devices to be leaked, resulting in lower security.

[0308] Therefore, to address the above issues, an embodiment of the present application further provides a wireless communication method, in which a second terminal device can confirm permission or rejection of paging a first terminal device through the second terminal device, or in other words, the second terminal device can confirm whether to authorize paging the first terminal device through the second terminal device, thereby helping to improve the security of data transmission in multi-access scenarios. The wireless communication method of an embodiment of the present application is described below in conjunction with Figure 15. The method shown in Figure 15 includes step S1510.

[0309] In step S1510, the first core network element sends a fifth message to the second terminal device. The fifth message is used to request the second terminal device to confirm whether to allow or deny paging the first terminal device through the second terminal device. In other words, the fifth message is used to request the second terminal device to confirm whether to authorize paging the first terminal device through the second terminal device. In other words, the fifth message is used to request the second terminal device to confirm whether to authorize entering a dual paging mode with the first terminal device. The dual paging mode can be described above. Therefore, in some scenarios, the fifth message can also be called an authorization request.

[0310] In some implementations, the first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to the same multi-access device, wherein the introduction to the multi-access device can be found above.

[0311] In some implementations, the fifth information is used to indicate one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; and whether the second terminal device supports paging the first terminal device via the second terminal device. The identifier of the first terminal device and / or the identifier of the second terminal device can be found in the above description.

[0312] In some implementations, the information used to indicate that the first terminal device supports paging of the first terminal device through the second terminal device can also be called "dual paging indication", that is, the information is used to indicate whether the first terminal device supports the dual paging mode. For the introduction to the dual paging mode, please refer to the above.

[0313] In some implementations, the first core network element provides services for the first terminal device (for example, the first core network element may be the service AMF for the first terminal device), and the second core network element serves the second terminal device (for example, the second core network element may be the service AMF for the second terminal device). Accordingly, the fifth information is sent from the first core network element to the second terminal device via the second core network element. In other implementations, the first core network element may serve both the first terminal device and the second terminal device at the same time. In this case, the first core network element may send the fifth information directly to the second terminal device.

[0314] In some implementations, the method further includes: the first core network element receiving, in response to the fifth information sent by the second terminal device, the response information indicating whether the second terminal device permits or denies paging the first terminal device through the second terminal device, or in other words, indicating whether the second terminal device authorizes paging the first terminal device through the second terminal device. In some scenarios, this response message is also referred to as an "authorization response message."

[0315] In some implementations, the response information indicates one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; and whether the second terminal device allows or denies paging the first terminal device through the second terminal device. The identifier information of the first terminal device and / or the identifier information of the second terminal device can be found in the previous description.

[0316] In some implementations, the information indicating whether the second terminal device allows or denies paging the first terminal device through the second terminal device may also be referred to as an "authorization result." Alternatively, the information indicates whether the second terminal device allows or denies entering dual paging mode with the first terminal device.

[0317] In some implementations, the first core network element provides services for the first terminal device (for example, the first core network element can be the service AMF for the first terminal device), and the second core network element serves the second terminal device (for example, the second core network element can be the service AMF for the second terminal device). Accordingly, the response information is sent from the first core network element to the second terminal device via the second core network element. In other implementations, the first core network element can serve both the first terminal device and the second terminal device at the same time. In this case, the first core network element can directly send the response information to the second terminal device.

[0318] In some implementations, if the second terminal device allows paging of the first terminal device through the second terminal device, the method also includes: the first core network network element sends sixth information to the first terminal device, and the sixth information is used to indicate that the second terminal device allows paging of the first terminal device through the second terminal device.

[0319] In some implementations, if the second terminal device refuses to page the first terminal device through the second terminal device, the method further includes: the first core network network element sends sixth information to the first terminal device, and the sixth information is used to indicate that the second terminal device refuses to page the first terminal device through the second terminal device.

[0320] In the embodiments of the present application, there is no limitation on the scheme by which the second terminal device allows or refuses to page the first terminal device through the second terminal device. In some implementations, the second terminal device may be determined based on the multi-access device to which the first terminal device belongs. For example, if the second terminal device and the first terminal device belong to the same multi-access device, the second terminal device may allow the first terminal device to be paged through the second terminal device. For another example, if the second terminal device and the first terminal device belong to different multi-access devices, the second terminal device may refuse to page the first terminal device through the second terminal device.

[0321] In some implementations, the fifth information is carried in a registration request message of the first terminal device, and / or the sixth information is carried in a registration acceptance message of the first terminal device.

[0322] It should be noted that the above is introduced using the example of paging the first terminal device through the second terminal device. The solution of the embodiment of the present application can also be applied to the scenario of paging the second terminal device through the first terminal device. That is to say, the fifth information can be used to request the second terminal device to confirm whether to allow or refuse to paging the second terminal device through the first terminal device. Accordingly, the response message of the fifth information is used to indicate that the second terminal device allows or refuses to paging the second terminal device through the first terminal device. Of course, the embodiment of the present application can also be applied to the scenario of paging the first terminal device and the second terminal device at the same time. That is to say, the fifth information can be used to request the second terminal device to confirm whether to allow or refuse to paging the first terminal device and the second terminal device at the same time. Accordingly, the response message of the fifth information is used to indicate that the second terminal device allows or refuses to paging the second terminal device at the same time by the first terminal device.

[0323] For ease of understanding, the following describes, in conjunction with Figure 16, a method for the second terminal device to determine whether to authorize the dual paging mode in an embodiment of the present application. Assume that the first terminal device is UE-1, and the access network serving UE-1 is AN-1, and the AMF serving UE-1 is AMF-1. The second terminal device is UE-2, and the access network serving UE-2 is AN-2, and the AMF serving UE-2 is AMF-2. The method shown in Figure 16 includes steps S1610 to S1670.

[0324] In step S1610, UE-1 sends a registration request 1 to AMF-1.

[0325] In some implementations, Registration Request 1 is sent to AMF-1 via AN-1.

[0326] In some implementations, registration request 1 includes one or more of the following: UE-1 identification information; identification information of UE-2 associated with UE-1; first capability information, wherein the first capability information is used to indicate the ability of UE-1 to support dual paging mode, for details, please refer to the introduction below.

[0327] In step S1620, AMF-1 interacts with UDM to obtain the subscription information of UE-1 and UE-2.

[0328] In some implementations, the AMF-1 may determine whether the network supports the dual paging mode based on the local configuration and subscription information. If not, step S1660 is directly executed, and the registration acceptance message includes the reason why the dual paging mode is not supported and / or the network rejects the dual paging mode (i.e., the network does not support the dual paging mode).

[0329] In step S1630, AMF-1 sends an authorization request message to AMF-2.

[0330] In some implementations, the authorization request message includes at least one of the following parameters: identification information of UE-1; identification information of UE-2; first capability information (dual paging indication);

[0331] In step S1640, AMF-2 forwards the authorization request message to UE-2.

[0332] It should be noted that if the AMF serving UE-1 and UE-2 is the same AMF, then this AMF sends an authorization request message to UE-2.

[0333] In step S1650, UE-2 sends an authorization response message to AMF-1.

[0334] In some implementations, the authorization message includes at least one of the following information: authorization result: whether the network is authorized to perform dual paging mode on UE-2 and the associated UE-1; UE-1 identification information; UE-2 identification information;

[0335] In step S1660, AMF-1 determines whether to support the dual paging mode requested by UE-1 based on the authorization result fed back by UE-2, and returns a registration acceptance message.

[0336] It should be noted that the authorization request can also be initiated by UDM, and after receiving the authorization result, the authorization result will be returned to AMF-1.

[0337] In the embodiment of the present application, when the network receives a request from UE-1 for dual paging capability negotiation, it can proactively query its associated UE-2, obtain its authorization result, and then return the capability negotiation result to UE-1.

[0338] As technology advances, the number of terminal devices associated with a multi-access device may increase. In some scenarios, the communication devices (e.g., the first device and the second device) may need to transmit the identifiers of all terminal devices, resulting in high information transmission overhead. For example, in the dual paging mode described above, when a network device sends a paging message to a terminal device, it typically needs to carry the identifiers of all terminal devices, resulting in high transmission overhead.

[0339] Therefore, to address the above issues, in an embodiment of the present application, a new identifier, namely a first identifier, is introduced for a multi-access device. This first identifier can identify the terminal device associated with the multi-access device by identifying the multi-access device. Compared to traditional solutions that transmit the identifiers of all terminal devices, this helps reduce transmission overhead. The wireless communication method of an embodiment of the present application is described below with reference to FIG17 . The method shown in FIG17 includes step S1710.

[0340] In step S1710, the first device sends a first identifier to the second device, where the first identifier is used to identify the multi-access device. In some scenarios, the first identifier may also be referred to as a "dual steer device ID."

[0341] In some implementations, the multi-access device may include multiple terminal devices, for example, a first terminal device and a second terminal device.

[0342] In some implementations, the first identifier is used to page the terminal device associated with the multi-access device. For example, the first identifier is used to page the first terminal device and / or the second terminal device.

[0343] In some implementations, the first identifier is carried in a subscription message of the first terminal device, or the first identifier is allocated by the UDM.

[0344] In some implementations, the first device includes a UDM, and the second device includes an AMF serving the first terminal device.

[0345] In some implementations, the first device includes an AMF serving the first terminal device, and the second device includes the first terminal device.

[0346] In some implementations, the first identifier is carried in a registration accept message.

[0347] In some implementations, the registration accept message is further used to indicate permission or refusal to page the first terminal device and / or the second terminal device based on the first identifier. For example, the registration accept message is further used to indicate permission or refusal to page the first terminal device and / or the second terminal device in a dual paging mode based on the first identifier, where the dual paging mode can be described above.

[0348] In some implementations, the first device includes a first terminal device, and the second device includes a second terminal device.

[0349] In some implementations, the first device includes a second terminal device, and the second device includes an AMF serving the second terminal device.

[0350] In some implementations, the first identifier is carried in the registration request.

[0351] In some implementations, the first device includes an AMF serving the second terminal device, and the second device includes a UDM.

[0352] In some implementations, the first device includes an AMF serving the second terminal device, and the second device includes the second terminal device.

[0353] For ease of understanding, the following describes, in conjunction with Figure 18, a scheme for the first terminal device and the second terminal device associated with the multi-access device based on the first identification paging in an embodiment of the present application. Assume that the first terminal device is UE-1, and the access network serving UE-1 is AN-1, and the AMF serving UE-1 is AMF-1. The second terminal device is UE-2, and the access network serving UE-2 is AN-2, and the AMF serving UE-2 is AMF-2. The method shown in Figure 18 includes steps S1810 to S1880.

[0354] In step S1810, UE-1 sends a Registration Request 1 to AMF-1.

[0355] In some implementations, Registration Request 1 is sent to AMF-1 via AN-1.

[0356] In some implementations, the registration request 1 includes one or more of the following: UE-1 identification information; first capability information, wherein the first capability information is used to indicate the capability of UE-1 to support the dual paging mode, as described below for details.

[0357] In steps S1820a to S1820b, AMF-1 interacts with UDM to obtain the subscription information of UE-1 and UE-2.

[0358] In some implementations, AMF-1 determines whether to support dual paging mode for UE-1 and UE-2 based on local configuration and / or UE-1's subscription message. For example, AMF-1 can send UE-1's identification information and / or first capability information to UDM (see S1820a). UDM sends UE-1's subscription message and / or multi-access device ID to AMF-1 (see S1820b). The multi-access device ID can be the content in the subscription message or dynamically allocated by UDM, and is mainly used for paging multiple associated UEs, or paging multiple UEs associated with the multi-access device.

[0359] In step S1830, AMF-1 sends a registration accept message to UE-1.

[0360] In some implementations, the registration acceptance message may include a multi-access device ID (this identification information may be encrypted using UE-1's security key when sent to UE-1); information indicating whether the dual paging mode is supported; and the reason for rejecting the dual paging mode (e.g., the subscription message is not authorized, the AMF function is not supported, etc.).

[0361] In step S1840, UE-1 sends the multi-access device ID to UE2.

[0362] In some implementations, after receiving the encrypted multi-access device ID, UE-1 decrypts it using a security key and sends the decrypted multi-access device ID to the associated UE-2.

[0363] In step S1850, UE-2 sends a Registration Request 2 to AMF-2.

[0364] In some implementations, the Registration Request 2 is sent to the AMF-1 via AN-1.

[0365] In some implementations, the registration request 2 includes one or more of the following: UE-2 identification information; first capability information (dual paging indication): used to indicate the capability of UE-2 to support dual paging; multi-access device ID: the multi-access device ID can be encrypted using the secret key of UE-2.

[0366] In step S1860, AMF-2 interacts with UDM to obtain the subscription information of UE-2.

[0367] In some implementations, AMF-2 determines whether to support dual paging mode for UE-1 and UE-2 based on local configuration and / or UE-2's subscription message. AMF-2 can obtain a subscription message related to the multi-access device ID from the UDM to determine whether to perform dual paging mode on UE-2 and whether to use the multi-access device ID to page UE-1 and UE-2. For example, AMF-2 queries the UDM whether the subscription message indicates that UE-1 and UE-2 are associated UEs, whether UE-1 and UE-2 support dual paging mode, and whether UE-1 and UE-2 can use the same multi-access device ID for paging.

[0368] In step S1870, AMF-2 sends a registration accept message to UE-2.

[0369] In some implementations, the registration accept message includes at least one of the following information: multi-access device ID: identification information used to paging UE-2; the identification information is encrypted with the security key of UE-2 when sent to UE-2; if the AMF confirms that dual paging is supported, this parameter is included; information used to indicate that the dual paging mode is supported; information used to indicate that the dual paging mode is not supported, and / or the reason why the network rejects the dual paging mode (for example, the contract message is not authorized, the AMF function is not supported, etc.).

[0370] In an embodiment of the present application, the network in the UDM can assign the same multi-access device identifier to all UEs associated with the multi-access device for paging. At this time, if the network adopts an enhanced paging strategy, it can only page the UE to which the network has assigned the multi-access device identifier, thereby isolating each UE from the network negotiation process, avoiding the additional delay and signaling overhead during multi-party capability negotiation caused by the increase in the number of associated UEs.

[0371] With the development of technology, the types of terminal devices connected to the communication system are increasing. The capabilities of different terminal devices may be slightly different. If these differences are ignored and the terminal devices are directly paged, the paging method used by the terminal devices may be less reasonable.

[0372] Therefore, to address the above issues, first capability information is introduced in an embodiment of the present application to indicate whether a terminal device associated with a multi-access device supports paging through other terminal devices associated with the access device. Taking the multi-access device as an example of a first terminal device and a second terminal device being associated with the multi-access device, the first capability information is used to indicate whether the second terminal device supports paging through the first terminal device, which helps to improve the rationality of paging the second terminal device. The following describes the transmission method of the first capability information in an embodiment of the present application in conjunction with Figure 19. The method shown in Figure 16 includes step S1910.

[0373] In step S1910 , the first device sends first capability information to the second device.

[0374] In some implementations, the first capability information is used to indicate whether the second terminal device supports paging through the first terminal device. In other implementations, the first capability information is used to indicate whether the second terminal device supports paging the first terminal device through the second terminal device. Of course, in an embodiment of the present application, the first capability information may also be used to indicate whether the second terminal device supports simultaneous paging of all terminal devices associated with the multi-access device.

[0375] In some scenarios, the first capability information may also be referred to as "dual paging capability".

[0376] In some implementations, the first capability information is carried in a registration request of the first terminal device. In other implementations, the first capability information is carried in a registration request that can be carried in a second terminal device. For example, the transmission method of the first capability information can be referred to the above description of FIG. 19.

[0377] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 19 . The device embodiment of the present application is described in detail below in conjunction with Figures 20 to 35 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for portions not described in detail, reference can be made to the above method embodiment.

[0378] FIG20 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 2000 shown in FIG20 is a first terminal device, and the terminal device 2000 includes a receiving unit 2010 .

[0379] The receiving unit 2010 is used to receive the first information sent by the second terminal device, where the first information includes one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; downlink information to be transmitted to the first terminal device; wherein the first terminal device and the second terminal device are multi-access devices.

[0380] In some implementations, if the first information includes the second paging message, the receiving unit is configured to receive the first information sent by the second terminal device when paging of the first terminal device fails.

[0381] In some implementations, the reason for the paging failure of the first terminal device is associated with one or more of the following: mobility of the first terminal device; mobility of a network device providing services to the first terminal device.

[0382] In some implementations, the second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, wherein the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; and second indication information, wherein the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

[0383] In some implementations, the second indication information is used to indicate that paging the first terminal device failed.

[0384] In some implementations, a second timer associated with the first terminal device is different from a second timer associated with the second terminal device, and the second timer is used to determine an implicit deregistration time of the associated terminal device.

[0385] In some implementations, the start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or the time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

[0386] In some implementations, the first paging message includes one or more of the following: identification information associated with the first terminal device; and first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

[0387] In some implementations, the identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

[0388] In some implementations, the multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

[0389] In some implementations, the value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

[0390] In some implementations, the multi-access device is associated with a second timer, and the second timer is used to determine a time for the multi-access device to implicitly deregister.

[0391] In some implementations, the value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

[0392] FIG21 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 2100 shown in FIG21 is a second terminal device, and the terminal device 2100 includes: a receiving unit 2110 .

[0393] The receiving unit 2110 is used to receive first information sent by a second network device, where the second terminal device and the first terminal device belong to the same multi-access device, wherein the first information includes one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; and downlink information to be transmitted to the first terminal device.

[0394] In some implementations, if the first information includes the second paging message, the receiving unit is configured to receive the first information sent by the second network device when paging of the first terminal device fails.

[0395] In some implementations, the reason for the paging failure of the first terminal device is associated with one or more of the following: mobility of the first terminal device; mobility of a network device providing services to the first terminal device.

[0396] In some implementations, the second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, wherein the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; and second indication information, wherein the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

[0397] In some implementations, the second indication information is used to indicate that paging the first terminal device failed.

[0398] In some implementations, a second timer associated with the first terminal device is different from a second timer associated with the second terminal device, and the second timer is used to determine an implicit deregistration time of the associated terminal device.

[0399] In some implementations, the start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or the time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

[0400] In some implementations, the first paging message includes one or more of the following: identification information associated with the first terminal device; and first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

[0401] In some implementations, the identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

[0402] In some implementations, the multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

[0403] In some implementations, the value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

[0404] In some implementations, the multi-access device is associated with a second timer, and the second timer is used to determine a time for the multi-access device to implicitly deregister.

[0405] In some implementations, the value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

[0406] In some implementations, the receiving unit is used to receive the first information sent by the first terminal device.

[0407] Figure 22 is a schematic diagram of a network device according to an embodiment of the present application, wherein the network device 2200 is a second network device, and the network device 2200 includes: a sending unit 2210.

[0408] The sending unit 2210 is used to send first information to a second terminal device, where the second terminal device and the first terminal device belong to the same multi-access device, wherein the first information includes one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; and downlink information to be transmitted to the first terminal device.

[0409] In some implementations, if the first information includes the second paging message, the sending unit is configured to send the first information to the second terminal device if paging of the first terminal device fails.

[0410] In some implementations, the reason for the paging failure of the first terminal device is associated with one or more of the following: mobility of the first terminal device; mobility of a network device providing services to the first terminal device.

[0411] In some implementations, the second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, wherein the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; and second indication information, wherein the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

[0412] In some implementations, the second indication information is used to indicate that paging the first terminal device failed.

[0413] In some implementations, a second timer associated with the first terminal device is different from a second timer associated with the second terminal device, and the second timer is used to determine an implicit deregistration time of the associated terminal device.

[0414] In some implementations, the start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or the time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

[0415] In some implementations, the first paging message includes one or more of the following: identification information associated with the first terminal device; and first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

[0416] In some implementations, the identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

[0417] In some implementations, the multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

[0418] In some implementations, the value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

[0419] In some implementations, the multi-access device is associated with a second timer, and the second timer is used to determine a time for the multi-access device to implicitly deregister.

[0420] In some implementations, the value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

[0421] In some implementations, the network device further includes a receiving unit configured to receive second information sent by the first network device, where the second information is configured to trigger the second network device to send the first information.

[0422] Figure 23 is a schematic diagram of a network device according to an embodiment of the present application. The network device 2300 is a first network device, and the network device 2300 includes: a sending unit 2310.

[0423] The sending unit 2310 is used to send second information to the second network device, where the second information is used to trigger the second network device to send first information, wherein the first information includes one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; downlink information to be transmitted to the first terminal device; wherein the first terminal device and the second terminal device are multi-access devices.

[0424] In some implementations, if the first information includes the second paging message, the sending unit is configured to send the first information to the second terminal device if paging of the first terminal device fails.

[0425] In some implementations, the reason for the paging failure of the first terminal device is associated with one or more of the following: mobility of the first terminal device; mobility of a network device providing services to the first terminal device.

[0426] In some implementations, the second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, wherein the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; and second indication information, wherein the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

[0427] In some implementations, the second indication information is used to indicate that paging the first terminal device failed.

[0428] In some implementations, a second timer associated with the first terminal device is different from a second timer associated with the second terminal device, and the second timer is used to determine an implicit deregistration time of the associated terminal device.

[0429] In some implementations, the start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or the time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

[0430] In some implementations, the first paging message includes one or more of the following: identification information associated with the first terminal device; and first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

[0431] In some implementations, the identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

[0432] In some implementations, the multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

[0433] In some implementations, the value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

[0434] In some implementations, the multi-access device is associated with a second timer, and the second timer is used to determine a time for the multi-access device to implicitly deregister.

[0435] In some implementations, the value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

[0436] In some implementations, the network device further includes: a receiving unit, configured to receive second information sent by the first network device, where the second information is used to trigger the second network device to send the first information.

[0437] FIG24 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 2400 shown in FIG24 is a first terminal device, and the terminal device 2400 includes a receiving unit 2410 .

[0438] The receiving unit 2410 is used to receive the first information sent by the second terminal device, where the first information includes one or more of the following: a first paging message for paging the first terminal device and the second terminal device; a second paging message for paging the first terminal device; downlink information to be transmitted to the first terminal device; wherein the first terminal device and the second terminal device are multi-access devices.

[0439] In some implementations, if the first information includes the second paging message, the receiving unit is configured to receive the first information sent by the second terminal device when paging of the first terminal device fails.

[0440] In some implementations, the reason for the paging failure of the first terminal device is associated with one or more of the following: mobility of the first terminal device; mobility of a network device providing services to the first terminal device.

[0441] In some implementations, the second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, wherein the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; and second indication information, wherein the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

[0442] In some implementations, the second indication information is used to indicate that paging the first terminal device failed.

[0443] In some implementations, a second timer associated with the first terminal device is different from a second timer associated with the second terminal device, and the second timer is used to determine an implicit deregistration time of the associated terminal device.

[0444] In some implementations, the start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or

[0445] The time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

[0446] In some implementations, the first paging message includes one or more of the following: identification information associated with the first terminal device; and first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

[0447] In some implementations, the identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

[0448] In some implementations, the multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

[0449] In some implementations, the value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

[0450] In some implementations, the multi-access device is associated with a second timer, and the second timer is used to determine a time for the multi-access device to implicitly deregister.

[0451] In some implementations, the value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

[0452] Figure 25 is a schematic diagram of a network device according to an embodiment of the present application. The network device 2500 shown in Figure 25 is a first core network element. The network device 2500 includes: a processing unit 2510.

[0453] The processing unit 2510 is configured to determine, based on a subscription message of the second terminal device, whether the second terminal device and the first terminal device belong to the same multi-access device.

[0454] In some implementations, the network device further includes: a receiving unit, configured to receive a signing message of the second terminal device sent by a second core network network element.

[0455] In some implementations, the signing message of the second terminal device includes one or more of the following: information of the service AMF of the second terminal device; information of the multi-access device associated with the second terminal device; information used to indicate whether the second terminal device supports being paging through other terminal devices, wherein the other terminal devices are other terminal devices in the multi-access device to which the second terminal device belongs except the second terminal device.

[0456] In some implementations, the network device further includes: a first sending unit, configured to send a first request to the second core network element, wherein the first request is used to request subscription to the contract information of the second terminal device.

[0457] In some implementations, if the second terminal device and the first terminal device belong to the same multi-access device, the network device also includes: a second sending unit, used to send third information to the first terminal device, and the third information is used to indicate that paging the second terminal device through the first terminal device is allowed.

[0458] In some implementations, if the second terminal device and the first terminal device do not belong to the same multi-access device, the network device also includes: a third sending unit, used to send third information to the first terminal device, and the third information is used to indicate a refusal to page the second terminal device through the first terminal device.

[0459] In some implementations, the third information is used to indicate a reason for rejecting paging the second terminal device through the first terminal device.

[0460] In some implementations, the third information is carried in a registration acceptance message of the second terminal device and / or a registration acceptance message of the first terminal device.

[0461] In some implementations, if paging the second terminal device through the first terminal device is allowed, the network device also includes: in response to the occurrence of a first event, a fourth sending unit, used to send fourth information to the first terminal device, the fourth information being used to indicate that paging the second terminal device through the first terminal device will be allowed, and updated to denying paging the second terminal device through the first terminal device.

[0462] In some implementations, the fourth information is carried in a UE configuration update message.

[0463] In some implementations, the first event includes one or more of the following: the second terminal device is different from the multi-access device to which the first terminal device belongs; a third timer times out, and the third timer is used to determine the waiting time for obtaining the signing message of the second terminal device; the second terminal device does not support being paged through other terminal devices, wherein the other terminal devices are other terminal devices in the multi-access device to which the second terminal device belongs except the second terminal device.

[0464] In some implementations, the start of the third timer is triggered based on a first request or a registration request of the first terminal device, wherein the first request is used by the first core network element to request to subscribe to a subscription message of the second terminal device.

[0465] FIG26 is a schematic diagram of a network device according to an embodiment of the present application. The network device 2600 shown in FIG26 is a second core network element, and the network device 2600 includes a sending unit 2610 .

[0466] The sending unit 2610 is used to send a subscription message of the second terminal device to the first core network network element, where the subscription information of the second terminal device is used to determine whether the second terminal device and the first terminal device belong to the same multi-access device.

[0467] In some implementations, the signing message of the second terminal device includes one or more of the following: information of the service AMF of the second terminal device; information of the multi-access device associated with the second terminal device; information used to indicate whether the second terminal device supports being paging through other terminal devices, wherein the other terminal devices are other terminal devices in the multi-access device to which the second terminal device belongs except the second terminal device.

[0468] In some implementations, the network device further includes: a receiving unit, configured to receive a first request sent by the first core network element, where the first request is used to request subscription to the contract information of the second terminal device.

[0469] FIG27 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 2700 shown in FIG27 is a first terminal device, and the terminal device 2700 includes a receiving unit 2710 .

[0470] Receiving unit 2710 is used to receive the second information or the third information sent by the first core network network element, wherein the second information is used to indicate a refusal to paging the second terminal device through the first terminal device, and the third information is used to indicate that paging the second terminal device through the first terminal device will be allowed, which is updated to a refusal to paging the second terminal device through the first terminal device.

[0471] FIG28 is a schematic diagram of a network device according to an embodiment of the present application. The network device 2800 shown in FIG28 is a first core network element, and the network device 2800 includes a sending unit 2810 .

[0472] Sending unit 2810 is used to send fifth information to the second terminal device, where the fifth information is used to request the second terminal device to confirm whether to allow or refuse to paging the first terminal device through the second terminal device, wherein the first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

[0473] In some implementations, the fifth information is used to indicate one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; and support for paging the first terminal device through the second terminal device by the first terminal device.

[0474] In some implementations, the first core network element provides services for the first terminal device, and the fifth information is sent by the first core network element to the second terminal device via the second core network element, and the second core network element serves the second terminal device; or the first core network element serves both the first terminal device and the second terminal device.

[0475] In some implementations, the network device further includes: a receiving unit configured to receive response information to the fifth information sent by the second terminal device, wherein the response information is configured to indicate whether the second terminal device allows or refuses to page the first terminal device through the second terminal device.

[0476] In some implementations, the response information is used to indicate one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; and whether the second terminal device allows or refuses paging the first terminal device through the second terminal device.

[0477] In some implementations, the first core network element provides services for the first terminal device, and the response information is sent by the first core network element to the second terminal device via the second core network element, and the second core network element serves the second terminal device; or the first core network element serves both the first terminal device and the second terminal device.

[0478] In some implementations, if the second terminal device allows paging of the first terminal device through the second terminal device, the network device also includes: the sending unit, used to send sixth information to the first terminal device, and the sixth information is used to indicate that the second terminal device allows paging of the first terminal device through the second terminal device.

[0479] In some implementations, if the second terminal device refuses to page the first terminal device through the second terminal device, the network device further includes: the sending unit, used to send sixth information to the first terminal device, and the sixth information is used to indicate that the second terminal device refuses to page the first terminal device through the second terminal device.

[0480] In some implementations, the sixth information is carried in a registration acceptance message of the first terminal device.

[0481] In some implementations, the fifth information is carried in a registration request message of the first terminal device.

[0482] FIG29 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 2900 shown in FIG29 is a second terminal device, and the terminal device 2900 includes a receiving unit 2910 .

[0483] Receiving unit 2910 is used to receive the fifth information sent by the first core network network element, and the fifth information is used to request the second terminal device to confirm whether to allow or refuse to paging the first terminal device through the second terminal device, wherein the first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

[0484] In some implementations, the fifth information is used to indicate one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; and support for paging the first terminal device through the second terminal device by the first terminal device.

[0485] In some implementations, the first core network element provides services for the first terminal device, and the fifth information is sent by the first core network element to the second terminal device via the second core network element, and the second core network element serves the second terminal device; or the first core network element serves both the first terminal device and the second terminal device.

[0486] In some implementations, the terminal device further includes: the second terminal device sends response information of the fifth information to the first core network element, and the response information is used to indicate that the second terminal device allows or refuses to page the first terminal device through the second terminal device.

[0487] In some implementations, the response information is used to indicate one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; and whether the second terminal device allows or refuses paging the first terminal device through the second terminal device.

[0488] In some implementations, the first core network element provides services for the first terminal device, and the response information is sent by the first core network element to the second terminal device via the second core network element, and the second core network element serves the second terminal device; or the first core network element serves both the first terminal device and the second terminal device.

[0489] In some implementations, the fifth information is carried in a registration request message of the first terminal device.

[0490] FIG30 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 3000 shown in FIG30 is a first terminal device, and the terminal device 3000 includes: a receiving unit 3010 .

[0491] The receiving unit 3010 is used to receive the sixth information sent by the first core network network element, and the sixth information is used to indicate that the second terminal device allows or refuses to paging the first terminal device through the second terminal device, wherein the first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

[0492] In some implementations, if the first terminal device and the second terminal device belong to the same multi-access device, the sixth information is used to indicate that the second terminal device allows paging of the first terminal device through the second terminal device.

[0493] In some implementations, if the first terminal device and the second terminal device belong to different multi-access devices, the sixth information is used to instruct the second terminal device to refuse to page the first terminal device through the second terminal device.

[0494] In some implementations, the sixth information is carried in a registration acceptance message of the first terminal device.

[0495] FIG31 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 3100 shown in FIG31 is a first device, and the communication device 3100 includes a sending unit 3110 .

[0496] The sending unit 3110 is configured to send a first identifier to a second device, where the first identifier is used to identify a multi-access device, where the multi-access device includes a first terminal device and a second terminal device.

[0497] In some implementations, the first identifier is used to page the first terminal device and / or the second terminal device.

[0498] In some implementations, the first identifier is carried in a subscription message of the first terminal device, or the first identifier is allocated by UDM.

[0499] In some implementations, the first device includes a UDM, and the second device includes an AMF serving the first terminal device.

[0500] In some implementations, the first device includes an AMF serving the first terminal device, and the second device includes the first terminal device.

[0501] In some implementations, the first identifier is carried in a registration acceptance message.

[0502] In some implementations, the registration acceptance message is further used to indicate permission or rejection of paging the first terminal device and / or the second terminal device based on the first identifier.

[0503] In some implementations, the first device includes the first terminal device, and the second device includes the second terminal device.

[0504] In some implementations, the first device includes the second terminal device, and the second device includes an AMF serving the second terminal device.

[0505] In some implementations, the first identifier is carried in a registration request.

[0506] In some implementations, the first device includes an AMF serving the second terminal device, and the second device includes a UDM.

[0507] In some implementations, the first device includes an AMF serving the second terminal device, and the second device includes the second terminal device.

[0508] FIG32 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 3200 shown in FIG32 is a second device, and the communication device 3200 includes a receiving unit 3210 .

[0509] The receiving unit 3210 is configured to receive a first identifier sent by a first device, where the first identifier is used to identify a multi-access device, where the multi-access device includes a first terminal device and a second terminal device.

[0510] In some implementations, the first identifier is used to page the first terminal device and / or the second terminal device.

[0511] In some implementations, the first identifier is carried in a subscription message of the first terminal device, or the first identifier is allocated by UDM.

[0512] In some implementations, the first device includes a UDM, and the second device includes an AMF serving the first terminal device.

[0513] In some implementations, the first device includes an AMF serving the first terminal device, and the second device includes the first terminal device.

[0514] In some implementations, the first identifier is carried in a registration acceptance message.

[0515] In some implementations, the registration acceptance message is further used to indicate permission or rejection of paging the first terminal device and / or the second terminal device based on the first identifier.

[0516] In some implementations, the first device includes the first terminal device, and the second device includes the second terminal device.

[0517] In some implementations, the first device includes the second terminal device, and the second device includes an AMF serving the second terminal device.

[0518] In some implementations, the first identifier is carried in a registration request.

[0519] In some implementations, the first device includes an AMF serving the second terminal device, and the second device includes a UDM.

[0520] In some implementations, the first device includes an AMF serving the second terminal device, and the second device includes the second terminal device.

[0521] FIG33 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 3300 shown in FIG33 is a first device, and the communication device 3300 includes a sending unit 3310 .

[0522] The sending unit 3310 is used to send first capability information to the second device, where the first capability information is used to indicate whether the second terminal device supports paging through the first terminal device, and the first terminal device and the second terminal device are multi-access devices.

[0523] In some implementations, the first capability information is carried in a registration request of the first terminal device; and / or a registration request of the second terminal device.

[0524] FIG34 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device 3400 shown in FIG34 is a second device, and the communication device 3400 includes a receiving unit 3410 .

[0525] The receiving unit 3410 is used to receive first capability information sent by a first device, where the first capability information is used to indicate whether a second terminal device supports paging through the first terminal device, and the first terminal device and the second terminal device are multi-access devices.

[0526] In some implementations, the first capability information is carried in a registration request of the first terminal device; and / or a registration request of the second terminal device.

[0527] Figure 35 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 35 indicate that the unit or module is optional. The device 3500 may be used to implement the method described in the above method embodiment. The device 3500 may be a chip, a terminal device, or a network device.

[0528] The device 3500 may include one or more processors 3510. The processor 3510 may support the device 3500 to implement the method described in the method embodiment above. The processor 3510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0529] The apparatus 3500 may further include one or more memories 3520. The memories 3520 store programs that can be executed by the processor 3510, causing the processor 3510 to perform the methods described in the above method embodiments. The memories 3520 may be independent of the processor 3510 or integrated into the processor 3510.

[0530] The apparatus 3500 may further include a transceiver 3530. The processor 3510 may communicate with other devices or chips via the transceiver 3530. For example, the processor 3510 may transmit and receive data with other devices or chips via the transceiver 3530.

[0531] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0532] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0533] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0534] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0535] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0536] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0537] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0538] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0539] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0540] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0541] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0542] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

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

[0545] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

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

Claims

1. A wireless communication method, characterized in that: include: The first terminal device receives first information sent by the second terminal device, where the first information includes one or more of the following: A first paging message used to page the first terminal device and the second terminal device; a second paging message for paging the first terminal device; Downlink information to be transmitted to the first terminal device; Among them, the first terminal device and the second terminal device are multi-access devices.

2. The method according to claim 1, wherein If the first information includes the second paging message, the first terminal device receives the first information sent by the second terminal device, including: In the event that paging of the first terminal device fails, the first terminal device receives the first information sent by the second terminal device.

3. The method according to claim 2, wherein The reason why the paging failure of the first terminal device is related to one or more of the following: mobility of the first terminal device; Mobility of the network device providing services for the first terminal device.

4. The method according to any one of claims 1 to 3, wherein The second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; Second indication information, where the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

5. The method according to claim 4, wherein The second indication information is used to indicate that paging the first terminal device has failed.

6. The method according to any one of claims 2 to 5, wherein: The second timer associated with the first terminal device is different from the second timer associated with the second terminal device, and the second timer is used to determine the implicit deregistration time of the associated terminal device.

7. The method according to claim 6, wherein The start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or The time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

8. The method according to claim 1, wherein The first paging message includes one or more of the following: identification information associated with the first terminal device; First indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

9. The method according to claim 8, wherein The identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

10. The method according to claim 8 or 9, characterized in that The multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

11. The method according to any one of claims 8 to 10, wherein: The value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

12. The method according to any one of claims 8 to 11, wherein The multi-access device is associated with a second timer, where the second timer is used to determine a time for implicit deregistration of the multi-access device.

13. The method according to any one of claims 8 to 12, wherein: The value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

14. A wireless communication method, characterized in that: include: A second terminal device receives the first information sent by the second network device, where the second terminal device and the first terminal device belong to the same multi-access device. The first information includes one or more of the following: a first paging message used to page the first terminal device and the second terminal device; a second paging message used to page the first terminal device; Downlink information to be transmitted to the first terminal device.

15. The method according to claim 14, wherein If the first information includes the second paging message, the second terminal device receives the first information sent by the network device, including: In the event that paging of the first terminal device fails, the second terminal device receives the first information sent by the second network device.

16. The method according to claim 15, wherein The reason why the paging failure of the first terminal device is related to one or more of the following: mobility of the first terminal device; Mobility of the network device providing services for the first terminal device.

17. The method according to any one of claims 14 to 16, wherein: The second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; Second indication information, where the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

18. The method according to claim 17, wherein The second indication information is used to indicate that paging the first terminal device has failed.

19. The method according to any one of claims 15 to 18, wherein The second timer associated with the first terminal device is different from the second timer associated with the second terminal device, and the second timer is used to determine the implicit deregistration time of the associated terminal device.

20. The method according to claim 19, wherein The start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or The time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

21. The method of claim 14, wherein: The first paging message includes one or more of the following: identification information associated with the first terminal device; First indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

22. The method according to claim 21, wherein The identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

23. The method according to claim 21 or 22, wherein: The multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

24. The method according to any one of claims 21 to 23, wherein The value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

25. The method according to any one of claims 21 to 24, wherein The multi-access device is associated with a second timer, where the second timer is used to determine a time for implicit deregistration of the multi-access device.

26. The method according to any one of claims 21 to 25, wherein The value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

27. The method according to any one of claims 14 to 26, wherein The method further comprises: The second terminal device receives the first information sent by the first terminal device.

28. A wireless communication method, characterized in that: include: The second network device sends the first information to the second terminal device, where the second terminal device and the first terminal device belong to the same multi-access device. The first information includes one or more of the following: a first paging message used to page the first terminal device and the second terminal device; a second paging message used to page the first terminal device; Downlink information to be transmitted to the first terminal device.

29. The method of claim 28, wherein If the first information includes the second paging message, the second network device sends the first information to the second terminal device, including: In the event that paging of the first terminal device fails, the second network device sends the first information to the second terminal device.

30. The method of claim 29, wherein: The reason why the paging failure of the first terminal device is related to one or more of the following: mobility of the first terminal device; Mobility of the network device providing services for the first terminal device.

31. The method according to any one of claims 28 to 30, wherein The second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; Second indication information, where the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

32. The method of claim 31, wherein The second indication information is used to indicate that paging the first terminal device has failed.

33. The method according to any one of claims 29 to 32, wherein The second timer associated with the first terminal device is different from the second timer associated with the second terminal device, and the second timer is used to determine the implicit deregistration time of the associated terminal device.

34. The method of claim 33, wherein: The start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or The time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

35. The method of claim 28, wherein The first paging message includes one or more of the following: identification information associated with the first terminal device; First indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

36. The method of claim 35, wherein: The identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

37. The method according to claim 35 or 36, wherein The multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

38. The method according to any one of claims 35 to 37, wherein The value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

39. The method according to any one of claims 35 to 38, wherein The multi-access device is associated with a second timer, where the second timer is used to determine a time for implicit deregistration of the multi-access device.

40. The method according to any one of claims 35 to 39, wherein The value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

41. The method according to any one of claims 28 to 40, wherein Before the second network device sends the first information to the second terminal device, the method further includes: The second network device receives second information sent by the first network device, where the second information is used to trigger the second network device to send the first information.

42. A wireless communication method, characterized in that: include: The first network device sends second information to the second network device, where the second information is used to trigger the second network device to send the first information, wherein the first information includes one or more of the following: A first paging message used to page the first terminal device and the second terminal device; a second paging message for paging the first terminal device; Downlink information to be transmitted to the first terminal device; Among them, the first terminal device and the second terminal device are multi-access devices.

43. The method of claim 42, wherein: If the first information includes the second paging message, the second network device sends the first information to the second terminal device, including: In the event that paging of the first terminal device fails, the second network device sends the first information to the second terminal device.

44. The method of claim 43, wherein: The reason why the paging failure of the first terminal device is related to one or more of the following: mobility of the first terminal device; Mobility of the network device providing services for the first terminal device.

45. The method according to any one of claims 42 to 44, wherein The second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; Second indication information, where the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

46. ​​The method of claim 45, wherein The second indication information is used to indicate that paging the first terminal device has failed.

47. The method according to any one of claims 43 to 46, wherein The second timer associated with the first terminal device is different from the second timer associated with the second terminal device, and the second timer is used to determine the implicit deregistration time of the associated terminal device.

48. The method of claim 47, wherein The start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or The time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

49. The method of claim 42, wherein The first paging message includes one or more of the following: identification information associated with the first terminal device; First indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

50. The method of claim 49, wherein The identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

51. The method according to claim 49 or 50, wherein The multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

52. The method according to any one of claims 49 to 51, wherein The value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

53. The method according to any one of claims 49 to 52, wherein The multi-access device is associated with a second timer, where the second timer is used to determine a time for implicit deregistration of the multi-access device.

54. The method according to any one of claims 49 to 53, wherein The value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

55. The method according to any one of claims 42 to 54, wherein Before the second network device sends the first information to the second terminal device, the method further includes: The second network device receives second information sent by the first network device, where the second information is used to trigger the second network device to send the first information.

56. A method of wireless communication, characterized in that: include: The first terminal device receives first information sent by the second terminal device, where the first information includes one or more of the following: A first paging message used to page the first terminal device and the second terminal device; a second paging message for paging the first terminal device; Downlink information to be transmitted to the first terminal device; Among them, the first terminal device and the second terminal device are multi-access devices.

57. The method of claim 56, wherein: If the first information includes the second paging message, the second network device sends the first information to the second terminal device, including: In the event that paging of the first terminal device fails, the first terminal device receives the first information sent by the second terminal device.

58. The method of claim 57, wherein: The reason why the paging failure of the first terminal device is related to one or more of the following: mobility of the first terminal device; Mobility of the network device providing services for the first terminal device.

59. The method according to any one of claims 56 to 58, wherein The second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; Second indication information, where the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

60. The method of claim 59, wherein The second indication information is used to indicate that paging the first terminal device has failed.

61. The method according to any one of claims 57 to 60, wherein The second timer associated with the first terminal device is different from the second timer associated with the second terminal device, and the second timer is used to determine the implicit deregistration time of the associated terminal device.

62. The method of claim 61, wherein The start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or The time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

63. The method of claim 56, wherein: The first paging message includes one or more of the following: identification information associated with the first terminal device; First indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

64. The method of claim 63, wherein: The identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

65. The method according to claim 63 or 64, wherein The multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

66. The method according to any one of claims 63 to 65, wherein The value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

67. The method according to any one of claims 63 to 66, wherein The multi-access device is associated with a second timer, where the second timer is used to determine a time for implicit deregistration of the multi-access device.

68. The method according to any one of claims 63 to 67, wherein The value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

69. A method of wireless communication, characterized in that: include: The first core network network element determines whether the second terminal device and the first terminal device belong to the same multi-access device based on the subscription message of the second terminal device.

70. The method of claim 69, wherein The method further comprises: The first core network network element receives a signing message of the second terminal device sent by the second core network network element.

71. The method according to claim 69 or 70, wherein The subscription message of the second terminal device includes one or more of the following: Information of the service access and mobility management function AMF of the second terminal device; Information of a multi-access device associated with the second terminal device; Information used to indicate whether the second terminal device supports being paging through other terminal devices, wherein the other terminal devices are other terminal devices other than the second terminal device in the multi-access device to which the second terminal device belongs.

72. The method of claim 70 or 71, wherein: The method further comprises: The first core network element sends a first request to the second core network element, where the first request is used to request subscription to the contract information of the second terminal device.

73. The method according to any one of claims 69 to 72, wherein If the second terminal device and the first terminal device belong to the same multi-access device, the method further includes: The first core network element sends third information to the first terminal device, where the third information is used to indicate that paging the second terminal device through the first terminal device is allowed.

74. The method according to any one of claims 69 to 73, wherein If the second terminal device and the first terminal device do not belong to the same multi-access device, the method further includes: The first core network element sends third information to the first terminal device, where the third information is used to indicate a refusal to page the second terminal device through the first terminal device.

75. The method of claim 74, wherein The third information is used to indicate the reason for rejecting paging the second terminal device through the first terminal device.

76. The method of any one of claims 73 to 75, wherein The third information is carried in a registration acceptance message of the second terminal device and / or a registration acceptance message of the first terminal device.

77. The method according to any one of claims 69 to 76, wherein If paging the second terminal device through the first terminal device is allowed, the method further includes: In response to the occurrence of the first event, the first core network element sends fourth information to the first terminal device, where the fourth information is used to indicate that paging the second terminal device through the first terminal device will be allowed, and is updated to denying paging the second terminal device through the first terminal device.

78. The method of claim 77, wherein The fourth information is carried in the UE configuration update message.

79. The method of claim 77 or 78, wherein The first event includes one or more of the following: The second terminal device and the first terminal device belong to a different multi-access device; A third timer times out, the third timer being used to determine a waiting time for obtaining a subscription message from the second terminal device; The second terminal device does not support being paged through other terminal devices, wherein the other terminal devices are other terminal devices other than the second terminal device in the multi-access device to which the second terminal device belongs.

80. The method of claim 79, wherein The start of the third timer is triggered based on a first request or a registration request of the first terminal device, wherein the first request is used by the first core network element to request to subscribe to the subscription message of the second terminal device.

81. A wireless communication method, characterized in that include: The second core network network element sends a signing message of the second terminal device to the first core network network element. The signing information of the second terminal device is used to determine whether the second terminal device and the first terminal device belong to the same multi-access device.

82. The method of claim 81, wherein The subscription message of the second terminal device includes one or more of the following: Information of the service AMF of the second terminal device; Information of a multi-access device associated with the second terminal device; Information used to indicate whether the second terminal device supports being paging through other terminal devices, wherein the other terminal devices are other terminal devices other than the second terminal device in the multi-access device to which the second terminal device belongs.

83. The method according to claim 81 or 82, wherein The method further comprises: The second core network element receives a first request sent by the first core network element, where the first request is used to request subscription to the contract information of the second terminal device.

84. A method of wireless communication, characterized in that include: The first terminal device receives the second information or the third information sent by the first core network element, The second information is used to indicate a refusal to page the second terminal device through the first terminal device, and the third information is used to indicate that paging the second terminal device through the first terminal device will be allowed, which is updated to a refusal to page the second terminal device through the first terminal device.

85. A method of wireless communication, characterized in that include: The first core network element sends fifth information to the second terminal device, where the fifth information is used to request the second terminal device to confirm whether to allow or refuse to page the first terminal device through the second terminal device. The first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

86. The method of claim 85, wherein The fifth information is used to indicate one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; The first terminal device supports paging the first terminal device through the second terminal device.

87. The method of claim 85 or 86, wherein The first core network network element provides services for the first terminal device, the fifth information is sent by the first core network network element to the second terminal device via a second core network network element, and the second core network network element provides services for the second terminal device; or The first core network element serves the first terminal device and the second terminal device.

88. The method according to any one of claims 85 to 87, wherein The method further comprises: The first core network element receives response information of the fifth information sent by the second terminal device, and the response information is used to indicate that the second terminal device allows or refuses to page the first terminal device through the second terminal device.

89. The method of claim 88, wherein The response information is used to indicate one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; The second terminal device allows or refuses to page the first terminal device through the second terminal device.

90. The method of claim 88 or 89, wherein: The first core network element provides services for the first terminal device, the response information is sent by the first core network element to the second terminal device via a second core network element, and the second core network element provides services for the second terminal device; or The first core network element serves the first terminal device and the second terminal device.

91. The method according to any one of claims 85 to 90, wherein If the second terminal device allows paging the first terminal device through the second terminal device, the method further includes: The first core network element sends sixth information to the first terminal device, where the sixth information is used to indicate that the second terminal device allows paging of the first terminal device through the second terminal device.

92. The method of any one of claims 85 to 90, wherein If the second terminal device refuses to page the first terminal device through the second terminal device, the method further includes: The first core network element sends sixth information to the first terminal device, where the sixth information is used to instruct the second terminal device to refuse to page the first terminal device through the second terminal device.

93. The method according to claim 91 or 92, wherein: The sixth information is carried in the registration acceptance message of the first terminal device.

94. The method of any one of claims 85 to 93, wherein The fifth information is carried in the registration request message of the first terminal device.

95. A wireless communication method, characterized in that: include: The second terminal device receives fifth information sent by the first core network network element, where the fifth information is used to request the second terminal device to confirm whether to allow or refuse to page the first terminal device through the second terminal device. The first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

96. The method of claim 95, wherein: The fifth information is used to indicate one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; The first terminal device supports paging the first terminal device through the second terminal device.

97. The method of claim 95 or 96, wherein: The first core network network element provides services for the first terminal device, the fifth information is sent by the first core network network element to the second terminal device via a second core network network element, and the second core network network element provides services for the second terminal device; or The first core network element serves the first terminal device and the second terminal device.

98. The method of any one of claims 95-97, wherein The method further comprises: The second terminal device sends response information of the fifth information to the first core network network element, and the response information is used to indicate that the second terminal device allows or refuses to page the first terminal device through the second terminal device.

99. The method of claim 98, wherein The response information is used to indicate one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; The second terminal device allows or refuses to page the first terminal device through the second terminal device.

100. The method of claim 98 or 99, wherein: The first core network element provides services for the first terminal device, the response information is sent by the first core network element to the second terminal device via a second core network element, and the second core network element provides services for the second terminal device; or The first core network element serves the first terminal device and the second terminal device.

101. The method according to any one of claims 95 to 100, wherein The fifth information is carried in the registration request message of the first terminal device.

102. A wireless communication method, characterized in that: include: The first terminal device receives sixth information sent by the first core network element, where the sixth information is used to instruct the second terminal device to allow or refuse to page the first terminal device through the second terminal device. The first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

103. The method of claim 102, wherein: If the first terminal device and the second terminal device belong to the same multi-access device, the sixth information is used to indicate that the second terminal device allows paging of the first terminal device through the second terminal device.

104. The method of claim 102, wherein: If the first terminal device and the second terminal device belong to different multi-access devices, the sixth information is used to instruct the second terminal device to refuse to page the first terminal device through the second terminal device.

105. The method according to any one of claims 102 to 104, wherein The sixth information is carried in the registration acceptance message of the first terminal device.

106. A method of wireless communication, characterized in that: include: The first device sends a first identifier to the second device, where the first identifier is used to identify a multi-access device, where the multi-access device includes a first terminal device and a second terminal device.

107. The method of claim 106, wherein: The first identifier is used to page the first terminal device and / or the second terminal device.

108. The method according to claim 106 or 107, wherein The first identifier is carried in a subscription message of the first terminal device, or the first identifier is allocated by a unified data management function UDM.

109. The method according to any one of claims 106 to 108, wherein The first device includes a UDM, and the second device includes an AMF serving the first terminal device.

110. The method according to any one of claims 106 to 108, wherein The first device includes an AMF serving the first terminal device, and the second device includes the first terminal device.

111. The method of claim 110, wherein: The first identifier is carried in the registration acceptance message.

112. The method of claim 111, wherein: The registration acceptance message is further used to indicate permission or rejection of paging the first terminal device and / or the second terminal device based on the first identifier.

113. The method according to any one of claims 106 to 108, wherein The first device includes the first terminal device, and the second device includes the second terminal device.

114. The method according to any one of claims 106 to 108, wherein The first device includes the second terminal device, and the second device includes an AMF serving the second terminal device.

115. The method of claim 114, wherein: The first identifier is carried in the registration request.

116. The method according to any one of claims 106 to 108, wherein The first device includes an AMF serving the second terminal device, and the second device includes a UDM.

117. The method according to any one of claims 106 to 108, wherein The first device includes an AMF serving the second terminal device, and the second device includes the second terminal device.

118. A wireless communication method, characterized in that: include: The second device receives a first identifier sent by the first device, where the first identifier is used to identify a multi-access device, where the multi-access device includes a first terminal device and a second terminal device.

119. The method of claim 118, wherein The first identifier is used to page the first terminal device and / or the second terminal device.

120. The method of claim 118 or 119, wherein: The first identifier is carried in a subscription message of the first terminal device, or the first identifier is allocated by UDM.

121. The method according to any one of claims 118 to 120, wherein The first device includes a UDM, and the second device includes an AMF serving the first terminal device.

122. The method according to any one of claims 118 to 120, wherein The first device includes an AMF serving the first terminal device, and the second device includes the first terminal device.

123. The method of claim 122, wherein: The first identifier is carried in the registration acceptance message.

124. The method of claim 123, wherein: The registration acceptance message is further used to indicate permission or rejection of paging the first terminal device and / or the second terminal device based on the first identifier.

125. The method of any one of claims 118 to 120, wherein The first device includes the first terminal device, and the second device includes the second terminal device.

126. The method of any one of claims 118 to 120, wherein The first device includes the second terminal device, and the second device includes an AMF serving the second terminal device.

127. The method of claim 126, wherein: The first identifier is carried in the registration request.

128. The method of any one of claims 118 to 120, wherein The first device includes an AMF serving the second terminal device, and the second device includes a UDM.

129. The method of any one of claims 118 to 120, wherein The first device includes an AMF serving the second terminal device, and the second device includes the second terminal device.

130. A wireless communication method, characterized in that: include: The first device sends first capability information to the second device, where the first capability information is used to indicate whether the second terminal device supports paging through the first terminal device, and the first terminal device and the second terminal device are multi-access devices.

131. The method of claim 130, wherein The first capability information is carried in a registration request of the first terminal device; and / or a registration request of the second terminal device.

132. A wireless communication method, characterized in that: include: The second device receives first capability information sent by the first device, where the first capability information is used to indicate whether the second terminal device supports paging through the first terminal device, and the first terminal device and the second terminal device are multi-access devices.

133. The method of claim 132, wherein: The first capability information is carried in a registration request of the first terminal device; and / or a registration request of the second terminal device.

134. A terminal device, characterized in that The terminal device is a first terminal device, including: A receiving unit, configured to receive first information sent by a second terminal device, where the first information includes one or more of the following: A first paging message used to page the first terminal device and the second terminal device; a second paging message for paging the first terminal device; Downlink information to be transmitted to the first terminal device; Among them, the first terminal device and the second terminal device are multi-access devices.

135. The terminal device according to claim 134, characterized in that If the first information includes the second paging message, the receiving unit is used to receive the first information sent by the second terminal device when the paging of the first terminal device fails.

136. The terminal device according to claim 135, characterized in that The reason why the paging failure of the first terminal device is related to one or more of the following: mobility of the first terminal device; Mobility of the network device providing services for the first terminal device.

137. The terminal device according to any one of claims 134 to 136, wherein: The second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; Second indication information, where the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

138. The terminal device according to claim 137, wherein: The second indication information is used to indicate that paging the first terminal device has failed.

139. The terminal device according to any one of claims 135 to 138, wherein: The second timer associated with the first terminal device is different from the second timer associated with the second terminal device, and the second timer is used to determine the implicit deregistration time of the associated terminal device.

140. The terminal device according to claim 139, wherein: The start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or The time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

141. The terminal device according to claim 134, wherein: The first paging message includes one or more of the following: identification information associated with the first terminal device; First indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

142. The terminal device according to claim 141, wherein: The identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

143. The terminal device according to claim 141 or 142, characterized in that The multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

144. The terminal device according to any one of claims 141 to 143, wherein: The value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

145. The terminal device according to any one of claims 141 to 144, characterized in that: The multi-access device is associated with a second timer, where the second timer is used to determine a time for implicit deregistration of the multi-access device.

146. The terminal device according to any one of claims 141 to 145, characterized in that: The value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

147. A terminal device, characterized in that: The terminal device is a second terminal device, including: a receiving unit, configured to receive first information sent by a second network device, where the second terminal device and the first terminal device belong to the same multi-access device, The first information includes one or more of the following: a first paging message used to page the first terminal device and the second terminal device; a second paging message used to page the first terminal device; Downlink information to be transmitted to the first terminal device.

148. The terminal device according to claim 147, wherein: If the first information includes the second paging message, the receiving unit is used to receive the first information sent by the second network device when the paging of the first terminal device fails.

149. The terminal device according to claim 148, characterized in that The reason why the paging failure of the first terminal device is related to one or more of the following: mobility of the first terminal device; Mobility of the network device providing services for the first terminal device.

150. The terminal device according to any one of claims 147 to 149, wherein: The second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; Second indication information, where the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

151. The terminal device according to claim 150, characterized in that The second indication information is used to indicate that paging the first terminal device has failed.

152. The terminal device according to any one of claims 148 to 151, wherein: The second timer associated with the first terminal device is different from the second timer associated with the second terminal device, and the second timer is used to determine the implicit deregistration time of the associated terminal device.

153. The terminal device according to claim 152, characterized in that The start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or The time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

154. The terminal device according to claim 147, wherein: The first paging message includes one or more of the following: identification information associated with the first terminal device; First indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

155. The terminal device according to claim 154, characterized in that The identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

156. The terminal device according to claim 154 or 155, wherein: The multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

157. The terminal device according to any one of claims 154-156, characterized in that The value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

158. The terminal device according to any one of claims 154-157, characterized in that: The multi-access device is associated with a second timer, where the second timer is used to determine a time for implicit deregistration of the multi-access device.

159. The terminal device according to any one of claims 154-158, characterized in that The value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

160. The terminal device according to any one of claims 147 to 159, wherein: The receiving unit is used to receive the first information sent by the first terminal device.

161. A network device, characterized in that The network device is a second network device, comprising: a sending unit, configured to send first information to a second terminal device, where the second terminal device and the first terminal device belong to the same multi-access device, The first information includes one or more of the following: a first paging message used to page the first terminal device and the second terminal device; a second paging message used to page the first terminal device; Downlink information to be transmitted to the first terminal device.

162. The network device according to claim 161, wherein If the first information includes the second paging message, the sending unit is used to send the first information to the second terminal device when the paging of the first terminal device fails.

163. The network device according to claim 162, wherein: The reason why the paging failure of the first terminal device is related to one or more of the following: mobility of the first terminal device; Mobility of the network device providing services for the first terminal device.

164. The network device according to any one of claims 161 to 163, wherein: The second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; Second indication information, where the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

165. The network device according to claim 164, wherein: The second indication information is used to indicate that paging the first terminal device has failed.

166. The network device according to any one of claims 162-165, wherein: The second timer associated with the first terminal device is different from the second timer associated with the second terminal device, and the second timer is used to determine the implicit deregistration time of the associated terminal device.

167. The network device according to claim 166, wherein: The start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or The time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

168. The network device according to claim 161, wherein The first paging message includes one or more of the following: identification information associated with the first terminal device; First indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

169. The network device according to claim 168, wherein The identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

170. The network device according to claim 168 or 169, wherein: The multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

171. The network device according to any one of claims 168 to 170, wherein: The value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

172. The network device according to any one of claims 168 to 171, wherein: The multi-access device is associated with a second timer, where the second timer is used to determine a time for implicit deregistration of the multi-access device.

173. The network device according to any one of claims 168 to 172, wherein: The value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

174. The network device according to any one of claims 161 to 173, wherein: The network device further includes a receiving unit, configured to receive second information sent by the first network device, where the second information is used to trigger the second network device to send the first information.

175. A network device, characterized in that The network device is a first network device, comprising: a sending unit, configured to send second information to a second network device, where the second information is used to trigger the second network device to send first information, wherein the first information includes one or more of the following: A first paging message used to page the first terminal device and the second terminal device; a second paging message for paging the first terminal device; Downlink information to be transmitted to the first terminal device; Among them, the first terminal device and the second terminal device are multi-access devices.

176. The network device according to claim 175, wherein If the first information includes the second paging message, the sending unit is used to send the first information to the second terminal device when the paging of the first terminal device fails.

177. The network device according to claim 176, wherein: The reason why the paging failure of the first terminal device is related to one or more of the following: mobility of the first terminal device; Mobility of the network device providing services for the first terminal device.

178. The network device according to any one of claims 175 to 177, wherein: The second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; Second indication information, where the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

179. The network device according to claim 178, wherein The second indication information is used to indicate that paging the first terminal device has failed.

180. The network device according to any one of claims 176 to 179, wherein: The second timer associated with the first terminal device is different from the second timer associated with the second terminal device, and the second timer is used to determine the implicit deregistration time of the associated terminal device.

181. The network device according to claim 180, wherein: The start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or The time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

182. The network device according to claim 175, wherein: The first paging message includes one or more of the following: identification information associated with the first terminal device; First indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

183. The network device according to claim 182, wherein: The identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

184. The network device according to claim 182 or 183, wherein: The multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

185. The network device according to any one of claims 182-184, wherein: The value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

186. The network device according to any one of claims 182-185, wherein: The multi-access device is associated with a second timer, where the second timer is used to determine a time for implicit deregistration of the multi-access device.

187. The network device according to any one of claims 182 to 186, wherein: The value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

188. The network device according to any one of claims 175-187, wherein: The network device further includes: A receiving unit is configured to receive second information sent by a first network device, wherein the second information is used to trigger the second network device to send The first information.

189. A terminal device, characterized in that: The terminal device is a first terminal device, including: A receiving unit, configured to receive first information sent by a second terminal device, where the first information includes one or more of the following: A first paging message used to page the first terminal device and the second terminal device; a second paging message for paging the first terminal device; Downlink information to be transmitted to the first terminal device; Among them, the first terminal device and the second terminal device are multi-access devices.

190. The terminal device according to claim 189, wherein: If the first information includes the second paging message, the receiving unit is used to receive the first information sent by the second terminal device when the paging of the first terminal device fails.

191. The terminal device according to claim 190, wherein: The reason why the paging failure of the first terminal device is related to one or more of the following: mobility of the first terminal device; Mobility of the network device providing services for the first terminal device.

192. The terminal device according to any one of claims 189 to 191, wherein: The second paging message includes one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; first indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device; Second indication information, where the second indication information is used to indicate the reason for paging the first terminal device through the second terminal device.

193. The terminal device according to claim 192, wherein: The second indication information is used to indicate that paging the first terminal device has failed.

194. The terminal device according to any one of claims 190-193, characterized in that The second timer associated with the first terminal device is different from the second timer associated with the second terminal device, and the second timer is used to determine the implicit deregistration time of the associated terminal device.

195. The terminal device according to claim 194, wherein: The start time of the second timer associated with the first terminal device is determined based on the time when the paging of the second terminal device fails, or The time period indicated by the second timer associated with the first terminal device is determined based on the time when the paging of the first terminal device fails and the duration of paging the second terminal device.

196. The terminal device as claimed in claim 189, characterized in that The first paging message includes one or more of the following: identification information associated with the first terminal device; First indication information, where the first indication information is used to instruct the network device to page the first terminal device through the second terminal device.

197. The terminal device according to claim 196, characterized in that The identification information associated with the first terminal device includes the terminal device identification of the first terminal device and / or the identification of the multi-access device.

198. The terminal device according to claim 196 or 197, wherein: The multi-access device is associated with a first timer, and the first timer is used to determine whether the multi-access device is reachable.

199. The terminal device according to any one of claims 196-198, characterized in that The value of the first timer associated with the multi-access device is determined based on the value of the first timer associated with the first terminal device and the value of the first timer associated with the second terminal device.

200. The terminal device according to any one of claims 196-199, characterized in that: The multi-access device is associated with a second timer, where the second timer is used to determine a time for implicit deregistration of the multi-access device.

201. The terminal device according to any one of claims 196-200, characterized in that: The value of the second timer associated with the multi-access device is determined based on the value of the second timer associated with the first terminal device and the value of the second timer associated with the second terminal device.

202. A network device, characterized in that The network device is a first core network element, including: The processing unit is configured to determine whether the second terminal device and the first terminal device belong to the same group based on the signing message of the second terminal device. Same multi-access device.

203. The network device according to claim 202, wherein: The network device further includes: A receiving unit is used to receive a signing message of the second terminal device sent by a second core network network element.

204. The network device according to claim 202 or 203, wherein: The subscription message of the second terminal device includes one or more of the following: Information of the service AMF of the second terminal device; Information of a multi-access device associated with the second terminal device; Information used to indicate whether the second terminal device supports being paging through other terminal devices, wherein the other terminal devices are other terminal devices other than the second terminal device in the multi-access device to which the second terminal device belongs.

205. The network device according to claim 203 or 204, wherein: The network device further includes: The first sending unit is used to send a first request to the second core network network element, where the first request is used to request subscription to the contract information of the second terminal device.

206. The network device according to any one of claims 202-205, characterized in that If the second terminal device and the first terminal device belong to the same multi-access device, the network device further includes: The second sending unit is used to send third information to the first terminal device, where the third information is used to indicate that paging the second terminal device through the first terminal device is allowed.

207. The network device according to any one of claims 202-206, wherein: If the second terminal device and the first terminal device do not belong to the same multi-access device, the network device further includes: A third sending unit is used to send third information to the first terminal device, where the third information is used to indicate a rejection of paging the second terminal device through the first terminal device.

208. The network device according to claim 207, wherein: The third information is used to indicate the reason for rejecting paging the second terminal device through the first terminal device.

209. The network device according to any one of claims 206-208, wherein: The third information is carried in a registration acceptance message of the second terminal device and / or a registration acceptance message of the first terminal device.

210. The network device according to any one of claims 202-209, wherein: If paging the second terminal device through the first terminal device is allowed, the network device further includes: In response to the occurrence of the first event, the fourth sending unit is used to send fourth information to the first terminal device, where the fourth information is used to indicate that paging the second terminal device through the first terminal device will be allowed, and is updated to denying paging the second terminal device through the first terminal device.

211. The network device according to claim 210, wherein: The fourth information is carried in the UE configuration update message.

212. The network device according to claim 210 or 211, wherein: The first event includes one or more of the following: The second terminal device and the first terminal device belong to a different multi-access device; A third timer times out, the third timer being used to determine a waiting time for obtaining a subscription message from the second terminal device; The second terminal device does not support being paged through other terminal devices, wherein the other terminal devices are other terminal devices other than the second terminal device in the multi-access device to which the second terminal device belongs.

213. The network device according to claim 212, wherein: The start of the third timer is triggered based on a first request or a registration request of the first terminal device, wherein the first request is used by the first core network element to request to subscribe to the subscription message of the second terminal device.

214. A network device, characterized in that The network device is a second core network element, including: A sending unit is used to send a signing message of a second terminal device to a first core network network element, where the signing information of the second terminal device is used to determine whether the second terminal device and the first terminal device belong to the same multi-access device.

215. The network device according to claim 214, wherein: The subscription message of the second terminal device includes one or more of the following: Information of the service AMF of the second terminal device; Information of a multi-access device associated with the second terminal device; Information used to indicate whether the second terminal device supports being paging through other terminal devices, wherein the other terminal devices are other terminal devices other than the second terminal device in the multi-access device to which the second terminal device belongs.

216. The network device according to claim 214 or 215, wherein: The network device further includes: A receiving unit is used to receive a first request sent by the first core network network element, where the first request is used to request subscription to the contract information of the second terminal device.

217. A terminal device, characterized in that The terminal device is a first terminal device, including: a receiving unit, configured to receive the second information or the third information sent by the first core network element, The second information is used to indicate a refusal to page the second terminal device through the first terminal device, and the third information is used to indicate that paging the second terminal device through the first terminal device will be allowed, which is updated to a refusal to page the second terminal device through the first terminal device.

218. A network device, characterized in that The network device is a first core network element, including: a sending unit, configured to send fifth information to the second terminal device, wherein the fifth information is used to request the second terminal device to confirm whether to allow or refuse to page the first terminal device through the second terminal device, The first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

219. The network device of claim 218, wherein: The fifth information is used to indicate one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; The first terminal device supports paging the first terminal device through the second terminal device.

220. The network device according to claim 218 or 219, wherein: The first core network network element provides services for the first terminal device, the fifth information is sent by the first core network network element to the second terminal device via a second core network network element, and the second core network network element provides services for the second terminal device; or The first core network element serves the first terminal device and the second terminal device.

221. The network device according to any one of claims 218 to 220, wherein: The network device further includes: A receiving unit is used to receive response information of the fifth information sent by the second terminal device, where the response information is used to indicate whether the second terminal device allows or refuses to page the first terminal device through the second terminal device.

222. The network device according to claim 221, wherein: The response information is used to indicate one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; The second terminal device allows or refuses to page the first terminal device through the second terminal device.

223. The network device according to claim 221 or 222, characterized in that The first core network element provides services for the first terminal device, the response information is sent by the first core network element to the second terminal device via a second core network element, and the second core network element provides services for the second terminal device; or The first core network element serves the first terminal device and the second terminal device.

224. The network device according to any one of claims 218 to 223, wherein: If the second terminal device allows paging the first terminal device through the second terminal device, the network device further includes: The sending unit is used to send sixth information to the first terminal device, where the sixth information is used to indicate that the second terminal device allows paging of the first terminal device through the second terminal device.

225. The network device according to any one of claims 218 to 223, wherein: If the second terminal device refuses to page the first terminal device through the second terminal device, the network device further includes: The sending unit is used to send sixth information to the first terminal device, where the sixth information is used to instruct the second terminal device to refuse to page the first terminal device through the second terminal device.

226. The network device according to claim 224 or 225, wherein: The sixth information is carried in the registration acceptance message of the first terminal device.

227. The network device according to any one of claims 218 to 226, wherein: The fifth information is carried in the registration request message of the first terminal device.

228. A terminal device, characterized in that The terminal device is a second terminal device, including: a receiving unit, configured to receive fifth information sent by the first core network network element, wherein the fifth information is used to request the second terminal device to confirm whether to allow or refuse to page the first terminal device through the second terminal device, The first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

229. The terminal device as described in claim 228, characterized in that The fifth information is used to indicate one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; The first terminal device supports paging the first terminal device through the second terminal device.

230. The terminal device according to claim 228 or 229, wherein: The first core network network element provides services for the first terminal device, the fifth information is sent by the first core network network element to the second terminal device via a second core network network element, and the second core network network element provides services for the second terminal device; or The first core network element serves the first terminal device and the second terminal device.

231. The terminal device according to any one of claims 228-230, characterized in that The terminal device further includes: The second terminal device sends response information of the fifth information to the first core network network element, and the response information is used to indicate that the second terminal device allows or refuses to page the first terminal device through the second terminal device.

232. The terminal device according to claim 231, characterized in that The response information is used to indicate one or more of the following: an identifier of the first terminal device; an identifier of the second terminal device; The second terminal device allows or refuses to page the first terminal device through the second terminal device.

233. The terminal device according to claim 231 or 232, characterized in that The first core network element provides services for the first terminal device, the response information is sent by the first core network element to the second terminal device via a second core network element, and the second core network element provides services for the second terminal device; or The first core network element serves the first terminal device and the second terminal device.

234. The terminal device according to any one of claims 228-233, characterized in that The fifth information is carried in the registration request message of the first terminal device.

235. A terminal device, characterized in that The terminal device is a first terminal device, including: a receiving unit, configured to receive sixth information sent by the first core network network element, wherein the sixth information is used to instruct the second terminal device to allow or refuse to page the first terminal device through the second terminal device, The first terminal device and the second terminal device belong to the same multi-access device, or the first terminal device and the second terminal device belong to different multi-access devices.

236. The terminal device according to claim 235, characterized in that If the first terminal device and the second terminal device belong to the same multi-access device, the sixth information is used to indicate that the second terminal device allows paging of the first terminal device through the second terminal device.

237. The terminal device according to claim 235, characterized in that If the first terminal device and the second terminal device belong to different multi-access devices, the sixth information is used to instruct the second terminal device to refuse to page the first terminal device through the second terminal device.

238. The terminal device according to any one of claims 235-237, characterized in that: The sixth information is carried in the registration acceptance message of the first terminal device.

239. A communication device, characterized in that The communication device is a first device, comprising: A sending unit is configured to send a first identifier to a second device, where the first identifier is used to identify a multi-access device, where the multi-access device includes a first terminal device and a second terminal device.

240. The communication device according to claim 239, wherein The first identifier is used to page the first terminal device and / or the second terminal device.

241. The communication device according to claim 239 or 240, characterized in that The first identifier is carried in a subscription message of the first terminal device, or the first identifier is allocated by UDM.

242. The communication device according to any one of claims 239 to 241, wherein: The first device includes a UDM, and the second device includes an AMF serving the first terminal device.

243. The communication device according to any one of claims 239 to 241, wherein: The first device includes an AMF serving the first terminal device, and the second device includes the first terminal device.

244. The communication device according to claim 243, wherein The first identifier is carried in the registration acceptance message.

245. The communication device according to claim 244, characterized in that The registration acceptance message is further used to indicate permission or rejection of paging the first terminal device and / or the second terminal device based on the first identifier.

246. The communication device according to any one of claims 239 to 241, wherein: The first device includes the first terminal device, and the second device includes the second terminal device.

247. The communication device according to any one of claims 239 to 241, wherein: The first device includes the second terminal device, and the second device includes an AMF serving the second terminal device.

248. The communication device according to claim 247, characterized in that The first identifier is carried in the registration request.

249. The communication device according to any one of claims 239 to 241, wherein: The first device includes an AMF serving the second terminal device, and the second device includes a UDM.

250. The communication device according to any one of claims 239 to 241, wherein: The first device includes an AMF serving the second terminal device, and the second device includes the second terminal device.

251. A communication device, characterized in that The communication device is a second device, including: The receiving unit is configured to receive a first identifier sent by a first device, where the first identifier is used to identify a multi-access device, where the multi-access device includes a first terminal device and a second terminal device.

252. The communication device of claim 251, wherein: The first identifier is used to page the first terminal device and / or the second terminal device.

253. The communication device according to claim 251 or 252, characterized in that The first identifier is carried in a subscription message of the first terminal device, or the first identifier is allocated by UDM.

254. The communication device according to any one of claims 251 to 253, wherein: The first device includes a UDM, and the second device includes an AMF serving the first terminal device.

255. The communication device according to any one of claims 251 to 253, wherein: The first device includes an AMF serving the first terminal device, and the second device includes the first terminal device.

256. The communication device of claim 255, wherein: The first identifier is carried in the registration acceptance message.

257. The communication device according to claim 256, characterized in that The registration acceptance message is further used to indicate permission or rejection of paging the first terminal device and / or the second terminal device based on the first identifier.

258. The communication device according to any one of claims 251 to 253, wherein: The first device includes the first terminal device, and the second device includes the second terminal device.

259. The communication device according to any one of claims 251 to 253, wherein: The first device includes the second terminal device, and the second device includes an AMF serving the second terminal device.

260. The communication device according to claim 259, wherein The first identifier is carried in the registration request.

261. The communication device according to any one of claims 251 to 253, wherein: The first device includes an AMF serving the second terminal device, and the second device includes a UDM.

262. The communication device according to any one of claims 251 to 253, wherein: The first device includes an AMF serving the second terminal device, and the second device includes the second terminal device.

263. A communication device, characterized in that The communication device is a first device, comprising: A sending unit is used to send first capability information to a second device, where the first capability information is used to indicate whether the second terminal device supports paging through the first terminal device, and the first terminal device and the second terminal device are multi-access devices.

264. The method of claim 130, wherein: The first capability information is carried in a registration request of the first terminal device; and / or a registration request of the second terminal device.

265. A communication device, characterized in that The communication device is a second device, including: A receiving unit is used to receive first capability information sent by a first device, where the first capability information is used to indicate whether a second terminal device supports paging through the first terminal device, and the first terminal device and the second terminal device are multi-access devices.

266. The method of claim 132, wherein: The first capability information is carried in a registration request of the first terminal device; and / or a registration request of the second terminal device.

267. A terminal device, characterized in that It includes a transceiver, a memory and a processor, the memory is used to store programs, the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the terminal device executes one of the following: the method according to any one of claims 1 to 13; the method according to any one of claims 14 to 27; the method according to any one of claims 56 to 68; the method according to claim 84; the method according to any one of claims 95 to 101; or the method according to any one of claims 102 to 105.

268. A network device, characterized in that It includes a transceiver, a memory and a processor, the memory is used to store a program, the processor is used to call the program in the memory and control the transceiver to receive or send a signal so that the network device performs one of the following: the method according to any one of claims 28-41; the method according to any one of claims 42-55; the method according to any one of claims 69-80; the method according to any one of claims 81-83; the method according to any one of claims 85-94.

269. A communication device, characterized in that It includes a transceiver, a memory and a processor, the memory is used to store a program, the processor is used to call the program in the memory and control the transceiver to receive or send a signal so that the communication device performs one of the following: the method according to any one of claims 106-117; the method according to any one of claims 118-129; the method according to any one of claims 130-131; the method according to any one of claims 132-133.

270. A device, characterized in that The device comprises a processor configured to call a program from a memory so as to cause the device to execute the method according to any one of claims 1 to 133.

271. A chip, characterized in that The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes a method according to any one of claims 1 to 133.

272. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 133.

273. A computer program product, characterized in that The method comprises a program for causing a computer to execute the method according to any one of claims 1 to 133.

274. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 133.

Images