Communication methods and communication apparatus

By carrying the first indication information and a timer mechanism in the registration acceptance message, the cell misalignment problem caused by the terminal not successfully receiving the registration acceptance message is solved, ensuring normal communication and system compatibility of the terminal.

WO2024234926A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/088616
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-04-18
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In the prior art, when the terminal fails to successfully receive the registration acceptance message, the network side cannot perceive, resulting in misalignment of the cells and affecting the normal communication of the terminal.

Method used

By carrying the first indication information in the registration acceptance message, the terminal replys to the registration completion message and starts the timer in the core network device. If the registration completion message is not received during the timeout, the registration acceptance message is retransmitted to ensure the cell alignment.

Benefits of technology

Ensure the alignment of cells in the registration acceptance message on the network side and the terminal side, improve system compatibility, and ensure that the terminal can communicate normally.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024088616_21112024_PF_FP_ABST
    Figure CN2024088616_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the present application are communication methods and a communication apparatus. A method comprises: sending a registration request message; receiving a registration acceptance message, the registration acceptance message carrying first instruction information, and the first instruction information being used for instructing to reply a registration completion message after receiving the registration acceptance message; and, according to the registration acceptance message, sending the registration completion message. On the basis of the method, cell alignment for the registration acceptance messages at the network side and the terminal side can be ensured, so that the terminal can normally communicate. In addition, carrying the first instruction information so as to enable the terminal to reply the registration completion message further helps to improve the system compatibility.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 12, 2023, with application number 202310537534.7, and priority to the Chinese patent application entitled “A Communication Method and Communication Device”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method and a communication device. Background Art

[0003] The current terminal registration process typically involves the terminal sending a registration request message to the network. The network then sends a registration accept message to the terminal, which includes information elements. These information elements can include PEIPS parameters or eDRX parameters. If the terminal fails to successfully receive the registration accept message containing these information elements, the network will not be able to detect whether the terminal has successfully received them and will not retransmit the registration accept message to the terminal. This can cause information element misalignment between the network and terminal, impacting subsequent normal communication.

[0004] Summary of the Invention

[0005] The present application provides a communication method and a communication device, which are conducive to ensuring the alignment of information elements in the registration acceptance message on the network side and the terminal side, so that the terminal can communicate normally.

[0006] In a first aspect, the present application provides a communication method, which can be executed by a terminal, or by a module applied to the terminal (such as a processor, chip, or chip system, etc.), or by a logical node, logical module, or software that can implement all or part of the terminal functions. The communication method includes:

[0007] Send a registration request message; receive a registration acceptance message, the registration acceptance message carries a first indication information, the first indication information is used to indicate that a registration completion message should be replied after receiving the registration acceptance message; according to the registration acceptance message, send a registration completion message.

[0008] Based on the method described in the first aspect, it is beneficial to ensure the alignment of the information elements in the registration acceptance message on the network side and the terminal side, so that the terminal can communicate normally, and by carrying the first indication information to enable the terminal to reply to the registration completion message, it is also beneficial to improve the compatibility of the system.

[0009] In a possible embodiment, the registration request message carries capability information of the terminal, where the capability information is used to indicate support for replying a registration completion message after receiving a registration acceptance message.

[0010] This possible embodiment is beneficial for terminals compatible with older versions of the protocol.

[0011] In a possible embodiment, the registration accept message further carries a Packet Assisted Paging Early Indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter.

[0012] Based on this possible embodiment, the PEIPS parameters on the network side and the terminal side can be aligned so that the terminal can successfully receive paging messages or save terminal power consumption. Alternatively, based on this possible embodiment, the eDRX parameters on the network side and the terminal side can be aligned to prevent the terminal from losing downlink information.

[0013] In a second aspect, the present application provides a communication method, which can be performed by a core network device, or by a module (such as a processor, chip, or chip system) applied to the core network device, or by a logical node, logical module, or software that can implement all or part of the core network device functions. The communication method includes:

[0014] Receive a registration request message from a terminal; send a registration acceptance message to the terminal based on the registration request message, wherein the registration acceptance message carries first indication information, and the first indication information is used to indicate to reply with a registration completion message after receiving the registration acceptance message; start a timer; if a registration completion message is received from the terminal before the timer expires, stop the timer; or, if a registration completion message is not received from the terminal when the timer expires, retransmit the registration acceptance message.

[0015] In a possible embodiment, the registration request message carries capability information of the terminal, where the capability information is used to indicate support for replying a registration completion message after receiving a registration acceptance message.

[0016] In a possible embodiment, starting the timer includes: if the registration request message carries the capability information of the terminal and the registration accept message carries the first indication information, starting the timer.

[0017] In a possible embodiment, the registration accept message further carries a Packet Assisted Paging Early Indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter.

[0018] The beneficial effects of the second aspect can be referred to the beneficial effects of the first aspect, and will not be repeated here.

[0019] In a third aspect, the present application provides a communication method, which can be executed by a terminal, or by a module applied to the terminal (such as a processor, chip, or chip system, etc.), or by a logical node, logical module, or software that can implement all or part of the terminal functions. The communication method includes:

[0020] Send a registration request message; receive a registration accept message; if the registration accept message carries the Packet Assisted Paging Early Indication PEIPS parameter or the enhanced discontinuous reception eDRX parameter, send a registration completion message.

[0021] It can be seen that the method described in the third aspect is conducive to ensuring that the PEIPS parameters or eDRX parameters in the registration acceptance messages on the network side and the terminal side are aligned, so that the terminal can communicate normally.

[0022] In a possible embodiment, the method further includes: determining that the registration accept message carries a PEIPS parameter or an eDRX parameter.

[0023] In a possible embodiment, the registration request message carries capability information of the terminal, where the capability information is used to indicate support for replying a registration completion message after receiving a registration accept message carrying a PEIPS parameter or an eDRX parameter.

[0024] Based on this possible embodiment, it is beneficial to be compatible with terminals of old version protocols.

[0025] In a fourth aspect, the present application provides a communication method, which can be performed by a core network device, or by a module (such as a processor, chip, or chip system) applied to the core network device, or by a logical node, logical module, or software that can implement all or part of the core network device functions. The communication method includes:

[0026] Receive a registration request message from the terminal; send a registration accept message to the terminal based on the registration request message; if the registration accept message carries the Packet Assisted Paging Early Indication PEIPS parameter or the enhanced discontinuous reception eDRX parameter, start a timer; if a registration completion message is received from the terminal before the timer expires, stop the timer; or, if the registration completion message is not received from the terminal when the timer expires, retransmit the registration accept message.

[0027] In a possible embodiment, the registration request message carries capability information of the terminal, where the capability information is used to indicate support for replying a registration completion message after receiving a registration accept message carrying a PEIPS parameter or an eDRX parameter.

[0028] In a possible embodiment, if the registration acceptance message carries a paging packet assisted paging early indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter, the timer is started, including: if the registration request message carries the terminal capability information and the registration acceptance message carries a paging packet assisted paging early indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter, the timer is started.

[0029] The beneficial effects of the fourth aspect can be found in the beneficial effects of the third aspect, which will not be repeated here.

[0030] In a fifth aspect, the present application provides a communication method, which can be executed by a terminal, or by a module applied to the terminal (such as a processor, chip, or chip system, etc.), or by a logical node, logical module, or software that can implement all or part of the terminal functions. The communication method includes:

[0031] Send a registration request message that carries the terminal's capability information, which indicates support for Packet-Assisted Early Indication for Paging (PEIPS); start a timer; if the timer times out without receiving a registration accept message, monitor the terminal's paging message during the paging opportunity within the discontinuous reception (DRX) cycle.

[0032] The method described in the fifth aspect is helpful in preventing the terminal from losing the paging message.

[0033] In a possible embodiment, before sending the registration request message, the terminal's paging message may be monitored in a paging packet. The paging packet is a user equipment identifier UE_ID packet or a PEIPS paging packet, and the terminal is located in the paging packet.

[0034] Based on this possible embodiment, it is helpful to avoid the terminal from losing the paging message.

[0035] In a sixth aspect, the present application provides a communication method, which can be executed by a terminal, or by a module applied to the terminal (such as a processor, chip, or chip system, etc.), or by a logical node, logical module, or software that can implement all or part of the terminal functions. The communication method includes:

