Method, terminal device and network device for wireless communication

Abstract

Embodiments of the present application provide a wireless communication method, terminal device, and network device that can avoid deviations between user settings and actual terminal behavior, thereby improving user experience. The wireless communication method includes: a terminal device receiving first information sent by a network device, wherein the first information includes at least one of the following: a paging cause value supported by the network device, and a paging cause value to which the terminal device needs to respond; wherein the paging cause value supported by the network device is a paging cause value that the network device can detect and / or add to a paging message.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and more specifically, to a wireless communication method, terminal device, and network device. Background Art

[0002] The paging process is used when the terminal device is in the Connection Management–Idle (CM-IDLE) state or the Radio Resource Connection–Inactive (RRC-Inactive) state. When downlink user plane data arrives at the network, the network side sends a paging (Paging) message to find the terminal device. After receiving the paging message, the terminal device initiates a non-access stratum (NAS) message or an access stratum (AS) message to establish a user plane connection to transmit data. In addition, the terminal device can learn the reason for triggering the paging based on the paging cause (Paging Cause) carried in the paging message. In the case where multiple paging causes have multiple values, the user needs to decide whether the paging message corresponding to a specific paging cause value is important or whether a reply is required. However, in some cases, the type of paging cause value broadcast by the network device can be determined based on the network itself, resulting in a deviation between the user's settings and the actual behavior of the terminal, affecting the user experience. Summary of the Invention

[0003] The embodiments of the present application provide a wireless communication method, terminal device, and network device, which can avoid deviations between user settings and actual terminal behavior, thereby improving user experience.

[0004] In a first aspect, a wireless communication method is provided, the method comprising:

[0005] The terminal device receives first information sent by the network device, where the first information includes at least one of the following:

[0006] The paging cause values supported by the network device and the paging cause values to which the terminal device needs to respond.

[0007] Optionally, the paging cause value supported by the network device is a paging cause value that the network device can detect and / or add to a paging message.

[0008] Optionally, the terminal device provides a setting option for the user according to the first information, and the option set by the user is used by the terminal device to determine whether to respond to the paging message.

[0009] In a second aspect, a wireless communication method is provided, the method comprising:

[0010] The network device sends first information to the terminal device, where the first information includes at least one of the following:

[0011] The paging cause values supported by the network device and the paging cause values to which the terminal device needs to respond.

[0012] Optionally, the paging cause value supported by the network device is a paging cause value that the network device can detect and / or add to a paging message.

[0013] Optionally, the first information is used by the terminal device to provide setting options for the user, and the options set by the user are used by the terminal device to determine whether to respond to the paging message.

[0014] In a third aspect, a terminal device is provided for executing the method in the first aspect.

[0015] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect.

[0016] In a fourth aspect, a network device is provided for executing the method in the second aspect.

[0017] Specifically, the network device includes a functional module for executing the method in the above second aspect.

[0018] In a fifth aspect, a terminal device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the method in the first aspect.

[0019] In a sixth aspect, a network device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the method in the second aspect.

[0020] In a seventh aspect, a device is provided for implementing the method in any one of the first to second aspects above.

[0021] Specifically, the apparatus includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the apparatus executes the method in any one of the first to second aspects described above.

[0022] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method in any one of the first to second aspects above.

[0023] In a ninth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to second aspects above.

[0024] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects above.

[0025] Through the above technical solution, the terminal device obtains the paging reason values supported by the network device and / or the paging reason values that the terminal device needs to respond to, so that the terminal device can provide the user with reasonable setting options accordingly, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 It is a schematic diagram of a communication system architecture applied in an embodiment of the present application.

[0027] Figure 2 This is a schematic diagram of a paging process in the CM-IDLE state provided by this application.

[0028] Figure 3 This is a schematic diagram of the paging process in the RRC-Inactive state provided by this application.

[0029] Figure 4 This is a schematic diagram of another paging process in the CM-IDLE state provided by this application.

[0030] Figure 5 This is a schematic diagram of another paging process in the RRC-Inactive state provided by this application.

[0031] Figure 6 It is a schematic flowchart of a wireless communication method provided according to an embodiment of the present application.

[0032] Figure 7 This is a schematic flowchart of a paging reason value indicated according to an embodiment of the present application.

[0033] Figure 8 This is another schematic flowchart of indicating a paging reason value provided according to an embodiment of the present application.

[0034] Figure 9 This is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

[0035] Figure 10 This is a schematic block diagram of a network device provided according to an embodiment of the present application.

[0036] Figure 11This is a schematic block diagram of a communication device provided according to an embodiment of the present application.

[0037] Figure 12 This is a schematic block diagram of a device provided according to an embodiment of the present application.

[0038] Figure 13 It is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0039] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. With respect to the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0040] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0041] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0042] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0043] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.

[0044] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device 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, etc.

[0045] The terminal device can be a station (ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0046] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0047] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0048] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0049] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device or base station (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0050] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0051] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0052] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 1 The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices within the coverage area.

[0053] Figure 1One network device and two terminal devices are shown as an example. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area. This embodiment of the present application does not limit this.

[0054] Optionally, the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

