Wireless communication method, device and storage medium

Abstract

This application is a divisional application of 202180068440.9. A wireless communication method, device and storage medium are provided, the method comprising: a first access network device sends a paging message to a second access network device, the paging message comprising: a first paging reason value to assist the terminal device in making a service priority decision.

Description

[0001] This application is a divisional application of the invention patent application with the application number 202180068440.9 and the invention title "Wireless Communication Method, Device and Storage Medium", which was filed with the Chinese Patent Office on January 29, 2021. Technical Field

[0002] Embodiments of the present application relate to the field of communications, and more specifically, to a wireless communication method, device, and storage medium. Background Art

[0003] Currently, the paging process is divided into a paging process initiated by the core network and a paging process sent by the access network. Among them, the paging process sent by the access network includes: the access network releases the terminal device from the connected state to the Radio Resource Control (RRC) inactive state (RRC_INACTIVE). At this time, the access network still stores the Access Stratum (AS) context of the terminal device, and the access network device that stores the AS context of the terminal device is called the anchor access network device. Among them, when the anchor access network device releases the terminal device from the connected state to the inactive state, a paging area configuration information will be configured for the terminal device. This paging area configuration information is used to determine which access network devices the subsequent anchor access network device will initiate a paging process to. At this time, the connection between the access network and the core network for this terminal device is still maintained. For the core network device, the terminal device is still in the connected state. When downlink user data arrives, the core network device directly sends the user data to the anchor access network device. After the anchor access network device determines that the terminal device is in the inactive state, it initiates a paging process for this terminal device. During the paging process, the anchor access network device will send a paging message to the access network devices included in the above paging area configuration information, and these access network devices will trigger the corresponding paging process through their own air interfaces.

[0004] However, the current paging process sent by the access network is not conducive to the terminal device to perform service priority judgment. Summary of the Invention

[0005] Embodiments of the present application provide a wireless communication method, device, and storage medium to assist the terminal device in performing service priority judgment.

[0006] In a first aspect, a wireless communication method is provided, including: a first access network device sends a paging message to a second access network device, and the paging message includes: a first paging cause value.

[0007] In a second aspect, a wireless communication method is provided, including: a second access network device receives a paging message sent by a first access network device, and the paging message includes: a first paging cause value.

[0008] In a third aspect, a wireless communication method is provided, including: a network device sending paging cause value auxiliary information to a first access network device. The paging cause value auxiliary information is used to assist the first access network device in determining a first paging cause value.

[0009] In a fourth aspect, a wireless communication method is provided, including: a terminal device receiving a paging message sent by a second access network device, where the paging message includes: a first paging cause value.

[0010] In a fifth aspect, an access network device is provided. The access network device is the first access network device and is used to execute the method in the first aspect or its various implementation manners.

[0011] Specifically, the access network device includes functional modules for executing the method in the first aspect or its various implementation manners.

[0012] In a sixth aspect, an access network device is provided. The access network device is the second access network device and is used to execute the method in the second aspect or its various implementation manners.

[0013] Specifically, the access network device includes functional modules for executing the method in the second aspect or its various implementation manners.

[0014] In a seventh aspect, a network device is provided and is used to execute the method in the third aspect or its various implementation manners.

[0015] Specifically, the network device includes functional modules for executing the method in the third aspect or its various implementation manners.

[0016] In an eighth aspect, a terminal device is provided and is used to execute the method in the fourth aspect or its various implementation manners.

[0017] Specifically, the terminal device includes functional modules for executing the method in the fourth aspect or its various implementation manners.

[0018] In a ninth aspect, an access network device is provided. The access network device is the first access network device and includes 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 or its various implementation manners.

[0019] In a tenth aspect, an access network device is provided. The access network device is the second access network device and includes 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 or its various implementation manners.

[0020] In an eleventh 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 third aspect or its various implementation manners as described above.

[0021] In a twelfth 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 fourth aspect or its various implementation manners as described above.

[0022] In a thirteenth aspect, a device is provided for implementing the method in the first aspect, second aspect, third aspect, fourth aspect or their various implementation manners as described above.

[0023] Specifically, the device includes: a processor, configured to call and run a computer program from a memory, such that a device installed with the device executes the method in the first aspect, second aspect, third aspect, fourth aspect or their various implementation manners as described above.

[0024] In a fourteenth aspect, a computer program product is provided, including computer program instructions, and the computer program instructions cause a computer to execute the method in the first aspect, second aspect, third aspect, fourth aspect or their various implementation manners as described above.

[0025] In a fifteenth aspect, a computer program is provided, which when running on a computer, causes the computer to execute the method in the first aspect, second aspect, third aspect, fourth aspect or their various implementation manners as described above.

[0026] In summary, in this application, during the paging process sent by the access network, a paging cause value may be carried in the paging message, so that the terminal device can perform service priority judgment according to the paging cause value. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 is a schematic diagram of an application scenario of an embodiment of this application;

[0028] Figure 2 is an interaction flowchart of a wireless communication method provided by an embodiment of this application;

[0029] Figure 3 is an interaction flowchart of another wireless communication method provided by an embodiment of this application;

[0030] Figure 4 is an interaction flowchart of yet another wireless communication method provided by an embodiment of this application;

[0031] Figure 5 shows a schematic block diagram of an access network device 500 according to an embodiment of this application;

[0032] Figure 6 shows a schematic block diagram of an access network device 600 according to an embodiment of the present application;

[0033] Figure 7 shows a schematic block diagram of a network device 700 according to an embodiment of the present application;

[0034] Figure 8 shows a schematic block diagram of a terminal device 800 according to an embodiment of the present application;

[0035] Figure 9 is a schematic structural diagram of a communication device 900 provided by an embodiment of the present application;

[0036] Figure 10 is a schematic structural diagram of a device according to an embodiment of the present application. Specific embodiments