[0036] Send a registration request message, which carries capability information of the terminal, and the capability information includes first indication information, and the first indication information is used to indicate support for paging group assisted paging early indication PEIPS; receive a registration accept message, and the registration accept message carries a PEIPS parameter; when the value of the PEIPS parameter does not belong to the valid value range supported by the terminal, listen to the paging message of the terminal during the paging opportunity within the discontinuous reception DRX cycle, or listen to the paging message of the terminal on a specific PEIPS paging group.

[0037] Based on the method described in the sixth aspect, when the value of the PEIPS parameter does not belong to the valid value range supported by the terminal, the terminal can use a traditional paging monitoring method to monitor its own paging message, which is helpful to avoid the terminal losing the paging message.

[0038] In a possible embodiment, the capability information further includes a valid value range of a PEIPS parameter supported by the terminal. Based on this possible embodiment, it is beneficial to reduce the power consumption of the core network device.

[0039] In a seventh aspect, the present application provides a communication method, which can be performed by a core network device, or by a module (such as a processor, chip, or chip system) applied to the core network device, or by a logical node, logical module, or software that can implement all or part of the core network device functions. The communication method includes:

[0040] Receive a registration request message from a terminal, the registration request message carrying capability information of the terminal, the capability information including first indication information, the first indication information being used to indicate support for paging group assisted early indication of paging (PEIPS); send a registration acceptance message based on the registration request message, the registration acceptance message carrying a PEIPS parameter; and page the terminal in a specific PEIPS paging group and a PEIPS paging group corresponding to the PEIPS parameter.

[0041] In a possible embodiment, the capability information also includes a valid value range of the PEIPS parameter supported by the terminal, and paging the terminal in a specific PEIPS paging group and a PEIPS paging group corresponding to the PEIPS parameter, including: when the value of the PEIPS parameter does not fall within the valid value range supported by the terminal, paging the terminal in a specific PEIPS paging group and a PEIPS paging group corresponding to the PEIPS parameter.

[0042] The beneficial effects of the seventh aspect can be found in the beneficial effects of the sixth aspect and will not be repeated here.

[0043] In an eighth aspect, the present application provides a communication method, which can be executed by a terminal, or by a module applied to the terminal (such as a processor, chip, or chip system, etc.), or by a logical node, logical module, or software that can implement all or part of the terminal functions. The communication method includes:

[0044] Send a registration request message, which carries the capability information of the terminal, and the capability information includes first indication information and a valid value range of the paging packet assisted paging early indication PEIPS parameter supported by the terminal, and the first indication information is used to indicate support for PEIPS; receive a registration acceptance message, which carries the PEIPS parameter, and the value of the PEIPS parameter is within the valid value range.

[0045] The method described in the eighth aspect is helpful in preventing the terminal from losing the paging message.

[0046] In a ninth aspect, the present application provides a communication method, which can be performed by a core network device, or by a module (such as a processor, chip, or chip system) applied to the core network device, or by a logical node, logical module, or software that can implement all or part of the core network device functions. The communication method includes:

[0047] Receive a registration request message, which carries the capability information of the terminal, the capability information includes first indication information and a valid value range of the paging packet assisted paging early indication PEIPS parameter supported by the terminal, and the first indication information is used to indicate support for PEIPS; according to the registration request message, send a registration acceptance message, which carries the PEIPS parameter, and the value of the PEIPS parameter is within the valid value range.

[0048] The method described in the ninth aspect is helpful in preventing the terminal from losing the paging message.

[0049] In a tenth aspect, the present application provides a communication method, which can be executed by a terminal, or by a module applied to the terminal (such as a processor, chip, or chip system, etc.), or by a logical node, logical module, or software that can implement all or part of the terminal functions. The communication method includes:

[0050] The invention also includes receiving downlink information based on enhanced discontinuous reception (eDRX) parameters; sending a registration request message, the registration request message carrying capability information, the capability information indicating support for eDRX; starting a timer; and if the timer times out and no registration accept message is received, receiving downlink information based on the discontinuous reception (DRX) parameters.

[0051] The method described in the tenth aspect is helpful in preventing the terminal from losing downlink information.

[0052] In an eleventh aspect, the present application provides a communication device, for example, the communication device may be a terminal or a module applied to a terminal, such as a processor, a chip, or a chip system, and may also be a logical node, a logical module, or software that can implement all or part of the terminal functions. The communication device includes a module / unit for executing any method of the first aspect, the third aspect, the fifth aspect, the sixth aspect, the eighth aspect, or the tenth aspect and any possible implementation thereof.

[0053] In a twelfth aspect, the present application provides a communication device. For example, the communication device may be a core network device or a module applied to a core network device, such as a processor, chip, or chip system. It may also be a logical node, logical module, or software that can implement all or part of the core network device functions. The communication device includes a module / unit for executing any method of the second aspect, the fourth aspect, the seventh aspect, or the ninth aspect and any implementation thereof.

[0054] In the thirteenth aspect, the present application provides a communication device, including a processor, the processor and a memory are coupled, the memory is used to store programs or instructions, when the program or instructions are executed by the processor, the device executes the method described in any one of the above-mentioned aspects 1 to 10.

[0055] In the fourteenth aspect, the present application provides a chip, which includes a processor and an interface, and the processor and the interface are coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions, so that the chip executes the method described in any one of the above-mentioned aspects one to tenth.

[0056] In a fifteenth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are called, any one of the above-mentioned first to tenth aspects is executed.

[0057] In a sixteenth aspect, the present application provides a computer program product, comprising: a computer program code, wherein when the computer program code is executed, any one of the above-mentioned first to tenth aspects is executed.

[0058] In the seventeenth aspect, the present application provides a communication system, which includes a communication device (such as a terminal) for executing the method described in the first aspect and a communication device (such as an access network device) for executing the second aspect, or the communication system includes a communication device (such as a terminal) for executing the method described in the third aspect and a communication device (such as an access network device) for executing the fourth aspect, or the communication system includes a communication device (such as a terminal) for executing the method described in the sixth aspect and a communication device (such as an access network device) for executing the seventh aspect, or the communication system includes a communication device (such as a terminal) for executing the method described in the eighth aspect and a communication device (such as an access network device) for executing the ninth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] FIG1 is a possible, non-limiting schematic diagram of a system provided by the present application;

[0060] FIG2 is a flow chart of a communication method provided by the present application;

[0061] FIG3 is a flow chart of a communication method provided by the present application;

[0062] FIG4 is a flow chart of a communication method provided by the present application;

[0063] FIG5 is a flow chart of a communication method provided by the present application;

[0064] FIG6 is a flow chart of a communication method provided by the present application;

[0065] FIG7 is a flow chart of a communication method provided by the present application;

[0066] FIG8 is a flow chart of a communication method provided by the present application;

[0067] FIG9 is a flow chart of a communication method provided by the present application;

[0068] FIG10 is a flow chart of a communication method provided by the present application;

[0069] FIG11 is a flow chart of a communication method provided by the present application;

[0070] FIG12 is a schematic structural diagram of a communication device provided by the present application;

[0071] FIG13 is a schematic structural diagram of another communication device provided in this application. DETAILED DESCRIPTION

[0072] The specific embodiments of the present application are further described in detail below with reference to the accompanying drawings.

[0073] The terms "first" and "second" and the like in the specification, claims, and drawings of this application are used to distinguish between different objects, not to describe a particular order. Furthermore, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.

[0074] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0075] In this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0076] In this application, "sending information" can be understood as one device sending information to another device, or as one logical module within a device sending information to another logical module. For example, "an access network device sending information" can be understood as an access network device sending information to another device (such as a terminal), or as logical module 1 within an access network device sending information to logical module 2 within the access network device.

[0077] In this application, "receiving information" can be understood as one device receiving information from another device, or as a logical module within a device receiving information from another logical module. For example, "an access network device receiving information" can be understood as the access network device receiving information from another device (such as a terminal), or as logical module 1 within the access network device receiving information from logical module 2 within the access network device.

[0078] In this application, "sending information to... (e.g., a terminal)" or the related illustrations in the accompanying drawings can be understood as the destination end of the information being the terminal. This can include sending information to the terminal directly or indirectly. "Receiving information from... (e.g., a terminal)" or "receiving information from... (e.g., a terminal)" or "receiving information sent by (e.g., a terminal)", or the related illustrations in the accompanying drawings can be understood as the source end of the information being the terminal, which can include receiving information from the terminal directly or indirectly. The information may be processed as necessary between the source end and the destination end of the information transmission, such as format changes, etc., but the destination end can understand the valid information from the source end. Similar expressions in this application can be understood similarly and will not be repeated here.