[0055] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be called a communication device. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above and will not be repeated here; the communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0056] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0057] The terms used in the embodiments of this application are intended only to explain the specific embodiments of this application and are not intended to limit this application. The terms "first," "second," "third," and "fourth," etc. in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, not to describe a specific order. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions.

[0058] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0059] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0060] In the embodiments of the present application, "predefined" can be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (for example, a terminal device and a network device). The present application does not limit the specific implementation method. For example, predefined can refer to information defined in a protocol.

[0061] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0062] To facilitate a better understanding of the embodiments of the present application, the paging process related to the present application is described.

[0063] The paging process is used when the terminal is in CM-IDLE or RRC-Inactive state. When downlink user plane data arrives at the network, the network side sends a paging message to find the terminal. The terminal device receives the paging message and initiates a NAS message (such as ServiceRequest) or AS message (such as RRC Resume) to establish a user plane connection to transmit data.

[0064] A paging message is a plain text message. One paging message contains multiple UE identities (IDs), which means that one paging message can page multiple UEs at the same time.

[0065] When the terminal device is in the CM-IDLE state (i.e., the connection between the terminal device and the RAN device and the N2 connection between the RAN device and the core network device are released), the paging process includes S11-S14, as shown in the following example: Figure 2 shown.

[0066] S11, the core network device sends a paging message to the RAN device;

[0067] S12, the Radio Access Network (RAN) device forwards the paging message to the terminal device;

[0068] S13, the terminal device responds to the paging message, such as sending a Service Request message to activate the NAS connection or PDU session;

[0069] S14, establishing a Radio Resource Control (RRC) connection between the terminal device and the RAN device. For example, the terminal device sends an RRC Setup request message to establish the RRC connection.

[0070] S15, the terminal device sends service request information to the core network device.

[0071] The terminal device is in RRC-Inactive (i.e., the connection between the terminal device and the RAN device is released, but the N2 connection between the RAN device and the core network device for the terminal device is not released). The paging process includes S21-S24, as shown in the following example: Figure 3 shown.

[0072] S21, the core network device sends downlink user plane data for the terminal device to the RAN device;

[0073] S22, the RAN device sends a paging message to the terminal device;

[0074] S23, the terminal device replies to the paging message;

[0075] S24: Establish an RRC connection between the terminal device and the RAN device. For example, the terminal device initiates an RRC resume request message to restore the RRC connection, or the terminal device sends an RRC setup request message to establish the RRC connection.

[0076] To more effectively enable terminals to respond to paging messages (for example, not responding to paging messages for low-priority services; or when a terminal user is performing a service on Universal Subscriber Identity Module (USIM)-1, USIM-2 receives a paging message, and the terminal user decides not to respond to avoid service interruption on USIM-1), the paging message can be enhanced by adding a Paging Cause parameter to the paging message. The Paging Cause parameter indicates the service whose downlink data packet arrived at the network, triggering the paging message. This allows the terminal device to determine the triggering paging message based on the Paging Cause parameter and decide whether to respond.

[0077] For example, the paging process in the CM-IDLE state includes S31-S34, as shown in the following example: Figure 4 shown.

[0078] S31, the application server sends downlink data to the core network device, which carries the Differentiated Services Code Point (DSCP) value;

[0079] S32, the core network device derives paging reason information based on the DSCP value carried by the downlink data;

[0080] S33: The core network device sends a paging message to the RAN device, which carries the paging reason.

[0081] S34, the RAN device sends a paging message to the terminal device, which carries the paging reason;

[0082] S35, the terminal device decides whether to reply based on the paging reason;

[0083] S36, the terminal device sends a reply message to the core network device, which carries the service request information.

[0084] For example, the paging process in the RRC-Inactive state includes S41-S44, as shown in FIG. Figure 5 shown.

[0085] S41: The application server sends downlink data to the core network device, which carries the DSCP value.

[0086] S42, the core network device sends a downlink PDU data packet to the RAN device, which carries parameters related to the paging reason;

[0087] S43, the RAN device derives paging reason information based on paging reason related parameters;

[0088] S44, the RAN device sends a paging message to the terminal device, which carries the paging reason;

[0089] S45, the terminal device decides whether to reply based on the paging reason;

[0090] S46, the terminal device sends a reply message to the core network device, which carries the service request information.

[0091] It's important to note that the specific content of the paging reason is derived by the core network or RAN equipment based on information carried in downlink (DL) data packets, such as the Type of Service (ToS) field in the Internet Protocol (IP) packet header (sometimes also referred to as the DSCP value). This means that the information carried in the downlink data packet indicates the service to which the packet corresponds. The core network or RAN equipment then uses this information to send the paging reason to the terminal device.

[0092] Paging cause values can be categorized as standardized or non-standardized. Standardized values standardize the mapping between specific values and services, and all networks must adhere to this mapping. Non-standardized values vary between networks (different values can have different mappings). Part of the value range within the Paging Cause parameter can be used for network-specific content mappings.

[0093] When multiple paging reasons have multiple values, the terminal user needs to decide whether the paging message corresponding to a specific paging reason value is important or whether a reply is required. In this case, the user usually pre-sets the value. Since the terminal does not know which paging reason values are supported or broadcast by the network, this will cause a discrepancy between the user's settings and the actual behavior of the terminal. Specific examples are as follows:

