CN116261887A

CN116261887A - Wireless communication method, terminal equipment and network equipment

Info

Publication number: CN116261887A
Application number: CN202080105173.3A
Authority: CN
Inventors: 许阳
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-11-04
Filing date: 2020-11-04
Publication date: 2023-06-13
Also published as: WO2022094804A1

Abstract

The embodiment of the application provides a wireless communication method, terminal equipment and network equipment, which can avoid deviation between the setting of a user and the actual behavior of the terminal, thereby improving the user experience. The method of wireless communication includes: the terminal equipment receives first information sent by the network equipment, wherein the first information comprises at least one of the following: paging cause value supported by the network equipment, paging cause value that the terminal equipment needs to answer; the paging cause value supported by the network device is a paging cause value that the network device can detect and/or add in a paging message.

Description

Wireless communication method, terminal equipment and network equipment

Technical Field

The embodiment of the application relates to the field of communication, and more particularly, to a wireless communication method, terminal equipment and network equipment.

Background

The Paging procedure is used for the terminal device to establish a user plane connection to transmit data by sending a Paging (Paging) message to the terminal device at the network side when downlink user plane data arrives in a connection management Idle (Connection Management-Idle) state or a radio resource control deactivation (Radio Resource Connection-Inactive, RRC-Inactive) state, and after the terminal device receives the Paging message, initiating a non-Access Stratum (Non Access Stratum, NAS) message or an Access Stratum (AS) message. In addition, the terminal device may learn the reason for triggering Paging based on the Paging Cause (Paging Cause) carried in the Paging message, and in the case that multiple Paging causes have multiple values, the user is required to determine whether the Paging message corresponding to the specific Paging Cause value is important or whether the Paging message needs to be replied. However, in some cases, the paging cause value type broadcasted by the network device may be determined based on the network itself, so that a deviation between the user's setting and the actual behavior of the terminal is caused, and the user experience is affected.

Disclosure of Invention

The embodiment of the application provides a wireless communication method, terminal equipment and network equipment, which can avoid deviation between the setting of a user and the actual behavior of the terminal, thereby improving the user experience.

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

the terminal equipment receives first information sent by the network equipment, wherein the first information comprises at least one of the following:

paging cause value supported by the network device, and paging cause value to be answered by the terminal device.

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

Optionally, the terminal device provides a setting option for the user according to the first information, and the user-set option is used for the terminal device to determine whether to answer the paging message.

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

the network device sends first information to the terminal device, wherein the first information comprises at least one of the following:

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

In a third aspect, a terminal device is provided for performing the method in the first aspect.

Specifically, the terminal device comprises functional modules for performing the method in the first aspect described above.

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

In particular, the network device comprises functional modules for performing the method in the second aspect described above.

In a fifth aspect, a terminal device is provided comprising a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the method in the first aspect.

In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect described above.

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

Specifically, the device comprises: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method of any of the first to second aspects as described above.

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

In a ninth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of 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 of the first to second aspects described above.

Through the technical scheme, the terminal equipment acquires the paging cause value supported by the network equipment and/or the paging cause value to be responded by the terminal equipment, so that the terminal equipment provides reasonable setting options for the user according to the paging cause value, and the user experience can be improved.

Drawings

Fig. 1 is a schematic diagram of a communication system architecture to which embodiments of the present application apply.

Fig. 2 is a schematic diagram of a CM-IDLE paging procedure provided in the present application.

Fig. 3 is a schematic diagram of a paging procedure in RRC-Inactive state provided in the present application.

Fig. 4 is a schematic diagram of another CM-IDLE state paging procedure provided in the present application.

Fig. 5 is a schematic diagram of another paging procedure in RRC-Inactive state provided in the present application.

Fig. 6 is a schematic flow chart diagram of a method of wireless communication provided in accordance with an embodiment of the present application.

Fig. 7 is a schematic flow chart of indicating paging cause values according to an embodiment of the present application.

Fig. 8 is a schematic flow chart of another indication paging cause value provided according to an embodiment of the present application.

Fig. 9 is a schematic block diagram of a terminal device 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 in accordance with 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 Description

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden for the embodiments herein, are intended to be within the scope of the present application.