[0037] Next, the technical solutions in the embodiments of the present application will be described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. For the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0038] Figure 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0039] As Figure 1 shown, the communication system 100 may include a terminal device 110, a first access network device 120, a second access network device 130, and a core network device 140. Among them, the first access network device 120 may be an anchor access network device in the paging process sent in the access network, that is, an access network device that stores the AS context of the terminal device. The second access network device 130 may be any access network device in the paging area configuration information configured for the terminal device 110. The second access network device 130 may communicate with the terminal device 110 through the air interface. Multi-service transmission is supported between the terminal device 110 and the second access network device 130.

[0040] It should be understood that the embodiments of the present application are only exemplarily described by the communication system 100, but the embodiments of the present application are not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), 5G communication system (also known as New Radio (NR) communication system), or future communication systems, etc.

[0041] Taking the 5G communication system as an example, the main application scenarios of 5G are: Enhance Mobile Broadband (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), massive Machine Type of Communication (mMTC). eMBB still aims at users to obtain multimedia content, services and data, and its demand is growing very rapidly. Since eMBB may be deployed in different scenarios, such as indoors, urban areas, rural areas, etc., the differences in its capabilities and requirements are relatively large, so it cannot be generalized and must be analyzed in detail in combination with specific deployment scenarios. Typical applications of URLLC include: industrial automation, power automation, remote medical operations (surgeries), traffic safety assurance, etc. The typical characteristics of mMTC include: high connection density, small data volume, delay-insensitive services, low cost and long service life of modules, etc.

[0042] In a 5G network environment, for the purpose of reducing air interface signaling and quickly restoring wireless connections and data services, a new RRC state, namely the RRC_INACTIVE (deactivated) state, is defined. This state is different from the RRC_IDLE (idle) and RRC_CONNECTED (connected) states. RRC_IDLE: Mobility is based on cell selection and reselection of the terminal device, paging is initiated by the Core Network (CN), and the paging area is configured by the CN. The access network device does not have the AS context of the terminal device and there is no RRC connection. RRC_CONNECTED: There is an RRC connection, and the access network device and the terminal device have the AS context of the terminal device; the access network device knows the location of the terminal device at the specific cell level. Mobility is the mobility controlled by the access network device. Unicast data can be transmitted between the terminal device and the access network device. RRC_INACTIVE: Mobility is based on cell selection and reselection of the terminal device, there is a connection between the CN and NR, the AS context of the terminal device exists on a certain access network device (i.e., the anchor access network device), paging is triggered by the Radio Access Network (RAN), the paging area based on the RAN is managed by the RAN, and the anchor access network device knows the location of the terminal device at the RAN-based paging area level.

[0043] In Figure 1 In the communication system 100 shown, the first access network device 120 and the second access network device 130 can provide communication coverage for a specific geographical area and can communicate with the terminal device 110 located within the coverage area.

[0044] Both the first access network device 120 and the second access network device 130 can be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a radio controller in a Cloud Radio Access Network (CRAN), or the access network device 120 can be a relay station, access point, vehicle-mounted device, wearable device, hub, switch, bridge, router, or an access network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0045] The terminal device 110 can be any terminal device, including but not limited to a terminal device that is wired or wirelessly connected to the first access network device 120, the second access network device 130, or other terminal devices.

[0046] For example, the terminal device 110 may refer to an access terminal, a user equipment (UE), a user unit, a user station, a mobile station, a mobile device, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device, or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved network, etc.

[0047] The terminal device 110 can be used for Device to Device (D2D) communication.

[0048] The core network device 140 can be a 5G Core (5GC) device. For example, it can be an Access and Mobility Management Function (AMF), or for another example, an Authentication Server Function (AUSF), or for another example, a User Plane Function (UPF), or for another example, a Session Management Function (SMF). Optionally, the core network device 140 can also be an Evolved Packet Core (EPC) device of an LTE network, such as a Session Management Function + Core Packet Gateway (SMF + PGW-C) device. It should be understood that SMF + PGW-C can simultaneously implement the functions that SMF and PGW-C can achieve. During the network evolution process, the above core network device may also have other names, or new network entities may be formed by dividing the functions of the core network. The embodiments of this application do not limit this.

[0049] Each functional unit in the communication system 100 can also establish a connection through the Next Generation (NG) interface to achieve communication.

[0050] For example, the terminal device establishes a radio interface connection with the first access network device and the second access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (abbreviated as N1); the first access network device and the second access network device, such as the next-generation radio access base station (gNB) for example, can establish a user plane data connection with the UPF through the NG interface 3 (abbreviated as N3); the first access network device and the second access network device can establish a control plane signaling connection with the AMF through the NG interface 2 (abbreviated as N2); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (abbreviated as N4); the UPF can interact with the data network for user plane data through the NG interface 6 (abbreviated as N6); the AMF can establish a control plane signaling connection with the SMF through the NG interface 11 (abbreviated as N11); the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (abbreviated as N7).

[0051] Figure 1 Exemplarily, one first access network device, one second access network device, one core network device, and one terminal device are shown. Optionally, the wireless communication system 100 may include other numbers of access network devices, and the coverage range of each access network device may include other numbers of terminal devices. The embodiments of the present application do not limit this.

[0052] It should be understood that in the embodiments of the present application, devices with communication functions in the network / system can all be referred to as communication devices. Taking Figure 1 the shown communication system 100 as an example, the communication devices may include the first access network device 120, the second access network device 130, and the terminal device 110 with communication functions. The first access network device 120, the second access network device 130, and the terminal device 110 may be the devices described above, which will not be elaborated here; the communication devices may also include other devices in the communication system 100, such as other network entities like network controllers and mobility management entities. The embodiments of the present application do not limit this.

[0053] It should be understood that the terms "system" and "network" are often used interchangeably in this article.

[0054] As described above, the paging process includes: the paging process initiated by the core network and the paging process initiated by the access network.

[0055] The paging process initiated by the core network:

[0056] Phase 1: The terminal device completes the registration process and obtains the registration area configuration information (Registration Area, RA) configured by the core network.

