Communication method, apparatus, network device, storage medium, and program product

Abstract

Embodiments of the present application provide a communication method and device, network equipment, storage medium and program product, which are applied to a first network equipment. The method comprises: sending a first message, wherein the first message is used to instruct a second network equipment to page a terminal equipment, and the first message is a radio access network (RAN) paging message. The above method can improve communication flexibility.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, apparatus, network device, storage medium, and program product. Background Technology

[0002] When an inactive terminal device moves to the coverage area of ​​a new base station, if the terminal device needs to receive downlink data, the original base station can page the terminal device via the Radio Access Network (RAN). The original base station can be the base station that provided services to the terminal device before the move.

[0003] Currently, the original base station can send RAN paging messages to the new base station, enabling the new base station to page the terminal equipment. However, if the original and new base stations do not have an Xn interface, RAN paging messages cannot be transmitted between them, resulting in poor communication flexibility. Summary of the Invention

[0004] This application provides a communication method, apparatus, network device, storage medium, and program product to solve the technical problem of poor communication flexibility.

[0005] In a first aspect, embodiments of this application provide a communication method applied to a first network device, the method comprising:

[0006] Send a first message, which is used to instruct the second network device to page the terminal device. The first message is a Radio Access Network (RAN) paging message.

[0007] In one possible implementation, the method further includes:

[0008] Receive a second message, which includes the identifier of the second network device.

[0009] In one possible implementation,

[0010] The first network device stores data to be transmitted to the terminal device.

[0011] In one possible implementation,

[0012] The data to be transmitted is transmitted via Non-Small Data Transmission (SDT).

[0013] In one possible implementation, the method further includes:

[0014] The first message is received, and the first message includes the identifier of the second network device.

[0015] In one possible implementation,

[0016] The third network device stores the data to be transmitted to the terminal device. The third network device is a device that stores the context of the terminal device.

[0017] In one possible implementation, the method further includes:

[0018] A third message is received, the third message being used to request the context of the terminal device, the third message including the identifier of a third network device, the third network device being a device that stores the context of the terminal device;

[0019] Send the third message.

[0020] In one possible implementation, the method further includes:

[0021] Receive the context of the terminal device;

[0022] Send the context of the terminal device.

[0023] In one possible implementation,

[0024] The first network device is an Access and Mobility Management Function (AMF) network element or a User Plane Function (UPF) network element.

[0025] Secondly, embodiments of this application provide a communication method applied to a second network device, the method comprising:

[0026] Receive a first message, the first message being used to instruct the second network device to page the terminal device, the first message being a Radio Access Network (RAN) paging message;

[0027] Send the paging message corresponding to the first message.

[0028] In one possible implementation,

[0029] The system receives a response message corresponding to the paging message, wherein the response message includes the identifier of a third network device, and the third network device is a device that stores the context of the terminal device.

[0030] In one possible implementation,

[0031] The response message corresponding to the paging message is a Radio Resource Control (RRC) Recovery Request.

[0032] In one possible implementation, the method further includes:

[0033] Send a third message, the third message being used to request the context of the terminal device, the third message including the identifier of the third network device;

[0034] Receive the context of the terminal device.

[0035] Thirdly, embodiments of this application provide a communication method applied to a third network device, the method comprising:

[0036] Send a first message, which includes the identifier of the second network device. The first message is used to instruct the second network device to page the terminal device. The first message is a Radio Access Network (RAN) paging message.

[0037] In one possible implementation,

[0038] The third network device stores data to be transmitted to the terminal device.

[0039] In one possible implementation,

[0040] Receive a third message, the third message being used to request the context of the terminal device, the third network device being a device that stores the context of the terminal device;

[0041] Send the context of the terminal device.

[0042] Fourthly, embodiments of this application provide a communication device applied to a first network device, the device comprising: a transmitting module, wherein...

[0043] The sending module is used to send a first message, which is used to instruct the second network device to page the terminal device. The first message is a Radio Access Network (RAN) paging message.

[0044] In one possible implementation, the communication device further includes a receiving module, wherein,

[0045] The receiving module is used to receive a second message, the second message including the identifier of the second network device.

[0046] In one possible implementation,

[0047] The first network device stores data to be transmitted to the terminal device.

[0048] In one possible implementation,

[0049] The data to be transmitted is transmitted via Non-Small Data Transmission (SDT).

[0050] In one possible implementation,

[0051] The receiving module is further configured to receive the first message, wherein the first message includes the identifier of the second network device.

[0052] In one possible implementation,

[0053] The third network device stores the data to be transmitted to the terminal device. The third network device is a device that stores the context of the terminal device.

[0054] In one possible implementation,

[0055] The receiving module is further configured to receive a third message, the third message being used to request the context of the terminal device, the third message including the identifier of a third network device, the third network device being a device that stores the context of the terminal device.

[0056] The sending module is also used to send the third message.

[0057] In one possible implementation,

[0058] The receiving module is further configured to receive the context of the terminal device;

[0059] The sending module is also used to send the context of the terminal device.

[0060] In one possible implementation,

[0061] The first network device is an Access and Mobility Management Function (AMF) network element or a User Plane Function (UPF) network element.

[0062] Fifthly, embodiments of this application provide a communication device applied to a second network device, the device comprising: a receiving module and a transmitting module, wherein...

[0063] The receiving module is used to receive a first message, which is used to instruct the second network device to page the terminal device, and the first message is a Radio Access Network (RAN) paging message.

[0064] The sending module is used to send the paging message corresponding to the first message.

[0065] In one possible implementation,

[0066] The receiving module is further configured to receive a response message corresponding to the paging message, wherein the response message corresponding to the paging message includes an identifier of a third network device, and the third network device is a device that stores the context of the terminal device.

[0067] In one possible implementation,

[0068] The response message corresponding to the paging message is a Radio Resource Control (RRC) Recovery Request.