The technical solution of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, long term evolution advanced (Advanced long term evolution, LTE-a) system, new Radio, NR system evolution system, LTE over unlicensed spectrum (LTE-based access to unlicensed spectrum, LTE-U) system, NR over unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, universal mobile telecommunication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, or internet of vehicles (Vehicle to everything, V2X) communication, etc., and the embodiments of the present application may also be applied to these communication systems.

Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, and a Stand Alone (SA) fabric scenario.

Optionally, the communication system in the embodiments of the present application may be applied to unlicensed spectrum, where unlicensed spectrum may also be considered as shared spectrum; alternatively, the communication system in the embodiments of the present application may also be applied to licensed spectrum, where licensed spectrum may also be considered as non-shared spectrum.

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

The terminal device may be a STATION (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) STATION, a personal digital assistant (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 (Public Land Mobile Network, PLMN) network, etc.

In embodiments of the present application, the terminal device may be deployed on land, including indoor or outdoor, hand-held, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).

In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned driving (self driving), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (smart city), or a wireless terminal device in smart home (smart home), and the like.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various 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, where the network device may be an Access Point (AP) in a WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, a relay station or an Access Point, a vehicle device, a wearable device, a network device or a base station (gNB) in an NR network, a network device in a PLMN network of future evolution, or a network device in an NTN network, etc.

By way of example and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.

In this embodiment of the present application, a network device may provide a service for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to a network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

Exemplary, a communication system 100 to which embodiments of the present application apply 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, terminal). 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 illustrates one network device and two terminal devices by way of example, and alternatively, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage area of each network device, which is not limited in this embodiment of the present application.

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

It should be understood that a device having a communication function in a network/system in an embodiment of the present application 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 communication functions, where the network device 110 and the terminal device 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

The terminology used in the description section of the present application is for the purpose of describing particular embodiments of the present application only and is not intended to be limiting of the present application. The terms "first," "second," "third," and "fourth" and the like in the description and in the claims of this application and in the drawings, are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion.

It should be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, or the like.

In the embodiment of the present application, the "predefining" may be implemented by pre-storing corresponding codes, tables or other manners that may be used to indicate relevant information in devices (including, for example, terminal devices and network devices), and the specific implementation of the present application is not limited. Such as predefined may refer to what is defined in the protocol.

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

To facilitate a better understanding of embodiments of the present application, paging procedures related to the present application are described.

The paging procedure is used for the terminal to establish user plane connection for transmitting data by receiving a paging message initiating NAS message (such AS Service Request) or an AS message (such AS RRC response) by the terminal in the CM-IDLE or RRC-Inactive state, when downlink user plane data arrives at the network, the network side sends the paging message to search for the terminal.

The paging message is a plaintext message, and one paging message has a plurality of UE Identities (IDs), that is, one paging message can page a plurality of UEs at the same time.

The paging procedure includes S11-S14 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), as shown in fig. 2.

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

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

s13, the terminal equipment replies to the paging message, such as sending a Service Request (Service Request) message to activate the NAS connection or PDU session;

s14, establishing a radio resource control (Radio Resource Control, RRC) connection between the terminal device and the RAN device, e.g., the terminal device sends an RRC establishment request (RRC Setup request) message, establishing an RRC connection;

s15, the terminal equipment sends service request information to the core network equipment.

The terminal device is in RRC-active (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), and the paging procedure comprises S21-S24, as shown in particular in fig. 3.

S21, the core network equipment sends downlink user plane data aiming at the terminal equipment to the RAN equipment;

s22, the RAN equipment sends a paging message to the terminal equipment;

s23, the terminal equipment replies the paging message;

s24, establishing RRC connection between the terminal equipment and the RAN equipment. Such as the terminal device initiating an RRC resume request (RRC Resume request) message, resuming the RRC connection, or the terminal device sending an RRC setup request (RRC Setup request) message, establishing the RRC connection.

In order to enable the terminal to respond to the Paging message more effectively (such as not responding to the Paging message for low priority service, or when the terminal user performs service on the universal subscriber identity module (Universal Subscriber Identity Module, USIM) -1, the USIM-2 receives the Paging message, and the terminal user decides not to respond to avoid interruption of service on the USIM-1), the Paging message can be enhanced, namely a Paging Cause (Paging Cause) parameter is added in the Paging message, and the Paging Cause is used for indicating what service downlink data packet arrives at the network, so that the Paging message is triggered. In this way, the terminal device can learn what triggered paging messages are based on the paging cause to decide whether to respond.

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

