A communication method and apparatus

Abstract

A communication method and device, the method comprising: a first access network device sending a first paging request to a first core network device, the first paging request comprising first paging area information and an identifier of a first terminal device, for requesting to page the first terminal device; the first core network device sending a second paging request to a second access network device, the second paging request comprising second paging area information and the identifier of the first terminal device, for requesting to page the first terminal device; and the second access network device sending a third paging request, the third paging request being used to page the first terminal device. In the method, the first access network device can trigger the first core network device to page the first terminal device, achieving enhancement of paging of a terminal device in an inactive state, thereby supporting no Xn interface connection or Xn interface failure between two base stations in an RNA, and enhancing the scalability of the network.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] Anchor base stations (e.g., base station 1) configure a radio access network notification area (RNA) for user equipment (UE) and store the UE's context. The radio access network (RAN) can paging UEs in an inactive state within the RNA. The paging UE can initiate an RRC resume procedure to transition from an inactive RRC state to a connected RRC state. The anchor base station refers to the last serving RAN node the UE was in when it was in the connected state.

[0003] After a UE enters the connected state in the cell of base station 1, base station 1 instructs the UE to switch from the RRC connected state to the RRC inactive state. The RRC inactive UE disconnects its RRC connection from base station 1, but base station 1 still stores the terminal device's context. If the RRC inactive UE moves to the coverage area of ​​base station 2 and initiates an RRC recovery request to base station 2, base station 2 needs to obtain the UE's context from base station 1 to restore the UE's RRC connection.

[0004] In the future, it will be possible to allow two base stations within the RNA configured for a UE to communicate without establishing an Xn interface connection. Therefore, enhancements are needed for the RRC inactive state, such as enhancements for paging of UEs in the RRC inactive state, to accommodate scenarios where two base stations within the RNA cannot communicate via the Xn interface. Summary of the Invention

[0005] This application provides a communication method and apparatus for enhancing paging of UEs in the RRC inactive state. Even if the base stations within the RNA cannot communicate with each other through the Xn interface, paging of UEs in the RRC inactive state can still be achieved, thereby reducing the latency of the UE entering the RRC connected state and saving power consumption in establishing the RRC connection.

[0006] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0007] Firstly, a communication method is provided, which can be applied to a core network device (hereinafter referred to as a core network device). Unless otherwise specified in this application, the core network device can be a core network element; or a module or unit used to perform some functions of the core network element (e.g., the core network device is a circuit or chip / chip system in the core network element); or the core network device can be a logical node, logical module, or software module that implements all or part of the functions of the core network element. In one example, the core network device is a core network element or a component in the core network element (e.g., a module, a system-on-chip (SoC) chip, or a system-in-package (SIP) chip). For ease of description, the following example uses the communication method provided in the first aspect applied to a first core network device, such as an access and mobility management function (AMF) entity.

[0008] The method includes: receiving a first paging request from a first access network device, and sending a second paging request to a second access network device. The first paging request is used to request paging of a first terminal device, and the first paging request includes first paging area information and an identifier of the first terminal device, wherein at least one area indicated by the first paging area information includes the area of ​​the second access network device. The second paging request is used to request paging of the first terminal device.

[0009] In this method, when the first core network device receives a first paging request from the first access network device, it triggers the sending of a second paging request to the second access network device to request paging of the first terminal device. This method supports cross-base station paging, ensuring successful paging even if the first terminal device moves into the coverage area of ​​other access network devices (such as the second access network device). Furthermore, triggering paging through the first core network device avoids the limitations of direct communication between access network devices, thus supporting the establishment of Xn interface connections between any two base stations within the RNA or supporting Xn interface failures between any two base stations within the RNA, further enhancing network stability and flexibility.

[0010] In one design, the second access network device and the first access network device cannot communicate based on a first interface, which is the communication interface between access network devices.

[0011] In this design, the second access network device and the first access network device may not be able to communicate directly, which allows the first terminal device to remain inactive in a larger area, thereby reducing the latency for the UE to enter the RRC connection state, saving power consumption for establishing the RRC connection, and improving communication efficiency.

[0012] In one design, the first terminal device is identified as an inactive radio network temporary identifier (I-RNTI).

[0013] In this design, the I-RNTI is used as the paging identifier, enabling the first core network device to clearly identify that the first paging request is directed to the first terminal device in the RRC inactive state, and thus determine the identifier of the first terminal device carried in the second paging request. This design helps the first core network device accurately determine the content of the second paging request, improving paging efficiency.

[0014] In one design, the identifier of the first terminal device includes a first identifier and / or a second identifier. The first identifier is used to identify the first terminal device in the access network, and the second identifier is used to identify the first terminal device in the core network. For example, the first identifier includes (or is) the NG-RAN UE NGAP ID, and the second identifier includes (or is) the AMF UE NGAP ID.

[0015] In this design, the first core network device can directly locate the context of the first terminal device through the first identifier and / or the second identifier, without the need for additional signaling interaction to determine the identity of the first terminal device, thus minimizing the delay and signaling overhead of the paging process.

[0016] In one design, the second paging request includes second paging area information and an identifier of the first terminal device. The second paging area information indicates at least one area provided by a second access network device. The identifier of the first terminal device includes the first terminal device's I-RNTI or a 5G (5th generation, 5G) system temporary mobile subscriber identity, abbreviated as 5G-S-TMSI.

[0017] In this design, the second paging request sent by the first core network device to the second access network device may include either I-RNTI or 5G-S-TMSI. I-RNTI indicates that the request is for a first terminal device that is in an inactive state. 5G-S-TMSI can also uniquely identify the first terminal device, eliminating the need for additional signaling interaction to determine its identity, thus reducing paging process latency and signaling overhead.

[0018] In one design, the second paging request is used to instruct the first terminal device to perform the RRC connection restoration procedure.

[0019] In this design, the second paging request is also used to instruct the first terminal device to perform the RRC connection recovery process, thereby avoiding the first terminal device receiving the paging message and performing the RRC connection establishment process, and reducing the latency of the first terminal device entering the RRC connection state.

[0020] In one design, the second paging request includes the 5G-S-TMSI, and the identifier of the first terminal device in the first paging request includes a first identifier and / or a second identifier. The method further includes: determining the 5G-S-TMSI of the first terminal device based on the first identifier and / or the second identifier.

[0021] In this design, the first core network device can determine the identifier of the first terminal device in the second paging request based on the identifier of the first terminal device in the first paging request. For example, the first core network device can convert the first identifier and / or the second identifier into a 5G-S-TMSI and send it to the second access network device.

[0022] Secondly, a communication method is provided, which can be applied to a network-side device (hereinafter referred to as a network device). Unless otherwise specified in this application, the network device can be a network equipment; or a module or unit for performing some functions of the network equipment (e.g., the network device is a circuit or chip / chip system in the network equipment); or the network device can be a logical node, logical module, or software module that implements all or part of the functions of the network equipment. In one example, the network device is a network equipment or a component in the network equipment (e.g., a module, a communication module, a circuit or chip responsible for communication functions (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core)). For example, the network device is a central unit (CU), a distributed unit (DU), or a radio unit (RU) for implementing some functions of the network equipment. For ease of description, the following example uses the communication method provided in the second aspect applied to a first access network device.

[0023] The method includes: releasing a first terminal device to a Radio Resource Control (RRC) inactive state and sending a first paging request to a first core network device. The first paging request is used to request paging of the first terminal device, and the first paging request includes first paging area information and an identifier of the first terminal device. The first paging area information indicates at least one area that includes the area of ​​a second access network device.

[0024] In one design, the first terminal device is identified as I-RNTI.

[0025] In one design, the identifier of the first terminal device includes a first identifier and / or a second identifier. The first identifier is used to identify the first terminal device in the access network, and the second identifier is used to identify the first terminal device in the core network.

[0026] The beneficial effects of the second aspect and its various designs can be referred to the aforementioned beneficial effects of the first aspect and its various designs, and will not be repeated here.

[0027] Thirdly, a communication method is provided that can be applied to a network-side device (hereinafter referred to as a network device). For details regarding the network device, please refer to the relevant description of the network device in the aforementioned second aspect. For ease of description, the following example uses the communication method provided in the third aspect applied to a second access network device.

[0028] The method includes: receiving a second paging request from a first core network device, and sending a third paging request based on the second paging request. The second paging request is used to request paging of a first terminal device. The third paging request is used to paging of the first terminal device, and the third paging request is also used to instruct the first terminal device to perform an RRC connection recovery procedure.

[0029] In this method, the second access network device, triggered by the first core network device, pages the first terminal device. Based on the second paging request, the second access network device determines that the purpose of paging the first terminal device is to instruct it to execute an RRC recovery procedure, thus determining a third paging request to instruct the first terminal device to execute the RRC connection recovery process. This method enhances the paging capability for terminal devices in an inactive RRC state. This enhancement supports pairwise base station connections within the RNA without the need to establish an Xn interface connection or if the Xn interface fails, thus improving network stability and flexibility.

[0030] In one design, the second paging request includes second area information and an identifier of the first terminal device. The second paging area information indicates at least one area provided by a second access network device. The identifier of the first terminal device includes either the I-RNTI or the 5G-S-TMSI of the first terminal device.

[0031] In one design, the third seeking request includes the 5G-S-TMSI of the first terminal device.

[0032] The beneficial effects of the third aspect and its various designs can be referred to the aforementioned beneficial effects of the first aspect and its various designs, and will not be repeated here.

