Communication method and communication device

By carrying the first indication information in the registration acceptance message and starting the timer retransmission mechanism in the core network device, the cell misalignment problem caused by the terminal not successfully receiving the registration acceptance message is solved, ensuring the terminal's normal communication and improving system compatibility.

CN118945802APending Publication Date: 2024-11-12HUAWEI TECH CO LTD
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202310537534.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-12
Publication Date
2024-11-12

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 will be retransmitted to ensure the cell alignment.

Benefits of technology

It effectively solves the problem of cell misalignment, ensures that the terminal can communicate normally, and improves the system compatibility, especially for the old version of the protocol terminal.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945802A_ABST
    Figure CN118945802A_ABST
Patent Text Reader

Abstract

The invention provides a communication method and a communication device. The method comprises the following steps: sending a registration request message; a registration acceptance message is received, the registration acceptance message carries first indication information, and the first indication information is used for indicating to reply a registration completion message after the registration acceptance message is received; and sending a registration completion message according to the registration acceptance message. Based on the method, the cell alignment in the registration acceptance messages of the network side and the terminal side can be ensured, so that the terminal can normally communicate, the terminal replies the registration completion message by carrying the first indication information, and the compatibility of the system can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] At present, the registration process of a terminal is usually as follows: the terminal sends a registration request message to the network side. The network side sends a registration acceptance message to the terminal, and the registration acceptance message includes a data element. For example, the data element may be a PEIPS parameter or an eDRX parameter. If the terminal fails to successfully receive the registration acceptance message including the data element, the network side cannot perceive whether the terminal has successfully received the data element, and the network side will not retransmit the registration acceptance message to the terminal. This will cause the data elements on the network side and the terminal side to be misaligned, affecting the subsequent normal communication of the terminal. Summary of the invention

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

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

[0005] Send a registration request message; receive a registration acceptance message, the registration acceptance message carries first indication information, the first indication information is used to indicate to reply to a registration completion message after receiving the registration acceptance message; according to the registration acceptance message, send a registration completion message.

[0006] 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.

[0007] 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.

[0008] This possible embodiment is beneficial for terminals compatible with old version protocols.

[0009] 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.

[0010] 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 the paging message or save the power consumption of the terminal. Alternatively, based on this possible embodiment, the eDRX parameters on the network side and the terminal side can be aligned to avoid the terminal from losing downlink information.

[0011] 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, a chip, or a chip system, etc.) applied to the core network device, or by a logical node, a logical module, or software that can implement all or part of the core network device functions. The communication method includes:

[0012] Receive a registration request message from a terminal; 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 indicate to reply to 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 times out, stop the timer; or, if no registration completion message is received from the terminal when the timer times out, retransmit the registration acceptance message.

[0013] In a possible embodiment, the registration request message carries 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.

[0014] In a possible embodiment, starting a 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 a timer.

[0015] 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.

[0016] The beneficial effects of the second aspect can refer to the beneficial effects of the first aspect, which will not be repeated here.

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

[0018] Send a registration request message; receive a registration acceptance message; if the registration acceptance message carries a packet assisted paging early indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter, send a registration completion message.

[0019] 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.

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

[0021] 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 carrying a PEIPS parameter or an eDRX parameter.

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

[0023] 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, a chip, or a chip system, etc.) applied to the core network device, or by a logical node, a logical module, or software that can implement all or part of the core network device functions. The communication method includes:

[0024] Receive a registration request message from a terminal; send a registration acceptance message to the terminal according to the registration request message; if the registration acceptance message carries a paging packet assisted paging early indication PEIPS parameter or an 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 no registration completion message is received from the terminal when the timer expires, retransmit the registration acceptance message.

[0025] 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 carrying a PEIPS parameter or an eDRX parameter.

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

[0027] The beneficial effects of the fourth aspect can refer to the beneficial effects of the third aspect, which will not be repeated here.

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

