Communication methods and devices

Abstract

This application discloses a communication method and apparatus relating to the field of communications. The method includes the steps of: a first access network device receiving information from a terminal device used to request the resumption of an RRC connection, wherein the inactive state paging cycle of the terminal device is a first paging cycle; and transmitting the first information to the terminal device or a second access network device, wherein the first information is used to configure the inactive state paging cycle of the terminal device as a second paging cycle; and transmitting the second information to a core network element, wherein the second information is used to initiate, cancel, or modify the mobile termination communication processing policy of the terminal device. According to the method described above, the terminal device and the core network element can synchronize the updating of the inactive state paging cycle of the terminal device even if the terminal device does not enter a connected state.

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims the priority of Chinese Patent Application No. 202310357788.0, titled "Communication Method and Device", filed with the China National Intellectual Property Administration on March 24, 2023, and the entire content of the Chinese patent application is incorporated herein by reference in its entirety.

[0002] This application relates to the field of communication technology, and in particular, to communication methods and devices.

Background Art

[0003] To reduce the power consumption when a terminal device monitors paging messages, an access network device may periodically transmit paging messages to the terminal device based on a paging cycle. Accordingly, the terminal device may periodically receive paging messages based on the paging cycle. In other words, the terminal device may periodically detect a physical downlink control channel (PDCCH).

[0004] The paging cycle of the terminal device in the inactive state is used as an example. The paging cycle of the terminal device in the inactive state may be a discontinuous reception (DRX) cycle or an extended DRX cycle in the inactive state. To further reduce the power consumption of the terminal device, enhanced extended DRX in the inactive state has been further introduced currently.

[0005] However, even after enhanced extended DRX in the inactive state is introduced, how to update the paging cycle of the terminal device in the inactive state still needs to be further considered.

Summary of the Invention

[0006] This application provides a communication method and apparatus for updating the inactive state paging cycle of a terminal device.

[0007] According to a first aspect, one embodiment of the present application provides a communication method. The method may be applied to a first access network device or a component (e.g., a circuit or chip) within the first access network device. For example, the method is applied to a first access network device. In the method, the first access network device receives information from a terminal device used to request the resumption of a radio resource control RRC connection, wherein the inactive state paging cycle of the terminal device is a first paging cycle; and transmits the first information to the terminal device or a second access network device, wherein the first information is used to configure the inactive state paging cycle of the terminal device as a second paging cycle; and transmits the second information to a core network element, wherein the second information is used to initiate, cancel or modify the mobile termination communication processing policy of the terminal device.

[0008] According to the method described above, when a terminal device initiates the RRC restart procedure, the first access network device may configure an inactive state paging cycle for the terminal device and send the second information to the core network element to notify the core network element to update (or start, modify, or cancel) the terminal device's mobile termination communication processing policy. In this way, the terminal device and the core network element can synchronize the updating of the terminal device's inactive state paging cycle even if the terminal device does not enter a connected state.

[0009] In a possible design, the method further includes the step of receiving third information from a third access network device, wherein the third information indicates a first paging cycle or indicates that the first paging cycle is greater than a threshold.

[0010] Thus, the first access network device may acquire the first paging cycle (or learn that the first paging cycle is greater than a threshold), and as a result, the first access network device can transmit the second information to the core network element in the designated manner based on the first paging cycle (or the first paging cycle being greater than a threshold). For example, if the first paging cycle is less than or equal to a threshold, and the second paging cycle is less than or equal to a threshold, the first access network device does not need to transmit the second information to the core network element in order to conserve communication resources.

[0011] In a possible design, the first piece of information is carried in the RRC release message, which indicates that the terminal device is in an inactive state.

[0012] In a possible design, the second piece of information is carried in the route switching request message.

[0013] In this way, the first access network device reuses the route switching request message to send the second information to the core network element, thereby eliminating the need for additional signaling and saving signaling resources.

[0014] In a possible design, if the first paging cycle is less than or equal to a threshold and the second paging cycle is greater than a threshold, the second information is used to initiate the mobile termination communication processing policy of the terminal device.

[0015] In a possible design, the first paging cycle is greater than the threshold, the second paging cycle is less than or equal to the threshold, and the second information is used to cancel the mobile termination communication processing policy of the terminal device.

[0016] In a possible design, the first paging cycle is greater than the threshold, the second paging cycle is greater than the threshold, and the second information is used to modify the mobile terminal communication processing policy of the terminal device.

[0017] In a possible design, the second information includes a second paging cycle and / or instruction information, where the instruction information indicates an action on a communication processing policy, and the action includes initiating, canceling, or modifying.

[0018] According to a second aspect, one embodiment of the present application provides a communication method. The method may be applied to a first access network device or a component (e.g., a circuit or chip) within the first access network device. For example, the method is applied to a first access network device. In the method, the first access network device transmits context information of an inactive terminal device to a second access network device, where the inactive paging cycle of the terminal device is greater than a threshold; obtains capability information of the second access network device, where the capability information indicates that the second access network device does not support paging cycles; and transmits fourth information to a core network element, where the fourth information instructs the terminal device to cancel its mobile termination communication processing policy.

[0019] In a possible design, the step of acquiring capability information of a second access network device includes the step of receiving capability information from the second access network device.

[0020] According to the method described above, when a terminal device initiates the RRC restart procedure, if the terminal device's inactive state paging cycle is greater than the threshold (or the core network element initiates the terminal device's mobile termination communication processing policy), and the first access network device performs anchor relocation, and the second access network device does not support enhanced INACTIVE eDRX (or the second access network device configures an inactive state paging cycle for the terminal device that is less than or equal to the threshold), the first access network device may send the fourth information to the core network element to cancel the terminal device's mobile termination communication processing policy. In this way, the terminal device and the core network element can synchronize the updating of the terminal device's inactive state paging cycle even if the terminal device does not enter a connected state.

[0021] According to a third aspect, one embodiment of the present application provides a communication method. The method may be applied to a first access network device or a component (e.g., a circuit or chip) within the first access network device. For example, the method is applied to a first access network device. In the method, the first access network device receives third information from a second access network device, where the third information indicates an inactive state paging cycle of a terminal device or an inactive state paging cycle greater than a threshold; and instructs the terminal device to enter a connected state based on the third information.

[0022] In a possible design, instructing a terminal device to enter a connected state includes sending an RRC restart message to the terminal device, which instructs the terminal device to enter a connected state.

[0023] According to the method described above, when a terminal device initiates the RRC restart procedure, if the terminal device's inactive state paging cycle is greater than a threshold, the first access network device may perform anchor relocation and then send third information to the second access network device. If the first paging cycle is still greater than a threshold, the second access network device may instruct the terminal device to enter a connected state based on the third information. As a result, the updating of the terminal device's inactive state paging cycle can be synchronized between the terminal device and the core network element.

[0024] According to a fourth aspect, the present invention provides a communication device having functions for implementing the first to third aspects. For example, the communication device includes corresponding modules, units, or means for performing the operations of the first to third aspects. The modules, units, or means may be implemented by software, by hardware, or by hardware by running corresponding software.

[0025] In a possible design, the communication device includes a processing unit and a communication unit. The communication unit may be configured to receive and transmit signals to implement communication between the communication device and another device. The processing unit may be configured to perform some internal operations of the communication device. The functions performed by the processing unit and the communication unit may correspond to the operations in the first to third embodiments.

[0026] In a possible design, the communication device includes a processor, which may be configured to be coupled to a memory. The memory may store the necessary computer programs or necessary instructions for implementing the functions in the first aspect to the third aspect. The processor may execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the communication device can implement the method according to any possible design or implementation in the first aspect to the third aspect.

[0027] In a possible design, the communication device includes a processor and a memory. The memory may store the necessary computer programs or necessary instructions for implementing the functions in the first aspect to the third aspect. The processor may execute the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the communication device can implement the method according to any possible design or implementation in the first aspect to the third aspect.

[0028] In a possible design, the communication device includes a processor and an interface circuit. The processor is configured to communicate with another device through the interface circuit and execute the method according to any possible design or implementation in the first aspect to the third aspect.

[0029] In a fourth aspect, it can be understood that the processor may be implemented by hardware or by software. When the processor is implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like. When the processor is implemented by software, the processor may be a general-purpose processor and is implemented by reading software code stored in a memory. In addition, one or more processors and one or more memories may exist. The memory may be integrated with the processor, or the memory and the processor may be separately arranged. In a specific implementation process, the memory and the processor may be integrated into one chip, or may be arranged on different chips. The type of the memory and the manner in which the memory and the processor are arranged are not limited in the embodiments of the present application.

[0030] According to a fifth aspect, the present application provides a computer-readable storage medium. The computer storage medium stores computer-readable instructions, and when a computer reads and executes the computer-readable instructions, the computer can execute a method according to any one of the possible designs of the first aspect to the third aspect.

[0031] According to a sixth aspect, the present application provides a computer program product. When a computer reads and executes the computer program product, the computer can execute a method according to any one of the possible designs of the first aspect to the third aspect.

[0032] According to a seventh aspect, the present application provides a chip. The chip includes a processor. The processor is coupled to a memory and is configured to read and execute a software program stored in the memory to implement a method according to any one of the possible designs of the first aspect to the third aspect.

[0033] According to the eighth aspect, the present invention provides a communication system comprising a terminal device and a first access network device, optionally further comprising a second access network device. The terminal device is configured to transmit information used to request the resumption of an RRC connection to the first or second access network device. The first access network device is configured to receive information used to request the resumption of an RRC connection; transmit the first information to the second access network device, where the first information is used to configure the terminal device's inactive state paging cycle as a second paging cycle; and transmit the second information to a core network element, where the second information is used to initiate, cancel, or modify the terminal device's mobile termination communication processing policy.

[0034] Optionally, the communication system further includes a core network element, which is configured to receive second information.