[0094] The PLMN-1 network to which the USIM-1 is registered supports three Paging Cause values: IP Multimedia Subsystem (IMS) voice, SMS, and CP signaling. Users can pre-configure the USIM-1 to prioritize IMS voice and SMS services while unimportant Control Plane (CP) signaling. This means that paging messages for IMS voice and SMS must be replied to, while paging messages for CP signaling do not.

[0095] However, when a user switches from PLMN-1 to PLMN-2, the network under PLMN-2 only supports IMS voice and CP signaling. This means that paging messages never carry the "Paging Cause = SMS" message. Consequently, the terminal on USIM-1 cannot determine whether a paging message corresponds to an SMS service and whether it must respond to the paging message. This creates a mismatch between user needs and actual terminal behavior, impacting the user experience.

[0096] Based on the above problems, the present application proposes a solution for indicating a paging cause value, which can avoid deviations between the user's settings and the actual behavior of the terminal, thereby improving the user experience.

[0097] The technical solution of this application is described in detail below through specific embodiments.

[0098] Figure 6 is a schematic flow chart of a wireless communication method 200 according to an embodiment of the present application, as shown in FIG. Figure 6 As shown, the method 200 may include at least part of the following contents:

[0099] S210: The network device sends first information to the terminal device, where the first information includes at least one of the following:

[0100] The paging cause values supported by the network device and the paging cause values that the terminal device needs to respond to;

[0101] S220: The terminal device receives the first information.

[0102] It should be noted that the paging cause values supported by the network device are paging cause values that the network device can detect and / or add to the paging message.

[0103] In addition, the above-mentioned "response" can be understood as a reply or reply to the paging message. For example, the terminal device sends an RRC establishment request message to establish an RRC connection, and sends a service request message to receive the service corresponding to the paging cause value; for example, the terminal device sends an RRC recovery request message to restore the RRC connection, and sends a service request message to receive the service corresponding to the paging cause value.

[0104] As another optional method, if the network does not send the first information to the terminal, for each network or each network that supports adding paging reason values in paging messages, it must support the same paging reason values (for example, it must support all standardized paging reason values) so that the terminal device can provide the user with the correct setting options and avoid the appearance of services corresponding to paging reason values that are not supported by the network side in the setting options.

[0105] As another optional approach, the terminal device may be pre-configured with the first information, such as the paging cause values supported by one or more PLMNs, so that the terminal device can provide the user with the correct setting options and avoid the appearance of services corresponding to paging cause values not supported by the network in the setting options. "Pre-configured" may be factory settings, settings written to a SIM card and read by the terminal device from the SIM card, or configurations obtained by the terminal device via Over the Air (OTA) technology.

[0106] In an embodiment of the present application, the network device may support one or more paging cause values.

[0107] Optionally, the network device may send the first information via at least one of an access stratum (AS) layer message, a non-access stratum (NAS) layer message, a broadcast message, and a user plane message.

[0108] The user plane message may be a connection established between the server and the terminal device via the user plane (e.g., an application layer Hypertext Transfer Protocol (HTTP) connection). In this case, the network device may be a server. For example, the server may send the first information to the terminal device via an HTTP connection.

[0109] The embodiments of the present application can be applicable to 5G systems (5GS), evolved packet systems (EPS) and future networks.

[0110] Optionally, in an embodiment of the present application, the terminal device may provide a setting option for the user based on the first information, and the option set by the user is used by the terminal device to determine whether to respond to the paging message. This can avoid the appearance of services corresponding to paging cause values that are not supported by the network side in the setting options.

[0111] For example, the terminal device can provide the user with setting options based on the first information. The services in the setting options can correspond to paging cause values. The user can set the importance of each service or set whether a response is required when a certain service occurs. The terminal device can decide whether to respond to the paging message containing the paging cause value corresponding to a certain service based on the user settings. For example, if a voice service comes, a response is required, so each subsequent time the terminal receives a paging message sent to USIM-2 containing Paging cause = voice, it responds to the paging message. In the setting options, the status of the two USIM cards can also be considered, such as when USIM-1 is performing a data service, USIM-2 is in an idle state, or vice versa. For example, when USIM-1 is browsing the web, a voice service occurs on USIM-2.

[0112] Optionally, in some embodiments, the paging cause values supported by the network device change as the location of the terminal device changes; and / or, the paging cause values supported by the network device change over time.

[0113] Optionally, in some embodiments, the paging cause value supported by the network device satisfies at least one of the following:

[0114] Different PLMN identifiers correspond to different paging cause values supported by corresponding network devices;

[0115] Different Tracking Area Indicator (TAI) lists correspond to different paging cause values supported by corresponding network devices;

[0116] Different cell identifiers correspond to different paging cause values supported by corresponding network devices;

[0117] Different RAN node identifiers correspond to different paging cause values supported by corresponding network devices.

[0118] That is, the paging cause values supported by the network device can be sent to the terminal device according to the granularity of Radio Access Technology (RAT), PLMN identity, TAI list, Cell identity, RAN node identity, etc.

[0119] For example, for PLMN 1, the paging cause values supported by the network device include 1, 2, and 3; and for PLMN 2, the paging cause values supported by the network device include 1, 4, and 5.