[0029] Send a registration request message, which carries the capability information of the terminal, and the capability information is used to indicate support for packet-assisted early indication of paging PEIPS; start a timer; if the timer times out and no registration acceptance message is received, monitor the paging message of the terminal during the paging opportunity in the discontinuous reception DRX cycle.

[0030] The method described in the fifth aspect is helpful to avoid the terminal from losing the paging message.

[0031] In a possible embodiment, before sending the registration request message, a paging message of the terminal may also be monitored in a paging group, where 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.

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

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

[0034] Send a registration request message, the registration request message carries the capability information of the terminal, the capability information includes first indication information, the first indication information is used to indicate support for paging group assisted paging early indication PEIPS; receive a registration acceptance message, the registration acceptance 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.

[0035] 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.

[0036] 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.

[0037] 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, a chip, or a chip system, etc.) applied to the core network device, or by a logical node, a logical module, or software that can implement all or part of the core network device functions. The communication method includes:

[0038] Receive a registration request message from a terminal, the registration request message carries capability information of the terminal, the capability information includes first indication information, the first indication information is used to indicate support for paging group assisted paging early indication PEIPS; send a registration acceptance message according to the registration request message, the registration acceptance message carries PEIPS parameters; page the terminal in a specific PEIPS paging group and a PEIPS paging group corresponding to the PEIPS parameters.

[0039] In a possible embodiment, the capability information also includes a valid value range of a 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.

[0040] The beneficial effects of the seventh aspect can refer to the beneficial effects of the sixth aspect and will not be repeated here.

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

[0042] 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 a 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 a PEIPS parameter, and the value of the PEIPS parameter is within the valid value range.

[0043] The method described in the eighth aspect is helpful to avoid the terminal from losing the paging message.

[0044] 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, a chip, or a chip system, etc.) applied to the core network device, or by a logical node, a logical module, or software that can implement all or part of the core network device functions. The communication method includes:

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

[0046] The method described in the ninth aspect is helpful to avoid the terminal from losing the paging message.

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

[0048] The invention relates to receiving downlink information based on enhanced discontinuous reception (eDRX) parameters; sending a registration request message, the registration request message carries capability information, the capability information indicates support for eDRX; starting a timer; if the timer times out and no registration acceptance message is received, receiving downlink information based on discontinuous reception (DRX) parameters.

[0049] The method described in the tenth aspect is helpful to avoid the terminal from losing downlink information.

[0050] 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 in the first aspect, the third aspect, the fifth aspect, the sixth aspect, the eighth aspect, or the tenth aspect and possible implementations thereof.

[0051] 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, 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 core network device functions. The communication device includes a module / unit for executing any method in the second aspect, the fourth aspect, the seventh aspect, or the ninth aspect and possible implementations thereof.

[0052] 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 any one of the methods described in the first to tenth aspects above.

[0053] 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 first to tenth aspects above.

[0054] In a fifteenth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are called, any one of the above-mentioned first to tenth aspects is executed.

[0055] 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.

[0056] 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

[0057] Figure 1 A possible, non-limiting system schematic diagram provided for this application;

[0058] Figure 2 A flow chart of a communication method provided by the present application;

[0059] Figure 3 A flow chart of a communication method provided by the present application;

[0060] Figure 4 A flow chart of a communication method provided by the present application;

[0061] Figure 5 A flow chart of a communication method provided by the present application;

[0062] Figure 6 A flow chart of a communication method provided by the present application;

[0063] Figure 7 A flow chart of a communication method provided by the present application;

[0064] Figure 8 A flow chart of a communication method provided by the present application;

[0065] Fig. 9 A flow chart of a communication method provided by the present application;

[0066] Fig.10 A flow chart of a communication method provided by the present application;

[0067] Fig.11 A flow chart of a communication method provided by the present application;

[0068] Fig.12 A schematic diagram of the structure of a communication device provided by the present application;