[0035] Alternatively, the communication system includes a first access network device and a second access network device. The second access network device is configured to transmit to the first access network device information used to request a terminal device to resume its RRC connection. The first access network device is configured to receive information used to request a terminal device to resume its RRC connection; transmit the first information to the second access network device, where the first information is used to configure the terminal device's inactive state paging cycle as a second paging cycle; and transmit the second information to the core network element, where the second information is used to initiate, cancel, or modify the terminal device's mobile termination communication processing policy.

[0036] Optionally, the communication system further includes a core network element, which is configured to receive second information.

[0037] Optionally, the communication system further includes a terminal device. The terminal device is configured to transmit information used to request the resumption of the RRC connection to a second access network device; and to receive the first information from the second access network device.

[0038] Alternatively, the communication system includes a first access network device and a second access network device. The first access network device is configured to transmit a third piece of information to the second access network device. The second access network device is configured to instruct a terminal device to enter a connected state after determining, based on the third piece of information, that a first paging cycle is greater than a threshold; and to transmit a fourth piece of information to the core network element, where the fourth piece of information is used to cancel the mobile termination communication processing policy of the terminal device. [Brief explanation of the drawing]

[0039] [Figure 1] This is a diagram of a network architecture to which one embodiment of the present invention can be applied.

[0040] [Figure 2] This is a diagram of a more specific network architecture to which one embodiment of the present invention can be applied.

[0041] [Figure 3] This is a diagram of the paging procedure according to one embodiment of the present invention.

[0042] [Figure 4] This is a diagram illustrating the RRC restart procedure according to one embodiment of the present invention.

[0043] [Figure 5] This is a schematic flowchart outlining the initiation of a mobile terminal communication processing policy according to one embodiment of the present invention.

[0044] [Figure 6] This is a schematic flowchart for canceling a mobile terminal communication processing policy according to one embodiment of the present invention.

[0045] [Figure 7] This is a schematic flowchart corresponding to the communication method according to Embodiment 1 of the present invention.

[0046] [Figure 8] This is a schematic flowchart corresponding to the communication method according to Embodiment 2 of the present invention.

[0047] [Figure 9] This is a schematic flowchart corresponding to the communication method according to Embodiment 3 of the present invention.

[0048] [Figure 10] This is a schematic flowchart corresponding to the communication method according to Embodiment 4 of the present invention.

[0049] [Figure 11] This is a schematic flowchart corresponding to the communication method according to Embodiment 5 of the present invention.

[0050] [Figure 12] This is a schematic flowchart corresponding to the communication method according to Embodiment 5 of the present invention.

[0051] [Figure 13] A possible exemplary block diagram of a device according to one embodiment of the present invention.

[0052] [Figure 14] This is a possible diagram of the structure of a device according to one embodiment of the present invention. [Modes for carrying out the invention]

[0053] The technical solutions in embodiments of this application will be described below with reference to the accompanying drawings. All aspects, embodiments, or features are presented in this application by describing systems that may include multiple devices, components, modules, and similars. It should be recognized and understood that each system may include other devices, components, modules, and similars, and / or may not include all of the devices, components, modules, and similars discussed with reference to the accompanying drawings. In addition, combinations of these solutions may be used.

[0054] In addition, in the embodiments of this application, terms such as “example” and “for example” are used to provide an example, illustration, or explanation. None of the embodiments or design schemes described as “examples” in this application should be described as being preferable or having more advantages than other embodiments or design schemes. Strictly speaking, the word “example” is used to present a concept in a particular manner. In the embodiments of this application, “of,” “relevant,” and “corresponding” may, in some cases, be used interchangeably. Note that the meanings expressed by these terms are consistent unless differences are emphasized.

[0055] The technical solutions in the embodiments of this application can be applied to various communication systems, such as 4th generation (4G) communication systems like universal mobile telecommunications systems (UMTS), wireless local area networks (WLAN), wireless fidelity (Wi-Fi®) systems, and long-term evolution (LTE) systems, 5G communication systems like new radio (NR) systems, and future advanced communication systems like 6th generation (6G) mobile communication systems.

[0056] Figure 1 shows a network architecture of a communication system to which this application is applicable. According to the 3GPP® protocol standard requirements, the network architecture includes four components: terminal devices, an access network (AN), a core network (CN), and a data network (DN). The access network may be a radio access network (RAN).

[0057] Terminal devices, (radio) access networks, and core networks are the main parts of the network architecture and can be logically divided into two parts: the user plane and the control plane. The control plane is used for mobile network management, and the user plane is used for service data transmission. For example, as shown in Figure 1, in a 5G communication system, the next generation (NG)2 reference point is located between the (radio) access network control plane and the core network control plane, the NG3 reference point is located between the (radio) access network user plane and the core network user plane, and the NG6 reference point is located between the core network user plane and the data network.

[0058] The following sections provide a detailed explanation of each component of the network architecture.

[0059] (1) Terminal device

[0060] A terminal device is a device that provides voice and / or data connectivity for the user. Terminal devices may also be referred to as user equipment (UE), terminal, access terminal, terminal unit, terminal station, mobile station (MS), remote station, remote terminal, mobile terminal (MT), wireless communication device, terminal agent, or terminal equipment, etc.

[0061] For example, a terminal device may be a handheld device with wireless connectivity, or a vehicle, in-vehicle device (e.g., an in-vehicle communication device or in-vehicle communication chip) or similar with communication capabilities. Currently, some examples of terminal devices are as follows: mobile phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistant (PDA®) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, tablet computers, computers with wireless transceiver capabilities, notebook computers, and palmtop computers. Mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, or similar devices.

[0062] Terminal devices may be deployed on land and include indoor or outdoor terminal devices, handheld terminal devices, wearable terminal devices, or in-vehicle terminal devices; or they may be deployed on water (e.g., on a ship); or they may be deployed in the air (e.g., on an airplane, balloon, or satellite). The specific technologies, device forms, application scenarios, and names used by the terminal devices are not limited to the embodiments of this application.

[0063] (2) Access Network

[0064] A (wireless) access network is deployed near terminal devices and provides network access functionality to authorized users within a specific area. It can determine transmission tunnels of different qualities based on user level, service requirements, and similar factors to carry out the transmission of user data. The (wireless) access network manages and appropriately utilizes its resources, can provide access services to terminal devices as needed, and is used to transfer control signals and service data between terminal devices and the core network.

[0065] A (wireless) access network device is deployed within a (wireless) access network and configured to connect terminal devices to the wireless network. A (wireless) access network device may generally be connected to the core network via a wired link (e.g., fiber optic cable). A (wireless) access network device may also be referred to as a RAN device / node or base station.

[0066] For example, a (wireless) access network device may include a base station, an evolved NodeB (eNodeB) in an LTE system or LTE-Advanced (LTE-A) system, a next-generation NodeB (gNB) in a 5G communication system, a transmission reception point (TRP), a baseband unit (BBU), an access point (AP) in a wireless local area network (WLAN), an integrated access and backhaul (IAB) node, a base station in a future mobile communication system, an access node in a Wi-Fi® system, or similar. Alternatively, a wireless access network device may be a module or unit that performs some of the functions of a base station, such as a central unit (CU), a distributed unit (DU), a CU control plane (CP), a CU user plane (UP), or a radio unit (RU). CUs and DUs may be arranged separately or may be included in the same network element, for example, a baseband unit (BBU). RUs may be included in radio frequency devices or radio frequency units, for example, a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). It should be understood that this application may also be applicable to 6G communication systems. Access network devices may be core network elements or devices that perform the functions of base stations in future communication systems. In this application, “access network devices” may also be referred to as “core network devices,” “core network equipment,” or “core network,” etc.

[0067] (Wireless) access network devices may be deployed on land and include indoor or outdoor (wireless) access network devices, handheld (wireless) access network devices, wearable (wireless) access network devices, or vehicle-mounted (wireless) access network devices; or they may be deployed on water (e.g., on a ship); or they may be deployed in the air (e.g., on an airplane, balloon, or satellite). The specific technologies, device forms, application scenarios, and names used by (wireless) access network devices are not limited to the embodiments of this application. In the embodiments of this application, (wireless) access network devices may be abbreviated as access network (AN) devices. Unless otherwise specified, all access network devices below may be (wireless) access network devices.

[0068] (3) Core Network

[0069] The core network is used to maintain mobile network subscription data, manage mobile network elements, and provide functions such as session management, mobility management, policy management, and security authentication for terminal devices.

[0070] Specifically, the core network may provide network access authentication to terminal devices when they are installed; allocate network resources to terminal devices when they have service requests; update the network resources of terminal devices when they are moved; provide terminal devices with a fast recovery mechanism when they are idle; release the network resources of terminal devices when they are removed; and provide terminal devices with data routing capabilities when they have service data, which may include, for example, forwarding uplink data to a data network to send downlink data to a terminal device, or receiving downlink data from a data network and forwarding the downlink data to a (wireless) access network.

[0071] 4. Data Network

[0072] A data network is configured to provide services to users. In actual communication processing, clients are typically located on terminal devices, and servers are typically located within the data network. The data network may be a private network, such as a local area network; an external network not managed and controlled by an operator, such as the Internet; or a dedicated network jointly deployed by multiple operators, such as a network providing IP multimedia core network subsystem (IMS) services.

[0073] Figure 2 is a diagram of a more specific network architecture to which one embodiment of the present application may be applied. The network architecture may be the network architecture of a 5G communication system. As shown in Figure 2, the network architecture includes terminal devices, access network devices, various types of core network elements / functional entities, and a data network.

[0074] The core network user plane includes user plane functions (UPF). The core network control plane includes, but is not limited to, access and mobility management function (AMF) network elements, session management function (SMF) network elements, policy control function (PCF) network elements, and unified data management (UDM) network elements.

