WO2022094804A1

WO2022094804A1 - Wireless communication method, terminal device, and network device

Info

Publication number: WO2022094804A1
Application number: PCT/CN2020/126533
Authority: WO
Inventors: 许阳
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-11-04
Filing date: 2020-11-04
Publication date: 2022-05-12
Also published as: CN116261887A

Abstract

Embodiments of the present application provide a wireless communication method, a terminal device, and a network device, capable of avoiding a deviation between a setting of a user and an actual behavior of a terminal, so as to improve user experience. The wireless communication method comprises: a terminal device receives first information sent by a network device, the first information comprising at least one of the following: a paging cause value supported by the network device, and a paging cause value that 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

Method, terminal device and network device for wireless communication

technical field

The embodiments of the present application relate to the field of communications, and more particularly, to a wireless communication method, terminal device, and network device.

Background technique

The paging process is used for the terminal equipment in the connection management idle (Connection Management-Idle, CM-IDLE) state or the radio resource control deactivation (Radio Resource Connection-Inactive, RRC-Inactive) state, when there is 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 (Non Access Stratum, NAS) message or an access stratum (Access Stratum, AS) message to establish a user plane connection to transfer data. In addition, the terminal device can learn the reason for triggering paging based on the paging cause (Paging Cause) carried in the paging message. In the case that multiple paging causes have multiple values, the user is required to determine a specific paging cause Whether the paging message corresponding to the value is important or requires a reply. However, in some cases, the paging cause value type broadcasted by the network device may be determined based on the network itself, thereby causing a deviation between the user's settings and the actual behavior of the terminal, affecting user experience.

SUMMARY OF THE INVENTION

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

In a first aspect, a method for wireless communication is provided, the method comprising:

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

The paging cause value supported by the network device, the paging cause value that the terminal device needs to answer.

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 the paging message.

Optionally, 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 answer the paging message.

In a second aspect, a method for wireless communication is provided, the method comprising:

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

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

In a third aspect, a terminal device is provided for executing the method in the above-mentioned first aspect.

Specifically, the terminal device includes functional modules for executing the method in the first aspect.

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

Specifically, the network device includes functional modules for executing the method in the second aspect above.

In a fifth aspect, a terminal device is provided, including a processor and a memory. 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 execute the method in the first aspect.

In a sixth aspect, a network device is provided, including a processor and a memory. 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 execute the method in the second aspect.

In a seventh aspect, an apparatus is provided for implementing the method in any one of the above-mentioned first to second aspects.

Specifically, the apparatus includes: a processor for invoking and running a computer program from a memory, so that a device on which the apparatus is installed executes the method in any one of the first to second aspects above.

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

In a ninth aspect, a computer program product is provided, comprising computer program instructions, the computer program instructions causing a computer to perform the method in any one of the first to second aspects above.

In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the above-mentioned first to second aspects.

Through the above technical solutions, the terminal device obtains the paging cause value supported by the network device and/or the paging cause value that the terminal device needs to answer, so that the terminal device can provide the user with reasonable setting options accordingly, thereby improving user experience.

Description of drawings

FIG. 1 is a schematic diagram of a communication system architecture to which an embodiment of the present application is applied.

FIG. 2 is a schematic diagram of a paging process in a CM-IDLE state provided by the present application.

FIG. 3 is a schematic diagram of a paging process in an RRC-Inactive state provided by the present application.

FIG. 4 is a schematic diagram of another paging process in the CM-IDLE state provided by the present application.

FIG. 5 is a schematic diagram of another paging process in the RRC-Inactive state provided by the present application.

FIG. 6 is a schematic flowchart of a method for wireless communication according to an embodiment of the present application.

FIG. 7 is a schematic flowchart of indicating a paging cause value according to an embodiment of the present application.

FIG. 8 is another schematic flowchart of indicating a paging cause value according to an embodiment of the present application.

FIG. 9 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

FIG. 10 is a schematic block diagram of a network device provided according to an embodiment of the present application.

FIG. 11 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

Fig. 12 is a schematic block diagram of an apparatus provided according to an embodiment of the present application.

