WO2020135536A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2020135536A1
WO2020135536A1 PCT/CN2019/128476 CN2019128476W WO2020135536A1 WO 2020135536 A1 WO2020135536 A1 WO 2020135536A1 CN 2019128476 W CN2019128476 W CN 2019128476W WO 2020135536 A1 WO2020135536 A1 WO 2020135536A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
terminal
information
event information
function entity
Prior art date
Application number
PCT/CN2019/128476
Other languages
English (en)
French (fr)
Inventor
吴义壮
张万强
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19902156.9A priority Critical patent/EP3897010A4/en
Publication of WO2020135536A1 publication Critical patent/WO2020135536A1/zh
Priority to US17/362,245 priority patent/US20210329504A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer

Definitions

  • This application relates to the field of communication technology, and in particular, to a communication method and device.
  • the schematic diagram of the existing evolved packet system (EPS) non-roaming architecture in order to support the installation of third-party applications (such as machine type applications, etc.) application (server, SCS/AS) uses the EPS network to enhance the existing network architecture. Introduced a service capability opening function (service capability, function, SCEF) network element.
  • service capability, function, SCEF service capability opening function
  • FIG. 2 the schematic diagram of the interface in the 3rd generation partnership project (3GPP) EPS network architecture opened through SCEF. SCEF provides SCS/AS with the services provided by the secure 3GPP network interface And ability.
  • 3GPP 3rd generation partnership project
  • Machine-type services include a service that does not require high latency, that is, a high-latency service.
  • a monitoring "downlink data notification (DDN) failure available terminal (availability after DDN failure)" event is defined. That is, SCS/AS can subscribe to the 3GPP EPS network through SCEF to monitor the "Notification available after DDN failure" event.
  • DDN downlink data notification
  • the EPS network When SCS/AS sends a data packet to the terminal through the EPS network, if the terminal is in an unavailable state, the EPS network will activate the "Notification after DDN failure" event, that is, monitor the status of the terminal: When the terminal enters the available state, the network passes SCEF Report the available state of the terminal to SCS/AS so that SCS/AS can send data to the terminal again.
  • mobility management entity mobility management entity
  • SGW serving gateway
  • MME mobility management entity
  • PSM power saving mode
  • MICO mobile initiated connection only
  • the report mechanism can be used after the DDN fails.
  • the session management functional entity that manages a specific service, subscribe to terminal events from it.
  • the session management functional entity When receiving the service detection notification of the user plane functional entity, the session management functional entity notifies the access and mobility management functional entity to monitor the terminal event, thus in the 5G architecture In, you can subscribe and monitor terminal events for specific services.
  • FIG. 3 is a schematic diagram of a 4G and 5G interworking architecture. Under this interworking architecture, terminal events can be subscribed to 4G or 5G networks. However, it does not solve the problem of how to perform terminal event notification when the terminal moves between different systems.
  • the present application provides a communication method and device to solve how to perform terminal event notification when a terminal device accesses a different communication system.
  • a communication method includes: a first mobility management entity receives first event information from a unified data management function entity, and the first event information is used to indicate a first type of terminal event, so The first event information includes an event association identifier, and the event association identifier is used to identify context information of the terminal event, or the event association identifier is used to identify the terminal event report;
  • the management function entity receives the service transmission notification; when the terminal device is unreachable, the first mobility management entity activates the first type of terminal event according to the first event information; and when the terminal device is reachable, The first mobility management entity sends a terminal event report to an application function entity that subscribes to the first type of terminal event.
  • the first mobility management functional entity may receive event information from the unified data management functional entity, and the event information is used to indicate a terminal event of the first type, so that when the terminal device is reachable, the first mobility management functional entity may According to the event information, terminal available notification information is sent to the application function entity subscribing to the first type of terminal event, which improves the pertinence of sending terminal event reports.
  • the first event information further includes indication information, and the indication information is used to indicate the terminal event of the first type.
  • the first event information may include explicit indication information indicating the terminal event of the first type.
  • the method further includes: after the terminal device switches the communication system, the first mobility management entity receives the first event information from the unified data management function entity.
  • the first mobile management entity corresponding to the switched communication system does not store the first event information, and can receive the first event information from the unified data management function entity, and the unified data management function entity Responsible for providing corresponding event information when the terminal device accesses different communication systems.
  • the method further includes: after the terminal switches the communication system, the first mobility management entity receives one or more of the second event information from the second mobility management entity, The indication information is not included in the second event information; the first mobility management entity receives the first event information from the unified data management function entity; and the first mobility management entity according to the first Event information, delete the second event information corresponding to the terminal event of the first type in the one or more second event information.
  • the first mobility management entity may receive second event information from the second mobility management entity corresponding to the communication system before switching, but the second event information does not include indication information because The first mobility management entity can perform corresponding activation and event notification on the first type of terminal event. Therefore, the first mobility management entity also needs to receive the first event information from the unified data management function entity, and the second event information is not different. Type terminal event to indicate, therefore, it is necessary to delete the second event information corresponding to the first type of terminal event in the plurality of second event information, so as not to generate when the terminal event is activated according to the first event information and the second event information conflict.
  • the method further includes: when the terminal switches the communication system, the first mobility management entity obtains second event information according to the first event information, and the second The event information does not include the indication information; and the first mobility management entity sends the second event information to the second mobility management entity.
  • the first mobility management entity can obtain the second Event information, that is, the first event information is mapped to the second event information without indicating the terminal event type, and then the first mobility management entity sends the processed second event information to the second mobility management entity.
  • the indication information includes data network name and/or slice information.
  • the terminal event of the first type is an enhanced terminal event, or the terminal event of the first type is a non-enhanced terminal event.
  • it may be an indication of an enhanced terminal event, or an indication of a non-enhanced terminal event.
  • the first mobility management entity activates the enhanced terminal event, and when the terminal device is reachable, subscribes to the enhanced terminal event Of the application function entity sends a terminal available notification message, but for non-enhanced terminal events, it does not activate and does not send a terminal available notification;
  • the first mobility management entity activates the non-enhanced terminal event, and when the terminal device is reachable, sends a terminal available notification message to the application function entity subscribing to the non-enhanced terminal event, but does not perform the enhanced terminal event Activate and do not send notification of terminal availability.
  • a communication method includes: a unified data management function entity receives third event information from a control function entity, the third event information includes an event association identifier, and the event association identifier is used to identify The context information of the terminal event, or the event association identifier is used to identify the terminal event report, and when the terminal event is a terminal event of the first type, the third event information further includes service description information;
  • the unified data management function entity obtains first event information according to the third event information, wherein the first event information is used to indicate a terminal event of the first type or a terminal event not of the first type, the first The event information includes the event association identifier; and when the terminal device accesses the first communication system, the unified data management function entity sends the first event information to the first mobility management function entity, and the first event information is It is used for the first mobility management function entity to activate the terminal event of the first type.
  • the first mobility management functional entity may receive event information from the unified data management functional entity, the event information is used to indicate the type of terminal event, so that when the terminal device is reachable, the first mobility management functional entity may For the type of event, terminal available notification information is sent to an application function entity subscribing to this type of terminal event, which improves the pertinence of terminal available notification.
  • the first event information further includes indication information, and the indication information is used to indicate the terminal event of the first type.
  • the method further includes: when the terminal device switches to the second communication system, the unified data management function entity sends second event information to the second mobility management function entity.
  • the second event information does not include the indication information, and the second event information is used to activate all terminal events.
  • the second mobility management function entity cannot distinguish the types of subscribed terminal events, and cannot send the available notification information of the terminal in a targeted manner.
  • the method further includes: after the terminal switches from the second communication system to the first communication system, the unified data management function entity moves to the first The management function entity sends the first event information.
  • the method further includes: after the terminal is switched from the first communication system to the second communication system, the unified data management function entity moves to the second mobility management function The entity sends the second event information.
  • a communication device which can implement the above-mentioned communication method in the first aspect.
  • the communication device may be a chip or a device.
  • the above method can be implemented by software, hardware, or corresponding software executed by hardware.
  • the structure of the communication device includes a processor and a memory; the processor is configured to support the device to perform the corresponding function in the above communication method.
  • the memory is used for coupling with a processor, which stores necessary programs (instructions) and/or data of the device.
  • the communication device may further include a communication interface for supporting communication between the device and other network elements.
  • the communication device may include a unit module that performs corresponding actions in the above method.
  • the device includes:
  • the transceiver unit is used to receive first event information from the unified data management function entity, the first event information is used to indicate a terminal event of the first type, the first event information includes an event association identifier, and the event association identifier is used To identify the context information of the terminal event, or the event association identifier is used to identify the terminal event report;
  • the transceiver unit is also used to receive service transmission notification from the session management function entity;
  • the processing unit is configured to activate the terminal event of the first type according to the first event information when the terminal device is unreachable;
  • the transceiver unit is also used to send a terminal event report to an application function entity that subscribes to the first type of terminal event when the terminal device is reachable.
  • the first event information further includes indication information, and the indication information is used to indicate the terminal event of the first type.
  • the transceiver unit is further configured to receive the first event information from the unified data management function entity after the terminal device switches the communication system.
  • the transceiver unit is further configured to receive one or more second event information from a second mobility management entity after the terminal switches the communication system, the second event information does not include the indication information;
  • the transceiver unit is further configured to receive the first event information from the unified data management function entity;
  • the processing unit is further configured to delete the second event information corresponding to the terminal event of the first category in the one or more second event information according to the first event information.
  • the processing unit is further used to obtain second event information according to the first event information during the process of the terminal switching the communication system, the second event information does not include the indication information;
  • the transceiver unit is also used to send the second event information to a second mobility management entity.
  • the indication information includes data network name and/or slice information.
  • the terminal event of the first type is an enhanced terminal event, or the terminal event of the first type is a non-enhanced terminal event.
  • a processor and a transceiver device are included.
  • the processor is coupled to the transceiver device, and the processor is used to execute a computer program or instruction to control the transceiver device to receive and receive information. Send; when the processor executes the computer program or instruction, the processor is also used to implement the above method.
  • the transceiver device may be a transceiver, a transceiver circuit or an input-output interface.
  • the transceiver device is a transceiver circuit or an input-output interface.
  • processor is used to perform the following steps:
  • the transceiver device When the terminal device is reachable, the transceiver device is controlled to send a terminal event report to an application function entity that subscribes to the first type of terminal event.
  • the first event information further includes indication information, and the indication information is used to indicate the terminal event of the first type.
  • the processor further executes the step of controlling the transceiver device to receive the first event information from the unified data management function entity after the terminal device switches the communication system.
  • the processor further executes the following step: after the terminal switches the communication system, controlling the transceiver device to receive one or more second event information from the second mobility management entity, the second event The instruction information is not included in the information;
  • the processor further performs the following steps: when the terminal switches the communication system, second event information is obtained according to the first event information, and the second event information does not include the indication information;
  • the indication information includes data network name and/or slice information.
  • the terminal event of the first type is an enhanced terminal event, or the terminal event of the first type is a non-enhanced terminal event.
  • the sending unit may be an output unit, such as an output circuit or a communication interface; the receiving unit may be an input unit, such as an input circuit or a communication interface.
  • the sending unit may be a transmitter or a transmitter; the receiving unit may be a receiver or a receiver.
  • a communication device which can implement the communication method in the second aspect described above.
  • the communication device may be a chip or a device, and the above method may be implemented through software, hardware, or executing corresponding software through hardware.
  • the structure of the communication device includes a processor and a memory; the processor is configured to support the device to perform the corresponding function in the above communication method.
  • the memory is used to couple with the processor, which stores necessary programs (instructions) and data of the device.
  • the communication device may further include a communication interface for supporting communication between the device and other network elements.
  • the communication device may include a unit module that performs corresponding actions in the above method.
  • the device includes:
  • the transceiver unit is configured to receive third event information from the control function entity, where the third event information includes an event association identifier, the event association identifier is used to identify context information of the terminal event, or the event association identifier is used to Identify the terminal event report, when the terminal event is a terminal event of the first type, the third event information further includes service description information;
  • a processing unit configured to obtain first event information according to the third event information, wherein the first event information is used to indicate a terminal event of the first type or a terminal event other than the first type, the first event
  • the information includes event-related identification
  • the transceiving unit is also used to send the first event information to the first mobility management function entity when the terminal device accesses the first communication system, the first event information is used to activate the terminal of the first type event.
  • the first event information further includes indication information, and the indication information is used to indicate the terminal event of the first type.
  • the transceiver unit is further configured to send second event information to the second mobility management function entity when the terminal device switches to the second communication system, the second event information does not include the indication information, The second event information is used to activate all terminal events.
  • the transceiver unit is further configured to send the first event information to the first mobility management function entity.
  • the transceiver unit is further configured to send the second event information to the second mobility management function entity.
  • a processor and a transceiver device are included.
  • the processor is coupled to the transceiver device, and the processor is used to execute a computer program or instruction to control the transceiver device to receive and receive information. Send; when the processor executes the computer program or instruction, the processor is also used to implement the above method.
  • the transceiver device may be a transceiver, a transceiver circuit or an input-output interface.
  • the transceiver device is a transceiver circuit or an input-output interface.
  • processor is used to perform the following steps:
  • first event information is used to indicate a terminal event of the first type or a terminal event other than the first type, and the first event information includes the event Associated identification;
  • the transceiver device When the terminal device accesses the first communication system, the transceiver device is controlled to send the first event information to the first mobility management function entity, and the first event information is used to activate the first type of terminal event.
  • the first event information further includes indication information, and the indication information is used to indicate the terminal event of the first type.
  • the processor further executes the following step: when the terminal device switches to the second communication system, controlling the transceiver device to send second event information to the second mobility management function entity, the second event information The indication information is not included, and the second event information is used to activate all terminal events.
  • the processor further executes the following step: after the terminal is switched from the second communication system to the first communication system, controlling the transceiver device to send the mobile station to the first mobility management function entity Describe the first event information.
  • the processor further executes the following step: after the terminal is switched from the first communication system to the second communication system, controlling the transceiver device to send the second mobile management function entity the first 2. Event information.
  • the receiving unit may be an input unit, such as an input circuit or a communication interface; and the sending unit may be an output unit, such as an output circuit or a communication interface.
  • the receiving unit may be a receiver (also called a receiver); the sending unit may be a transmitter (also called a transmitter).
  • a computer-readable storage medium in which instructions are stored in the computer-readable storage medium, which when executed on a computer, causes the computer to execute the method described in the above aspects.
  • a computer program product containing instructions, which when executed on a computer, causes the computer to execute the method described in the above aspects.
  • Figure 1 is a schematic diagram of an existing EPS non-roaming architecture
  • Figure 2 is a schematic diagram of the interface architecture of the 3GPP EPS network architecture opened through SCEF;
  • Figure 3 is a schematic diagram of a 4G and 5G interworking architecture
  • 4a is a schematic diagram of a 5G non-roaming architecture based on a service interface
  • 4b is a schematic diagram of a 5G reference point-based non-roaming architecture
  • FIG. 5 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of an exemplary method for configuring event information
  • FIG. 7 is a schematic diagram of subsequent event detection, activation, and notification processes corresponding to FIG. 6;
  • FIG. 8 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • 9 is a schematic flowchart of an example of acquiring event information from 4G to 5G;
  • FIG. 10 is a schematic flowchart of an example of acquiring event information from 5G to 4G;
  • FIG. 11 is a schematic structural diagram of a module of a communication device according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of another communication device according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a hardware structure of a communication device provided by an embodiment of the present application.
  • the technical solution of the present application can be applied to the non-roaming architecture of the EPS network shown in FIG. 1, and can also be applied to the roaming architecture of the EPS network; it can also be applied to the non-roaming architecture and roaming architecture of the next generation network, for example In the 5G non-roaming architecture based on the service interface shown in FIG. 4a, and in the 5G reference point-based non-roaming architecture shown in FIG. 4b.
  • the communication system mainly includes an access and mobility management function (access and mobility management function, AMF) entity, and a session management function (Session Management Function, SMF) Entity, user plane function (UPF) entity, network open function (NEF) entity, and application function (AF) entity. It may also include a policy control function (PCF) entity, a unified data repository (UDR) entity and a unified data management (UDM) functional entity.
  • AMF access and mobility management function
  • SMF Session Management Function
  • UPF user plane function
  • NEF network open function
  • AF application function
  • PCF policy control function
  • UDR unified data repository
  • UDM unified data management
  • FIGS. 4a and 4b the functions of the functional entities in FIGS. 4a and 4b are as follows:
  • AMF entity mainly responsible for the processing of signaling, such as access control, mobility management, attachment and detachment, and gateway selection.
  • AMF entity When the AMF entity provides services for the session in the terminal, it will provide control plane storage resources for the session to store the session ID, the SMF entity ID associated with the session ID, and so on.
  • SMF entity mainly responsible for session management, specifically responsible for the selection of user plane functional entities, user plane functional entity redirection, Internet protocol (IP) address allocation, bearer establishment, modification and release, and quality of service , QoS) control.
  • IP Internet protocol
  • UPF entity responsible for forwarding and receiving user data in the terminal.
  • User data can be received from the data network and transmitted to the terminal through the access network device; user data can also be received from the terminal through the access network device and forwarded to the data network.
  • the transmission resources and scheduling functions in the UPF entity serving the terminal are managed and controlled by the SMF entity.
  • NEF entity mainly supports the secure interaction between the 3GPP network and third-party applications. NEF can safely open network capabilities and events to third-party applications to strengthen or improve application service quality. 3GPP networks can also securely obtain relevant data from third-party applications to enhance network intelligent decision-making; meanwhile, this functional entity supports Restore structured data from UDR or store structured data in UDR.
  • AF entity Major support network interacts with the 3GPP to provide services, such as impact data routing decisions, policy control function, or provide some business services (these services may be a third party (3 rd party) on the network side, a third party may not be of).
  • services such as impact data routing decisions, policy control function, or provide some business services (these services may be a third party (3 rd party) on the network side, a third party may not be of).
  • PCF entity mainly supports the provision of a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is responsible for obtaining user contract information related to policy decisions.
  • UDR entity Mainly responsible for storing structured data.
  • the stored content includes contract data and strategy data, externally exposed structured data and application-related data.
  • UDM entity mainly used to manage user subscription information.
  • the above functional entity is only a name, and the name itself does not constitute a limitation on the entity.
  • the session management function entity may also be replaced with "session management function" or other names.
  • the session management function entity may also correspond to an entity including other functions besides the session management function.
  • the user plane functional entity may also be replaced with "user plane function” or other names, and the user plane functional entity may also correspond to an entity that includes other functions in addition to the user plane function. A unified description will be made here, and will not be repeated below.
  • the terminal accesses the network through a radio access network (RAN) device or an access network (AN) device.
  • the RAN device is mainly a wireless network device in a 3GPP network
  • the AN may be an access network device defined by non-3GPP.
  • the terminal may be a user equipment (UE), a handheld terminal, a notebook computer, a subscriber unit, a cellular phone, a smart phone, a wireless data card, and a personal digital Assistant (personal digital assistant, PDA) computer, tablet computer, wireless modem (modem), handheld device (handheld), laptop computer (laptop), cordless phone (cordless phone) or wireless local loop (wireless local loop (WLL ) Stations, machine type communication (MTC) terminals or other devices that can access the network.
  • UE user equipment
  • PDA personal digital assistant
  • modem wireless modem
  • handheld device handheld
  • laptop computer laptop
  • cordless phone cordless phone
  • WLL wireless local loop
  • MTC machine type communication
  • the terminal can communicate with a radio access network (RAN) device using a certain air interface technology.
  • the RAN equipment is mainly responsible for the radio resource management, QoS management, data compression and encryption functions on the air interface side.
  • the access network device may include various forms of base stations, such as macro base stations, micro base stations (also called small stations), relay stations, and access points. In systems that use different wireless access technologies, the names of devices with base station functions may be different.
  • gNB In a 5G system, it is called gNB; in a long term evolution (LTE) system, it is called It is evolved Node B (evolved NodeB, eNB or eNodeB); in the third generation (3rd generation, 3G) system, it is called Node B (Node B) and so on.
  • LTE long term evolution
  • Node B evolved Node B
  • Node B Node B
  • the AN equipment allows non-3GPP technologies to be used for interconnection between the terminal and the 3GPP core network.
  • non-3GPP technologies such as wireless fidelity (Wi-Fi), global microwave interconnection access (worldwide interoperability for microwave access, WiMAX ), code division multiple access (code division multiple access, CDMA) network, etc.
  • the terminal is in an unavailable state, which means that the network initiates paging for the terminal, but no response is received, or the terminal is in PSM mode, or the terminal is in MICO-only mode, and so on.
  • the PSM mode refers to allowing the terminal to reduce energy consumption and cannot be immediately reached to receive service data sent to the terminal.
  • MICO mode means that only the terminal is allowed to initiate a connection.
  • the DDN failure may be that the network detects that the terminal is in an unavailable state, or the priority of the data that triggers DDN (that is, allocation and reservation priority (ARP), which is not higher than the DDN that previously triggered The priority of the data.
  • ARP allocation and reservation priority
  • the terminal event may be an event that needs to obtain various types of status or information from the network.
  • the technical solution of the present application may be applied to a high-latency communication scenario, and the terminal event may be an event that the terminal is available after the DDN fails.
  • the application function entity that provides the high-latency communication service can support service communication that does not require a long delay by subscribing to the event available to the terminal after the DDN fails.
  • the terminal event may also be a terminal reachable event and so on.
  • the application function entity installs related applications to provide corresponding services or services.
  • the subscription of terminal events refers to subscribing to event notifications or modifying already subscribed events through service operations.
  • “Multiple” refers to two or more. In view of this, in the embodiments of the present application, “multiple” may also be understood as “at least two”.
  • “And/or” describes the relationship of the related objects, indicating that there can be three relationships, for example, A and/or B, which can indicate: there are three cases of A alone, A and B, and B alone. In addition, the character “/”, unless otherwise specified, generally indicates that the related object is a "or" relationship.
  • the enhanced terminal event refers to the application function (application) (AF) entity sends a terminal event subscription request to the network, the request includes service description information;
  • the non-enhanced terminal event refers to the AF sends a terminal event subscription request to the network At this time, the service description information was not included in the request.
  • AF supporting enhanced terminal events may be referred to as enhanced AF
  • AF not supporting enhanced terminal events may be referred to as non-enhanced AF.
  • Embodiments of the present application provide a communication method and device.
  • the first mobility management function entity may receive event information from the unified data management function entity.
  • the event information is used to indicate the first type of terminal event, so that when the terminal device is reachable,
  • the first mobility management function entity can send a terminal event report to the application function entity subscribing to the first type of terminal event according to the event information, which improves the pertinence of sending the terminal event report.
  • FIG. 5 is a schematic flowchart of a communication method according to an embodiment of the present application. The method may include the following steps:
  • the unified data management functional entity receives third event information from the control functional entity.
  • the application function entity subscribes the event to the control function entity.
  • the control function entity may be NEF or SCEF, for example.
  • the event subscription message includes GPSI/external ID, AF ID, and event type.
  • the event type is, for example, an event available to the terminal after DDN failure (availability after DDN failure).
  • the event subscription message also includes DNN/NSSAI and business description information (traffic descriptor) .
  • the application function entity is a non-enhanced application function entity or other types of terminal events, the service subscription information is not included in the event subscription message.
  • the control function entity sends the third event information to UDM or HSS.
  • the control function entity (such as NEF or SCEF or NEF+SCEF) generates the corresponding event association identifier according to the above event subscription message.
  • the event association identifier is used to identify context information of the terminal event, or the event association identifier is used to identify the terminal event report. That is, the control function entity determines the address of the target function entity according to the event association identifier in the received terminal event report message.
  • the event correlation identifier can also be expressed as Reference ID.
  • the event correlation identifier can be used to correlate terminal events and terminal event contexts, so that the context information of the terminal event can be determined by the correlation identifier; in addition, optionally, the event correlation identifier can also It is used to correlate terminal events, subscription requests of application function network elements, and context information of terminal events.
  • the event association identifier is used to identify the terminal event report.
  • the association identifier may be included in the terminal event report.
  • the report may also include the terminal event type. By identifying the terminal event report, it can be determined
  • the terminal event corresponding to the report further identifies the context of the terminal event and is further determined.
  • the event association identifier is used to identify the context information of the terminal event.
  • each functional entity can determine whether to activate the terminal event and report the terminal event report according to the context information of the terminal event.
  • the event association identifier is used to identify the terminal event report, and the mobile management function entity can determine whether to report the terminal event report to the application function entity subscribing to the terminal event according to the event association identifier.
  • the third event information includes UE identification or group identification, AF ID, and event type.
  • the event subscription message also includes DNN/NSSAI and service description information.
  • the third event information also includes DNN/NSSA1 and service description information.
  • the service subscription information is not included in the event subscription message.
  • the unified data management function entity obtains first event information according to the third event information.
  • the UDM can determine that the terminal event is a terminal event of the first type or a terminal event other than the first type according to the service description information included in the third event information, so that the first event information can be obtained according to the third event information.
  • the first event information is used to indicate a terminal event of the first type or a terminal event not of the first type. That is, the first event information is obtained according to the third event information, and the first event information is obtained based on the conversion of the service description information included in the third event information.
  • the first event information may include indication information, which is used to indicate a terminal event of the first type. There is no special definition for the first type of terminal event.
  • the difference between the first type of terminal event and the non-first type terminal event is that the first type of terminal event can be an enhanced AF-subscribed terminal event, not the first type of terminal event.
  • the terminal events are terminal events of non-enhanced AF subscription; or vice versa
  • terminal events of the first type are terminal events of non-enhanced AF subscription
  • terminal events of the non-first category are terminal events of enhanced AF subscription. That is, terminal events that are subscribed to enhanced AF or non-enhanced AF can be distinguished by the type of terminal event.
  • the first event information is used to indicate the terminal event of the first type as an example for description.
  • the first event information includes the event association identifier, and may also include the event type and NEF+SCEF ID. Since the event correlation identifier is used to identify the context information of the terminal event, the network can understand that the terminal event is the first type of terminal event or the non-first type of terminal event according to the event correlation identifier.
  • the unified data management function entity sends the first event information to the first mobility management function entity.
  • the first communication system may be a 5G system, for example.
  • the first event information is used to activate the terminal event of the first type.
  • the first mobility management entity receives first event information from the unified data management function entity, the first event information is used to indicate a terminal event of the first type, and the first event information includes an event association identifier, the event The association identifier is used to identify the context information of the terminal event, or the event association identifier is used to identify the terminal event report.
  • the first mobility management entity receives the service transmission notification from the session management function entity.
  • the service transmission notification is used to notify the first mobile management entity of receiving the downlink data notification from the application function entity that subscribes to the first type of terminal event.
  • the first mobility management function entity activates the terminal event of the first type according to the first event information.
  • the first mobility management function entity After receiving the above service transmission notification, the first mobility management function entity detects whether the terminal device is reachable. When the terminal device is unreachable, the first mobility management function entity activates the first type of terminal event according to the first event information.
  • the first mobility management function entity sends a terminal event report to an application function entity that subscribes to the first type of terminal event.
  • the first mobility management function entity When the first mobility management function entity detects that the terminal device is reachable, it sends a terminal event report to the application function entity that subscribes to the first type of terminal event, instead of sending the terminal event report to all application function entities that send subscription messages.
  • the unified data management function entity sends second event information to the second mobility management function entity, and the second event information does not include the indication information.
  • the second communication system is, for example, a 4G communication system, or any generation communication system below 5G.
  • the UDM sends second event information to the second mobility management function entity, and the second event information does not indicate that the terminal event is a terminal event of the first type, or does not include the foregoing indication information.
  • the second mobility management function entity activates all terminal events when receiving the service transmission notification sent by the session management function entity.
  • the second mobility management function entity receives the service transmission notification of one or more application function entities and detects that the terminal device is unreachable Time, activate all subscribed terminal events.
  • the second mobility management function entity sends terminal event report information to all application function entities that subscribe to the terminal event.
  • the second mobile management function entity Since the second event information does not indicate whether the terminal event is the first type of terminal event, the second mobile management function entity sends a terminal event to all application function entities subscribing to the terminal event when it detects that the terminal device is reachable Report information.
  • the first mobility management function entity may receive event information from the unified data management function entity, and the event information is used to indicate a terminal event of the first type, so that when the terminal device is reachable,
  • the first mobility management function entity can send a terminal event report to the application function entity subscribing to the first type of terminal event according to the event information, which improves the pertinence of sending the terminal event report.
  • a schematic flowchart of a method for configuring event information includes the following steps:
  • AF1 AF1, AF2 and AF3 initiate event subscription to UDM+HSS/UDM through NEF+SCEF/NEF.
  • AF1 is enhanced AF
  • AF2 and AF3 are non-enhanced AF.
  • AF1 sends an event subscription to NEF+SCEF/NEF, it contains ⁇ DNN/NSSAI, service description information (traffic descriptor), event type (for example, terminal available event after DDN failure), UE ID or group ID (GPSI /external ID), application ID (AF ID) ⁇ .
  • NEF+SCEF means that NEF and SCEF are jointly responsible for event subscriptions
  • UDM+HSS means that UDM and HSS are jointly responsible for receiving event subscriptions.
  • NEF+SCEF/NEF sends the third event information to UDM+HSS/UDM according to the received event.
  • NEF+SCEF/NEF sends ⁇ DNN/NSSAI, service description information, event type, UE ID or group ID, NEF+SCEF/NEF ID, reference ID1 ⁇ ; for AF2, NEF+SCEF/NEF Send ⁇ UE ID or group ID, event type, NEF+SCEF/NEF ID, reference ID2 ⁇ ; for AF3, NEF+SCEF/NEF send ⁇ UE ID or group ID, event type, NEF+SCEF/NEF ID, reference ID2 ⁇ .
  • Reference ID is the event association identifier.
  • reference ID1 is used to associate terminal events subscribed by AF1, for example, this is the first type of terminal events
  • reference ID2 is used to associate terminal events subscribed to AF2 and AF3, for example, this is other types of terminal events.
  • UDM+HSS/UDM provides event information to the MME or AMF according to the received third event information and the type of network accessed by the UE.
  • the specific timings include: 1) provide event information to AMF or MME during the UE's registration or attachment process; 2) at any time after the UE has registered to the network, UDM+HSS/UDM receives the subscription event, Provide event information to AMF or MME.
  • UDM+HSS/UDM provides event information that contains indication information.
  • UDM+HSS/UDM provides event information including indication information.
  • UDM+HSS/UDM always provides the existing event information.
  • UDM+HSS/UDM provides event information including indication information 1, for non-enhanced events, when the UE accesses via AMF, UDM+HSS/ UDM provides event information including instruction information 2.
  • the MME is not modified, and UDM+HSS/UDM provides the second event information to the MME.
  • the event information provided by UDM+HSS/UDM to MME is ⁇ Event type, Reference ID1, NEF+SCEF ID ⁇ , ⁇ Event type, Reference ID2, NEF+SCEF ID ⁇ , ⁇ Event type, Reference ID2, NEF+ SCEF ID ⁇ .
  • UDM+HSS/UDM provides the first event information to the AMF.
  • the event information provided to the AMF is ⁇ Event type, Reference ID1, NEF+SCEF ID, Information ⁇ , ⁇ Event type, Reference ID2, NEF+SCEF ID ⁇ , ⁇ Event type, Reference ID3, NEF+SCEF ID ⁇ Or ⁇ Event type, Reference ID1, NEF+SCEF ID ⁇ , ⁇ Event type, Reference ID2, NEF+SCEF ID, Information ⁇ , ⁇ Event type, Reference ID3, NEF+SCEF ID, Information ⁇ .
  • UDM+HSS/UDM depends on the AF that initiated the subscription, and according to the UE access to the communication system.
  • the first event information is provided to the AMF.
  • the event information is used to indicate the terminal event of the first type; for example, when accessing the 4G communication system, the second event information is provided to the MME, and the second event information is not used to indicate the terminal event of the first type.
  • UDM+HSS/UDM provides SMF with event detection information, so that SMF notifies UPF to detect service information, so as to determine that a specific service occurs when the UE is unreachable.
  • FIG. 6 the subsequent event detection, activation, and notification processes are shown in FIG. 7. The method includes the following steps:
  • UDM+HSS determines to transmit event information to SMF.
  • UDM+HSS sends event subscription information to SMF.
  • the event subscription information includes: event type, service description information, NEF+SCEF ID (NEF+SCEFID) and event association ID (NEFreferenceID).
  • S703, SMF and UPF perform N4 session establishment/modification.
  • UDM+HSS/UDM provides event service information to SMF, so that SMF sends service information to UPF.
  • the service information includes a packet filter (PDR) or first indication information.
  • PDR packet filter
  • the first indication information is used to indicate to the SMF when service data corresponding to the terminal event is detected.
  • AF1 sends a downlink data packet to the UE, and the UPF receives the downlink data packet sent by AF1.
  • AF2 sends a downlink data packet to the UE, and the UPF receives the downlink data packet sent by AF2.
  • the UPF When the UPF receives the downlink data packet sent by AF1 and determines that the downlink tunnel is unavailable, the UPF sends a data notification (DN) to the SMF.
  • the data notification includes second indication information.
  • the second indication information is used to indicate that a downlink data packet sent by AF1 is detected.
  • the SMF can determine that it is a downlink data packet sent by AF1 according to the second instruction information.
  • the second indication information includes data network name or slice information.
  • the UPF When the UPF receives the downlink data packet sent by AF2, and determines that the downlink tunnel is unavailable, the UPF sends a data notification to the SMF.
  • the data notification does not include the second indication information.
  • the SMF cannot determine that it is a downlink data packet sent by AF2 or AF3.
  • the SMF sends a Namf_communication_N1N2MessageTransfer message to the AMF.
  • the message includes NEF reference ID1.
  • the SMF determines that it is the downlink data packet sent by AF1
  • the NEF reference ID1 corresponding to the terminal event is included in the message.
  • the NEF reference ID is used to uniquely identify the subscribed terminal event.
  • the SMF sends a Namf_communication_N1N2MessageTransfer message to the AMF.
  • the message does not include the NEF reference ID.
  • the SMF cannot determine the downlink data packet sent by AF2 or AF3, the NEF reference ID corresponding to the terminal event is not included in the message.
  • the AMF sends an Nsmf_communication_N1N2MessageTransfer message to the SMF.
  • the SMF sends a failure indication to the UPF.
  • the AMF After the AMF receives the Namf_communication_N1N2MessageTransfer message sent by the SMF, because the message includes NEF reference ID1, the AMF activates the terminal event associated with the NEF reference ID1.
  • the AMF After the AMF receives the Namf_communication_N1N2MessageTransfer message sent by the SMF, because the message does not include the NEF reference ID, the AMF cannot distinguish between the AF2 and AF3 sending the downstream data packet, and both activate the terminal events subscribed by AF2 and AF3.
  • the UE connects to the network.
  • the AMF sends an event report to the NEF+SCEF/NEF according to the activated event.
  • the event report includes the UE available notification and NEF reference ID1.
  • AMF After AMF detects that the UE is connected to the network, and detects the terminal event where the AF1 subscription is activated, it reports the event to NEF+SCEF/NEF, and includes NEF reference ID1 in the event report.
  • AMF sends an event report to NEF+SCEF/NEF according to the activated event.
  • the event report includes the UE available notification, NEF reference ID2 and NEF reference ID3.
  • AMF After AMF detects that the UE is connected to the network and detects the terminal event that activated the subscription of AF2 and AF3, it reports the event to NEF+SCEF/NEF, and NEF reference ID2 and NEF reference ID3 are included in the event report.
  • NEF+SCEF/NEF sends a subscription event notification to AF1.
  • the subscription event notification is used to notify the UE that it is available.
  • NEF+SCEF/NEF After receiving the event report, NEF+SCEF/NEF sends a subscription event notification to AF1 according to the NEF reference ID1 included in the event report.
  • NEF+SCEF/NEF sends a subscription event notification to AF2 and AF3.
  • the subscription event notification is used to notify the UE that it is available.
  • NEF+SCEF/NEF After receiving the event report, NEF+SCEF/NEF sends subscription event notifications to AF2 and AF3 according to NEF reference ID2 and NEF reference ID3 included in the event report.
  • the AMF when the AMF receives the downlink data sent by the AF subscribing to the first type of terminal event, and when the UE is unavailable, it can activate the terminal event according to the first event information, and when the UE is available, only The terminal event report is sent to the AF; while for the downlink data sent by other AFs, it cannot be distinguished which of the AFs sent the downlink data, so that when the UE is available, the terminal event report is sent to all AFs.
  • the UE may switch between communication systems of different standards, for example, from a 5G communication system to a 4G communication system, or from a 4G communication system to a 5G communication system.
  • the mobile management function entity in the switched communication system may not store the above events Information, how the mobility management function entity obtains corresponding event information during the UE handover process, and the following embodiments provide corresponding solutions.
  • FIG. 8 is a schematic flowchart of another communication method according to an embodiment of the present application. The method may include the following steps:
  • the unified data management function entity After the terminal device switches to the first communication system, the unified data management function entity sends the first event information to the first mobility management function entity.
  • the terminal device is in the second communication system before the handover, and may be a 4G system, for example.
  • the terminal device is switched from the second communication system to the first communication system.
  • the first communication system may be a 5G system, for example.
  • the UDM is the first communication system according to the accessed network, and the UDM sends the first event information to the first mobility management function entity.
  • the first mobility management function entity always uses the first event information provided by UDM.
  • the first event information is used to indicate a terminal event of the first type, that is, it can be determined that the first event information corresponds to the terminal event of the first type according to the content included in the first event information.
  • the first event information also includes indication information, which is used to indicate the terminal event of the first type, and indicates that the first event information corresponds to the terminal event of the first type through explicit instruction information, in other words In other words, this first event information describes the first type of terminal event information.
  • the second mobility management function entity in the second communication system may also provide second event information to the first mobility management function entity.
  • the second event information does not include the above indication information, that is, it cannot be indicated. What type of terminal event corresponds to the second event information.
  • the first mobility management function entity After receiving the first event information sent by the UDM, the first mobility management function entity updates the local event information according to the information provided by the UDM, and deletes the second type of event information received from the second mobility management function entity with the terminal of the first type The second event information corresponding to the event.
  • the second event information provided by the second mobile function functional entity includes event information corresponding to terminal events of the first type, and also includes event information corresponding to terminal events of other types, and event information corresponding to terminal events of other types does not need to be indicated Therefore, the local event information can be updated according to the information provided by the UDM, and the second event information corresponding to the terminal event of the first type in the second event information received from the second mobility management function entity can be deleted.
  • the first mobility management function entity obtains second event information according to the first event information.
  • the first mobility management entity After the terminal device is switched from the first communication system to the second communication system, the second event information provided by the first mobility management function entity to the second mobility management function entity does not include the above indication information. Therefore, the first mobility management entity first The first event information obtains the second event information. In other words, the first event information is mapped to the second event information, that is, to the event information that does not include the indication information.
  • the event information ⁇ Event Type, Reference ID1, NEF+SCEF ID, Indication ⁇ , ⁇ Event Type, Reference ID2, NEF+SCEF ID ⁇ , ⁇ Event Type, Reference ID3, NEF+SCEF ID ⁇ or ⁇ Event type, Reference ID1, NEF+SCEF ID ⁇ , ⁇ Event type, Reference ID2, NEF+SCEF ID, Information ⁇ , ⁇ Event type, Reference ID3, NEF+SCEF ID, Information ⁇ ; map to ⁇ Event type,ReferenceID1,NEF+SCEFID ⁇ , ⁇ Event,type,ReferenceID2,NEF+SCEFID ⁇ , ⁇ Event,type,ReferenceID2,NEF+SCEFID ⁇ .
  • the first mobility management function entity sends the second event information to a second mobility management function entity.
  • the mobile management function entity when switching between different communication systems, for example, when switching from a 4G to a 5G system, the mobile management function entity may obtain the first event information from the unified data management function entity, or The mobile management function entity obtains one or more second event information from the mobile management function entity in the communication system before handover, and receives the first event information from the same data management function entity, and deletes one or more second event information
  • the second event information corresponding to the first type of terminal event, so that the mobility management function entity can obtain the event information in time, and activate the terminal event according to the event information, and subscribe to the terminal in time when the terminal device is reachable
  • the event application function entity sends a terminal event report; for example, when switching from 5G to 4G system, the mobile management function entity in the communication system before the switch can obtain the second event information based on the first event information and send it to the communication system after the switch
  • the mobile management function entity in sends the second event information to apply the unchanged mobile management function entity.
  • the following describes a method for switching from 4G to 5G, 5G to 4G, and the mobile management entity in the switched communication system to obtain event information through FIGS. 9 and 10, respectively.
  • FIG. 9 is a schematic flowchart of an example of acquiring event information from 4G to 5G.
  • the mobility management function entity may be MME, and in the 5G system, the mobility management function entity may be AMF.
  • the MME sends the acquired event information to the AMF, and the MME does not need to be enhanced.
  • the MME sends a handover command (handover command) to the E-UTRAN.
  • E-UTRAN is the access network equipment in the 4G system.
  • the switch command is used to instruct to switch to the 5G system.
  • the E-UTRAN sends a handover command (handover from E-UTRAN command) to the UE.
  • the UE sends a handover determination response message (handover to 5G-RAN confirm) to 5G NG-RAN.
  • 5GNG-RAN is the access network equipment in the 5G system.
  • the NG-RAN sends a handover notification to the AMF.
  • AMF sends a relocation completion notification (forward relocation complete notification) to the MME.
  • the MME sends a relocation completion notification determination response message (forward relocation complete notification) to the AMF.
  • the MME sends the stored event information to the AMF, and the MME does not need to be enhanced.
  • the AMF sends a session update session management context request (Nsmf_PDUSession_UpdateSMContext Request) to SMF+PGW-C.
  • the process is performed through V-SMF in a roaming scenario.
  • S908 SMF+PWG-C and UPF+PGW-U perform the N4session modification process (N4session modification).
  • SMF+PGW-C initiates a registration process to HSS+UDM.
  • HSS+UDM provides service detection information ⁇ NEF+SCEFID/NEFID, referenceID, service information ⁇ to SMF+UDM based on local event information.
  • the SMF sends service information to the UPF in S908 in order for the UPF to report the occurrence of SMF specific events.
  • the SM policy association modification process (SMF initiated, SM policy association, modification) is executed between the SMF+PWG-C and the PCF.
  • This step is optional.
  • SMF+PWG-C sends a session update session management context response (Nsmf_PDUSession_UpdateSMContext) to AMF.
  • the process is performed through V-SMF in a roaming scenario.
  • the N4 session modification process is performed between V-SMF and V-UPF.
  • the UE initiates a mobile registration process (EPS to 5GS mobility registration procedure) to the network.
  • EPS mobile registration process
  • the UE performs a mobile registration process.
  • HSS+UDM provides corresponding event information to AMF according to the access network is 5G.
  • AMF always uses the event information provided by HSS+UDM.
  • the local event information is updated according to the information provided by HSS+UDM, and the event information corresponding to the terminal event of the first type in the event information received from the MME is deleted. Refer to the embodiment shown in FIG. 5 for the description of event information.
  • AMF obtains event information ⁇ Event, type, Reference ID1, NEF+SCEF ID, Information ⁇ , ⁇ Event type, Reference ID2, NEF+SCEF ID ⁇ , ⁇ Event type from UDM ,Reference ID3,NEF+SCEFID ⁇ or ⁇ Event,type,ReferenceID1,NEF+SCEFID ⁇ , ⁇ Event ⁇ type,Reference ID2,NEF+SCEFID,Indication ⁇ , ⁇ Event ⁇ type,Reference ID3,NEF+SCEFID, Indication ⁇ .
  • the MME executes to release resources in the EPC (resource clean in EPC by MME).
  • the mobile management function entity when switching from 4G to 5G system, may obtain the first event information from the unified data management function entity, or the mobile management function entity may obtain one from the mobile management function entity in the communication system before switching Or multiple second event information, and receive the first event information from the same data management function entity, and delete one or more second event information corresponding to the first type of terminal event, thereby making the mobile
  • the sexual management functional entity can obtain the event information in time, activate the terminal event according to the event information, and when the terminal device is reachable, send the terminal event report to the application functional entity subscribing to the terminal event in time.
  • FIG. 10 is a schematic flowchart of an example of acquiring event information from 5G to 4G. The specific process is as follows:
  • NG-RAN sends a handover request (handover request) to AMF.
  • AMF sends a session context request (Nsmf_PDUSession_ContextRequest) to PGW-C+SMF.
  • N4 session modification N4 session modification
  • PGW-C+SMF sends a session context response (Nsmf_PDUSession_Context Response) to the AMF.
  • AMF performs this process through V-SMF and H-SMF.
  • the AMF maps the event to an event used by the MME and includes it in a redirect request (relocation request) and sends it to the MME.
  • AMF performs event mapping, which is based on mapping events to event information that MME can recognize, that is, it does not contain the indicated event information.
  • AMF performs event mapping.
  • the event information ⁇ Event, type, Reference ID1, NEF+SCEF ID, Information ⁇ , ⁇ Event type, Reference ID2, NEF+SCEF ID ⁇ , ⁇ Event type, Reference ID3, NEF+SCEF ID ⁇ or ⁇ Event type, Reference ID1,NEF+SCEFID ⁇ , ⁇ Event,type,ReferenceID2,NEF+SCEFID,Indication ⁇ , ⁇ Event ⁇ type,ReferenceID3,NEF+SCEFID,Indication ⁇ ; mapped to ⁇ Event,type,ReferenceID1,NEF+SCEF ID ⁇ , ⁇ Event, type,ReferenceID2,NEF+SCEFID ⁇ , ⁇ Event,type,ReferenceID2,NEF+SCEFID ⁇ .
  • the MME sends a create session request (create session request) to the SGW.
  • the SGW sends a create session response (create session response) to the MME.
  • the MME sends a handover request (handover request) to the E-UTRAN.
  • E-UTRAN sends a handover request response (handover request) to the MME.
  • MME and SGW execute the process of creating indirect data forwarding tunnel (create omdorect data forwarding tunnel request/response).
  • This step is optional.
  • the MME sends a redirect response (relocation response) to the AMF.
  • Nsmf_PDU_UpdateSMContext a PDU update session management context
  • This step is optional.
  • AMF sends a handover command (handover command) to NG-RAN.
  • the NG-RAN sends a handover command to the UE.
  • the UE sends a handover complete to the NG-RAN.
  • the NG-RAN sends a handover notification to the MME.
  • the MME and AMF perform redirection completion notification (relocation complete notification).
  • the MME sends a modify bearer request (modify bearer request) to the SGW.
  • the SGW sends a modification request bearer request to PGW-C+SMF.
  • the N4 session modification process is performed between PGW-C+SMF and UPF.
  • PGW-C+SMF sends a modify bearer response (modify bearer response) to the SGW.
  • the SGW sends a modify bearer response to the MME.
  • the UE and the EPC network perform a location area update procedure (TAU procedure).
  • TAU procedure location area update procedure
  • the MME obtains event information from HSS+UDM.
  • HSS+UDM provides corresponding event information to MME for 4G according to the accessed network, and MME always uses the event information of HSS+UDM. Specifically, update the local event information according to the information provided by HSS+UDM, or delete the event information received from the MME. Please refer to the embodiment shown in FIG. 5 for the description of the event information.
  • PGW-C+SMF initiates a dedicated bearer activation process (PGW initiated dedicated bearer activation) with SGW, MME and UE.
  • a process of deleting an indirect data forwarding tunnel (delete indirect data forwarding tunnel request/response) is performed between the SGW and the MME.
  • S1021a, AMF and PGW-C+SMF execute a deletion indirect data forwarding tunnel process.
  • the process is performed through V-SMF in the roaming scenario.
  • the mobile management function entity in the communication system before the switch can obtain the second event information according to the first event information, and send it to the mobile management function entity in the communication system after the switch Send the second event information to apply the unchanged mobile management function entity.
  • the device 1100 includes a transceiver unit 111 and a processing unit 112, and the transceiver unit 111 and the processing unit 112 are connected.
  • the transceiver unit 111 is used to receive first event information from the unified data management function entity, where the first event information is used to indicate a terminal event of the first type, the first event information includes an event association identifier, and the event association identifier is used for To identify the context information of the terminal event, or the event association identifier is used to identify the terminal event report;
  • the transceiver unit 111 is also used to receive service transmission notification from the session management function entity;
  • the processing unit 112 is configured to activate the terminal event of the first type according to the first event information when the terminal device is unreachable;
  • the transceiver unit 111 is also used to send a terminal event report to an application function entity that subscribes to the first type of terminal event when the terminal device is reachable.
  • the transceiver unit 111 is further configured to receive the first event information from the unified data management function entity after the terminal device switches the communication system.
  • the transceiver unit 111 is further configured to receive one or more second event information from a second mobility management entity after the terminal switches the communication system, the second event information does not include the Instructions
  • the transceiver unit 111 is further configured to receive the first event information from the unified data management function entity;
  • the processing unit 112 is further configured to delete the second event information corresponding to the terminal event of the first category in the one or more second event information according to the first event information.
  • the processing unit 112 is further configured to obtain second event information according to the first event information after the terminal switches the communication system, and the second event information does not include the indication information;
  • the transceiver unit 111 is further configured to send the second event information to a second mobility management entity.
  • the device 1100 may be a network device, for example, may be a first mobility management function entity or a chip in the first mobility management function entity.
  • the apparatus 1100 may implement other functions of the first mobility management function entity in the embodiment of the present application through the transceiver unit 111 and the processing unit 112. For details, reference may be made to related content in the embodiments shown in FIG. 5 and FIG. 8.
  • the device 1200 includes a transceiver unit 121 and a processing unit 122, and the transceiver unit 121 and the processing unit 122 are connected.
  • the transceiver unit 121 is configured to receive third event information from the control function entity, where the third event information includes an event association identifier, and the event association identifier is used to identify context information of the terminal event, or the event association identifier is used for To identify the terminal event report, when the terminal event is a terminal event of the first type, the third event information further includes service description information;
  • the processing unit 122 is configured to obtain first event information according to the third event information, where the first event information is used to indicate a terminal event of the first type or a terminal event not of the first type, the first Event information includes the event association identifier;
  • the transceiving unit 121 is further configured to send the first event information to the first mobility management function entity when the terminal device accesses the first communication system, the first event information is used to activate the first type of Terminal events.
  • the first event information further includes indication information, and the indication information is used to indicate the terminal event of the first type.
  • the transceiver unit 121 is further configured to send second event information to the second mobility management function entity when the terminal device switches to the second communication system, the second event information does not include all According to the instruction information, the second event information is used to activate all terminal events.
  • the transceiver unit 121 is further configured to send the first event information to the first mobility management function entity after the terminal is switched from the second communication system to the first communication system.
  • the transceiver unit 121 is further configured to send the second event information to the second mobility management function entity after the terminal is switched from the first communication system to the second communication system.
  • the device 1200 may be a network device, for example, may be a unified data management function entity or a chip in the unified data management function entity.
  • a network device for example, may be a unified data management function entity or a chip in the unified data management function entity.
  • the device includes a processor 131 and a transceiver 132.
  • the device further includes a memory 133.
  • the processor 131, the transceiver 132 and the memory 133 are connected through a communication bus.
  • the transceiver device 132 may be a device with a transceiver function for communicating with other network equipment or a communication network.
  • the transceiver device may be an independent sending unit and receiving unit, or it may be a whole transceiver device.
  • the transceiver device can also be called a communication unit.
  • the memory 133 may include one or more memories, and the memory may be one or more devices or devices in a circuit for storing programs or data.
  • the memory 133 may exist independently, and is connected to the processor 131 through a communication bus.
  • the memory may also be integrated with the processor 131.
  • the apparatus 1300 may be used in network equipment, circuits, hardware components, or chips.
  • the apparatus 1300 may be the first mobility management function entity or a chip in the first mobility management function entity in the embodiment of the present application.
  • the device 1300 may implement the first in the embodiments shown in FIGS. 5 and 8 above. A method performed by a mobile management function entity.
  • the processor is used to perform the following steps:
  • the transceiver device When the terminal device is reachable, the transceiver device is controlled to send a terminal event report to an application function entity that subscribes to the first type of terminal event.
  • the first event information further includes indication information, and the indication information is used to indicate the terminal event of the first type.
  • the processor further executes the step of controlling the transceiver device to receive the first event information from the unified data management function entity after the terminal device switches the communication system.
  • the processor further executes the following step: after the terminal switches the communication system, controlling the transceiver device to receive one or more second event information from the second mobility management entity, the second event The instruction information is not included in the information;
  • the processor further performs the following steps: when the terminal switches the communication system, second event information is obtained according to the first event information, and the second event information does not include the indication information;
  • the indication information includes data network name and/or slice information.
  • the terminal event of the first type is an enhanced terminal event, or the terminal event of the first type is a non-enhanced terminal event.
  • the device 1300 may be a unified data management function entity or a chip in the unified data management function entity in the embodiment of the present application.
  • the device 1300 may implement the unified data management in the embodiments shown in FIGS. 5 and 8 above The method performed by the functional entity.
  • the processor is used to perform the following steps:
  • first event information is used to indicate a terminal event of the first type or a terminal event other than the first type, and the first event information includes the event Associated identification;
  • the transceiver device When the terminal device accesses the first communication system, the transceiver device is controlled to send the first event information to the first mobility management function entity, and the first event information is used to activate the first type of terminal event.
  • the first event information further includes indication information, and the indication information is used to indicate the terminal event of the first type.
  • the processor further executes the following step: when the terminal device switches to the second communication system, controlling the transceiver device to send second event information to the second mobility management function entity, the second event information The indication information is not included, and the second event information is used to activate all terminal events.
  • the processor further executes the following step: after the terminal is switched from the second communication system to the first communication system, controlling the transceiver device to send the mobile station to the first mobility management function entity Describe the first event information.
  • the processor further executes the following step: after the terminal is switched from the first communication system to the second communication system, controlling the transceiver device to send the second mobile management function entity the first 2. Event information.
  • the embodiments of the present application also provide a computer-readable storage medium.
  • the methods described in the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media may include computer storage media and communication media, and may also include any media that can transfer a computer program from one place to another.
  • a storage medium may be any available medium that can be accessed by a computer.
  • computer-readable media may include random access memory (RAM), read-only memory (read-only memory (ROM), electrically erasable programmable read-write memory (electrically erasable programmable memory) only memory, EEPROM), compact disk-read-only memory (CD-ROM) or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or in the form of instructions or data structures Store the required program code, and can be accessed by the computer. Also, any connection is properly termed a computer-readable medium.
  • coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio, and microwave
  • coaxial Cables, fiber optic cables, twisted pairs, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of media.
  • magnetic disks and optical discs include compact discs (CDs), laser discs, optical discs, digital universal discs (DVDs), floppy disks, and Blu-ray discs, where magnetic disks usually reproduce data magnetically, while optical discs use The laser optically reproduces the data. Combinations of the above should also be included within the scope of computer-readable media.
  • An embodiment of the present application also provides a computer program product.
  • the methods described in the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in 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 instructions. When the above computer program instructions are loaded and executed on the computer, all or part of the processes or functions described in the above method embodiments are generated.
  • the above-mentioned computer may be a general-purpose computer, a dedicated computer, a computer network, a network device, user equipment, or other programmable devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种通信方法及装置。第一移动管理功能实体可以从统一数据管理功能实体接收事件信息，该事件信息用于指示第一类的终端事件，从而在终端装置可达时，第一移动管理功能实体可以根据该事件信息，向订阅该第一类的终端事件的应用功能实体发送终端事件报告，提高了发送终端事件报告的针对性。

Description

一种通信方法及装置
本申请要求于2018年12月29日提交中国国家知识产权局、申请号为201811646628.3、发明名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
如图1所示的现有的演进分组系统(evolved packet system，EPS)非漫游架构示意图，为了支持安装第三方应用(如机器类型的应用等)的业务能力服务器/应用服务器(service capability server/application server，SCS/AS)使用EPS网络，对现有的网络架构进行了增强。引入了业务能力开放功能(service capability exposure function，SCEF)网元。如图2所示的通过SCEF开放的第三代合作伙伴计划(3rd generation partnership project，3GPP)EPS网络架构中接口的架构示意图，SCEF向SCS/AS提供了通过安全的3GPP网络接口所提供的业务和能力。
机器类型的业务包含一种对时延要求不高的业务，即高延迟业务。基于上述能力开放的架构中，为了支持高延迟业务通信，定义了监测“下行数据通知(downlink data notification，DDN)失败后终端可用通知(availability after DDN failure)”事件。即SCS/AS可以通过SCEF向3GPP EPS网络订阅监测“DDN失败后可用通知”事件。当SCS/AS通过EPS网络向终端发送数据包时，若终端处于不可用状态，EPS网络将激活“DDN失败后可用通知”事件，即监测终端的状态：当终端进入可用状态时，网络通过SCEF向SCS/AS上报终端可用状态，以便SCS/AS重新向终端发送数据。
在第四代(4 th generation，4G)移动通信系统架构中，会话和移动性都是由移动性管理实体(mobility management entity，MME)控制。当接收到服务网关(serving gateway，SGW)发送的DDN消息时，且当终端处于不可用状态时，例如，MME为终端发起寻呼，但是没有收到响应，或者终端处于省电模式(power saving mode，PSM)，或者终端处于只允许终端发起连接(mobile initiated connection only，MICO)模式，MME直接激活监测事件。而在第五代(5 th generation，5G)移动通信系统架构中，会话管理、接入和移动性管理分别由不同的功能实体进行控制。
在5G架构中，例如物联网(internet of things，IoT)业务，需要支持高延迟通信，可以重用DDN失败后可用上报机制。对于管理特定业务的会话管理功能实体，向其订阅终端事件，会话管理功能实体在接收到用户面功能实体的业务检测通知时，通知接入和移动性管理功能实体监测终端事件，从而在5G架构中，可以针对特定的业务进行终端事件的订阅和监测。
在4G和5G架构中，都分别解决了向网络订阅终端事件的问题，但只考虑了单系统场景下的方案。图3为一种4G和5G的互通架构示意图，在该互通架构下，可以向4G或5G 网络订阅终端事件。但是并未解决终端在不同的系统之间移动时如何进行终端事件通知的问题。
发明内容
本申请提供一种通信方法及装置，以解决在终端装置接入不同通信系统时，如何进行终端事件通知。
第一方面，提供了一种通信方法，所述方法包括：第一移动管理实体从统一数据管理功能实体接收第一事件信息，所述第一事件信息用于指示第一类的终端事件，所述第一事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告；所述第一移动管理实体从会话管理功能实体接收业务传输通知；当终端装置不可达时，所述第一移动管理实体根据所述第一事件信息，激活所述第一类的终端事件；以及当所述终端装置可达时，所述第一移动管理实体向订阅所述第一类的终端事件的应用功能实体发送终端事件报告。
在该方面中，第一移动管理功能实体可以从统一数据管理功能实体接收事件信息，该事件信息用于指示第一类的终端事件，从而在终端装置可达时，第一移动管理功能实体可以根据该事件信息，向订阅该第一类的终端事件的应用功能实体发送终端可用通知信息，提高了发送终端事件报告的针对性。
在一种可能的实现方式中，所述第一事件信息还包括指示信息，所述指示信息用于指示所述第一类的终端事件。
在该实现方式中，第一事件信息可以包括明确的指示信息，指示第一类的终端事件。
在另一种可能的实现方式中，所述方法还包括：当所述终端装置切换通信系统后，所述第一移动管理实体从所述统一数据管理功能实体接收所述第一事件信息。
在该实现方式中，终端装置切换通信系统后，切换后的通信系统对应的第一移动管理实体未存储第一事件信息，可以从统一数据管理功能实体接收第一事件信息，统一数据管理功能实体负责终端装置接入不同通信系统时提供对应的事件信息。
在又一种可能的实现方式中，所述方法还包括：当所述终端切换通信系统后，所述第一移动管理实体从第二移动管理实体接收一个或多个所述第二事件信息，所述第二事件信息中未包括所述指示信息；所述第一移动管理实体从所述统一数据管理功能实体接收所述第一事件信息；以及所述第一移动管理实体根据所述第一事件信息，删除所述一个或多个第二事件信息中的与所述第一类的终端事件所对应的第二事件信息。
在该实现方式中，终端装置切换通信系统后，第一移动管理实体可以从切换前的通信系统对应的第二移动管理实体接收第二事件信息，但第二事件信息中未包括指示信息，因为第一移动管理实体可以对第一类的终端事件进行对应的激活和事件通知，因此，第一移动管理实体还需从统一数据管理功能实体接收第一事件信息，并且第二事件信息未对不同类型的终端事件进行指示，因此，还需删除多个第二事件信息中与第一类的终端事件对应的第二事件信息，以免根据第一事件信息和第二事件信息激活终端事件时，产生冲突。
在又一种可能的实现方式中，所述方法还包括：当所述终端切换通信系统过程中，所述第一移动管理实体根据所述第一事件信息得到第二事件信息，所述第二事件信息未包括 所述指示信息；以及所述第一移动管理实体向第二移动管理实体发送所述第二事件信息。
在该实现方式中，终端装置切换通信系统后，由于切换后的通信系统对应的第二移动管理实体不对终端事件的类型进行区分，因此，第一移动管理实体可以根据第一事件信息得到第二事件信息，即将第一事件信息映射为第二事件信息，不对终端事件的类型进行指示，然后第一移动管理实体将处理得到的第二事件信息发送给第二移动管理实体。
在又一种可能的实现方式中，所述指示信息包括数据网络名称和/或切片信息。
在又一种可能的实现方式中，所述第一类的终端事件是增强的终端事件，或所述第一类的终端事件是非增强的终端事件。
在该实现方式中，可以是对增强的终端事件进行指示，也可以是对非增强的终端事件进行指示。当对增强的终端事件进行指示时，可以知道该终端事件的类型是增强的终端事件，第一移动管理实体激活该增强的终端事件，并且在终端装置可达时，向订阅该增强的终端事件的应用功能实体发送终端可用通知消息，而对于非增强的终端事件则不进行激活并且不发送终端可用通知；当对非增强的终端事件进行指示时，可以知道该终端事件的类型是非增强的终端事件，第一移动管理实体激活该非增强的终端事件，并且在终端装置可达时，向订阅该非增强的终端事件的应用功能实体发送终端可用通知消息，而对于增强的终端事件则不进行激活并且不发送终端可用通知。
第二方面，提供了一种通信方法，所述方法包括：统一数据管理功能实体从控制功能实体接收第三事件信息，所述第三事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告，当所述终端事件为第一类的终端事件时，所述第三事件信息还包括业务描述信息；所述统一数据管理功能实体根据所述第三事件信息，得到第一事件信息，其中，所述第一事件信息用于指示第一类的终端事件或非第一类的终端事件，所述第一事件信息包括所述事件关联标识；以及当终端装置接入第一通信系统时，所述统一数据管理功能实体向第一移动管理功能实体发送所述第一事件信息，所述第一事件信息被用于所述第一移动管理功能实体激活所述第一类的终端事件。
在该方面中，第一移动管理功能实体可以从统一数据管理功能实体接收事件信息，该事件信息用于指示终端事件的类型，从而在终端装置可达时，第一移动管理功能实体可以根据终端事件的类型，向订阅该类型的终端事件的应用功能实体发送终端可用通知信息，提高了终端可用通知的针对性。
在一种可能的实现方式中，所述第一事件信息还包括指示信息，所述指示信息用于指示所述第一类的终端事件。
在另一种可能的实现方式中，所述方法还包括：当所述终端装置切换至第二通信系统时，所述统一数据管理功能实体向第二移动管理功能实体发送第二事件信息，所述第二事件信息未包括所述指示信息，所述第二事件信息被用于激活所有终端事件。
在该实现方式中，第二移动管理功能实体则无法区分订阅的终端事件的类型，不能针对性地进行终端可用通知信息的发送。
在又一种可能的实现方式中，所述方法还包括：当所述终端从所述第二通信系统切换至所述第一通信系统后，所述统一数据管理功能实体向所述第一移动管理功能实体发送所 述第一事件信息。
在又一种可能的实现方式中，所述方法还包括：当所述终端从第一通信系统切换至所述第二通信系统后，所述统一数据管理功能实体向所述第二移动管理功能实体发送所述第二事件信息。
第三方面，提供了一种通信装置，可以实现上述第一方面中的通信方法。例如所述通信装置可以是芯片或者设备。可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
在一种可能的实现方式中，所述通信装置的结构中包括处理器、存储器；所述处理器被配置为支持所述装置执行上述通信方法中相应的功能。存储器用于与处理器耦合，其保存所述装置必要的程序(指令)和/或数据。可选的，所述通信装置还可以包括通信接口用于支持所述装置与其他网元之间的通信。
在另一种可能的实现方式中，所述通信装置，可以包括执行上述方法中相应动作的单元模块。
其中，所述装置包括：
收发单元，用于从统一数据管理功能实体接收第一事件信息，所述第一事件信息用于指示第一类的终端事件，所述第一事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告；
所述收发单元还用于从会话管理功能实体接收业务传输通知；
处理单元，用于当终端装置不可达时，根据所述第一事件信息，激活所述第一类的终端事件；
所述收发单元还用于当所述终端装置可达时，向订阅所述第一类的终端事件的应用功能实体发送终端事件报告。
可选地，所述第一事件信息还包括指示信息，所述指示信息用于指示所述第一类的终端事件。
可选地，所述收发单元还用于当所述终端装置切换通信系统后，从所述统一数据管理功能实体接收所述第一事件信息。
可选地，所述收发单元还用于当所述终端切换通信系统后，从第二移动管理实体接收一个或多个所述第二事件信息，所述第二事件信息中未包括所述指示信息；
所述收发单元还用于从所述统一数据管理功能实体接收所述第一事件信息；
所述处理单元还用于根据所述第一事件信息，删除所述一个或多个第二事件信息中的与所述第一类的终端事件所对应的第二事件信息。
可选地，所述处理单元还用于当所述终端切换通信系统过程中，根据所述第一事件信息得到第二事件信息，所述第二事件信息未包括所述指示信息；
所述收发单元还用于向第二移动管理实体发送所述第二事件信息。
可选地，所述指示信息包括数据网络名称和/或切片信息。
可选地，所述第一类的终端事件是增强的终端事件，或所述第一类的终端事件是非增强的终端事件。
在又一种可能的实现方式中，包括处理器和收发装置，所述处理器与所述收发装置耦 合，所述处理器用于执行计算机程序或指令，以控制所述收发装置进行信息的接收和发送；当所述处理器执行所述计算机程序或指令时，所述处理器还用于实现上述方法。其中，所述收发装置可以为收发器、收发电路或输入输出接口。当所述通信装置为芯片时，所述收发装置为收发电路或输入输出接口。
其中，所述处理器用于执行如下步骤：
控制所述收发装置从统一数据管理功能实体接收第一事件信息，所述第一事件信息用于指示第一类的终端事件，所述第一事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告；
控制所述收发装置从会话管理功能实体接收业务传输通知；
当终端装置不可达时，根据所述第一事件信息，激活所述第一类型的终端事件；
当所述终端装置可达时，控制所述收发装置向订阅所述第一类型的终端事件的应用功能实体发送终端事件报告。
可选地，所述第一事件信息还包括指示信息，所述指示信息用于指示所述第一类的终端事件。
可选地，所述处理器还执行如下步骤：当所述终端装置切换通信系统后，控制所述收发装置从所述统一数据管理功能实体接收所述第一事件信息。
可选地，所述处理器还执行如下步骤：当所述终端切换通信系统后，控制所述收发装置从第二移动管理实体接收一个或多个所述第二事件信息，所述第二事件信息中未包括所述指示信息；
控制所述收发装置从所述统一数据管理功能实体接收所述第一事件信息；
根据所述第一事件信息，删除所述一个或多个第二事件信息中的与所述第一类的终端事件所对应的第二事件信息。
可选地，所述处理器还执行如下步骤：当所述终端切换通信系统过程中，根据所述第一事件信息得到第二事件信息，所述第二事件信息未包括所述指示信息；
控制所述收发装置向第二移动管理实体发送所述第二事件信息。
可选地，所述指示信息包括数据网络名称和/或切片信息。
可选地，所述第一类的终端事件是增强的终端事件，或所述第一类的终端事件是非增强的终端事件。
当所述通信装置为芯片时，发送单元可以是输出单元，比如输出电路或者通信接口；接收单元可以是输入单元，比如输入电路或者通信接口。当所述通信装置为网络设备时，发送单元可以是发射器或发射机；接收单元可以是接收器或接收机。
第四方面，提供了一种通信装置，可以实现上述第二方面中的通信方法。例如所述通信装置可以是芯片或者设备，可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
在一种可能的实现方式中，所述通信装置的结构中包括处理器、存储器；所述处理器被配置为支持所述装置执行上述通信方法中相应的功能。存储器用于与处理器耦合，其保存所述装置必要的程序(指令)和数据。可选的，所述通信装置还可以包括通信接口用于支持所述装置与其他网元之间的通信。
在另一种可能的实现方式中，所述通信装置，可以包括执行上述方法中的相应动作的单元模块。
其中，所述装置包括：
收发单元，用于从控制功能实体接收第三事件信息，所述第三事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告，当所述终端事件为第一类的终端事件时，所述第三事件信息还包括业务描述信息；
处理单元，用于根据所述第三事件信息，得到第一事件信息，其中，所述第一事件信息用于指示第一类的终端事件或非第一类的终端事件，所述第一事件信息包括事件关联标识；
所述收发单元还用于当终端装置接入第一通信系统时，向第一移动管理功能实体发送所述第一事件信息，所述第一事件信息被用于激活所述第一类的终端事件。
可选地，所述第一事件信息还包括指示信息，所述指示信息用于指示所述第一类的终端事件。
可选地，所述收发单元还用于当所述终端装置切换至第二通信系统时，向第二移动管理功能实体发送第二事件信息，所述第二事件信息未包括所述指示信息，所述第二事件信息被用于激活所有终端事件。
可选地，当所述终端从所述第二通信系统切换至所述第一通信系统后，所述收发单元还用于向所述第一移动管理功能实体发送所述第一事件信息。
可选地，当所述终端从第一通信系统切换至所述第二通信系统后，所述收发单元还用于向所述第二移动管理功能实体发送所述第二事件信息。
在又一种可能的实现方式中，包括处理器和收发装置，所述处理器与所述收发装置耦合，所述处理器用于执行计算机程序或指令，以控制所述收发装置进行信息的接收和发送；当所述处理器执行所述计算机程序或指令时，所述处理器还用于实现上述方法。其中，所述收发装置可以为收发器、收发电路或输入输出接口。当所述通信装置为芯片时，所述收发装置为收发电路或输入输出接口。
其中，所述处理器用于执行如下步骤：
控制所述收发装置从控制功能实体接收第三事件信息，所述第三事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告，当所述终端事件为第一类的终端事件时，所述第三事件信息还包括业务描述信息；
根据所述第三事件信息，得到第一事件信息，其中，所述第一事件信息用于指示第一类的终端事件或非第一类的终端事件，所述第一事件信息包括所述事件关联标识；
当终端装置接入第一通信系统时，控制所述收发装置向第一移动管理功能实体发送所述第一事件信息，所述第一事件信息被用于激活所述第一类的终端事件。
可选地，所述第一事件信息还包括指示信息，所述指示信息用于指示所述第一类的终端事件。
可选地，所述处理器还执行如下步骤：当所述终端装置切换至第二通信系统时，控制 所述收发装置向第二移动管理功能实体发送第二事件信息，所述第二事件信息未包括所述指示信息，所述第二事件信息被用于激活所有终端事件。
可选地，所述处理器还执行如下步骤：当所述终端从所述第二通信系统切换至所述第一通信系统后，控制所述收发装置向所述第一移动管理功能实体发送所述第一事件信息。
可选地，所述处理器还执行如下步骤：当所述终端从第一通信系统切换至所述第二通信系统后，控制所述收发装置向所述第二移动管理功能实体发送所述第二事件信息。
当所述通信装置为芯片时，接收单元可以是输入单元，比如输入电路或者通信接口；发送单元可以是输出单元，比如输出电路或者通信接口。当所述通信装置为终端设备时，接收单元可以是接收器(也可以称为接收机)；发送单元可以是发射器(也可以称为发射机)。
第五方面，提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第六方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
图1为现有的EPS非漫游架构示意图；
图2为通过SCEF开放的3GPP EPS网络架构中接口的架构示意图；
图3为一种4G和5G互通的架构示意图；
图4a为5G的基于服务化接口的非漫游架构示意图；
图4b为5G的基于参考点的非漫游架构示意图；
图5为本申请实施例提供的一种通信方法的流程示意图；
图6为示例的一种配置事件信息的方法的流程示意图；
图7为对应于图6的后续的事件检测、激活和通知流程示意图；
图8为本申请实施例提供的另一种通信方法的流程示意图；
图9为示例的4G切换至5G的一种获取事件信息的流程示意图；
图10为示例的5G切换至4G的一种获取事件信息的流程示意图；
图11为本申请实施例提供的一种通信装置的模块结构示意图；
图12为本申请实施例提供的另一种通信装置的模块结构示意图；
图13为本申请实施例提供的一种通信装置的硬件结构示意图。
具体实施方式
下面结合本发明实施例中的附图对本发明实施例进行描述。
本申请的技术方案可以应用于如图1所示的EPS网络的非漫游架构中，还可以应用于EPS网络的漫游架构中；还可以应用于下一代网络的非漫游架构和漫游架构中，例如，如图4a所示的5G的基于服务化接口的非漫游架构中，以及如图4b所示的5G的基于参考点的非漫游架构中。
以图4a和图4b所示的5G的通信系统架构为例，该通信系统主要包括接入和移动性管理功能(access and mobility management function，AMF)实体、会话管理功能(Session  Management Function，SMF)实体、用户面功能(user plane function，UPF)实体、网络开放功能(network exposure function，NEF)实体、以及应用功能(application function，AF)实体。还可以包括策略控制功能(policy control function，PCF)实体、统一数据库功能(unified data repository，UDR)实体和统一数据管理(unified data management，UDM)功能实体。需要说明的是，图4a和图4b中包括的功能实体及功能实体的功能可以是相同的，而图4a中由于是基于服务化接口，一个功能实体发送给另一个功能实体的消息中需携带该另一个功能实体的标识；而图4b中由于是基于参考点，功能实体之间的消息是接口化消息，不需要携带功能实体的标识。
其中，图4a和图4b中的各功能实体的功能如下：
AMF实体：主要负责信令的处理，例如：接入控制、移动性管理、附着与去附着以及网关选择等功能。AMF实体为终端中的会话提供服务的情况下，会为该会话提供控制面的存储资源，以存储会话标识、与会话标识关联的SMF实体标识等。
SMF实体：主要负责会话管理，具体负责用户面功能实体的选择、用户面功能实体的重定向、因特网协议(internet protocol，IP)地址分配、承载的建立、修改和释放以及服务质量(quality of service，QoS)的控制。
UPF实体：负责终端中用户数据的转发和接收。可以从数据网络接收用户数据，通过接入网设备传输给终端；还可以通过接入网设备从终端接收用户数据，转发到数据网络。UPF实体中为终端提供服务的传输资源和调度功能是由SMF实体进行管理控制的。
NEF实体：主要支持3GPP网络和第三方应用进行安全的交互。NEF能够安全的向第三方应用开放网络能力和事件，用于加强或者改善应用服务质量，3GPP网络同样可以安全的从第三方应用获取相关数据，用以增强网络的智能决策；同时该功能实体支持从UDR恢复结构化数据或者向UDR中存储结构化数据。
AF实体：主要支持与3GPP网络交互来提供服务，例如影响数据路由决策，策略控制功能，或者向网络侧提供一些业务服务(这些服务可以是第三方(3 rd party)的，也可以不是第三方的)。
PCF实体：主要支持提供统一的策略框架来控制网络行为，提供策略规则给控制层网络功能，同时负责获取与策略决策相关的用户签约信息。
UDR实体：主要负责存储结构化数据，存储的内容包括签约数据和策略数据、对外暴露的结构化数据和应用相关的数据。
UDM实体：主要用于管理用户签约信息。
需要说明的是，以上功能实体仅是一个名字，名字本身对实体不构成限定。例如，该会话管理功能实体也有可能被替换为“会话管理功能”或其它名字。而且，该会话管理功能实体也可以对应一个包括除了会话管理功能外还有其他功能的实体。用户面功能实体也有可能被替换为“用户面功能”或其它名字，而且，该用户面功能实体也可以对应一个包括除了用户面功能外还有其他功能的实体。在此进行统一说明，以下不再赘述。
终端通过无线接入网(radio access network，RAN)设备或接入网(access network，AN)设备接入网络。RAN设备主要是3GPP网络中的无线网络设备，AN可以是non-3GPP定义的接入网设备。
在本申请中，终端可以为用户设备(user equipment，UE)、手持终端、笔记本电脑、用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、手提电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication，MTC)终端或是其他可以接入网络的设备。
终端可以与无线接入网(radio access network，RAN)设备之间采用某种空口技术相互通信。RAN设备主要负责空口侧的无线资源管理、QoS管理、数据压缩和加密等功能。所述接入网设备可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如，在5G系统中，称为gNB；在长期演进(long term evolution，LTE)系统中，称为演进的节点B(evolved NodeB，eNB或者eNodeB)；在第三代(3rd generation，3G)系统中，称为节点B(Node B)等。
AN设备允许终端和3GPP核心网之间采用非3GPP技术互连互通，其中，非3GPP技术例如：无线保真(wireless fidelity，Wi-Fi)、全球微波互联接入(worldwide interoperability for microwave Access，WiMAX)、码分多址(code division multiple access，CDMA)网络等。
在本申请中，终端处于不可用状态，是指网络为终端发起寻呼，但是没有收到响应，或者终端处于PSM模式，或者终端处于只允许MICO模式，等。其中，PSM模式是指允许终端减少能量损耗，不能立即可达来接收发送给终端的业务数据。MICO模式是指仅允许终端发起连接，当终端处于该模式，且终端处于空闲态时，网络认为终端不可达。
在本申请中，DDN失败可以是网络检测到终端处于不可用状态，或者触发DDN的数据的优先级(即分配和预留优先级(allocation and retention priority，ARP)，不高于之前触发DDN的数据的优先级。
在本申请中，终端事件可以是需要从网络获取各种类型的状态或信息的事件。例如，本申请的技术方案可以应用于高延迟通信的场景，终端事件可以是DDN失败后终端可用事件。提供该高延迟通信业务的应用功能实体能够通过订阅DDN失败后终端可用事件来支持对时延要求不高的业务通信。终端事件也可以是终端可达事件等。应用功能实体安装相关应用以提供对应的业务或服务。终端事件的订阅是指通过服务操作订阅事件通知或修改已经订阅的事件。
需要说明的是，本申请实施例中的术语“系统”和“网络”可被互换使用。“多个”是指两个或两个以上，鉴于此，本申请实施例中也可以将“多个”理解为“至少两个”。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，字符“/”，如无特殊说明，一般表示前后关联对象是一种“或”的关系。
本申请中，定义了两种类型的终端事件：增强的终端事件和非增强的终端事件。其中，增强的终端事件是指应用功能(application function，AF)实体向网络发送终端事件订阅请求时，该请求中包括业务描述信息；非增强的终端事件则是指AF向网络发送终端事件订阅请求时，该请求中未包括业务描述信息。则相应地，支持增强的终端事件的AF可以称 为增强的AF，不支持增强的终端事件的AF可以称为非增强的AF。
现有技术中，当增强的AF和非增强的AF都通过图3所示的互通架构订阅了终端事件时，现有的MME和AMF无法区分是增强的终端事件还是非增强的终端事件，无法执行对应的上报流程。UE在不同系统之间移动时，如何处理对应的事件未定义。
本申请实施例提供一种通信方法及装置，第一移动管理功能实体可以从统一数据管理功能实体接收事件信息，该事件信息用于指示第一类的终端事件，从而在终端装置可达时，第一移动管理功能实体可以根据该事件信息，向订阅该第一类的终端事件的应用功能实体发送终端事件报告，提高了发送终端事件报告的针对性。
图5为本申请实施例提供的一种通信方法的流程示意图，该方法可包括以下步骤：
S501、统一数据管理功能实体从控制功能实体接收第三事件信息。
应用功能实体向控制功能实体进行事件订阅。控制功能实体例如可以是NEF或者SCEF。事件订阅消息中包括GPSI/external group ID，AF ID，事件类型(event type)。事件类型例如为DDN失败后终端可用事件(availability after DDN failure)等。在本实施例中，当应用功能实体是增强的应用功能实体，或者当所述终端事件为第一类的终端事件时，则事件订阅消息中还包括DNN/NSSAI和业务描述信息(traffic descriptor)。当应用功能实体是非增强的应用功能实体或者其他类型的终端事件时，则事件订阅消息中未包括业务描述信息。
控制功能实体向UDM或者HSS发送第三事件信息。控制功能实体(如NEF或者SCEF或者NEF+SCEF)根据上述事件订阅消息，生成对应的事件关联标识。其中，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告。即控制功能实体根据接收到的终端事件上报消息中的事件关联标识，确定目标功能实体的地址。事件关联标识也可表示为Reference ID，事件关联标识可通过用于关联终端事件和终端事件上下文，来使得可以通过该关联标识确定终端事件的上下文信息；此外，可选的，事件关联标识还可以用于关联终端事件、应用功能网元的订阅请求以及终端事件的上下文信息。在另一种实施方式中，所述事件关联标识用于标识所述终端事件报告，该关联标识可包含在终端事件报告中，该报告还可包含终端事件类型，通过标识终端事件报告，可确定该报告所对应的终端事件，进一步标识终端事件的上下文，进一步确定。事件关联标识用于标识终端事件的上下文信息，在后续的业务传输过程中，各功能实体可根据该终端事件的上下文信息确定是否激活终端事件以及上报终端事件报告。事件关联标识用于标识终端事件报告，移动管理功能实体可以根据该事件关联标识确定是否向订阅该终端事件的应用功能实体上报终端事件报告。
第三事件信息包括UE标识或者群组标识，AF ID，事件类型。在本实施例中，当应用功能实体是增强的应用功能实体时，则事件订阅消息中还包括DNN/NSSAI和业务描述信息，对应的，第三事件信息还包括DNN/NSSA1和业务描述信息。当应用功能实体是非增强的应用功能实体时，则事件订阅消息中未包括业务描述信息。
S502、所述统一数据管理功能实体根据所述第三事件信息，得到第一事件信息。
UDM根据第三事件信息中包括的业务描述信息，可以确定该终端事件是第一类的终端事件或非第一类的终端事件，从而可以根据第三事件信息，得到第一事件信息。其中，所 述第一事件信息用于指示第一类的终端事件或非第一类的终端事件。即根据第三事件信息，得到第一事件信息，是根据第三事件信息中包括的业务描述信息转换而得到第一事件信息的。可选的，第一事件信息可以包括指示信息，该指示信息用于指示第一类的终端事件。第一类的终端事件没有特殊的定义，第一类的终端事件与非第一类的终端事件的区别在于，第一类的终端事件可以是增强的AF订阅的终端事件，非第一类的终端事件是非增强的AF订阅的终端事件；或者反之也可以，第一类的终端事件是非增强的AF订阅的终端事件，非第一类的终端事件是增强的AF订阅的终端事件。即通过终端事件的类型可以区分是增强的AF或非增强的AF订阅的终端事件。本实施例以第一事件信息用于指示第一类的终端事件为例进行描述。
第一事件信息包括事件关联标识，还可包括事件类型和NEF+SCEF ID。由于事件关联标识用于标识终端事件的上下文信息，则网络根据事件关联标识，可以了解该终端事件是第一类的终端事件或非第一类的终端事件。
S503、当终端装置接入第一通信系统时，所述统一数据管理功能实体向第一移动管理功能实体发送所述第一事件信息。
该第一通信系统例如可以是5G系统。
其中，所述第一事件信息被用于激活所述第一类的终端事件。
相应地，第一移动管理实体从统一数据管理功能实体接收第一事件信息，所述第一事件信息用于指示第一类的终端事件，所述第一事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告。
S504、所述第一移动管理实体从会话管理功能实体接收业务传输通知。
该业务传输通知用于通知第一移动管理实体从订阅第一类的终端事件的应用功能实体接收到下行数据通知。
S505、当终端装置不可达时，所述第一移动管理功能实体根据所述第一事件信息，激活所述第一类的终端事件。
第一移动管理功能实体在接收到上述业务传输通知后，检测终端装置是否可达。当终端装置不可达时，第一移动管理功能实体根据所述第一事件信息，激活所述第一类的终端事件。
S506、当所述终端装置可达时，所述第一移动管理功能实体向订阅所述第一类的终端事件的应用功能实体发送终端事件报告。
当第一移动管理功能实体检测到终端装置可达时，向订阅该第一类的终端事件的应用功能实体发送终端事件报告，而不是向所有发送订阅消息的应用功能实体发送终端事件报告。
S507、当所述终端装置切换至第二通信系统时，所述统一数据管理功能实体向第二移动管理功能实体发送第二事件信息，所述第二事件信息未包括所述指示信息。
该第二通信系统例如是4G通信系统，或者5G以下的任一代通信系统。UDM向第二移动管理功能实体发送第二事件信息，该第二事件信息未指示该终端事件是第一类的终端事件，或者未包括上述指示信息。
S508、当终端装置不可达时，所述第二移动管理功能实体接收所述会话管理功能实体发送的业务传输通知时，激活所有终端事件。
由于第二事件信息未对终端事件是否是第一类的终端事件进行指示，则第二移动管理功能实体在接收到一个或多个应用功能实体的业务传输通知时，并且检测到终端装置不可达时，激活所有被订阅的终端事件。
S509、当所述终端装置可达时，所述第二移动管理功能实体向所有订阅所述终端事件的应用功能实体发送终端事件报告信息。
由于第二事件信息未对终端事件是否是第一类的终端事件进行指示，则第二移动管理功能实体在检测到终端装置可达时，向所有订阅所述终端事件的应用功能实体发送终端事件报告信息。
根据本申请实施例提供的一种通信方法，第一移动管理功能实体可以从统一数据管理功能实体接收事件信息，该事件信息用于指示第一类的终端事件，从而在终端装置可达时，第一移动管理功能实体可以根据该事件信息，向订阅该第一类的终端事件的应用功能实体发送终端事件报告，提高了发送终端事件报告的针对性。
下面分别从配置事件信息和进行事件检测的流程对图5所示的实施例的进行示例性的详细描述：
如图6所示的示例的一种配置事件信息的方法的流程示意图，该方法包括以下步骤：
S601a～S601c、不同的AF(AF1，AF2和AF3)通过NEF+SCEF/NEF向UDM+HSS/UDM发起事件订阅。其中，AF1为增强的AF，AF2和AF3为非增强的AF。AF1向NEF+SCEF/NEF发送事件订阅时，包含{DNN/NSSAI,业务描述信息(traffic descriptor),事件类型(event type，例如为DDN失败后终端可用事件)，UE标识或者群组标识(GPSI/external group ID)，应用标识(AF ID)}。AF2和AF3向NEF+SCEF/NEF发送事件订阅时，包含{事件类型，UE标识或者群组标识，应用标识}。这里，NEF+SCEF是指NEF和SCEF共同负责事件的订阅，UDM+HSS是指UDM和HSS共同负责接收事件的订阅。
S602a～S602c、NEF+SCEF/NEF根据接收到的事件，向UDM+HSS/UDM发送第三事件信息。具体的，对于AF1，NEF+SCEF/NEF发送{DNN/NSSAI,业务描述信息,事件类型，UE标识或者群组标识，NEF+SCEF/NEF ID，reference ID1}；对于AF2，NEF+SCEF/NEF发送{UE标识或者群组标识，事件类型，NEF+SCEF/NEF ID，reference ID2}；对于AF3，NEF+SCEF/NEF发送{UE标识或者群组标识，事件类型，NEF+SCEF/NEF ID，reference ID2}。reference ID为事件关联标识。其中，reference ID1用于关联AF1所订阅的终端事件，例如这是第一类的终端事件；reference ID2用于关联AF2和AF3所订阅的终端事件，例如这是其它类型的终端事件。
S603、UDM+HSS/UDM根据接收到的第三事件信息和UE接入的网络类型，向MME或者AMF提供事件信息。
具体的提供时机包括：1)在UE执行注册流程或者附着流程的过程中向AMF或MME提供事件信息；2)在UE已经注册到网络后的任意时间，UDM+HSS/UDM接收到订阅事件，向AMF或MME提供事件信息。
具体的提供信息，对于增强的事件，当UE通过AMF接入时，UDM+HSS/UDM提供 包含指示信息的事件信息。或者可选的，对于非增强的事件，当UE通过AMF接入时，UDM+HSS/UDM提供包含指示信息的事件信息。当UE通过MME接入时，UDM+HSS/UDM总是提供现有的事件信息。或者可选的，对于增强的事件，当UE通过AMF接入时，UDM+HSS/UDM提供包含指示信息1的事件信息，对于非增强的事件，当UE通过AMF接入时，UDM+HSS/UDM提供包含指示信息2的事件信息。
S604a、在UE执行附着流程的过程中，对MME不做修改，UDM+HSS/UDM向MME提供第二事件信息。具体地，UDM+HSS/UDM向MME提供的事件信息为{Event type,Reference ID1,NEF+SCEF ID}、{Event type,Reference ID2,NEF+SCEF ID}、{Event type,Reference ID2,NEF+SCEF ID}。
S604b、在UE执行注册流程的过程中，UDM+HSS/UDM向AMF提供第一事件信息。具体地，向AMF提供的事件信息为{Event type,Reference ID1,NEF+SCEF ID，Indication}、{Event type,Reference ID2,NEF+SCEF ID}、{Event type,Reference ID3,NEF+SCEF ID}或者{Event type,Reference ID1,NEF+SCEF ID}、{Event type,Reference ID2,NEF+SCEF ID，Indication}、{Event type,Reference ID3,NEF+SCEF ID，Indication}。
在该实施例中，UDM+HSS/UDM根据发起订阅的AF的不同，以及根据UE接入通信系统的不同，例如，在接入5G通信系统时，向AMF提供第一事件信息，该第一事件信息用于指示第一类的终端事件；例如，在接入4G通信系统时，向MME提供第二事件信息，该第二事件信息未用于指示第一类的终端事件。
进一步地，UDM+HSS/UDM向SMF提供事件检测信息，以便SMF通知UPF检测业务信息，从而确定在UE不可达时特定的业务发生。对应于图6，其后续的事件检测、激活和通知流程如图7所示，该方法包括以下步骤：
S701、UDM+HSS确定向SMF传输事件信息。
S702、UDM+HSS向SMF发送事件订阅信息。
其中，该事件订阅信息包括：事件类型，业务描述信息、NEF+SCEF标识(NEF+SCEF ID)和事件关联标识(NEF reference ID)。
S703、SMF与UPF进行N4会话建立/修改。
在会话建立过程中或者会话建立之后，UDM+HSS/UDM向SMF提供事件的业务信息，以便SMF向UPF发送业务信息。该业务信息包括包过滤器(packet filter，PDR)或者第一指示信息。该第一指示信息用于指示检测到该终端事件对应的业务数据时，通知SMF。
S704a、AF1向UE发送下行数据包，UPF接收AF1发送的下行数据包。
S704b、AF2向UE发送下行数据包，UPF接收AF2发送的下行数据包。
S705a、当UPF接收AF1发送的下行数据包时，且确定下行隧道不可用，UPF向SMF发送数据通知(data notification，DN)，该数据通知中包括第二指示信息。该第二指示信息用于指示检测到AF1发送的下行数据包。
SMF根据该第二指示信息，可以确定是AF1发送的下行数据包。该第二指示信息包括数据网络名称或切片信息。
S705b、当UPF接收AF2发送的下行数据包时，且确定下行隧道不可用，UPF向SMF发送数据通知，该数据通知不包括上述第二指示信息。
由于数据通知中不包括上述第二指示信息，SMF不能确定是AF2或AF3发送的下行数据包。
S706a、SMF向AMF发送Namf_communication_N1N2MessageTransfer消息，该消息中包括NEF reference ID1。
由于SMF确定了是AF1发送的下行数据包，则在该消息中包括该终端事件对应的NEF reference ID1。NEF reference ID用于唯一标识所订阅的终端事件。
S706b、SMF向AMF发送Namf_communication_N1N2MessageTransfer消息，该消息中不包括NEF reference ID。
由于SMF不能确定是AF2或AF3发送的下行数据包，则在该消息中不包括该终端事件对应的NEF reference ID。
S707、AMF向SMF发送Nsmf_communication_N1N2MessageTransfer消息。
S708、SMF向UPF发送失败指示。
S709a、AMF确定UE不可达时，激活AF1订阅的DDN失败上报UE可用事件。
AMF接收到SMF发送的Namf_communication_N1N2MessageTransfer消息后，由于该消息中包括NEF reference ID1，AMF激活该NEF reference ID1所关联的终端事件。
S709b、AMF确定UE不可达时，激活AF2和AF3订阅的DDN失败上报UE可用事件。
AMF接收到SMF发送的Namf_communication_N1N2MessageTransfer消息后，由于该消息中未包括NEF reference ID，则AMF不能区分发送下行数据包的是AF2还是AF3，则均激活AF2和AF3订阅的终端事件。
S710、UE连接到网络。
S711a、AMF根据激活的事件向NEF+SCEF/NEF发送事件上报，该事件上报包括UE可用通知和NEF reference ID1。
AMF在检测到UE连接到网络后，并且监测到激活了AF1订阅的终端事件，则向NEF+SCEF/NEF进行事件上报，且在事件上报中包括NEF reference ID1。
S711b、AMF根据激活的事件向NEF+SCEF/NEF发送事件上报，该事件上报包括UE可用通知、NEF reference ID2和NEF reference ID3。
AMF在检测到UE连接到网络后，并且监测到激活了AF2和AF3订阅的终端事件，则向NEF+SCEF/NEF进行事件上报，且在事件上报中包括NEF reference ID2和NEF reference ID3。
S712a、NEF+SCEF/NEF向AF1发送订阅事件通知，该订阅事件通知用于通知UE可用。
NEF+SCEF/NEF在接收到事件上报后，根据事件上报中包括的NEF reference ID1，向AF1发送订阅事件通知。
S712b、NEF+SCEF/NEF向AF2和AF3发送订阅事件通知，该订阅事件通知用于通知UE可用。
NEF+SCEF/NEF在接收到事件上报后，根据事件上报中包括的NEF reference ID2和NEF reference ID3，分别向AF2和AF3发送订阅事件通知。
由此可见，由于AF2和AF3不是增强的AF，使得网络在进行订阅事件激活和通知时，不能区分是AF2或AF3发送的下行数据，从而在UE可用时，向AF2和AF3都发送了事件通知。
在该实施例中，AMF在接收到订阅第一类的终端事件的AF发送的下行数据时，并且在UE不可用时，可以根据第一事件信息，激活该终端事件，以及在UE可用时，只向该AF发送终端事件报告；而对于其它的AF发送的下行数据时，不能区分是其中哪一个AF发送的下行数据，从而在UE可用时，向所有AF发送终端事件报告。
UE可以在不同制式的通信系统之间切换，例如由5G通信系统切换至4G通信系统，或者由4G通信系统切换至5G通信系统，切换后的通信系统中的移动管理功能实体可能没有存储上述事件信息，移动管理功能实体如何在UE切换过程中，获取对应的事件信息，下面的实施例提供相应的解决方案。
图8为本申请实施例提供的另一种通信方法的流程示意图，该方法可包括以下步骤：
S801、当终端装置切换至第一通信系统后，统一数据管理功能实体向第一移动管理功能实体发送第一事件信息。
终端装置在切换前处于第二通信系统，例如可以是4G系统。终端装置由第二通信系统切换至第一通信系统。该第一通信系统例如可以是5G系统。UDM根据接入的网络为第一通信系统，UDM向第一移动管理功能实体发送第一事件信息。第一移动管理功能实体总是使用UDM提供的第一事件信息。可选地，第一事件信息用于指示第一类的终端事件，即根据第一事件信息中包括的内容可以确定该第一事件信息对应的是第一类的终端事件。可选地，第一事件信息也包括指示信息，所述指示信息用于指示第一类的终端事件，通过明确的指示信息指示该第一事件信息对应的为第一类的终端事件，换句话说，这第一事件信息描述的是第一类的终端事件的信息。
可选地，在切换过程中，第二通信系统中的第二移动管理功能实体也可以向第一移动管理功能实体提供第二事件信息，该第二事件信息未包括上述指示信息，即不能指示第二事件信息对应的是哪一类的终端事件。第一移动管理功能实体在接收到UDM发送的第一事件信息后，根据UDM提供的信息更新本地事件信息，删除从第二移动管理功能实体接收到的第二事件信息中与第一类的终端事件所对应的第二事件信息。第二移动功能功能实体提供的第二事件信息包括第一类的终端事件对应的事件信息，也包括其它类的终端事件对应的事件信息，而其它类的终端事件对应的事件信息不需要进行指示，因此，可以根据UDM提供的信息更新本地事件信息，删除从第二移动管理功能实体接收到的第二事件信息中与第一类的终端事件所对应的第二事件信息。
S802、当所述终端装置切换至第二通信系统后，所述第一移动管理功能实体根据所述第一事件信息得到第二事件信息。
终端装置由第一通信系统切换至第二通信系统后，第一移动管理功能实体给第二移动管理功能实体提供的第二事件信息未包括上述指示信息，因此，第一移动管理实体首先根据第一事件信息得到第二事件信息，换句话说，将第一事件信息映射为第二事件信息，即映射为不包括指示信息的事件信息。
仍以上面的示例为例，如将事件信息{Event type,Reference ID1,NEF+SCEF ID， Indication}、{Event type,Reference ID2,NEF+SCEF ID}、{Event type,Reference ID3,NEF+SCEF ID}或者{Event type,Reference ID1,NEF+SCEF ID}、{Event type,Reference ID2,NEF+SCEF ID，Indication}、{Event type,Reference ID3,NEF+SCEF ID，Indication}；映射为{Event type,Reference ID1,NEF+SCEF ID}、{Event type,Reference ID2,NEF+SCEF ID}、{Event type,Reference ID2,NEF+SCEF ID}。
S803、所述第一移动管理功能实体向第二移动管理功能实体发送所述第二事件信息。
根据本申请实施例提供的一种通信方法，在不同的通信系统之间切换时，例如，从4G切换到5G系统时，移动管理功能实体可以向统一数据管理功能实体获取第一事件信息，或者移动管理功能实体从切换前的通信系统中的移动管理功能实体获取一个或多个第二事件信息，以及从同一数据管理功能实体接收第一事件信息，并删除一个或多个第二事件信息中与第一类的终端事件所对应的第二事件信息，从而使得移动性管理功能实体可以及时获得事件信息，并根据该事件信息激活终端事件，并在终端装置可达时，及时向订阅该终端事件的应用功能实体发送终端事件报告；例如，从5G切换到4G系统时，切换前的通信系统中的移动管理功能实体可以根据第一事件信息得到第二事件信息，并向切换后的通信系统中的移动管理功能实体发送第二事件信息，以适用未做改变的移动管理功能实体。
针对图8所示的切换通信系统后，下面分别通过图9和图10描述从4G切换至5G、5G切换至4G，切换后的通信系统中的移动管理实体获取事件信息的方法。
图9为示例的4G切换至5G的一种获取事件信息的流程示意图。在4G系统中，移动管理功能实体可以是MME，在5G系统中，移动管理功能实体可以是AMF。UE从4G切换到5G的过程中，MME向AMF发送获取到的事件信息，MME不需要增强。
切换执行过程，具体的流程如下：
S901、MME向E-UTRAN发送切换命令(handover command)。
其中，E-UTRAN是4G系统中的接入网设备。该切换命令用于指示切换到5G系统。
S902、E-UTRAN向UE发送切换命令(handover from E-UTRAN command)。
S903、UE向5G NG-RAN发送切换确定响应消息(handover to 5G-RAN confirm)。
其中，5G NG-RAN是5G系统中的接入网设备。
S904、NG-RAN向AMF发送切换通知(handover notify)。
S905、AMF向MME发送重定位完成通知(forward relocation complete notification)。
S906、MME向AMF发送重定位完成通知确定响应消息(forward relocation complete notification ack)。
在切换准备阶段，MME向AMF发送存储的的事件信息，MME不需要增强。
S907、AMF向SMF+PGW-C发送会话更新会话管理上下文请求(Nsmf_PDUSession_UpdateSMContext Request)。
可选地，漫游场景下通过V-SMF执行该过程。
S908、SMF+PWG-C与UPF+PGW-U进行N4会话修改流程(N4session modification)。
进一步的，在切换执行阶段，如S907，SMF+PGW-C在接收到AMF的请求后，SMF+PGW-C向HSS+UDM发起注册流程。此时，HSS+UDM根据本地的事件信息向SMF+UDM提供业务检测信息{NEF+SCEF ID/NEF ID,reference ID,业务信息}。SMF在S908 中向UPF发送业务信息以便UPF上报SMF特定事件发生。
S909、SMF+PWG-C与PCF之间执行SM策略关联修改流程(SMF initiated SM policy association modification)。
该步骤为可选的步骤。
S910、SMF+PWG-C向AMF发送会话更新会话管理上下文响应(Nsmf_PDUSession_UpdateSMContext)。
可选地，漫游场景下通过V-SMF执行该过程。
S911、漫游场景下，V-SMF与V-UPF之间执行N4会话修改(N4session modification)流程。
S912、UE向网络发起移动注册流程(EPS to 5GS mobility registration procedure)。
在切换执行阶段的S912，UE执行移动的注册流程。在执行移动的注册流程中，HSS+UDM根据接入的网络为5G，向AMF提供对应的事件信息。AMF总是使用HSS+UDM提供的事件信息。具体的，根据HSS+UDM提供的信息更新本地事件信息，删除从MME接收到的事件信息中与第一类的终端事件对应的事件信息。有关事件信息的描述可参考图5所示实施例。
仍以上面的示例为例，在该流程中，AMF从UDM获取事件信息{Event type,Reference ID1,NEF+SCEF ID，Indication}、{Event type,Reference ID2,NEF+SCEF ID}、{Event type,Reference ID3,NEF+SCEF ID}或者{Event type,Reference ID1,NEF+SCEF ID}、{Event type,Reference ID2,NEF+SCEF ID，Indication}、{Event type,Reference ID3,NEF+SCEF ID，Indication}。
S913、MME执行释放EPC中的资源(resource clean up in EPC by MME)。
在该实施例中，从4G切换到5G系统时，移动管理功能实体可以向统一数据管理功能实体获取第一事件信息，或者移动管理功能实体从切换前的通信系统中的移动管理功能实体获取一个或多个第二事件信息，以及从同一数据管理功能实体接收第一事件信息，并删除一个或多个第二事件信息中与第一类的终端事件所对应的第二事件信息，从而使得移动性管理功能实体可以及时获得事件信息，并根据该事件信息激活终端事件，并在终端装置可达时，及时向订阅该终端事件的应用功能实体发送终端事件报告。
图10为示例的5G切换至4G的一种获取事件信息的流程示意图。具体的流程如下：
S1001、NG-RAN向AMF发送切换请求(handover request)。
S1002a、AMF向PGW-C+SMF发送会话上下文请求(Nsmf_PDUSession_Context Request)。
S1002b、PGW-C+SMF与PGW-U+UPF执行N4会话修改(N4 session modification)。
S1002c、PGW-C+SMF向AMF发送会话上下文响应(Nsmf_PDUSession_Context Response)。
可选地，漫游场景，AMF通过V-SMF与H-SMF执行该流程。
S1003、AMF将事件映射为MME使用的事件，并包含在重定向请求(relocation request)中发送给MME。
AMF执行事件的映射，即根据将事件映射为MME可以识别的事件信息，即不包含指 示的事件信息。AMF在接收到NG-RAN的切换请求后，执行事件的映射。如将事件信息{Event type,Reference ID1,NEF+SCEF ID，Indication}、{Event type,Reference ID2,NEF+SCEF ID}、{Event type,Reference ID3,NEF+SCEF ID}或者{Event type,Reference ID1,NEF+SCEF ID}、{Event type,Reference ID2,NEF+SCEF ID，Indication}、{Event type,Reference ID3,NEF+SCEF ID，Indication}；映射为{Event type,Reference ID1,NEF+SCEF ID}、{Event type,Reference ID2,NEF+SCEF ID}、{Event type,Reference ID2,NEF+SCEF ID}。
此为MME获取事件信息的可选方式一。
S1004、MME向SGW发送创建会话请求(create session request)。
S1005、SGW向MME发送创建会话响应(create session response)。
S1006、MME向E-UTRAN发送切换请求(handover request)。
S1007、E-UTRAN向MME发送切换请求响应(handover request ack)。
S1008、MME与SGW执行创建间接数据转发隧道流程(create omdorect data forwarding tunnel request/response)。
该步骤为可选的步骤。
S1009、MME向AMF发送重定向响应(relocation response)。
S1010a～S1010c、AMF与PGW-C+SMF之间执行PDU更新会话管理上下文(Nsmf_PDU_UpdateSMContext)流程。
该步骤为可选的步骤。
S1011a、AMF向NG-RAN发送切换命令(handover command)。
S1011b、NG-RAN向UE发送切换命令。
S1012a、UE向NG-RAN发送切换完成(handover complete)。
S1012b、NG-RAN向MME发送切换通知(handover notify)。
S1012c～S1012d、MME与AMF之间执行重定向完成通知(relocation complete notification)。
S1013、MME向SGW发送修改承载请求(modify bearer request)。
S1014、SGW向PGW-C+SMF发送修改请求承载请求。
S1015、PGW-C+SMF与UPF之间执行N4会话修改(N4session modification)流程。
S1016、PGW-C+SMF向SGW发送修改承载响应(modify bearer response)。
S1017、SGW向MME发送修改承载响应。
S1018、UE与EPC网络执行位置区更新流程(TAU procedure)。
可选的，在该流程中MME从HSS+UDM获取事件信息。
在切换过程的TAU过程中，HSS+UDM根据接入的网络为4G向MME提供对应的事件信息，MME总是使用HSS+UDM的事件信息。具体的，根据HSS+UDM提供的信息更新本地事件信息，或者删除从MME接收到的事件信息。该事件信息的描述请参考图5所示实施例。
此为MME获取事件信息的可选方式二。
S1019、PGW-C+SMF发起与SGW，MME和UE之间的专有承载激活流程(PGW initiated  dedicated bearer activation)。
S1020、SGW与MME之间执行删除间接数据转发隧道流程(delete indirect data forwarding tunnel request/response)。
S1021a、AMF与PGW-C+SMF之间执行删除间接数据转发隧道流程。
可选地，漫游场景中通过V-SMF执行该过程。
S1021b、修改N4会话。
在该实施例中，从5G切换到4G系统时，切换前的通信系统中的移动管理功能实体可以根据第一事件信息得到第二事件信息，并向切换后的通信系统中的移动管理功能实体发送第二事件信息，以适用未做改变的移动管理功能实体。
下面介绍本申请实施例提供的一种装置1100。如图11所示：
装置1100包括收发单元111和处理单元112，收发单元111和处理单元112相连。
收发单元111用于从统一数据管理功能实体接收第一事件信息，所述第一事件信息用于指示第一类的终端事件，所述第一事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告；
所述收发单元111还用于从会话管理功能实体接收业务传输通知；
处理单元112，用于当终端装置不可达时，根据所述第一事件信息，激活所述第一类的终端事件；
所述收发单元111还用于当所述终端装置可达时，向订阅所述第一类的终端事件的应用功能实体发送终端事件报告。
可选的，所述收发单元111还用于当所述终端装置切换通信系统后，从所述统一数据管理功能实体接收所述第一事件信息。
可选的，所述收发单元111还用于当所述终端切换通信系统后，从第二移动管理实体接收一个或多个所述第二事件信息，所述第二事件信息中未包括所述指示信息；
所述收发单元111还用于从所述统一数据管理功能实体接收所述第一事件信息；
所述处理单元112还用于根据所述第一事件信息，删除所述一个或多个第二事件信息中的与所述第一类的终端事件所对应的第二事件信息。
可选的，所述处理单元112还用于当所述终端切换通信系统后，根据所述第一事件信息得到第二事件信息，所述第二事件信息未包括所述指示信息；
所述收发单元111还用于向第二移动管理实体发送所述第二事件信息。
装置1100可以是网络装置，例如可以是第一移动管理功能实体或者第一移动管理功能实体内的芯片。装置1100可以通过收发单元111和处理单元112实现本申请实施例中第一移动管理功能实体的其他功能，具体可以参考图5和图8所示实施例中的相关内容。
下面介绍本申请实施例提供的一种装置1200。如图12所示：
装置1200包括收发单元121和处理单元122，收发单元121和处理单元122相连。
收发单元121，用于从控制功能实体接收第三事件信息，所述第三事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告，当所述终端事件为第一类的终端事件时，所述第三事件信息还包括业务描述信息；
处理单元122，用于根据所述第三事件信息，得到第一事件信息，其中，所述第一事件信息用于指示第一类的终端事件或非第一类的终端事件，所述第一事件信息包括所述事件关联标识；
所述收发单元121还用于当终端装置接入第一通信系统时，向第一移动管理功能实体发送所述第一事件信息，所述第一事件信息被用于激活所述第一类的终端事件。
在一个实现方式中，所述第一事件信息还包括指示信息，所述指示信息用于指示所述第一类的终端事件。
在另一个实现方式中，所述收发单元121还用于当所述终端装置切换至第二通信系统时，向第二移动管理功能实体发送第二事件信息，所述第二事件信息未包括所述指示信息，所述第二事件信息被用于激活所有终端事件。
所述收发单元121还用于当所述终端从所述第二通信系统切换至所述第一通信系统后，向所述第一移动管理功能实体发送所述第一事件信息。
所述收发单元121还用于当所述终端从第一通信系统切换至所述第二通信系统后，向所述第二移动管理功能实体发送所述第二事件信息。
装置1200可以是网络装置，例如可以是统一数据管理功能实体或统一数据管理功能实体中的芯片。具体可以可以参考图5和图8所示实施例的相关内容，在此不再赘述。
下面介绍本申请实施例提供的一种装置。如图13所示：
该装置包括处理器131和收发装置132。可选的，该装置还包括存储器133。处理器131、收发装置132和存储器133通过通信总线相连。
收发装置132可以是具有收发功能的装置，用于与其他网络设备或者通信网络进行通信。收发装置可以是独立的发送单元和接收单元，也可以是一个整体的收发装置。收发装置又可以称为通信单元。
存储器133可以包括一个或者多个存储器，存储器可以是一个或者多个设备、电路中用于存储程序或者数据的器件。
存储器133可以独立存在，通过通信总线与处理器131相连。存储器也可以与处理器131集成在一起。
装置1300可以用于网络设备、电路、硬件组件或者芯片中。
在一个实施例中，装置1300可以是本申请实施例中的第一移动管理功能实体或者第一移动管理功能实体中的芯片。当装置1300是本申请实施例中的终端或者终端中的芯片第一移动管理功能实体或者第一移动管理功能实体中的芯片时，装置1300可以实现上述图5和图8所示实施例中第一移动管理功能实体执行的方法。
具体地，所述处理器用于执行如下步骤：
控制所述收发装置从统一数据管理功能实体接收第一事件信息，所述第一事件信息用于指示第一类的终端事件，所述第一事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告；
控制所述收发装置从会话管理功能实体接收业务传输通知；
当终端装置不可达时，根据所述第一事件信息，激活所述第一类型的终端事件；
当所述终端装置可达时，控制所述收发装置向订阅所述第一类型的终端事件的应用功 能实体发送终端事件报告。
可选地，所述第一事件信息还包括指示信息，所述指示信息用于指示所述第一类的终端事件。
可选地，所述处理器还执行如下步骤：当所述终端装置切换通信系统后，控制所述收发装置从所述统一数据管理功能实体接收所述第一事件信息。
可选地，所述处理器还执行如下步骤：当所述终端切换通信系统后，控制所述收发装置从第二移动管理实体接收一个或多个所述第二事件信息，所述第二事件信息中未包括所述指示信息；
控制所述收发装置从所述统一数据管理功能实体接收所述第一事件信息；
根据所述第一事件信息，删除所述一个或多个第二事件信息中的与所述第一类的终端事件所对应的第二事件信息。
可选地，所述处理器还执行如下步骤：当所述终端切换通信系统过程中，根据所述第一事件信息得到第二事件信息，所述第二事件信息未包括所述指示信息；
控制所述收发装置向第二移动管理实体发送所述第二事件信息。
可选地，所述指示信息包括数据网络名称和/或切片信息。
可选地，所述第一类的终端事件是增强的终端事件，或所述第一类的终端事件是非增强的终端事件。
在另一个实施例中，装置1300可以是本申请实施例中的统一数据管理功能实体或者统一数据管理功能实体中的芯片。当装置1300是本申请实施例中的终端或者终端中的芯片统一数据管理功能实体或者统一数据管理功能实体中的芯片时，装置1300可以实现上述图5和图8所示实施例中统一数据管理功能实体执行的方法。
具体地，所述处理器用于执行如下步骤：
控制所述收发装置从控制功能实体接收第三事件信息，所述第三事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告，当所述终端事件为第一类的终端事件时，所述第三事件信息还包括业务描述信息；
根据所述第三事件信息，得到第一事件信息，其中，所述第一事件信息用于指示第一类的终端事件或非第一类的终端事件，所述第一事件信息包括所述事件关联标识；
当终端装置接入第一通信系统时，控制所述收发装置向第一移动管理功能实体发送所述第一事件信息，所述第一事件信息被用于激活所述第一类的终端事件。
可选地，所述第一事件信息还包括指示信息，所述指示信息用于指示所述第一类的终端事件。
可选地，所述处理器还执行如下步骤：当所述终端装置切换至第二通信系统时，控制所述收发装置向第二移动管理功能实体发送第二事件信息，所述第二事件信息未包括所述指示信息，所述第二事件信息被用于激活所有终端事件。
可选地，所述处理器还执行如下步骤：当所述终端从所述第二通信系统切换至所述第一通信系统后，控制所述收发装置向所述第一移动管理功能实体发送所述第一事件信息。
可选地，所述处理器还执行如下步骤：当所述终端从第一通信系统切换至所述第二通 信系统后，控制所述收发装置向所述第二移动管理功能实体发送所述第二事件信息。
本申请实施例还提供了一种计算机可读存储介质。上述实施例中描述的方法可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。如果在软件中实现，则功能可以作为一个或多个指令或代码存储在计算机可读介质上或者在计算机可读介质上传输。计算机可读介质可以包括计算机存储介质和通信介质，还可以包括任何可以将计算机程序从一个地方传送到另一个地方的介质。存储介质可以是可由计算机访问的任何可用介质。
作为一种可选的设计，计算机可读介质可以包括随机存储存储器(random access memory，RAM)，只读存储器(read-only memory，ROM)，带电可擦可编程读写存储器(electrically erasable programmable read only memory，EEPROM)，只读光盘(compact disc read-only memory，CD-ROM)或其它光盘存储器，磁盘存储器或其它磁存储设备，或可用于承载的任何其它介质或以指令或数据结构的形式存储所需的程序代码，并且可由计算机访问。而且，任何连接被适当地称为计算机可读介质。例如，如果使用同轴电缆，光纤电缆，双绞线，数字用户线(digital subscriber line，DSL)或无线技术(如红外，无线电和微波)从网站，服务器或其它远程源传输软件，则同轴电缆，光纤电缆，双绞线，DSL或诸如红外，无线电和微波之类的无线技术包括在介质的定义中。如本文所使用的磁盘和光盘包括光盘(compact disc，CD)，激光盘，光盘，数字通用光盘(digital versatile disc，DVD)，软盘和蓝光盘，其中磁盘通常以磁性方式再现数据，而光盘利用激光光学地再现数据。上述的组合也应包括在计算机可读介质的范围内。
本申请实施例还提供了一种计算机程序产品。上述实施例中描述的方法可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。如果在软件中实现，可以全部或者部分得通过计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行上述计算机程序指令时，全部或部分地产生按照上述方法实施例中描述的流程或功能。上述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本申请的具体实施方式而已，并不用于限定本申请的保护范围，凡在本申请的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本申请的保护范围之内。