[0069] In one possible implementation,

[0070] The sending module is further configured to send a third message, the third message being used to request the context of the terminal device, the third message including the identifier of the third network device;

[0071] The receiving module is also used to receive the context of the terminal device.

[0072] Sixthly, embodiments of this application provide a communication device applied to a third network device, the device comprising: a transmitting module, wherein...

[0073] The sending module is used to send a first message, the first message including the identifier of the second network device, the first message being used to instruct the second network device to page the terminal device, and the first message being a Radio Access Network (RAN) paging message.

[0074] In one possible implementation,

[0075] The third network device stores data to be transmitted to the terminal device.

[0076] In one possible implementation, the device further includes a receiving module, wherein,

[0077] The receiving module is used to receive a third message, the third message being used to request the context of the terminal device, wherein the third network device is a device that stores the context of the terminal device.

[0078] The sending module is also used to send the context of the terminal device.

[0079] In a seventh aspect, this application provides a chip on which a computer program is stored, and when the computer program is executed by the chip, it implements the method as described in any one of the first aspects.

[0080] Eighthly, this application provides a chip on which a computer program is stored, which, when executed by the chip, implements the method as described in any one of the second aspects.

[0081] Ninthly, this application provides a chip having a computer program stored thereon, which, when executed by the chip, implements the method as described in any one of the third aspects.

[0082] In a tenth aspect, this application provides a chip module on which a computer program is stored, and when the computer program is executed by the chip module, it implements the method as described in any one of the first aspects.

[0083] In one aspect, this application provides a chip module on which a computer program is stored, and when the computer program is executed by the chip module, it implements the method as described in any one of the second aspects.

[0084] In a twelfth aspect, this application provides a chip module on which a computer program is stored, and when the computer program is executed by the chip module, it implements the method as described in any one of the third aspects.

[0085] In a thirteenth aspect, embodiments of this application provide a network device, including:

[0086] At least one processor; and

[0087] A memory communicatively connected to the at least one processor; wherein,

[0088] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method described in any one of the first aspects.

[0089] The method.

[0090] In a fourteenth aspect, embodiments of this application provide a network device, including:

[0091] At least one processor; and

[0092] A memory communicatively connected to the at least one processor; wherein,

[0093] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method described in any one of the second aspects.

[0094] The method.

[0095] In a fifteenth aspect, embodiments of this application provide a network device, including:

[0096] At least one processor; and

[0097] A memory communicatively connected to the at least one processor; wherein,

[0098] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method described in any one of the third aspects.

[0099] In a sixteenth aspect, embodiments of this application provide a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to perform the method described in any one of the first aspects.

[0100] In a seventeenth aspect, embodiments of this application provide a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to perform the method described in any one of the second aspects.

[0101] In an eighteenth aspect, embodiments of this application provide a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to perform the method described in any one of the third aspects.

[0102] In a nineteenth aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the method described in any one of the first aspects.

[0103] In a twentieth aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the method described in any one of the second aspects.

[0104] In a twentieth aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the method described in any one of the third aspects.

[0105] The communication method, apparatus, network device, storage medium, and program product provided in this application embodiment allow a first network device to send a first message to a second network device, and the second network device to send a paging message corresponding to the first message to a terminal device. In the above method, the second network device does not need to receive RAN paging messages through the Xn interface, solving the problem that the second network device cannot receive RAN paging messages when the Xn interface is absent, thus improving communication flexibility. Attached Figure Description

[0106] Figure 1 A flowchart illustrating a random access method provided in an embodiment of this application;

[0107] Figure 2 A flowchart illustrating another random access method provided in an embodiment of this application;

[0108] Figure 3A flowchart illustrating an RRC recovery method provided in an embodiment of this application;

[0109] Figure 4 A flowchart illustrating another RRC recovery method provided in this application embodiment;

[0110] Figure 5 This is a schematic diagram of an SDT transmission process provided in an embodiment of this application;

[0111] Figure 6 This is a schematic diagram of another SDT transmission process provided in an embodiment of this application;

[0112] Figure 7 A schematic diagram of a communication system architecture provided in an embodiment of this application;

[0113] Figure 8 A flowchart illustrating a communication method provided in an embodiment of this application;

[0114] Figure 9 A flowchart illustrating another communication method provided in an embodiment of this application;

[0115] Figure 10 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0116] Figure 11 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0117] Figure 12 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0118] Figure 13 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0119] Figure 14 This is a schematic diagram of the network device provided in an embodiment of this application. Detailed Implementation

[0120] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0121] The technical solutions provided in this application can be applied to a variety of systems. Applicable systems may include, but are not limited to: Narrow Band Internet of Things (NB-IoT) systems, Wideband Code Division Multiple Access (WCDMA) systems, Code Division Multiple Access 2000 (CDMA2000) systems, Time Division Synchronous Code Division Multiple Access (TDSCDMA) systems, Long Term Evolution (LTE) systems, Advanced Long Term Evolution (LTE-A) systems, fifth-generation mobile communication systems or possible sixth-generation or seventh-generation mobile communication systems, vehicle-mounted short-range wireless communication systems, and future mobile communication systems.

[0122] The technical solutions provided in this application are also applicable to different network architectures, including but not limited to relay network architecture, dual-link architecture, vehicle-to-everything (V2X) architecture, and device-to-device (D2D) architecture.

[0123] The network devices involved in the embodiments of this application can be access network devices and core network devices. Taking access network devices as an example, they can include base stations and base station controllers.