[0069] Fig.13 A schematic diagram of the structure of another communication device provided in this application. DETAILED DESCRIPTION

[0070] The specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.

[0071] The terms "first" and "second" and the like in the specification, claims and drawings of this application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products or devices.

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

[0073] In the present application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. 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.

[0074] In this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as a logic module inside a device sending information to another logic 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 it can be understood as logic module 1 in an access network device sending information to logic module 2 in an access network device.

[0075] In this application, "receiving information" can be understood as a device receiving information from another device, or it can also be understood as a logic module inside a device receiving information from another logic module. For example, "the access network device receives information" can be understood as the access network device receiving information from another device (such as a terminal), or it can be understood as logic module 1 in the access network device receiving information from logic module 2 in the access network device.

[0076] In this application, "sending information to... (for example, a terminal)" or the related illustrations in the accompanying drawings can be understood as the destination end of the information is the terminal. It can include sending information to the terminal directly or indirectly. "Receiving information from... (for example, a terminal)" or "receiving information from... (for example, a terminal)" or "receiving information sent by (for example, a terminal)", or the related illustrations in the accompanying drawings can be understood as the source end of the information is the terminal, which can include directly or indirectly receiving information from the terminal. 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.

[0077] In order to better understand the embodiments of the present application, the system architecture involved in the embodiments of the present application is first introduced below:

[0078] The embodiments of the present application can be applied to long term evolution (LTE) systems, fifth generation mobile communication (5G) systems, sixth generation mobile communication (6G) systems and other communication systems evolved after 5G, satellite communication 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.

[0079] Figure 1 A possible, non-limiting system schematic is shown. Figure 1 As shown, the communication system 10 includes a radio access network (RAN) 100 , a core network (CN) 200 and the Internet 300 .

[0080] RAN 100

[0081] RAN 100 includes at least one RAN node (e.g. Figure 1 110a and 110b, collectively referred to as 110) and at least one terminal (such as Figure 1 RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment ( Figure 1 The terminal 120 is connected to the RAN node 110 in a wireless manner. The RAN node 110 is connected to the core network 200 in a wireless or wired manner. The core network device in the core network 200 and the RAN node 110 in the RAN 100 may be different physical devices, or may be the same physical device that integrates the core network logical function and the radio access network logical function.

[0082] RAN 100 may be a cellular system related to the third generation partnership project (3GPP), for example, a 4G, 5G mobile communication system, or a future evolution system (for example, a 6G mobile communication system). RAN 100 may also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (cloud radio access network, CRAN), or a wireless fidelity (wireless fidelity, WiFi) system. RAN 100 may also be a communication system that integrates two or more of the above systems.

[0083] 1. RAN node 110

[0084] The RAN node 110, which may also be sometimes referred to as an access network device, a RAN entity or an access node, constitutes a part of the communication system to help the terminal achieve wireless access. The multiple RAN nodes 110 in the communication system 10 may be nodes of the same type or nodes of different types. In some scenarios, the roles of the RAN node 110 and the terminal 120 are relative, for example, Figure 1 The network element 120i may be a helicopter or a drone, which may be configured as a mobile base station. For the terminals 120j that access the RAN 100 through the network element 120i, the network element 120i is a base station; but for the base station 110a, the network element 120i is a terminal. The RAN node 110 and the terminal 120 are sometimes referred to as communication devices, for example Figure 1 The network elements 110a and 110b may be understood as communication devices having base station functions, and the network elements 120a-120j may be understood as communication devices having terminal functions.

[0085] In a 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 (e.g., Figure 1 110a in), micro base stations or indoor stations (such as Figure 1110b in the present application), a relay node or a donor node, or a wireless controller in a CRAN scenario. In a possible embodiment, the RAN node 110 may also be a server, a wearable device, a vehicle or an on-board device, etc. For example, the access network device in the vehicle to everything (V2X) technology may be a road side unit (RSU). All or part of the functions of the RAN node 110 in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The RAN node 110 in the present 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.

[0086] 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 can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH).

[0087] 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, CU, CU-CP, CU-UP, DU and RU are described as examples in this application. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0088] In the embodiment of the present application, the form of the RAN node 110 is not limited. The device for implementing the function of the RAN node 110 may be the RAN node 110; or it may be a device capable of supporting the RAN node 110 to implement the function, such as a chip system. The device may be installed in the RAN node 110 or used in conjunction with the RAN node 110.