S31, an application server sends downlink data to core network equipment, wherein the downlink data carries differential service code point (Differentiated Services Code Point, DSCP) values;

s32, the core network equipment derives paging cause information according to the DSCP value carried by the downlink data;

s33, the core network equipment sends a paging message to the RAN equipment, wherein the paging message carries paging reasons;

s34, the RAN equipment sends a paging message to the terminal equipment, wherein the paging message carries paging reasons;

s35, the terminal equipment decides whether to reply according to the paging reason;

s36, the terminal equipment sends a reply message to the core network equipment, wherein the reply message carries service request information.

For example, the paging procedure in the RRC-active state includes S41-S44, as shown in fig. 5.

S41, an application server sends downlink data to core network equipment, wherein the downlink data carries a DSCP value;

s42, the core network device sends a downlink PDU data packet to the RAN device, wherein the downlink PDU data packet carries paging reason related parameters;

s43, the RAN equipment derives paging reason information according to the paging reason related parameters;

s44, the RAN equipment sends a paging message to the terminal equipment, wherein the paging message carries paging reasons;

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

s46, the terminal equipment sends a reply message to the core network equipment, wherein the reply message carries service request information.

It should be noted that the specific content of the paging cause is obtained by the core network device or the RAN device according to information carried in a Downlink (DL) packet, such as a content (sometimes also referred to as DSCP value) in a Type of Service (ToS) field in an internet protocol (Internet Protocol, IP) packet header. That is, the information carried in the downlink data packet may indicate what the service corresponding to the data packet is, and then the core network device or the RAN device sends the information to the terminal device through the paging cause based on the information.

Paging cause values can be divided into two values, standardized and non-standardized. The standardized value refers to standardized mapping relation between a specific value and a service, different networks need to follow the corresponding relation, the non-standardized value refers to different mapping relation between the specific value and the service in each network (the corresponding relation between different values under different networks can be different), and part of value ranges in paging cause parameters can be used for content corresponding relation unique to the network.

When there are multiple paging causes, the terminal user is required to determine whether the paging message corresponding to the specific paging cause is important or needs to be replied, and a preset manner is usually adopted. The current terminal does not know which paging reasons supported or broadcasted in the network have values, so that errors occur between the user setting and the actual behavior of the terminal. Specific examples are as follows:

three Paging Cause values are supported in the PLMN-1 network registered by USIM-1 for voice, SMS and CP signaling of the IP multimedia subsystem (IP Multimedia Subsystem, IMS). The user may configure USIM-1 in advance that IMS voice and SMS short message service is important and Control Plane (CP) signaling is not important, which means that paging messages corresponding to IMS voice and SMS short messages must be replied to, and paging messages corresponding to CP signaling need not be replied to.

However, when the user changes from PLMN-1 to PLMN-2, the network under PLMN-2 only supports two options of IMS voice and CP signaling, that is, paging messages never carry Paging cause=short message. In this way, the terminal of USIM-1 does not know whether the paging message corresponds to SMS short message service or not, and cannot determine whether the paging message must be replied to. Therefore, deviation between the user demand and the actual terminal behavior is caused, and the user experience is affected.

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

The technical scheme of the present application is described in detail below through specific embodiments.

Fig. 6 is a schematic flow chart diagram of a method 200 of wireless communication according to an embodiment of the present application, as shown in fig. 6, the method 200 may include at least some of the following:

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

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

s220, the terminal equipment 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 in the paging message.

In addition, the above-mentioned "reply" may be understood as a reply or reply to a paging message, for example, the terminal device transmits an RRC establishment request message to establish an RRC connection, and transmits a service request message to receive a service for which a paging cause value is to be given; for another example, the terminal device transmits an RRC resume request message to resume the RRC connection and transmits a service request message to receive the traffic for the paging cause value pair.

Alternatively, if the network does not send the first information to the terminal, it must support the same paging cause value (for example, all standardized paging cause values must be supported) for each network or each network supporting adding the paging cause value in the paging message, so that the terminal device provides the user with a correct setting option, and it is possible to avoid occurrence of a service corresponding to the paging cause value that is not supported by the network side in the setting option.

As another alternative, the first information, for example, paging cause values supported by one or more PLMNs, is preconfigured on the terminal device, so that the terminal device provides the user with a correct setting option, and services corresponding to paging cause values not supported by the network side can be avoided from occurring in the setting option. The "pre-configuration" may be a factory setting, a setting written in the SIM card and read from the SIM by the terminal device, a configuration obtained by Over The Air (OTA) technique.

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

