Communication methods, devices, equipment, storage media and software products

Abstract

This application provides a communication method, apparatus, device, storage medium, and program product. The method includes: a core network device can send a flexible notification message, which can further notify the terminal device of the current caller's information and / or the type of service currently occurring when the terminal device fails to receive a paging message, so that the terminal device can receive notifications about services such as incoming calls or SMS messages, thereby increasing the probability of the user receiving notifications.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, apparatus, device, storage medium, and program product. Background Technology

[0002] In non-line-of-sight (NLOS) environments, due to increased path loss, terminal devices may be unable to perceive the channel status when receiving mobile terminated calls, thus missing critical paging messages and consequently missing calls and messages. Summary of the Invention

[0003] This application provides a communication method, apparatus, device, storage medium, and program product to solve the problem of how a terminal device can receive notifications such as incoming calls or SMS messages when the channel quality of the terminal device is poor.

[0004] In a first aspect, this application provides a communication method applied to a core network device, comprising:

[0005] Send a flexible notification message, the flexible notification message including the information of the first caller and / or the first service type of the terminal device.

[0006] In one possible implementation, sending elastic notification messages includes:

[0007] Send a paging message and start the paging response timer;

[0008] When the paging response timer expires, the elastic notification message is sent.

[0009] In one possible implementation, sending elastic notification messages includes:

[0010] Obtain the subscription data of the terminal device, the subscription data including flexible notification service information;

[0011] Based on the elastic notification service information, send the elastic notification message.

[0012] In one possible implementation, the elastic notification service information includes any one or more of the following:

[0013] The first parameter is used to indicate whether to send the elastic notification message;

[0014] The second parameter indicates a second service type, which is the service type specified by the terminal device; or...

[0015] Information about the second caller, wherein the second caller is the caller designated by the terminal device.

[0016] In one possible implementation, the value of the first parameter includes a first value and a second value;

[0017] The first value is used to indicate sending the elastic notification message, and the second value is used to indicate not sending the elastic notification message.

[0018] In one possible implementation, the second parameter is a type identifier, which is used to indicate the second service type.

[0019] In one possible implementation, sending the elastic notification message based on the elastic notification service information includes:

[0020] Obtain first information, which is used to indicate the information of the first calling party and / or the first service type;

[0021] Based on the first information and the elastic notification service information, the elastic notification message is sent.

[0022] In one possible implementation, sending the elastic notification message based on the first information and the elastic notification service information includes:

[0023] If the second service type includes the first service type, and / or if the second calling party includes the first calling party, then the elastic notification message is sent.

[0024] In one possible implementation, the method further includes:

[0025] If the second service type does not include the first service type, and / or if the second caller does not include the first caller, then the elastic notification message will not be sent.

[0026] In one possible implementation, the information of the first calling party includes the identifier of the first calling party and / or the network address of the first calling party.

[0027] In one possible implementation, obtaining the subscription data of the terminal device includes:

[0028] The contract data is obtained from the UDM.

[0029] In one possible implementation, the method further includes:

[0030] Determine the elastic notification strategy information, which is used to indicate the sending strategy of the elastic notification message.

[0031] In one possible implementation, the core network device is an AMF entity;

[0032] Determine the elastic notification policy information, including:

[0033] Receive the elastic notification policy information sent by the SMF entity.

[0034] In one possible implementation, the elastic notification strategy information includes subscription data.

[0035] In one possible implementation, the first parameter is determined based on the first capability information of the terminal device and the second capability information of the network device;

[0036] Wherein, the first capability information is used to indicate whether the terminal device supports receiving the elastic notification message, and the second capability information is used to indicate whether the network device supports receiving the elastic notification message.

[0037] In one possible implementation, the sending strategy includes whether to resend the elastic notification message;

[0038] The method further includes:

[0039] Based on the elastic notification policy information, determine whether to resend the elastic notification message;

[0040] If so, then resend the elastic notification message.

[0041] In one possible implementation, the elastic notification strategy information includes a third parameter, which indicates the number of times the elastic notification message is sent;

[0042] Based on the elastic notification policy information, determine whether to resend the elastic notification message, including:

[0043] If the number of times the elastic notification message is sent, as indicated by the third parameter, is 1, then it is determined that the elastic notification message will not be resent.

[0044] If the number of times the elastic notification message is sent, as indicated by the third parameter, is greater than 1, then it is determined that the elastic notification message will be retransmitted, and the number of times the elastic notification message is retransmitted is the number of times it is sent, as indicated by the third parameter, minus 1.

[0045] In one possible implementation, the elastic notification strategy information further includes a fourth parameter, which is used to indicate a timer, the timer being a timer for elastic notification;

[0046] Resending the elastic notification message includes:

[0047] The timer is started when the elastic notification message is sent;

[0048] If the timer times out, the elastic notification message will be resent.

[0049] In one possible implementation, the elastic notification message is a paging message, and the elastic notification message further includes a first parameter;

[0050] The first parameter is used to instruct the network device to send a flexible notification message to the terminal device.

[0051] Secondly, this application provides a communication method applied to a terminal device, comprising:

[0052] Receive a flexible notification message, the flexible notification message including information of the first caller and / or the first service type of the terminal device.

[0053] In one possible implementation, the elastic notification message is sent by the core network device based on the subscription data of the terminal device; the subscription data includes elastic notification service information.

[0054] In one possible implementation, the elastic notification service information includes any one or more of the following:

[0055] The first parameter is used to indicate whether to send the elastic notification message;

[0056] The second parameter indicates a second service type, which is the service type specified by the terminal device; or...

[0057] Information about the second caller, wherein the second caller is the caller designated by the terminal device.

[0058] In one possible implementation, the value of the first parameter includes a first value and a second value;

[0059] The first value is used to indicate sending the elastic notification message, and the second value is used to indicate not sending the elastic notification message.

[0060] In one possible implementation, the second parameter is a type identifier, which is used to indicate the second service type.

[0061] In one possible implementation, the method further includes:

[0062] Send a registration request, the registration request including first capability information of the terminal device, the first capability information being used to indicate whether the terminal device supports receiving the elastic notification message, and the first capability information being used to determine the first parameter.

[0063] Thirdly, this application provides a communication device applied to core network equipment, comprising:

[0064] A sending module is used to send a flexible notification message, the flexible notification message including information of the first caller of the terminal device and / or the first service type.

[0065] In one possible implementation, the sending module is specifically used for:

[0066] Send a paging message and start the paging response timer;

[0067] When the paging response timer expires, the elastic notification message is sent.

[0068] In one possible implementation, the sending module is specifically used for:

[0069] Obtain the subscription data of the terminal device, the subscription data including flexible notification service information;

[0070] Based on the elastic notification service information, send the elastic notification message.

[0071] In one possible implementation, the elastic notification service information includes any one or more of the following:

[0072] The first parameter is used to indicate whether to send the elastic notification message;

[0073] The second parameter indicates a second service type, which is the service type specified by the terminal device; or...

[0074] Information about the second caller, wherein the second caller is the caller designated by the terminal device.

[0075] In one possible implementation, the value of the first parameter includes a first value and a second value;

[0076] The first value is used to indicate sending the elastic notification message, and the second value is used to indicate not sending the elastic notification message.

[0077] In one possible implementation, the second parameter is a type identifier, which is used to indicate the second service type.

[0078] In one possible implementation, the sending module is specifically used for:

[0079] Obtain first information, which is used to indicate the information of the first calling party and / or the first service type;

[0080] Based on the first information and the elastic notification service information, the elastic notification message is sent.

[0081] In one possible implementation, the sending module is specifically used for:

[0082] If the second service type includes the first service type, and / or if the second calling party includes the first calling party, then the elastic notification message is sent.