[0124] The base station (BS) in this application embodiment, also known as a base station device, is a device deployed in a radio access network (RAN) to provide wireless communication functions. For example, in a 2G network, the device providing base station functions includes a base transceiver station (BTS); in a 3G network, the device providing base station functions includes a node B; in a 4G network, the device providing base station functions includes an evolved node B (eNB); in wireless local area networks (WLANs), the device providing base station functions is an access point (AP); in 5G New Radio (NR), the device providing base station functions is a gNB; and there is a next-generation eNodeB (ng-eNB). The gNB communicates with the terminal device using NR technology, and the ng-eNB communicates with the terminal device using evolved universal terrestrial radio access (E-UTRA) technology. Both the gNB and the ng-eNB can connect to the 5G core network. The base station in this application embodiment also includes equipment that provides base station functions in future new communication systems.

[0125] The base station controller in this application embodiment can also be called a base station controller device, which is a device for managing base stations, such as the base station controller (BSC) in 2G networks, the radio network controller (RNC) in 3G networks, and can also refer to the device for controlling and managing base stations in future new communication systems.

[0126] The terminal devices in this application typically have wireless transceiver capabilities and can also be referred to as User Equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc. Terminal devices can be fixed or mobile. Terminal devices can be stations (STs) in WLANs, cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistant (PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, and next-generation communication systems, such as terminal devices in NR networks or terminal devices in future evolved Public Land Mobile Network (PLMN) networks, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, vehicle-mounted terminal devices, wireless terminals in self-driving, wireless terminal devices in remote medical care, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, wireless terminal devices in smart homes, wearable terminal devices, etc.

[0127] For example, in this embodiment, the terminal device can be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0128] In the Radio Resource Control (RRC) module, the state of establishing an RRC connection between the terminal device and the base station can be characterized by Idle Mode, Connected Mode, or Inactive Mode. This application embodiment involves these three states, which are explained below.

[0129] a. Idle state

[0130] Even when the terminal device is in idle state, it does not establish an RRC connection with the network, but it will still listen for network broadcast information (such as system information, paging messages, etc.).

[0131] b. Connected state

[0132] The terminal device has established an RRC connection with the network, enabling data transmission.

[0133] c. Inactive state

[0134] When a terminal device is inactive, it releases its RRC connection to the network, but the network retains the terminal device's context. Because the network retains the terminal device's context, the inactive terminal device can quickly restore the RRC connection through a simplified signaling process without having to re-perform a complete configuration and authentication process. The inactive state is a state between the idle state and the connected state, primarily used to reduce power consumption and signaling overhead.

[0135] To facilitate understanding, the following will be combined with... Figure 1 The communication system architecture involved in the embodiments of this application will be described.

[0136] Figure 1 This is a schematic diagram of a communication system architecture provided in an embodiment of this application. Figure 1As shown, the communication system includes: a new base station, an existing base station, and terminal equipment.

[0137] The terminal device can be an inactive terminal device.

[0138] The new base station can be the base station selected by the terminal device after a cell reselection.

[0139] The original base station can be the base station that provided services to the terminal device before the cell reselection occurred. The original base station stores the context of the terminal device.

[0140] It should be understood that the number of terminal devices in a communication system can be one or more, and is not limited in the embodiments of this application.

[0141] This application relates to data transmission of inactive terminal devices. The technologies involved in this application are described below.

[0142] I. If a terminal device in an inactive state needs to transmit data, it can transition to a connected state through a random access procedure. The random access procedure can be a four-step random access or a two-step random access. The following section will discuss this in conjunction with... Figures 2-3 The two random access procedures will be explained separately.

[0143] Figure 2 This is a flowchart illustrating a random access method provided in an embodiment of this application. Please refer to... Figure 2 The method may include:

[0144] S201, The terminal device sends message 1 to the base station.

[0145] The terminal device selects an SSB or CSI-RS from the qualified Synchronization Signal Block (SSB) or Channel State Information Reference Signal (CSI-RS) and determines a random access preamble based on the selected SSB or CSI-RS.

[0146] The terminal device sends message 1 (Msg1) to the base station. Message 1 includes a random access preamble sequence.

[0147] S202, The base station sends message 2 to the terminal device.

[0148] After detecting the random access preamble sequence sent by the terminal device, the base station sends a random access response (RAR) to the terminal device. The RAR can be message 2 (Msg2).

[0149] RAR is scheduled using a Physical Downlink Control Channel (PDCCH) scrambled with a Random Access Radio Network Temporary Identifier (RA-RNTI).

[0150] The RAR can include Timing Advance Command (TA), Uplink Grant (UL Grant), and Temporary C-RNTI. The TA command is used to adjust the UE's transmission time to ensure uplink synchronization. The uplink grant can carry resources for the terminal device to send message 3 (Msg3). The temporary identifier is used by UEs without a C-RNTI to receive message 4 (Msg4).

[0151] S203, The terminal device sends message 3 to the base station.

[0152] The terminal device uses the uplink authorization in message 2 to send message 3.

[0153] For terminal devices in a non-connected state, message 3 may include a Radio Resource Control Common Control Channel (RRC CCCH) message. The RRC CCCH message can be an RRC Setup Request, an RRC Resume Request, or an RRC Resume Request 1. Hereinafter, the RRC Resume Request and RRC Resume Request 1 will be collectively referred to as the RRC Resume Request.

[0154] Some of the information carried in message 3 (e.g., the device identifier of the terminal device) can be used for conflict resolution.

[0155] S204, The base station sends message 4 to the terminal device.

[0156] If the contention resolution identifier included in message 4 is the same as the device identifier of the terminal device, then the terminal device can determine that the contention resolution was successful.

[0157] Figure 3 This is a flowchart illustrating another random access method provided in an embodiment of this application. Please refer to... Figure 3 The method may include:

[0158] S301, The terminal device sends message A to the base station.

[0159] The terminal device transmits a random access preamble on the Physical Random Access Channel (PRACH) and a payload on the Physical Uplink Shared Channel (PUSCH). The transmission of the random access preamble and the payload by the terminal device can be collectively referred to as transmitting message A.

[0160] For inactive or idle terminal devices, the payload typically includes an RRC message. An RRC message can be, for example, an RRC Setup Request or an RRC Resume Request.