[0033] Fourthly, a communication method is provided, which can be applied to a terminal-side device (hereinafter referred to as a terminal device). Unless otherwise specified in this application, the terminal device can be a terminal equipment, or a component within a terminal equipment (e.g., a module, a communication module, a circuit or chip responsible for communication functions (such as a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core), or a logical node, logical module, or software capable of implementing all or part of the functions of a communication device. For ease of description, the following example uses the communication method provided in the fourth aspect applied to a first terminal device.

[0034] The method includes: receiving a third proclamation request from a second access network device, and sending an RRC recovery request to the second access network device. The third proclamation request is used to page a first terminal device. The third proclamation request includes the 5G-S-TMSI of the first terminal device, and the third proclamation request is also used to instruct the first terminal device to perform an RRC connection recovery procedure.

[0035] In this method, the third request includes 5G-S-TMSI, and the first terminal device determines to perform the RRC connection recovery procedure based on the third request. Unlike 5G-S-TMSI, which is only used for paging terminal devices in the idle state, this method enhances the paging capability for terminal devices in the RRC inactive state. This enhancement supports the establishment of Xn interface connections between pairs of base stations within the RNA or in the event of Xn interface failure, thereby enhancing network stability and flexibility.

[0036] Fifthly, embodiments of this application provide a communication method, which can be executed by a first access network device, a second access network device, a first core network device, and a first terminal device. The first access network device sends a first paging request to the first core network device. The first paging request requests paging of the first terminal device. The first paging request includes first paging area information and an identifier of the first terminal device. At least one area indicated by the first paging area information includes the area of ​​the second access network device. The first core network device sends a second paging request to the second access network device. The second paging request includes second paging area information and an identifier of the first terminal device, and requests paging of the first terminal device. At least one area indicated by the second paging area information includes the area of ​​the second access network device. The second access network device sends a third paging request, which requests paging of the first terminal device.

[0037] The beneficial effects of the fifth aspect and its various designs can be found in the first to fourth aspects and their respective designs mentioned above, and will not be repeated here.

[0038] Sixthly, embodiments of this application provide a communication device for performing the methods described in any of the first to fourth aspects and any of their designs. The beneficial effects can be found in the relevant descriptions of any of the first to fourth aspects, which will not be repeated here.

[0039] In one possible design, the communication device includes corresponding means, modules, or units for performing the methods of any of the first to fourth aspects. These modules, units, or means can be implemented in software, hardware, or a combination of both. For example, the communication device includes a processing module (sometimes also called a processing unit or processor) and / or input / output interfaces. Input / output interfaces include input interfaces and / or output interfaces, which can be interface circuits, output circuits, input circuits, pins, or related circuits. Optionally, the communication device also includes a transceiver module (sometimes also called a transceiver unit or transceiver). The transceiver module is capable of both transmitting and receiving functions. When the transceiver module performs the transmitting function, it can be called a transmitting module (sometimes also called a transmitting unit), and when it performs the receiving function, it can be called a receiving module (sometimes also called a receiving unit). The transmitting module and the receiving module can be the same functional module, referred to as the transceiver module, which performs both transmitting and receiving functions; or, the transmitting module and the receiving module can be different functional modules, with "transceiver module" being a collective term for these functional modules. These input / output interfaces and units (modules) can perform the corresponding functions in the method examples of any of the first to fourth aspects mentioned above. For details, please refer to the detailed description in the method examples, which will not be repeated here.

[0040] In one possible design, the processing module includes a baseband device, and the transceiver module includes a radio frequency device.

[0041] For example, when the communication device is used to implement the corresponding function in the method example of the first aspect, the transceiver module is used to receive a first paging request from a first access network device and send a second paging request to a second access network device. The first paging request is used to request paging of a first terminal device, and the first paging request includes first paging area information and an identifier of the first terminal device, wherein at least one area indicated by the first paging area information includes the area of ​​the second access network device. The second paging request is used to request paging of the first terminal device. The processing module is used to determine the second paging request.

[0042] When the communication device is used to implement the corresponding function in the method example of the second aspect, the transceiver module is used to release the first terminal device into the RRC inactive state and send a first paging request to the first core network device. The first paging request is used to request paging of the first terminal device, and the first paging request includes first paging area information and an identifier of the first terminal device. The first paging area information indicates at least one area that includes the area of ​​the second access network device. The processing module is used to determine the first paging request.

[0043] When the communication device is used to implement the corresponding function in the method example of the third aspect, the transceiver module is used to receive a second paging request from the first core network device and send a third paging request. The processing module is used to determine the third paging request based on the second paging request. The second paging request is used to request paging of the first terminal device. The third paging request is used to paging of the first terminal device, and the third paging request is also used to instruct the first terminal device to perform an RRC connection restoration procedure.

[0044] When the communication device is used to implement the corresponding function in the method example of the fourth aspect, the transceiver module is used to receive a third proclamation request from the second access network device and send an RRC recovery request to the second access network device. The third proclamation request is used to page the first terminal device. The third proclamation request includes the 5G-S-TMSI of the first terminal device, and the third proclamation request is also used to instruct the first terminal device to perform an RRC connection recovery procedure. The processing module is used to determine the RRC recovery request.

[0045] In a seventh aspect, embodiments of this application provide a communication device including a processor configured to execute the methods described in any of the first to fourth aspects and any design thereof. This application does not limit the specific type of processor. For example, the processor may be a baseband device, a central processing unit (CPU), or other specific integrated circuits. As another example, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0046] Optionally, the communication device further includes a communication interface. Optionally, the communication device also includes a memory for storing computer programs (also referred to as code or instructions), data, etc. The processor is coupled to the memory and the communication interface. When the processor reads the computer program, data, etc., from the memory, it causes any of the first to fourth aspects and any method in any of their designs to be executed.

[0047] In one design, the memory is located outside the communication device.

[0048] In one design, the memory is located within the communication device.

[0049] In one design, the processor and memory are integrated together.

[0050] Eighthly, embodiments of this application provide a chip system including a processor and a communication interface for implementing the methods described in any of the first to fourth aspects. Optionally, the chip system further includes a memory. The memory stores a computer program (also referred to as code or instructions). The processor retrieves and executes the computer program from the memory, causing a device equipped with the chip system to perform any of the first to fourth aspects and the methods in any of their designs. The chip system may be composed of chips or may include chips and other discrete devices.

[0051] Ninthly, embodiments of this application provide a communication device including an input / output interface and logic circuitry. The input / output interface is used for inputting and / or outputting information. The input / output interface may be an interface circuit, an output circuit, an input circuit, a pin, or related circuitry, etc. The logic circuitry is used to execute the methods described in any of the first to fourth aspects.

[0052] In one implementation of the ninth aspect, when the communication device is an access network device or a terminal device, the interface circuit can be a radio frequency processing chip in the access network device, and the processing circuit can be a baseband processing chip in the access network device or the terminal device.

[0053] In one implementation of the ninth aspect, when the communication device is a chip or chip system, the input circuit can be an input pin, the output circuit can be an output pin, and the logic circuit can be a transistor, gate circuit, flip-flop, or various other logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver; the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the input / output interface and the logic circuit.

[0054] The aforementioned communication device may be a first core network device as described in the first aspect. Alternatively, the communication device may be a means capable of supporting the first core network device in implementing the methods provided in the first aspect, for example, the communication device may be a chip or chip system in the first core network device. Alternatively, the aforementioned communication device may be a first access network device as described in the second aspect. Alternatively, the communication device may be a means capable of supporting the first access network device in implementing the methods provided in the second aspect, for example, the communication device may be a chip or chip system in the first access network device. Alternatively, the aforementioned communication device may be a second access network device as described in the third aspect. Alternatively, the communication device may be a means capable of supporting the second access network device in implementing the methods provided in the third aspect, for example, the communication device may be a chip or chip system in the second access network device. Alternatively, the aforementioned communication device may be a first terminal device as described in the fourth aspect. Alternatively, the communication device may be a means capable of supporting the first terminal device in implementing the methods provided in the fourth aspect, for example, the communication device may be a chip or chip system in the first core network device. Wherein, the chip may be a baseband chip and / or a radio frequency chip, and the chip system may be composed of chips or may include chips and other discrete devices.

[0055] In a tenth aspect, embodiments of this application provide a communication system comprising a first access device, a second access network device, a first core network device, and a first terminal device. The first core network device sends a first paging request to the second access network device, the first paging request being used to request paging of the first terminal device. The first paging request includes first paging area information and an identifier of the first terminal device, and the first paging area information indicates at least one area that includes the area of ​​the second access network device. The first core network device sends a second paging request to the second access network device, the second paging request including second paging area information and an identifier of the first terminal device, for requesting paging of the first terminal device. The second paging area information indicates at least one area that includes the area of ​​the second access network device. The second access network device sends a third paging request, the third paging request being used to paging the first terminal device. The terminal device receives the third paging request and executes an RRC (Restore Connection Control) procedure to restore connection.

[0056] In one design, the second access network device and the first access network device cannot communicate based on a first interface, which is the communication interface between access network devices.

[0057] In one design, the first terminal device is identified as I-RNTI.

[0058] In one design, the identifier of the first terminal device includes a first identifier and / or a second identifier. The first identifier is used to identify the first terminal device in the access network, and the second identifier is used to identify the first terminal device in the core network.

[0059] In one design, the second paging request includes second paging area information and an identifier of the first terminal device. The second paging area information indicates at least one area provided by a second access network device. The identifier of the first terminal device includes either its I-RNTI or 5G-S-TMSI.

[0060] In one design, the second paging request is used to instruct the first terminal device to perform the RRC connection restoration procedure.

[0061] In one design, the second paging request includes the 5G-S-TMSI, and the identifier of the first terminal device in the first paging request includes a first identifier and / or a second identifier. The first access network device further determines the 5G-S-TMSI of the first terminal device based on the first identifier and / or the second identifier.