[0079] To better understand the embodiments of the present application, the following first introduces the system architecture involved in the embodiments of the present application:

[0080] The embodiments of the present application can be applied to communication systems evolved after 5G, such as long term evolution (LTE) systems, fifth generation mobile communication (5G) systems, sixth generation mobile communication (6G) systems, satellite communications, and short-range wireless communication systems. Among them, the wireless communication systems mentioned in the embodiments of the present application include but are not limited to: three major application scenarios of 5G / 6G mobile communication systems: enhanced mobile broadband (eMBB), ultra reliable low latency communication (URLLC) and massive machine type communication (mMTC), long range Internet of Things (LoRa) systems or vehicle networking systems. The wireless communication system may include one or more access network devices, and one or more terminal devices.

[0081] FIG1 shows a possible, non-limiting system schematic diagram. As shown in FIG1 , a communication system 10 includes a radio access network (RAN) 100 , a core network (CN) 200 , and the Internet 300 .

[0082] RAN 100

[0083] The RAN 100 includes at least one RAN node (e.g., 110a and 110b in FIG. 1 , collectively referred to as 110) and at least one terminal (e.g., 120a-120j in FIG. 1 , collectively referred to as 120). The RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment (not shown in FIG. 1 ). The terminal 120 is wirelessly connected to the RAN node 110. The RAN node 110 is wirelessly or wiredly connected to the core network 200. The core network equipment in the core network 200 and the RAN node 110 in the RAN 100 may be separate physical devices, or they may be a single physical device that integrates core network logical functions and radio access network logical functions.

[0084] The RAN 100 may be a cellular system related to the Third Generation Partnership Project (3GPP), such as a 4G or 5G mobile communication system, or a future-oriented evolutionary system (such as a 6G mobile communication system). The RAN 100 may also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. The RAN 100 may also be a communication system that integrates two or more of the above systems.

[0085] 1.RAN node 110

[0086] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, constitutes part of the communication system and facilitates wireless access for terminals. Multiple RAN nodes 110 in the communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminal 120j accessing RAN 100 via network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functionality, and network elements 120a-120j can be understood as communication devices with terminal functionality.

[0087] In one possible scenario, the RAN node 110 may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a sixth-generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. The RAN node 110 may be a macro base station (such as 110a in FIG. 1 ), a micro base station or an indoor station (such as 110b in FIG. 1 ), a relay node or a donor node, or a wireless controller in a CRAN scenario. In one possible embodiment, the RAN node 110 may also be a server, a wearable device, a vehicle, or an onboard device. For example, the access network device in vehicle-to-everything (V2X) technology may be a roadside unit (RSU). All or part of the functionality of the RAN node 110 in this application may also be implemented via software functions running on hardware, or via virtualized functions instantiated on a platform (such as a cloud platform). The RAN node 110 in this application may also be a logical node, a logical module or software that can implement all or part of the functions of the RAN node 110.

[0088] In another possible scenario, multiple RAN nodes 110 collaborate to assist the terminal in achieving wireless access, and different RAN nodes 110 respectively implement part of the functions of the base station. For example, the RAN node 110 can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately or included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0089] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0090] In the embodiments of the present application, the form of the RAN node 110 is not limited. The device used to implement the functions of the RAN node 110 can be the RAN node 110, or it can be a device that supports the RAN node 110 in implementing the functions, such as a chip system. The device can be installed in the RAN node 110 or used in conjunction with the RAN node 110.

[0091] For ease of description, the RAN node 110 will be referred to as an access network device in the following description.

[0092] 2. Terminal

[0093] Terminals can also be referred to as terminal devices, user equipment (UE), mobile stations, or mobile terminals. They can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, and smart home appliances.

[0094] In the embodiments of the present application, the form of the terminal is not limited. The device for implementing the function of the terminal can be a terminal; it can also be a device that can support the terminal to implement the function, such as a chip system. The device can be installed in the terminal or used in conjunction with the terminal.

[0095] 2. Core Network 200

[0096] Core network 200 performs three major functions: registration, connection, and session management. Core network 200 includes core network equipment. For example, the core network equipment may include an Active Mobile Device (AMF). The AMF network element is primarily responsible for mobility management in mobile networks, such as user location updates, user network registration, and user handovers.

[0097] Optionally, the core network equipment may also include one or more of the following: network slice selection function (NSSF), network exposure function (NEF), network function repository function (NRF), policy control function (PCF), unified data management (UDM) network element, application function (AF), network slice and SNPN authentication and authorization function (NSSAAF), authentication server function (AUSF), access and mobility management function (AMF), session management function (SMF), service communication prox (SCP), network slice admission control function (NSACF), user plane function (UPF), unified data repository (UDR), etc.

[0098] In the embodiments of the present application, the form of the core network device is not limited. The device used to implement the functions of the core network device can be the core network device; it can also be a device that can support the core network device to implement the functions, such as a chip system. The device can be installed in the core network device or used in conjunction with the core network device.

[0099] In order to facilitate the understanding of the content of this solution, some of the terms involved in the embodiments of this application are explained below to facilitate understanding by those skilled in the art. This part is only for ease of understanding and cannot be regarded as a disclosure or specific limitation of the technical solution of this application.

[0100] 1. Paging: Paging is an important technology in wireless communication systems. Network equipment can find terminals through paging and initiate services to the terminals.

[0101] 2. Paging monitoring method based on PEIPS paging group

[0102] The PEIPS paging group-based paging monitoring method can also be called the paging early indication with paging subgrouping assistance (PEIPS) paging monitoring method or the core network group-based paging monitoring method. The core network assigns the terminal to a group and assigns a paging subgrouping ID. For example, the valid value range of the paging subgrouping ID is (0-7), with a total of 8 groups. The terminal only needs to monitor its own paging messages in the PEIPS paging group configured by the network.

[0103] 3. Paging monitoring method based on user equipment identification (UE_ID) grouping

[0104] In the UE_ID group-based paging monitoring method, the access network device assigns terminals to a specific group and then configures it through system messages. This group is called a UE_ID group or UE_ID paging group. The terminal then monitors its own paging messages within the UE_ID group. The UE_ID group-based paging monitoring method is described in Section 7 of 3GPP 38.304 and is not detailed here.

[0105] 4. Traditional paging monitoring method

[0106] In the traditional paging monitoring method, the terminal will monitor its own paging message during the paging occasion (PO) within the discontinuous reception (DRX) cycle. For a terminal device, each paging cycle includes a PO. The location where the paging downlink control information (paging DCI) and / or the paging message is located is called a PO. A paging occasion includes the location of the paging DCI and the time domain location of the paging message. The terminal device can calculate its own corresponding PO based on relevant parameters (such as its own identification number information and paging-related parameters provided by the system message, etc.). So that the paging DCI and paging message can be received at the corresponding PO.

[0107] The paging DCI is used to schedule the paging message, that is, the paging DCI indicates the time-frequency resources of the paging message. After receiving the paging DCI, the terminal device can receive the paging message based on the time-frequency resources of the paging message indicated by the paging DCI.

[0108] The paging message is carried on the paging physical downlink shared channel (PDSCH) and is used to page terminal devices. The paging message includes the identifier of the terminal device being paged. In other words, if the identifier of a terminal device is included in the paging message, it means that the terminal device is being paged by the network device.

[0109] 5. Enhanced discontinuous reception (eDRX)

[0110] The 5G system introduces LTE's DRX and expands it to eDRX, which helps terminals avoid waking up frequently to listen to network paging or downlink information, thereby improving terminal power consumption.

[0111] The communication method and communication device are further introduced below in conjunction with the accompanying drawings. It can be understood that the core network device and the terminal are used as examples of the execution subjects of the interaction diagram in this application, but this application does not limit the execution subjects of the interaction diagram. For example, the core network device in the method provided by this application can also be a chip, chip system, or processor applied to the core network device, or a logical node, logical module or software that can implement all or part of the core network device; the terminal in the method provided by this application can also be a chip, chip system, or processor applied to the terminal, or a logical node, logical module or software that can implement all or part of the terminal functions.

[0112] Please refer to FIG2 , which is a flow chart of a communication method provided in an embodiment of the present application, wherein:

[0113] 201. A terminal sends a registration request message. Correspondingly, a core network device may receive the registration request message.