[0120] For another example, for PLMN 1, the paging cause values supported by the network device include 1, 2, and 3; and for PLMN 2, the paging cause values supported by the network device include 4, 5, and 6.

[0121] For another example, for TAI list 1, the paging cause values supported by the network device include 2 and 3; and for TAI list 2, the paging cause values supported by the network device include 4 and 5.

[0122] For another example, for TAI list 1, the paging cause values supported by the network device include 1, 2, and 3; and for TAI list 2, the paging cause values supported by the network device include 3 and 4.

[0123] For another example, for cell 1, the paging cause values supported by the network device include 2 and 3; and for cell 2, the paging cause values supported by the network device include 4 and 5.

[0124] For another example, for cell 1, the paging cause values supported by the network device include 1, 2, and 3; while for cell 2, the paging cause values supported by the network device include 3, 4, and 5.

[0125] For another example, for RAN node 1, the paging cause values supported by the network device include 2 and 3; and for RAN node 2, the paging cause values supported by the network device include 4 and 5.

[0126] For another example, for RAN node 1, the paging cause values supported by the network device include 2 and 3; and for RAN node 2, the paging cause values supported by the network device include 3 and 5.

[0127] Optionally, in some embodiments, different paging cause values correspond to different services.

[0128] Optionally, the correspondence between the paging cause value and the service is pre-configured or agreed upon by a protocol, or the correspondence between the paging cause value and the service is configured by a network device.

[0129] That is, the correspondence between the paging cause value and the service can be a standardized correspondence or a correspondence specific to different networks.

[0130] Optionally, in some embodiments, the terminal device sends a second message to the network device, where the second message includes a paging cause value supported by the terminal device; and after receiving the second message, the network device determines the first information based on the paging cause value supported by the terminal device. For example, the second message is at least one of an AS message, a NAS message, and a user plane message.

[0131] That is, the terminal device sends the second message to the network device before receiving the first message.

[0132] Optionally, the paging cause values supported by the terminal device may include: paging cause values that the terminal device can provide to the user for setting service options, or paging cause values that the terminal device can identify.

[0133] For example, the paging cause values supported by the terminal device are 1, 2, and 3, and the paging cause values supported by the network device are 2, 3, and 4. The network device can inform the terminal device in the first information that the paging cause values it supports are 2 and 3.

[0134] Optionally, in some embodiments, the first information is carried by registration response information, wherein the registration response information is response information to the registration request information sent by the terminal device.

[0135] For example, the terminal device sends a registration request message to the network device, and the network device sends a registration response message to the terminal device in response to the registration request message, wherein the registration response message carries the first information. Optionally, the registration request message may carry a paging cause value supported by the terminal device.

[0136] Optionally, in some embodiments, the first information is carried by information broadcast by the network device.

[0137] Specifically, for example, the first information is carried by information broadcast by the network device before executing the RRC connection establishment process and / or the registration process. For example, the first information is carried by a system information block (SIB) in the broadcast information. In this case, the terminal device can complete the user settings when establishing the RRC connection or NAS connection, avoiding the need to perform user settings after the terminal device is registered, thereby improving the user experience.

[0138] Optionally, in some embodiments, the first information is carried through signaling in a protocol data unit (PDU) session establishment process, or the first information is carried through signaling in a PDU session modification process.

[0139] For example, the first information is carried through PDU session establishment response information.

[0140] For another example, the first information is carried through PDU session modification response information.

[0141] Optionally, in some embodiments, the first information is carried via RRC signaling. For example, during the RRC connection establishment process, the terminal device receives the first information from the network device via RRC signaling interaction.

[0142] Therefore, in an embodiment of the present application, the terminal device obtains the paging reason values supported by the network device and / or the paging reason values that the terminal device needs to respond to, so that the terminal device can provide the user with reasonable setting options based on this, thereby improving the user experience.

[0143] Furthermore, before executing the RRC connection establishment process and / or the registration process, the information broadcast by the network device carries the paging cause values supported by the network device and / or the paging cause values that the terminal device needs to respond to. As a result, the terminal device can complete user settings when establishing the RRC connection or NAS connection, avoiding user settings after the terminal device is registered, thereby improving the user experience.

[0144] The technical solution of this application is described in detail below through two specific embodiments.

[0145] In embodiment 1, the network device may indicate the paging cause values supported by the network device and / or the paging cause values that the terminal device needs to respond to during the registration process, which may be done by Figure 7 The process S51-S53 shown in is implemented.

[0146] S51, the terminal device sends a registration request message to the core network device, optionally including a paging cause value supported by the terminal device;

[0147] S52, the core network device sends a registration response message to the terminal device in response to the registration request message, where the registration response message carries a paging cause value supported by the network device and / or a paging cause value that the terminal device needs to respond to;

[0148] S53. Optionally, the terminal device may provide the user with setting options based on the paging reason values supported by the network device and / or the paging reason values that the terminal device needs to respond to, so as to avoid the appearance of services corresponding to paging reason values that are not supported by the network side in the setting options.

[0149] It should be noted that if the core network device receives a paging cause value supported by the terminal device in S51, it may also refer to the paging cause values supported by the terminal device. For example, if the paging cause values supported by the terminal device are 1, 2, and 3, and the paging cause values supported by the network side are 2, 3, and 4, the core network device may inform the terminal device in S52 that the paging cause values supported by the network side are 2 and 3.