[0083] In one possible implementation, the sending module is also used for:

[0084] If the second service type does not include the first service type, and / or if the second caller does not include the first caller, then the elastic notification message will not be sent.

[0085] In one possible implementation, the information of the first calling party includes the identifier of the first calling party and / or the network address of the first calling party.

[0086] In one possible implementation, the sending module is specifically used for:

[0087] The contract data is obtained from the UDM.

[0088] In one possible implementation, the apparatus further includes a determining module, the determining module being configured to:

[0089] Determine the elastic notification strategy information, which is used to indicate the sending strategy of the elastic notification message.

[0090] In one possible implementation, the core network device is an AMF entity;

[0091] The module is specifically used for:

[0092] Receive the elastic notification policy information sent by the SMF entity.

[0093] In one possible implementation, the elastic notification strategy information includes subscription data.

[0094] In one possible implementation, the first parameter is determined based on the first capability information of the terminal device and the second capability information of the network device;

[0095] Wherein, the first capability information is used to indicate whether the terminal device supports receiving the elastic notification message, and the second capability information is used to indicate whether the network device supports receiving the elastic notification message.

[0096] In one possible implementation, the sending strategy includes whether to resend the elastic notification message;

[0097] The sending module is also used for:

[0098] Based on the elastic notification policy information, determine whether to resend the elastic notification message;

[0099] If so, then resend the elastic notification message.

[0100] In one possible implementation, the elastic notification strategy information includes a third parameter, which indicates the number of times the elastic notification message is sent;

[0101] The sending module is also used for:

[0102] If the number of times the elastic notification message is sent, as indicated by the third parameter, is 1, then it is determined that the elastic notification message will not be resent.

[0103] If the number of times the elastic notification message is sent, as indicated by the third parameter, is greater than 1, then it is determined that the elastic notification message will be retransmitted, and the number of times the elastic notification message is retransmitted is the number of times it is sent, as indicated by the third parameter, minus 1.

[0104] In one possible implementation, the elastic notification strategy information further includes a fourth parameter, which is used to indicate a timer, the timer being a timer for elastic notification;

[0105] The sending module is specifically used for:

[0106] The timer is started when the elastic notification message is sent;

[0107] If the timer times out, the elastic notification message will be resent.

[0108] In one possible implementation, the elastic notification message is a paging message, and the elastic notification message further includes a first parameter;

[0109] The first parameter is used to instruct the network device to send a flexible notification message to the terminal device.

[0110] Fourthly, this application provides a communication device for use in a terminal device, the device comprising:

[0111] A receiving module is used to receive elastic notification messages, the elastic notification messages including information of the first caller of the terminal device and / or the first service type.

[0112] In one possible implementation, the elastic notification message is sent by the core network device based on the subscription data of the terminal device; the subscription data includes elastic notification service information.

[0113] In one possible implementation, the elastic notification service information includes any one or more of the following:

[0114] The first parameter is used to indicate whether to send the elastic notification message;

[0115] The second parameter indicates a second service type, which is the service type specified by the terminal device; or...

[0116] Information about the second caller, wherein the second caller is the caller designated by the terminal device.

[0117] In one possible implementation, the value of the first parameter includes a first value and a second value;

[0118] The first value is used to indicate sending the elastic notification message, and the second value is used to indicate not sending the elastic notification message.

[0119] In one possible implementation, the second parameter is a type identifier, which is used to indicate the second service type.

[0120] In one possible implementation, the apparatus further includes a transmitting module, which is configured to:

[0121] Send a registration request, the registration request including first capability information of the terminal device, the first capability information being used to indicate whether the terminal device supports receiving the elastic notification message, and the first capability information being used to determine the first parameter.

[0122] Fifthly, this application provides a core network device, including: a processor, and a memory communicatively connected to the processor;

[0123] The memory stores computer-executed instructions;

[0124] The processor executes computer execution instructions stored in the memory to implement the method as described in the first aspect.

[0125] Sixthly, this application provides a terminal device, including: a processor, and a memory communicatively connected to the processor;

[0126] The memory stores computer-executed instructions;

[0127] The processor executes computer execution instructions stored in the memory to implement the method as described in the second aspect.

[0128] In a seventh aspect, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a computer, are used to implement the method described in the first or second aspect.

[0129] Eighthly, this application provides a computer program product, including a computer program, which, when executed by a computer, is used to implement the method described in the first or second aspect.

[0130] Ninthly, embodiments of this application provide a chip on which a computer program is stored, and when the computer program is executed by the chip, the method described in the first aspect is executed.

[0131] In one possible implementation, the chip is a chip in a chip module.

[0132] In a tenth aspect, embodiments of this application provide a module device, the module device including a power module, a storage module, and a chip module;

[0133] The power module is used to provide electrical energy to the module device;

[0134] The storage module is used to store data and instructions;

[0135] The chip module is used to perform the method described in the first aspect or the second aspect.

[0136] This application provides a communication method, apparatus, device, storage medium, and program product. The core network device can send flexible notification messages, which can further notify the terminal device of the current caller's information and / or the current service type when the terminal device fails to receive a paging message. This allows the terminal device to receive notifications about current incoming calls or SMS messages, thereby increasing the probability that the user will receive notifications. Attached Figure Description

[0137] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0138] Figure 1 This is a schematic diagram of a communication system applicable to an embodiment of this application;

[0139] Figure 2 A flowchart illustrating a communication method provided in an embodiment of this application;

[0140] Figure 3 A flowchart illustrating another communication method provided in an embodiment of this application;

[0141] Figure 4 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0142] Figure 5 A signaling flowchart of a communication method provided in an embodiment of this application;

[0143] Figure 6 A signaling flowchart for another communication method provided in the embodiments of this application;

[0144] Figure 7 A signaling flowchart for another communication method provided in an embodiment of this application;

[0145] Figure 8 A signaling flowchart for another communication method provided in an embodiment of this application;

[0146] Figure 9 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0147] Figure 10 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0148] Figure 11 A schematic diagram of the structure of a core network device provided in an embodiment of this application;

[0149] Figure 12 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application.

[0150] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0151] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0152] The technical solutions of this application embodiment can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, and 5th Generation (5G) New Radio Access Technology (NR) systems. Among them, the 5G mobile communication system can include non-standalone (NSA) 5G mobile communication systems and / or standalone (SA) 5G mobile communication systems.

[0153] The technical solutions provided in this application can also be applied to future communication systems, such as sixth-generation (6G) mobile communication systems. This application does not limit this application.

[0154] The technical solutions provided in this application can also be applied to satellite communication systems, such as non-terrestrial network (NTN) communication systems. As examples, the NTN system may include a 4G-based NTN system, an NR-based NTN system, an Internet of Things (IoT)-based NTN system, and a narrowband Internet of Things (NB-IoT)-based NTN system.

[0155] To more clearly illustrate this application, the relevant technologies involved in the embodiments of this application will be introduced below:

[0156] In situations with poor channel quality, such as when the terminal device is in an NLOS environment, communication quality deteriorates significantly. This is particularly pronounced in NTN communication systems, where some terminal devices may face downlink environments with poor channel quality. For example, when a terminal device is placed in a pocket, backpack, or vehicle, or when it is obstructed by objects such as buildings and leaves, the additional path loss increases significantly, causing a sharp decrease in the signal-to-noise ratio of the terminal device and resulting in poor channel quality.

[0157] When the core network equipment detects that there is downlink data (such as when there is an incoming call or SMS) that needs to be transmitted to a terminal device in an idle or inactive state, it will trigger a paging message to notify the terminal device.

[0158] However, when the downlink channel quality of the terminal device is poor, the terminal device may miss critical paging messages, thus missing incoming calls or SMS messages.