[0114] Optionally, the core network device may be an AMF.

[0115] 202. The core network device sends a registration accept message (registration accept) to the terminal according to the registration request message. The registration accept message carries first indication information. The first indication information is used to instruct the terminal to reply with a registration completion message after receiving the registration accept message.

[0116] Optionally, the first indication information is used to instruct the terminal to reply with a registration completion message after receiving the registration acceptance message, which can also be understood as the first indication information is used to instruct the terminal to "require information element confirmation." For example, the first indication information can be "acknowledgement required."

[0117] That is, if the terminal receives the registration accept message and recognizes that the registration accept message carries the first indication information, the terminal sends a registration completion message to notify the core network device that the terminal has successfully received the registration accept message.

[0118] 203. The core network device starts a timer.

[0119] In an embodiment of the present application, after the core network device sends a registration acceptance message to the terminal, if the registration acceptance message carries the first indication information, the core network device starts a timer.

[0120] Optionally, the timer may be T3550 or a timer of other duration, which is not limited in the embodiment of the present application.

[0121] 204. The terminal sends a registration complete message (registration complete) according to the registration acceptance message.

[0122] In the embodiment of the present application, if the terminal receives a registration acceptance message and recognizes that the registration acceptance message carries the first indication information, the terminal sends a registration completion message.

[0123] 205. If the core network device receives a registration completion message from the terminal before the timer expires, the core network device stops the timer.

[0124] If the core network device receives the registration completion message from the terminal before the timer expires, it proves that the terminal has successfully received the registration completion message. Therefore, the core network device stops the timer and does not retransmit the registration acceptance message.

[0125] If the terminal does not receive the Registration Complete message, it will not send a Registration Complete message. If the core network device does not receive the Registration Complete message from the terminal before the timer expires, it will retransmit the Registration Accept message to synchronize the information elements in the Registration Accept message between the terminal and the core network device. For example, steps 301 to 304 are shown in Figure 3.

[0126] In a possible embodiment, the registration request message carries capability information of the terminal, where the capability information is used to indicate that the terminal supports replying a registration completion message after receiving the registration acceptance message.

[0127] Optionally, the capability information is used to indicate that the terminal supports replying a registration completion message after receiving a registration acceptance message, which can also be understood as indicating that the terminal supports "cell acknowledgment". For example, the capability information is "acknowledgement supported".

[0128] Assume that the core network device sends a registration acceptance message carrying first indication information to a terminal using an old version of the protocol. The terminal using the old version of the protocol cannot recognize the first indication information in the registration acceptance message. If the information element carried in the registration acceptance message is not an information element that requires a registration completion message to be replied as required by the protocol, then after receiving the registration acceptance message, the terminal using the old version of the protocol will not reply with a registration completion message. After the core network device sends the registration acceptance message, it starts a timer to wait for the terminal using the old version of the protocol to reply with a registration completion message. The core network device may not receive the registration completion message sent by the terminal using the old version of the protocol, causing the core network device to keep retransmitting the registration acceptance message.

[0129] The above-mentioned capability information can be used by the core network device to distinguish whether the terminal is a terminal of the new version of the protocol or a terminal of the old version of the protocol. By making the terminal carry the above-mentioned capability information in the registration request message, the core network device can know that the terminal is a terminal of the new version of the protocol. If the terminal is a terminal of the new version of the protocol, and the information element to be carried in the registration acceptance message is an information element that requires the core network device and the terminal to be aligned (such as PEIPS parameters or eDRX parameters), the core network device will carry the first indication information in the registration acceptance message. After the core network device sends the registration acceptance message, if the registration acceptance message carries the first indication information, the core network device will start the timer and wait for the terminal to reply with a registration completion message.

[0130] If the terminal does not include the aforementioned capability information in the Registration Request message, the core network device will recognize that the terminal is using an older protocol version. If the terminal is using an older protocol version, the core network device will not include the first indication information in the Registration Accept message. Instead, the core network device will process the information element items according to the older protocol specifications to determine whether to start a timer after sending the Registration Accept message, waiting for the terminal to respond with a Registration Complete message. Therefore, including the aforementioned capability information in the Registration Request message facilitates system compatibility with terminals using older protocol versions.

[0131] In a possible embodiment, if the registration request message carries the terminal's capability information and the registration accept message carries the first indication information, the core network device starts the timer. This possible embodiment is beneficial for compatibility with terminals of older versions of the protocol.

[0132] For example, the core network device will only carry the first indication information in the registration accept message if it determines that the registration request message carries the above-mentioned capability information and that the information element to be carried in the registration accept message is an information element that requires alignment between the core network device and the terminal (such as a PEIPS parameter or an eDRX parameter). If the registration accept message sent by the core network device carries the first indication information, the core network device will trigger the start timer only after sending the registration accept message, waiting for the terminal to reply with a registration completion message.

[0133] If the terminal carries the aforementioned capability information in the registration request message, but the information element to be carried in the registration accept message does not require alignment between the core network device and the terminal, the first indication information may not be carried in the registration accept message. After the core network device sends the registration accept message, it does not start the timer.

[0134] If the terminal does not carry the above-mentioned capability information in the registration request message, the core network device does not carry the first indication information in the registration acceptance message, and still determines whether to start the timer after sending the registration acceptance message according to the processing of the information element items specified in the old protocol to wait for the terminal to reply with a registration completion message.

[0135] In a possible embodiment, the registration accept message further carries a PEIPS parameter or an eDRX parameter.

[0136] For example, the PEIPS parameter may be a paging group identifier, or may be other parameters related to PEIPS.

[0137] For another example, the eDRX parameter may be an eDRX cycle, or may be other parameters related to eDRX.

[0138] Based on this possible embodiment, the PEIPS parameters on the network side and the terminal side can be aligned so that the terminal can successfully receive paging messages or save terminal power consumption. Alternatively, based on this possible embodiment, the eDRX parameters on the network side and the terminal side can be aligned to prevent the terminal from losing downlink information.

[0139] In one possible embodiment, information exchange can be performed between a terminal and a core network device via an access network device. For example, a terminal can send a registration request message to a core network device via the access network device. Accordingly, the core network device can receive the registration request message via the access network device. In another example, the core network device can send a registration acceptance message to a terminal via the access network device. Accordingly, the terminal can receive the registration acceptance message via the access network device. In another example, a terminal can send a registration completion message to a core network device via the access network device. Accordingly, the core network device can receive the registration completion message via the access network device. The same applies to the following embodiments and will not be further described.

[0140] It can be seen that the method described in Figure 2 is conducive to ensuring the alignment of the information elements in the registration acceptance message on the network side and the terminal side, so that the terminal can communicate normally, and by carrying the first indication information to enable the terminal to reply to the registration completion message, it is also conducive to improving the compatibility of the system.

[0141] Please refer to FIG4 , which is a flow chart of another communication method provided in an embodiment of the present application, wherein:

[0142] 401. The terminal sends a registration request message. Correspondingly, the core network device may receive the registration request message.

[0143] Optionally, the core network device may be an AMF.

[0144] 402. The core network device sends a registration acceptance message to the terminal according to the registration request message.

[0145] For descriptions of PEIPS parameters or eDRX parameters, please refer to the previous descriptions and will not be repeated here.

[0146] 403. If the registration accept message carries a PEIPS parameter or an eDRX parameter, the core network device starts a timer.

[0147] In an embodiment of the present application, after the core network device sends a registration acceptance message to the terminal, if the registration acceptance message carries a PEIPS parameter or an eDRX parameter, the core network device starts a timer.

[0148] Optionally, the timer may be T3550 or a timer of other duration, which is not limited in the embodiment of the present application.

[0149] 404. If the registration accept message carries a PEIPS parameter or an eDRX parameter, the terminal sends a registration completion message.

[0150] That is, if the terminal receives a registration accept message, and the registration accept message carries a PEIPS parameter or an eDRX parameter, the terminal sends a registration completion message.

[0151] Optionally, before sending the registration completion message, the terminal determines that the registration accept message carries the PEIPS parameter or the eDRX parameter. That is, if the terminal receives the registration accept message and recognizes that the registration accept message carries the PEIPS parameter or the eDRX parameter, the terminal sends the registration completion message.

[0152] Optionally, if the terminal receives the registration accept message and does not recognize that the registration accept message carries the PEIPS parameter or the eDRX parameter, the terminal determines whether to send a registration completion message by processing the information element item according to the old protocol.