[0062] Eleventhly, embodiments of this application provide a computer-readable storage medium for storing a computer program or instructions that, when executed, enable the methods described in any of the first to fourth aspects and any of their designs to be implemented.

[0063] In a twelfth aspect, embodiments of this application also provide a computer program product containing instructions that, when run on a computer, cause the methods described in any of the first to fourth aspects and any of their designs to be implemented.

[0064] The beneficial effects of the sixth to twelfth aspects mentioned above can be referenced to the beneficial effects of the first or third aspects and any one of their designs. Attached Figure Description

[0065] Figure 1 A flowchart illustrating the process of performing RRC connection restoration for a UE;

[0066] Figure 2 A schematic diagram of a network architecture for a communication system;

[0067] Figure 3 A flowchart illustrating the communication method provided in an embodiment of this application;

[0068] Figures 4-6 These are schematic diagrams of three structures of the communication device provided in the embodiments of this application. Detailed Implementation

[0069] In the embodiments of this application, "transmission" includes "sending" and / or "receiving." "Sending" and "receiving" indicate the direction of signal transmission. For example, "sending information to XX" can be understood as the destination of the information being XX, including direct sending as well as indirect sending through other units, modules, devices, or network elements. "Receiving information from YY" can be understood as the source of the information being YY, including receiving directly from YY via the air interface as well as receiving indirectly from YY via the air interface from other units or modules. "Sending" can also be understood as the "output" of a chip interface, and "receiving" can also be understood as the "input" of a chip interface. In other words, sending and receiving can occur between devices, such as between access network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via buses, traces, or interfaces.

[0070] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A / B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and / or c means the following combinations: a exists alone, b exists alone, c exists alone, a and b exist simultaneously, a and c exist simultaneously, b and c exist simultaneously, or a, b, and c exist simultaneously, where a, b, and c can be single or multiple.

[0071] In the embodiments of this application, "when," "if," and "if" all refer to the device taking corresponding actions under certain objective circumstances, not to a time limit, nor to requiring the device to perform a judgment action, nor implying any other limitations. Unless otherwise specified, "if" and "if" are interchangeable, and "when" and "in the case of" are interchangeable. "When" and "if" / "if" are interchangeable. "of," "corresponding, relevant," and "corresponding" can sometimes be used interchangeably, and it should be noted that their meanings are consistent when their differences are not emphasized. In addition, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0072] In this application's embodiments, ordinal numbers such as "first" and "second" are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. For example, "first paging request" and "second paging request" refer to two different paging requests, and do not indicate a difference in the priority or importance of these two paging requests.

[0073] The following explanations and descriptions of some of the uses or concepts involved in the embodiments of this application are provided to facilitate understanding of the solutions provided in the embodiments of this application.

[0074] (1) Access network equipment

[0075] Access network equipment refers to radio access network (RAN) equipment / RAN nodes. RAN and RAN are interchangeable; for ease of description, RAN will be used as an example below. RAN can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as a 5G / NR mobile communication system, or a future-oriented evolution system. RAN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), a virtualized RAN (vRAN), or a non-terrestrial network (NTN) (such as a satellite communication system). RAN can also be a communication system that integrates two or more of the above systems. RAN equipment can also be called a RAN node, RAN entity, or access node, etc.

[0076] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation nodeB (gNB), a satellite (or satellite base station), or a high-altitude platform station (HAPS), or base station equipment mounted on a satellite / HAPS, or a base station in a future mobile communication system. The satellite can include at least one of the following: a geostationary orbit (GEO) satellite or a non-geostationary orbit (NGEO) satellite. A non-geostationary orbit satellite can include at least one of the following: a medium Earth orbit (MEO) satellite or a low Earth orbit (LEO) satellite. There are no restrictions here. RAN nodes can also be macro base stations, micro base stations, indoor stations, relay nodes, donor / host nodes, or wireless controllers. RAN nodes can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in Vehicle-to-Everything (V2X) technology, the RAN node can be a roadside unit (RSU). The AP can serve as the central hub of this communication system, and can be a base station, router, gateway, repeater, communication server, switch, or bridge, etc., equipped with a Wi-Fi chip. RAN nodes can also be gateway stations (or ground stations, earth stations, signaling stations, gateways, or gateway stations). Notably, gNBs and next-generation radio access networks (NG-RAN) are interchangeable.

