US 12,219,406 B2
Communication method and apparatus
Yizhuang Wu, Beijing (CN); and Wanqiang Zhang, Beijing (CN)
Assigned to Huawei Technologies Co., Ltd., Shenzhen (CN)
Filed by Huawei Technologies Co., Ltd., Shenzhen (CN)
Filed on Jun. 29, 2021, as Appl. No. 17/362,245.
Application 17/362,245 is a continuation of application No. PCT/CN2019/128476, filed on Dec. 25, 2019.
Claims priority of application No. 201811646628.3 (CN), filed on Dec. 29, 2018.
Prior Publication US 2021/0329504 A1, Oct. 21, 2021
Int. Cl. H04W 36/00 (2009.01); H04W 4/50 (2018.01); H04W 4/60 (2018.01); H04W 8/08 (2009.01); H04W 36/14 (2009.01)
CPC H04W 36/0033 (2013.01) [H04W 4/50 (2018.02); H04W 4/60 (2018.02); H04W 8/08 (2013.01); H04W 36/0011 (2013.01); H04W 36/144 (2023.05)] 15 Claims
OG exemplary drawing
 
1. A communication method comprising:
receiving, by a first mobility management entity, first event information from a unified data management function entity,
wherein the first event information indicates a first-type terminal event to be either an enhanced terminal event or a non-enhanced terminal event,
wherein the first event information comprises indication information that indicates the first-type terminal event,
wherein each of the enhanced or non-enhanced terminal events is based on an application function (AF) entity sending a terminal event subscription request to a network,
wherein the terminal event subscription request for the enhanced terminal event includes service description information, and
wherein the terminal event subscription request for the non-enhanced terminal event does not include service description information;
receiving, by the first mobility management entity, a service transmission notification from a session management function entity;
activating, by the first mobility management entity, the first-type terminal event based on the first event information in response to a terminal apparatus being unreachable;
sending, by the first mobility management entity, the terminal event report to an application function entity that subscribes to the first-type terminal event in response to the terminal apparatus being reachable;
receiving, by the first mobility management entity, second event information based on the first event information in response to the terminal being handed over to a communications system, wherein the second event information does not comprise the indication information; and
based on the first event information, deleting, by the first mobility management entity, information in the second event information associated with the first-type terminal event.
 
7. A first mobility management entity comprising:
a processor; and
a memory coupled to the processor, wherein the memory comprises instructions that, when executed by the processor, cause the terminal apparatus to perform operations comprising:
receiving first event information from a unified data management function entity,
wherein the first event information indicates a first-type terminal event to be either an enhanced terminal event or a non-enhanced terminal event,
wherein the first event information comprises indication information that indicates the first-type terminal event,
wherein each of the enhanced or non-enhanced terminal events is based on an application function (AF) entity sending a terminal event subscription request to a network,
wherein the terminal event subscription request for the enhanced terminal event includes service description information, and
wherein the terminal event subscription request for the non-enhanced terminal event does not include service description information;
receiving a service transmission notification from a session management function entity;
activating the first-type terminal event based on the first event information when a terminal apparatus is unreachable;
sending the terminal event report to an application function entity that subscribes to the first-type terminal event when the terminal apparatus is reachable;
receiving second event information based on the first event information in response to the terminal being handed over to a communications system, wherein the second event information does not comprise the indication information; and
based on the first event information, deleting information in the second event information associated with the first-type terminal event.
 
12. A unified data management function entity comprising:
a processor; and
a memory coupled to the processor, wherein the memory comprises instructions that, when executed by the processor, cause the unified data management function entity to perform operations comprising:
receiving third event information from a control function entity,
wherein the third event information further comprises service description information when a terminal event is a first-type terminal event;
obtaining first event information based on the third event information, wherein the first event information indicates whether the first-type terminal event is either an enhanced terminal event or a non-enhanced terminal event,
wherein each of the enhanced or non-enhanced terminal events is based on an application function (AF) entity sending a terminal event subscription request to a network,
wherein the terminal event subscription request for the enhanced terminal event includes service description information, and
wherein the terminal event subscription request for the non-enhanced terminal event does not include service description information;
sending the first event information to a first mobility management function entity when a terminal apparatus accesses a first communications system,
wherein the first event information is used to activate the first-type terminal event or the non-first-type terminal event; and
sending a second event information to a second mobility management function entity after the terminal is handed over from the first communications system to a second communications system.