[0159] Therefore, how to enable terminal devices to receive notifications such as incoming calls or text messages when the channel quality of the terminal device is poor is an urgent problem to be solved.

[0160] Therefore, this application provides a communication method in which the core network device can send a first message when the channel conditions of the terminal device are poor, such as when the terminal device fails to receive a message, to further notify the terminal device of the information of the current caller and / or the type of service currently occurring, so that the terminal device can receive notifications about services such as incoming calls or SMS messages.

[0161] To facilitate understanding, the following will be combined with... Figure 1 The following example illustrates the communication system to which the embodiments of this application are applicable.

[0162] Figure 1 This is a schematic diagram of a communication system applicable to embodiments of this application, such as... Figure 1 As shown, the communication system 10 includes a terminal device 101, a core network device 102, and a network device 103. The communication system 10 may include multiple terminal devices and multiple network devices. Figure 1 The terminal device and network device shown are merely examples, and the embodiments of this application are not intended to limit them.

[0163] When the channel quality of terminal device 101 is poor, terminal device 101 will miss the paging message sent by network device 103, thus missing notifications of incoming calls or SMS messages. This paging message may be sent from core network device 102 to network device 103, which then forwards it to terminal device 101.

[0164] When terminal device 101 fails to receive a message, such as when it fails to receive a paging message, core network device 102 can send a flexible notification message to notify terminal device 101 of the current caller's information and / or the type of service currently in operation.

[0165] In one possible implementation, core network device 102 can send elastic notification messages to network device 103, and network device 103 can send elastic notification messages to terminal devices.

[0166] In this embodiment of the application, the core network device 102 may be an access and mobility management function (AMF) entity in the core network. The AMF entity may be responsible for user access management, authentication and mobility management, etc.

[0167] The core network also includes Session Management Function (SMF) entities and User Plane Function (UPF) entities. The SMF entity is used to manage sessions in the mobile network, such as session establishment, modification, and release. The UPF entity is used to manage user plane data transmission and traffic statistics.

[0168] In this embodiment of the application, the network device 103 can be any device with wireless transceiver function. This equipment includes, but is not limited to: evolved node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved node B, or home node B, HNB), baseband unit (BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP) in a wireless fidelity (WiFi) system. It can also be a next-generation node B (gNB) or transmission point (TRP or TP) in a 5G system, such as NR, one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or transmission point, such as a baseband unit (BBU) or a distributed unit (DU).

[0169] In some deployments, a gNB may include a centralized unit (CU) and a distribution unit (DU). A gNB may also include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU handles physical layer protocols and real-time services, implementing the functions of the radio link control (RLC), medium access control (MAC), and physical layer (PHY) layers. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of the active antenna. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered as being sent by the DU, or by the DU+AAU. It is understood that network devices can be devices that include one or more of the following: CU nodes, DU nodes, and AAU nodes. Furthermore, CU can be considered as a network device in the radio access network (RAN) or a network device in the core network (CN), and this application does not limit it in this regard.

[0170] Network device 103 can provide services to the cell where terminal device 101 is located. Terminal device 101 communicates with the cell through the transmission resources (e.g., frequency domain resources, or spectrum resources) allocated by network device 103. The cell can belong to a macro base station (e.g., macro eNB or macro gNB) or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0171] In the embodiments of this application, the terminal device 101 may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.

[0172] Terminal device 101 can be a device that provides voice / data connectivity to a user, such as a handheld device or in-vehicle device with wireless connectivity. Examples of terminals currently include: mobile phones, tablets, computers with wireless transceiver capabilities (such as laptops and PDAs), mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, extended reality (XR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, and personal digital assistants (PDAs). PDA (Power Assistant), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks or terminal devices in future public land mobile networks (PLMNs), etc.

[0173] Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined, wearable smart devices include those with comprehensive functions, large sizes, and the ability to perform complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses. They also include devices focused on a specific application function that require the use of other devices, such as smart bracelets and smart jewelry for vital sign monitoring.

[0174] The technical solutions of this application and how they solve the aforementioned technical problems are described in detail below with specific embodiments. These specific embodiments may exist independently or in combination with each other. Identical or similar concepts or processes may not be repeated in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0175] Figure 2 This is a flowchart illustrating a communication method provided in an embodiment of this application, such as... Figure 2 As shown, the method includes the following steps:

[0176] S201. Send a flexible notification message, which includes information about the first caller and / or the first service type of the terminal device.

[0177] Core network devices can send elastic notifications to terminal devices in various ways, such as by sending elastic notification messages to network devices, which in turn can send elastic notification messages to terminal devices. In other words, core network devices can send elastic notification messages to terminal devices through network devices, i.e., by forwarding elastic notification messages through network devices. It should be understood that this network device can be a device that provides network services to the terminal devices.

[0178] A flexible notification message is a notification sent to a terminal device when the terminal device fails to receive a message. Alternatively, a flexible notification message can also be called a robust notification message, which is a notification sent to a terminal device when the terminal device fails to receive a message.

[0179] In other words, a resilient notification message or robust notification message can be understood as a notification sent by the terminal device when the channel quality is poor or when receiving messages (such as paging messages) fails.

[0180] In one possible implementation, when the terminal device fails to receive a message, the core network device sends a resilient notification message.

[0181] In one possible implementation, the failure of the terminal device to receive a message could be a failure to receive a paging message, or a failure to receive a synchronization signal / physical broadcast channel (PBCH) block (SSB) message.

[0182] In one possible implementation, the core network device can send a paging message to the network device and start a paging response timer. When the paging response timer expires, it can be determined that the terminal device failed to receive the paging message, and the core network device can send a resilient notification message to the terminal device.

[0183] In one possible implementation, the core network equipment can be an AMF entity.

[0184] In one possible implementation, the core network device may send the elastic notification message via a dedicated channel or by transmitting it with higher transmission power; this application does not limit the method of transmission.

[0185] In this embodiment, the first calling party is the current calling party of the terminal device. For example, the first calling party can be any one of the whitelisted entities on the terminal device, or it can be another calling party. The current calling party can be understood as the party currently initiating the call.

[0186] The first service type is the type of service currently occurring on the terminal device. For example, the first service type can be voice, SMS, public alarm message, or data, etc.

[0187] Among them, voice refers to voice call services, which involve digitizing sound signals and transmitting them over a network to achieve real-time voice communication.

[0188] Short message usually refers to SMS (Short Message Service), which is a service for sending and receiving short text messages via mobile networks.

[0189] Public alert messages are a service used to send emergency information to the public, typically including natural disaster warnings, emergency safety information, or other important announcements, which are sent to terminal devices via broadcast or mobile networks.

[0190] Data refers to various non-voice information transmitted over the network, including internet browsing, email, video streaming, and file transfers.

[0191] In this embodiment, the core network device can send elastic notification messages to notify the terminal device of the current caller's information and / or the type of service currently in operation, so that the terminal device can receive notifications about services such as incoming calls or SMS messages, thereby increasing the probability that the user will receive the notifications.

[0192] The following explains how core network devices send elastic notification messages.

[0193] Figure 3 A flowchart illustrating another communication method provided in an embodiment of this application is shown below. Figure 3 As shown, the method includes the following steps:

[0194] S301. The core network equipment obtains the subscription data of the terminal equipment, which includes elastic notification service information.

[0195] Core network equipment can obtain subscription data from terminal equipment.

[0196] In one possible implementation, core network equipment can obtain subscription data from user data management (UDM).

[0197] In one possible implementation, the core network device can obtain subscription data when the paging response timer times out.

[0198] In one possible implementation, the core network device may obtain the subscription data from the UDM after receiving the registration request, or it may obtain the subscription data from the UDM after the core network device sends a registration acceptance message to the terminal device. This application does not limit this.