[0150] It should also be noted that the paging cause values supported by the terminal device may include: paging cause values that the terminal device can provide to the user for setting service options, or paging cause values that the terminal device can recognize. The paging cause values supported by the network device are paging cause values that the network device can detect and / or add to the paging message. (The specific detection and addition behavior of the network device can be as follows Figure 4 and Figure 5 shown).

[0151] In embodiment 2, the network device may indicate the paging cause values supported by the network device and / or the paging cause values that the terminal device needs to respond to before executing the RRC connection establishment and registration process, which can be specifically done by Figure 8 The process S61-S62 shown in is implemented.

[0152] S61, the base station sends a broadcast message to the terminal device, where the broadcast message carries a paging cause value supported by the network device and / or a paging cause value that the terminal device needs to respond to;

[0153] S62. Optionally, the terminal device may provide the user with setting options based on the paging reason values supported by the network device and / or the paging reason values that the terminal device needs to respond to, so as to avoid the appearance of services corresponding to paging reason values that are not supported by the network side in the setting options.

[0154] In Example 2, before executing the RRC connection establishment process and / or the registration process, the information broadcast by the network device carries the paging cause values supported by the network device and / or the paging cause values that the terminal device needs to respond to. As a result, the terminal device can complete user settings when establishing the RRC connection or NAS connection, avoiding the need to perform user settings after the terminal device is registered, thereby improving the user experience.

[0155] Combined with the above Figures 6 to 8 , describes the method embodiment of the present application in detail, and the following is combined with Figures 9 to 13 , the device embodiments of the present application are described in detail. It should be understood that the device embodiments and the method embodiments correspond to each other, and similar descriptions can refer to the method embodiments.

[0156] Figure 9 FIG. 3 shows a schematic block diagram of a terminal device 300 according to an embodiment of the present application. Figure 9As shown, the terminal device 300 includes:

[0157] The communication unit 310 is configured to receive first information sent by a network device, where the first information includes at least one of the following:

[0158] The paging cause values supported by the network device and the paging cause values to which the terminal device needs to respond.

[0159] Optionally, the paging cause value supported by the network device is a paging cause value that the network device can detect and / or add to a paging message.

[0160] Optionally, the communication unit 310 is specifically configured to:

[0161] Receive the first information sent by the network device through at least one of an access layer AS layer message, a non-access layer NAS layer message, a broadcast message, and a user plane message.

[0162] Optionally, the terminal device 300 further includes:

[0163] The processing unit 320 is configured to provide a setting option for the user according to the first information, and the option set by the user is used by the terminal device to determine whether to answer the paging message.

[0164] Optionally, the paging cause values supported by the network device change as the location of the terminal device changes; and / or the paging cause values supported by the network device change over time.

[0165] Optionally, the paging cause values supported by the network device satisfy at least one of the following:

[0166] Different public land mobile network PLMN identifiers correspond to different paging cause values supported by the network equipment;

[0167] Different tracking area indication TAI lists correspond to different paging cause values supported by the corresponding network device;

[0168] Different cell identifiers correspond to different paging cause values supported by the network device;

[0169] Different radio access network RAN node identifiers correspond to different paging cause values supported by the corresponding network device.

[0170] Optionally, the communication unit 310 is further configured to send a second message to the network device, where the second message includes a paging cause value supported by the terminal device.

[0171] Optionally, the paging cause values supported by the terminal device include: paging cause values that the terminal device can provide to the user for setting service options, or paging cause values that the terminal device can identify.

[0172] Optionally, the second message is at least one of an AS message, a NAS message, and a user plane message.

[0173] Optionally, different paging cause values correspond to different services.

[0174] Optionally, the correspondence between the paging cause value and the service is pre-configured or agreed upon by a protocol, or the correspondence between the paging cause value and the service is configured by the network device.

[0175] Optionally, the first information is carried by registration response information, wherein the registration response information is response information to the registration request information sent by the terminal device.

[0176] Optionally, the first information is carried by information broadcast by the network device.

[0177] Optionally, the first information is carried by information broadcast by the network device before executing the radio resource control RRC connection establishment process and / or executing the registration process.

[0178] Optionally, the first information is carried through signaling in a protocol data unit (PDU) session establishment process, or the first information is carried through signaling in a PDU session modification process.

[0179] Optionally, the first information is carried through RRC signaling.

[0180] Alternatively, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0181] It should be understood that the terminal device 300 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the above and other operations and / or functions of each unit in the terminal device 300 are respectively to achieve Figure 6 For the sake of brevity, the corresponding processes of the terminal device in the method 200 are not repeated here.

[0182] Figure 10 FIG. 4 shows a schematic block diagram of a network device 400 according to an embodiment of the present application. Figure 10 As shown, the network device 400 includes:

[0183] The communication unit 410 is configured to send first information to the terminal device, where the first information includes at least one of the following:

[0184] The paging cause values supported by the network device and the paging cause values to which the terminal device needs to respond.

[0185] Optionally, the paging cause value supported by the network device is a paging cause value that the network device can detect and / or add to a paging message.

[0186] Optionally, the communication unit 410 is specifically configured to:

[0187] The first information is sent to the terminal device via at least one of an access layer AS layer message, a non-access layer NAS layer message, a broadcast message, and a user plane message.