[0089] For the convenience of description, the RAN node 110 is referred to as an access network device in the following description.

[0090] 2. Terminal

[0091] Terminals can also be called terminal devices, user equipment (UE), mobile stations, mobile terminals, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. Terminals can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.

[0092] In the embodiments of the present application, the form of the terminal is not limited, and the device for implementing the function of the terminal can be a terminal; or it can 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.

[0093] 2. Core Network 200

[0094] The core network 200 can complete the three functions of registration, connection, and session management. The core network 200 includes core network equipment. For example, the core network equipment may include AMF. The AMF network element is mainly responsible for mobility management in the mobile network, such as user location update, user registration network, user switching, etc.

[0095] 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.

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

[0097] 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.

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

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

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

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

[0102] In the paging monitoring method based on UE_ID grouping, the access network device will assign the terminal to a group in a specific way, and then configure it to the terminal through a system message. This group can be called a UE_ID group or a UE_ID paging group. The terminal will then monitor its own paging message in the UE_ID group. For the paging monitoring method based on UE_ID grouping, please refer to the description in Section 7 of 3GPP 38.304, which will not be repeated here.

[0103] 4. Traditional paging monitoring method

[0104] In the traditional paging monitoring method, the terminal will monitor its own paging message during the paging occasion (PO) in 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.

[0105] 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.

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

[0107] 5. Enhanced discontinuous reception (eDRX)

[0108] 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 the power consumption of terminals.

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

[0110] See also Figure 2 , Figure 2 A flow chart of a communication method provided in an embodiment of the present application, wherein:

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

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

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

[0114] Optionally, the first indication information is used to indicate that a registration completion message is replied after receiving a registration acceptance message, which can also be understood as the first indication information is used to indicate that the terminal "requires information element confirmation". For example, the first indication information can be "acknowledgement required".

[0115] That is, 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 to notify the core network device that the terminal has successfully received the registration acceptance message.

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

[0117] 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.

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

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

[0120] 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.

[0121] 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.

[0122] If the core network device receives a 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.

[0123] If the terminal does not receive the registration completion message, the terminal will not send the registration completion message. If the core network device does not receive the registration completion message from the terminal when the timer expires, the registration acceptance message is retransmitted so that the terminal and the core network device can keep the information elements in the registration acceptance message synchronized. For example, Figure 3 Steps 301 to 304 are shown.

[0124] 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 a registration acceptance message.

[0125] 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 confirmation". For example, the capability information is "acknowledgement supported".

[0126] Assume that the core network device sends a registration acceptance message carrying the first indication information to a terminal of the old version of the protocol. The terminal of 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 the information element required to reply to the registration completion message as required by the protocol, then after receiving the registration acceptance message, the terminal of the old version of the protocol will not reply to the registration completion message. After the core network device sends the registration acceptance message, it starts the timer to wait for the terminal of the old version of the protocol to reply to the registration completion message. The core network device may not receive the registration completion message sent by the terminal of the old version of the protocol, causing the core network device to keep retransmitting the registration acceptance message.

[0127] 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 enabling the terminal to 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.

[0128] If the terminal does not carry the above capability information in the registration request message, the core network device will know that the terminal is a terminal of the old version protocol when it sees that the registration request message does not carry the above capability information. If the terminal is a terminal of the old version protocol, the core network device does not carry the first indication information in the registration acceptance message, but still determines whether to start the timer after sending the registration acceptance message according to the processing of the information element item specified in the old protocol to wait for the terminal to reply the registration completion message. Therefore, by carrying the above capability information in the registration request message, it is beneficial for the system to be compatible with terminals of the old version protocol.