[0199] In one possible implementation, the core network device can receive elastic notification policy information sent by the SMF, which includes subscription data.

[0200] In one possible implementation, the SMF can send elastic notification policy information to the core network device via N1N2 Message Transfer messages. The N1N2 Message Transfer messages are messages transmitted through the N1 and N2 interfaces. The N1N2 Message Transfer messages include elastic notification policy information, and may also include subscription permanent identity (SUPI), protocol data unit (PDU) session identifier (ID), N1 message, N2 message, N1N2TransferFailure notification target address, etc. Among them, the N1 message is a message transmitted through the N1 interface, the N2 message is a message transmitted through the N2 interface, and the N1N2TransferFailure notification target address is the address of the relevant party to be notified when the transmission of N1 message and N2 message fails.

[0201] In one possible implementation, the SMF can send the elastic notification policy information to the core network equipment by carrying the elastic notification policy information in other messages. The other messages can be existing messages or new messages, and this application does not limit them.

[0202] In one possible implementation, the elastic notification message may include any one or more of the following:

[0203] The first parameter indicates whether to send an elastic notification message;

[0204] The second parameter indicates the second service type, which is the service type specified by the terminal device; or...

[0205] Information about the second caller, where the second caller is the caller designated by the terminal device.

[0206] For ease of description, Table 1 below illustrates the data included in the elastic notification message. It is understood that the examples in Table 1 can also have other forms. For example, when the first parameter is TRUE, it can indicate that an elastic notification message is sent. When the first parameter is FALSE or NOT, it indicates that an elastic notification message is not sent. Of course, the first parameter can also be used to indicate whether to send an elastic notification message through other characters, numbers, letters, or combinations of numbers and letters. This application does not limit this.

[0207] In one possible implementation, the first parameter can take two values: a first value and a second value. The first value indicates that an elastic notification message should be sent, and the second value indicates that an elastic notification message should not be sent.

[0208] For example, as shown in Table 1, the first value can be 1 and the second value can be 0.

[0209] In one possible implementation, the second parameter is a type identifier, which is used to indicate the second business type.

[0210] For example, as shown in Table 1, the type identifier can be 0, 1, 2, 3, and 4, etc.

[0211] In one possible implementation, the first parameter can be called the resilience enable parameter (resilienceNotificationEnable) or the resilience notification indicator, which is used to indicate whether to send a resilience notification message.

[0212] The first parameter indicates whether to send a flexible notification message; it can be understood as indicating whether to use flexible notifications. Alternatively, it can be understood as indicating whether the terminal device has the capability for flexible notifications. Here, "flexible notification" can refer to a flexible notification message.

[0213] In one possible implementation, the second parameter can be called the ResilienceNotificationMTService, where MTService refers to the message transfer service, and the second service type is the service type subscribed to by the terminal device. The examples in Table 1 (i.e., the example second service type) can be some or all of the service types supported by the core network. For instance, if the second service type is all of the service types supported by the core network, it means that the terminal device has subscribed to all the service types supported by the core network.

[0214] In one possible implementation, the information of the second caller can be called a resiliencenotificationwhitelist. The number of second callers can be one or more, and the list includes information of one or more callers.

[0215] In one possible implementation, the information of the second calling party may include the second calling party's identifier and / or the second calling party's network address. The identifier may be a telephone number, and the network address may be an Internet Protocol (IP) address.

[0216] As shown in Table 1, the second service type can be understood as the service type specified by the terminal device. This specified service type is the service type that can send elastic notifications, or it can be understood as the service type that can be used to send elastic notifications, which is the service type that the terminal device subscribes to.

[0217] The second calling party can be understood as the calling party designated by the terminal device. The calling party designated by the terminal device is the calling party that can send flexible notifications, or it can be understood as the calling party that can be used to send flexible notifications.

[0218] Table 1

[0219]

[0220] In one possible implementation, the first parameter may be determined based on first capability information of the terminal device and second capability information of the network device. The first capability information indicates whether the terminal device supports receiving elastic notification messages, and the second capability information indicates whether the network device supports receiving elastic notification messages.

[0221] The first capability information can be sent by the terminal device through a registration request, that is, the first capability information is carried in the registration request. The second capability information can be sent by the network device.

[0222] In other words, the terminal device can send a registration request to the core network device, and the registration request includes the first capability information.

[0223] For example, the registration request may be a registration request sent by the terminal device when it first accesses the core network.

[0224] For example, if the first capability information indicates that receiving elastic notification messages is not supported, and / or the second capability information indicates that receiving elastic notification messages is not supported, then the first parameter can be set to a value indicating that elastic notification messages will not be sent, such as a second value. If the first capability information indicates that receiving elastic notification messages is supported, and the second capability information indicates that receiving elastic notification messages is supported, then the first parameter can be set to a value indicating that elastic notification messages will be sent, such as a first value.

[0225] S302. Core network equipment sends elastic notification messages to network equipment based on elastic notification service information.

[0226] Core network equipment can send elastic notification messages based on the elastic notification service information in the acquired subscription data.

[0227] In one possible implementation, the core network device can obtain first information, which is used to indicate the message and / or first service type of the first calling party.

[0228] For example, the core network device can receive first information sent by the SMF entity, wherein the first information is generated based on downlink data packets related to the PDU session received by the UPF entity. The UPF entity can determine whether to cache the downlink data packets based on the SMF data caching notification. If the SMF data caching notification indicates not to cache the downlink data packets, the UPF can process the downlink data packets immediately; if the SMF data caching notification indicates to cache the downlink data packets, the UPF can cache the downlink data packets. The downlink data packets may include data packets related to the current service type occurring at the terminal device.

[0229] When the first downlink packet of any quality of service (QoS) flow arrives at the UPF, the UPF sends a data notification to the SMF to inform the SMF that there is a new downlink packet to process.

[0230] The SMF can send first information to the core network equipment based on the received data notification. The first information can be an N1N2 Message Transfer message, which indicates the message of the first calling party and / or the first service type.

[0231] In one possible implementation, the information of the first calling party may include the identifier of the first calling party and / or the network address of the first calling party.

[0232] For example, the identifier of the first caller could be the phone number of the first caller. Alternatively, the identifier could be used to indicate whether the first caller is an important caller of the terminal device. For instance, if the identifier is 1, it means that the first caller is a caller in the whitelist of the terminal device, thus indicating that the first caller is an important caller. If the identifier is 0, it means that the first caller is not a caller in the whitelist of the terminal device, i.e., the first caller is a regular caller.

[0233] In one possible implementation, if the second service type includes the first service type, and / or if the second calling party includes the first calling party, then a flexible notification message is sent.

[0234] In other words, if the second service type is one of the service types specified by the terminal device, and / or the second calling party is one of the calling parties specified by the terminal device, the core network device can send a flexible notification message.

[0235] The following lists several possible scenarios:

[0236] In one possible implementation, if the subscription data includes a first parameter and a second parameter, and if the first parameter indicates that an elastic notification message is to be sent, it means that the terminal device supports receiving elastic notification messages. The core network device can determine whether the second service type includes the first service type. If so, it can send an elastic notification message.

[0237] In one possible implementation, if the subscription data includes the first parameter and the information of the second calling party, and if the first parameter indicates that an elastic notification message is to be sent, it can be indicated that the terminal device supports receiving elastic notification messages. The core network device can determine whether the first calling party is included in the second calling party. If so, an elastic notification message can be sent.