Optionally, the network device may send the first information 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 user plane message may be a connection (e.g., an application layer hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP) connection) established by the server and the terminal device via the user plane. In this case, the network device may be a server, for example, which may send the first information to the terminal device via an HTTP connection.

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

Optionally, in the embodiment of the present application, the terminal device may provide a setting option for the user according to the first information, and the user-set option is used for the terminal device to determine whether to answer the paging message. Therefore, the service corresponding to the Paging cause (Paging cause) value which is not supported by the network side can be avoided from occurring in the setting options.

For example, the terminal device may provide the user with setting options according to the first information. The service in the setting option may correspond to a paging cause value, the user may set importance of each service or set whether a response is required when a certain service occurs, and the terminal device may decide whether to respond to a paging message containing a paging cause value corresponding to a certain service according to the user setting. For example, if voice service is coming, a response is needed, then the terminal responds to the Paging message every time the Paging message sent to the USIM-2 contains Paging cause=voice. In the setup option, the status of two USIM cards may also be considered, such as when USIM-1 is in data traffic, USIM-2 is idle, or vice versa. And if the USIM-1 is browsing the web page service, voice service occurs on the USIM-2.

Optionally, in some embodiments, the paging cause value supported by the network device changes with a change in a location where the terminal device is located; and/or the paging cause value supported by the network device changes over time.

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

different PLMN identifications and paging cause values supported by corresponding network equipment are different;

different tracking area indication (Tracking Area Indicator, TAI) lists, corresponding network devices supporting different paging cause values;

different cell identifiers and paging cause values supported by corresponding network equipment are different;

different RAN node identifiers and paging cause values supported by corresponding network equipment are different.

That is, paging cause values supported by the network device may be issued to the terminal device according to granularity of radio access technology (Radio Access Technology, RAT), PLMN identity, TAI list, cell identity, RAN node identity, etc.

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.

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, paging cause values supported by the network device include 2 and 3; and for TAI list 2, paging cause values supported by the network device include 4 and 5.

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

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, paging cause values supported by the network device include 1,2, and 3; and for cell 2, paging cause value packets 3, 4 and 5 are supported by the network device.

As 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.

As 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 traffic.

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

That is, the correspondence between the paging cause value and the service may be standardized or may be specific to different networks.

Optionally, in some embodiments, the terminal device sends a second message to the network device, the second message including a paging cause value supported by the terminal device; and after receiving the second message, the network device determines the first information according to 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.

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

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

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 may inform the terminal device that the paging cause values supported by the terminal device are 2 and 3 in the first information.

Optionally, in some embodiments, the first information is carried by registration response information, where the registration response information is response information to 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 by information broadcast by the network device.

Specifically, for example, the first information is carried by information broadcast by the network device before performing an RRC connection establishment procedure and/or performing a 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 user setting when establishing RRC connection or NAS connection, so that user setting after registration of the terminal device is avoided, and user experience is improved.

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

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

For another example, the first information is carried by a PDU session modification response message.

Optionally, in some embodiments, the first information is carried by RRC signaling. For example, in the RRC connection setup procedure, the terminal device receives the first information from the network device through RRC signaling interactions.

Therefore, in the embodiment of the application, the terminal equipment acquires the paging cause value supported by the network equipment and/or the paging cause value to be responded by the terminal equipment, so that the terminal equipment provides reasonable setting options for the user according to the paging cause value, and user experience can be improved.

Further, before performing the RRC connection establishment procedure and/or performing the registration procedure, the information broadcasted by the network device carries paging cause values supported by the network device and/or paging cause values that the terminal device needs to answer. Therefore, the terminal equipment can complete user setting when establishing RRC connection or NAS connection, and user setting after the terminal equipment is registered is avoided, so that user experience is improved.

The technical scheme of the application is described in detail below through two specific embodiments.

In embodiment 1, the network device may 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 procedure, which may be specifically implemented by the procedures S51-S53 shown in fig. 7.

S51, the terminal equipment sends registration request information to the core network equipment, optionally, the registration request information comprises paging cause values supported by the terminal equipment;

s52, the core network device sends registration response information aiming at the registration request information to the terminal device, wherein the registration response information carries paging cause values supported by the network device and/or paging cause values to be responded by the terminal device;