[0129] In a possible embodiment, if the registration request message carries the capability information of the terminal and the registration acceptance message carries the first indication information, the core network device starts the timer. This possible embodiment is beneficial for terminals compatible with old version protocols.

[0130] For example, the core network device determines that the registration request message carries the above-mentioned capability information, 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 align (such as PEIPS parameters or eDRX parameters), and then carries the first indication information in the registration acceptance message. If the registration acceptance message sent by the core network device carries the first indication information, the core network device will trigger the start timer after sending the registration acceptance message, waiting for the terminal to reply with a registration completion message.

[0131] If the terminal carries the above capability information in the registration request message, but the information element to be carried in the registration acceptance message is not an information element that requires the core network device and the terminal to be aligned, the first indication information may not be carried in the registration acceptance message. After the core network device sends the registration acceptance message, the timer is not started.

[0132] If the terminal does not carry the above 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 processes the information element items in accordance with the old protocol to determine whether to start the timer after sending the registration acceptance message to wait for the terminal to reply with a registration completion message.

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

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

[0135] For another example, the eDRX parameter may be an eDRX cycle. Alternatively, the eDRX parameter may also be other parameters related to eDRX.

[0136] 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 the paging message or save the power consumption of the terminal. Alternatively, based on this possible embodiment, the eDRX parameters on the network side and the terminal side can be aligned to avoid the terminal from losing downlink information.

[0137] In a possible embodiment, information exchange can be performed between the terminal and the core network device through the access network device. For example, the terminal can send a registration request message to the core network device through the access network device. Correspondingly, the core network device can receive the registration request message through the access network device. For another example, the core network device can send a registration acceptance message to the terminal through the access network device. Correspondingly, the terminal can receive the registration acceptance message through the access network device. For another example, the terminal can send a registration completion message to the core network device through the access network device. Correspondingly, the core network device can receive the registration completion message through the access network device. The same applies to the embodiments below, which will not be repeated below.

[0138] It can be seen that based on Figure 2 The described method is 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, and by carrying the first indication information, the terminal replies to the registration completion message, which is also conducive to improving the compatibility of the system.

[0139] See also Figure 4 , Figure 4 A flow chart of another communication method provided in an embodiment of the present application, wherein:

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

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

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

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

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

[0145] 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.

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

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

[0148] 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.

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

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

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

[0152] If the core network device receives a 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.

[0153] If the terminal does not receive the registration completion message, the terminal will not send the registration completion message. If the core network device does not receive the registration completion message from the terminal when the timer expires, the registration acceptance message is retransmitted so that the terminal and the core network device can keep the PEIPS parameter or eDRX parameter in the registration acceptance message synchronized. For example, Figure 5 Steps 501 to 504 are shown.

[0154] 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 carrying a PEIPS parameter or an eDRX parameter.

[0155] 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 the 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.

[0156] The above 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 allowing the terminal to carry the above 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, after sending a registration acceptance message carrying PEIPS parameters or eDRX parameters, the core network device will trigger the start timer and wait for the terminal to reply with a registration completion message.

[0157] If the terminal does not carry the above capability information in the registration request message, the core network device will know that the terminal is a terminal of the old version of the protocol. If the terminal is a terminal of the old version of the protocol, after sending the registration acceptance message carrying the PEIPS parameter or the eDRX parameter, the core network device still processes the information element items according to the old protocol to determine whether to start the timer after sending the registration acceptance message to wait for the terminal to reply the registration completion message. Therefore, by carrying the above capability information in the registration request message, it is conducive to compatibility with terminals of the old version of the protocol.

[0158] 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, a timer is started, including: 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. This possible embodiment is beneficial to terminals compatible with old versions of the protocol.

[0159] For example, if the registration request message carries the above capability information, and the registration acceptance 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.