[0161] For connected terminal devices, the payload may include uplink data.

[0162] S302, The base station sends message B to the terminal device.

[0163] After the base station detects the random access preamble and payload, it can send message B to the terminal device.

[0164] Message B may include RAR and conflict resolution information. RAR may include TA commands and uplink authorization. Conflict resolution information may include a contention resolution identifier.

[0165] 2. If an inactive terminal device needs to send uplink data, the terminal device can initiate an RRC recovery request to restore the connected state.

[0166] The following is combined with Figure 4 This section explains the process of a terminal device requesting RRC recovery.

[0167] Figure 4 This is a flowchart illustrating an RRC recovery method provided in an embodiment of this application. Please refer to... Figure 4 The method may include:

[0168] S401. The terminal device sends an RRC recovery request to the new base station.

[0169] S402. The new base station sends a terminal device context acquisition request to the original base station.

[0170] After receiving the RRC recovery request sent by the terminal device, the new base station can send a terminal device context acquisition request to the original base station to request the acquisition of the terminal device's context.

[0171] S403: The original base station sends a successful response to the new base station regarding the acquisition of the terminal device context.

[0172] The successful acquisition of the terminal device context response may include the context of the terminal device.

[0173] S404. The new base station sends an RRC recovery response to the terminal equipment.

[0174] S405. The terminal device sends an RRC recovery completion message to the new base station.

[0175] The RRC recovery complete message indicates that the RRC recovery process has been successful.

[0176] The terminal device can update the connection status based on the RRC recovery response and can send an RRC recovery completion message to the new base station.

[0177] based on Figure 4 The provided solution allows the new base station to instruct the terminal device to re-establish an RRC connection if the new base station fails to obtain the terminal device's context from the original base station. The following section combines... Figure 5 This further explains the process of the terminal device requesting RRC recovery.

[0178] Figure 5 This is a flowchart illustrating another RRC recovery method provided in an embodiment of this application. Please refer to... Figure 5 The method may include:

[0179] S501, The terminal device sends an RRC recovery request to the new base station.

[0180] S502, The new base station sends a terminal device context acquisition request to the original base station.

[0181] S503: The original base station sends a terminal device context acquisition failure response to the new base station.

[0182] If the original base station is unable to find the context of the terminal device, or if the search for the terminal device's context fails, the original base station can send a terminal device context retrieval failure response to the new base station.

[0183] The Terminal Device Context Acquisition Failure Response indicates that the terminal device context could not be acquired.

[0184] S504. The new base station sends an RRC connection establishment message to the terminal device.

[0185] If the new base station cannot obtain the context of the terminal device from the original base station, the new base station can send an RRC connection establishment message to the terminal device.

[0186] RRC connection establishment messages can be used to instruct terminal devices to re-establish RRC connections.

[0187] Third, inactive terminal devices can also transmit data in an inactive state, which can be called small data transmission (SDT).

[0188] 1. The two implementation methods of SDT can include: Random Access SDT (RA-SDT) and Configured Grant SDT (CG-SDT).

[0189] RA-SDT method: In the traditional four-step or two-step Random Access Channel (RACH) process, the terminal device can carry data in addition to sending an RRC message in message 3 or message A. This method can be called RA-SDT.

[0190] CG-SDT method: If the terminal device's timing advance (TA) is valid, the terminal device can directly send data using the dedicated resources pre-allocated by the network (Configured Grant Type 1 resources) instead of sending a random access preamble. This method is called CG-SDT.

[0191] 2. SDT resource configuration

[0192] When a base station migrates a terminal device to an inactive state via an RRC Release message, it configures certain conditions that allow the use of SDT, such as data volume thresholds and allowed radio bearers (RBs).

[0193] RA-SDT resources are configured through system messages for each cell and have different signal thresholds. If CG-SDT is used, the base station will configure the corresponding CG resources, the threshold range for Reference Signal Received Power (RSRP) variation, and the signal threshold used by the SSB, etc.

[0194] 3. SDT Usage Process

[0195] When an inactive terminal device needs to send data, it can determine whether the data to be sent meets the usage conditions of SDT resources.

[0196] If the data to be sent does not meet the usage conditions of SDT resources, the terminal device can use non-SDT RACH resources for data transmission.

[0197] If the data to be sent meets the usage conditions of SDT resources, the terminal device can further determine whether the data to be sent meets the usage conditions of CG-SDT. If the data to be sent meets the usage conditions of CG-SDT, the terminal device can send the data via CG-SDT. If the data to be sent does not meet the usage conditions of CG-SDT, the terminal device can send the data via RA-SDT.

[0198] 4. The SDT method will be explained below.

[0199] (1) First, the method of sending data by the terminal device via SDT in the scenario where the terminal device needs to send data will be explained. The scenario where the terminal device needs to send data can also be called the Mobile Originated (MO) scenario.

[0200] Figure 6 This is a schematic diagram of an SDT transmission process provided in an embodiment of this application. Please refer to [link / reference]. Figure 6 The method includes:

[0201] S601. The terminal device sends an RRC recovery request to the new base station, carrying uplink small data packets and / or uplink small data transmission signaling.

[0202] Uplink small data packets can be the data that the terminal device needs to send.

[0203] Uplink small data transmission signaling can carry data sent by terminal devices through relevant transmission signaling.

[0204] S602. The new base station sends a terminal device context acquisition request to the original base station.

[0205] The terminal device context acquisition request may include an SDT indication.

[0206] SDT indication can be used to indicate that a terminal device needs to send data via SDT.

[0207] S603: The original base station sends a successful response to the new base station regarding the acquisition of the terminal device context.

[0208] The successful acquisition of the terminal device context response may include the context of the terminal device.

[0209] S604. The new base station is determined to transmit small data packets in an inactive state.