[0057] Phase 2: The terminal device is in the idle state in the core network. When downlink user data arrives, the core network sends a paging message to the access network device included in the terminal device's registration area configuration information. After receiving the paging message triggered by the core network, the access network triggers the corresponding paging process on the air interface.

[0058] Paging process initiated by the access network:

[0059] Phase 1: The access network releases the terminal device from the connected state to the inactive state. At this time, the anchor access network device still stores the terminal device's AS context. Among them, when the anchor access network device releases the terminal device from the connected state to the inactive state, it will configure a paging area configuration information for the terminal device. At this time, the connection between the access network and the core network for this terminal device is still maintained.

[0060] Phase 2: For the core network device, the terminal device is still in the connected state. When downlink user data arrives, the core network device directly sends the user data to the anchor access network device. After the anchor access network device determines that the terminal device is in the inactive state, it initiates a paging process for the terminal device. During the paging process, the anchor access network device will send the paging message to the access network devices included in the above paging area configuration information, and these access network devices will trigger the corresponding paging process through their own air interfaces.

[0061] As described above, the current paging process sent by the access network is not conducive to the terminal device to perform service priority judgment.

[0062] To solve the above technical problems, in the paging process sent by the access network in this application, a paging reason value is carried in the paging message, so that the terminal device can perform service priority judgment according to the paging reason value.

[0063] The technical solution of this application will be elaborated in detail below:

[0064] Figure 2 It is an interaction flowchart of a wireless communication method provided by an embodiment of this application. As Figure 2 shown, the method includes the following steps:

[0065] S210: The first access network device sends a paging message to the second access network device. The paging message includes: a first paging reason value.

[0066] S220: The second access network device sends the above paging message to the terminal device.

[0067] It should be understood that the first access network device may be the anchor access network device in the paging process sent by the access network. The second access network device may be any access network device in the paging area configuration information configured for the terminal device.

[0068] It should be understood that in this application, the paging cause value corresponds one-to-one with the paging cause, that is, one paging cause value represents one paging cause. This paging cause value is also referred to as a paging cause index, a paging cause parameter, etc., and this application does not limit this.

[0069] Optionally, in this application, any paging cause may be any one of the following: voice, video, short message, high-priority service, data, non-access stratum (NAS) signaling.

[0070] Optionally, in order to prevent the paging cause value from being stolen by a third party organization, the core network may formulate an encryption rule for the paging cause value. The core idea is to map the paging cause value to be encrypted to pseudo-random identification information through a specific mapping algorithm. Based on this, the first paging cause value may be an encrypted paging cause value. Of course, the first paging cause value may also be an unencrypted paging cause value, and this application does not limit this.

[0071] It should be understood that the above encryption rule is also referred to as a security mapping rule, and this application does not limit this.

[0072] Optionally, when the first paging cause value is an encrypted paging cause value, the terminal device may decrypt the first paging cause value through a decryption rule.

[0073] It should be understood that the above decryption rule is the reverse algorithm of the above encryption rule.

[0074] Optionally, for the terminal device, the decryption rule is pre-configured for the terminal device or may be obtained through the NAS process. This application does not limit the way for the terminal device to obtain the decryption rule.

[0075] Optionally, after the terminal device obtains the first paging cause value, the terminal device may perform a service priority judgment according to the first paging cause value.

[0076] Exemplarily, when the first paging cause value is the paging cause value corresponding to voice, its priority is higher than that of other services. Therefore, the terminal device first processes this paging message regarding voice. When the first paging cause value is the paging cause value corresponding to a short message, its priority is lower than that of other services. Therefore, the terminal device may first process other services and then process the paging message regarding the short message.

[0077] In this application, during the paging process sent by the access network, a paging cause value may be carried in the paging message so that the terminal device can perform service priority judgment based on the paging cause value.

[0078] Optionally, in this application, the first access network device may also obtain paging cause value auxiliary information from a network device, and the paging cause value auxiliary information is used to assist the first access network device in determining the first paging cause value.

[0079] Optionally, the network device may be a core network device or an Operation and Maintenance (OAM) node, but is not limited thereto.

[0080] Assume that the paging cause value auxiliary information is obtained from the core network device. Based on this, the wireless communication method will be further described below:

[0081] Figure 3 For the interaction flowchart of another wireless communication method provided in the embodiments of this application, as Figure 3 shown, the method includes the following steps:

[0082] Optionally, the following steps may also be executed before S210:

[0083] S310: The network device sends a first message to the first access network device, and the first message includes: paging cause value auxiliary information.

[0084] S320: The first access network device determines the first paging cause value according to the paging cause value auxiliary information.

[0085] Figure 4 For the interaction flowchart of yet another wireless communication method provided in the embodiments of this application, as Figure 4 shown, the method includes the following steps:

[0086] Optionally, the following steps may also be executed before S210:

[0087] S410: The first access network device sends a second message to the core network device, and the second message is used to request to obtain paging cause value auxiliary information.

[0088] S420: The network device sends a first message to the first access network device, and the first message includes: paging cause value auxiliary information.

[0089] S430: The first access network device determines the first paging cause value according to the paging cause value auxiliary information.

[0090] It should be understood that the first message is triggered by the process initiated by the first access network device, as Figure 3As shown, or the first message is triggered by a process initiated by the core network device, such as Figure 4 as shown.

[0091] Optionally, the paging cause value auxiliary information includes at least one of the following, but is not limited to:

[0092] (1) At least one paging cause value.

[0093] (2) The Protocol Data Unit (PDU) session identifier associated with each paging cause value.

[0094] (3) The Quality of Service (QoS) flow value associated with each paging cause value.

[0095] (4) The slice identifier associated with each paging cause value.

[0096] (5) The encryption rule that the paging cause value to be encrypted needs to follow.

[0097] It should be understood that in this application, the QoS flow value corresponds to the QoS flow one by one, that is, one QoS flow value represents one QoS flow. This QoS flow value is also referred to as a QoS flow index, a QoS flow parameter, etc., and this application does not limit this.