[0153] 405. If a registration completion message is received from the terminal before the timer times out, the core network device stops the timer.

[0154] If the core network device receives the registration completion message from the terminal before the timer expires, it proves that the terminal has successfully received the registration completion message. Therefore, the core network device stops the timer and does not retransmit the registration acceptance message.

[0155] If the terminal does not receive the Registration Complete message, it will not send a Registration Complete message. If the core network device does not receive the Registration Complete message from the terminal before the timer expires, it retransmits the Registration Accept message so that the terminal and the core network device maintain synchronization of the PEIPS parameters or eDRX parameters in the Registration Accept message. For example, as shown in steps 501 to 504 in Figure 5.

[0156] In a possible embodiment, the registration request message carries capability information of the terminal, where the capability information is used to indicate support for replying a registration completion message after receiving a registration accept message carrying a PEIPS parameter or an eDRX parameter.

[0157] Assume that the core network device sends a registration acceptance message carrying PEIPS parameters or eDRX parameters to a terminal of the old version of the protocol. After receiving the registration acceptance message carrying PEIPS parameters or eDRX parameters, the terminal of the old version of the protocol may not reply with a registration completion message. For example, if the registration acceptance message carries PEIPS parameters or eDRX parameters and does not carry the information element required to reply to the registration completion message as required by the protocol, the terminal will not reply with a registration completion message after receiving the registration acceptance message. If the core network device starts a timer to wait for the terminal to reply with a registration completion message after sending the registration acceptance message, the core network device may not receive the registration completion message sent by the terminal, causing the core network device to keep retransmitting the registration acceptance message.

[0158] This capability information allows core network devices to distinguish whether a terminal is using the newer protocol version or the older protocol version. By having the terminal include this capability information in a registration request message, the core network device can identify the terminal as using the newer protocol version. If the terminal is using the newer protocol version, after sending a registration accept message with PEIPS or eDRX parameters, the core network device triggers a start timer and waits for the terminal to respond with a registration completion message.

[0159] If the terminal does not include the aforementioned capability information in the Registration Request message, the core network device will know that the terminal is using an older protocol version. If the terminal is using an older protocol version, after sending a Registration Accept message with PEIPS or eDRX parameters, the core network device will still process the information element items according to the older protocol specifications to determine whether to start a timer after sending the Registration Accept message to wait for the terminal to reply with a Registration Complete message. Therefore, including the aforementioned capability information in the Registration Request message facilitates compatibility with terminals using older protocol versions.

[0160] In one possible embodiment, if the registration accept message carries a Packet Assisted Paging Early Indication (PEIPS) parameter or an enhanced discontinuous reception (eDRX) parameter, then starting a timer includes: if the registration request message carries terminal capability information and the registration accept message carries the PEIPS parameter or the eDRX parameter, then starting a timer. This possible embodiment facilitates compatibility with terminals of older protocol versions.

[0161] For example, if the registration request message carries the above capability information and the registration accept message carries the PEIPS parameter or the eDRX parameter, the core network device will trigger the start timer and wait for the terminal to reply with a registration completion message.

[0162] If the terminal does not carry the above capability information in the registration request message, the core network device may process the information element according to the old protocol to determine whether to start the timer after sending the registration acceptance message.

[0163] It can be seen that the method described in FIG. 4 is conducive to ensuring that the PEIPS parameters or eDRX parameters in the registration acceptance messages on the network side and the terminal side are aligned, thereby enabling the terminal to communicate normally.

[0164] After a terminal registration fails, it may lose its own paging message. For example, if the terminal has already enabled paging monitoring based on the UE_ID group before sending the Registration Request message, the core network device sends a Registration Accept message with the PEIPS parameter, but the terminal does not receive it. The core network device will page the terminal based on the PEIPS paging group, while the terminal is still monitoring paging messages based on the UE_ID group, resulting in the terminal being unable to monitor its own paging message.

[0165] For another example, if the terminal has already started the paging monitoring mode based on the PEIPS paging packet before sending the registration request message. After the core network device sends the registration acceptance message carrying the new PEIPS parameters, the terminal does not receive the registration acceptance message. The core network device will page the terminal based on the new PEIPS paging packet, while the terminal still monitors the paging message based on the old PEIPS paging packet, which will cause the terminal to be unable to monitor its own paging message. In order to prevent the terminal from losing its own paging message after the terminal registration fails, an embodiment of the present application provides a communication method, which is further described below:

[0166] Please refer to FIG6 , which is a flow chart of another communication method provided in an embodiment of the present application, wherein:

[0167] 601. A terminal sends a registration request message, which carries the terminal's capability information, and the capability information is used to indicate PEIPS. Correspondingly, a core network device may receive the registration request message.

[0168] 602. The terminal starts a timer.

[0169] In the embodiment of the present application, after the terminal sends the registration request message, a timer may be started. If the timer times out without receiving a registration acceptance message, it indicates that the registration has failed. If a registration acceptance message is received before the timer times out, it indicates that the registration has succeeded.

[0170] Optionally, the timer may be a T3510 timer or other timer, which is not limited in the embodiment of the present application.

[0171] 603. The core network device sends a registration acceptance message to the terminal based on the registration request message. The registration acceptance message carries a PEIPS parameter.

[0172] 604. The core network device pages the terminal based on the PEIPS parameters.

[0173] 605. If the terminal does not receive the registration acceptance message when the timer times out, the terminal monitors the paging message of the terminal during the paging occasion in the DRX cycle.

[0174] That is, if the terminal registration fails, the terminal uses the traditional paging monitoring method to monitor its own paging message, which is helpful to avoid the terminal losing the paging message. The description of the traditional paging monitoring method can be found in the terminology introduction in the previous article and will not be repeated here.

[0175] In a possible embodiment, before sending the registration request message, the terminal may monitor a paging message of the terminal in a paging group, where the paging group is a UE_ID group or a PEIPS paging group, and the terminal is located in the paging group, for example, as shown in 701 to 706 of FIG.

[0176] That is, before sending a registration request message, the terminal uses a paging monitoring method based on UE_ID packets or PEIPS paging packets. If the registration fails, it falls back to the traditional paging monitoring method. This helps prevent the terminal from missing paging messages.

[0177] Currently, the valid value range for the PEIPS paging packet identifier is 0-7. This range may be expanded in the future, for example, to 0-10. After this expansion, terminals using older versions of the protocol may not be able to successfully receive their own paging messages in some cases.

[0178] For example, assuming that the identifier of the PEIPS paging packet assigned by the core network device to the terminal is 8, that is, the core network device will page the terminal on PEIPS paging packet 8. Assuming that the terminal is a terminal of the old protocol version, after the terminal receives the identifier of the PEIPS paging packet assigned to it by the core network device, it finds that the identifier of the PEIPS paging packet is not in the valid value range of 0-7 of the identifier of the PEIPS paging packet it supports. In this case, the terminal of the old protocol version will listen to its own paging message on PEIPS paging packet 0. The core network device will page the terminal on PEIPS paging packet 8, which results in the terminal being unable to listen to its own paging message. In order to enable the terminal to successfully listen to its own paging message, an embodiment of the present application also provides a communication method, which is further explained below:

[0179] Please refer to FIG8 , which is a flow chart of another communication method provided in an embodiment of the present application, wherein:

[0180] 801. A terminal sends a registration request message, where the registration request message carries capability information of the terminal. The capability information includes first indication information, where the first indication information is used to indicate support for PEIPS. Accordingly, a core network device may receive the registration request message.

[0181] 802. The core network device sends a registration acceptance message according to the registration request message. The registration acceptance message carries a PEIPS parameter. Accordingly, the terminal may receive the registration acceptance message.

[0182] For example, the PEIPS parameter may be an identifier of a PEIPS paging packet.

[0183] 803. The core network device pages the terminal using the PEIPS paging packet corresponding to the PEIPS parameter.

[0184] That is, after the core network device sends the message carrying the PEIPS parameter to the terminal, it can page the terminal using the PEIPS paging packet corresponding to the PEIPS parameter.

[0185] For example, the PEIPS parameter is an identifier of a PEIPS paging packet, and the value of the PEIPS parameter is 8. The core network device pages the terminal on the PEIPS paging packet 8.

[0186] 804. When the value of the PEIPS parameter does not belong to the valid value range supported by the terminal, the terminal monitors the paging message of the terminal during the paging occasion in the DRX cycle.