[0077] In another possible scenario, the RAN node can be a module or unit that performs some of the functions of the base station; or multiple RAN nodes can cooperate to assist terminal equipment in achieving wireless access, with different RAN nodes performing some of the functions of the base station. For example, the RAN node can be a CU, DU, or RU. The function of the CU can be implemented by a single entity or by different entities. For example, the function of the CU can be further divided, that is, the control plane and the user plane can be separated and implemented by different entities, namely the control plane CU entity (i.e., CU-control plane (CP) entity) and the user plane CU entity (i.e., CU-user plane (UP) entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the function of the RAN node. The CU and DU can be set up separately or included in the same network element, such as in the baseband unit (BBU). Any of the units among the CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented by software modules, hardware modules, or a combination of software modules and hardware modules.

[0078] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples.

[0079] The CU and DU can be configured according to the protocol layer functions of the wireless network they implement. For example, the CU can be configured to implement the functions of the Packet Data Convergence Protocol (PDCP) layer and higher protocol layers (such as the Radio Resource Control (RRC) layer and / or the Service Data Adaptation Protocol (SDAP) layer). The CU connects to network nodes such as the core network through interfaces, which can be E2 interfaces. Optionally, the CU can have some core network functions. The CU (e.g., the PDCP layer and higher) connects to the DU (e.g., the Radio Link Control (RLC) layer and lower layers) through interfaces. For example, the DU can be configured to implement the functions of protocol layers below the PDCP layer (e.g., RLC, MAC, and / or the Physical (PHY) layer). For specific descriptions of the above protocol layers, please refer to the relevant 3GPP technical specifications or the technical specifications of other applicable communication protocols.

[0080] The above division of CU and DU processing functions according to the protocol layer is merely an example; other division methods are also possible, and this application does not impose any restrictions.

[0081] For example, in one design, the CU or DU can be further divided into processing functions with protocol layers. In one design, some functions of the RLC layer and the protocol layer functions above the RLC layer are located in the CU, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer are located in the DU. In another possible design, the DU and RU cooperate to implement the PHY layer functions, or it can be described as moving some of the PHY layer functions of the DU to the RU. A DU can be connected to one or more RUs. The functions of the DU and RU can be configured in various ways depending on the design. For example, the DU is configured to implement baseband functions, and the RU is configured to implement mid-RF functions. As another example, the DU is configured to implement higher-level functions in the PHY layer, and the RU is configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions.

[0082] When the RAN is O-RAN, it can also have artificial intelligence (AI) capabilities. For example, O-RAN includes an intelligent controller. The intelligent controller can be a non-real-time RAN intelligent controller (RIC / non-RT RIC / NRTRIC) or a near-real-time RAN intelligent controller (RIC / nRT RIC / nRT RIC). A non-real-time RIC can be used to implement non-real-time intelligent management of RAN functions, enabling workflows including model training and updates, and guiding applications / functions in the nRT RIC based on policies. A near-real-time RIC can be used to implement near-real-time intelligent management of the RAN. Through data collection and related operations on the E2 interface, near-real-time control and optimization of O-RAN modules and resources are achieved.

[0083] (2) Terminal equipment

[0084] Terminal equipment refers to any device capable of communicating with a base station. It is also known as a terminal, terminal device, user equipment (UE), user terminal, mobile station, or mobile terminal. Examples of terminal equipment include: mobile phones, computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, stations (STA), robotic arms, cameras, robots, vehicles, drones, smart home devices, relays, and customer premises equipment (CPE). STAs can include Wi-Fi-enabled mobile phones, tablets, smart TVs, smart wearable devices, vehicle communication devices, routers, switches, and so on.

[0085] Furthermore, in this embodiment, the terminal device can also be a terminal device in an Internet of Things (IoT) system, such as a water meter or electricity meter. When the terminal device is applied to V2X, it can also be called a V2X device. All the terminal devices described above, if located on a vehicle (e.g., placed / installed inside the vehicle), can be considered in-vehicle terminal devices. In-vehicle terminal devices can be built into a vehicle's in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit as one or more components or units. The vehicle can implement the methods of this application through the built-in in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit. In-vehicle terminal devices can be vehicle equipment, in-vehicle modules, vehicles, in-vehicle units (on-board units, OBUs), remote sensing units (RSUs), in-vehicle infotainment systems (or in-vehicle transmission units) (telematics boxes, T-boxes), chips, or system-on-chips (SoCs), etc. These chips or SoCs can be installed in the vehicle, OBU, RSU, or T-box.

[0086] (3) Core Network

[0087] In this application, the core network may include equipment that processes and forwards user signaling and data. This includes, for example, AMF (Active Network Function) elements, Session Management Function (SMF) elements, and user plane gateways. The user plane gateway can be a server with functions such as mobility management, routing, and forwarding of user plane data, typically located on the network side, such as a User Plane Function (UPF) element. The core network may also include other network elements, which are not listed here.

[0088] In this application, the communication device used to implement the functions of the core network equipment can be referred to as a core network device. This core network device can be a core network element, a core network device, or a device capable of supporting the core network device or network element to implement the function, such as a chip system. This device can be installed in the core network device. In the technical solutions provided in the embodiments of this application, the core network device is used as an example to describe the technical solutions provided in the embodiments of this application. Additionally, a network element can also be referred to as an entity or functional entity. For example, an AMF network element can also be referred to as an AMF entity or an AMF functional entity. Optionally, the device name mentioned in the embodiments of this application can omit "network element". For example, AMF network element and AMF represent the same meaning. Furthermore, a network element / functional entity can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above-mentioned network element or functional entity can be implemented by one device, or by multiple devices, or can be different functional modules within one device. The embodiments of this application do not specifically limit this. In actual deployment, the above-mentioned network elements can be co-located.

[0089] (4) RRC status.

[0090] Terminal devices have three RRC states: RRC connected, RRC idle, and RRC inactive.

[0091] RRC Connection State: The terminal device has established an RRC connection with the network and can transmit data. RRC connection state can also be simply referred to as connection state. In this article, "connection state" and "RRC connection state" are the same concept and the two terms can be used interchangeably.

[0092] RRC Idle State: The terminal device has not established an RRC connection with the network and cannot transmit data with network devices, but it can receive broadcast information from the cell, such as system information and paging messages. Furthermore, the base station does not store the context of this terminal device. If the terminal device needs to transition from the RRC Idle State to the RRC Connected State, it needs to initiate an RRC connection establishment process. The RRC Idle State can also be simply referred to as the Idle State. In this article, "Idle State" and "RRC Idle State" are the same concept, and the two terms can be used interchangeably.

[0093] RRC Inactive State: The terminal device previously entered the RRC connected state at the anchor base station, and then the anchor base station released the RRC connection, but it preserved the terminal device's context. If the terminal device needs to re-enter the RRC connected state from the RRC inactive state, it needs to initiate an RRC connection recovery process (or RRC connection re-establishment process) at the currently camped base station. Because the terminal device may be in a mobile state, the base station currently camped by the terminal device and the anchor base station may be the same base station or different base stations. Compared to the RRC establishment process, the RRC recovery process has shorter latency and lower signaling overhead. However, the base station needs to preserve the terminal device's context, which consumes base station storage overhead. The RRC inactive state can also be called the RRC inactive state, or simply inactive or inactive state. In this article, "deactivated state," "inactive state," "deactivated state," "inactive state," "RRC inactive state," or "RRC deactivated state" are all the same concept and these terms are interchangeable.

[0094] (5) RA and RNA

[0095] A Tracking Area (RA) is a geographical area in a mobile communication network, consisting of one or more Tracking Areas (TAs). Each TA corresponds to a Tracking Area Identity (TAI), which is used to manage the mobility and location updates of terminal devices.

[0096] An RNA (Radio Area) is a specific geographic region used for UE mobility management. Generally, an RNA can be a smaller area than the RA (Radio Area). An RNA can cover one or more cells, or one or more RAN (Radio Area) regions. An RNA can include multiple cells, and each RNA corresponds to an RNA identifier (ID).

[0097] For UEs in the RRC inactive state, paging can be performed within the RNA range. The RNA is managed by the base station, which can locate the UE by paging it via the RNA (RAN paging). This process is called radio access network level terminal tracking.

[0098] (6) UE paging process

[0099] For UEs in an inactive or idle state, when there are data packets that the UE needs to receive, or when there are non-access stratum (NAS) protocol data units (PDUs), the UE can be paged.

[0100] For inactive UEs, the RAN can use paging to notify the UE to receive data or signaling, or to enable the UE to send management area updates. The basic RAN paging process is as follows: select the area to be paging (referred to as the paging area), send a paging message to the UE, and the paging message includes paging area information and the UE's identity (ID). The area indicated by the paging area information is the paging area selected by the access network equipment. For inactive UEs, the UE ID in the paging message is the UE's I-RNTI.

[0101] For UEs in idle mode, the core network can use paging to notify the UE to receive data or signaling, or to handle related events (such as message notifications). The basic paging process of the core network is as follows: the core network device can select the area to send the paging message (referred to as the paging area) and send a paging message to the access network device. The paging area corresponding to this paging message is the paging area selected by the core network device. The access network device receives the paging message from the core network device and forwards it to the UE. For UEs in idle mode, the UE ID in the paging message sent by the core network device to the access network device is the UE's 5G-S-TMSI, which is used to instruct the UE to execute the RRC connection establishment procedure.

[0102] When UE paging fails, the user plane data that triggered RAN paging may be lost. If the NG-RAN has at least one pending NAS PDU, the RAN node should initiate an access network (AN) release procedure, transferring the UE's connection management (CM) state in the AMF to the CM-DILE state and indicating to the AMF that the NAS has not been delivered. Alternatively, if the NG-RAN has pending user plane data, the RAN node can maintain N2 connection activation or initiate an AN release procedure based on its local configuration.

[0103] (7) UE ID

[0104] There are several types of UE identifiers, such as 5G-S-TMSI, I-RNTI, NG-RAN UE NGAP ID, and AMF UE NGAPID, etc.

[0105] The I-RNTI can be used as a paging identifier for the RAN to paging UEs in an inactive state. The I-RNTI identifies the context of a UE in an inactive state. When a base station releases a UE to an inactive state, it assigns an I-RNTI to that UE. When the RAN wants to page a UE, it sends a paging message containing the UE's I-RNTI to all cells in the UE's RAN. If the UE receives this paging message and finds a matching I-RNTI, it initiates an RRC connection recovery procedure to switch to a connected state.

[0106] The 5G-S-TMSI is a temporary identifier used to identify a UE in a 5G network. The 5G-S-TMSI is generated by the core network and assigned to the UE, and typically changes when the UE's state is updated. Currently, the 5G-S-TMSI can be used for paging UEs in idle mode.

[0107] The NG-RAN UE NGAP ID and AMF UE NGAP ID can be used in pairs. The NG-RAN UE NGAP ID is used to uniquely identify the UE on the NG interface (the interface between the NG-RAN and the core network). The NG-RAN UE NGAP ID is assigned by the RAN and communicated to the AMF. The AMF UE NGAP ID is used to identify the UE on the NG interface and is assigned by the AMF.

[0108] (8) The process of UE switching from inactive state to connected state

[0109] See Figure 1 As shown, the process of a UE switching from an inactive state to a connected state includes the following steps:

[0110] S101: The UE sends an RRC resume request message to the currently camped base station. This message carries the I-RNTI allocated by the UE's anchor base station and sends the RRC resumeRequest message. The currently camped base station and the UE's anchor base station may be different, such as... Figure 1 As shown, the example is taken with the anchor base station as base station 1 and the currently stationed base station as base station 2.

[0111] S102: If base station 2 can resolve the identity of base station 1 contained in I-RNTI, then base station 2 sends a UE context retrieval request to base station 1 through the Xn interface to request base station 1 to provide the UE's context data.

[0112] Two base stations can exchange their respective supported local RAN node identifiers and I-RNTI configuration profile identifiers (i.e., a 2-bit Full I-RNTI configuration profile identifier or a 1-bit Short I-RNTI configuration profile identifier) ​​via the Xn interface. This allows base stations to identify each other's local RAN node identifiers. Therefore, if base station 2 can resolve the identity of base station 1 contained in the I-RNTI, it means that base station 2 has received the local RAN node identifier of base station 1 through the Xn interface between base stations 1 and 2. Based on the local RAN node identifier in the I-RNTI, the anchor base station of the UE can be identified as base station 1.

[0113] S103: Base station 1 sends a UE context retrieval response to base station 2 via the Xn interface to provide UE context data to base station 2.

[0114] S104: Base station 2 instructs the UE to return to RRC connection state.

[0115] S105: The UE completes the restoration of the RRC connection state and returns an RRC resumecomplete message to base station 2.

[0116] S106: Base station 2 provides Xn user plane (Xn-U) address indication information to base station 1. In this way, base station 1 can send its cached downlink (DL) user data to base station 2 to prevent the loss of DL user data cached in base station 1.

[0117] S107: Base station 2 sends a path switch request to AMF.

[0118] S108: AMF sends a path switch response to base station 2.

[0119] S109: Base station 2 notifies base station 1 to release UE resources, such as UE context resources.

[0120] The terms and concepts involved in the embodiments of this application have been introduced above. The technical features related to the embodiments of this application are described below.

[0121] The UE receives paging messages when inactive. Upon detecting its own paging message, the UE can initiate an RRC connection restoration procedure to the network side to switch to connected mode. (Continued) Figure 1For example, base station 1 can page the UE through coordination with other base stations (such as base station 2). For instance, base station 1 can trigger base station 2 to page the UE. This requires an Xn interface connection to be established between base station 1 and base station 2, and the Xn interface must be functioning correctly. If base station 1 and base station 2 do not have an Xn interface, or if the Xn interface between base station 1 and base station 2 is faulty, then base station 1 cannot successfully trigger base station 2 to page the UE (or base station 1 cannot successfully send a message to base station 2 requesting base station 2 to page the UE). Consequently, the RRC connection recovery procedure for the UE triggered by this paging will also fail, potentially resulting in the loss of user plane data or NAS PDUs that triggered the paging.

[0122] However, within an operator's entire network, it's impossible to guarantee that all base stations will establish Xn interfaces. Firstly, data transmission between distant base stations may be minimal or nonexistent; establishing Xn interfaces would waste unnecessary base station resources. Secondly, operators generally avoid establishing Xn interfaces for base stations at geographical boundaries based on network management strategies. Therefore, if every pair of base stations within a UE's configured RNA has Xn connectivity, it clearly limits the RNA's coverage and the advantages of inactive related functions (e.g., shorter network access latency). For example, if every pair of base stations within a UE's configured RNA has Xn connectivity, then that RNA generally doesn't include base stations far from the UE's serving base station. Thus, an inactive UE cannot access a base station far from its serving base station through the RRC recovery process.

[0123] In the future, it will be possible to configure a UE with no need for Xn connectivity between any two base stations within the RNA (e.g., Xn connection is not required). Figure 1 In a network configuration, base stations 1 and 2 may not have an Xn interface to allow for a larger RNA configuration for the UE. However, if base stations 1 and 2 lack an Xn interface, base station 1 cannot successfully trigger base station 2 to page the UE, resulting in paging failure. Furthermore, even if base stations 1 and 2 have an Xn interface, a failure in this interface—for example, due to network policy restrictions, temporary network outages, or recovery time—can also prevent base station 1 from successfully triggering base station 2 to page the UE, leading to paging failure and potentially resulting in the loss of user plane data or NAS PDUs that triggered the paging process.

[0124] In view of this, this application provides a scheme to enhance UE paging in the inactive state, supporting situations where communication between two base stations within the RNA cannot be achieved through the Xn interface. In this scheme, when an access network device (e.g., a first access network device) needs to paging a UE, it can trigger another access network device (e.g., a second access network device) that has no Xn connection with the first access network device to paging the UE through the core network. Even if the first and second access network devices cannot communicate through the Xn interface, UE paging can still be achieved, allowing the UE to transition from the inactive state to the connected state, reducing the latency of the UE entering the connected state, and improving communication efficiency. Furthermore, compared to the UE entering the connected state through a connection establishment process, this also reduces signaling interaction and lowers signaling overhead.

[0125] The technical solutions provided in the embodiments of this application can be applied to various communication systems, such as long-term evolution (LTE) communication systems, 5th generation (5G) mobile communication systems / new radio (NR) communication systems, or future mobile communication systems, or other similar communication systems. Other similar communication systems may include vehicle-to-everything (V2X) systems, IoT systems, wireless local area networks (WLANs), NTN (e.g., satellite communication systems), or systems integrating NTN with terrestrial networks (TN), etc. The NTN system can be an NTN system integrated with 4G, 5G, and any future generation of communication systems, such as NR NTN, IoT NTN, etc. The NTN communication system can be, for example, a satellite communication system, and may also include drones, HAPS, and other airborne access network equipment; this application does not limit this.

[0126] Please see Figure 2 This illustrates a communication system to which embodiments of this application are applicable. Figure 2 This includes terminal equipment, access network equipment 1, access network equipment 2, and core network (CN) equipment. Access network equipment 1 and access network equipment 2 can both communicate with core network equipment. The terminal equipment can communicate with either access network equipment 1 or access network equipment 2 via a wireless air interface. The terminal equipment can move between cells provided by these two access network equipments. When moving to one of the access network equipments (e.g., camped in a cell provided by that access network equipment), the terminal equipment can communicate with that access network equipment. Alternatively, the terminal equipment may only move between different cells provided by one access network equipment; or the terminal equipment may move between cells provided by more access network equipment, in which case there can be even more access network equipment. Figure 2 Take the case where there are two access network devices as an example.

[0127] Figure 2 The communication system shown can be a 5G NR communication system. The first interface can be an Xn interface. Access network device 1 and access network device 2 can communicate with the core network device through the NG interface. The radio interface can be a Uu interface. However, access network device 1 and access network device 2 cannot communicate with each other through the first interface. Figure 2 An "×" indicates that access network device 1 and access network device 2 cannot communicate through the first interface. The inability for the two access network devices to communicate through the first interface includes situations where the two access network devices do not have a first interface, or where the first interface between the two access network devices is faulty or unavailable.

[0128] The solutions provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0129] For ease of description, the following description will use the communication method provided in the embodiments of this application, which is executed by a first communication device, a second communication device, a third communication device, and a fourth communication device, as an example.