[0098] It should be understood that in this application, the slice identifier is also referred to as a network slice identifier, and this application does not limit this.

[0099] It should be understood that for the encryption rule, reference can be made to the above explanation of the encryption rule, and this application does not limit this.

[0100] Optionally, any one of the at least one paging cause value is an encrypted paging cause value or an unencrypted paging cause value.

[0101] Optionally, the first message is a dedicated message for a specific terminal device, or a common message that is not for a specific terminal device.

[0102] Optionally, when the first message is a dedicated message for a specific terminal device, the first message is any one of the following, but is not limited to:

[0103] The PDU session establishment message of the specific terminal device.

[0104] The PDU session modification message of the specific terminal device.

[0105] The PDU session reconstruction message of the specific terminal device.

[0106] PDU session release message of a specific terminal device.

[0107] Context establishment message of a specific terminal device.

[0108] Context modification message of a specific terminal device.

[0109] Context reconstruction message of a specific terminal device.

[0110] Context release message of a specific terminal device.

[0111] RRC status acquisition message of a specific terminal device.

[0112] It should be noted that the PDU session establishment message here is also referred to as any message sent by the network device involved in the PDU session establishment process to the first access network device. The PDU session modification message is also referred to as any message sent by the network device involved in the PDU session modification process to the first access network device. The PDU session reconstruction message is also referred to as any message sent by the network device involved in the PDU session reconstruction process to the first access network device. The PDU session release message is also referred to as any message sent by the network device involved in the PDU session release process to the first access network device. The context establishment message is also referred to as any message sent by the network device involved in the context establishment process to the first access network device. The context modification message is also referred to as any message sent by the network device involved in the context modification process to the first access network device. The context reconstruction message is also referred to as any message sent by the network device involved in the context reconstruction process to the first access network device. The context release message is also referred to as any message sent by the network device involved in the context release process to the first access network device. The RRC status acquisition message is also referred to as any message sent by the network device involved in the RRC status acquisition process to the first access network device.

[0113] Optionally, when the first message is not a common message for a specific terminal device, the first message is any one of the following:

[0114] Interface initialization message, interface update message, resource reporting message, exception reporting message.

[0115] It should be noted that the interface initialization message is also referred to as any message sent by the network device involved in the interface initialization process to the first access network device. The interface update message is also referred to as any message sent by the network device involved in the interface update process to the first access network device. The resource reporting message is also referred to as any message sent by the network device involved in the resource reporting process to the first access network device. The exception reporting message is also referred to as any message sent by the network device involved in the exception reporting process to the first access network device.

[0116] Optionally, the second message is an empty message or a non-empty message.

[0117] It should be understood that the empty message is a newly defined message by the first access network device, which is used to request to obtain paging cause value auxiliary information.

[0118] It should be understood that the non-empty message can be a newly defined message by the first access network device, or a message defined by the first access network device based on an existing message.

[0119] Optionally, when the second message is a non-empty message, the second message is a dedicated message for a specific terminal device, or a common message not for a specific terminal device.

[0120] Optionally, when the second message is a dedicated message for a specific terminal device, the second message is any one of the following:

[0121] The PDU session establishment message of the specific terminal device.

[0122] The PDU session modification message of the specific terminal device.

[0123] The PDU session re-establishment message of the specific terminal device.

[0124] The PDU session release message of the specific terminal device.

[0125] The context establishment message of the specific terminal device.

[0126] The context modification message of the specific terminal device.

[0127] The context re-establishment message of the specific terminal device.

[0128] The context release message of the specific terminal device.

[0129] The RRC status acquisition message of the specific terminal device.

[0130] It should be noted that the PDU session establishment message here is also referred to as any message sent by the first access network device involved in the PDU session establishment process to the network device. The PDU session modification message is also referred to as any message sent by the first access network device involved in the PDU session modification process to the network device. The PDU session reestablishment message is also referred to as any message sent by the first access network device involved in the PDU session reestablishment process to the network device. The PDU session release message is also referred to as any message sent by the first access network device involved in the PDU session release process to the network device. The context establishment message is also referred to as any message sent by the first access network device involved in the context establishment process to the network device. The context modification message is also referred to as any message sent by the first access network device involved in the context modification process to the network device. The context reestablishment message is also referred to as any message sent by the first access network device involved in the context reestablishment process to the network device. The context release message is also referred to as any message sent by the first access network device involved in the context release process to the network device. The RRC status acquisition message is also referred to as any message sent by the first access network device involved in the RRC status acquisition process to the network device.

[0131] Optionally, when the second message is not a common message for a specific terminal device, the second message is any one of the following: interface initialization message, interface update message, resource reporting message, exception reporting message.

[0132] It should be noted that the interface initialization message is also referred to as any message sent by the first access network device involved in the interface initialization process to the network device. The interface update message is also referred to as any message sent by the first access network device involved in the interface update process to the network device. The resource reporting message is also referred to as any message sent by the first access network device involved in the resource reporting process to the network device. The exception reporting message is also referred to as any message sent by the first access network device involved in the exception reporting process to the network device.

[0133] Optionally, when the second message is a non-empty message, the second message includes at least one of the following, but is not limited thereto:

[0134] (1) Indication information for requesting the paging cause value auxiliary information from the core network device.

[0135] (2) PDU session identifier list information for which the paging cause value auxiliary information needs to be obtained.

[0136] (3) QoS flow value list information for which the paging cause value auxiliary information needs to be obtained.

[0137] (4) Slice identifier list information for which the paging cause value auxiliary information needs to be obtained.

[0138] (5) Instructions for obtaining the encryption rules that the paging cause value to be encrypted needs to follow.

[0139] The instructions in item (1) are used to request the paging cause value auxiliary information from the core network device. The instructions in item (5) are used to obtain the above encryption rules.