[0187] For example, assuming that the PEIPS parameter value is 8 and the valid value range of the PEIPS parameter supported by the terminal is 0-7, the terminal monitors the terminal's paging message during the paging opportunity in the DRX cycle, that is, the terminal monitors its own paging message using a traditional paging monitoring method.

[0188] Based on the method described in FIG8 , when the value of the PEIPS parameter does not belong to the valid value range supported by the terminal, the terminal may use a traditional paging monitoring method to monitor its own paging message, which helps to prevent the terminal from losing the paging message.

[0189] Please refer to FIG9 , which is a flow chart of another communication method provided in an embodiment of the present application, wherein:

[0190] 901. A terminal sends a registration request message, where the registration request message carries capability information of the terminal. The capability information includes first indication information, where the first indication information is used to indicate support for PEIPS. Accordingly, a core network device may receive the registration request message.

[0191] 902. The core network device sends a registration acceptance message according to the registration request message. The registration acceptance message carries a PEIPS parameter. Accordingly, the terminal may receive the registration acceptance message.

[0192] For example, the PEIPS parameter may be an identifier of a PEIPS paging packet.

[0193] 903. The core network device pages the terminal with a specific PEIPS paging group and a PEIPS paging group corresponding to the PEIPS parameters.

[0194] That is, after the core network device sends a registration acceptance message carrying PEIPS parameters to the terminal, it can page the terminal using a specific PEIPS paging group and a PEIPS paging group corresponding to the PEIPS parameters. The specific PEIPS paging group can be specified by the protocol, for example, the specific PEIPS paging group is PEIPS paging group 0 or other PEIPS paging groups.

[0195] For example, the specific PEIPS paging group is PEIPS paging group 0, and the value of the PEIPS parameter is 9. The core network device pages the terminal in PEIPS paging group 0 and PEIPS paging group 9.

[0196] 904. When the value of the PEIPS parameter does not belong to the valid value range supported by the terminal, the terminal monitors the paging message of the terminal on a specific PEIPS paging group.

[0197] For example, the specific PEIPS paging group is PEIPS paging group 0, and the value of the PEIPS parameter is 9. The core network device pages the terminal on PEIPS paging group 0 and PEIPS paging group 9. When the valid value range of the PEIPS parameter supported by the terminal is 0-7, the terminal listens to the terminal's paging message on PEIPS paging group 0.

[0198] In a possible embodiment, the capability information of the terminal also includes the valid value range of the PEIPS parameter supported by the terminal. The specific implementation method of the core network device paging the terminal in a specific PEIPS paging group and a PEIPS paging group corresponding to the PEIPS parameter is: when the value of the PEIPS parameter does not fall within the valid value range supported by the terminal, the terminal is paged in a specific PEIPS paging group and a PEIPS paging group corresponding to the PEIPS parameter.

[0199] For example, the specific PEIPS paging group is PEIPS paging group 0. If the PEIPS parameter value assigned by the core network device to the terminal is 8, and the valid value range of the PEIPS parameter supported by the terminal is 0-7, the core network device pages the terminal on PEIPS paging group 0 and PEIPS paging group 8. If the PEIPS parameter value assigned by the core network device to the terminal is 6, and the valid value range of the PEIPS parameter supported by the terminal is 0-7, the core network device pages the terminal on PEIPS paging group 6.

[0200] Based on this possible embodiment, the core network device will page the terminal on a specific PEIPS paging group and on a PEIPS paging group corresponding to the PEIPS parameter only when the value of the PEIPS parameter does not fall within the valid value range supported by the terminal. It will not always page the terminal on a specific PEIPS paging group and a PEIPS paging group corresponding to the PEIPS parameter, which is beneficial to reducing the power consumption of the core network device.

[0201] Based on the method described in Figure 9, when the value of the PEIPS parameter does not fall within the valid value range supported by the terminal, the terminal can still monitor its own paging message on the specific PEIPS paging packet. Therefore, the method described in Figure 9 is helpful in preventing the terminal from losing the paging message.

[0202] Please refer to FIG10, which is a flow chart of another communication method provided in an embodiment of the present application, wherein:

[0203] 1001. The terminal sends a registration request message, which carries capability information of the terminal. The capability information includes first indication information and a valid value range of a PEIPS parameter supported by the terminal. The first indication information is used to indicate support for PEIPS. Accordingly, the core network device may receive the registration request message.

[0204] 1002. The core network device sends a registration acceptance message based on the registration request message. The registration acceptance message carries a PEIPS parameter whose value is within the valid value range supported by the terminal. Accordingly, the terminal may receive the registration acceptance message.

[0205] In this embodiment of the present application, the core network device can subsequently page the terminal using the PEIPS paging packet corresponding to the PEIPS parameter. Because the PEIPS parameter assigned by the core network device to the terminal falls within the valid value range supported by the terminal, the terminal monitors its own paging message on the PEIPS paging packet corresponding to the PEIPS parameter. Therefore, the terminal can monitor its own paging message.

[0206] Therefore, the method described based on FIG. 10 is helpful in preventing the terminal from losing the paging message.

[0207] Please refer to FIG11, which is a flow chart of another communication method provided in an embodiment of the present application, wherein:

[0208] 1101. The terminal receives downlink information based on eDRX parameters.

[0209] 1102. The terminal sends a registration request message, which carries capability information indicating support for eDRX. Correspondingly, the core network device may receive the registration request message.

[0210] 1103. The terminal starts a timer.

[0211] In the embodiment of the present application, after the terminal sends the registration request message, a timer may be started. If the timer times out without receiving a registration acceptance message, it indicates that the registration has failed. If a registration acceptance message is received before the timer times out, it indicates that the registration has succeeded.

[0212] Optionally, the timer may be a T3511 timer or other timer, which is not limited in the embodiment of the present application.

[0213] 1104. The core network device sends a registration accept message to the terminal based on the registration request message. The registration accept message carries updated eDRX parameters.

[0214] 1105. The core network device sends downlink information based on the updated eDRX parameters.

[0215] 1106. If the registration accept message is not received when the timer times out, the terminal receives downlink information based on the DRX parameters.

[0216] If the terminal has already enabled downlink information reception based on eDRX parameters before sending a Registration Request message, and the core network device sends a Registration Accept message with updated eDRX parameters, but the terminal does not receive the Registration Accept message, the core network device will send downlink information to the terminal based on the updated eDRX parameters. However, the terminal will continue to receive downlink information based on the old eDRX parameters, causing the terminal to miss downlink information.

[0217] In an embodiment of the present application, if the terminal does not receive the registration acceptance message when the timer times out, the terminal receives downlink information based on the DRX parameters. Since the eDRX cycle is a positive multiple of the DRX cycle, even if the core network device sends downlink information to the terminal based on the updated eDRX parameters, the terminal can also receive its own downlink information based on the DRX parameters.

[0218] It can be seen that the method described in FIG11 is helpful in preventing the terminal from losing downlink information.

[0219] The present application provides a communication device that can be used to implement the functions of the above-mentioned terminal or core network device. The communication device can be a terminal or a core network device. The communication device includes a module or unit that corresponds one-to-one to the method / operation / step / action performed by the terminal or core network device in the above-mentioned method embodiment. The unit can be a hardware circuit, or software, or a combination of a hardware circuit and software. Please refer to Figure 12, which shows a structural diagram of a communication device 1200 of an embodiment of the present application. The communication device 1200 may include an interface unit 1201 and a processing unit 1202. Specifically, the processing unit 1202 is used to process signaling and / or data, and the signaling and / or data may be data received by the interface unit 1201, and the processed signaling and / or data may also be sent by the interface unit 1201;

[0220] In one embodiment, when the communication device 1200 is a terminal, wherein:

[0221] Interface unit 1201, used to send a registration request message;

[0222] The interface unit 1201 is further configured to receive a registration acceptance message, the registration acceptance message carrying first indication information, and the first indication information is configured to indicate that a registration completion message should be replied to after receiving the registration acceptance message;

[0223] The interface unit 1201 is further configured to send a registration completion message according to the registration acceptance message.

[0224] In a possible embodiment, the registration request message carries capability information of the terminal, where the capability information is used to indicate support for replying a registration completion message after receiving a registration acceptance message.

[0225] In a possible embodiment, the registration accept message further carries a Packet Assisted Paging Early Indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter.