[0130] In this context, the first and second communication devices can be access network devices, the third communication device can be a core network device, and the fourth communication device can be a terminal device. For a single communication device (e.g., the first, second, or third communication device), the steps performed by that device can be implemented by the communication device itself, by a device including the communication device, by a component within the communication device (e.g., a processing unit / processor), or by a logic module or software that performs some or all of the functions of the communication device. For example, if the first communication device is a RAN device, the steps performed by the first communication device can be implemented by the RAN device, or by a CU, DU, or RU that performs some of the functions of the RAN device. Similarly, if the third communication device is a core network device, the steps performed by the third communication device can be implemented by a module that performs some of the functions of the core network device (e.g., a CPU chip). For ease of description, the following examples will use the first communication device as a first access network device, the second communication device as a second access network device, the third communication device as a first core network device, and the fourth communication device as a terminal device. The terminal device can be... Figure 2 The terminal equipment in the network, the first access network equipment can be Figure 2 Access network device 1 and the second access network device can be... Figure 2 Access network device 2 in the middle, the first core network element can be Figure 2 The core network equipment, for example, the first core network equipment includes AMF.

[0131] In this application embodiment, "regional information" refers to one or more regions. Here, "region" may include one or more cells, or it may be used to represent a group of physically close or geographically adjacent cells that together cover a large geographical area. The terminal device may move randomly within this large geographical area, possibly moving from one cell to another.

[0132] In this application embodiment, the area served by the access network device, the area broadcast by the access network device, the area provided by the access network device, the area of ​​the access network device, and the area covered by the access network device are all the same concept and can be substituted for each other.

[0133] Please see Figure 3 This is a flowchart illustrating the communication method provided in an embodiment of this application. Figure 3 Taking the interaction between a first access network device, a second access network device, a first core network device, and a first terminal device as an example. The first terminal device is in an inactive state. The first access network device is the last RAN node serving the first terminal device, or it can be any base station connected to the first core network device. The second access network device is the access network device where the first terminal device resides. Both the first and second access network devices can communicate with the first core network device. Furthermore, the processing performed by a single execution entity can be divided into multiple execution entities, which can be logically and / or physically separated. For example, the steps performed by the first access network device can be executed by one or more of the CU, DU, and RU.

[0134] S301. The first access network device sends a first paging request to the first core network device.

[0135] Accordingly, the first core network device receives a first paging request from the first access network device. This first paging request is used to request paging of the first terminal device, or it can trigger the first core network device to paging the first terminal device. When data or a NAS PDU needs to be received by the first terminal device, the first access network device can send a first paging request to the first core network device. The name of the first paging request is not limited, as long as it is used to request paging of the first terminal device. For example, the first paging request can be called a first request message, a first paging message, or simply paging, etc.

[0136] Optionally, before sending the first paging request to the first core network device, the first access network device may trigger a third access network device that can directly communicate with the first access network device to page the first terminal device. The third access network device and the first access network device can communicate based on a first interface. The first interface is the communication interface between access network devices. For example, the first interface is the Xn interface (or the X2 interface). If the third access network device fails to page the first terminal device or does not page the first terminal device, the first access network device may send the first paging request to the first core network device.

[0137] The reason why the third access network device fails to page the first terminal device or cannot page the first terminal device may be that the first terminal device is not within the coverage area of ​​the third access network device. In this case, the first access network device can request to page the first terminal device from the first core network device. Since the first core network device manages more access network devices, cross-base station paging can be achieved. Even if the first terminal device moves to the coverage area of ​​other access network devices (such as the second access network device) that cannot directly communicate with the first access network device, it can still be successfully paged. Furthermore, the first access network device's request for the first core network device to page the first terminal device is not limited by the need for direct communication between access network devices, thus supporting the establishment of Xn interface connections between pairs of base stations within the RNA or Xn interface failures, further enhancing network stability and flexibility.

[0138] Optionally, when a NAS PDU needs to be received by the first terminal device, the first access network device may indicate at least one area to the first core network device in advance, so that the first core network device can page the first terminal device based on the at least one area. For example, before S301, the first access network device may also send paging assistance information to the first core network device, which is used to indicate at least one area. The at least one area may include the coverage area of ​​the second access network device. The first core network device may consider that the first terminal device is located within the coverage area of ​​the at least one area. When the first core network device needs to send a NAS PDU to the first terminal device, the first core network device uses the at least one area as the paging area, triggering the second access network device to page the first terminal device.

[0139] Optionally, at least one region is an RNA, or at least one region is a portion of an RNA. When at least one region is an RNA, or at least one region is a region supported by all access network devices that cannot communicate with the first access network device through the first interface, the first access network device may not send a first paging request to the first core network device. When at least one region is a portion of an RNA, or at least one region includes only regions supported by access network devices that cannot communicate with the first access network device through the first interface, or at least one region includes regions supported by access network devices that cannot communicate with the first access network device through the first interface, and regions supported by a portion of access network devices that can communicate with the first access network device through the first interface, the first access network device may also trigger other access network devices to page the first terminal device (or trigger RAN paging) to improve the success rate of paging the UE.

[0140] The first paging request may include first paging area information and an identifier of the first terminal device. The first paging area information may indicate a paging area; for example, the first paging area information may indicate at least one area including the area of ​​at least one access network device. This at least one access network device may include devices that cannot communicate with the first access network device through the first interface. Alternatively, this at least one access network device may also include devices that can communicate with the first access network device through the first interface. Taking the example that the second access network device and the first network device cannot communicate based on the first interface, the first paging area information may indicate at least one area including the area of ​​the second access network device. The first access network device indicating the area of ​​the second access network device to the first core network device may implicitly instruct the first core network device to trigger the second access network device to paging the first terminal device.

[0141] The identifier of the first terminal device in the first paging request enables the first core network device to clearly identify the paging terminal device as the first terminal device. There are various implementations of the first terminal device identifier, which are illustrated with examples below.

[0142] In Example 1, the identifier of the first terminal device may include (or be) the I-RNTI of the first terminal device.

[0143] I-RNTI can uniquely identify the first terminal device within the RNA. Using I-RNTI as a paging identifier allows the first core network device to clearly identify that the first paging request is directed to the first terminal device in an inactive state.