[0140] Optionally, after obtaining the paging cause value auxiliary information, the first access network device may determine the first paging cause value according to a certain selection rule. For example: The paging cause value auxiliary information includes: at least one paging cause value, and the PDU identifier associated with each paging cause value. Then, the first access network device may determine the first paging cause value according to the PDU identifier of the terminal device and the mapping relationship between the PDU identifier and the paging cause value. Or, the paging cause value auxiliary information includes: at least one paging cause value, and the QoS flow value associated with each paging cause value. Then, the first access network device may determine the first paging cause value according to the QoS flow value of the terminal device and the mapping relationship between the QoS flow value and the paging cause value. Or, the paging cause value auxiliary information includes: at least one paging cause value, and the slice identifier associated with each paging cause value. Then, the first access network device may determine the first paging cause value according to the slice identifier of the terminal device and the mapping relationship between the slice identifier and the paging cause value. Of course, the terminal device may also determine the first paging cause value according to at least one item in the paging cause value auxiliary information, which will not be elaborated in this application.

[0141] In this application, the first access network device may obtain the paging cause value auxiliary information from the network device, and determine the above first paging cause value according to the paging cause value auxiliary information. Thus, in the paging process sent by the access network, the first paging cause value may be carried in the paging message, so that the terminal device may perform service priority judgment according to the first paging cause value.

[0142] As described above, each paging cause value in the paging cause value auxiliary information is associated with a PDU session identifier, a QoS flow value, a slice identifier, etc.

[0143] Next, the mapping relationship, that is, the association relationship, between the paging cause value and the PDU session identifier, the QoS flow value, and the slice identifier will be described:

[0144] Optionally, for any one of the at least one paging cause value, the mapping relationship between the paging cause value and the PDU session identifier is a one-to-one, one-to-many, or many-to-one mapping relationship. And / or, the mapping relationship between the paging cause value and the QoS flow value is a one-to-one, one-to-many, or many-to-one mapping relationship. And / or, the mapping relationship between the paging cause value and the slice identifier is a one-to-one, one-to-many, or many-to-one mapping relationship.

[0145] The mapping relationship, i.e., the association relationship, between the paging cause value, the PDU session identifier, the QoS flow value, and the slice identifier will be exemplarily described through several examples as follows:

[0146] Example 1: As shown in Table 1, one paging cause value is mapped to one PDU session identifier:

[0147] Table 1

[0148] PDU Session Identifier 1 PDU Session Identifier 2 …… PDU Session Identifier N Paging Cause Value 1 Paging Cause Value 2 …… Paging Cause Value N

[0149] Example 2: As shown in Table 2, one paging cause value is mapped to multiple PDU session identifiers:

[0150] Table 2

[0151]

[0152] Example 3: As shown in Table 3, multiple paging cause values are mapped to one PDU session identifier:

[0153] Table 3

[0154]

[0155] Example 4: As shown in Table 4, one paging cause value is mapped to one QoS flow value:

[0156] Table 4

[0157] QoS Flow Value 1 QoS Flow Value 2 …… QoS Flow Value N Paging Cause Value 1 Paging Cause Value 2 …… Paging Cause Value N

[0158] Example 5: As shown in Table 5, one paging cause value is mapped to multiple QoS flow values:

[0159] Table 5

[0160]

[0161] Example 6: As shown in Table 6, multiple paging cause values are mapped to one QoS flow value:

[0162] Table 6

[0163]

[0164]

[0165] Example 7: As shown in Table 7, one paging cause value is mapped to one slice identifier:

[0166] Table 7

[0167] Slice Identifier 1 Slice Identifier 2 …… Slice Identifier N Paging Cause Value 1 Paging Cause Value 2 …… Paging Cause Value N

[0168] Example 8: As shown in Table 8, one paging cause value is mapped to multiple slice identifiers:

[0169] Table 8

[0170]

[0171] Example 9: As shown in Table 9, multiple paging cause values are mapped to one slice identifier:

[0172] Table 9

[0173]

[0174] Example 10: As shown in Table 10, one paging cause value is mapped to one PDU session identifier, and a set of QoS flow values associated with the paging cause value and the PDU session identifier are mapped:

[0175] Table 10

[0176]

[0177] Example 11: As shown in Table 11, one paging cause value is mapped to one PDU session identifier, and one QoS flow value associated with the paging cause value and the PDU session identifier is mapped:

[0178] Table 11

[0179]

[0180] Example 12: As shown in Table 12, one paging cause value is mapped to one slice identifier, and a set of PDU session identifiers associated with the paging cause value and the slice identifier are mapped:

[0181] Table 12

[0182]

[0183] Example 13: As shown in Table 13, one paging cause value is mapped to one slice identifier, and one PDU session identifier associated with the paging cause value and the slice identifier is mapped:

[0184] Table 13

[0185]

[0186] Example 14: As shown in Table 14, one paging cause value is mapped to one slice identifier, and a set of QoS flow values associated with the paging cause value and the slice identifier are mapped:

[0187] Table 14

[0188]

[0189] Example 15: As shown in Table 15, a paging cause value is mapped to a slice identifier, and a QoS flow value associated with the paging cause value and the slice identifier is mapped:

[0190] Table 15

[0191]

[0192] Example 16: As shown in Table 16, a paging cause value is mapped to a slice identifier, and a PDU session identifier associated with the paging cause value and the slice identifier is mapped, and a set of QoS flow values associated with the paging cause value and the PDU session identifier is mapped:

[0193] Table 16

[0194]

[0195] It should be understood that the mapping relationships of the paging cause value with the PDU session identifier, the QoS flow value, and the slice identifier are the above examples of the association relationships.

[0196] Figure 5 Fig. shows a schematic block diagram of an access network device 500 according to an embodiment of the present application. The access network device 500 is a first access network device, as Figure 5 shown, a communication unit 510, configured to send a paging message to a second access network device, where the paging message includes: a first paging cause value.

[0197] Optionally, the communication unit 510 is further configured to: obtain paging cause value auxiliary information from a network device. The paging cause value auxiliary information is used to assist the first access network device in determining the first paging cause value.