[0226] In one embodiment, when the communication device 1200 is a core network device, wherein:

[0227] The interface unit 1201 is configured to receive a registration request message from a terminal;

[0228] The interface unit 1201 is further configured to send a registration acceptance message to the terminal according to the registration request message, wherein the registration acceptance message carries first indication information, and the first indication information is used to instruct the terminal to reply with a registration completion message after receiving the registration acceptance message;

[0229] The processing unit 1202 is configured to start a timer;

[0230] The processing unit 1202 is further configured to stop the timer if a registration completion message is received from the terminal before the timer times out; or

[0231] The interface unit 1201 is further configured to retransmit the registration acceptance message if no registration completion message is received from the terminal when the timer times out.

[0232] In a possible embodiment, the registration request message carries capability information of the terminal, where the capability information is used to indicate support for replying a registration completion message after receiving a registration acceptance message.

[0233] In a possible embodiment, the processing unit 1202 starts the timer, including:

[0234] If the registration request message carries the capability information of the terminal and the registration accept message carries the first indication information, the timer is started.

[0235] In a possible embodiment, the registration accept message further carries a Packet Assisted Paging Early Indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter.

[0236] In one embodiment, when the communication device 1200 is a terminal, wherein:

[0237] Interface unit 1201, used to send a registration request message;

[0238] The interface unit 1201 is further configured to receive a registration acceptance message;

[0239] The interface unit 1201 is further configured to send a registration completion message if the registration accept message carries a Packet Assisted Paging Early Indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter.

[0240] In a possible embodiment, the processing unit 1202 is configured to determine whether the registration accept message carries a PEIPS parameter or an eDRX parameter.

[0241] In a possible embodiment, the registration request message carries capability information of the terminal, where the capability information is used to indicate support for replying a registration completion message after receiving a registration accept message carrying a PEIPS parameter or an eDRX parameter.

[0242] In one embodiment, when the communication device 1200 is a core network device, wherein:

[0243] The interface unit 1201 is configured to receive a registration request message from a terminal;

[0244] The interface unit 1201 is further configured to send a registration acceptance message to the terminal according to the registration request message;

[0245] The processing unit 1202 is configured to start a timer if the registration accept message carries a packet assisted paging early indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter;

[0246] The processing unit 1202 is further configured to stop the timer if a registration completion message is received from the terminal before the timer times out; or

[0247] The interface unit 1201 is further configured to retransmit the registration acceptance message if no registration completion message is received from the terminal when the timer times out.

[0248] In a possible embodiment, the registration request message carries capability information of the terminal, where the capability information is used to indicate support for replying a registration completion message after receiving a registration accept message carrying a PEIPS parameter or an eDRX parameter.

[0249] In a possible embodiment, if the registration accept message carries a Packet Assisted Paging Early Indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter, the processing unit 1202 starts a timer, including:

[0250] If the registration request message carries the capability information of the terminal, and the registration accept message carries a Packet Assisted Paging Early Indication (PEIPS) parameter or an enhanced discontinuous reception (eDRX) parameter, a timer is started.

[0251] In one embodiment, when the communication device 1200 is a terminal, wherein:

[0252] The interface unit 1201 is configured to send a registration request message, where the registration request message carries capability information of the terminal, where the capability information is used to indicate support for packet-assisted early indication of paging (PEIPS);

[0253] The processing unit 1202 is configured to start a timer;

[0254] The interface unit 1201 is further configured to monitor the paging message of the terminal during a paging opportunity within a discontinuous reception (DRX) cycle if no registration acceptance message is received when the timer times out.

[0255] In a possible embodiment, the interface unit 1201 is further configured to monitor a paging message of the terminal in a paging group before sending the registration request message. The paging group is a user equipment identifier UE_ID group or a PEIPS paging group, and the terminal is located in the paging group.

[0256] In one embodiment, when the communication device 1200 is a terminal, wherein:

[0257] The interface unit 1201 is configured to send a registration request message, where the registration request message carries capability information of the terminal, where the capability information includes first indication information, where the first indication information is used to indicate support for packet-assisted early indication of paging (PEIPS);

[0258] The interface unit 1201 is further configured to receive a registration acceptance message, wherein the registration acceptance message carries a PEIPS parameter;

[0259] The interface unit 1201 is further configured to monitor the terminal's paging message in a paging opportunity within a discontinuous reception (DRX) cycle, or monitor the terminal's paging message in a specific PEIPS paging group, when the PEIPS parameter value does not fall within a valid value range supported by the terminal.

[0260] In a possible embodiment, the capability information further includes a valid value range of a PEIPS parameter supported by the terminal.

[0261] In one embodiment, when the communication device 1200 is a core network device, wherein:

[0262] The interface unit 1201 is configured to receive a registration request message from a terminal, where the registration request message carries capability information of the terminal, where the capability information includes first indication information, where the first indication information is used to indicate support for packet-assisted early indication of paging (PEIPS);

[0263] The interface unit 1201 is further configured to send a registration acceptance message according to the registration request message, wherein the registration acceptance message carries a PEIPS parameter;

[0264] The interface unit 1201 is further configured to page the terminal using a specific PEIPS paging group and a PEIPS paging group corresponding to a PEIPS parameter.

[0265] In a possible embodiment, the capability information also includes a valid value range of the PEIPS parameter supported by the terminal, and the interface unit 1201 pages the terminal in a specific PEIPS paging group and a PEIPS paging group corresponding to the PEIPS parameter, including: when the value of the PEIPS parameter does not fall within the valid value range supported by the terminal, paging the terminal in a specific PEIPS paging group and a PEIPS paging group corresponding to the PEIPS parameter.

[0266] In one embodiment, when the communication device 1200 is a terminal, wherein:

[0267] Interface unit 1201 is configured to send a registration request message, where the registration request message carries capability information of the terminal, where the capability information includes first indication information and a valid value range of a Packet-Assisted Early Indication for Paging (PEIPS) parameter supported by the terminal, where the first indication information is used to indicate support for PEIPS;

[0268] The interface unit 1201 is further configured to receive a registration acceptance message, where the registration acceptance message carries a PEIPS parameter, and the value of the PEIPS parameter is within a valid value range.

[0269] In one embodiment, when the communication device 1200 is a core network device, wherein:

[0270] An interface unit 1201 is configured to receive a registration request message, the registration request message carrying capability information of a terminal, the capability information including first indication information and a valid value range of a Packet-Assisted Early Indication for Paging (PEIPS) parameter supported by the terminal, the first indication information being used to indicate support for PEIPS;

[0271] The interface unit 1201 is further configured to send a registration acceptance message according to the registration request message. The registration acceptance message carries a PEIPS parameter, and the value of the PEIPS parameter is within a valid value range.

[0272] In one embodiment, when the communication device 1200 is a terminal, wherein:

[0273] The interface unit 1201 is configured to send a registration request message, where the registration request message carries capability information, where the capability information indicates support for enhanced discontinuous reception (eDRX);

[0274] Interface unit 1201, used to start the timer;

[0275] The interface unit 1201 is further configured to, if the registration acceptance message is not received when the timer times out, receive downlink information based on the eDRX parameters and fall back to receiving downlink information based on the discontinuous reception (DRX) parameters.

[0276] FIG13 shows a communication device 1300 provided in an embodiment of the present application, configured to implement the aforementioned terminal or core network device functions. The device may be a communication device or a device used in a communication device. The communication device may be a terminal or core network device. The device used in the communication device may be a chip system or chip within the communication device. The chip system may consist of a chip alone or may include a chip and other discrete components.

[0277] The communication device 1300 includes at least one processor 1310 for implementing the processing functions of the device (such as a core network device or a terminal) in the method provided in the embodiment of the present application. The communication device 1300 may also include a communication interface 1320 for implementing the transceiver operation of the device (such as a core network device or a terminal) in the method provided in the embodiment of the present application. In the embodiment of the present application, the communication interface may be a transceiver, a circuit, a bus, a module or other type of communication interface for communicating with other devices through a transmission medium. For example, the communication interface 1320 is used for the device in the communication device 1300 to communicate with other devices. The processor 1310 uses the communication interface 1320 to send and receive data, and is used to implement the method described in the above method embodiment.

[0278] The communication device 1300 may also include at least one memory 1330 for storing program instructions and / or data. The memory 1330 is coupled to the processor 1310. Coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processor 1310 may operate in conjunction with the memory 1330. The processor 1310 may execute program instructions stored in the memory 1330. At least one of the at least one memory may be included in the processor.