Claims (27)

  1. 一种通信方法，其特征在于，所述方法包括：
    第一移动管理实体从统一数据管理功能实体接收第一事件信息，所述第一事件信息用于指示第一类的终端事件，所述第一事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告；
    所述第一移动管理实体从会话管理功能实体接收业务传输通知；
    当终端装置不可达时，所述第一移动管理实体根据所述第一事件信息，激活所述第一类型的终端事件；
    当所述终端装置可达时，所述第一移动管理实体向订阅所述第一类型的终端事件的应用功能实体发送终端事件报告。
  2. 如权利要求1所述的方法，其特征在于，所述第一事件信息还包括指示信息，所述指示信息用于指示所述第一类的终端事件。
  3. 如权利要求2所述的方法，其特征在于，所述方法还包括：当所述终端装置切换通信系统后，所述第一移动管理实体从所述统一数据管理功能实体接收所述第一事件信息。
  4. 如权利要求2所述的方法，其特征在于，所述方法还包括：当所述终端切换通信系统后，所述第一移动管理实体从第二移动管理实体接收一个或多个所述第二事件信息，所述第二事件信息中未包括所述指示信息；
    所述第一移动管理实体从所述统一数据管理功能实体接收所述第一事件信息；
    所述第一移动管理实体根据所述第一事件信息，删除所述一个或多个第二事件信息中的与所述第一类的终端事件所对应的第二事件信息。
  5. 如权利要求2所述的方法，其特征在于，所述方法还包括：当所述终端切换通信系统过程中，所述第一移动管理实体根据所述第一事件信息得到第二事件信息，所述第二事件信息未包括所述指示信息；
    所述第一移动管理实体向第二移动管理实体发送所述第二事件信息。
  6. 根据权利要求2～5任一项所述的方法，其特征在于，所述指示信息包括数据网络名称和/或切片信息。
  7. 如权利要求1～6任一项所述的方法，其特征在于，所述第一类的终端事件是增强的终端事件，或所述第一类的终端事件是非增强的终端事件。
  8. 一种通信方法，其特征在于，所述方法包括：
    统一数据管理功能实体从控制功能实体接收第三事件信息，所述第三事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告，当所述终端事件为第一类的终端事件时，所述第三事件信息还包括业务描述信息；
    所述统一数据管理功能实体根据所述第三事件信息，得到第一事件信息，其中，所述第一事件信息用于指示第一类的终端事件或非第一类的终端事件，所述第一事件信息包括所述事件关联标识；
    当终端装置接入第一通信系统时，所述统一数据管理功能实体向第一移动管理功能实体发送所述第一事件信息，所述第一事件信息被用于激活所述第一类的终端事件。
  9. 如权利要求8所述的方法，其特征在于，所述第一事件信息还包括指示信息，所述指示信息用于指示所述第一类的终端事件。
  10. 如权利要求8所述的方法，其特征在于，所述方法还包括：
    当所述终端装置切换至第二通信系统时，所述统一数据管理功能实体向第二移动管理功能实体发送第二事件信息，所述第二事件信息未包括所述指示信息，所述第二事件信息被用于激活所有终端事件。
  11. 如权利要求10所述的方法，其特征在于，所述方法还包括：当所述终端从所述第二通信系统切换至所述第一通信系统后，
    所述统一数据管理功能实体向所述第一移动管理功能实体发送所述第一事件信息。
  12. 如权利要求8所述的方法，其特征在于，所述方法还包括：当所述终端从第一通信系统切换至所述第二通信系统后，
    所述统一数据管理功能实体向所述第二移动管理功能实体发送所述第二事件信息。
  13. 一种通信装置，其特征在于，所述装置包括：
    收发单元，用于从统一数据管理功能实体接收第一事件信息，所述第一事件信息用于指示第一类的终端事件，所述第一事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告；
    所述收发单元还用于从会话管理功能实体接收业务传输通知；
    处理单元，用于当终端装置不可达时，根据所述第一事件信息，激活所述第一类的终端事件；
    所述收发单元还用于当所述终端装置可达时，向订阅所述第一类的终端事件的应用功能实体发送终端事件报告。
  14. 如权利要求13所述的装置，其特征在于，所述第一事件信息还包括指示信息，所述指示信息用于指示所述第一类的终端事件。
  15. 如权利要求14所述的装置，其特征在于，所述收发单元还用于当所述终端装置切换通信系统后，从所述统一数据管理功能实体接收所述第一事件信息。
  16. 如权利要求13所述的装置，其特征在于，所述收发单元还用于当所述终端切换通信系统后，从第二移动管理实体接收一个或多个所述第二事件信息，所述第二事件信息中未包括所述指示信息；
    所述收发单元还用于从所述统一数据管理功能实体接收所述第一事件信息；
    所述处理单元还用于根据所述第一事件信息，删除所述一个或多个第二事件信息中的与所述第一类的终端事件所对应的第二事件信息。
  17. 如权利要求14所述的装置，其特征在于，所述处理单元还用于当所述终端切换通信系统过程中，根据所述第一事件信息得到第二事件信息，所述第二事件信息未包括所述指示信息；
    所述收发单元还用于向第二移动管理实体发送所述第二事件信息。
  18. 根据权利要求14～17任一项所述的装置，其特征在于，所述指示信息包括数据网络名称和/或切片信息。
  19. 如权利要求13～18任一项所述的装置，其特征在于，所述第一类的终端事件是增强的终端事件，或所述第一类的终端事件是非增强的终端事件。
  20. 一种通信装置，其特征在于，所述装置包括：
    收发单元，用于从控制功能实体接收第三事件信息，所述第三事件信息包括事件关联标识，所述事件关联标识用于标识所述终端事件的上下文信息，或者所述事件关联标识用于标识所述终端事件报告，当所述终端事件为第一类的终端事件时，所述第三事件信息还包括业务描述信息；
    处理单元，用于根据所述第三事件信息，得到第一事件信息，其中，所述第一事件信息用于指示第一类的终端事件或非第一类的终端事件，所述第一事件信息包括事件关联标识；
    所述收发单元还用于当终端装置接入第一通信系统时，向第一移动管理功能实体发送所述第一事件信息，所述第一事件信息被用于激活所述第一类的终端事件。
  21. 如权利要求20所述的装置，其特征在于，所述第一事件信息还包括指示信息，所述指示信息用于指示所述第一类的终端事件。
  22. 如权利要求20所述的装置，其特征在于，所述收发单元还用于当所述终端装置切换至第二通信系统时，向第二移动管理功能实体发送第二事件信息，所述第二事件信息未 包括所述指示信息，所述第二事件信息被用于激活所有终端事件。
  23. 如权利要求22所述的装置，其特征在于，当所述终端从所述第二通信系统切换至所述第一通信系统后，所述收发单元还用于向所述第一移动管理功能实体发送所述第一事件信息。
  24. 如权利要求20所述的装置，其特征在于，当所述终端从第一通信系统切换至所述第二通信系统后，所述收发单元还用于向所述第二移动管理功能实体发送所述第二事件信息。
  25. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序或指令，当所述计算机程序或指令被执行时，实现如权利要求1～7任一项或如权利要求8～12任一项所述的方法。
  26. 一种计算机程序产品，其特征在于，用于当所述计算机程序在计算设备上执行时，实现如权利要求1～7任一项或如权利要求8～12任一项所述的方法。
  27. 一种通信系统，其特征在于，包括如权利要求13～19任一项所述的通信装置和如权利要求20～24任一项所述的装置。