[0210] After receiving the context from the terminal device, the new base station can determine whether to transmit small data packets in the inactive state.

[0211] It should be noted that the specific process of transmitting small data packets in the inactive state in this embodiment of the application will not be described in detail.

[0212] (2) Next, the method of receiving data by the terminal device via SDT in scenarios where the terminal device needs to receive data will be explained. The scenario where the terminal device needs to receive data can also be called the Mobile Terminated (MT) scenario.

[0213] Figure 7 This is a schematic diagram of another SDT transmission process provided in an embodiment of this application. Please refer to... Figure 7 The method includes:

[0214] S701, the core network element sends downlink data to the original base station.

[0215] Core network elements can be User Plane Function (UPF) network elements or Access and Mobility Management Function (AMF) network elements, etc.

[0216] Downlink data can be data to be sent to the terminal device.

[0217] S702, original base station cached downlink data.

[0218] S703, the original base station sends a RAN paging message to the new base station.

[0219] RAN paging messages are used to instruct new base station paging terminal equipment.

[0220] RAN paging messages may include MT-SDT indications.

[0221] The MT-SDT indicator can be used to indicate that the terminal device needs to receive data via SDT.

[0222] S704, the new base station sends a paging message to the terminal equipment.

[0223] Paging messages are used to page terminal equipment. Paging messages may include MT-SDT indications.

[0224] S705, The terminal device determines that it receives downlink data in an inactive state.

[0225] It should be noted that the specific process of the terminal device receiving downlink data in the inactive state is not described in the embodiments of this application. In the above communication system, if the terminal device needs to receive downlink data, the original base station can send a RAN paging message to the new base station so that the new base station can page the terminal device.

[0226] Currently, the original base station and the new base station can communicate via the Xn interface, and the Xn interface can be used to instruct the new base station to page the terminal device. However, if the original base station and the new base station do not have an Xn interface, or if the Xn interface of the original base station and the new base station malfunctions and cannot transmit information, or if the connection of the Xn interface of the original base station and the new base station is released or disconnected, the original base station cannot instruct the new base station to page the terminal device, resulting in poor communication flexibility.

[0227] The method described in this application will now be illustrated through specific embodiments. It should be noted that the following embodiments may exist independently or in combination with each other; identical or similar content will not be repeated in different embodiments.

[0228] Figure 8 This is a flowchart illustrating a communication method provided in an embodiment of this application. Please refer to [link / reference]. Figure 8 The method may include:

[0229] S801, The first network device sends a first message to the second network device.

[0230] Correspondingly, the second network device receives the first message sent by the first network device.

[0231] The first message is used to instruct the second network device to page the terminal device.

[0232] In some embodiments, the first message may be a RAN paging message.

[0233] The terminal device can be an inactive terminal device.

[0234] The first network device can be a network element of the core network.

[0235] In some embodiments, the first network device may be an AMF network element.

[0236] In some embodiments, the first network device may be a UPF network element.

[0237] The second network device can be the base station selected by the terminal device after cell reselection.

[0238] It should be noted that before the cell reselection occurs, the base station providing services to the terminal device can be referred to as the third network device. In this embodiment, there is no Xn interface between the third network device and the second network device, or the Xn interface between the third network device and the second network device is faulty, or the Xn interface between the third network device and the second network device has been released.

[0239] In some embodiments, the first network device may send a first message to the second network device through a Next Generation (NG) interface.

[0240] In this embodiment, the first network device stores data to be transmitted to the terminal device. The first network device can generate a first message and send the first message to the second network device.

[0241] It should be noted that with the introduction of the enhanced Discontinuous Reception (DRX) mechanism, the paging period is further lengthened, allowing the data to be transmitted to be buffered in the first network device. Based on the DRX parameters provided by the access network device, the first network device can send the data to be transmitted to the access network device within the time frame during which the terminal device can receive paging requests, thus triggering paging of the terminal device. This operation can be called Core Network Mobility Termination Buffering (CNMT buffering).

[0242] It should be noted that if the terminal device can perform SDT transmission, the data to be transmitted to the terminal device can be transmitted via SDT. If the terminal device cannot perform SDT transmission, the data to be transmitted to the terminal device can be transmitted via a non-SDT method.

[0243] Specifically, the third network device can determine whether the terminal device can perform SDT transmission based on the radio bearer information established by the terminal device. For example, the third network device can... Figure 1 The original base station is shown. The third network device can also indicate to the first network device whether the terminal device can perform SDT transmission in the following ways:

[0244] Method 1: The third network device can send indication information to the first network device. The indication information can explicitly indicate that the terminal device cannot perform SDT transmission; or, the indication information can implicitly indicate that the terminal device cannot perform SDT transmission by not carrying an SDT transmission indication.

[0245] Method 2: The third network device can send the Quality of Service (QoS) parameters of the data packets used by the terminal device for SDT transmission to the first network device. The first network device can then determine whether the terminal device is capable of SDT transmission based on these parameters.

[0246] In some embodiments, the data to be transmitted can be transmitted via SDT, and the first message may carry an MT-SDT indication.

[0247] In some embodiments, the data to be transmitted can be transmitted in a non-SDT manner, and the first message may not carry an MT-SDT indication.

[0248] It should be noted that the third network device and the first network device can communicate via the NG interface.

[0249] It should be noted that before the first network device sends the first message to the second network device, it needs to identify the second network device. The first network device can identify the second network device in at least the following ways:

[0250] Method 1: The first network device can determine the second network device based on the instructions of the third network device.

[0251] In this method, the first network device can receive a second message sent by the third network device, the second message including the identifier of the second network device. The first network device can identify the second network device based on the identifier of the second network device.

[0252] The second message can be a signaling message sent by a third network device to a first network device. For example, the second message can be an N2 message. That is, the signaling message that the third network device can send to the first network device can carry the identifier of the second network device.