FIG. 13 is a schematic block diagram of a communication system provided according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. With regard to the embodiments in the present application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

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

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 communication, but also support, for example, Device to Device (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.

Optionally, the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.

Optionally, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered as a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to a licensed spectrum, where, Licensed spectrum can also be considered unshared spectrum.

The embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, where the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

The terminal device may be a station (STATION, ST) in the WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a Wireless Local Loop (WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as end devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In this embodiment of the present application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites) superior).

In this embodiment of the present application, the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.

As an example and not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, 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 clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones. Use, such as all kinds of smart bracelets, smart jewelry, etc. for physical sign monitoring.

In this embodiment of the present application, the network device may be a device for communicating with a mobile device, and the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA , it can also be a base station (NodeB, NB) in WCDMA, it can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or in-vehicle equipment, wearable devices and NR networks The network equipment or base station (gNB) in the PLMN network or the network equipment in the future evolved PLMN network or the network equipment in the NTN network, etc.

As an example and not a limitation, in this embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Optionally, 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 in a location such as land or water.

In this embodiment of the present application, a network device may provide services for a cell, and a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device ( For example, the cell corresponding to the base station), the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell). Pico cell), Femto cell (Femto cell), etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

Exemplarily, a communication system 100 to which this embodiment of the present application is applied is shown in FIG. 1 . The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). The network device 110 may provide communication coverage for a particular geographic area, and may communicate with terminal devices located within the coverage area.

FIG. 1 exemplarily shows one network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. This application The embodiment does not limit this.

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

It should be understood that, in the embodiments of the present application, a device having a communication function in the network/system may be referred to as a communication device. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here. ; The communication device may also include other devices in the communication system 100, such as other network entities such as a network controller, a mobility management entity, etc., which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

The terms used in the embodiments of the present application are only used to explain specific embodiments of the present application, and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" in the description and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order . Furthermore, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion.

It should be understood that the "instruction" mentioned in the embodiments of the present application may be a direct instruction, an indirect instruction, or an associated relationship. For example, if A indicates B, it can indicate that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indicates B indirectly, such as A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect corresponding relationship between the two, or may indicate that there is an associated relationship between the two, or indicate and be instructed, configure and be instructed configuration, etc.

In this embodiment of the present application, "predefinition" may be implemented by pre-saving corresponding codes, forms, or other means that can be used to indicate relevant information in devices (for example, including terminal devices and network devices). The implementation method is not limited. For example, predefined may refer to the definition in the protocol.

In the embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, may include the LTE protocol, the NR protocol, and related protocols applied in future communication systems, which are not limited in this application.

In order to facilitate a better understanding of the embodiments of the present application, a paging process related to the present application is described.

The paging process is used when the terminal is in the 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, and the terminal device receives the paging message to initiate a NAS message (such as Service Request) or AS messages (such as RRC Resume) establish user plane connections to transmit data.

The paging message is a plaintext message, and one paging message contains multiple UE identities (Identities, IDs), that is to say, one paging message can simultaneously page multiple UEs.

When the terminal device is in the CM-IDLE state (that is, 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 Figure 2. Show.

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

S12, the radio access network (Radio Access Network, RAN) device forwards the paging message to the terminal device;

S13, the terminal device replies to the paging message, such as sending a service request (Service Request) message to activate the NAS connection or the PDU session;

S14, establish a radio resource control (Radio Resource Control, RRC) connection between the terminal device and the RAN device, for example, the terminal device sends an RRC setup request (RRC Setup request) message to establish an RRC connection;

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

The terminal device is in RRC-Inactive (that is, 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), and the paging process includes S21-S24, Specifically as shown in Figure 3.

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

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

S23, the terminal device replies to the paging message;

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 (RRC Setup request) message to establish the RRC connection.

In order to allow the terminal to respond to the paging message more effectively (for example, the low-priority service does not respond to its paging message; or when the terminal user performs services on the Universal Subscriber Identity Module, USIM)-1, the USIM -2 After receiving the paging message, the terminal user decides not to respond to avoid service interruption on USIM-1), the paging message can be enhanced, that is, the paging cause (Paging Cause) parameter is added to the paging message, the paging cause A downlink data packet indicating what service arrives at the network triggers a paging message. In this way, the terminal device can know what triggers the paging message according to the paging reason, so as to decide whether to respond.