[0144] In Example 2, the identifier of the first terminal device may include (or be) a first identifier and / or a second identifier. The first identifier can be used to identify the first terminal device in the access network; for example, the first identifier is the NG-RAN UE NGAP ID. The second identifier is used to identify the first terminal device in the core network; for example, the second identifier is the AMF UE NGAP ID. For details on the NG-RAN NGAP ID and AMF UE NGAP ID, please refer to the relevant descriptions in the aforementioned "UE ID" section, which will not be repeated here.

[0145] The first identifier can be an identifier assigned to the first terminal device by the first access network device and sent to the first core network device. Therefore, the first core network device can identify the first terminal device based on the first identifier. The second identifier can also be an identifier assigned to the first terminal device by the first core network device; therefore, the first core network device can also identify the first terminal device based on the second identifier. The first and second identifiers can be used in pairs to identify the first terminal device on the interface between the first access network device and the first core network device. The first core network device can directly locate the context of the first terminal device based on the first identifier and / or the second identifier, without additional signaling interaction to determine the identity of the first terminal device, thereby reducing the latency and signaling overhead of the paging process.

[0146] S302, The first core network device sends a second paging request to the second access network device.

[0147] Accordingly, the second access network device receives a second paging request from the first core network device. This second paging request is used to request the first terminal device to be paged. Alternatively, the second paging request can trigger the second access network device to page the first terminal device. After receiving the first paging request from the first access network device, the first core network device sends a second paging request to the second access network device. The name of the second paging request is not limited, as long as it is used to request the pagement of the first terminal device. For example, the second paging request can be called a second request message, a second paging message, or simply a paging request.

[0148] The second paging request may include second paging area information and an identifier of the first terminal device. Similar to the first paging area, the second paging area information may indicate a paging area; for example, the second paging area information may indicate at least one area including the area of ​​at least one access network device. This at least one access network device may include a device that cannot communicate with the first access network device through the first interface. For example, the second paging area information may indicate at least one area including the area of ​​the second access network device. Alternatively, the at least one access network device may also include a device that can communicate with the first access network device through the first interface.

[0149] The second paging request includes the identifier of the first terminal device, enabling the second access network device to clearly identify the paging terminal device as the first terminal device based on this identifier. The following example illustrates the identifier of the first terminal device in the second paging request.

[0150] In Example 1, the identifier of the first terminal device may include (or be) I-RNTI.

[0151] When the identifier of the first terminal device in the first paging request is I-RNTI, the first core network device can carry the I-RNTI as the identifier of the first terminal device in the second paging request. Using the I-RNTI as a paging identifier allows the second access network device to clearly understand that the second paging request is for the inactive first terminal device.

[0152] In Example 2, the identifier of the first terminal device may include (or be) 5G-S-TMSI.

[0153] The 5G-S-TMSI can be generated and assigned to the first terminal device by the first core network device. When the first core network device identifies the first terminal device, it can assign a 5G-S-TMSI to the first terminal device. For example, the identifier of the first terminal device in the first paging request includes (or is) a first identifier and / or a second identifier. The first core network device determines the first terminal device based on the first identifier and / or the second identifier, and then determines / generates the 5G-S-TMSI of the first terminal device. Alternatively, the first core network device generates the 5G-S-TMSI based on the NG-RAN UE NGAP ID and / or AMF UE NGAP ID in the first paging request. For the second access network device, the first terminal device can be identified based on the 5G-S-TMSI without additional signaling interaction to determine the identity of the first terminal device, which can reduce the latency and signaling overhead of the paging process.

[0154] Optionally, the second paging request can also be used to instruct the first terminal device to perform an RRC connection restoration procedure. The phrase "the second paging request can also be used to instruct the first terminal device to perform an RRC connection restoration procedure" can be replaced with "the second paging request can also be used to instruct the first terminal device to enter the RRC connected state from the RRC inactive state." Here, the second paging request can implicitly or explicitly instruct the first terminal device to perform the RRC connection restoration procedure. For the second access network device, receiving the second paging request allows it to determine that the first terminal device to be paged must perform the RRC connection restoration procedure to enter the connected state.

[0155] For example, the I-RNTI is for an inactive UE. When the second paging request includes the I-RNTI, it can implicitly instruct the first terminal device to perform the RRC connection restoration procedure. Alternatively, the first terminal device can also be instructed to perform the RRC connection restoration procedure through additional signaling or a certain information element in the second paging request.

[0156] For example, when the second paging request includes a 5G-S-TMSI, it can instruct the first terminal device to perform an RRC connection restoration procedure. Typically, 5G-S-TMSI is for idle terminal devices. However, in this embodiment, the 5G-S-TMSI in the paging message can be used for inactive terminal devices. When the second paging request sent by the first core network device to the second access network device includes a 5G-S-TMSI, this second paging request (or 5G-S-TMSI) is also used to instruct the first terminal device to perform an RRC connection restoration procedure. Optionally, the inclusion of a 5G-S-TMSI in the second paging request can also instruct the first terminal device to perform an RRC connection restoration procedure through additional signaling or a specific element in the second paging request.

[0157] S303, the second access network device sends a third paging request.

[0158] The second access network device receives the second paging request and, based on the second paging request, can send a third paging request, which is used to page the first terminal device. The third paging request can also be replaced by a paging message. The third paging request may include the 5G-S-TMSI of the first terminal device. When the first terminal device receives the third paging request and determines that the third paging request contains its own 5G-S-TMSI, it enters the connected state.

[0159] Similar to the second paging request containing the 5G-T-TMSI, the third paging request containing the 5G-S-TMSI also instructs the first terminal device to perform an RRC connection restoration procedure, or instructs the first terminal device to transition from an RRC inactive state to an RRC connected state. Alternatively, if the third paging request sent by the second access network device includes the 5G-S-TMSI, then the third paging request also instructs the first terminal device to perform an RRC connection restoration procedure or instructs the first terminal device to transition from an RRC inactive state to an RRC connected state. This avoids the first terminal device performing an RRC connection establishment procedure.

[0160] Optionally, the third paging request may include 5G-S-TMSI, and may also instruct the first terminal device to perform the RRC connection recovery process via additional signaling or a cell in the third paging request.

[0161] S304. The first terminal device executes the RRC connection restoration process according to the third paging request.

[0162] The first terminal device receives a third paging request. Based on the 5G-S-TMSI in the third paging request, the first terminal device can determine that it has been paged. Furthermore, based on the third paging request, the first terminal device can also determine to execute the RRC connection restoration process instead of the RRC connection establishment process. After executing the RRC connection restoration process, the first terminal device enters the RRC connection state and can send and / or receive data.

[0163] For example, the second access network device provides the first core network device with NG user plane (NG-U) address indication information. This NG-U address indication information includes downlink (DL) forwarding user plane (UP) transport network layer (TNL) information, used to indicate or configure information related to user plane data path handover. The first core network device receives the NG-U address indication information and forwards it to the first access network device to instruct the first access network device on how to receive or process data.

[0164] For example, the second access network device can send a path switch request to the first core network device, which includes DL forwarding UP TNL information. The first core device sends a path switch response to the first access network device, which includes DL forwarding UPTNL information to instruct the first access network device on how to receive or process data.

[0165] This application embodiment enhances paging for inactive UEs, thereby supporting situations where no Xn interface connection is established between any two base stations within the RNA. For example, if a first access network device fails to paging a first terminal device, a first paging request can trigger a first core network device to paging the first terminal device. The failure of the first access network device to paging the first terminal device may be because: the first terminal device is not within the coverage area of ​​a third access network device, which can communicate with the first access network device through the first interface. However, the first core network device can communicate with more access network devices, such as a second access network device, which cannot communicate with the first access network device through the first interface. Therefore, the first core network device can trigger the second access network device to paging the first terminal device, improving the paging success rate of the first terminal device and reducing data loss. Furthermore, when triggered by paging, the first terminal device executes the RRC connection recovery process, reducing the latency of entering the connected state and improving network efficiency and signaling overhead.

[0166] In the embodiments provided above, the methods provided by the embodiments of this application are described using access network devices (e.g., a first access network device and a second access network device), a first core network device, and a first terminal device as examples. In this application, each embodiment can be implemented independently or in combination based on certain inherent connections; in each embodiment, different implementation methods can be implemented in combination or independently. To achieve the functions in the methods provided by the embodiments of this application above, the steps executed by each device can be implemented by the device itself, or by a functional entity including the device, or by different functional entities constituting the device. For example, the steps executed by the access network device can be implemented by the access network device itself, or by a functional entity including the access network device, or by different functional entities constituting the access network device. To achieve the functions in the methods provided by the embodiments of this application above, the access network device and the first core network element can include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or hardware structures plus software modules. Whether a particular function is executed in the form of hardware structures, software modules, or hardware structures plus software modules depends on the specific application and design constraints of the technical solution.

[0167] Based on the same inventive concept as the method embodiments, this application provides a communication device. The communication device used to implement the above method in the embodiments of this application is described below with reference to the accompanying drawings. The content above can be used in subsequent embodiments, and repeated content will not be repeated.

[0168] Figure 4This is a schematic block diagram of a communication device 400 provided in an embodiment of this application. The communication device 400 can correspondingly implement the functions or steps implemented by the first access network device, second access network device, first core network device, or first terminal device in the various method embodiments described above. For example, the communication device 400 can be an access network device or a terminal device; or, the communication device 400 can be a chip (system) in the access network device or terminal device; or, the communication device 400 can be a software module of the access network device or terminal device. Alternatively, the communication device 400 can be a first core network device; or, the communication device 400 can be a chip (system) in the first core network device; or, the communication device 400 can be a software module of the first core network device.