PCT/CN2019/128476 2018-12-29 2019-12-25 一种通信方法及装置 WO2020135536A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19902156.9A EP3897010A4 (en) 2018-12-29 2019-12-25 COMMUNICATION METHOD AND DEVICE
US17/362,245 US20210329504A1 (en) 2018-12-29 2021-06-29 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811646628.3A CN111385851B (zh) 2018-12-29 2018-12-29 一种通信方法及装置
CN201811646628.3 2018-12-29

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/362,245 Continuation US20210329504A1 (en) 2018-12-29 2021-06-29 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2020135536A1 true WO2020135536A1 (zh) 2020-07-02

Family

ID=71129101

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/128476 WO2020135536A1 (zh) 2018-12-29 2019-12-25 一种通信方法及装置

Country Status (4)

Country Link
US (1) US20210329504A1 (zh)
EP (1) EP3897010A4 (zh)
CN (2) CN113873588A (zh)
WO (1) WO2020135536A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110536282B (zh) * 2019-03-28 2023-03-21 中兴通讯股份有限公司 一种事件通知方法及装置
CN113938911A (zh) * 2020-07-13 2022-01-14 华为技术有限公司 一种通信方法、设备及系统
CN114727240A (zh) * 2021-01-06 2022-07-08 中国电信股份有限公司 短消息服务中心提醒信息服务化实现方法、装置和系统
CN113114651B (zh) * 2021-04-02 2024-03-29 腾讯科技（深圳）有限公司 报告控制方法、装置、设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130262576A1 (en) * 2012-04-03 2013-10-03 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods for event notification framework in a machine-to-machine (m2m) context
CN103384380A (zh) * 2012-05-02 2013-11-06 中兴通讯股份有限公司 一种机器类通信事件的上报方法及相应装置
CN106982425A (zh) * 2016-01-19 2017-07-25 中兴通讯股份有限公司 一种实现mtc事件监控的方法、装置和系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108696861A (zh) * 2017-02-17 2018-10-23 中国移动通信集团河南有限公司 一种呼叫处理方法、移动管理实体设备和服务网关
WO2020076630A1 (en) * 2018-10-08 2020-04-16 Convida Wireless, Llc Device discovery and connectivity in a cellular network
CN111031517A (zh) * 2018-10-10 2020-04-17 中兴通讯股份有限公司 消息通知方法、装置、网元、系统及存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130262576A1 (en) * 2012-04-03 2013-10-03 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods for event notification framework in a machine-to-machine (m2m) context
CN103384380A (zh) * 2012-05-02 2013-11-06 中兴通讯股份有限公司 一种机器类通信事件的上报方法及相应装置
CN106982425A (zh) * 2016-01-19 2017-07-25 中兴通讯股份有限公司 一种实现mtc事件监控的方法、装置和系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP3897010A4
ZTE: "Update of Solution 39: UE availability after DDN failure for multiple AFs", 3GPP DRAFT; S2-1811458, 18 October 2018 (2018-10-18), Dongguan, China, pages 1 - 9, XP051540257 *