[0160] If the terminal does not carry the above capability information in the registration request message, the core network device can determine whether to start the timer after sending the registration acceptance message by processing the information element item according to the old protocol regulations.

[0161] It can be seen that based on Figure 4 The described method 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.

[0162] After the terminal registration fails, the terminal may lose its own paging message. For example, if the terminal has started the paging monitoring mode based on the UE_ID group before sending the registration request message. After the core network device sends the registration acceptance message carrying the PEIPS parameter, the terminal does not receive the registration acceptance message. The core network device will page the terminal based on the PEIPS paging group, while the terminal still monitors the paging message based on the UE_ID group, which will cause the terminal to be unable to monitor its own paging message.

[0163] For another example, if the terminal has started the paging monitoring method based on the PEIPS paging packet before sending the registration request message. After the core network device sends a registration acceptance message carrying 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, and the communication method is further described below:

[0164] See also Figure 6 , Figure 6 A flow chart of another communication method provided in an embodiment of the present application, wherein:

[0165] 601. A terminal sends a registration request message, where the registration request message carries the capability information of the terminal, where the capability information is used to indicate PEIPS. Accordingly, a core network device may receive the registration request message.

[0166] 602. The terminal starts a timer.

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

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

[0169] 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.

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

[0171] 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 at the paging occasion in the DRX cycle.

[0172] 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 text, which will not be repeated here.

[0173] In a possible embodiment, before sending the registration request message, the terminal may monitor the paging message of the terminal in the 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. Figure 7 As shown in 701~706.

[0174] That is, before sending the registration request message, the terminal adopts the paging monitoring mode based on UE_ID group or PEIPS paging group, and if the registration fails, it falls back to the traditional paging monitoring mode, which helps to avoid the terminal losing the paging message.

[0175] Currently, the valid value range of the identifier of the PEIPS paging group is 0 to 7. In the future, the valid value range of the identifier of the PEIPS paging group may be expanded, for example, to 0 to 10. After the valid value range of the identifier of the PEIPS paging group is expanded, a terminal of the old version of the protocol may not be able to successfully receive its own paging message in some cases.

[0176] For example, suppose 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 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, the embodiment of the present application also provides a communication method, which is further described below:

[0177] See also Figure 8 , Figure 8 A flow chart of another communication method provided in an embodiment of the present application, wherein:

[0178] 801. A terminal sends 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 PEIPS; accordingly, a core network device may receive the registration request message.

[0179] 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.

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

[0181] 803. The core network device pages the terminal with the PEIPS paging group corresponding to the PEIPS parameter.

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

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

[0184] 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 at the paging occasion in the DRX cycle.

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

[0186] based on Figure 8 In the described method, when the value of the PEIPS parameter does not belong to the valid value range supported by the terminal, the terminal can use the traditional paging monitoring method to monitor its own paging message, which is helpful to avoid the terminal losing the paging message.

[0187] See also Fig. 9 , Fig. 9 A flow chart of another communication method provided in an embodiment of the present application, wherein:

[0188] 901. A terminal sends 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 PEIPS; accordingly, a core network device may receive the registration request message.

[0189] 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.

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

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

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

[0193] 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.

[0194] 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.