[0169] The communication device 400 may include a processing module 410 and a transceiver module 420. Optionally, it may also include a storage module, which can be used to store instructions (code or program) and / or data. This storage module may be, for example, a memory. The processing module 410 and the transceiver module 420 may be coupled to the storage module. For example, the processing module 410 can read instructions (code or program) and / or data from the storage module to implement a corresponding method. When the communication device 400 is a chip in a core network device, access network device, or terminal device, the storage module may be an internal storage module within that chip, such as a register or cache. For example, the storage module may also be an external storage module located within the first core network device, access network device, or terminal device, such as a read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, such as random access memory (RAM). The above-mentioned units may be set independently or partially or completely integrated.

[0170] Processing module 410 may be a processor or controller, such as a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing unit (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc. Transceiver module 420 is a transceiver, interface circuit, bus, pin, or other possible communication interface for receiving signals from other devices. For example, when the device is implemented as a chip, transceiver module 420 is an interface circuit for the chip to receive signals from other chips or devices, or an interface circuit for the chip to send signals to other chips or devices.

[0171] In one implementation, the communication device 400 can correspondingly implement the behavior and functions of the first core network device in the above method embodiments. The communication device 400 can be a core network device, a component (e.g., a chip or circuit) within the core network device, a part of a chip or chipset within the core network device used to execute related method functions, or a software module in the first core network device capable of implementing the above communication method; no limitation is imposed. For details, please refer to the relevant content of the foregoing method embodiments, which will not be repeated here.

[0172] For example, transceiver module 420 is used to receive a first paging request from a first access network device and send a second paging request to a second access network device. The first paging request requests to page a first terminal device, and includes first paging area information and an identifier of the first terminal device. The first paging area information indicates at least one area that includes the area of ​​the second access network device. The second paging request requests to page the first terminal device. Processing module 410 is used to determine the second paging request.

[0173] As an optional implementation, the second access network device and the first access network device cannot communicate based on the first interface, which is the communication interface between access network devices.

[0174] As an optional implementation, the first terminal device is identified as I-RNTI.

[0175] As an optional implementation, the identifier of the first terminal device includes a first identifier and / or a second identifier. The first identifier is used to identify the first terminal device in the access network, and the second identifier is used to identify the first terminal device in the core network.

[0176] As an optional implementation, the second paging request includes second paging area information and an identifier of the first terminal device. The second paging area information indicates at least one area, including an area provided by the second access network device. The identifier of the first terminal device includes either I-RNTI or 5G-S-TMSI.

[0177] As an optional implementation, the second paging request is used to instruct the first terminal device to perform the RRC connection restoration process.

[0178] As an optional implementation, the second paging request includes the 5G-S-TMSI, and the identifier of the first terminal device in the first paging request includes a first identifier and / or a second identifier. The processing module 410 is further configured to determine the 5G-S-TMSI of the first terminal device based on the first identifier and / or the second identifier.

[0179] In one implementation, the communication device 400 can correspondingly implement the behavior and functions of the first access network device in the above method embodiments. The communication device 400 can be an access network device, a component (e.g., a chip or circuit) within the access network device, a part of a chip or chipset within the access network device used to execute the relevant method functions, or a software module in the first access network device capable of implementing the above communication method; no limitation is imposed. For details, please refer to the relevant content of the foregoing method embodiments, which will not be repeated here.

[0180] For example, the transceiver module 420 is used to release the first terminal device into a Radio Resource Control (RRC) inactive state and send a first paging request to the first core network device. The first paging request requests paging of the first terminal device, and includes first paging area information and an identifier of the first terminal device. The first paging area information indicates at least one area that includes the area of ​​the second access network device. The processing module is used to determine the first paging request.

[0181] As an optional implementation, the first terminal device is identified as I-RNTI.

[0182] As an optional implementation, the identifier of the first terminal device includes a first identifier and / or a second identifier. The first identifier is used to identify the first terminal device in the access network, and the second identifier is used to identify the first terminal device in the core network.

[0183] In one implementation, the communication device 400 can correspondingly implement the behavior and functions of the second access network device in the above method embodiments. The communication device 400 can be an access network device, a component (e.g., a chip or circuit) within the access network device, a part of a chip or chipset in the access network device used to execute the relevant method functions, or a software module in the second access network device capable of implementing the above communication method; no limitation is imposed. For details, please refer to the relevant content of the foregoing method embodiments, which will not be repeated here.

[0184] For example, transceiver module 420 is used to receive a second paging request from the first core network device and send a third paging request. The second paging request is used to request paging of the first terminal device. The third paging request is used to paging of the first terminal device, and the third paging request is also used to instruct the first terminal device to perform an RRC connection restoration procedure. Processing module 410 is used to determine the third paging request based on the second paging request.

[0185] As an optional implementation, the second paging request includes second area information and an identifier of the first terminal device. The second paging area information indicates at least one area, including areas provided by the second access network device. The identifier of the first terminal device includes either the I-RNTI or the 5G-S-TMSI of the first terminal device.

[0186] As an optional implementation, the third request includes the 5G-S-TMSI of the first terminal device.

[0187] In one implementation, the communication device 400 can correspondingly implement the behavior and functions of the first terminal device in the above method embodiments. The communication device 400 can be the terminal device itself, a component (e.g., a chip or circuit) within the terminal device, a part of a chip or chipset in the terminal device used to execute the relevant method functions, or a software module in the terminal device capable of implementing the above communication method; no limitation is imposed. For details, please refer to the relevant content of the foregoing method embodiments, which will not be repeated here.

[0188] For example, transceiver module 420 is used to receive a third paging request from the second access network device and send an RRC recovery request to the second access network device. The third paging request is used to page the first terminal device. The third paging request includes the 5G-S-TMSI of the first terminal device, and the third paging request is also used to instruct the first terminal device to perform an RRC connection recovery procedure. Processing module 410 is used to determine whether to perform the RRC connection recovery procedure based on the third paging request.

[0189] When the communication device 400 is a chip-based device or circuit, the transceiver module can be an input / output circuit and / or a communication interface; the processing module is an integrated processor, microprocessor, or integrated circuit.

[0190] Figure 5 This is a schematic block diagram of a communication device 500 provided in an embodiment of this application. The communication device 500 can be used to implement the functions of the first access network device, second access network device, first core network device, or first terminal device in the above embodiments. For example, the communication device 500 can be an access network device, core network device, or terminal device, or the communication device 500 can be a chip (system) in an access network device, core network device, or terminal device. In this embodiment, the chip system can be composed of chips or can include chips and other discrete devices. Specific functions can be found in the descriptions in the above method embodiments.

[0191] The communication device 500 includes one or more processors 501, used to implement or support the communication device 500 in implementing the functions of the first access network device, second access network device, first core network device, or first terminal device in the methods provided in the embodiments of this application. For details, please refer to the detailed description in the method examples, which will not be repeated here. The processor 501 can also be called a processing unit or processing module, and can implement certain control functions. The processor 501 can be a general-purpose processor or a dedicated processor, etc. For example, it includes: a baseband processor, a central processing unit, an application processor, a modem processor, a graphics processor, an image signal processor, a digital signal processor, a video codec processor, a controller, a memory, and / or a neural network processor, etc. The baseband processor can be used to process communication protocols and communication data. The central processing unit can be used to control the communication device 500 (e.g., access network device, core network device, or terminal device), execute software programs, and / or process data. Different processors can be independent devices or integrated into one or more processors, for example, integrated on one or more application-specific integrated circuits.

[0192] In one design, processor 501 may include program 503 (sometimes also referred to as code or instructions), which can be executed on processor 501 to cause communication device 500 to perform the methods described in the embodiments below. In yet another possible design, communication device 500 includes circuitry (…). Figure 5 (Not shown), the circuit is used to implement the functions of the first access network device, the second access network device, the first core network device, or the first terminal device in the above embodiments.

[0193] In one design, the communication device 500 may include one or more memories 502 storing a program 504 (sometimes referred to as code or instructions), which can be run on the processor 501 to cause the communication device 500 to perform the methods described in the above method embodiments.

[0194] In one design, the processor 501 and / or memory 502 may include an AI module 507 and an AI module 505, which are used to implement AI-related functions. The AI ​​modules can be implemented through software, hardware, or a combination of both. For example, the AI ​​module may include a RIC module. For example, the AI ​​module may be a near real-time RIC or a non-real-time RIC.

[0195] In one possible design, the processor 501 and / or memory 502 may also store data. The processor and memory may be configured separately or integrated together.

[0196] In one possible design, when the communication device 500 is a first access network device, a second access network device, or a first terminal device, the communication device 500 may further include a transceiver and / or an antenna. The processor 501, sometimes referred to as a processing unit, controls the communication device 500. The transceiver, sometimes referred to as a transceiver unit, transceiver, transceiver circuit, or simply a transceiver, is used to implement the transmission and reception functions of the communication device 500 via the antenna.

[0197] In one possible design, the communication device 500 may further include one or more of the following components: a wireless communication module, an audio module, an external memory interface, internal memory, a universal serial bus (USB) interface, a power management module, an antenna, a speaker, a microphone, an input / output module, a sensor module, a motor, a camera, or a display screen, etc. It is understood that in some embodiments, the communication device 500 may include more or fewer components, or some components may be integrated, or some components may be separated. These components may be implemented in hardware, software, or a combination of software and hardware.

[0198] Please see Figure 6 This application also provides another communication device 600, including an input / output interface 610 and a logic circuit 620; the input / output interface 610 is used to receive code instructions and transmit them to the logic circuit 620; the logic circuit 620 is used to run the code instructions to execute the method executed by the terminal device or network device in any of the above embodiments, which can be referred to the above method embodiments, and will not be repeated here.

[0199] When the communication device 600 executes the method performed by the first core network device, the input / output interface 610 is used to receive a first paging request from the first access network device and send a second paging request to the second access network device. The first paging request requests to page the first terminal device, and includes first paging area information and an identifier of the first terminal device. The first paging area information indicates at least one area that includes the area of ​​the second access network device. The second paging request requests to page the first terminal device. Logic circuitry 620 is used to determine the second paging request.

[0200] When the communication device 600 executes the method performed by the first access network device, the input / output interface 610 is used to release the first terminal device into an RRC inactive state and send a first paging request to the first core network device. The first paging request requests to page the first terminal device, and includes first paging area information and an identifier of the first terminal device. The first paging area information indicates at least one area that includes the area of ​​the second access network device. The logic circuit 620 is used to determine the first paging request.

[0201] When the communication device 600 is used to execute the method performed by the second access network device, the input / output interface 610 is used to receive a second paging request from the first core network device and send a third paging request. The logic circuit 620 is used to determine the third paging request based on the second paging request. The second paging request is used to request paging of the first terminal device. The third paging request is used to paging of the first terminal device, and the third paging request is also used to instruct the first terminal device to perform an RRC connection restoration procedure.

[0202] When the communication device 600 executes the method performed by the first terminal device, the input / output interface 610 receives a third request from the second access network device and sends an RRC recovery request to the second access network device. The third request is used to page the first terminal device. The third request includes the 5G-S-TMSI of the first terminal device and also instructs the first terminal device to perform an RRC connection recovery process. The logic circuit 620 determines the RRC recovery request.

[0203] The communication device in the above embodiments can be an access network device, a core network device, or a terminal device. It can also be a circuit, a chip applied in the access network device, core network device, or terminal device, or other combined devices or components having the aforementioned access network device, core network device, or terminal device. When the communication device is an access network device or a terminal device, the transceiver module can be a transceiver, which may include an antenna and radio frequency circuits, etc., and the processing module can be a processor, such as a CPU. When the communication device is a chip system, it can be an FPGA, a dedicated ASIC, a SoC, a CPU, a network processor (NP), a DSP, a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips. The processing module can be the processor of the chip system. The transceiver module or communication interface can be the input / output interface or interface circuit of the chip system. For example, the interface circuit can be a code / data read / write interface circuit. The interface circuit can be used to receive code instructions (the code instructions are stored in memory and can be read directly from memory or through other devices) and transmit them to the processor; the processor can then execute the code instructions to perform the methods described in the above method embodiments. Alternatively, the interface circuit can also be a signal transmission interface circuit between a communication processor and a transceiver.

[0204] This application also provides a communication system comprising at least two access network devices, a core network device, and a terminal device. The at least two access network devices include a first access network device and a second access network device. The first access network device implements the functions of the first access network device in the above-described communication method, and the second access network device implements the functions of the second access network device in the above-described communication method. The core network device implements the functions of the first core network device in the above-described communication method. The terminal device implements the functions of the first terminal device in the above-described communication method.

[0205] This application also provides a computer-readable storage medium including instructions that, when run on a computer, cause the method executed by the first access network device, the second access network device, the first core network device, or the first terminal device in the above-described communication method to be executed.

[0206] This application also provides a computer program product, including computer program code, which, when executed, causes the method executed by the first access network device, the second access network device, the first core network device, or the first terminal device in the above-described communication method to be executed.

[0207] This application provides a chip system including a processor and potentially a memory, for implementing the functions of the first access network device, second access network device, first core network device, or first terminal device in the aforementioned communication method. The chip system may be composed of chips or may include chips and other discrete components.

[0208] To achieve the above Figures 4-6 In addition to the functions of the communication device, this application also provides a chip, including a processor, for supporting the communication device in implementing the functions involved in the first access network device, second access network device, first core network device, or first terminal device in the above method embodiments. In one possible design, the chip is connected to a memory or the chip includes a memory for storing necessary computer programs or instructions and data for the communication device.

[0209] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply 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 this application.

[0210] Those skilled in the art will recognize that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0211] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0212] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0213] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0214] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the essential contributing part of the technical solution of this application, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, external hard drives, ROM, RAM, magnetic disks, or optical disks.

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