[0075] UPF network elements are primarily used to connect to external networks, forward user data packets according to the routing rules of SMF network elements, for example, to send uplink data to a data network or another UPF network element, and to send downlink data to another UPF network element or access network device.

[0076] AMF network elements are primarily used for access management and mobility management of terminal devices, such as maintaining the status of terminal devices, managing the reachability of terminal devices, forwarding mobility management non-access-stratum (MM NAS) messages, and forwarding session management (SM) N2 messages.

[0077] SMF network elements are primarily used for session management within mobile networks, including establishing sessions for terminal devices and allocating and releasing resources for those sessions. These resources include session quality of service (QoS), session routing, forwarding rules, and similar elements. For example, SMF network elements are used to assign Internet Protocol (IP) addresses to terminal devices or to select UPF network elements that provide packet forwarding capabilities.

[0078] PCF network elements are primarily used for user policy management, including policy authorization, quality of service, and billing rule generation, and for distributing corresponding rules to UPF network elements via SMF network elements to complete the installation of corresponding policies and rules.

[0079] UDM network elements are primarily used to manage and control user data, including managing subscription information (e.g., retrieving subscription information and providing it to another network element, such as an AMF network element); generating 3GPP® authentication credentials for terminal devices; and registering and maintaining the network element currently providing services to terminal devices (e.g., the AMF represented by AMF ID1 is the terminal device's current serving AMF, i.e., the serving AMF). Note that, although not shown in Figure 2, the network architecture shown in Figure 2 may further include a unified data repository (UDR) network element. The functionality of a UDM network element can be implemented by interacting with a UDR network element. The UDR network element is configured to store data required for the UDM network element to perform its operations. UDM network elements are configured to interact with other network elements. In actual implementation, the UDM network element and the UDR network element may be two separate physical entities, or the UDR network element may be integrated into the UDM network element. This is not limited to these cases.

[0080] Although not shown, the aforementioned network architecture may further include other possible network elements. This is not particularly limited.

[0081] Figure 2 can be seen as illustrating an example where the core network control plane uses a service-oriented architecture. In a service-oriented architecture, multiple control plane network elements are connected to a single service bus, and interactions between these control plane network elements are performed in a service call manner. In other words, these control plane network elements release services to other control plane network elements for calls by those other control plane network elements. In another possible implementation, the core network control plane may alternatively use a point-to-point communication method. In point-to-point communication, a specific set of messages exists on the communication interface between control plane network elements and is used by the control plane network elements at the two ends of the interface during communication. For example, the interface between an access network device and an AMF network element may be called an N2 interface, the interface between an access network device and an AMF network element may be called an N3 interface, the interface between an AMF network element and an SMF network element may be called an N4 interface, and the interface between an AMF network element and a data network may be called an N6 interface.

[0082] In future communication systems, such as 6th generation (6G) communication systems, the aforementioned network elements or devices may still use the names of network elements or devices in 4th generation (4G) or 5G communication systems, or they may have different names. The functionality of a network element or device may be completed by one independent network element, or by several network elements working together. This is not limited to the embodiments of the present application. During actual deployment, network elements may be located in the same location. For example, an access and mobility management function network element may be located in the same location as a session management function network element. A session management function network element may be located in the same location as a user plane function network element. When two network elements are located in the same location, the interaction between the two network elements provided in the embodiments of the present application may be an internal operation of the network elements located in the same location, or it may be omitted.

[0083] Various possible network elements / functional entities within a network architecture may be network elements within hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). Optionally, these network elements or functional entities may be implemented by a single device, jointly by multiple devices, or by multiple different functional modules within a single device. This is not particularly limited to the embodiments of the present application.

[0084] The network architectures and service scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions in the embodiments of this application and do not constitute limitations on the technical solutions provided in the embodiments of this application. With the evolution of communication system architectures and the emergence of new service scenarios, those skilled in the art will recognize that the technical solutions provided in the embodiments of this application are also applicable to similar technical challenges.

[0085] The following describes the relevant technical features of the embodiments of this application. It should be noted that these descriptions are intended to facilitate understanding of the embodiments of this application and should not be considered as limitations on the scope of protection claimed herein.

[0086] 1. Paging

[0087] The status of a terminal device may include radio resource control (RRC) idle state, RRC inactive state, and RRC connected state. The RRC idle state may be abbreviated as idle state, the RRC inactive state may be abbreviated as inactive state, and the RRC connected state may be abbreviated as connected state.

[0088] Paging is used to notify idle or inactive terminal devices to set up (i.e., invoke) a service, to notify terminal devices that a system message has been modified and that the terminal device needs to reread the modified system broadcast message, or to notify terminal devices to receive earthquake and tsunami warning system (ETWS) information. Based on the initiator of the paging message, paging can be classified into CN paging and RAN paging. CN paging messages are initiated by core network elements, while RAN paging messages are initiated by access network devices. CN paging is primarily used to page idle terminal devices, while RAN paging is used to page inactive terminal devices.

[0089] An inactive terminal device is used as an example. The possible paging procedure is described below with reference to Figure 3. As shown in Figure 3, this procedure may include the following steps.

[0090] S301: Access network device 1 sends an RRC release message to the terminal device, instructing the terminal device to enter an inactive state.

[0091] For example, after a terminal device accesses a cell of access network device 1 (e.g., cell a1) and enters a connected state, access network device 1 may instruct the terminal device to switch from the connected state to an inactive state. For example, access network device 1 may send an RRC release message to the terminal device, which instructs the terminal device to enter an inactive state. Accordingly, the terminal device may enter an inactive state after receiving the RRC release message. The RRC connection between the inactive terminal device and access network device 1 is disconnected, but access network device 1 still remembers the context information of the terminal device. In this example, access network device 1 may also be referred to as the access network device to which the terminal device ultimately connects, or the access network device that provides the final service to the terminal device.

[0092] In addition, the RRC release message transmitted from access network device 1 to the terminal device may include RAN-based notification area (RNA) configuration information, which is used to configure the RNA of the terminal device. The RNA may contain one or more cells, and the RNA configuration information includes at least one of the following: (1) identifiers for one or more cells, where the cells may belong to one or more access network devices. For example, if the RNA contains cell a1 of access network device 1 and cell b1 of access network device 2, the RNA configuration information may include identifiers for cell a1 and cell b1. (2) at least one RAN tracking area code, where one RAN tracking area may contain one or more cells. If one RAN tracking area contains multiple cells, the cells may belong to one or more access network devices.

[0093] S302: After the terminal device enters an inactive state, the UPF network element may, after receiving the terminal device's downlink data, send downlink data to the access network device 1 to which the terminal device is ultimately connected; or, after the terminal device enters an inactive state, the AMF network element may send signaling associated with the terminal device (excluding UE context release command messages) to the access network device 1 to which the terminal device is ultimately connected.

[0094] S303: Access network device 1 sends a paging message within the RAN paging area of ​​access network device 1 based on the RNA configured for the terminal device.

[0095] S304: Access network device 1 sends an XnAP RAN Paging message to access network device 2 via the Xn interface, based on the RNA configured for the terminal device.

[0096] S305: Access network device 2 sends a paging message within the RAN paging area of ​​access network device 2.

[0097] Regarding S303 to S305, specifically, after access network device 1 receives downlink data from a terminal device, access network device 1 cannot determine whether the terminal device is within access network device 1's coverage. Therefore, access network device 1 may determine its RAN paging area (e.g., cell a1) based on the RNA configured for the terminal device and transmit a paging message within its RAN paging area. The RAN paging area of ​​access network device 1 may contain one or more cells, one or more of which are cells of access network device 1, and one or more which belong to the RNA of the terminal device.

[0098] In addition, access network device 1 may further send a RAN paging message to access network device 2 based on the RNA configured for the terminal device, where the RAN paging message may include the identifier of the terminal device. Accordingly, after receiving the RAN paging message, access network device 2 determines its RAN paging area (e.g., cell b1) and further sends a paging message within its RAN paging area.

[0099] A paging message may include a paging record list (PagingRecordlist), which contains the identifiers of one or more terminal devices that need to be paged. If, after receiving a paging message from access network device 2, it is determined that the paging record list contains the identifiers of terminal devices, an inactive terminal device may initiate the RRC restart procedure.

[0100] 2. RRC Restart Procedure

[0101] If the terminal device is in an inactive state, the terminal device may initiate the RRC restart procedure.

[0102] The following describes possible RRC restart procedures with reference to Figure 4, using the scenario in which "Access Network Device 1 is the last access network device to provide service to the terminal device, and the terminal device moves from the coverage of Access Network Device 1 to the coverage of Access Network Device 2" as an example. As shown in Figure 4, this procedure may include the following steps.

[0103] S401: After the terminal device moves to the coverage of access network device 2, it sends an RRC restart request message to access network device 2.

[0104] Here, there may be multiple scenarios in which the terminal device sends an RRC restart request message to access network device 2.

[0105] For example, in the procedure shown in Figure 3, the terminal device may send an RRC restart request message to the access network device 2 after receiving a paging message from the access network device 2.

[0106] In another example, a terminal device may send an RRC restart request message to access network device 2 after its RNA timer has timed out.

[0107] In another example, a terminal device may send an RRC restart request message to access network device 2 after the terminal device has moved away from the RNA.

[0108] In another example, the terminal device proactively sends an RRC restart request message to access network device 2.

[0109] For example, an RRC restart request message may include the inactive-radio network temporary identity (I-RNTI) of the terminal device and may further include other possible information.

[0110] S402: After access network device 2 receives an RRC restart request message, it sends a retrieve UE context request message to access network device 1, and access network device 1 may receive the retrieve UE context request message accordingly.

[0111] Here, after obtaining the identifier of access network device 1 within the I-RNTI through analysis, access network device 2 may send an acquired UE context request message to access network device 1. The acquired UE context request message may include the I-RNTI of the terminal device. Furthermore, access network device 1 may determine the context information of the terminal device based on the I-RNTI.