[0279] The specific connection medium between the communication interface 1320, processor 1310, and memory 1330 is not limited in the embodiments of the present application. In Figure 13, the embodiment of the present application shows that the memory 1330, processor 1310, and communication interface 1320 are connected via a bus. The bus is represented by a bold line in Figure 13. The connection method between other components is only for schematic illustration and is not limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in Figure 13, but this does not mean that there is only one bus or one type of bus.

[0280] When the communication device 1300 is specifically a device for a device (such as a core network device or a terminal), for example, when the communication device 1300 is specifically a chip or a chip system, the communication interface 1320 may output or receive a baseband signal. When the communication device 1300 is specifically a device (such as a core network device or a terminal), the communication interface 1320 may output or receive a radio frequency signal. In an embodiment of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0281] It should be noted that the above-mentioned communication interface 1320 can be used to execute the functions of the above-mentioned interface unit 1201, and the above-mentioned processor 1310 can be used to execute the functions of the above-mentioned processing unit 1202, which will not be repeated here.

[0282] When the above-mentioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above-mentioned method embodiment, and the terminal chip receives information from other network elements; or, the terminal chip sends information to other network elements.

[0283] When the communication device is a chip used in a core network device, the core network device chip implements the functions of the core network device in the above method embodiment. The core network device chip receives information from other network elements; or the core network device chip sends information to other network elements.

[0284] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0285] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, mobile hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a core network device or a terminal. Of course, the processor and storage medium can also exist as discrete components in a terminal or access network device.

[0286] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program or instruction may be stored in a computer-readable storage medium or transmitted via the computer-readable storage medium. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a tape; it may also be an optical medium, such as a DVD; it may also be a semiconductor medium, such as a solid state disk (SSD).

[0287] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0288] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

[0289] An embodiment of the present application further provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are executed, the method executed by the terminal or access network device in the above method embodiment is implemented.

[0290] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed, the method executed by the terminal or access network device in the above method embodiment is implemented.

[0291] The present application also provides a communication system including a terminal or an access network device, wherein the terminal is configured to execute the method executed by the terminal in the above method embodiment, and the access network device is configured to execute the method executed by the access network device in the above method embodiment.

[0292] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0293] The descriptions of the various embodiments provided in this application can refer to each other. The descriptions of each embodiment have their own focus. For parts not described in detail in a particular embodiment, please refer to the relevant descriptions of other embodiments. For the convenience and brevity of description, for example, the functions and execution steps of the various devices and equipment provided in the embodiments of this application can refer to the relevant descriptions of the method embodiments of this application. The various method embodiments and the various device embodiments can also refer to, be combined with, or quote each other.

[0294] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A communication method, characterized in that: Applied to a terminal, the method comprises: Send a registration request message; receiving a registration acceptance message, wherein the registration acceptance message carries first indication information, and the first indication information is used to indicate that a registration completion message is replied after receiving the registration acceptance message; According to the registration acceptance message, a registration completion message is sent.

2. The method according to claim 1, characterized in that The registration request message carries the capability information of the terminal, and the capability information is used to indicate support for replying a registration completion message after receiving a registration acceptance message.

3. The method according to claim 1 or 2, characterized in that: The registration acceptance message also carries a packet assisted paging early indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter.

4. A communication method, characterized in that: Applied to a core network device, the method comprises: Receiving a registration request message from a terminal; Sending a registration acceptance message to the terminal according to the registration request message, wherein the registration acceptance message carries first indication information, and the first indication information is used to indicate that a registration completion message is replied after receiving the registration acceptance message; Start the timer; If a registration completion message is received from the terminal before the timer times out, stopping the timer; or, If the registration completion message from the terminal is not received when the timer times out, the registration acceptance message is retransmitted.

5. The method according to claim 4, characterized in that The registration request message carries the capability information of the terminal, and the capability information is used to indicate support for replying a registration completion message after receiving a registration acceptance message.

6. The method according to claim 5, characterized in that The starting timer comprises: If the registration request message carries the capability information of the terminal, and the registration accept message carries the first indication information, the timer is started.

7. The method according to any one of claims 4 to 6, characterized in that: The registration acceptance message also carries a packet assisted paging early indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter.

8. A communication method, characterized in that: Applied to a terminal, the method comprises: Send a registration request message; Receive registration acceptance message; If the registration accept message carries a packet assisted paging early indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter, a registration completion message is sent.

9. The method according to claim 8, characterized in that The method further comprises: It is determined that the registration accept message carries a PEIPS parameter or an eDRX parameter.

10. The method according to claim 8 or 9, characterized in that: The registration request message carries the capability information of the terminal, where the capability information is used to indicate support for replying a registration completion message after receiving a registration accept message carrying a PEIPS parameter or an eDRX parameter.

11. A communication method, characterized in that: Applied to a core network device, the method comprises: Receiving a registration request message from a terminal; Sending a registration acceptance message to the terminal according to the registration request message; If the registration accept message carries a paging packet assisted paging early indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter, starting a timer; If a registration completion message is received from the terminal before the timer times out, stopping the timer; or, If the registration completion message from the terminal is not received when the timer times out, the registration acceptance message is retransmitted.

12. The method according to claim 11, characterized in that The registration request message carries the capability information of the terminal, where the capability information is used to indicate support for replying a registration completion message after receiving a registration accept message carrying a PEIPS parameter or an eDRX parameter.

13. The method according to claim 12, characterized in that If the registration acceptance message carries a paging packet assisted paging early indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter, starting a timer includes: If the registration request message carries the capability information of the terminal, and the registration accept message carries the PEIPS parameter or the eDRX parameter, a timer is started.

14. A communication method, characterized in that: Applied to a terminal, the method comprises: Sending a registration request message, where the registration request message carries capability information of the terminal, where the capability information is used to indicate support for paging packet assisted paging early indication PEIPS; Start the timer; If the registration acceptance message is not received when the timer times out, the paging message of the terminal is monitored during a paging opportunity in a discontinuous reception (DRX) cycle.

15. The method according to claim 14, characterized in that Before sending the registration request message, the method further includes: The paging message of the terminal is monitored in a paging group, where the paging group is a user equipment identification UE_ID group or a PEIPS paging group, and the terminal is located in the paging group.

16. A communication device, characterized in that: Comprising a unit for executing the method as claimed in any one of claims 1 to 3, or comprising a unit for executing the method as claimed in any one of claims 4 to 7, or comprising a unit for executing the method as claimed in any one of claims 8 to 10, or comprising a unit for executing the method as claimed in any one of claims 11 to 13, or comprising a unit for executing the method as claimed in any one of claims 14 to 15.

17. A communication device, characterized in that: The method comprises a processor and a memory, wherein the processor and the memory are coupled, wherein the processor is used to implement the method according to any one of claims 1 to 3, or the processor is used to implement the method according to any one of claims 4 to 7, or the processor is used to implement the method according to any one of claims 8 to 10, or the processor is used to implement the method according to any one of claims 11 to 13, or the processor is used to implement the method according to any one of claims 14 to 15.

18. A chip, characterized in that: The invention comprises a processor and an interface, wherein the processor and the interface are coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions so that the method described in any one of claims 1 to 3 is executed, or the method described in any one of claims 4 to 7 is executed, or the method described in any one of claims 8 to 10 is executed, or the method described in any one of claims 11 to 13 is executed, or the method described in any one of claims 14 to 15 is executed.

19. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which, when called by the computer, enable the computer to execute the method described in any one of claims 1 to 3, or the method described in any one of claims 4 to 7, or the method described in any one of claims 8 to 10, or the method described in any one of claims 11 to 13, or the method described in any one of claims 14 to 15.

20. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is executed, the method according to any one of claims 1 to 3 is executed, or the method according to any one of claims 4 to 7 is executed, or the method according to any one of claims 8 to 10 is executed, or the method according to any one of claims 11 to 13 is executed, or the method according to any one of claims 14 to 15 is executed.

Citation Information

Patent Citations

  • Communication method and communication device

    CN118945802A

  • Paging method and communication device

    CN114946234A

  • Method, apparatus and computer program product for accelerating emergency service initiation

    CN115669013A

  • Apparatus and method for network function profile management

    US20190230556A1

  • Edrx enhancement for reduced capability device

    WO2022031972A1