[0253] It should be noted that when an inactive terminal device moves within the RAN-based Notification Area (RNA), it does not need to report its location change to the base station. The third network device can determine the second network device according to a preset method and can send a second message to the first network device, which may include the identifier of the second network device.

[0254] For example, the Access and Mobility Management Function (AMF) network element can maintain the location information of terminal devices and the coverage information of base stations. A default approach could be that the third network device obtains the identifier of the second network device from the AMF network element.

[0255] It should be noted that this embodiment is only an example to illustrate the preset method and does not constitute a limitation on the technical solution provided in the embodiments of this application.

[0256] Method 2: The first network device can determine the second network device on its own.

[0257] In this method, the first network device can determine the second network device based on the RAN-based Notification Area (RNA) or Tracking Area (TA).

[0258] S802, the second network device sends a paging message corresponding to the first message to the terminal device.

[0259] The paging message corresponding to the first message can also be called a paging message.

[0260] The paging message corresponding to the first message can be used for paging terminal equipment.

[0261] In the communication method provided in this embodiment, the first network device can send a first message to the second network device, and the second network device can send a paging message corresponding to the first message to the terminal device. In this method, the second network device does not need to receive RAN paging messages through the Xn interface, solving the problem that the second network device cannot receive RAN paging messages when the Xn interface is not available, thus improving communication flexibility.

[0262] Based on the above embodiments, the first network device can also forward the first message to the second network device. The following is in conjunction with... Figure 9 The communication method provided in the embodiments of this application will be further described.

[0263] Figure 9 This is a flowchart illustrating another communication method provided in an embodiment of this application. Please refer to... Figure 9 The method may include:

[0264] S901, The first network device receives the first message sent by the third network device.

[0265] In this embodiment, the third network device stores data to be transmitted to the terminal device. The third network device can generate a first message.

[0266] In some embodiments, the first message may be a RAN paging message.

[0267] In some embodiments, the first message includes the identifier of the second network device. The RAN paging message can be in the form of a container, which may contain the content of the RAN paging message and may carry the identifier of the second network device outside the container.

[0268] The identifier for the second network device can be the Global RAN Node ID, or other information used to identify the second network device.

[0269] S902, The first network device sends a first message to the second network device.

[0270] In this embodiment, after receiving the first message, the first network device can parse the identifier of the second network device carried outside the container in the first message, and can send the first message to the second network device according to the identifier of the second network device.

[0271] S903, the second network device sends a paging message corresponding to the first message to the terminal device.

[0272] In the communication method provided in this embodiment, the first network device can receive a first message sent by the third network device and can also send a first message to the second network device. The second network device can send a paging message corresponding to the first message to the terminal device. In the above method, the third network device does not need to communicate with the second network device, which solves the problem that the second network device cannot receive RAN paging messages when there is no Xn interface between the second and third network devices, thus improving communication flexibility.

[0273] Based on any of the above embodiments, the second network device can also receive a response message corresponding to a paging message sent by the terminal device, and can obtain the context of the terminal device from the third network device through the first network device.

[0274] The following section uses the example of the first network device generating the first message to illustrate the process by which the second network device obtains the context of the terminal device.

[0275] Figure 10 This is a flowchart illustrating another communication method provided in an embodiment of this application. Please refer to... Figure 10 The method may include:

[0276] S1001, The first network device sends a first message to the second network device.

[0277] S1002, The second network device sends a paging message corresponding to the first message to the terminal device.

[0278] It should be noted that the specific implementation methods of S1001-S1002 can be found in S801-S802, and will not be repeated here.

[0279] S1003, The second network device receives the response message corresponding to the paging message sent by the terminal device.

[0280] The response message corresponding to the paging message includes the identifier of the third network device, which is a device that stores the terminal device context.

[0281] In some embodiments, the response message corresponding to the paging message can be an RRC recovery request.

[0282] S1004, The second network device sends a third message to the first network device.

[0283] The third message is used to request the context of the terminal device, and the third message includes the identifier of the third network device.

[0284] In some embodiments, the third message may also be referred to as a retrieve ue context request.

[0285] In some embodiments, the second network device may send a third message to the first network device via the NG interface.

[0286] S1005, The first network device sends a third message to the third network device.

[0287] In some embodiments, the first network device may send a third message to the third network device via the NG interface.

[0288] S1006, The third network device sends the context of the terminal device to the first network device.

[0289] In response to a third message, the third network device can send the context of the terminal device to the first network device.

[0290] S1007, The first network device sends the context of the terminal device to the second network device.

[0291] After obtaining the context of the terminal device, the first network device can send the context of the terminal device to the second network device.

[0292] In the communication method provided in this embodiment, a first network device can send a first message to a second network device; the second network device can send a paging message corresponding to the first message to a terminal device, receive a response message corresponding to the paging message sent by the terminal device, and send a third message to the first network device; the first network device can send a third message to a third network device, receive the context of the terminal device sent by the third network device, and send the context of the terminal device to the second network device. In this method, the second network device does not need to receive RAN paging messages through the Xn interface, solving the problem that the second network device cannot receive RAN paging messages when there is no Xn interface between the second and third network devices, thus improving communication flexibility. Furthermore, in this method, when there is no Xn interface between the second and third network devices, the second network device can obtain the context of the terminal device through the first network device without re-establishing an RRC connection with the terminal device, resulting in lower data transmission latency for the terminal device.

[0293] The following section uses the example of a third network device generating a first message to illustrate the process by which a second network device obtains the context of a terminal device.

[0294] Figure 11 This is a flowchart illustrating another communication method provided in an embodiment of this application. Please refer to... Figure 11 The method may include:

[0295] S1101, The first network device receives the first message sent by the third network device.

[0296] S1102, The first network device sends a first message to the second network device.

[0297] S1103, The second network device sends a paging message corresponding to the first message to the terminal device.