Claims

1. A communication method, characterized in that, include: A first paging request is received from a first access network device. The first paging request is used to request paging of a first terminal device. The first paging request includes first paging area information and an identifier of the first terminal device. At least one area indicated by the first paging area information includes the area of ​​the second access network device. A second paging request is sent to the second access network device, the second paging request being used to request paging of the first terminal device.

2. The method as described in claim 1, characterized in that, The second access network device and the first network device cannot communicate based on the first interface, which is the communication interface between access network devices.

3. The method as described in claim 1 or 2, characterized in that, The identifier of the first terminal device is the Inactive Wireless Network Temporary Identifier (I-RNTI).

4. The method as described in claim 1 or 2, characterized in that, The identifier of the first terminal device includes: A first identifier and / or a second identifier, wherein the first identifier is used to identify the first terminal device in the access network, and the second identifier is used to identify the first terminal device in the core network.

5. The method according to any one of claims 1-4, characterized in that, The second paging request includes: The second paging area information and the identifier of the first terminal device, wherein the second paging area information indicates at least one area including an area provided by the second access network device, and the identifier of the first terminal device includes the I-RNTI of the first terminal device, or the identifier of the first terminal device includes the 5G-S-TMSI of the 5G mobile communication technology system temporary mobility service identifier.

6. The method as described in claim 5, characterized in that, The second paging request is used to instruct the first terminal device to perform the Radio Resource Control (RRC) connection restoration process.

7. The method as described in claim 5 or 6, characterized in that, The second paging request includes the 5G-S-TMSI, and the identifier of the first terminal device in the first paging request includes the first identifier and / or the second identifier. The method further includes: The 5G-S-TMSI of the first terminal device is determined based on the first identifier and / or the second identifier.

8. A communication method, characterized in that, include: Release the first terminal device into the Radio Resource Control (RRC) inactive state; A first paging request is sent to a first core network device. The first paging request is used to request paging of a first terminal device. The first paging request includes first paging area information and the identifier of the first terminal device. The first paging area information indicates at least one area that includes the area of ​​the second access network device.

9. The method as described in claim 8, characterized in that, The identifier of the first terminal device is the Inactive Wireless Network Temporary Identifier (I-RNTI).

10. The method as described in claim 8, characterized in that, The identifier of the first terminal device includes: A first identifier and / or a second identifier, wherein the first identifier is used to identify the first terminal device in the access network, and the second identifier is used to identify the first terminal device in the core network.

11. A communication method, characterized in that, include: Receive a second paging request from the first core network device, the second paging request being used to request paging of the first terminal device; Based on the second paging request, a third paging request is sent, the third paging request being used to page the first terminal device, and the third paging request also being used to instruct the first terminal device to perform a Radio Resource Control (RRC) connection recovery procedure.

12. The method as described in claim 11, characterized in that, The second paging request includes: The second area information and the identifier of the first terminal device, wherein at least one area indicated by the second paging area information includes an area provided by the second access network device, and the identifier of the first terminal device includes the I-RNTI of the first terminal device, or the identifier of the first terminal device includes the 5G-S-TMSI of the fifth generation mobile communication technology system temporary mobility service identifier.

13. The method as described in claim 11 or 12, characterized in that, The third Request for Assistance includes the 5G-S-TMSI of the first terminal device.

14. A communication method, characterized in that, include: The device receives a third request from a second access network device, the third request being used to page the first terminal device, the third request including the fifth-generation mobile communication technology system temporary mobility service identifier (5G-S-TMSI) of the first terminal device, and the third request also being used to instruct the first terminal device to perform a radio resource control (RRC) connection recovery procedure. Send an RRC recovery request to the second access network device.

15. A communication system, characterized in that, The communication system includes at least two access network devices, a first core network device, and a first terminal device, wherein the at least two access network devices include a first access network device and a second access network device. Wherein, the first core network device sends a first paging request to the first core network device. The first paging request is used to request paging of the first terminal device. The first paging request includes first paging area information and the identifier of the first terminal device. The first paging area information indicates at least one area including the area of ​​the second access network device. The first core network device sends a second paging request to the second access network device, the second paging request being used to request paging of the first terminal device; The second access network device sends a third request, which is used to page the first terminal device.

16. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 1-7, or includes a module for performing the method as described in any one of claims 8-10, or includes a module for performing the method as described in any one of claims 11-13, or includes a module for performing the method as described in claim 14.

17. A communication device, characterized in that, The communication device includes at least one processor, the at least one processor being configured to cause the method of any one of claims 1-7 to be performed by the communication device, or the at least one processor being configured to cause the communication device to perform the method of any one of claims 8-10, or the at least one processor being configured to cause the communication device to perform the method of any one of claims 11-13, or the at least one processor being configured to cause the communication device to perform the method of claim 14.

18. A chip or chip system, characterized in that, The chip or chip system includes: At least one processor and an interface, the at least one processor being configured to call and execute instructions from the interface, such that, when the at least one processor executes the instructions, the method as claimed in any one of claims 1-7 is executed, or the method as claimed in any one of claims 8-10 is executed, or the method as claimed in any one of claims 11-13 is executed, or the method as claimed in claim 14 is executed.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a computer, causes the method as described in any one of claims 1-7 to be performed, or causes the method as described in any one of claims 8-10 to be performed, or causes the method as described in any one of claims 11-13 to be performed, or causes the method as described in claim 14 to be performed.

20. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a computer, causes the method as described in any one of claims 1-7 to be performed, or causes the method as described in any one of claims 8-10 to be performed, or causes the method as described in any one of claims 11-13 to be performed, or causes the method as described in claim 14 to be performed.

Images