and S53, optionally, the terminal equipment can provide a setting option for the user according to the paging cause value supported by the network equipment and/or the paging cause value to be responded by the terminal equipment so as to avoid causing the service corresponding to the paging cause value which is not supported by the network side in the setting option.

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

It should also be noted that the paging cause value supported by the terminal device may include: the terminal device can provide the paging cause value for the user to set the service option, or the paging cause value that the terminal device can identify. The paging cause value supported by the network device is a paging cause value that the network device is able to detect and/or add in the paging message. (the specific detection and addition behavior of the network device may be as shown in fig. 4 and 5).

In embodiment 2, the network device may 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 procedure, which may be specifically implemented by the procedures S61-S62 shown in fig. 8.

S61, the base station sends broadcast information to the terminal equipment, wherein the broadcast information carries paging cause values supported by the network equipment and/or paging cause values which the terminal equipment needs to answer;

and S62, optionally, the terminal equipment can provide a setting option for the user according to the paging cause value supported by the network equipment and/or the paging cause value to be responded by the terminal equipment so as to avoid causing the service corresponding to the paging cause value which is not supported by the network side in the setting option.

In embodiment 2, before performing the RRC connection setup procedure and/or performing the registration procedure, the information broadcast by the network device carries paging cause values supported by the network device and/or paging cause values that the terminal device needs to answer. Therefore, the terminal equipment can complete user setting when establishing RRC connection or NAS connection, and user setting after the terminal equipment is registered is avoided, so that user experience is improved.

The method embodiments of the present application are described in detail above with reference to fig. 6 to 8, and the apparatus embodiments of the present application are described in detail below with reference to fig. 9 to 13, it being understood that the apparatus embodiments and the method embodiments correspond to each other, and similar descriptions may refer to the method embodiments.

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:

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

Optionally, the communication unit 310 is specifically configured to:

and receiving the first information sent by the network equipment 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.

Optionally, the terminal device 300 further includes:

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

Optionally, the paging cause value supported by the network device changes with a change in a location where the terminal device is located; and/or the paging cause value supported by the network device changes over time.

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

different public land mobile network PLMN identifiers and corresponding paging cause values supported by the network equipment are different;

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

different cell identifiers and paging cause values supported by the corresponding network equipment are different;

different radio access network RAN node identifiers and paging cause values supported by the corresponding network devices are different.

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: the terminal device can provide the paging cause value for the user to set the service option, or the 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.

Alternatively, 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 registration request information sent by the terminal device.

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

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

Optionally, the first information is carried through signaling in a protocol data unit PDU session establishment procedure, or the first information is carried through signaling in a PDU session modification procedure.

Optionally, the first information is carried through RRC signaling.

Alternatively, in some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a chip. The 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 embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 300 are respectively for implementing the corresponding flow of the terminal device in the method 200 shown in fig. 6, which is not described herein 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 fig. 10, the network device 400 includes:

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

Optionally, the communication unit 410 is specifically configured to:

and sending the first information to the terminal equipment 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.

Optionally, the network device 400 further includes: the processing unit 420 is configured to process the received data,

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 a paging cause value supported by the terminal device.

Alternatively, 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 embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the network device 400 are respectively for implementing the corresponding flow of the network device in the method 200 shown in fig. 6, and are not further described herein for brevity.

Fig. 11 is a schematic structural diagram of a communication device 500 provided in an embodiment of the present application. The communication device 500 shown in fig. 11 comprises a processor 510, from which the processor 510 may call and run a computer program to implement the method in the embodiments of the present application.

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

Wherein the memory 520 may be a separate device from the processor 510 or may be integrated into 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, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

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

Optionally, the communication device 500 may be specifically a network device in the embodiment of the present application, and the communication device 500 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 500 may be specifically a mobile terminal/terminal device in the embodiment of the present application, and the communication device 500 may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Fig. 12 is a schematic structural view of an apparatus of an embodiment of the present application. The apparatus 600 shown in fig. 12 includes a processor 610, and the processor 610 may call and run a computer program from a memory to implement the methods in the embodiments of the present application.

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

The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

Optionally, the apparatus 600 may further comprise an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and in particular, may acquire information or data sent by the other devices or chips.

Optionally, the apparatus 600 may further comprise an output interface 640. Wherein the processor 610 may control the output interface 640 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the apparatus may be applied to a network device in the embodiments of the present application, and the apparatus may implement a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the apparatus may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Alternatively, the device mentioned in the embodiments of the present application may also be a chip. For example, a system-on-chip or a system-on-chip, etc.