[0188] Optionally, the first information is used by the terminal device to provide setting options for the user, and the options set by the user are used by the terminal device to determine whether to respond to the paging message.

[0189] Optionally, the paging cause values supported by the network device change as the location of the terminal device changes; and / or the paging cause values supported by the network device change over time.

[0190] Optionally, the paging cause values supported by the network device satisfy at least one of the following:

[0191] Different public land mobile network PLMN identifiers correspond to different paging cause values supported by the network equipment;

[0192] Different tracking area indication TAI lists correspond to different paging cause values supported by the corresponding network device;

[0193] Different cell identifiers correspond to different paging cause values supported by the network device;

[0194] Different radio access network RAN node identifiers correspond to different paging cause values supported by the corresponding network device.

[0195] Optionally, the network device 400 further includes: a processing unit 420,

[0196] The communication unit 410 is further configured to receive a second message sent by the terminal device, where the second message includes a paging cause value supported by the terminal device;

[0197] The processing unit 420 is configured to determine the first information according to a paging cause value supported by the terminal device.

[0198] Optionally, the paging cause values supported by the terminal device include: paging cause values that the terminal device can provide to the user for setting service options, or paging cause values that the terminal device can identify.

[0199] Optionally, the second message is at least one of an AS message, a NAS message, and a user plane message.

[0200] Optionally, different paging cause values correspond to different services.

[0201] Optionally, the correspondence between the paging cause value and the service is pre-configured or agreed upon by a protocol, or the correspondence between the paging cause value and the service is configured by the network device.

[0202] Optionally, the first information is carried by registration response information, wherein the registration response information is response information to the registration request information sent by the terminal device.

[0203] Optionally, the first information is carried by information broadcast by the network device.

[0204] Optionally, the first information is carried by information broadcast by the network device before executing the radio resource control RRC connection establishment process and / or executing the registration process.

[0205] Optionally, the first information is carried through signaling in a protocol data unit (PDU) session establishment process, or the first information is carried through signaling in a PDU session modification process.

[0206] Optionally, the first information is carried through RRC signaling.

[0207] Alternatively, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0208] It should be understood that the network device 400 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the above and other operations and / or functions of each unit in the network device 400 are respectively for implementing Figure 6 For the sake of brevity, the corresponding processes of the network device in the method 200 are not described here in detail.

[0209] Figure 11 It is a schematic structural diagram of a communication device 500 provided in an embodiment of the present application. Figure 11 The communication device 500 shown includes a processor 510, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0210] Alternatively, as Figure 11 As shown, the communication device 500 may further include a memory 520. The processor 510 may call and execute a computer program from the memory 520 to implement the method in the embodiment of the present application.

[0211] The memory 520 may be a separate device independent of the processor 510 , or may be integrated into the processor 510 .

[0212] Alternatively, as Figure 11 As shown, the communication device 500 may further include a transceiver 530 , and the processor 510 may control the transceiver 530 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0213] The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include an antenna, and the number of antennas may be one or more.

[0214] Optionally, the communication device 500 may specifically be a network device in an embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0215] Optionally, the communication device 500 may specifically be a mobile terminal / terminal device in an embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0216] Figure 12 It is a schematic structural diagram of the device of an embodiment of the present application. Figure 12 The device 600 shown includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0217] Alternatively, as Figure 12 As shown, the apparatus 600 may further include a memory 620. The processor 610 may call and execute a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0218] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0219] Optionally, the apparatus 600 may further include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0220] Optionally, the apparatus 600 may further include an output interface 640. The processor 610 may control the output interface 640 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0221] Optionally, the device can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0222] Optionally, the apparatus can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0223] Optionally, the device mentioned in the embodiments of the present application may also be a chip, for example, a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-chip chip.

[0224] Figure 13 700 is a schematic block diagram of a communication system 700 provided in an embodiment of the present application. Figure 13 As shown, the communication system 700 includes a terminal device 710 and a network device 720 .

[0225] Among them, the terminal device 710 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 720 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0226] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly implemented as a hardware decoding processor, or can be implemented by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0227] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0228] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0229] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0230] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0231] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0232] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0233] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0234] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0235] The embodiment of the present application also provides a computer program.

[0236] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0237] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0238] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0239] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0240] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0241] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0242] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0243] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. In view of this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0244] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that: include: The terminal device receives first information sent by the network device, where the first information includes at least one of the following: The paging cause values supported by the network device and the paging cause values to which the terminal device needs to respond; The paging cause values supported by the network device satisfy at least one of the following: Different public land mobile network (PLMN) identifiers correspond to different paging cause values supported by the network device; Different tracking area indication TAI lists correspond to different paging cause values supported by the corresponding network device; Different cell identifiers correspond to different paging cause values supported by the network device; Different radio access network RAN node identifiers correspond to different paging cause values supported by the network device; Before the terminal device receives the first information, the method further includes: The terminal device sends a second message to the network device, where the second message includes a paging cause value supported by the terminal device, and the first information is determined based on the paging cause value supported by the terminal device; The paging cause values supported by the terminal device include: The terminal device can provide a paging cause value for the user to set service options, or the terminal device can identify the paging cause value.