[0198] Optionally, the paging cause value auxiliary information includes at least one of the following:

[0199] At least one paging cause value.

[0200] A PDU session identifier associated with each paging cause value.

[0201] A QoS flow value associated with each paging cause value.

[0202] A slice identifier associated with each paging cause value.

[0203] An encryption rule that the paging cause value to be encrypted needs to follow.

[0204] Optionally, the mapping relationship between the paging cause value and the PDU session identifier is a one-to-one, one-to-many, or many-to-one mapping relationship. And / or, the mapping relationship between the paging cause value and the QoS flow value is a one-to-one, one-to-many, or many-to-one mapping relationship. And / or, the mapping relationship between the paging cause value and the slice identifier is a one-to-one, one-to-many, or many-to-one mapping relationship.

[0205] Optionally, any one of at least one paging cause value is an encrypted paging cause value or an unencrypted paging cause value.

[0206] Optionally, the network device is a core network device or an OAM node.

[0207] Optionally, when the network device is a core network device, the communication unit 510 is specifically configured to: receive a first message sent by the core network device, where the first message includes: paging cause value auxiliary information.

[0208] Optionally, the first message is a dedicated message for a specific terminal device, or is a common message not for a specific terminal device.

[0209] Optionally, when the first message is a dedicated message for a specific terminal device, the first message is any one of the following:

[0210] The PDU session establishment message of the specific terminal device.

[0211] The PDU session modification message of the specific terminal device.

[0212] The PDU session reconstruction message of the specific terminal device.

[0213] The PDU session release message of the specific terminal device.

[0214] The context establishment message of the specific terminal device.

[0215] The context modification message of the specific terminal device.

[0216] The context reconstruction message of the specific terminal device.

[0217] The context release message of the specific terminal device.

[0218] The radio resource control (RRC) status acquisition message of the specific terminal device.

[0219] Optionally, when the first message is a common message not for a specific terminal device, the first message is any one of the following:

[0220] The interface initialization message.

[0221] The interface update message.

[0222] The resource reporting message.

[0223] Abnormal reporting message.

[0224] Optionally, the first message is triggered by a process initiated by the first access network device or by a process initiated by the core network device.

[0225] Optionally, if the first message is triggered by a process initiated by the first access network device, the communication unit 510 is further configured to: send a second message to the core network device, where the second message is used to request paging cause value auxiliary information.

[0226] Optionally, the second message is an empty message or a non-empty message.

[0227] Optionally, when the second message is a non-empty message, the second message is a dedicated message for a specific terminal device or a common message not for a specific terminal device.

[0228] Optionally, when the second message is a dedicated message for a specific terminal device, the second message is any one of the following:

[0229] PDU session establishment message for a specific terminal device.

[0230] PDU session modification message for a specific terminal device.

[0231] PDU session reconstruction message for a specific terminal device.

[0232] PDU session release message for a specific terminal device.

[0233] Context establishment message for a specific terminal device.

[0234] Context modification message for a specific terminal device.

[0235] Context reconstruction message for a specific terminal device.

[0236] Context release message for a specific terminal device.

[0237] RRC status acquisition message for a specific terminal device.

[0238] Optionally, when the second message is a common message not for a specific terminal device, the second message is any one of the following:

[0239] Interface initialization message.

[0240] Interface update message.

[0241] Resource reporting message.

[0242] Abnormal reporting message.

[0243] Optionally, when the second message is a non-empty message, the second message includes at least one of the following:

[0244] Indication information for requesting the paging cause value auxiliary information from the core network device.

[0245] PDU session identifier list information that needs to obtain the paging cause value auxiliary information.

[0246] QoS flow value list information that needs to obtain the paging cause value auxiliary information.

[0247] Slice identifier list information that needs to obtain the paging cause value auxiliary information.

[0248] Indication information for the encryption rule that the paging cause value to be encrypted needs to follow.

[0249] Optionally, the first paging cause value is an encrypted paging cause value or an unencrypted paging cause value.

[0250] Optionally, in some embodiments, the above communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-chip.

[0251] It should be understood that the access network device 500 according to the embodiments of the present application may correspond to the first access network device in the method embodiments, and the above and other operations and / or functions of each unit in the access network device 500 respectively implement the corresponding processes of the first access network device in the method embodiments. For the sake of brevity, they will not be described in detail here.

[0252] Figure 6 Fig. shows a schematic block diagram of an access network device 600 according to an embodiment of the present application. The access network device 600 is a second access network device, such as Figure 6 As shown, a communication unit 610 is configured to receive a paging message sent by a first access network device, where the paging message includes: a first paging cause value.

[0253] Optionally, the first paging cause value is an encrypted paging cause value or an unencrypted paging cause value.

[0254] Optionally, in some embodiments, the above communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-chip.

[0255] It should be understood that the access network device 600 according to the embodiments of the present application may correspond to the second access network device in the method embodiments, and the above and other operations and / or functions of each unit in the access network device 600 respectively implement the corresponding processes of the second access network device in the method embodiments. For the sake of brevity, they will not be described in detail here.

[0256] Figure 7FIG. 0 shows a schematic block diagram of a network device 700 according to an embodiment of the present application. As Figure 7 shown, the network device 700 includes: a communication unit 710, configured to send paging cause value auxiliary information to a first access network device. The paging cause value auxiliary information is used to assist the first access network device in determining a first paging cause value.

[0257] Optionally, the paging cause value auxiliary information includes at least one of the following:

[0258] At least one paging cause value.

[0259] The PDU session identifier associated with each paging cause value.

[0260] The QoS flow value associated with each paging cause value.

[0261] The slice identifier associated with each paging cause value.

[0262] The encryption rule that the paging cause value to be encrypted needs to follow.