[0238] In one possible implementation, if the subscription data includes a first parameter, a second parameter, and information about the second calling party, and if the first parameter indicates that a flexible notification message should be sent, then the terminal device supports receiving flexible notification messages. The core network device can determine whether the second calling party includes the first calling party, and / or whether the second service type includes the first service type. If so (i.e., the second calling party includes the first calling party, and / or the second service type includes the first service type), then a flexible notification message can be sent.

[0239] In one possible implementation, if the subscription data includes a first parameter, and if the first parameter indicates that an elastic notification message should be sent, the core network device can send an elastic notification message.

[0240] In the above possible scenarios, if the first parameter indicates that elastic notification messages should not be sent, it means that the terminal device does not support receiving elastic notification messages, and the core network device may not send elastic notification messages.

[0241] In one possible implementation, if the subscription data includes the second parameter and / or the information of the second calling party, the core network device can determine whether the second calling party includes the first calling party, and / or whether the second service type includes the first service type. If so (i.e., the second calling party includes the first calling party, and / or the second service type includes the first service type), then a flexible notification message can be sent.

[0242] In one possible implementation, if the contracted data includes the second parameter and / or the information of the second calling party, if the second service type does not include the first service type, and / or if the second calling party does not include the first calling party, then the core network device does not send a flexible notification message.

[0243] S303. Network devices send flexible notification messages to terminal devices.

[0244] In this embodiment, when a terminal device fails to receive a message, such as when the paging response timer times out, the core network device can obtain subscription data and send an elastic notification message to the network device based on the subscription data. This allows the network device to further notify the terminal device of the current caller's information and / or the type of service currently in operation, enabling the terminal device to receive notifications about incoming calls or SMS messages, thereby increasing the probability of the user receiving notifications.

[0245] In one possible implementation, the elastic notification message can be a paging message or a new message. The new message can be understood as the type of message proposed in the embodiments of this application.

[0246] In one possible implementation, if the elastic notification message is a paging message, it may further include a first parameter, which can be used to instruct the network device to send the elastic notification message to the terminal device. That is, the elastic notification message sent by the core network device to the network device may carry the first parameter to instruct the network device to send the elastic notification message to the terminal device.

[0247] In this scenario, the elastic notification message sent by the network device to the terminal device may or may not be the same as the elastic notification message received by the network device from the core network device. For example, the elastic notification message sent by the network device to the terminal device may not include the first parameter, in which case the elastic notification message sent by the network device to the terminal device will be different from the elastic notification message received by the network device from the core network device. If the elastic notification message sent by the network device to the terminal device may include the first parameter, then the elastic notification message sent by the network device to the terminal device will be the same as the elastic notification message received by the network device from the core network device; this application does not impose any limitations on this.

[0248] The following describes the enhanced processing after the core network equipment sends the elastic notification message. This enhanced processing can be used to improve the probability that the terminal equipment can successfully receive the elastic notification message.

[0249] In one possible implementation, the core network device can determine elastic notification policy information, which indicates whether to send elastic notification messages. For example, the sending policy includes whether to retransmit elastic notification messages, whether to send elastic notification messages at all, etc.

[0250] In one possible implementation, the core network device is an AMF (Advanced Management Function). The core network device can receive elastic notification policy information sent by the SMF. In other words, the elastic notification policy information can be determined by the SMF and sent to the core network device.

[0251] In one possible implementation, the elastic notification strategy information may include a third parameter, which indicates the number of times the elastic notification message will be sent. This number of sends can also be referred to as the elastic notification count.

[0252] In one possible implementation, the elastic notification strategy information may also include a fourth parameter, which is used to indicate a timer for elastic notification.

[0253] For ease of description, Table 2 below explains the data included in the elastic notification strategy information.

[0254] Table 2

[0255]

[0256] The third parameter indicates the maximum cumulative number of times the elastic notification message can be sent. For example, if the third parameter is 2, when the terminal device fails to receive the elastic notification message, it can resend the elastic notification message, that is, resend the elastic notification message once. The elastic notification message can be sent a maximum of two times. After the terminal device successfully receives the elastic notification message (i.e., the elastic notification is successful), this parameter becomes invalid.

[0257] It should be noted that, in the embodiments of this application, the core network device may continue to send paging messages to the network device while sending elastic notification messages to the terminal device. If paging of the terminal device is successful during the sending of elastic notification messages, that is, the core network device receives the paging response from the terminal device, such as a registration request service request, control plane service, etc., the core network device and / or the network device may stop the relevant processing of elastic notification messages, for example, by turning off / stopping the timer (i.e., the timer used for elastic notifications).

[0258] The following section provides further explanation regarding the "whether to resend elastic notification messages" option in the sending strategy.

[0259] Figure 4 This is a flowchart illustrating another communication method provided in an embodiment of this application. This method can be executed by a core network device, such as... Figure 4 As shown, the method includes the following steps:

[0260] S401. Based on the elastic notification policy information, determine whether to resend the elastic notification message.

[0261] If so, then execute S402.

[0262] In one possible implementation, the core network device can determine whether to retransmit the elastic notification message based on the third parameter in the elastic notification policy information.

[0263] Specifically, if the number of times the elastic notification message is sent, as indicated by the third parameter, is 1, then it is determined that the elastic notification message will not be resent. In other words, if the number of times the elastic notification message is sent, as indicated by the third parameter, is 1, then it means that the elastic notification message does not need to be resent.

[0264] If the number of times the elastic notification message has been sent, as indicated by the third parameter, is greater than 1, then it is determined that the elastic notification message will be resent. In other words, if the number of times the elastic notification message has been sent, as indicated by the third parameter, is greater than 1, then the elastic notification message can be resent, and the number of resentments is the number of times the elastic notification message has been sent, as indicated by the third parameter, minus 1.

[0265] S402, Resend the elastic notification message.

[0266] In one possible implementation, if it is determined that the elastic notification message should be retransmitted, the core network device can determine whether the terminal device has failed to accept the elastic notification message. If it is determined that the message has failed, the elastic notification can be retransmitted.

[0267] The core network equipment can determine whether a terminal device has failed to receive an elastic notification message in the following ways:

[0268] Method 1

[0269] After sending an elastic notification message, the core network device can listen for a feedback message from the terminal device. If no feedback message is received, the core network device can determine that the terminal device failed to receive the elastic notification message. For example, if the core network device does not receive a feedback message from the terminal device within a preset time after sending the elastic notification message, it can determine that the terminal device failed to receive the elastic notification message.

[0270] Method 2

[0271] The core network equipment can start a timer indicated by the fourth parameter after sending the elastic notification message. If the timer expires, it is determined that the terminal device failed to receive the elastic notification message. In other words, if the timer duration reaches the set duration, it can be determined that the terminal device failed to receive the elastic notification message; if the timer duration stops before reaching the set duration, it can be determined that the terminal device successfully received the elastic notification message.

[0272] If the core network device determines that the terminal device fails to receive the elastic notification message, it can retransmit the elastic notification message. For example, if the number of times the elastic notification message is sent, as indicated by the third parameter, is 3, the core network device can retransmit the elastic notification message twice.

[0273] In this embodiment, the core network device can perform enhancement processing based on the third and fourth parameters. For example, when the terminal device fails to receive the elastic notification message, it can resend the elastic notification message to increase the probability that the terminal device will successfully receive the elastic notification message.

[0274] Below, through Figures 5 to 7 The interaction between the various devices in the communication method provided in the embodiments of this application will be described.

[0275] Figure 5 This application provides a signaling flowchart for a communication method. Based on the above embodiments, this embodiment describes in detail the interaction process between devices, such as... Figure 5 As shown, the method provided in this embodiment includes the following steps.

[0276] S501, The terminal device sends a registration request to the AMF entity.

[0277] S502, AMF entities obtain contract data.

[0278] S503, the AMF entity sends a registration acceptance message to the terminal device.