2. The method according to claim 1, wherein The paging cause value supported by the network device is a paging cause value that the network device can detect and / or add to a paging message.

3. The method according to claim 1, wherein The terminal device receives first information sent by the network device, including: The terminal device receives the first information sent by the network device through at least one of an access layer AS layer message, a non-access layer NAS layer message, a broadcast message, and a user plane message.

4. The method according to claim 1, wherein The method further comprises: The terminal device provides setting options for the user according to the first information, and the options set by the user are used by the terminal device to determine whether to respond to the paging message.

5. The method according to claim 1, wherein The paging cause values supported by the network device change as the location of the terminal device changes; and / or, The paging cause values supported by the network device change over time.

6. The method according to claim 1, wherein The second message is at least one of an AS message, a NAS message, and a user plane message.

7. The method according to any one of claims 1 to 6, characterized in that Different paging reason values correspond to different services.

8. The method according to claim 7, wherein The corresponding relationship between the paging cause value and the service is pre-configured or agreed upon by a protocol, or the corresponding relationship between the paging cause value and the service is configured by the network device.

9. The method according to any one of claims 1 to 6, characterized in that The first information is carried by registration response information, wherein the registration response information is response information to the registration request information sent by the terminal device.

10. The method according to any one of claims 1 to 6, characterized in that The first information is carried by information broadcast by the network device.

11. The method according to claim 10, wherein The first information is carried by information broadcast by the network device before executing a radio resource control RRC connection establishment process and / or executing a registration process.

12. The method according to any one of claims 1 to 6, characterized in that The first information is carried through signaling in a protocol data unit (PDU) session establishment process, or the first information is carried through signaling in a PDU session modification process.

13. The method according to any one of claims 1 to 6, characterized in that The first information is carried through RRC signaling.

14. A wireless communication method, characterized in that: include: The network device sends first information to the terminal device, where the first information includes at least one of the following: The paging cause values supported by the network device and the paging cause values to which the terminal device needs to respond; The paging cause values supported by the network device satisfy at least one of the following: Different public land mobile network (PLMN) identifiers correspond to different paging cause values supported by the network device; Different tracking area indication TAI lists correspond to different paging cause values supported by the corresponding network device; Different cell identifiers correspond to different paging cause values supported by the network device; Different radio access network RAN node identifiers correspond to different paging cause values supported by the network device; Before the network device sends the first information, the method further includes: The network device receives a second message from the terminal device, where the second message includes a paging cause value supported by the terminal device; The network device determines the first information according to a paging cause value supported by the terminal device; The paging cause values supported by the terminal device include: The terminal device can provide a paging cause value for the user to set service options, or the terminal device can identify the paging cause value.

15. The method according to claim 14, wherein The paging cause value supported by the network device is a paging cause value that the network device can detect and / or add to a paging message.

16. The method according to claim 14, wherein The network device sending first information to the terminal device includes: The network device sends the first information to the terminal device via at least one of an access layer AS layer message, a non-access layer NAS layer message, a broadcast message, and a user plane message.

17. The method according to claim 14, wherein The first information is used by the terminal device to provide setting options for the user, and the options set by the user are used by the terminal device to determine whether to respond to the paging message.

18. The method according to claim 14, wherein The paging cause values supported by the network device change as the location of the terminal device changes; and / or, The paging cause values supported by the network device change over time.

19. The method according to claim 14, wherein The second message is at least one of an AS message, a NAS message, and a user plane message.

20. The method according to any one of claims 14 to 19, characterized in that Different paging reason values correspond to different services.

21. The method according to claim 20, wherein The corresponding relationship between the paging cause value and the service is pre-configured or agreed upon by a protocol, or the corresponding relationship between the paging cause value and the service is configured by the network device.

22. The method according to any one of claims 14 to 19, wherein The first information is carried by registration response information, wherein the registration response information is response information to the registration request information sent by the terminal device.

23. The method according to any one of claims 14 to 19, characterized in that The first information is carried by information broadcast by the network device.

24. The method according to claim 23, wherein The first information is carried by information broadcast by the network device before executing a radio resource control RRC connection establishment process and / or executing a registration process.

25. The method according to any one of claims 14 to 19, characterized in that The first information is carried through signaling in a protocol data unit (PDU) session establishment process, or the first information is carried through signaling in a PDU session modification process.

26. The method according to any one of claims 14 to 19, wherein The first information is carried through RRC signaling.

27. A terminal device, characterized in that: include: A communication unit, configured to receive first information sent by a network device, wherein the first information includes at least one of the following: The paging cause values supported by the network device and the paging cause values to which the terminal device needs to respond; The paging cause values supported by the network device satisfy at least one of the following: Different public land mobile network (PLMN) identifiers correspond to different paging cause values supported by the network device; Different tracking area indication TAI lists correspond to different paging cause values supported by the corresponding network device; Different cell identifiers correspond to different paging cause values supported by the network device; Different radio access network RAN node identifiers correspond to different paging cause values supported by the network device; Before the terminal device receives the first information, the communication unit is further configured to send a second message to the network device, where the second message includes a paging cause value supported by the terminal device, and the first information is determined based on the paging cause value supported by the terminal device; The paging cause values supported by the terminal device include: The terminal device can provide a paging cause value for the user to set service options, or the terminal device can identify the paging cause value.