[0263] Optionally, the mapping relationship between the paging cause value and the PDU session identifier is a one-to-one, one-to-many, or many-to-one mapping relationship. And / or, the mapping relationship between the paging cause value and the QoS flow value is a one-to-one, one-to-many, or many-to-one mapping relationship. And / or, the mapping relationship between the paging cause value and the slice identifier is a one-to-one, one-to-many, or many-to-one mapping relationship.

[0264] Optionally, any one of the at least one paging cause value is an encrypted paging cause value or an unencrypted paging cause value.

[0265] Optionally, the network device is a core network device or an OAM node.

[0266] Optionally, when the network device is a core network device, the communication unit 710 is specifically configured to: send a first message to the first access network device, where the first message includes: the paging cause value auxiliary information.

[0267] Optionally, the first message is a dedicated message for a specific terminal device, or a common message that is not for a specific terminal device.

[0268] Optionally, when the first message is a dedicated message for a specific terminal device, the first message is any one of the following:

[0269] The PDU session establishment message of the specific terminal device.

[0270] The PDU session modification message of the specific terminal device.

[0271] The PDU session reconstruction message of the specific terminal device.

[0272] PDU session release message of a specific terminal device.

[0273] Context establishment message of a specific terminal device.

[0274] Context modification message of a specific terminal device.

[0275] Context reconstruction message of a specific terminal device.

[0276] Context release message of a specific terminal device.

[0277] Radio Resource Control (RRC) status acquisition message of a specific terminal device.

[0278] Optionally, when the first message is not a common message for a specific terminal device, the first message is any one of the following:

[0279] Interface initialization message.

[0280] Interface update message.

[0281] Resource reporting message.

[0282] Exception reporting message.

[0283] Optionally, the first message is triggered by a process initiated by the first access network device or by a process initiated by the core network device.

[0284] Optionally, if the first message is triggered by a process initiated by the first access network device, the communication unit 710 is further configured to: receive a second message sent by the first access network device, where the second message is used to request paging cause value auxiliary information.

[0285] Optionally, the second message is an empty message or a non-empty message.

[0286] Optionally, when the second message is a non-empty message, the second message is a dedicated message for a specific terminal device or a common message not for a specific terminal device.

[0287] Optionally, when the second message is a dedicated message for a specific terminal device, the second message is any one of the following:

[0288] PDU session establishment message of a specific terminal device.

[0289] PDU session modification message of a specific terminal device.

[0290] PDU session reconstruction message of a specific terminal device.

[0291] PDU session release message of a specific terminal device.

[0292] Context establishment message of a specific terminal device.

[0293] Context modification message for a specific terminal device.

[0294] Context reconstruction message for a specific terminal device.

[0295] Context release message for a specific terminal device.

[0296] RRC status acquisition message for a specific terminal device.

[0297] Optionally, when the second message is not a common message for a specific terminal device, the second message is any one of the following:

[0298] Interface initialization message.

[0299] Interface update message.

[0300] Resource reporting message.

[0301] Exception reporting message.

[0302] Optionally, when the second message is a non-empty message, the second message includes at least one of the following:

[0303] Indication information for requesting paging cause value auxiliary information from the core network device.

[0304] PDU session identifier list information for which paging cause value auxiliary information needs to be obtained.

[0305] QoS flow value list information for which paging cause value auxiliary information needs to be obtained.

[0306] Slice identifier list information for which paging cause value auxiliary information needs to be obtained.

[0307] Indication information for the encryption rule that needs to be followed for the paging cause value to be encrypted.

[0308] Optionally, the first paging cause value is an encrypted paging cause value or an unencrypted paging cause value.

[0309] Optionally, in some embodiments, the above communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-chip.

[0310] It should be understood that the network device 700 according to the embodiments of the present application may correspond to the network device in the method embodiments, and the above and other operations and / or functions of each unit in the network device 700 respectively implement the corresponding processes of the network device in the method embodiments. For the sake of brevity, they are not described herein again.

[0311] Figure 8 Fig. shows a schematic block diagram of a terminal device 800 according to an embodiment of the present application. AsFigure 8 As shown in the figure, the terminal device 800 includes: a communication unit 810, configured to receive a paging message sent by a second access network device, where the paging message includes: a first paging cause value.

[0312] Optionally, the first paging cause value is an encrypted paging cause value or an unencrypted paging cause value.

[0313] Optionally, when the first paging cause value is an encrypted paging cause value, the terminal device further includes: a processing unit 820, configured to decrypt the first paging cause value according to a decryption rule.

[0314] Optionally, the decryption rule is pre-configured for the terminal device, or is obtained by the terminal device through a NAS procedure.

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

[0316] It should be understood that the terminal device 800 according to the embodiments of the present application may correspond to the terminal device in the method embodiments of the present application, and the above and other operations and / or functions of each unit in the terminal device 800 respectively implement the corresponding processes of the terminal device in the above method embodiments. For the sake of brevity, they will not be described in detail here.

[0317] Figure 9 It is a schematic structural diagram of a communication device 900 provided by an embodiment of the present application. Figure 9 The shown communication device 900 includes a processor 910, and the processor 910 may call and run a computer program from a memory to implement the method in the embodiments of the present application.

[0318] Optionally, as Figure 9 shown, the communication device 900 may further include a memory 920. Among them, the processor 910 may call and run a computer program from the memory 920 to implement the method in the embodiments of the present application.

[0319] Among them, the memory 920 may be a separate device independent of the processor 910, or may be integrated in the processor 910.

[0320] Optionally, as Figure 9 shown, the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices. Specifically, it may send information or data to other devices, or receive information or data sent by other devices.

[0321] Among them, the transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include an antenna, and the number of antennas may be one or more.