For example, the paging process in the CM-IDLE state includes S31-S34, as shown in FIG. 4 .

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

S32, the core network device derives the paging reason information according to the DSCP value carried by the downlink data;

S33, the core network device sends a paging message to the RAN device, which carries the paging reason;

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

S35, the terminal device decides whether to reply according to the paging reason;

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

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

S41, the application server sends downlink data to the core network device, which carries the DSCP value;

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

S43, the RAN device derives the paging cause information according to the parameters related to the paging cause;

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

S45, the terminal device decides whether to reply according to the paging reason;

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

It should be noted that the specific content of the paging reason is that the core network device or the RAN device according to the information carried in the downlink (Downlink, DL) data packet, such as the type of service (Type of Service) in the Internet Protocol (Internet Protocol, IP) data packet header. , ToS) field (sometimes also become DSCP value). That is to say, the information carried in the downlink data packet can indicate what the service corresponding to the data packet is, and then the core network device or the RAN device sends it to the terminal device through the paging reason based on this.

The paging cause value can be divided into two types: standardized and non-standardized. Standardized value refers to standardizing the mapping relationship between specific values and services. Different networks need to follow the corresponding relationship. Non-standardized values refer to the different mapping relationships between specific values and services in each network (different network The relationship corresponding to the following different values may be different), and part of the value range in the paging reason parameter can be used for the unique content corresponding relationship of the network itself.

When multiple paging causes have multiple values, the terminal user needs to decide whether the paging message corresponding to the specific paging cause value is important or whether it needs to be replied, which is usually set by the user. Since the current terminal does not know the paging cause values that are supported or can be broadcasted in the network, a discrepancy occurs between the user's settings and the actual behavior of the terminal. Specific examples are as follows:

The PLMN-1 network registered by USIM-1 supports three Paging Cause values of IP Multimedia Subsystem (IMS) voice, short message and CP signaling. Users can pre-configure USIM-1. IMS voice and SMS message services are important and control plane (Control Plane, CP) signaling is not important, which means that paging messages corresponding to IMS voice and SMS messages must be replied, while The paging message corresponding to the CP signaling does not need to be replied.

However, when the user switches from PLMN-1 to PLMN-2, the network under PLMN-2 only supports two options of IMS voice and CP signaling, that is to say, the paging message will never carry Paging Cause=SMS. In this way, the terminal of USIM-1 does not know whether the paging message corresponds to the SMS short message service, and therefore cannot determine whether it must reply to the paging message. As a result, there is a deviation between user needs and actual terminal behavior, which affects user experience.

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

The technical solutions of the present application are described in detail below through specific embodiments.

FIG. 6 is a schematic flowchart of a method 200 for wireless communication according to an embodiment of the present application. As shown in FIG. 6 , the method 200 may include at least part of the following contents:

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

The paging cause value supported by the network device, the paging cause value that the terminal device needs to answer;

S220, the terminal device receives the first information.

It should be noted that the paging cause value supported by the network device is a paging cause value that the network device can detect and/or add to the paging message.

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 for which the paging cause value corresponds; For example, the terminal device sends an RRC recovery request message to recover the RRC connection, and sends a service request message to receive the service corresponding to the paging cause value.

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 a paging cause value in the paging message, it must support the same paging cause value ( For example, all standardized paging cause values must be supported), so that the terminal device can provide users with correct setting options, which can avoid the occurrence of services corresponding to paging cause values that are not supported by the network side in the setting options.

As another optional method, the above-mentioned first information, such as the paging cause values supported by one or more PLMNs, is preconfigured on the terminal device, so that the terminal device can provide the user with correct setting options, which can avoid setting The service corresponding to the paging cause value not supported by the network side appears in the options. The "pre-configuration" may be a factory setting, a setting written in the SIM card and read from the SIM by the terminal device, and a configuration obtained by the terminal device through the Over the Air (OTA) technology.

In this embodiment of the present application, the network device may support one or more paging cause values.