28. The terminal device according to claim 27, wherein: The paging cause value supported by the network device is a paging cause value that the network device can detect and / or add to a paging message.

29. The terminal device according to claim 27, wherein: The communication unit is specifically used for: Receive the first information sent by the network device through at least one of an access layer AS layer message, a non-access layer NAS layer message, a broadcast message, and a user plane message.

30. The terminal device according to claim 27, wherein: The terminal device further includes: A processing unit is used to provide setting options for the user according to the first information, and the options set by the user are used by the terminal device to determine whether to answer the paging message.

31. The terminal device according to claim 27, wherein: The paging cause values supported by the network device change as the location of the terminal device changes; and / or, The paging cause values supported by the network device change over time.

32. The terminal device according to claim 27, wherein: The second message is at least one of an AS message, a NAS message, and a user plane message.

33. The terminal device according to any one of claims 27 to 32, characterized in that: Different paging reason values correspond to different services.

34. The terminal device according to claim 33, wherein: The corresponding relationship between the paging cause value and the service is pre-configured or agreed upon by a protocol, or the corresponding relationship between the paging cause value and the service is configured by the network device.

35. The terminal device according to any one of claims 27 to 32, characterized in that: The first information is carried by registration response information, wherein the registration response information is response information to the registration request information sent by the terminal device.

36. The terminal device according to any one of claims 27 to 32, characterized in that: The first information is carried by information broadcast by the network device.

37. The terminal device according to claim 36, wherein: The first information is carried by information broadcast by the network device before executing a radio resource control RRC connection establishment process and / or executing a registration process.

38. The terminal device according to any one of claims 27 to 32, characterized in that: The first information is carried through signaling in a protocol data unit (PDU) session establishment process, or the first information is carried through signaling in a PDU session modification process.

39. The terminal device according to any one of claims 27 to 32, characterized in that: The first information is carried through RRC signaling.

40. A network device, characterized in that: include: A communication unit, configured to send first information to a terminal device, wherein the first information includes at least one of the following: The paging cause values supported by the network device and the paging cause values to which the terminal device needs to respond; The paging cause values supported by the network device satisfy at least one of the following: Different public land mobile network (PLMN) identifiers correspond to different paging cause values supported by the network device; Different tracking area indication TAI lists correspond to different paging cause values supported by the corresponding network device; Different cell identifiers correspond to different paging cause values supported by the network device; Different radio access network RAN node identifiers correspond to different paging cause values supported by the network device; Before the network device sends the first information, the communication unit is further configured to receive a second message from the terminal device, where the second message includes a paging cause value supported by the terminal device; a processing unit, configured to determine the first information according to a paging cause value supported by the terminal device; The paging cause values supported by the terminal device include: The terminal device can provide a paging cause value for the user to set service options, or the terminal device can identify the paging cause value.

41. The network device according to claim 40, wherein: The paging cause value supported by the network device is a paging cause value that the network device can detect and / or add to a paging message.

42. The network device according to claim 40, wherein: The communication unit is specifically used for: The first information is sent to the terminal device via at least one of an access layer AS layer message, a non-access layer NAS layer message, a broadcast message, and a user plane message.

43. The network device according to claim 40, wherein: The first information is used by the terminal device to provide setting options for the user, and the options set by the user are used by the terminal device to determine whether to respond to the paging message.

44. The network device according to claim 40, wherein: The paging cause values supported by the network device change as the location of the terminal device changes; and / or, The paging cause values supported by the network device change over time.

45. The network device according to claim 40, wherein: The second message is at least one of an AS message, a NAS message, and a user plane message.

46. The network device according to any one of claims 40 to 45, characterized in that Different paging reason values correspond to different services.

47. The network device according to claim 46, wherein: The corresponding relationship between the paging cause value and the service is pre-configured or agreed upon by a protocol, or the corresponding relationship between the paging cause value and the service is configured by the network device.

48. The network device according to any one of claims 40 to 45, characterized in that The first information is carried by registration response information, wherein the registration response information is response information to the registration request information sent by the terminal device.

49. The network device according to any one of claims 40 to 45, wherein: The first information is carried by information broadcast by the network device.

50. The network device according to claim 49, wherein: The first information is carried by information broadcast by the network device before executing a radio resource control RRC connection establishment process and / or executing a registration process.

51. The network device according to any one of claims 40 to 45, characterized in that The first information is carried through signaling in a protocol data unit (PDU) session establishment process, or the first information is carried through signaling in a PDU session modification process.

52. The network device according to any one of claims 40 to 45, characterized in that The first information is carried through RRC signaling.

53. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 13.

54. A network device, characterized in that include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 14 to 26.

55. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 13.

56. A chip, characterized in that include: A processor, configured to call and execute a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 14 to 26.

57. A computer-readable storage medium, characterized in that Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 13.

58. A computer-readable storage medium, characterized in that Used to store a computer program, the computer program causing a computer to execute the method according to any one of claims 14 to 26.

59. A computer program product, characterized in that The method comprises computer program instructions for causing a computer to execute the method according to any one of claims 1 to 13.

60. A computer program product, characterized in that The method comprises computer program instructions for causing a computer to perform the method according to any one of claims 14 to 26.

Images