[0322] Optionally, the communication device 900 may specifically be the first access network device of the embodiments of the present application, and the communication device 900 may implement the corresponding processes implemented by the first access network device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0323] Optionally, the communication device 900 may specifically be the second access network device of the embodiments of the present application, and the communication device 900 may implement the corresponding processes implemented by the second access network device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0324] Optionally, the communication device 900 may specifically be the network device of the embodiments of the present application, and the communication device 900 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0325] Optionally, the communication device 900 may specifically be the terminal device of the embodiments of the present application, and the communication device 900 may implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0326] Figure 10 is a schematic structural diagram of the device of the embodiments of the present application. Figure 10 The illustrated device 1000 includes a processor 1010. The processor 1010 may call and run a computer program from a memory to implement the methods in the embodiments of the present application.

[0327] Optionally, as Figure 10 shown, the device 1000 may further include a memory 1020. Among them, the processor 1010 may call and run a computer program from the memory 1020 to implement the methods in the embodiments of the present application.

[0328] Among them, the memory 1020 may be a separate device independent of the processor 1010 or may be integrated in the processor 1010.

[0329] Optionally, the device 1000 may further include an input interface 1030. Among them, the processor 1010 may control the input interface 1030 to communicate with other devices or chips. Specifically, it may obtain information or data sent by other devices or chips.

[0330] Optionally, the device 1000 may further include an output interface 1040. The processor 1010 may control the output interface 1040 to communicate with other devices or chips. Specifically, it may output information or data to other devices or chips.

[0331] Optionally, the device may be applied to the first access network device in the embodiments of the present application, and the device may implement the corresponding processes implemented by the first access network device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0332] Optionally, the device may be applied to the second access network device in the embodiments of the present application, and the device may implement the corresponding processes implemented by the second access network device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0333] Optionally, the device may be applied to the network device in the embodiments of the present application, and the device may implement the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

[0334] Optionally, the device may be applied to the terminal device in the embodiments of the present application, and the device may implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, details are not described herein again.

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

[0336] It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiments can be completed by the integrated logic circuit in the hardware of the processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being 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 a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0337] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (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.

[0338] It should be understood that the above-mentioned memory is by way of example but not limitation. For example, the memory in the embodiments of the present application can also be a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synch link dynamic random access memory (SLDRAM), and a direct rambus random access memory (DR RAM), and so on. That is to say, the memory in the embodiments of the present application is intended to include but not be limited to these and any other suitable types of memory.

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

[0340] Optionally, the computer-readable storage medium can be applied to the network device or base station in the embodiment of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device or base station in the various methods of the embodiment of the present application. For the sake of brevity, it will not be elaborated here.

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

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

[0343] Optionally, the computer program product can be applied to the network device or base station in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device or base station in the various methods of the embodiment of the present application. For the sake of brevity, it will not be elaborated here.

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

[0345] An embodiment of the present application also provides a computer program.

[0346] Optionally, the computer program can be applied to the network device or base station in the embodiment of the present application. When the computer program runs on the computer, it enables the computer to execute the corresponding processes implemented by the network device or base station in the various methods of the embodiment of the present application. For the sake of brevity, it will not be elaborated here.

[0347] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiment of the present application. When the computer program runs on the computer, it enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiment of the present application. For the sake of brevity, it will not be elaborated here.

[0348] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled professionals may use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0349] Those skilled in the art can clearly understand that for the sake of convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein.

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

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

[0352] In addition, the functional units in each embodiment of this application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0353] When the above-mentioned functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. With this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing 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 various embodiments of this application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROM), random access memories (RAM), magnetic disks, or optical discs that can store program codes.

[0354] As described above, the above are only specific implementation manners of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed by this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that: include: The first access network device obtains paging cause value auxiliary information from the network device, where the paging cause value auxiliary information is used to assist the first access network device in determining a first paging cause value; The first access network device sends a paging message to the second access network device, where the paging message includes: the first paging reason value; Among them, the first access network device is an anchor access network device, the second access network device is an access network device in the paging area configuration information configured for the terminal device, and the network device is a core network device.

2. The method according to claim 1, characterized in that The paging cause value auxiliary information includes at least one of the following: At least one paging cause value; A protocol data unit PDU session identifier associated with each of the paging cause values; A quality of service QoS flow value associated with each of the paging cause values; A slice identifier associated with each of the paging cause values; The encryption rules that the paging reason value to be encrypted needs to follow.

3. The method according to claim 1 or 2, characterized in that: The first access network device obtains the paging cause value auxiliary information from the network device, including: The first access network device receives a first message sent by the core network device, where the first message includes: the paging cause value auxiliary information.

4. The method according to claim 3, characterized in that The first message is a dedicated message for a specific terminal device, or is a public message not for a specific terminal device.

5. A wireless communication method, characterized in that: include: The terminal device receives a paging message sent by the second access network device, where the paging message includes: a first paging reason value; The first paging reason value is determined based on the following steps: The first access network device obtains paging reason value auxiliary information from a network device, and the paging reason value auxiliary information is used to assist the first access network device in determining the first paging reason value. The first access network device is an anchor access network device, and the second access network device is an access network device in the paging area configuration information configured for the terminal device. The network device is a core network device.

6. An access network device, the access network device being a first access network device, characterized in that: include: a communication unit, configured to obtain paging cause value auxiliary information from a network device, wherein the paging cause value auxiliary information is used to assist the first access network device in determining a first paging cause value; The communication unit is further configured to send a paging message to the second access network device, wherein the paging message includes: a first paging reason value; Among them, the first access network device is an anchor access network device, the second access network device is an access network device in the paging area configuration information configured for the terminal device, and the network device is a core network device.

7. A terminal device, characterized in that: include: A communication unit, configured to receive a paging message sent by a second access network device, wherein the paging message includes: a first paging reason value; The first paging reason value is determined based on the following steps: The first access network device obtains paging reason value auxiliary information from a network device, and the paging reason value auxiliary information is used to assist the first access network device in determining the first paging reason value. The first access network device is an anchor access network device, and the second access network device is an access network device in the paging area configuration information configured for the terminal device. The network device is a core network device.

8. An access network device, the access network device being a first access network device, characterized in that: include: A processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 4.

9. A terminal device, characterized in that: include: A processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method as claimed in claim 5.

Images