[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 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 paging message of the terminal on PEIPS paging group 0.

[0196] In a possible embodiment, the capability information of the terminal also includes the valid value range of the PEIPS parameters 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.

[0197] For example, the specific PEIPS paging group is PEIPS paging group 0. If the value of the PEIPS parameter 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 value of the PEIPS parameter 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.

[0198] Based on this possible embodiment, the core network device will page the terminal in a specific PEIPS paging group and in 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. The core network device will not always page the terminal in a specific PEIPS paging group and in a PEIPS paging group corresponding to the PEIPS parameter, which is beneficial to reducing the power consumption of the core network device.

[0199] based on Fig. 9 According to the method described, when the value of the PEIPS parameter does not belong to the valid value range supported by the terminal, the terminal can also monitor its own paging message on a specific PEIPS paging group. Fig. 9 The described method is helpful to avoid the terminal from losing the paging message.

[0200] See also Fig.10 , Fig.10 A flow chart of another communication method provided in an embodiment of the present application, wherein:

[0201] 1001. A terminal sends 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 PEIPS parameter supported by the terminal, where the first indication information is used to indicate support for PEIPS; accordingly, a core network device may receive the registration request message.

[0202] 1002. The core network device sends a registration acceptance message according to the registration request message, wherein the registration acceptance message carries a PEIPS parameter, and the value of the PEIPS parameter belongs to a valid value range supported by the terminal. Accordingly, the terminal may receive the registration acceptance message.

[0203] In the embodiment of the present application, the core network device may subsequently page the terminal on the PEIPS paging group corresponding to the PEIPS parameter. Since the PEIPS parameter assigned by the core network device to the terminal is within the valid value range supported by the terminal, the terminal will monitor its own paging message on the PEIPS paging group corresponding to the PEIPS parameter. Therefore, the terminal can monitor its own paging message.

[0204] Therefore, based on Fig.10 The described method is helpful to avoid the terminal from losing the paging message.

[0205] See also Fig.11 , Fig.11 A flow chart of another communication method provided in an embodiment of the present application, wherein:

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

[0207] 1102. The terminal sends a registration request message, where the registration request message carries capability information, where the capability information indicates support for eDRX. Accordingly, the core network device may receive the registration request message.

[0208] 1103. The terminal starts a timer.

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

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

[0211] 1104. The core network device sends a registration acceptance message to the terminal based on the registration request message, where the registration acceptance message carries updated eDRX parameters.

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

[0213] 1106. If the timer times out and no registration acceptance message is received, the terminal receives downlink information based on the DRX parameters.

[0214] If the terminal has started receiving downlink information based on eDRX parameters before sending the registration request message, the terminal does not receive the registration acceptance message after the core network device sends the registration acceptance message carrying the updated eDRX parameters. The core network device will send downlink information to the terminal based on the updated eDRX parameters, but the terminal still receives downlink information based on the old eDRX parameters, which will cause the terminal to miss downlink information.

[0215] 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.

[0216] It can be seen that based on Fig.11 The described method is helpful to avoid the terminal from losing downlink information.

[0217] 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 corresponding 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. Fig.12 , Fig.12 The structure diagram of a communication device 1200 according to an embodiment of the present application is shown. 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, 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;

[0218] In one implementation, when the communication device 1200 is a terminal, wherein:

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

[0220] The interface unit 1201 is further used to receive a registration acceptance message, where 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;

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

[0222] 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.

[0223] 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.

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

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

[0226] 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 indicate that a registration completion message is replied after receiving the registration acceptance message;

[0227] The processing unit 1202 is used to start the timer;

[0228] 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,

[0229] 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.

[0230] 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.

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

[0232] 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.

[0233] 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.

[0234] In one implementation, when the communication device 1200 is a terminal, wherein:

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

[0236] The interface unit 1201 is also used to receive a registration acceptance message;

[0237] The interface unit 1201 is further configured to send a registration completion message if the registration acceptance message carries a packet assisted paging early indication PEIPS parameter or an enhanced discontinuous reception eDRX parameter.

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

[0239] 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 carrying a PEIPS parameter or an eDRX parameter.

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

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

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

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

[0244] 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,

[0245] 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.

[0246] 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 carrying a PEIPS parameter or an eDRX parameter.

[0247] 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 processing unit 1202 starts a timer, including:

[0248] 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.

[0249] In one implementation, when the communication device 1200 is a terminal, wherein:

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

[0251] The processing unit 1202 is used to start the timer;

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

[0253] 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.

[0254] In one implementation, when the communication device 1200 is a terminal, wherein:

[0255] The interface unit 1201 is used 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 paging packet assisted paging early indication PEIPS;

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

[0257] The interface unit 1201 is further configured to monitor the paging message of the terminal in a paging opportunity within a discontinuous reception DRX cycle, or monitor the paging message of the terminal on a specific PEIPS paging group, when the value of the PEIPS parameter does not belong to a valid value range supported by the terminal.

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

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

[0260] 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 paging packet assisted paging early indication PEIPS;

[0261] 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;

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

[0263] In a possible embodiment, the capability information also includes a valid value range of a 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.

[0264] In one implementation, when the communication device 1200 is a terminal, wherein:

[0265] The interface unit 1201 is used to send a registration request message, where the registration request message carries the capability information of the terminal, where the capability information includes first indication information and a valid value range of a paging packet assisted paging early indication PEIPS parameter supported by the terminal, where the first indication information is used to indicate support for PEIPS;

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

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

[0268] The interface unit 1201 is configured to receive 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 paging packet assisted paging early indication PEIPS parameter supported by the terminal, where the first indication information is used to indicate support for PEIPS;

[0269] 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, and a value of the PEIPS parameter is within a valid value range.

[0270] In one implementation, when the communication device 1200 is a terminal, wherein:

[0271] 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;

[0272] The interface unit 1201 is used to start the timer;

[0273] 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 receive downlink information based on the discontinuous reception DRX parameters.

[0274] like Fig.13 The present invention provides a communication device 1300, which is used to implement the functions of the above-mentioned terminal or core network device. The device may be a communication device or a device used in a communication device. The communication device may be a terminal or a core network device. The device used in the communication device may be a chip system or a chip in the communication device. The chip system may be composed of a chip, or may include a chip and other discrete devices.

[0275] The communication device 1300 includes at least one processor 1310, which is used to implement the processing function 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, which is used to implement 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 can be a transceiver, circuit, bus, module or other type of communication interface, which is used to communicate 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.

[0276] 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. The coupling in the embodiment of the present application is an indirect coupling or communication connection between devices, units or modules, which may 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.

[0277] The specific connection medium between the communication interface 1320, the processor 1310 and the memory 1330 is not limited in the embodiment of the present application. Fig.13 The memory 1330, the processor 1310 and the communication interface 1320 are connected via a bus. Fig.13 The connections between the other components are shown in bold lines, which are only for illustration and are not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.13 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0278] 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.

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