[0112] S403: Access network device 1 decides whether to perform anchor relocation. If access network device 1 decides to perform anchor relocation, S404-a to S407-a are executed. If access network device 1 decides not to perform anchor relocation, S404-b and S405-b are executed.

[0113] Here, anchor relocation can be understood as the relocation of context information for a terminal device when the terminal device is in an inactive state. Before anchor relocation is performed, the context information for the terminal device is stored in access network device 1. After anchor relocation is performed, the context information for the terminal device is stored in access network device 2. Optionally, access network device 1 may release the context information for the terminal device.

[0114] S404-a: Access network device 1 sends a retrieved UE context response message to access network device 2, and access network device 2 receives the retrieved UE context response message accordingly.

[0115] Here, the acquired UE context response message may contain context information of the terminal device, and as a result, access network device 2 can acquire the context information of the terminal device.

[0116] S405-a: Access network device 2 performs route switching. For example, access network device 2 sends a route switching request message to the AMF network element, and the AMF network element receives the route switching request message accordingly.

[0117] S406-a: The AMF network element sends a route switching response message to the access network device 2, and in response, the access network device 2 receives the route switching response message and completes the route switching.

[0118] Here, route switching means that the data transmission path of the terminal device is switched from "UPF network element → access network device 1 → terminal device" to "UPF network element → access network device 2 → terminal device". In other words, after route switching, downlink data may be sent by the UPF network element to access network device 2, and then by access network device 2 to the terminal device. Uplink data may be sent by the terminal device to access network device 2, and then by access network device 2 to the UPF network element.

[0119] Optionally, access network device 2 may further transmit address instruction information to access network device 1, which indicates the address to be used by access network device 1 to transfer data (i.e., downlink data). If access network device 1 receives downlink data from a terminal device from the UPF network element before routing, access network device 1 may transfer the downlink data to access network device 2 based on the address instruction information, and access network device 2 transmits the downlink data to the terminal device.

[0120] S407-a: Access network device 2 may instruct terminal devices to enter a connected state, remain in an inactive state, or enter an idle state.

[0121] Here, the specific state in which the access network device 2 instructs the terminal device to enter a connection state may depend on the internal implementation of the access network device 2. This is not limited to the embodiments of the present application. For example, if there is downlink data that needs to be sent to the terminal device, the access network device 2 may instruct the terminal device to enter a connection state in order to receive the downlink data.

[0122] S404b: Access network device 1 sends a retrieve UE context failure message to access network device 2, which instructs the device not to perform anchor relocation.

[0123] S405b: Access network device 1 may instruct terminal devices through access network device 2 to enter a connected state, remain in an inactive state, or enter an idle state.

[0124] Here, the specific state in which access network device 1 instructs the terminal device to enter may depend on the internal implementation of access network device 1. This is not limited to the embodiments of the present application. Since the terminal device is located within the coverage of access network device 2, access network device 1 may instruct the terminal device through access network device 2 to enter a connected state, remain in an inactive state, or enter an idle state. For example, access network device 1 may send an RRC restart message or an RRC release message to the terminal device through access network device 2, and the RRC restart message or RRC release message may be encapsulated within an acquired UE context failure message.

[0125] 3. Paging Cycle

[0126] To reduce power consumption when monitoring paging messages by terminal devices, an access network device (for example, access network device 1 or access network device 2 described above) may periodically transmit paging messages to terminal devices based on a paging cycle. Accordingly, terminal devices may periodically receive paging messages based on the paging cycle, that is, terminal devices may periodically detect PDCCH. The paging cycle in the embodiments of this application may be a RAN paging cycle, i.e., a paging cycle in which the access network device pages terminal devices.

[0127] An example is the inactive state paging cycle of a terminal device. The inactive state paging cycle of a terminal device may be a DRX cycle, an INACTIVE extended DRX (eDRX) cycle, or an enhanced INACTIVE eDRX (enhanced INACTIVE eDRX) cycle.

[0128] To further reduce power consumption, enhanced DRX technology has been introduced in Release 17 (R17) of the 3rd generation partnership project (3GPP®). This increases the DRX cycle length, allowing terminal devices to remain in sleep mode for longer periods. The idle eDRX cycle of a terminal device can be extended to over 3 hours. However, only cases where the inactive eDRX (i.e., INACTIVE eDRX) cycle of a terminal device is 10.24 seconds or less have been discussed.

[0129] To further reduce power consumption, a potential method is to make the INACTIVE eDRX cycle longer than 10.24 seconds. An INACTIVE eDRX cycle longer than 10.24 seconds may be referred to as an extended INACTIVE eDRX cycle.

[0130] 4. Mobile Termination Communication Processing Policy

[0131] As explained above in Figure 3, for terminal devices in an inactive state, the UPF network element sends downlink data to the access network device after the terminal device's downlink data has arrived. After the introduction of the Extended INACTIVE eDRX cycle, a mobile terminated (MT) communication handling policy may be initiated (or enabled) for the terminal device to avoid excessively large amounts of data that need to be buffered by the access network device due to the terminal device's excessively long sleep time. For example, after the mobile terminated communication handling policy is initiated, the core network element considers the terminal device to be temporarily unreachable. Therefore, the core network element rejects signaling received from other network elements for the terminal device, and the data received by the terminal device is temporarily buffered. For example, the mobile terminated communication handling policy may include a buffer time length, which may be determined based on the terminal device's inactive state paging cycle. For specific details of the mobile terminated communication handling policy, please refer to the protocol specifications. Further details will not be explained again.

[0132] The following describes possible implementation procedures with reference to Figure 5. As shown in Figure 5, this procedure may include the following steps:

[0133] S501: Access network device 1 sends an RRC release message to the terminal device, instructing the terminal device to enter an inactive state.

[0134] For example, an RRC release message may include an inactive state paging cycle configured by access network device 1 for a terminal device. For example, the inactive state paging cycle is an extended inactive eDRX cycle, and the extended inactive eDRX cycle is greater than 10.24 seconds.

[0135] S502: Access network device 1 sends request message a1 to the AMF network element.

[0136] For example, request message a1 may be a new N2 message, which includes at least one of the following: an instruction indicating that an extended inactive eDRX cycle is configured for the terminal device; the extended inactive eDRX cycle; the corresponding paging transmission window (PTW) length; or I-RNTI. Herein, an example is used in which request message a1 includes an extended inactive eDRX cycle.

[0137] Furthermore, after request message a1 is sent, access network device 1 may wait for a response message from the AMF network element, where the response message indicates whether the core network has initiated the mobile termination communication processing policy for the terminal device.

[0138] It can be understood that S502 may be executed before S501, or after S501, or concurrently with S501. This is not particularly limited.

[0139] S503: After receiving request message a1, the AMF network element may initiate the mobile termination communication processing policy for the terminal device and send request message a2 to the SMF network element. For example, request message a2 may include an enhanced INACTIVE eDRX.

[0140] For example, request message a2 may be a session context update request (Nsmf_PDUSession_UpdateSMContext request) message.

[0141] S504: After the SMF network element receives request message a2, it sends request message a3 to the UPF network element, and request message a3 includes an enhanced INACTIVE eDRX.

[0142] For example, request message a3 may be an N4 session modification message.

[0143] S505: After receiving request message a3, the UPF network element may initiate the terminal device's mobile termination communication processing policy or data buffer function.

[0144] For example, a UPF network element may, after receiving downlink data from a terminal device, first buffer the downlink data from the terminal device, and then, after the buffer time reaches the buffer time length, transmit the downlink data from the terminal device to the access network device 1 (where the buffer time length may be configured for the UPF network element by the SMF network element).

[0145] Optionally, in the procedure shown in Figure 5, the UPF network element may further send an N4 session correction response message to the SMF network element. After receiving the N4 session correction response message, the SMF network element sends a session context update response message to the AMF network element. After receiving the session context update response message, the AMF network element sends an N2 response message to the access network device 1.

[0146] Thus, according to the procedure shown in Figure 5, if the terminal device's inactive state paging cycle is longer than 10.24 seconds, the terminal device's mobile termination communication processing policy is initiated.

[0147] Furthermore, after the terminal device enters a connected state, the terminal device's mobile termination communication processing policy can be canceled.

[0148] The following describes possible implementation procedures with reference to Figure 6. As shown in Figure 6, this procedure may include the following steps:

[0149] S601: After the terminal device moves to the coverage of access network device 2, it sends an RRC restart request message to access network device 2.

[0150] S602: Access network device 2 obtains context information of the terminal device from access network device 1 and sends an RRC restart message to the terminal device, instructing the terminal device to enter a connected state.