[0279] S504, the AMF entity receives the first message sent by the SMF entity.

[0280] The first piece of information can be an N1N2 Message Transfer message. The N1N2 Message Transfer message can be generated by the SMF entity based on a data notification received from the UPF entity. This data notification can be generated by the UPF based on received downlink data packets. The interaction between the UPF entity and the SMF entity is not shown in the diagram.

[0281] S505 and AMF entities send paging messages to network devices.

[0282] S506, The network device sends a paging message to the terminal device.

[0283] S507. When the terminal device fails to receive the paging message, the AMF sends a flexible notification message to the network device.

[0284] S508, Network devices send flexible notification messages to terminal devices.

[0285] For the specific implementation and technical effects of the embodiments of this application, please refer to the above embodiments, which will not be repeated here.

[0286] Figure 6 This embodiment provides a signaling flowchart for another communication method according to an embodiment of this application. Based on the above embodiments, this embodiment describes in detail the interaction process between devices, such as... Figure 6 As shown, the method provided in this embodiment includes the following steps.

[0287] S601, The terminal device sends a registration request to the AMF entity.

[0288] S602, AMF entity obtains contract data.

[0289] S603, the AMF entity sends a registration acceptance message to the terminal device.

[0290] S604, the AMF entity receives the first message sent by the SMF entity.

[0291] The first information is used to indicate the information of the first caller and / or the first service type.

[0292] S605, AMF entities set up flexible notification policy information and flexible notification messages based on the signed data.

[0293] The elastic notification strategy information may include a third parameter and a fourth parameter.

[0294] The S606 and AMF entities send paging messages to network devices and start paging response timers.

[0295] S607. The network device sends a paging message to the terminal device.

[0296] S608. When the paging response timer expires, send an elastic notification message to the network device according to the first information and the elastic notification policy information AMF.

[0297] S609. Network devices send flexible notification messages to terminal devices.

[0298] For the specific implementation and technical effects of the embodiments of this application, please refer to the above embodiments, which will not be repeated here.

[0299] It should be noted that, in Figure 5 and Figure 6 In the embodiments described, the execution order of steps S502 and S602 is not limited. For example, S502 may be executed after S503. Furthermore, in step S507, if the terminal device fails to receive the paging message, the AMF entity may continue to send paging messages to the network device. And in step S608, if the paging response timer times out, the AMF entity may continue to send paging messages to the network device.

[0300] Below, through Figure 7 This section explains whether to send elastic notification messages in the sending strategy.

[0301] Figure 7 This is a signaling flowchart for another communication method provided in this application embodiment. Based on the above embodiments, this embodiment describes in detail the interaction process between devices, such as... Figure 7 As shown, the method provided in this embodiment includes the following steps.

[0302] S701. The terminal device sends a registration request to the AMF entity. The registration request includes the terminal device's first capability information.

[0303] The registration request includes first capability information of the terminal device, which indicates whether the terminal device supports receiving flexible notification messages. For example, the first capability information can also be called flexible notification capability indication information.

[0304] For example, when the first capability information is TRUE or 1, it can indicate that receiving elastic notification messages is supported. When the first capability information is FALSE or NOT, it indicates that receiving elastic notification messages is not supported. Of course, the first capability information can also indicate whether to send elastic notification messages in other forms such as characters, numbers, letters or combinations of numbers and letters. This application does not limit this.

[0305] S702, AMF entity obtains contract data.

[0306] S703, the AMF entity sends a registration acceptance message to the terminal device.

[0307] S704, the AMF entity receives the first message sent by the SMF entity.

[0308] The first information is used to indicate the information of the first caller and / or the first service type.

[0309] S705 and AMF entities set flexible notification policy information based on the signed data. The flexible notification policy information may include a third parameter and a fourth parameter.

[0310] The S706 and AMF entities send paging messages to network devices and start paging response timers.

[0311] S707, Network devices send paging messages to terminal devices.

[0312] S708. When the paging response timer expires, the AMF entity sends a resilient notification message to the network device based on the first capability information.

[0313] For example, if the first capability information indicates that the terminal device supports receiving elastic notification messages, the AMF sends elastic notification messages to the network device; if the first capability information indicates that the terminal device does not support receiving elastic notification messages, the AMF does not send elastic notification messages to the network device.

[0314] S709, Start the timer indicated by the fourth parameter.

[0315] S710, network devices send flexible notification messages to terminal devices.

[0316] It is understandable that the execution order of S709 and S710 is not important.

[0317] S711. If the timer indicated by the fourth parameter times out and the number of elastic notification messages sent indicated by the third parameter is greater than 1, the AMF entity retransmits the elastic notification message to the network device.

[0318] S712, the network device resends the elastic notification message to the terminal device.

[0319] For the specific implementation and technical effects of the embodiments of this application, please refer to the above embodiments, which will not be repeated here.

[0320] It should be noted that, in Figure 7 In the embodiments described, the execution order of step S702 is not limited. For example, S702 may be executed after S703. Furthermore, for step S708, the AMF entity may continue to send paging messages to the network device when the paging response timer expires.

[0321] Figure 8This is a signaling flowchart for another communication method provided in this application embodiment. Based on the above embodiments, this embodiment describes in detail the interaction process between devices, such as... Figure 8 As shown, the method provided in this embodiment includes the following steps.

[0322] S801, The terminal device sends a registration request to the AMF entity.

[0323] S802, the AMF entity sends contract data to the SMF entity.

[0324] S803, the AMF entity sends a registration acceptance message to the terminal device.

[0325] S804, the AMF entity receives the first message sent by the SMF entity.

[0326] S805, SMF entities set flexible notification policy information based on contracted data.

[0327] The elastic notification strategy information may include a third parameter and a fourth parameter.

[0328] S806, the SMF entity sends elastic notification policy information to the AMF entity.

[0329] This flexible notification policy information can be sent in an N1N2 Message Transfer message.

[0330] The S807 and AMF entities send paging messages to the network devices and start the paging response timer.

[0331] S808, the network device sends a paging message to the terminal device.

[0332] S809. When the paging response timer expires, send an elastic notification message to the network device according to the first information and the elastic notification policy information AMF.

[0333] S810, network devices send flexible notification messages to terminal devices.

[0334] For the specific implementation and technical effects of the embodiments of this application, please refer to the above embodiments, which will not be repeated here.

[0335] It should be noted that, in Figure 8 In the embodiments described, the execution order of step S802 is not limited. For example, S802 may be executed after S803. Furthermore, for step S809, the AMF entity may continue to send paging messages to the network device when the paging response timer expires.

[0336] Figure 9This is a schematic diagram of a communication device provided in an embodiment of this application. This device can be applied to core network equipment, such as an AMF entity, etc. Figure 9 As shown, the device 90 includes a transmitting module 901.

[0337] The sending module 901 is used to send a flexible notification message, which includes information about the first caller of the terminal device and / or the first service type.

[0338] In one possible implementation, the sending module 901 is specifically used for:

[0339] Send a paging message and start the paging response timer.

[0340] When the paging response timer times out, an elastic notification message is sent.

[0341] In one possible implementation, the sending module 901 is specifically used for:

[0342] Obtain the subscription data of the terminal device, which includes information about the flexible notification service.

[0343] Send elastic notification messages based on the elastic notification service information.

[0344] In one possible implementation, the elastic notification business information includes any one or more of the following:

[0345] The first parameter indicates whether to send an elastic notification message;

[0346] The second parameter indicates the second service type, which is the service type specified by the terminal device; or...

[0347] Information about the second caller, where the second caller is the caller designated by the terminal device.

[0348] In one possible implementation, the first parameter can take the values ​​of a first value and a second value.

[0349] The first value indicates that an elastic notification message should be sent, and the second value indicates that an elastic notification message should not be sent.