[0280] When the above-mentioned communication device is a chip applied to a terminal, the terminal chip implements the function 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.

[0281] When the communication device is a chip applied to a core network device, the core network device chip implements the function 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.

[0282] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or 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.

[0283] 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, and the software modules 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 a component of the processor. The processor and the 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 the storage medium can also exist as discrete components in a terminal or an access network device.

[0284] 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 through 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).

[0285] In the various embodiments of the present application, unless otherwise specified or provided for in any logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

[0286] It is understood that the various numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic.

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

[0288] 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.

[0289] The embodiment of the present application also provides a communication system, which includes a terminal or an access network device. The terminal is used to execute the method executed by the terminal in the above method embodiment. The access network device is used to execute the method executed by the access network device in the above method embodiment.

[0290] 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 the present application is not limited by the described order of actions, because according to the present 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 the present application.

[0291] The descriptions of the various embodiments provided in this application can refer to each other, and the descriptions of the various embodiments have their own emphasis. For parts that are not described in detail in a certain embodiment, refer to the relevant descriptions of other embodiments. For the convenience and simplicity of description, for example, the functions of the various devices and equipment provided in the embodiments of this application and the steps of execution can refer to the relevant descriptions of the method embodiments of this application, and the various method embodiments and the various device embodiments can also refer to, combine or quote each other.

[0292] 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 it. 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 replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate 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.

Citation Information

Cited By

  • Communication methods and communication apparatus

    EP4694410A1

  • Communication methods and communication apparatus

    WO2024234926A1