[0151] S603: Access network device 2 sends request message b1 to the AMF network element. For example, request message b1 includes status information of the terminal device, which instructs the terminal device to enter a connected state (i.e., the status information instructs the core network element to cancel the terminal device's mobile termination communication processing policy or data buffer behavior).

[0152] For example, request message b1 may be an N2 message. For instance, an existing RRC inactive transition report message may be reused. Alternatively, based on improvements to this message, request message b1 may be used to notify the core network that the status of a terminal device has changed, for example, that the terminal device is in an RRC connected state or remains in an RRC inactive state.

[0153] It can be understood that S603 may be executed before S602, or after S602, or concurrently with S602. This is not particularly limited.

[0154] S604: After the AMF network element receives request message b1, it sends request message b2 to the SMF network element, where request message a2 includes status information of the terminal device.

[0155] For example, request message b2 may be a session context update request message.

[0156] S605: After the SMF network element receives request message b2, it sends request message b3 to the UPF network element, where request message b3 includes status information of the terminal device.

[0157] For example, request message b3 may be an N4 session modification message.

[0158] S606: A UPF network element may cancel the mobile termination communication processing policy of a terminal device after receiving request message b3.

[0159] Optionally, in the procedure shown in Figure 6, the UPF network element may further send an N4 session correction response message to the SMF network element. After receiving the N4 session correction response message, the SMF network element sends a session context update response message to the AMF network element. After receiving the session context update response message, the AMF network element sends an N2 response message to the access network device 1.

[0160] Based on the description of the relevant technical features described above, relevant implementations for updating the inactive state paging cycle of a terminal device are considered in embodiments of the present application.

[0161] For example, access network device 1 configures an inactive state paging cycle for a terminal device, and the paging cycle is greater than 10.24 seconds (i.e., access network device 1 notifies the core network element to initiate the terminal device's mobile termination communication processing policy). If the terminal device's inactive state paging cycle needs to be updated, in a possible implementation, the terminal device is first instructed to move from the inactive state to the connected state, and the terminal device's mobile termination communication processing policy is canceled using S604 to S606 in Figure 6. Furthermore, if the updated inactive state paging cycle of the terminal device is also greater than 10.24 seconds, the access network device must initiate the terminal device's mobile termination communication processing policy using the procedure shown in Figure 5.

[0162] In other words, in the aforementioned method, the terminal device needs to enter a connected state to update the terminal device's inactive state paging cycle. This results in unnecessary connection access and wasted communication resources. To solve this problem, one embodiment of the present invention provides a communication method. For details, please refer to Embodiments 1 to 5. According to this communication method, when the terminal device is in an inactive state, the terminal device's inactive state paging cycle is updated.

[0163] In addition, in the aforementioned method, when an inactive terminal device moves from the coverage of access network device 1 to the coverage of access network device 2, access network device 2 does not recognize whether the inactive state paging cycle configured for the terminal device by access network device 1 is greater than 10.24 seconds (in other words, access network device 2 does not recognize whether the core network element has initiated the mobile termination communication processing policy for the terminal device). Therefore, if the inactive state paging cycle configured for the terminal device by access network device 1 is less than or equal to 10.24 seconds, and access network device 2 still instructs the terminal device to enter a connected state and notifies the core network element to cancel the mobile termination communication processing policy for the terminal device, this is invalid behavior and wastes transmission resources. To solve this problem, one embodiment of the present invention provides a communication method. For details, please refer to Embodiment 6. According to this communication method, in order to reduce transmission resource overhead, the terminal device is instructed to enter a connected state using the target method, and the core network element is notified to cancel the terminal device's mobile termination communication processing policy.

[0164] The communication method provided in this application will be described below with reference to a specific embodiment. Embodiment 1

[0165] Figure 7 is a schematic flowchart of the communication method according to Embodiment 1 of the present invention. As shown in Figure 7, this method includes the following steps.

[0166] S701: A terminal device or a second access network device sends information to the first access network device used to request the resumption of the RRC connection, and in response, the first access network device receives information used to request the resumption of the RRC connection, where the inactive state paging cycle of the terminal device is the first paging cycle.

[0167] S702: The first access network device transmits first information to a terminal device or a second access network device, where the first information is used to configure the terminal device's inactive state paging cycle as the second paging cycle.

[0168] For example, the information used to request the resumption of the RRC connection may be an RRC resume cause value, or other possible information. The RRC resume cause value may indicate the reason why the terminal device sends an RRC resume request message, or the reason why the terminal device requests the resumption of the RRC connection. For example, the reason why the terminal device sends an RRC resume request message is that RNA updating is triggered due to the terminal device's RNA timer timing out.

[0169] For example, the first paging cycle may be configured for a terminal device by the access network device that last provided service to the terminal device. For example, prior to S701, the access network device that last provided service to the terminal device may send an RRC release message to the terminal device, which instructs the terminal device to enter an inactive state, and the RRC release message includes the first paging cycle.

[0170] (1) In possible scenarios, the first access network device is the last access network device to provide service to a terminal device (or the access network device that stores context information for a terminal device), and an inactive terminal device is currently within the coverage of the first access network device. In other words, the first paging cycle may be configured for a terminal device by the first access network device.

[0171] In this scenario, the terminal device may communicate with the first access network device. For example, in S701, the terminal device may send information to the first access network device that is used to request the resumption of the RRC connection, and in S702, the first access network device may send first information to the terminal device.

[0172] (2) In another possible scenario, the first access network device is the last access network device to provide service to the terminal device, and the inactive terminal device is currently within the coverage of the second access network device. In other words, the first paging cycle may be configured for the terminal device by the first access network device.

[0173] In this scenario, the terminal device may communicate with the first access network device through the second access network device. For example, in S701, after receiving information from the terminal device used to request the resumption of the RRC connection, the second access network device may send information to the first access network device used to request the resumption of the RRC connection. In addition, in S702, the first access network device may send the first information to the second access network device, and the second access network device forwards the first information to the terminal device.

[0174] (3) In another possible scenario, the third access network device is the last access network device to provide service to the terminal device, and the inactive terminal device is currently within the coverage of the first access network device. In other words, the first paging cycle may be configured for the terminal device by the third access network device.

[0175] In this scenario, the terminal device may communicate with the first access network device. For example, in S701, the terminal device may send information to the first access network device that is used to request the resumption of the RRC connection, and in S702, the first access network device may send first information to the terminal device.

[0176] Optionally, in this scenario, the third access network device may transmit third information to the first access network device, where the third information indicates a first paging cycle or that the first paging cycle is greater than a threshold. In this way, the first access network device may obtain the first paging cycle or learn that the first paging cycle is greater than a threshold.

[0177] S703: The first access network device transmits second information to the core network element, where the second information is used to initiate, cancel, or modify the mobile termination communication processing policy of the terminal device.

[0178] In this specification, a core network element includes, for example, an AMF network element, and optionally further includes at least one of an SMF network element and a UPF network element.

[0179] For example, the second piece of information may include a second paging cycle and / or instruction information, the instruction information indicating an action on the communication processing policy. An action on the communication processing policy may include initiating, canceling, or modifying.

[0180] (1) In a possible implementation, the first access network device may transmit second information to the core network element based on the first and second paging cycles.

[0181] Specifically, if the first paging cycle is less than or equal to a threshold and the second paging cycle is greater than the threshold, the first access network device may send second information to the core network element, where the second information is used to initiate the mobile termination communication processing policy of the terminal device. In this example, the second information may include the second paging cycle and optionally further include instruction information (where the action instructed by the instruction information is "start"). The threshold may be pre-configured or pre-defined in the protocol. For example, the threshold may be 10.24 seconds.

[0182] If the first paging cycle is greater than a threshold and the second paging cycle is greater than a threshold, the first access network device may send second information to the core network element, where the second information is used to modify the mobile termination communication processing policy of the terminal device. In this example, the second information may include the second paging cycle and optionally further include instruction information (where the action instructed by the instruction information is "modification").

[0183] If the first paging cycle is greater than a threshold and the second paging cycle is less than or equal to the threshold, the first access network device may send second information to the core network element, which is used to cancel the mobile termination communication processing policy of the terminal device. In this case, the second information may include the second paging cycle and / or directive information (where the action indicated by the directive information is "cancel"). If the second information includes the second paging cycle but does not include directive information, it can be understood that the second paging cycle implicitly indicates that the action for the communication processing policy is "cancel".

[0184] If the first paging cycle is less than or equal to the threshold, and the second paging cycle is less than or equal to the threshold, the first access network device does not need to send the second information to the core network element.

[0185] (2) In another possible implementation, the first access network device may transmit the second information directly to the core network element (i.e., the first access network device does not need to pay attention to the values ​​of the first and second paging cycles). In this case, the second information may include the second paging cycle (without instruction information). Accordingly, after receiving the second information, the core network element may decide based on the second paging cycle whether to initiate the mobile termination communication processing policy for the terminal device. For example, if the second paging cycle is greater than a threshold, the core network element may initiate the mobile termination communication processing policy for the terminal device based on the second paging cycle. If the second paging cycle is less than or equal to a threshold, the core network element does not need to initiate the mobile termination communication processing policy for the terminal device.

[0186] Alternatively, if the core network element has initiated the mobile termination processing policy for the terminal device and the second paging cycle is greater than the threshold, the core network element may, based on the second information, restart or modify (e.g., modify the buffer time length) the mobile termination processing policy for the terminal device. If the core network element has initiated the mobile termination processing policy for the terminal device and the second paging cycle is less than or equal to the threshold, the core network element may, based on the second information, cancel the mobile termination processing policy for the terminal device. If the core network element has not previously initiated the mobile termination processing policy for the terminal device and the second paging cycle is greater than the threshold, the core network element may, based on the second information, initiate the mobile termination processing policy for the terminal device. If the core network element has not previously initiated the mobile termination processing policy for the terminal device and the second paging cycle is less than or equal to the threshold, the core network element may ignore the second information.

[0187] In addition, there are multiple implementations in which the first access network device transmits the second information to the core network element. For example, the first access network device may transmit the second information to the core network element by reusing the request message a1 in Figure 5. In other words, the second information may be carried in the request message a1. Alternatively, the access network device may transmit the second information to the core network element by reusing the request message b1 in Figure 6. In other words, the second information may be carried in the request message b1 (wherein the difference between Figure 7 and Figure 6 is that the terminal device in Figure 7 is inactive and does not need to enter a connected state).

[0188] According to the method described above, when a terminal device initiates the RRC restart procedure, the first access network device may configure an inactive state paging cycle (i.e., a second paging cycle) for the terminal device and send the second information to the core network element to notify the core network element to update (or start, modify, or cancel) the terminal device's mobile termination communication processing policy. In this way, the terminal device and the core network element can synchronize the updating of the terminal device's inactive state paging cycle even if the terminal device does not enter a connected state. Embodiment 2

[0189] Embodiment 2 describes possible implementation procedures for Embodiment 1 by using as an example a scenario in which "Access Network Device 1 is the access network device that provides the last service to a terminal device (or an access network device that stores context information of a terminal device), and the terminal device, which is in an inactive state, is currently located within the coverage of Access Network Device 1."

[0190] Figure 8 is a schematic flowchart corresponding to the communication method according to Embodiment 2 of the present invention. As shown in Figure 8, this method includes the following steps.

[0191] S801: The terminal device sends information to the access network device 1 to request that the RRC connection be resumed, where the inactive state paging cycle of the terminal device is the first paging cycle; and accordingly, the access network device 1 receives information to request that the RRC connection be resumed.

[0192] For example, a terminal device may send an RRC restart request message to access network device 1, which includes information used to request the restart of the RRC connection. In other words, information used to request the restart of the RRC connection may be carried in the RRC restart request message.

[0193] S802: Access network device 1 transmits first information to terminal device, where the first information is used to configure the terminal device's inactive state paging cycle as a second paging cycle; and accordingly, terminal device receives the first information.

[0194] Here, there are several ways in which the access network device 1 transmits the first information to the terminal device. For example, the access network device 1 transmits an RRC release message to the terminal device, where the RRC release message indicates that the terminal device is in an inactive state (or the RRC release message instructs the terminal device to enter an inactive state), and the RRC release message contains the first information. Accordingly, after receiving the RRC release message, the terminal device remains in an inactive state and, based on the first information, may update the terminal device's inactive state paging cycle from the first paging cycle to the second paging cycle.

[0195] S803: Access network device 1 transmits second information to core network element, where the second information is used to initiate, cancel, or modify the mobile termination communication processing policy of a terminal device; the core network element receives the second information accordingly.

[0196] For details on the implementation of S803, please refer to the explanation for S703.

[0197] It should be understood that the execution order of S802 and S803 is not limited to this embodiment of the present application. Embodiment 3

[0198] Embodiment 3 describes another possible implementation procedure of Embodiment 1 by using as an example a scenario in which "access network device 1 is the access network device that provides the final service to the terminal device, and the terminal device moves from the coverage of access network device 1 to the coverage of access network device 2."

[0199] Figure 9 is a schematic flowchart corresponding to the communication method according to Embodiment 3 of the present invention. As shown in Figure 9, this method includes the following steps.

[0200] S901: The terminal device sends information to the access network device 2 to request that the RRC connection be resumed, where the inactive state paging cycle of the terminal device is the first paging cycle; and accordingly, the access network device 2 receives information to request that the RRC connection be resumed.

[0201] For example, a terminal device may send an RRC restart request message to access network device 2, which includes information used to request the restart of the RRC connection. For example, the information used to request the restart of the RRC connection is the RRC restart cause value.

[0202] S902: Access network device 2 transmits to access network device 1 information used to request the resumption of the RRC connection, which is received by access network device 2; in response, access network device 1 receives information used to request the resumption of the RRC connection.

[0203] For example, access network device 2 may send an GET UE context request message to access network device 1, which includes information used to request the resumption of the RRC connection, such as an RRC resumption cause value.

[0204] S903: If access network device 1 decides not to perform anchor relocation, access network device 1 sends an acquired UE context failure message to access network device 2, where the acquired UE context failure message indicates that anchor relocation will not be performed.

[0205] For example, an RRC release message may be encapsulated within an acquired UE context failure message, the RRC release message instructs the terminal device to enter an inactive state, and the RRC release message contains first information. In other words, the first information is carried in the RRC release message.

[0206] It may be understood that for the purposes of this specification, an example in which the first information is carried in an RRC release message is used. Alternatively, the first information may be carried in another possible message, and this is not limited to that.

[0207] S904: After receiving an acquired UE context failure message, access network device 2 may acquire an RRC release message through decapsulation and send the RRC release message to terminal device; in response, after receiving the RRC release message, terminal device may remain in an inactive state and, based on the first information, update the terminal device's inactive state paging cycle from the first paging cycle to the second paging cycle.

[0208] S905: Access network device 1 transmits second information to core network element, where the second information is used to initiate, cancel, or modify the mobile termination communication processing policy of a terminal device; the core network element receives the second information accordingly.

[0209] For details on the implementation of S905, please refer to the explanation in S703.

[0210] It should be understood that the execution order of S905 and S903 is not limited to this embodiment of the present application.

[0211] According to the method described above, when a terminal device initiates the RRC restart procedure, access network device 1 may configure an inactive state paging cycle for the terminal device and send second information to the core network element without performing anchor relocation to notify the core network element to update (or start, modify, or cancel) the terminal device's mobile termination communication processing policy. In this way, the terminal device and the core network element can synchronize the updating of the terminal device's inactive state paging cycle even if the terminal device does not enter a connected state. Embodiment 4

[0212] Embodiment 4 describes another possible implementation procedure of Embodiment 1 by using as an example a scenario in which "access network device 1 is the access network device that provides the final service to the terminal device, and the terminal device moves from the coverage of access network device 1 to the coverage of access network device 2."

[0213] Figure 10 is a schematic flowchart corresponding to the communication method according to Embodiment 4 of the present invention. As shown in Figure 10, this method includes the following steps.

[0214] S1001: The terminal device sends information to the access network device 2 to request that the RRC connection be resumed, where the inactive state paging cycle of the terminal device is the first paging cycle; and accordingly, the access network device 2 receives information to request that the RRC connection be resumed.

[0215] For specific details on the implementation of S1001, please refer to the explanation for S901.

[0216] S1002: Access network device 2 sends information to access network device 1 that is used to request the resumption of the RRC connection; in response, access network device 1 receives information that is used to request the resumption of the RRC connection.

[0217] For example, access network device 2 may send an acquired UE context request message to access network device 1, which includes information used to request the resumption of the RRC connection.

[0218] S1003: Access network device 1 sends context information of the terminal device to access network device 2.

[0219] If access network device 1 decides to perform anchor relocation, it sends context information of the terminal device to access network device 2.

[0220] For example, access network device 1 may send an acquired UE context response message to access network device 2, where the acquired UE context response message includes context information of the terminal device.

[0221] Optionally, access network device 1 may further transmit third information to access network device 2, where the third information indicates a first paging cycle or whether the first paging cycle is greater than a threshold (i.e., whether the terminal device's mobile termination communication processing policy is initiated). The first paging cycle may be configured by access network device 1 for the terminal device. The third information may be carried in an acquired UE context response message or in another message. This is not particularly limited.

[0222] Regarding the statement, "The third piece of information indicates whether the first paging cycle is greater than the threshold," in one example, the third piece of information may contain one bit. If the bit's value is 1, it indicates that the first paging cycle is greater than the threshold. If the bit's value is 0, it indicates that the first paging cycle is less than or equal to the threshold. Alternatively, an implicit indication method may be used. For example, if the first paging cycle is greater than the threshold, access network device 1 sends the third piece of information to access network device 2. If the first paging cycle is less than or equal to the threshold, access network device 1 does not send the third piece of information to access network device 2.

[0223] S1004 Access network device 2 transmits first information to terminal device, where the first information is used to configure the terminal device's inactive state paging cycle as a second paging cycle; and accordingly, terminal device receives the first information.

[0224] Here, there are several ways in which the access network device 2 transmits the first information to the terminal device. For example, the access network device 2 transmits an RRC release message to the terminal device, where the RRC release message indicates that the terminal device is in an inactive state, and the RRC release message contains the first information. Accordingly, after receiving the RRC release message, the terminal device remains in an inactive state and, based on the first information, may update the terminal device's inactive state paging cycle from the first paging cycle to the second paging cycle.

[0225] S1005: Access network device 2 transmits second information to core network element, where the second information is used to initiate, cancel, or modify the mobile termination communication processing policy of a terminal device; the core network element receives the second information accordingly.

[0226] For example, the second piece of information may include a second paging cycle and / or instruction information, the instruction information indicating an action on the communication processing policy. An action on the communication processing policy may include initiating, canceling, or modifying.

[0227] In possible implementations, access network device 2 may transmit second information to the core network element based on third information and second paging cycle. For specific implementations, please refer to the description in Embodiment 1, ", the first access network device transmits second information to the core network element based on first and second paging cycles."

[0228] In another possible implementation, access network device 2 may transmit the second information directly to the core network element (i.e., access network device 2 does not need to pay attention to the values ​​of the first and second paging cycles). In this case, the second information may include the second paging cycle (without instruction information). For details, see the description in Embodiment 1, "The first access network device transmits the second information directly to the core network element." In this case, access network device 1 does not need to transmit the third information to access network device 2.

[0229] In addition, there are multiple implementations in which the access network device 2 transmits the second information to the core network element. For example, the access network device 2 may transmit the second information to the core network element by reusing request message a1 in Figure 5 or request message b1 in Figure 6. In other words, the second information may be carried in request message a1 or request message b1. Alternatively, the access network device 2 may transmit the second information to the core network element by reusing a route switching request message; that is, the second information may be carried in a route switching request message.

[0230] It can be understood that the execution order of S1005, S1003, and S1004 is not limited to the embodiments of this application.

[0231] According to the method described above, when a terminal device initiates the RRC restart procedure and access network device 1 performs anchor relocation, access network device 2 may configure an inactive state paging cycle for the terminal device and send second information to the core network element to notify the core network element to update (or start, modify, or cancel) the terminal device's mobile termination communication processing policy. In this way, the terminal device and the core network element can synchronize the updating of the terminal device's inactive state paging cycle even if the terminal device does not enter a connected state. Embodiment 5

[0232] In Embodiment 5, the scenario in which "Access Network Device 1 is the last access network device to provide service to a terminal device, and the terminal device moves from the coverage of Access Network Device 1 to the coverage of Access Network Device 2" is used as an example for explanation.

[0233] Figure 11 is a schematic flowchart corresponding to the communication method according to Embodiment 5 of the present invention. As shown in Figure 11, this method includes the following steps.

[0234] S1101: The terminal device sends information to the access network device 2 to request that the RRC connection be resumed, where the inactive state paging cycle of the terminal device is the first paging cycle, and the first paging cycle is greater than a threshold; and accordingly, the access network device 2 receives information to request that the RRC connection be resumed.

[0235] For specific details on the implementation of S1101, please refer to the explanation for S901.

[0236] A first paging cycle may be configured by access network device 1 for a terminal device. Since the first paging cycle is greater than a threshold, before S1101, access network device 1 may notify the core network element to initiate the mobile termination communication processing policy for the terminal device.

[0237] S1102: Access network device 2 sends information to access network device 1 that is used to request the resumption of the RRC connection; in response, access network device 1 receives information that is used to request the resumption of the RRC connection.

[0238] For example, access network device 2 may send an acquired UE context request message to access network device 1, which includes information used to request the resumption of the RRC connection.

[0239] It can be understood that S1101 and S1102 are optional steps.

[0240] S1103: Access network device 1 sends context information of the terminal device to access network device 2.

[0241] If access network device 1 decides to perform anchor relocation, access network device 1 may send context information of the terminal device to access network device 2. For example, access network device 1 sends an acquired UE context response message to access network device 2, where the acquired UE context response message includes context information of the terminal device.

[0242] S1104: Access network device 1 obtains capability information of access network device 2, where the capability information indicates that access network device 2 does not support the first paging cycle (or does not support enhanced INACTIVE eDRX).

[0243] Here, there may be multiple implementations in which access network device 1 obtains capability information from access network device 2. For example, access network device 2 may send capability information to access network device 1 via the Xn interface. Access network device 2 may proactively send capability information to access network device 1, or may send capability information to access network device 1 based on a request from access network device 1.

[0244] S1105: Access network device 1 transmits fourth information to core network element, where fourth information is used to cancel the mobile termination communication processing policy of terminal device; accordingly, core network element receives fourth information.

[0245] According to the method described above, when a terminal device initiates the RRC restart procedure, and access network device 1 configures enhanced inactive eDRX for the terminal device (i.e., the core network element initiates the mobile termination communication processing policy for the terminal device), if access network device 2 does not support enhanced inactive eDRX after access network device 1 has performed anchor relocation (i.e., access network device 2 configures an inactive state paging cycle for the terminal device that is less than or equal to a threshold), access network device 1 may send fourth information to the core network element to cancel the mobile termination communication processing policy for the terminal device. In this way, the terminal device and the core network element can synchronize the updating of the terminal device's inactive state paging cycle even if the terminal device does not enter a connected state. Embodiment 6

[0246] In Embodiment 6, the scenario in which "access network device 1 is the access network device that provides the final service to the terminal device, and the terminal device moves from the coverage of access network device 1 to the coverage of access network device 2" is used as an example for explanation.

[0247] Figure 12 is a schematic flowchart corresponding to the communication method according to Embodiment 6 of the present invention. As shown in Figure 12, this method includes the following steps.

[0248] S1201: The terminal device sends information to the access network device 2 to request that the RRC connection be resumed, where the inactive state paging cycle of the terminal device is the first paging cycle; and accordingly, the access network device 2 receives information to request that the RRC connection be resumed.

[0249] For specific details on the implementation of S1201, please refer to the explanation for S901.

[0250] S1202: Access network device 2 sends information to access network device 1 that is used to request the resumption of the RRC connection; in response, access network device 1 receives information that is used to request the resumption of the RRC connection.

[0251] For example, access network device 2 may send an acquired UE context request message to access network device 1, which includes information used to request the resumption of the RRC connection.

[0252] It can be understood that S1201 and S1202 are optional steps.

[0253] S1203, access network device 1 transmits third information to access network device 2, where the third information indicates the first paging cycle, or whether the first paging cycle is greater than a threshold.

[0254] If access network device 1 decides to perform anchor relocation, it will send third information to access network device 2 and optionally send context information of the terminal device to access network device 2 as well.

[0255] For example, access network device 1 may send an acquired UE context response message to access network device 2, where the acquired UE context response message includes context information of the terminal device and a third piece of information.

[0256] S1204: After the access network device 2 determines, based on the third piece of information, that the first paging cycle is greater than the threshold, it instructs the terminal device to enter a connected state.

[0257] Here, the access network device 2 may send an RRC restart message to the terminal device, which instructs the terminal device to restart the RRC connection or enter a connected state.

[0258] It can be understood that S1204 may be alternatively replaced with "Access network device 2 instructs terminal device to enter an idle state after determining, based on third information, that the first paging cycle is greater than a threshold."

[0259] S1205: Access network device 2 transmits fourth information to the core network element, where the fourth information is used to cancel the mobile termination communication processing policy of the terminal device; the core network element receives the fourth information accordingly.

[0260] Optionally, if in S1204 the access network device 2 instructs the terminal device to enter a connected state, after S1205, the access network device 2 may configure an enhanced INACTIVE eDRX for the terminal device using the procedure shown in Figure 5 and notify the core network element to initiate the mobile termination communication processing policy for the terminal device.

[0261] Optionally, if in S1204 the access network device 2 instructs the terminal device to enter an idle state, the fourth piece of information in S1205 may be a UE context release request. In other words, the fourth piece of information is further used to request the core network element to release the NG connection associated with the terminal device and to mark the terminal device as a connection management idle state.

[0262] According to the method described above, when a terminal device initiates the RRC restart procedure, and access network device 1 configures an enhanced INACTIVE eDRX for the terminal device, after access network device 1 performs anchor relocation, access network device 1 may send third information to access network device 2, and if the first paging cycle is greater than a threshold, access network device 2 may instruct the terminal device to enter a connected state (or idle state) based on the third information, thereby aligning the updates of the terminal device's inactive state paging cycle.

[0263] In addition, if access network device 2 determines that the first paging cycle is less than or equal to the threshold, access network device 2 does not need to instruct the terminal device to enter a connected state (or idle state). This reduces transmission resource overhead. For example, if, after access network device 2 determines that the first paging cycle is less than or equal to the threshold, the inactive state paging cycle (i.e., the second paging cycle) configured by access network device 2 for the terminal device is greater than the threshold, access network device 2 may notify the core network element. In this way, the core network element initiates the mobile termination communication processing policy for the terminal device. If the second paging cycle is less than or equal to the threshold, the core network element does not need to be notified.

[0264] It can be understood that the method in Embodiment 6 is also applicable to a scenario in which "access network device 1 is the last access network device to provide service to a terminal device, and an inactive terminal device is currently within the coverage of access network device 1." In this case, if the first paging cycle is greater than the threshold, access network device 1 may instruct the terminal device to enter a connected (or idle) state and notify the core network element to cancel the mobile termination communication processing policy of the terminal device. In addition, if the first paging cycle is less than or equal to the threshold, access network device 1 does not need to instruct the terminal device to enter a connected (or idle) state.

[0265] Embodiments 1 to 6 described above can be understood as follows.

[0266] (1) The step numbers in the flowcharts described in Embodiments 1 to 6 are merely examples of execution procedures and do not constitute a limitation on the execution order of the steps. In the embodiments of the present application, there is no strict execution order between steps that are not chronologically dependent on each other. Not all steps shown in each flowchart are necessarily steps that are executed; some steps may be deleted from each flowchart according to the actual requirements, or other possible steps may be added from each flowchart according to the actual requirements.

[0267] (2) The foregoing description focuses on the differences between the different embodiments in Embodiments 1 to 6, and Embodiments 1 to 6 may be referenced to one another, apart from the differences. In addition, different implementations or different examples within the same embodiment may also be referenced to one another.

[0268] The foregoing description primarily explains the solutions provided in the embodiments of the present application in terms of the interaction between devices and network elements. It can be understood that, in order to implement the aforementioned functions, an access network device may include corresponding hardware structures and / or software modules for implementing these functions. Those skilled in the art will readily recognize that, in embodiments of the present application, the units and algorithmic stages in the examples described with reference to the embodiments disclosed herein may be implemented in hardware, or in combination with hardware and computer software. Whether the functions are performed by hardware or by hardware driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art may employ different methods to implement the described functions for specific applications, but such implementations should not be considered beyond the scope of the present application.

[0269] In embodiments of the present application, the access network device may be divided into a plurality of functional units based on the examples of the methods described above, for example, each functional unit may be obtained through division based on each of the corresponding functions, or two or more functions may be integrated into a single unit. The integrated unit may be implemented in hardware form or in the form of a software functional unit.

[0270] When an integrated unit is used, Figure 13 is a possible exemplary block diagram of an apparatus according to one embodiment of the present application. As shown in Figure 13, the apparatus 1300 may include a processing unit 1302 and a communication unit 1303. The processing unit 1302 is configured to control and manage the operation of the apparatus 1300. The communication unit 1303 is configured to support communication between the apparatus 1300 and another device. Optionally, the communication unit 1303 may also be referred to as a transceiver unit (or transceiver) and may include a receiving unit and / or a transmitting unit configured to perform receiving and transmitting operations, respectively. The apparatus 1300 may further include a storage unit 1301 configured to store program code and / or data of the apparatus 1300.

[0271] The device 1300 may be an access network device in the embodiments described above (e.g., access network device 1 or access network device 2), or a component (e.g., a circuit or chip) located within the access network device. The processing unit 1302 may support the device 1300 in performing the operation of the access network device in the example of the method described above. Alternatively, the processing unit 1302 may primarily perform the internal operation of the access network device in the example of the method, and the communication unit 1303 may support communication between the device 1300 and another device.

[0272] For example, in one embodiment, the communication unit 1303 is configured to receive information from a terminal device used to request the resumption of a radio resource control RRC connection, wherein the inactive state paging cycle of the terminal device is a first paging cycle; and transmit the first information to the terminal device or a second access network device, wherein the first information is used to configure the inactive state paging cycle of the terminal device as a second paging cycle; and transmit the second information to a core network element, wherein the second information is used to start, cancel, or modify the mobile termination communication processing policy of the terminal device.

[0273] Optionally, the communication unit 1303 is further configured to receive third information from a third access network device, where the third information indicates a first paging cycle or indicates that the first paging cycle is greater than a threshold.

[0274] In another embodiment, the communication unit 1303 is configured to transmit context information of an inactive terminal device to a second access network device, where the terminal device's inactive paging cycle is greater than a threshold; to obtain capability information of the second access network device, where the capability information indicates that the second access network device does not support paging cycles; and to transmit fourth information to the core network element, where the fourth information instructs the cancellation of the terminal device's mobile termination communication processing policy.

[0275] In another embodiment, the communication unit 1303 is configured to receive third information from a second access network device, where the third information indicates an inactive paging cycle of a terminal device or an inactive paging cycle greater than a threshold; and to instruct the terminal device to enter a connected state based on the third information.

[0276] It should be understood that the division of the device into multiple units is merely a logical functional division. In actual implementation, all or some of these units may be integrated into a single physical entity or physically separated. In addition, all units in the device may be implemented in the form of software called by processing elements, or in the form of hardware; or some units may be implemented in the form of software called by processing elements, and some units may be implemented in the form of hardware. For example, each unit may be a separately located processing element, or it may be integrated into the chip of the device for implementation. In addition, each unit may alternatively be stored in memory in the form of a program called by the processing elements of the device to perform the function of the unit. In addition, all or some of these units may be integrated or implemented independently. Processing elements as used herein may also be referred to as processors and may be integrated circuits having signal processing capabilities. In the implementation process, the aforementioned method or the operation in the aforementioned unit may be implemented by using hardware integrated logic circuits within the processor element, or in the form of software called by the processing element.

[0277] In one example, a unit in any one of the aforementioned devices may be one or more integrated circuits configured to implement the method described above, such as one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more field programmable gate arrays (FPGAs), or a combination of at least two of these forms of integrated circuits. In another example, if a unit in the device can be implemented in a manner in which a processing element schedules a program, the processing element may be a processor, such as a central processing unit (CPU), or another processor capable of calling a program. In yet another example, these units may be integrated and implemented in the form of a system-on-a-chip (SOC).

[0278] The aforementioned unit configured for receiving is an interface circuit of the device and is configured to receive signals from another device. For example, if the device is implemented on a chip, the receiving unit is an interface circuit of the chip configured to receive signals from another chip or device. The aforementioned unit configured for transmitting is an interface circuit of the device and is configured to transmit signals to another device. For example, if the device is implemented on a chip, the transmitting unit is an interface circuit of the chip configured to transmit signals to another chip or device.

[0279] Figure 14 is a diagram showing the structure of a device according to one embodiment of the present invention. The device 1400 may be an access network device in the above-described embodiment and is configured to implement the functions of the access network device in the above-described embodiment.

[0280] As shown in Figure 14, the device 1400 may include a processor 1401, a memory 1402, and an interface circuit 1403. The processor 1401 may be configured to process communication protocols and communication data and to control the device 1400. The memory 1402 may be configured to store programs and data. The processor 1401 may execute, on a program basis, the methods performed by the device 1400 in the embodiments of the present application. The interface circuit 1403 may be used by the device 1400 to communicate with another device, which may be wired or wireless.

[0281] Alternatively, the memory 1402 may be connected externally to the device 1400. In this case, the device 1400 may include an interface circuit 1403 and a processor 1401. The interface circuit 1403 may, alternatively, be connected externally to the device 1400. In this case, the device 1400 may include a memory 1402 and a processor 1401. If both the interface circuit 1403 and the memory 1402 are connected externally to the device 1400, the device 1400 may include a processor 1401.

[0282] The device 1400 shown in Figure 14 can implement the processing related to the access network device in the embodiments of the method described above. The operation and / or function of each module in the device 1400 shown in Figure 14 is intended to implement the corresponding procedure in the embodiments of the method described above. For details, please refer to the description of the embodiments of the method described above. To avoid repetition, detailed descriptions are omitted here where appropriate.

[0283] The terms "system" and "network" can be used in the same sense as in the embodiments of the present application. "At least one" means one or more, and "a plurality of" means two or more. The term "and / or" describes the relationship between related objects and indicates that three relationships can exist. For example, A and / or B may indicate a case where only A exists, a case where both A and B exist, and a case where only B exists, where A and B may be singular or plural. The character " / " generally indicates an "or" relationship between related objects. "At least one of the following items (elements)" or a similar expression indicates any combination of these items, including a single item (element) or any combination of multiple items (elements). For example, "at least one of A, B, or C" includes A, B, C, AB, AC, BC, or ABC, and "at least one of A, B, and C" can also be understood to include A, B, C, AB, AC, BC, or ABC. In addition, unless otherwise specified, ordinal numbers such as "first" and "second" in the embodiments of the present application are used to distinguish multiple objects and are not used to limit the order, chronological order, priority, or importance of multiple objects.

[0284] A person skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application may use the form of an embodiment having only hardware, only software, or a combination of software and hardware. Furthermore, the present application may use the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, optical memories, and the like) containing computer-usable program code.

[0285] This application is described by reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the present application. It should be understood that computer program instructions may be used to implement each process and / or each block in the flowcharts and / or block diagrams, and combinations of processes and / or blocks in the flowcharts and / or block diagrams. These computer program instructions are provided for the processor of a general-purpose computer, a dedicated computer, an embedded processor, or another programmable data processing device, resulting in a machine being generated, and as a result, an apparatus for implementing specific functions in one or more processes in the flowchart and / or one or more blocks in the block diagram may be generated by instructions executed by the processor of the computer or another programmable data processing device.

[0286] Alternatively, these computer program instructions can be directed to a computer or another programmable data processing device to operate in a specific manner, and as a result, they may be stored in a computer-readable memory that generates an artifact including an instruction device by the instructions stored in the computer-readable memory. The instruction device implements specific functions in one or more processes of the flowchart and / or one or more blocks of the block diagram.

[0287] Alternatively, these computer program instructions may be loaded onto a computer or another programmable data processing device, and as a result, a series of operations and steps are executed on the computer or another programmable device, and as a result, a computer-implemented process is generated. Therefore, the instructions executed on the computer or another programmable device provide steps for implementing specific functions in one or more processes of the flowchart and / or one or more blocks of the block diagram.

[0288] It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from its spirit and scope. Thus, the present application is intended to encompass such modifications and variations, provided that they fall within the scope of protection defined by the following claims and equivalent art.

Claims

1. A communication method, wherein the method is applied to a first access network device, and the method is The step of receiving information from a terminal device used to request the resumption of a wireless resource control (RRC) connection, wherein the inactive state paging cycle of the terminal device is the first paging cycle; and A step of transmitting first information to the terminal device or a second access network device, wherein the first information is used to configure the inactive state paging cycle of the terminal device as a second paging cycle; and a step of transmitting second information to a core network element, wherein the second information is used to start, cancel, or modify the mobile termination communication processing policy of the terminal device. A communication method that includes the following features.

2. The method according to claim 1, wherein the information used to request the resumption of the RRC connection is an RRC resumption cause value, and the RRC resumption cause value indicates a wireless access network RAN-based notification area update.

3. The aforementioned method, The step of receiving third information from a third access network device, wherein the third information indicates the first paging cycle, or indicates that the first paging cycle is greater than a threshold; or In the step of sending an RRC release message to the terminal device, the RRC release message instructs the terminal device to enter an inactive state, and the RRC release message includes the first paging cycle. The method according to claim 1 or 2, further comprising:

4. The method according to any one of claims 1 to 3, wherein the first information is conveyed in an RRC release message, and the RRC release message indicates that the terminal device is in the inactive state.

5. The method according to any one of claims 1 to 4, wherein the second information is conveyed in a route switching request message.

6. The method according to any one of claims 1 to 5, wherein if the first paging cycle is less than or equal to a threshold and the second paging cycle is greater than the threshold, the second information is used to initiate the mobile termination communication processing policy of the terminal device.

7. The method according to any one of claims 1 to 5, wherein if the first paging cycle is greater than the threshold, the second information is used to cancel the mobile termination communication processing policy of the terminal device.

8. The method according to any one of claims 1 to 5, wherein if the first paging cycle is greater than the threshold and the second paging cycle is greater than the threshold, the second information is used to restart the mobile termination communication processing policy of the terminal device.

9. The method according to any one of claims 3 to 8, wherein the threshold is 10.24 seconds.

10. The second information includes the second paging cycle and / or instruction information, wherein The instruction information indicates an action on the communication processing policy, and the action includes starting, canceling, or modifying. The method according to any one of claims 1 to 9.

11. A communication method, wherein the method is applied to a first access network device, and the method is The step involves sending context information of an inactive terminal device to a second access network device, where the inactive paging cycle of the terminal device is greater than a threshold; The step of obtaining capability information of the second access network device, wherein the capability information indicates that the second access network device does not support the paging cycle; and The fourth step involves transmitting the information to the core network element, where the fourth information instructs the terminal device to cancel its mobile termination communication processing policy. A communication method that includes the following features.

12. The step of obtaining the capability information of the second access network device is: Steps to receive the capability information from the second access network device. Having, The method according to claim 11.

13. A communication device comprising a module configured to perform the method described in any one of claims 1 to 12.

14. A communication device comprising a processor, wherein the processor is coupled to a memory, the memory stores a computer program; and the processor is configured to call the computer program in the memory, thereby enabling the communication device to perform the method according to any one of claims 1 to 12.

15. A computer-readable storage medium, wherein the storage medium stores a computer program or instruction, and when the computer program or instruction is executed by a computer, the method according to any one of claims 1 to 12 is implemented in the computer-readable storage medium.

16. A computer program product, wherein, when a computer reads and executes the computer program product, the computer is able to perform the method described in any one of claims 1 to 12.

Images