[0350] In one possible implementation, the second parameter is a type identifier, which is used to indicate the second business type.

[0351] In one possible implementation, the sending module 901 is specifically used for:

[0352] Obtain first information, which is used to indicate the information of the first calling party and / or the first service type;

[0353] Based on the first information and the elastic notification service information, send an elastic notification message.

[0354] In one possible implementation, the sending module 901 is specifically used for:

[0355] If the second service type includes the first service type, and / or if the second calling party includes the first calling party, then send a flexible notification message.

[0356] In one possible implementation, the sending module 901 is further configured to:

[0357] If the second service type does not include the first service type, and / or if the second caller does not include the first caller, then no flexible notification message will be sent.

[0358] In one possible implementation, the information of the first calling party includes the identifier of the first calling party and / or the network address of the first calling party.

[0359] In one possible implementation, the sending module 901 is specifically used for:

[0360] Retrieve contract data from UDM.

[0361] In one possible implementation, the device 90 further includes a determining module 902, which is used to:

[0362] Determine the elastic notification policy information, which is used to indicate the sending strategy for elastic notification messages.

[0363] In one possible implementation, the core network equipment is an AMF entity.

[0364] Module 902 is specifically used for:

[0365] Receive elastic notification policy information sent by SMF entities.

[0366] In one possible implementation, the elastic notification strategy information includes subscription data.

[0367] In one possible implementation, the first parameter is determined based on the first capability information of the terminal device and the second capability information of the network device.

[0368] The first capability information is used to indicate whether the terminal device supports receiving elastic notification messages, and the second capability information is used to indicate whether the network device supports receiving elastic notification messages.

[0369] In one possible implementation, the sending strategy includes whether to resend the elastic notification message.

[0370] The sending module 901 is also used for:

[0371] Based on the elastic notification policy information, determine whether to resend the elastic notification message.

[0372] If so, resend the elastic notification message.

[0373] In one possible implementation, the elastic notification strategy information includes a third parameter, which indicates the number of times the elastic notification message will be sent.

[0374] The sending module 901 is also used for:

[0375] If the number of times the elastic notification message is sent, as indicated by the third parameter, is 1, then it is determined that the elastic notification message will not be resent.

[0376] If the number of times the elastic notification message is sent, as indicated by the third parameter, is greater than 1, then it is determined that the elastic notification message will be resent, and the number of times the elastic notification message is resent is the number of times it is sent, as indicated by the third parameter, minus 1.

[0377] In one possible implementation, the elastic notification strategy information also includes a fourth parameter, which is used to indicate a timer for elastic notifications.

[0378] The sending module 901 is specifically used for:

[0379] Start the timer when the elastic notification message is sent.

[0380] If the timer times out, the elastic notification message will be resent.

[0381] In one possible implementation, the elastic notification message is a paging message, and the elastic notification message also includes a first parameter.

[0382] The first parameter is used to instruct the network device to send a flexible notification message to the terminal device.

[0383] It should be noted that the communication device 90 provided in this application can implement all the method steps implemented by the core network equipment (e.g., AMF entity) in the above method embodiment, and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0384] Figure 10 This is a schematic diagram of a communication device provided in an embodiment of this application. This device can be applied to terminal devices, such as... Figure 10 As shown, the device 100 includes a receiving module 1001.

[0385] The receiving module 1001 is used to receive elastic notification messages, which include information about the first caller of the terminal device and / or the first service type.

[0386] In one possible implementation, the elastic notification message is sent by the core network equipment based on the subscription data of the terminal equipment; the subscription data includes elastic notification service information.

[0387] In one possible implementation, the elastic notification business information includes any one or more of the following:

[0388] The first parameter indicates whether to send an elastic notification message;

[0389] The second parameter indicates the second service type, which is the service type specified by the terminal device; or...

[0390] Information about the second caller, where the second caller is the caller designated by the terminal device.

[0391] In one possible implementation, the first parameter can take the values ​​of a first value and a second value.

[0392] The first value indicates that an elastic notification message should be sent, and the second value indicates that an elastic notification message should not be sent.

[0393] In one possible implementation, the second parameter is a type identifier, which is used to indicate the second business type.

[0394] In one possible implementation, the device 100 further includes a transmitting module 1002, which is used for:

[0395] A registration request is sent, which includes the terminal device's first capability information. The first capability information is used to indicate whether the terminal device supports receiving elastic notification messages and to determine the first parameter.

[0396] It should be noted that the communication device 100 provided in this application can realize the same parts and beneficial effects as those in the terminal device in the above method embodiment, which will be described in detail below.

[0397] Figure 11 This is a schematic diagram of the structure of a core network device provided in an embodiment of this application, as shown below. Figure 11 As shown, the core network device 110 may include at least one processor 1101 and a memory 1102.

[0398] The memory 1102 is used to store programs. Specifically, the program may include program code, which includes computer-executable instructions.

[0399] The memory 1102 may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device.

[0400] The processor 1101 is used to execute computer execution instructions stored in the memory 1102 to implement the method described in the foregoing method embodiments. The processor 1101 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0401] Optionally, the electronic device 110 may also include a communication interface 1103. In specific implementations, if the communication interface 1103, memory 1102, and processor 1101 are implemented independently, they can be interconnected via a bus to complete communication. The bus can be an industry-standard architecture (ISA) bus, a peripheral component (PCI) bus, or an extended industry standard architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc., but this does not imply that there is only one bus or one type of bus.

[0402] Optionally, in a specific implementation, if the communication interface 1103, memory 1102 and processor 1101 are integrated on a single chip, then the communication interface 1103, memory 1102 and processor 1101 can communicate through an internal interface.

[0403] Core network device 110 can be an AMF entity.

[0404] The core network device in this embodiment can be used to execute the technical solutions of the above method embodiments. The specific implementation and technical effects are similar, and will not be repeated here.

[0405] Figure 12 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application, such as... Figure 12 As shown, the core network device 120 may include at least one processor 1201 and a memory 1202.

[0406] The memory 1202 is used to store programs. Specifically, the program may include program code, which includes computer-executable instructions.

[0407] The memory 1202 may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device.

[0408] The processor 1201 is used to execute computer execution instructions stored in the memory 1202 to implement the method described in the foregoing method embodiments. The processor 1201 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0409] Optionally, the electronic device 120 may also include a communication interface 1203. In specific implementations, if the communication interface 1203, memory 1202, and processor 1201 are implemented independently, they can be interconnected via a bus to complete communication. The bus can be an industry standard architecture (ISA) bus, a peripheral component (PCI) bus, or an extended industry standard architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc., but this does not imply that there is only one bus or one type of bus.

[0410] Optionally, in a specific implementation, if the communication interface 1203, memory 1202 and processor 1201 are integrated on a single chip, then the communication interface 1203, memory 1202 and processor 1201 can communicate through an internal interface.

[0411] The terminal device in this embodiment can be used to execute the technical solution of the above method embodiment. The specific implementation method and technical effect are similar, and will not be repeated here.

[0412] This application provides a computer-readable storage medium, which may include various media capable of storing computer-executable instructions, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), RAM, a disk, or an optical disk. Specifically, the computer-readable storage medium stores computer-executable instructions, which, when executed by a computer, cause the technical solution shown in the above method embodiment to be executed. The specific implementation and technical effects are similar and will not be repeated here.

[0413] This application provides a computer program product, including a computer program. When the computer program is executed by a computer, the technical solution shown in the above method embodiment is executed. The specific implementation method and technical effect are similar, and will not be repeated here.

[0414] This application provides a chip that stores a computer program. When the computer program is executed by the chip, the technical solution shown in the above method embodiment is executed.