Optionally, the network device may send the network device through at least one of an access stratum (Access Stratum, AS) layer message, a non-access stratum (Non-Access Stratum, NAS) layer message, a broadcast message, and a user plane message. first information.

The user plane message may be a connection established between the server and the terminal device through the user plane (such as an application layer Hyper Text Transfer Protocol (Hyper Text 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 through an HTTP connection.

The embodiments of the present application may be applicable to a 5G system (5GS), an evolved packet system (Evolved Packet System, EPS), and future networks.

Optionally, in this embodiment of the present application, the terminal device may provide setting options for the user according to the first information, and the options set by the user are used for the terminal device to determine whether to answer the paging message. Therefore, it is possible to avoid the occurrence of a service corresponding to a paging cause value that is not supported by the network side in the setting options.

For example, the terminal device may provide the user with setting options according to the first information. The business in the setting options can correspond to the paging cause value. The user can set the importance of each business or set whether a response is required when a certain business occurs. The terminal device can decide whether to respond to the paging cause corresponding to a certain business according to the user settings. value of the paging message. For example, if a voice service comes and needs to be answered, the terminal responds to the paging message every time it subsequently receives a paging message sent to USIM-2 that contains Paging cause=voice. In the setting options, the states of the two USIM cards can also be considered, for example, when the USIM-1 is conducting data services, the USIM-2 is in an idle state, or vice versa. Another example is that when the USIM-1 is browsing the web page, there is a voice service on the USIM-2.

Optionally, in some embodiments, the paging cause value supported by the network device changes as the location of the terminal device changes; and/or, the paging cause value supported by the network device changes with time. Change.

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

Different PLMN identities have different paging cause values supported by the corresponding network equipment;

Different Tracking Area Indicator (TAI) lists have different paging cause values supported by corresponding network devices;

Different cell identities have different paging cause values supported by the corresponding network equipment;

Different RAN node identifiers have different paging cause values supported by the corresponding network equipment.

That is to say, the paging cause value supported by the network device can be delivered to the terminal device according to the granularity of radio access technology (Radio Access Technology, RAT), PLMN identifier, TAI list, Cell identifier, and RAN node identifier.

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

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.

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.

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.

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.

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

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.

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.

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

Optionally, the corresponding relationship between the paging cause value and the service is pre-configured or agreed in a protocol, or the corresponding relationship between the paging cause value and the service is configured by the network device.

That is to say, the correspondence between the paging cause value and the service may be a standardized correspondence or a unique correspondence of different networks.

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

That is, before receiving the first information, the terminal device sends the second message to the network device.

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

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 device are 2, 3, and 4, the network device can inform the terminal device of the paging it supports in the first information. The reason values are 2 and 3.

Optionally, in some embodiments, the first information is carried by registration response information, where the registration response information is response information to the registration request information sent by the terminal device.

For example, the terminal device sends registration request information to the network device, and the network device sends registration response information for the registration request information to the terminal device, where the registration response information carries the first information. Optionally, the registration request information may carry a paging cause value supported by the terminal device.

Optionally, in some embodiments, the first information is carried through information broadcast by the network device.

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

Optionally, in some embodiments, the first information is carried by signaling in a protocol data unit (Protocol Data Unit, PDU) session establishment process, or the first information is carried by signaling in a PDU session modification process .

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

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

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

Therefore, in this embodiment of the present application, the terminal device obtains the paging cause value supported by the network device and/or the paging cause value that the terminal device needs to answer, so that the terminal device can provide the user with reasonable setting options accordingly, thereby improving the user experience. experience.

Further, before executing the RRC connection establishment procedure and/or executing the registration procedure, the information broadcast by the network device carries the paging cause value supported by the network device and/or the paging cause value that the terminal device needs to answer. Therefore, the terminal device can complete the user setting when establishing the RRC connection or the NAS connection, avoiding the need to perform the user setting after the terminal device is registered, thereby improving the user experience.

The technical solution of the present application will be described in detail below through two specific embodiments.

In Embodiment 1, the network device can indicate the paging cause value supported by the network device and/or the paging cause value that the terminal device needs to answer in the registration process, which can be specifically implemented through the processes S51-S53 shown in FIG. 7 .

S51, the terminal device sends registration request information to the core network device, optionally, the registration request information includes a paging cause value supported by the terminal device;

S52, the core network device sends registration response information for the registration request information to the terminal device, where the registration response information carries a paging cause value supported by the network device and/or a paging cause value that the terminal device needs to respond to;

S53: Optionally, the terminal device may provide setting options for the user according to the paging cause value supported by the network device and/or the paging cause value that the terminal device needs to answer, so as to avoid paging that is not supported by the network side in the setting options. The business corresponding to the cause value.

It should be noted that, if the core network device receives the paging cause value supported by the terminal device in S51, it may also refer to the paging cause value 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 of the paging cause values supported by the network side in S52. are 2 and 3.

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 identify. 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 shown in Figure 4 and Figure 5).

In Embodiment 2, the network device can indicate the paging cause value supported by the network device and/or the paging cause value that the terminal device needs to answer before performing the RRC connection establishment and registration process. Specifically, the process as shown in FIG. 8 can be used. S61-S62 implementation.

S61, the base station sends broadcast information to the terminal device, where the broadcast information carries the paging cause value supported by the network device and/or the paging cause value that the terminal device needs to answer;

S62, optionally, the terminal device may provide setting options for the user according to the paging cause value supported by the network device and/or the paging cause value that the terminal device needs to answer, so as to avoid paging that is not supported by the network side in the setting options. The business corresponding to the cause value.

In Embodiment 2, before executing the RRC connection establishment procedure and/or executing the registration procedure, the information broadcast by the network device carries the paging cause value supported by the network device and/or the paging cause value that the terminal device needs to answer. Therefore, the terminal device can complete the user setting when establishing the RRC connection or the NAS connection, avoiding the need to perform the user setting after the terminal device is registered, thereby improving the user experience.

The method embodiments of the present application are described in detail above with reference to FIGS. 6 to 8 , and the device embodiments of the present application are described in detail below with reference to FIGS. 9 to 13 . It should be understood that the device embodiments and method embodiments correspond to each other, and are similar to each other. For the description, refer to the method embodiment.

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

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

Optionally, the communication unit 310 is specifically used for:

The first information sent by the network device through 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 is received.

Optionally, the terminal device 300 further includes:

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

Optionally, the paging cause value supported by the network device changes as the location of the terminal device changes; and/or, the paging cause value supported by the network device changes with time.

Optionally, the paging cause value supported by the network device satisfies at least one of the following:

Different public land mobile network PLMN identities have different paging cause values supported by the corresponding network equipment;

Different tracking areas indicate TAI lists, and the corresponding paging cause values supported by the network device are different;

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.

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.

Optionally, the paging cause value supported by the terminal device includes: a paging cause value that the terminal device can provide to the user for setting service options, or a paging cause value that the terminal device can identify.

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

Optionally, different paging cause values correspond to different services.

Optionally, the first information is carried by registration response information, where the registration response information is response information to the registration request information sent by the terminal device.

Optionally, the first information is carried through information broadcast by the network device.

Optionally, the first information is carried by information broadcast by the network device before performing the RRC connection establishment procedure and/or the registration procedure.

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.

Optionally, the first information is carried through RRC signaling.

Optionally, in some embodiments, the above-mentioned 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 aforementioned processing unit may be one or more processors.

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 method embodiment of the present application, and the above-mentioned and other operations and/or functions of the various units in the terminal device 300 are respectively for realizing the method shown in FIG. 6 . The corresponding process of the terminal device in 200 is not repeated here for brevity.

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

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:

Optionally, the communication unit 410 is specifically used for:

The first information is sent to the terminal 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.

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

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;

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

Optionally, different paging cause values correspond to different services.

Optionally, the first information is carried through RRC signaling.

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 method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the network device 400 are respectively for realizing the method shown in FIG. 6 . The corresponding process of the network device in 200 is not repeated here for brevity.

FIG. 11 is a schematic structural diagram of a communication device 500 provided by an embodiment of the present application. The communication device 500 shown in FIG. 11 includes a processor 510, and the processor 510 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 11 , the communication device 500 may further include a memory 520 . The processor 510 may call and run a computer program from the memory 520 to implement the methods in the embodiments of the present application.

The memory 520 may be a separate device independent of the processor 510 , or may be integrated in the processor 510 .

Optionally, as shown in FIG. 11 , 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, may send information or data to other devices, or receive other Information or data sent by a device.

Among them, the transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include antennas, and the number of the antennas may be one or more.

Optionally, the communication device 500 may specifically be a network device in this 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 brevity, details are not repeated here. .

Optionally, the communication device 500 may specifically be the mobile terminal/terminal device of the embodiments of the present application, and the communication device 500 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and will not be repeated here.

FIG. 12 is a schematic structural diagram of an apparatus according to an embodiment of the present application. The apparatus 600 shown in FIG. 12 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so as to implement the method in this embodiment of the present application.

Optionally, as shown in FIG. 12 , the apparatus 600 may further include a memory 620 . The processor 610 may call and run a computer program from the memory 620 to implement the methods in the embodiments of the present application.

The memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .

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 acquire information or data sent by other devices or chips.

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

Optionally, the apparatus can be applied to the network equipment in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application, which are not repeated here for brevity.

Optionally, the apparatus can be applied to the mobile terminal/terminal equipment in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the mobile terminal/terminal equipment in each method of the embodiments of the present application. For brevity, here No longer.

Optionally, the device mentioned in the embodiment of the present application may also be a chip. For example, it can be a system-on-chip, a system-on-a-chip, a system-on-a-chip, or a system-on-a-chip.

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

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 brevity, details are not repeated here. .

It should be understood that the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. 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.

It can be understood that the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Wherein, the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may be Random Access Memory (RAM), which acts as an external cache. By way of illustration and not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

It should be understood that the above memory is an example but not a limitative description, for example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

Embodiments of the present application further provide a computer-readable storage medium for storing a computer program.

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 brevity, here No longer.

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 each method of the embodiments of the present application. , and are not repeated here for brevity.

Embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.

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 cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, For brevity, details are not repeated here.

The embodiments of the present application also provide a computer program.

Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application, and when the computer program is run on the computer, the mobile terminal/terminal device implements the various methods of the computer program in the embodiments of the present application. The corresponding process, for the sake of brevity, will not be repeated here.

Those of ordinary skill in the art can realize 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. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

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 alone, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. For such understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

A method of wireless communication, comprising:

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

The paging cause value supported by the network device, and the paging cause value that the terminal device needs to answer.
The method of 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.
The method according to claim 1 or 2, wherein the terminal device receives the first information sent by the network device, comprising:

The terminal device receives the first information sent by the network device through 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.
The method according to any one of claims 1 to 3, 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 answer the paging message.
The method of any one of claims 1 to 4, wherein,

The paging cause value supported by the network device changes with the location of the terminal device; and/or,

The paging cause values supported by the network device change over time.
The method according to any one of claims 1 to 5, wherein the paging cause value supported by the network device satisfies at least one of the following:

Different public land mobile network PLMN identities have different paging cause values supported by the corresponding network equipment;

Different tracking areas indicate TAI lists, and the corresponding paging cause values supported by the network device are different;

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.
The method of any one of claims 1 to 6, further comprising:

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.
The method of claim 7, wherein the paging cause value supported by the terminal device comprises:

The terminal device can provide the user with a paging cause value for setting service options, or a paging cause value that can be identified by the terminal device.
The method according to claim 7 or 8, wherein the second message is at least one of an AS message, a NAS message, and a user plane message.
The method according to any one of claims 1 to 9, wherein,

Different paging cause values correspond to different services.
The method of claim 10, wherein:

The corresponding relationship between the paging cause value and the service is pre-configured or agreed in the protocol, or the corresponding relationship between the paging cause value and the service is configured by the network device.
The method of any one of claims 1 to 11, wherein,

The first information is carried by registration response information, where the registration response information is response information to the registration request information sent by the terminal device.
The method of any one of claims 1 to 11, wherein,

The first information is carried through information broadcast by the network device.
The method of claim 13, wherein:

The first information is carried by the information broadcast by the network device before performing the RRC connection establishment procedure and/or the registration procedure.
The method of any one of claims 1 to 11, wherein,

The first information is carried by the signaling in the protocol data unit PDU session establishment process, or the first information is carried by the signaling in the PDU session modification process.
The method of any one of claims 1 to 11, wherein,

The first information is carried through RRC signaling.
A method of wireless communication, comprising:

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

The paging cause value supported by the network device, and the paging cause value that the terminal device needs to answer.
The method of claim 17, 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 the paging message.
The method according to claim 17 or 18, wherein the network device sends the first information to the terminal device, comprising:

The network device sends the first information to the terminal device through 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.
The method according to any one of claims 17 to 19, wherein the first information is used for the terminal device to provide setting options for the user, and the options set by the user are used for the terminal device to determine whether to Answer the paging message.
The method of any one of claims 17 to 20, wherein,

The paging cause value supported by the network device changes with the location of the terminal device; and/or,

The paging cause values supported by the network device change over time.
The method according to any one of claims 17 to 21, wherein the paging cause value supported by the network device satisfies at least one of the following:

Different public land mobile network PLMN identities have different paging cause values supported by the corresponding network equipment;

Different tracking areas indicate TAI lists, and the corresponding paging cause values supported by the network device are different;

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.
The method of any one of claims 17 to 22, further comprising:

receiving, by the network device, a second message sent by 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 method according to claim 23, wherein the paging cause value supported by the terminal device comprises: a paging cause value that the terminal device can provide to the user for setting service options, or the terminal device can Identified paging reason value
The method according to claim 23 or 24, wherein the second message is at least one of an AS message, a NAS message, and a user plane message.
The method of any one of claims 17 to 25, wherein,

Different paging cause values correspond to different services.
The method of claim 26, wherein

The corresponding relationship between the paging cause value and the service is pre-configured or agreed in the protocol, or the corresponding relationship between the paging cause value and the service is configured by the network device.
The method of any one of claims 17 to 27, wherein,

The first information is carried by registration response information, where the registration response information is response information to the registration request information sent by the terminal device.
The method of any one of claims 17 to 27, wherein,

The first information is carried through information broadcast by the network device.
The method of claim 29, wherein

The first information is carried by the information broadcast by the network device before performing the RRC connection establishment procedure and/or the registration procedure.
The method of any one of claims 17 to 27, wherein,

The first information is carried by the signaling in the protocol data unit PDU session establishment process, or the first information is carried by the signaling in the PDU session modification process.
The method of any one of claims 17 to 27, wherein,

The first information is carried through RRC signaling.
A terminal device, characterized in that it includes:

A communication unit, configured to receive first information sent by a network device, where the first information includes at least one of the following:

The paging cause value supported by the network device, and the paging cause value that the terminal device needs to answer.
The terminal device according to claim 33, 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 the paging message.
The terminal device according to claim 33 or 34, wherein the communication unit is specifically used for:

The first information sent by the network device through 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 is received.
The terminal device according to any one of claims 33 to 35, wherein the terminal device further comprises:

The processing unit is configured to provide setting options for the user according to the first information, and the options set by the user are used for the terminal device to determine whether to answer the paging message.
The terminal device according to any one of claims 33 to 36, wherein,

The paging cause value supported by the network device changes with the location of the terminal device; and/or,

The paging cause values supported by the network device change over time.
The terminal device according to any one of claims 33 to 37, wherein the paging cause value supported by the network device satisfies at least one of the following:

Different public land mobile network PLMN identities have different paging cause values supported by the corresponding network equipment;

Different tracking areas indicate TAI lists, and the corresponding paging cause values supported by the network device are different;

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.
The terminal device according to any one of claims 33 to 38, wherein 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.
The terminal device according to claim 39, wherein the paging cause value supported by the terminal device comprises: a paging cause value that the terminal device can provide to the user for setting service options, or the terminal device The paging reason value that can be identified.
The terminal device according to claim 39 or 40, wherein the second message is at least one of an AS message, a NAS message, and a user plane message.
The terminal device according to any one of claims 33 to 41, wherein,

Different paging cause values correspond to different services.
The terminal device of claim 42, wherein,

The corresponding relationship between the paging cause value and the service is pre-configured or agreed in the protocol, or the corresponding relationship between the paging cause value and the service is configured by the network device.
The terminal device according to any one of claims 33 to 43, wherein,

The first information is carried by registration response information, where the registration response information is response information to the registration request information sent by the terminal device.
The terminal device according to any one of claims 33 to 43, wherein,

The first information is carried through information broadcast by the network device.
The terminal device of claim 45, wherein,

The first information is carried by the information broadcast by the network device before performing the RRC connection establishment procedure and/or the registration procedure.
The terminal device according to any one of claims 33 to 43, wherein,

The first information is carried by the signaling in the protocol data unit PDU session establishment process, or the first information is carried by the signaling in the PDU session modification process.
The terminal device according to any one of claims 33 to 43, wherein,

The first information is carried through RRC signaling.
A network device, characterized in that it includes:

A communication unit, configured to send first information to the terminal device, where the first information includes at least one of the following:

The paging cause value supported by the network device, and the paging cause value that the terminal device needs to answer.
The network device according to claim 49, 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 the paging message.
The network device according to claim 49 or 50, wherein the communication unit is specifically used for:

The first information is sent to the terminal device through 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.
The network device according to any one of claims 49 to 51, wherein the first information is used for the terminal device to provide setting options for the user, and the options set by the user are used for the terminal device to determine Whether to answer paging messages.
The network device according to any one of claims 49 to 52, wherein,

The paging cause value supported by the network device changes with the location of the terminal device; and/or,

The paging cause values supported by the network device change over time.
The network device according to any one of claims 49 to 53, wherein the paging cause value supported by the network device satisfies at least one of the following:

Different public land mobile network PLMN identities have different paging cause values supported by the corresponding network equipment;

Different tracking areas indicate TAI lists, and the corresponding paging cause values supported by the network device are different;

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.
The network device according to any one of claims 49 to 54, the network device further comprising: a processing unit, wherein:

The communication unit 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;

The processing unit is configured to determine the first information according to the paging cause value supported by the terminal device.
The network device according to claim 55, wherein the paging cause value supported by the terminal device comprises: a paging cause value that the terminal device can provide to the user for setting service options, or the terminal device The paging reason value that can be identified.
The network device according to claim 55 or 56, wherein the second message is at least one of an AS message, a NAS message, and a user plane message.
The network device according to any one of claims 49 to 57, wherein,

Different paging cause values correspond to different services.
The network device of claim 58, wherein,

The corresponding relationship between the paging cause value and the service is pre-configured or agreed in the protocol, or the corresponding relationship between the paging cause value and the service is configured by the network device.
The network device according to any one of claims 49 to 59, wherein,

The first information is carried by registration response information, where the registration response information is response information to the registration request information sent by the terminal device.
The network device according to any one of claims 49 to 59, wherein,

The first information is carried through information broadcast by the network device.
The network device of claim 61, wherein,

The first information is carried by the information broadcast by the network device before performing the RRC connection establishment procedure and/or the registration procedure.
The network device according to any one of claims 49 to 59, wherein,

The first information is carried by the signaling in the protocol data unit PDU session establishment process, or the first information is carried by the signaling in the PDU session modification process.
The network device according to any one of claims 49 to 59, wherein,

The first information is carried through RRC signaling.
A terminal device, characterized in that it comprises: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 1 to 16. one of the methods described.
A network device, characterized in that it comprises: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute any one of claims 17 to 32. one of the methods described.
A chip, characterized by comprising: a processor for invoking and running a computer program from a memory, so that a device on which the chip is installed executes the method according to any one of claims 1 to 16 .
A chip, characterized by comprising: a processor for calling and running a computer program from a memory, so that a device installed with the chip executes the method according to any one of claims 17 to 32.
A computer-readable storage medium, characterized by being used for storing a computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 16.
A computer-readable storage medium, characterized by being used for storing a computer program, the computer program causing a computer to execute the method according to any one of claims 17 to 32.
A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 16.
A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 17 to 32.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1 to 16.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 17 to 32.