Fig. 13 is a schematic block diagram of a communication system 700 provided in 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 may be configured to implement the corresponding functions implemented by the terminal device in the above method, and the network device 720 may be configured to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may 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 programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

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

Optionally, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, which is not described herein for brevity.

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

Optionally, the computer program product may be applied to a network device in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiments of the present application, where the computer program when run on a computer causes the computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, and for brevity, will not be described herein.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. For such understanding, the technical solutions of the present application may be embodied in essence or in a part contributing to the prior art or in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of wireless communication, comprising:

the terminal equipment receives first information sent by the network equipment, wherein the first information comprises at least one of the following:

the paging cause value supported by the network device, and the paging cause value to be responded by the terminal device.
The method of claim 1, wherein the paging cause value supported by the network device is a paging cause value that the network device is capable of detecting and/or adding in 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 equipment receives the first information sent by the network equipment 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.
A method according to any one of claims 1 to 3, wherein the method further comprises:

and the terminal equipment provides a setting option for the user according to the first information, and the option set by the user is used for the terminal equipment to determine whether to answer the paging message.
The method according to any one of claim 1 to 4,

the paging cause value supported by the network equipment changes along with the change of the position of the terminal equipment; and/or the number of the groups of groups,

the paging cause value supported by the network device changes with time.
The method of any of claims 1 to 5, wherein the paging cause value supported by the network device satisfies at least one of:

different public land mobile network PLMN identifications and different paging cause values supported by corresponding network equipment;

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

different cell identifiers and paging cause values supported by the corresponding network equipment are different;

different Radio Access Network (RAN) node identifiers and paging cause values supported by the corresponding network equipment are different.
The method of any one of claims 1 to 6, further comprising:

and the terminal equipment sends a second message to the network equipment, wherein the second message comprises paging cause values supported by the terminal equipment.
The method of claim 7, wherein the paging cause value supported by the terminal device comprises:

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

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

the corresponding relation between the paging cause value and the service is pre-configured or agreed by a protocol, or the corresponding relation between the paging cause value and the service is configured by the network equipment.
The method according to any one of claim 1 to 11,

the first information is carried by registration response information, wherein the registration response information is response information of registration request information sent by the terminal equipment.
The method according to any one of claim 1 to 11,

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

the first information is carried by information broadcast by the network device before performing a radio resource control RRC connection establishment procedure and/or performing a registration procedure.
The method according to any one of claim 1 to 11,

the first information is carried by signaling in a protocol data unit PDU session establishment procedure, or the first information is carried by signaling in a PDU session modification procedure.
The method according to any one of claim 1 to 11,

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

the network device sends first information to the terminal device, wherein the first information comprises at least one of the following:

the paging cause value supported by the network device, and the paging cause value to be responded by the terminal device.
The method of claim 17, wherein the paging cause value supported by the network device is a paging cause value that the network device is capable of detecting and/or adding in a paging message.
The method according to claim 17 or 18, wherein the network device sending the first information to the terminal device comprises:

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.
A method according to any of claims 17 to 19, wherein the first information is for the terminal device to provide a user with a set option, and the user-set option is for the terminal device to determine whether to answer a paging message.
The method according to any one of claim 17 to 20,

the paging cause value supported by the network equipment changes along with the change of the position of the terminal equipment; and/or the number of the groups of groups,

the paging cause value supported by the network device changes with time.
The method of any of claims 17 to 21, wherein the paging cause value supported by the network device satisfies at least one of:

different public land mobile network PLMN identifications and different paging cause values supported by corresponding network equipment;

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

different cell identifiers and paging cause values supported by the corresponding network equipment are different;

different Radio Access Network (RAN) node identifiers and paging cause values supported by the corresponding network equipment are different.
The method of any one of claims 17 to 22, the method further comprising:

the network equipment receives a second message sent by the terminal equipment, wherein the second message comprises paging cause values supported by the terminal equipment;

and the network equipment determines the first information according to the paging cause value supported by the terminal equipment.
The method of claim 23, wherein the paging cause value supported by the terminal device comprises: the terminal equipment can provide the paging cause value for the user to set the service option, or the paging cause value which can be identified by the terminal equipment
The method of claim 23 or 24, wherein the second message is at least one of an AS message, a NAS message, a user plane message.
The method of any one of claim 17 to 25,

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