[0415] In one possible implementation, the chip can also be a chip module.

[0416] The chip in this embodiment can be used to execute the technical solution shown in the above method embodiment. The specific implementation method and technical effect are similar, and will not be described again here.

[0417] This application provides a module device, which includes a power module, a storage module, and a chip module.

[0418] The power module is used to provide power to the module devices.

[0419] Storage modules are used to store data and instructions.

[0420] The chip module in this embodiment can be used to execute the technical solution shown in the above method embodiment. The specific implementation method and technical effect are similar, and will not be repeated here.

[0421] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0422] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

[0423] In this application, "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document indicates that the preceding and following related objects have an "or" relationship.

[0424] "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, or a, b, and c, where each of a, b, and c can be an element itself or a set containing one or more elements.

[0425] In this application, "at least one" means one or more. "More than one" means two or more. The descriptions of "first," "second," etc., appearing in the embodiments of this application are only for illustration and to distinguish the described objects, and have no order, nor do they indicate a special limitation on the number of devices in the embodiments of this application, and cannot constitute any limitation on the embodiments of this application. For example, "first threshold" and "second threshold" are only used to distinguish different thresholds, and do not indicate that the size, priority, or importance of these two thresholds are different.

[0426] In this application, terms such as "exemplary," "in some embodiments," and "in other embodiments" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the term "exemplary" is used to present the concept in a specific manner.

[0427] In this application, the terms "of," "corresponding (relevant)," "corresponding," and "related" may sometimes be used interchangeably. It should be noted that, unless a distinction is emphasized, their intended meanings are consistent. Similarly, in the embodiments of this application, "communication" and "transmission" may sometimes be used interchangeably. It should be noted that, unless a distinction is emphasized, their intended meanings are consistent. For example, transmission can include sending and / or receiving, and can be a noun or a verb.

Claims

1. A communication method, characterized in that, Applied to core network equipment, including: Send a flexible notification message, the flexible notification message including information of the first caller of the terminal device and / or the first service type.

2. The method according to claim 1, characterized in that, Send elastic notification messages, including: Send a paging message and start the paging response timer; When the paging response timer expires, the elastic notification message is sent.

3. The method according to claim 1 or 2, characterized in that, Send elastic notification messages, including: Obtain the subscription data of the terminal device, the subscription data including flexible notification service information; Based on the elastic notification service information, send the elastic notification message.

4. The method according to claim 3, characterized in that, The elastic notification service information includes any one or more of the following: The first parameter is used to indicate whether to send the elastic notification message; The second parameter indicates a second service type, which is the service type specified by the terminal device; or... Information about the second caller, wherein the second caller is the caller designated by the terminal device.

5. The method according to claim 4, characterized in that, The value of the first parameter includes a first value and a second value; The first value is used to indicate sending the elastic notification message, and the second value is used to indicate not sending the elastic notification message.

6. The method according to claim 4 or 5, characterized in that, The second parameter is a type identifier, which is used to indicate the second service type.

7. The method according to any one of claims 3-6, characterized in that, Based on the elastic notification service information, send the elastic notification message, including: Obtain first information, which is used to indicate the information of the first calling party and / or the first service type; Based on the first information and the elastic notification service information, the elastic notification message is sent.

8. The method according to claim 7, characterized in that, Based on the first information and the elastic notification service information, the elastic notification message is sent, including: If the second service type includes the first service type, and / or if the second calling party includes the first calling party, then the elastic notification message is sent.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: If the second service type does not include the first service type, and / or if the second caller does not include the first caller, then the elastic notification message will not be sent.

10. The method according to any one of claims 1-9, characterized in that, The information of the first calling party includes the identifier of the first calling party and / or the network address of the first calling party.

11. The method according to any one of claims 3-6, characterized in that, Obtaining the subscription data of the terminal device includes: The contract data is obtained from the User Data Management (UDM).

12. The method according to any one of claims 1-11, characterized in that, The method further includes: Determine the elastic notification strategy information, which is used to indicate the sending strategy of the elastic notification message.

13. The method according to claim 12, characterized in that, The core network equipment is the Access and Mobility Management Function (AMF) entity. Determine the elastic notification policy information, including: Receive the elastic notification policy information sent by the Session Management Function (SMF) entity.

14. The method according to claim 12 or 13, characterized in that, The flexible notification strategy information includes subscription data.

15. The method according to claim 14, characterized in that, The first parameter is determined based on the first capability information of the terminal device and the second capability information of the network device; Wherein, the first capability information is used to indicate whether the terminal device supports receiving the elastic notification message, and the second capability information is used to indicate whether the network device supports receiving the elastic notification message.

16. The method according to any one of claims 12-15, characterized in that, The sending strategy includes whether to resend the elastic notification message; The method further includes: Based on the elastic notification policy information, determine whether to resend the elastic notification message; If so, then resend the elastic notification message.

17. The method according to claim 16, characterized in that, The elastic notification strategy information includes a third parameter, which is used to indicate the number of times the elastic notification message is sent; Based on the elastic notification policy information, determine whether to resend the elastic notification message, including: If the number of times the elastic notification message is sent, as indicated by the third parameter, is 1, then it is determined that the elastic notification message will not be resent. If the number of times the elastic notification message is sent, as indicated by the third parameter, is greater than 1, then it is determined that the elastic notification message will be retransmitted, and the number of times the elastic notification message is retransmitted is the number of times it is sent, as indicated by the third parameter, minus 1.

18. The method according to claim 16 or 17, characterized in that, The elastic notification strategy information also includes a fourth parameter, which is used to indicate a timer, and the timer is a timer used for elastic notifications; Resending the elastic notification message includes: The timer is started when the elastic notification message is sent; If the timer times out, the elastic notification message will be resent.

19. The method according to any one of claims 1-18, characterized in that, The elastic notification message is a paging message, and the elastic notification message also includes a first parameter; The first parameter is used to instruct the network device to send a flexible notification message to the terminal device.

20. A communication method, characterized in that, Applied to terminal devices, including: Receive a flexible notification message, the flexible notification message including information of the first caller and / or the first service type of the terminal device.

21. The method according to claim 20, characterized in that, The elastic notification message is sent by the core network device based on the subscription data of the terminal device; the subscription data includes elastic notification service information.

22. The method according to claim 21, characterized in that, The elastic notification service information includes any one or more of the following: The first parameter is used to indicate whether to send the elastic notification message; The second parameter indicates a second service type, which is the service type specified by the terminal device; or... Information about the second caller, wherein the second caller is the caller designated by the terminal device.

23. The method according to claim 22, characterized in that, The value of the first parameter includes a first value and a second value; The first value is used to indicate sending the elastic notification message, and the second value is used to indicate not sending the elastic notification message.

24. The method according to claim 22 or 23, characterized in that, The second parameter is a type identifier, which is used to indicate the second service type.

25. The method according to any one of claims 22-24, characterized in that, The method further includes: Send a registration request, the registration request including first capability information of the terminal device, the first capability information being used to indicate whether the terminal device supports receiving the elastic notification message, and the first capability information being used to determine the first parameter.

26. A communication device, characterized in that, Applied to core network equipment, the device includes: The sending module is used to send a flexible notification message to the terminal device according to the paging response timer. The flexible notification message includes information of the first caller and / or the first service type of the terminal device.

27. A communication device, characterized in that, Applied to a terminal device, the device includes: A receiving module is used to receive elastic notification messages, the elastic notification messages including information of the first caller of the terminal device and / or the first service type.

28. A core network device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 19.

29. A terminal device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 20 to 25.

30. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as claimed in any one of claims 1 to 19, or the method as claimed in any one of claims 20 to 25.

31. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 19, or the method of any one of claims 20 to 25.

Images