[0298] It should be noted that the specific implementation methods of S1101-S1103 can be found in S901-S903, and will not be repeated here.

[0299] S1104. The second network device receives the response message corresponding to the paging message sent by the terminal device.

[0300] S1105, The second network device sends a third message to the first network device.

[0301] S1106, The first network device sends a third message to the third network device.

[0302] S1107, The third network device sends the context of the terminal device to the first network device.

[0303] S1108, The first network device sends the context of the terminal device to the second network device.

[0304] It should be noted that the specific implementation methods of S1104-S1108 can be found in S1003-S1007, and will not be repeated here.

[0305] In the communication method provided in this embodiment, the first network device can receive a first message sent by the third network device and can also send a first message to the second network device; the second network device can send a paging message corresponding to the first message to the terminal device, can receive a response message corresponding to the paging message sent by the terminal device, and can also send a third message to the first network device; the first network device can send a third message to the third network device, can receive the context of the terminal device sent by the third network device, and can also send the context of the terminal device to the second network device. In the above method, the second network device does not need to receive RAN paging messages through the Xn interface, solving the problem that the second network device cannot receive RAN paging messages when there is no Xn interface between the second and third network devices, thus improving communication flexibility. Furthermore, in the above method, when there is no Xn interface between the second and third network devices, the second network device can obtain the context of the terminal device through the first network device without needing to re-establish an RRC connection with the terminal device, resulting in lower data transmission latency for the terminal device.

[0306] Based on any of the above embodiments, if the terminal device needs to send uplink data, the terminal device can send an RRC recovery request to the second network device. The second network device can obtain the context of the terminal device from the third network device through the first network device. Below, in conjunction with... Figure 12 The communication method provided in the embodiments of this application will be further described.

[0307] Figure 12 This is a flowchart illustrating another communication method provided in an embodiment of this application. Please refer to... Figure 12 The method may include:

[0308] S1201, The terminal device sends an RRC recovery request to the second network device.

[0309] S1202, The second network device sends a third message to the first network device.

[0310] S1203, The first network device sends a third message to the third network device.

[0311] S1204, The third network device sends the context of the terminal device to the first network device.

[0312] S1205, The first network device sends the context of the terminal device to the second network device.

[0313] It should be noted that the specific implementation methods of S11202-S1205 can be found in S1004-S1007, and will not be repeated here.

[0314] In the communication method provided in this embodiment, when a terminal device needs to send data to the network, it can send an RRC recovery request to a second network device; the second network device can send a third message to a first network device; the first network device can send a third message to a third network device, receive the context of the terminal device sent by the third network device, and send the context of the terminal device to the second network device. In this method, the second network device can obtain the context of the terminal device from the third network device through the first network device, solving the problem that the second network device cannot obtain the context of the terminal device when there is no Xn interface between the second and third network devices, thus improving communication flexibility.

[0315] Figure 13 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device provided in this embodiment can be in the form of software and / or hardware. The communication device provided in this embodiment can be a network device, or a chip or chip module in a network device.

[0316] Please see Figure 13 The communication device 10 provided in this embodiment may include a transmitting module 11 and a receiving module 12. The communication device will be described in detail below with several specific examples, considering different application scenarios.

[0317] In one example, the communication device of this embodiment is applied to a first network device. In this case,

[0318] The sending module 11 is used to send a first message, which is used to instruct the second network device to page the terminal device. The first message is a Radio Access Network (RAN) paging message.

[0319] In one possible implementation,

[0320] The receiving module 12 is used to receive a second message, the second message including the identifier of the second network device.

[0321] In one possible implementation,

[0322] The first network device stores data to be transmitted to the terminal device.

[0323] In one possible implementation,

[0324] The data to be transmitted is transmitted via Non-Small Data Transmission (SDT).

[0325] In one possible implementation,

[0326] The receiving module 12 is further configured to receive the first message, wherein the first message includes the identifier of the second network device.

[0327] In one possible implementation,

[0328] The third network device stores the data to be transmitted to the terminal device. The third network device is a device that stores the context of the terminal device.

[0329] In one possible implementation,

[0330] The receiving module 12 is further configured to receive a third message, the third message being used to request the context of the terminal device, the third message including the identifier of a third network device, the third network device being a device that stores the context of the terminal device.

[0331] The sending module 11 is also used to send the third message.

[0332] In one possible implementation,

[0333] The receiving module 12 is further configured to receive the context of the terminal device;

[0334] The sending module 11 is also used to send the context of the terminal device.

[0335] In one possible implementation,

[0336] The first network device is an Access and Mobility Management Function (AMF) network element or a User Plane Function (UPF) network element.

[0337] The communication device provided in this application embodiment can execute the communication method executed by the first network device in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0338] In another example, the communication device provided in this embodiment can be applied to a second network device. In this case:

[0339] The receiving module 12 is used to receive a first message, which is used to instruct the second network device to page the terminal device, and the first message is a Radio Access Network (RAN) paging message.

[0340] The sending module 11 is used to send the paging message corresponding to the first message.

[0341] In one possible implementation,

[0342] The receiving module 12 is further configured to receive a response message corresponding to the paging message, wherein the response message corresponding to the paging message includes an identifier of a third network device, and the third network device is a device that stores the context of the terminal device.

[0343] In one possible implementation,

[0344] The response message corresponding to the paging message is a Radio Resource Control (RRC) Recovery Request.

[0345] In one possible implementation,

[0346] The sending module 11 is further configured to send a third message, the third message being used to request the context of the terminal device, the third message including the identifier of the third network device;

[0347] The receiving module 12 is also used to receive the context of the terminal device.

[0348] The communication device provided in this application embodiment can execute the communication method executed by the second network device in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0349] In yet another example, the communication device provided in this embodiment can be applied to a third network device. In this case:

[0350] The sending module 11 is used to send a first message, the first message including the identifier of the second network device, the first message being used to instruct the second network device to page the terminal device, and the first message being a Radio Access Network (RAN) paging message.