Also Published As

Publication number Publication date
EP3897010A1 (en) 2021-10-20
CN113873588A (zh) 2021-12-31
CN111385851B (zh) 2021-09-07
EP3897010A4 (en) 2022-01-26
CN111385851A (zh) 2020-07-07
US20210329504A1 (en) 2021-10-21

Similar Documents

Publication Publication Date Title
WO2019137207A1 (zh) 事件通知方法及相关设备
WO2020135536A1 (zh) 一种通信方法及装置
WO2020224596A1 (zh) 通信方法及装置
US11533666B2 (en) Communication method, communications apparatus, and communications system
WO2018153346A1 (zh) 一种网络切片的选择方法及装置
JP2020505816A (ja) 通信方法、アクセスネットワークデバイス、コアネットワークデバイス及びユーザ装置
WO2021017999A1 (zh) 策略控制功能网元的选择方法、装置、系统及存储介质
WO2019033796A1 (zh) 会话处理方法及相关设备
WO2020173430A1 (zh) 一种会话建立方法及装置
JP7083925B2 (ja) レート制御方法、装置、およびシステム
WO2020001402A1 (zh) 一种管理监控事件的方法及装置
WO2019037500A1 (zh) 一种选择无线接入网设备的方法及装置
WO2021051420A1 (zh) 一种dns缓存记录的确定方法及装置
WO2020052463A1 (zh) 通信方法和网元
WO2022068771A1 (zh) 一种通信方法及通信装置
WO2022022322A1 (zh) 访问本地网络的方法和装置
WO2023087965A1 (zh) 一种通信方法及装置
WO2021160096A1 (zh) 一种私网签约信息更新方法及装置
WO2018228309A1 (zh) 缓存控制方法、网元及控制器
CN116321110B (zh) 服务订阅方法、装置、服务提供网元及存储介质
WO2023221604A1 (zh) 一种通信方法和装置
WO2021115022A1 (zh) 通信方法、装置及设备
US20240163735A1 (en) Cellular communication session management for user equipment (ues) in idle mode
WO2022141528A1 (zh) 一种确定mec接入点的方法及装置
WO2021203249A1 (zh) 会话释放方法与装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19902156

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019902156

Country of ref document: EP

Effective date: 20210714