the corresponding relation between the paging cause value and the service is pre-configured or agreed by a protocol, or the corresponding relation between the paging cause value and the service is configured by the network equipment.
The method according to any one of claim 17 to 27,

the first information is carried by registration response information, wherein the registration response information is response information of registration request information sent by the terminal equipment.
The method according to any one of claim 17 to 27,

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

the first information is carried by information broadcast by the network device before performing a radio resource control RRC connection establishment procedure and/or performing a registration procedure.
The method according to any one of claim 17 to 27,

the first information is carried by signaling in a protocol data unit PDU session establishment procedure, or the first information is carried by signaling in a PDU session modification procedure.
The method according to any one of claim 17 to 27,

the first information is carried through RRC signaling.
A terminal device, comprising:

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

the paging cause value supported by the network device, and the paging cause value to be responded by the terminal device.
The terminal device of claim 33, wherein the paging cause value supported by the network device is a paging cause value that the network device is capable of detecting and/or adding in a paging message.
Terminal device according to claim 33 or 34, wherein the communication unit is specifically configured to:

and receiving the first information sent by the network equipment 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 terminal device according to any of the claims 33 to 35, wherein the terminal device further comprises:

and the processing unit is used for providing a setting option for the user according to the first information, and the option set by the user is used for the terminal equipment to determine whether to answer the paging message.
The terminal device according to any of the claims 33 to 36, characterized in that,

the paging cause value supported by the network equipment changes along with the change of the position of the terminal equipment; and/or the number of the groups of groups,

the paging cause value supported by the network device changes with time.
The terminal device according to any of the 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 identifications and different paging cause values supported by corresponding network equipment;

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

different cell identifiers and paging cause values supported by the corresponding network equipment are different;

different Radio Access Network (RAN) node identifiers and paging cause values supported by the corresponding network equipment are different.
The terminal device according to any of claims 33 to 38, the communication unit further being adapted to send a second message to the network device, the second message comprising paging cause values supported by the terminal device.
The terminal device of claim 39, wherein the paging cause value supported by the terminal device comprises: the terminal device can provide the paging cause value for the user to set the service option, or the paging cause value which can be identified by the terminal device.
The terminal device of claim 39 or 40, wherein the second message is at least one of an AS message, a NAS message, a user plane message.
The terminal device according to any one of claims 33 to 41, characterized in that,

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

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

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

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

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

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

the first information is carried through RRC signaling.
A network device, comprising:

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

the paging cause value supported by the network device, and the paging cause value to be responded by the terminal device.
The network device of claim 49, wherein the paging cause value supported by the network device is a paging cause value that the network device is capable of detecting and/or adding to a paging message.
Network device according to claim 49 or 50, characterized in that said communication unit is in particular adapted to:

and sending the first information to the terminal equipment 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.
A network device as claimed in any one of claims 49 to 51, wherein the first information is for the terminal device to provide a user with a set option, and the user-set option is for the terminal device to determine whether to answer a paging message.
The network device of any one of claims 49 to 52,

the paging cause value supported by the network equipment changes along with the change of the position of the terminal equipment; and/or the number of the groups of groups,

the paging cause value supported by the network device changes with time.
The network device of any one of claims 49 to 53, wherein the paging cause value supported by the network device satisfies at least one of:

different public land mobile network PLMN identifications and different paging cause values supported by corresponding network equipment;

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

different cell identifiers and paging cause values supported by the corresponding network equipment are different;

different Radio Access Network (RAN) node identifiers and paging cause values supported by the corresponding network equipment are different.
The network device of any one of claims 49 to 54, 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 used for determining the first information according to the paging cause value supported by the terminal equipment.
The network device of claim 55, wherein the paging cause value supported by the terminal device comprises: the terminal device can provide the paging cause value for the user to set the service option, or the paging cause value which can be identified by the terminal device.
The network device of claim 55 or 56, wherein the second message is at least one of an AS message, a NAS message, a user plane message.
The network device of any one of claims 49 to 57,

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

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

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

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

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

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

the first information is carried through RRC signaling.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory to perform the method of any of claims 1 to 16.
A network device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 17 to 32.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 16.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 17 to 32.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 16.
A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 17 to 32.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 16.
A computer program product comprising computer program instructions which cause a computer to perform the method of any 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 of any of claims 17 to 32.