[0351] In one possible implementation,

[0352] The third network device stores data to be transmitted to the terminal device.

[0353] In one possible implementation,

[0354] The receiving module 12 is used to receive a third message, the third message being used to request the context of the terminal device, wherein the third network device is a device that stores the context of the terminal device.

[0355] The sending module 11 is also used to send the context of the terminal device.

[0356] The communication device provided in this application embodiment can execute the communication method executed by the third network device in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0357] Figure 14 This is a schematic diagram of the structure of a network device provided in an embodiment of this application. The network device can be, for example, the first network device, the second network device, or the third network device mentioned above. Please refer to... Figure 14The network device 20 includes a transceiver 21, a memory 22, and a processor 23. The transceiver 21 may include a transmitter and / or a receiver. The transmitter may also be referred to as a transmitter, transmitter port, or transmitter interface, etc., and the receiver may also be referred to as a receiver, receiver port, or receiver interface, etc. Exemplarily, the transceiver 21, memory 22, and processor 23 are interconnected via a bus 24.

[0358] Memory 22 is used to store program instructions;

[0359] The processor 23 is used to execute the program instructions stored in the memory to cause the network device 20 to perform any of the communication methods shown above.

[0360] The transceiver 21 is used to perform the transmit and receive functions of the network device 20 in the above communication method.

[0361] The network device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0362] This application provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the above-described method when executed by a processor.

[0363] This application embodiment may also provide a computer program product, including a computer program that, when executed by a processor, can implement the above-described method.

[0364] All or part of the steps in the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a readable memory. When the program is executed, it performs the steps of the above-described method embodiments; and the aforementioned memory (storage medium) includes: read-only memory (ROM), random access memory (RAM), flash memory, hard disk, solid-state drive, magnetic tape, floppy disk, optical disk, and any combination thereof.

[0365] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0366] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0367] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0368] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include these modifications and variations.

[0369] In this application, the term "comprising" and its variations can refer to non-limiting inclusion; the term "or" and its variations can refer to "and / or". The terms "first", "second", etc., in this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. In this application, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

Claims

1. A communication method, characterized in that, Applied to a first network device, the method includes: Send a first message, which is used to instruct the second network device to page the terminal device. The first message is a Radio Access Network (RAN) paging message.

2. The method according to claim 1, characterized in that, The method further includes: Receive a second message, which includes the identifier of the second network device.

3. The method according to claim 1 or 2, characterized in that, The first network device stores data to be transmitted to the terminal device.

4. The method according to claim 3, characterized in that, The data to be transmitted is transmitted via Non-Small Data Transmission (SDT).

5. The method according to claim 1, characterized in that, The method further includes: The first message is received, and the first message includes the identifier of the second network device.

6. The method according to claim 5, characterized in that, The third network device stores the data to be transmitted to the terminal device. The third network device is a device that stores the context of the terminal device.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: A third message is received, the third message being used to request the context of the terminal device, the third message including the identifier of a third network device, the third network device being a device that stores the context of the terminal device; Send the third message.

8. The method according to claim 7, characterized in that, The method further includes: Receive the context of the terminal device; Send the context of the terminal device.

9. The method according to any one of claims 1-8, characterized in that, The first network device is an Access and Mobility Management Function (AMF) network element or a User Plane Function (UPF) network element.

10. A communication method, characterized in that, Applied to a second network device, the method includes: Receive a first message, the first message being used to instruct the second network device to page the terminal device, the first message being a Radio Access Network (RAN) paging message; Send the paging message corresponding to the first message.

11. The method according to claim 10, characterized in that, The system receives a response message corresponding to the paging message, wherein the response message includes the identifier of a third network device, and the third network device is a device that stores the context of the terminal device.

12. The method according to claim 11, characterized in that, The response message corresponding to the paging message is a Radio Resource Control (RRC) Recovery Request.

13. The method according to claim 11 or 12, characterized in that, The method further includes: Send a third message, the third message being used to request the context of the terminal device, the third message including the identifier of the third network device; Receive the context of the terminal device.

14. A communication method, characterized in that, Applied to a third network device, the method includes: Send a first message, which includes the identifier of the second network device. The first message is used to instruct the second network device to page the terminal device. The first message is a Radio Access Network (RAN) paging message.

15. The method according to claim 14, characterized in that, The third network device stores data to be transmitted to the terminal device.

16. The method according to any one of claims 14 or 15, characterized in that, Receive a third message, the third message being used to request the context of the terminal device, the third network device being a device that stores the context of the terminal device; Send the context of the terminal device.

17. A communication device, characterized in that, Applied to a first network device, the apparatus includes: a transmitting module, wherein, The sending module is used to send a first message, which is used to instruct the second network device to page the terminal device. The first message is a Radio Access Network (RAN) paging message.

18. A communication device, characterized in that, Applied to a second network device, the device includes: a receiving module and a transmitting module, wherein, The receiving module is used to receive a first message, which is used to instruct the second network device to page the terminal device, and the first message is a Radio Access Network (RAN) paging message. The sending module is used to send the paging message corresponding to the first message.

19. A communication device, characterized in that, Applied to a third network device, the device includes: a transmitting module, wherein, The sending module is used to send a first message, the first message including the identifier of the second network device, the first message being used to instruct the second network device to page the terminal device.

20. A network device, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the method of any one of claims 1 to 9, or the method of any one of claims 10 to 13, or the method of any one of claims 14 to 16.

21. A non-transitory computer-readable storage medium storing computer instructions, characterized in that, in, The computer instructions are used to cause the computer to perform the method according to any one of claims 1 to 9, or any one of claims 10 to 13, or any one of claims 14 to 16.

22. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements any one of claims 1 to 9, or any one of claims 10 to 13, or any one of claims 14 to 16.

Images