Communication method and communication device

Abstract

The invention provides a communication method and a communication device. The method comprises the following steps: receiving first indication information, wherein the first indication information is used for indicating the priority of terminal equipment; and generating first information according to the first indication information, the first information being used for configuring a backoff timer of the terminal device. And sending the first information. Through the method, the UE urgently having a network demand can enter the network as soon as possible, and the user urgently having the network demand can access the network in an off-peak manner, so that the demand of timely network access of the high-priority UE is met, the balance of network access of different types of UE is achieved, the influence on the user experience is kept within a controllable range when the AMF is congested, and the user experience is improved. And the satisfaction degree of the user is improved.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly, to a communication method and a communication device. Background Art

[0002] If a large number of user equipments (UEs) simultaneously attempt to access a network device and initiate non-access stratum (NAS) requests to an access and mobility management function (AMF) network element, when it exceeds the processing capacity range of the AMF, it may cause congestion in the AMF. When the AMF is congested and unable to handle the requests of these UEs, the AMF will allocate a back-off timer to each UE or each group of UEs. When a UE receives a rejection message containing the back-off timer, the UE will start the timer locally. Before the timer expires, the UE will not initiate a NAS request to the network again; only after the timer expires will the UE re-initiate the registered NAS request.

[0003] The duration of the back-off timer will be adjusted according to a random algorithm so that UE devices wait for different time intervals during the delayed period. This can avoid multiple UE devices attempting to retransmit at the same time. However, the random time period set by the back-off timer will increase the delay of data retransmission; and due to the uncertainty of the data transmission time during the back-off timer period, the back-off timer may cause some access points to obtain more transmission opportunities while excluding other access points, which will lead to network unfairness and may even cause other devices not to obtain satisfactory transmission opportunities.

[0004] Therefore, how to set a reasonable back-off timer is one of the technical problems that need to be urgently solved by those skilled in the art. Summary of the Invention

[0005] This application provides a communication method and a communication device. By setting different priorities for UEs and allocating back-off timers with different durations to UEs with different priorities, UEs with different urgencies for network requirements can access the network in batches, improving the utilization rate of network resources and also improving the satisfaction of overall users.

[0006] In a first aspect, a communication method is provided. This method can be executed by an AMF network element, or can also be executed by a component (such as a chip or a circuit) of the AMF network element, and this is not limited.

[0007] The method may include: receiving first indication information for indicating the priority of a terminal device; generating first information for configuring a backoff timer of the terminal device according to the first indication information; and sending the first information.

[0008] Based on the above technical solution, the first indication information received by the AMF carries priority indication information of the terminal device, and the AMF configures a reasonable backoff timer for the terminal device according to the priority indication information. By guiding the UE to access the network in batches according to its own priority level, network congestion is alleviated. UEs with more urgent network requirements can enter the network as soon as possible, and UEs with general urgent network requirements can access the network during off-peak hours to meet the timely network access requirements of high-priority UEs, achieving a balance in the network access of different types of UEs, so that the impact on user experience is kept within a controllable range when the AMF is congested, and user satisfaction is improved.

[0009] It should be understood that in an optional implementation manner, the first indication information is the priority indication (priority indication) of the UE for indicating the priority of the UE.

[0010] In another optional implementation manner, the first indication information includes the priority indication (priority indication) of the UE, that is, the first indication information includes a field for indicating the priority of the UE.

[0011] It should be understood that the first indication information includes the registration request information of the UE, or service request information, etc. The first indication information refers to the priority of the UE to access the network. The first indication information can be uniformly formulated for all UE devices according to a certain rule, or can be uniformly allocated by the operator, and this application does not make special limitations on this.

[0012] It should be understood that in an optional implementation manner, the first information carries a backoff timer configured for the terminal device, and the terminal device starts and / or configures its own backoff timer according to the first information after receiving it.

[0013] It should be understood that in another optional implementation manner, the first information carries indication information for configuring the duration of the backoff timer of the terminal device, and the terminal device configures its own backoff timer according to the first information after receiving it.

[0014] In combination with the first aspect, in some implementation manners of the first aspect, it further includes receiving second information, performing a registration process of the terminal device according to the second information and obtaining subscription information of the terminal device. Obtaining the priority of the terminal device according to the subscription information, and generating first indication information according to the priority of the terminal device. Sending third information, where the third information carries the first indication information.

[0015] Based on the above technical solution, when the UE does not carry its own priority indication information when first accessing the network, the priority indication can be allocated by the operator and stored in the unified data management (UDM) network element. The AMF obtains the subscription information of the UE from the UDM network element. The AMF generates the priority indication information of the UE according to the priority information in the subscription information, and carries it to the UE in the registration approval information when the UE first accesses the network. The UE carries the priority indication information provided by the AMF in subsequent registration requests or service requests. When the AMF is congested, the AMF can set a reasonable backoff timer value for the UE according to the priority indication.

[0016] In combination with the first aspect, in some implementation manners of the first aspect, it further includes receiving a fourth piece of information, where the fourth piece of information carries a second indication information. The second indication information is used to indicate the initial priority of the terminal device. According to the second indication information, the priority of the terminal device is determined, and the first indication information is generated according to the priority of the terminal device. A third piece of information is sent, and the third piece of information carries the first indication information.

[0017] Based on the above technical solution, the UE carries the initial priority information in the sent information. The AMF can generate the priority indication information of the UE according to the initial priority information carried in the UE request, and send the priority indication information to the UE. The AMF side can recognize the meaning represented by the priority indication information, which can effectively prevent the UE side from tampering with its own priority information, protect the security of the priority information, and maintain the relative fairness of the network access environment.

[0018] In combination with the first aspect, in some implementation manners of the first aspect, it further includes performing a registration process of the terminal device according to the fourth piece of information and obtaining the subscription information of the terminal device. The priority of the terminal device is obtained according to the subscription information, and the first indication information is obtained according to the priority of the terminal device.

[0019] Based on the above technical solution, the UE carries the initial priority information in the sent information. The AMF can register with the UDM according to the UE request and obtain the subscription information of the UE, obtain the latest priority information of the UE from the UDM to overwrite the initial priority information, generate the priority indication information of the UE, and send the priority indication information to the UE. The AMF side can recognize the meaning represented by the priority indication information, which can effectively prevent the UE side from tampering with its own priority information, protect the security of the priority information, and maintain the relative fairness of the network access environment.

[0020] In combination with the first aspect, in some implementation manners of the first aspect, the first indication information is determined by the type of the terminal device.

[0021] Based on the above technical solution, the AMF can configure different priority indications for the UE according to the type of the UE. The UE carries its own priority indication in the network access request message. When there is congestion, the AMF sets different backoff timers for the UEs that need congestion control according to the priority indication information of the UE. This enables UEs with more urgent network requirements to enter the network as soon as possible, and enables users with generally urgent network requirements to access the network during off-peak hours, so as to meet the need for high-priority UEs to enter the network in a timely manner, achieve a balance in the access of different types of UEs to the network, keep the impact on the user experience within a controllable range when the AMF is congested, and improve user satisfaction.

[0022] In combination with the first aspect, in some implementation manners of the first aspect, it further includes receiving a fifth piece of information. The fifth piece of information is used to indicate the degree of dependence of the terminal device on the network. The priority of the terminal device is judged according to the fifth piece of information, and the first indication information is determined according to the priority of the terminal device. The third piece of information is sent, and the third piece of information carries the first indication information.

[0023] Based on the above technical solution, the AMF can generate the priority indication information of the UE according to the analysis of the degree of dependence of the obtained UE on the network, and can more accurately judge the priority of the UE according to the network access habits of the UE, configure a more reasonable backoff timer for the UE, further improve the overall user experience, and more accurately reflect the actual situation of the priority of the UE.

[0024] In combination with the first aspect, in some implementation manners of the first aspect, it further includes sending a sixth piece of information, and the sixth piece of information is used to subscribe to the analysis result based on the behavior information of the terminal device. The analysis result includes the fifth piece of information.

[0025] Based on the above technical solution, the AMF can generate the priority indication information of the UE according to the analysis of the degree of dependence of the obtained UE on the network, and can more accurately judge the priority of the UE according to the network access habits of the UE, configure a more reasonable backoff timer for the UE, further improve the overall user experience, and more accurately reflect the actual situation of the priority of the UE.

[0026] It should be understood that in different implementation manners of the present application, the fields of the indication information with the same function generated according to different manners may be the same or different, and the present application does not make special limitations thereon. Specifically, for example, the first indication information sent by the terminal device is used to indicate its own priority level. In different implementation manners, the fields of the first indication information may be the same or different, and the present application does not make special limitations thereon. For another example, the first indication information is carried in the third information sent by the AMF. In different implementation manners, the fields of the third information may be the same or different, and the present application does not make special limitations thereon. It should be understood that the same is true for other information, and the present application will not elaborate herein.

[0027] In a second aspect, a communication method is provided. This method may be executed by a network data analytics function (NWDAF) network element, or alternatively, may be executed by a component (such as a chip or a circuit) of the NWDAF network element, and no limitation is made thereto.

[0028] The method may include: receiving sixth information, where the sixth information carries information of the terminal device. According to the sixth information, obtaining the behavior information of the terminal device, and analyzing the degree of dependence of the terminal device on the network based on the behavior information. Sending fifth information, where the fifth information is used to indicate the degree of dependence of the terminal device on the network. The fifth information is further used to instruct the first network device to configure a backoff timer for the terminal device.

[0029] It should be understood that in an optional implementation manner, the first network device includes an AMF network element.

[0030] Based on the above technical solution, the AMF can generate the priority indication information of the UE according to the analysis of the degree of dependence of the UE on the network, and can more accurately judge the priority of the UE according to the network access habit of the UE, configure a more reasonable backoff timer for the UE, further improve the overall user experience, and more accurately reflect the actual situation of the priority of the UE.

[0031] In combination with the second aspect, in some implementation manners of the second aspect, the fifth information is further used to instruct the first network device to generate first indication information, where the first indication information is used to indicate the priority of the terminal device. The first network device generates first information according to the first indication information, and the first information is used to configure the backoff timer of the terminal device.

[0032] Based on the above technical solution, the first indication information received by the AMF carries the priority indication information of the terminal device, and the AMF configures a reasonable backoff timer for the terminal device according to the priority indication information. By guiding the UE to access the network in batches according to its own priority level, network congestion is alleviated. This enables UEs with more urgent network requirements to enter the network as soon as possible, and UEs with generally urgent network requirements to access the network during off-peak hours, so as to meet the timely network access needs of high-priority UEs, achieve a balance in the network access of different types of UEs, keep the impact on the user experience within a controllable range when the AMF is congested, and improve user satisfaction.

[0033] In combination with the second aspect, in some implementation manners of the second aspect, the sixth information carries a device list or an area of interest of the terminal device.

[0034] Based on the above technical solution, the AMF can generate the priority indication information of the UE according to the analysis of the degree of network dependence of the obtained UE, and can more accurately judge the priority of the UE according to the network access habit of the UE, configure a more reasonable backoff timer for the UE, further improve the overall user experience, and more accurately reflect the actual situation of the UE's priority.

[0035] In combination with the second aspect, in some implementation manners of the second aspect, the fifth information includes an analysis of the degree of network dependence of the terminal device at different time periods.

[0036] Based on the above technical solution, the AMF can generate the priority indication information of the UE according to the analysis of the degree of network dependence of the obtained UE, and can more accurately judge the priority of the UE according to the network access habit of the UE, configure a more reasonable backoff timer for the UE, further improve the overall user experience, and more accurately reflect the actual situation of the UE's priority.

[0037] In a third aspect, a communication method is provided. This method can be executed by the terminal device, or can also be executed by components (such as chips or circuits) of the terminal device, and this is not limited.

[0038] The method may include: sending first indication information, where the first indication information is used to indicate the priority of the terminal device. The priority is used to indicate that the network device allocates a backoff timer for the terminal device. Receiving first information and configuring the backoff timer of the terminal device according to the first information.

[0039] Based on the above technical solution, the first indication information sent by the terminal device carries its own priority information. The AMF allocates a reasonable timer for the UE according to the priority information of the UE. The UE configures its own backoff timer according to the received first information, and initiates an access request again after the timer expires. By guiding the UE to access the network in batches according to its own priority level, network congestion is alleviated. This enables UEs with more urgent network requirements to enter the network as soon as possible, and for users with moderately urgent network requirements to access the network during off-peak hours, so as to meet the timely network access requirements of high-priority UEs, achieve a balance in the network access of different types of UEs, and keep the impact on user experience within a controllable range when the AMF is congested, thereby improving user satisfaction.

[0040] Combined with the third aspect, in some implementation manners of the third aspect, it further includes sending a second message, which is used to indicate the execution of the registration process of the terminal device and obtain the subscription information of the terminal device. The subscription information is used to indicate obtaining the priority of the terminal device. Receive a third message, which carries the priority information of the terminal device. Generate the first indication information according to the third message.

[0041] Based on the above technical solution, when the UE does not carry its own priority indication information during the first network access, the priority indication can be allocated by the operator and stored in the unified data management (UDM) network element. The AMF obtains the subscription information of the UE from the UDM network element. The AMF generates the priority indication information of the UE according to the priority information in the subscription information, and carries it in the registration approval information of the UE's first network access and sends it to the UE. The UE carries the priority indication information provided by the AMF in subsequent registration requests or service requests. When the AMF is congested, the AMF can set a reasonable value for the backoff timer of the UE according to the priority indication.

[0042] Combined with the third aspect, in some implementation manners of the third aspect, it further includes sending a fourth message, which carries a second indication information, and the second indication information is used to indicate the initial priority of the terminal device. Receive a third message, which carries the updated priority information of the terminal device. Generate the first indication information according to the third message.

[0043] Based on the above technical solution, the UE carries the initial priority information in the sent message. The AMF can generate the priority indication information of the UE according to the initial priority information carried in the UE request, and send the priority indication information to the UE. The AMF side can recognize the meaning represented by the priority indication information, which can effectively prevent the UE side from tampering with its own priority information, protect the security of the priority information, and maintain the relative fairness of the network access environment.

[0044] In combination with the third aspect, in some implementation manners of the third aspect, the fourth information is further used to indicate the execution of the registration process of the terminal device and obtain the subscription information of the terminal device. The subscription information is used to indicate the acquisition of the updated priority information of the terminal device.

[0045] Based on the above technical solution, the UE carries the initial priority information in the sent information. The AMF can register with the UDM according to the UE request and obtain the subscription information of the UE, obtain the latest priority information of the UE from the UDM to overwrite the initial priority information, generate the priority indication information of the UE, and send the priority indication information to the UE. The AMF side can identify the meaning represented by the priority indication information, which can effectively prevent the UE side from tampering with its own priority information, protect the security of the priority information, and maintain the relative fairness of the network access environment.

[0046] In combination with the third aspect, in some implementation manners of the third aspect, the first indication information is determined by the type of the terminal device.

[0047] Based on the above technical solution, different priority indications can be configured for the UE according to the type of the UE. The UE carries its own priority indication in the network access request message. When there is congestion, the AMF sets different backoff timers for the UEs that need congestion control according to the priority indication information of the UE. This enables the UEs with more urgent network requirements to enter the network as soon as possible, and the users with generally urgent network requirements to access the network during off-peak hours, so as to meet the timely network access requirements of high-priority UEs, achieve the balance of network access for different types of UEs, keep the impact on the user experience within a controllable range when the AMF is congested, and improve user satisfaction.

[0048] In combination with the third aspect, in some implementation manners of the third aspect, it further includes receiving third information, and the third information carries the first indication information. The first indication information is determined according to the degree of dependence of the terminal device on the network.

[0049] Based on the above technical solution, the first indication information carries the priority indication information of the terminal device, and the AMF configures a reasonable backoff timer for the terminal device according to the priority indication information. By guiding the UE to access the network in batches according to its own priority level, network congestion is alleviated. This enables the UEs with more urgent network requirements to enter the network as soon as possible, and the users with generally urgent network requirements to access the network during off-peak hours, so as to meet the timely network access requirements of high-priority UEs, achieve the balance of network access for different types of UEs, keep the impact on the user experience within a controllable range when the AMF is congested, and improve user satisfaction.

[0050] Fourthly, a communication device is provided, which is used to execute the methods provided in the first to third aspects above. Specifically, the device may include units and / or modules for executing the methods provided in any of the above implementation manners of the first to third aspects, such as a processing unit and / or a communication unit.

[0051] In one implementation manner, the device is a terminal device. When the device is a terminal device, the communication unit may be a transceiver, or an input / output interface; the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0052] In another implementation manner, the device is a chip, a chip system or a circuit in a terminal device. When the device is a chip, a chip system or a circuit in a terminal device, the communication unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc. on the chip, the chip system or the circuit; the processing unit may be at least one processor, a processing circuit or a logic circuit, etc.

[0053] In one implementation manner, the device is an AMF network element. When the device is an AMF network element, the communication unit may be a transceiver, or an input / output interface; the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0054] In another implementation manner, the device is a chip, a chip system or a circuit in an AMF network element. When the device is a chip, a chip system or a circuit in an AMF network element, the communication unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc. on the chip, the chip system or the circuit; the processing unit may be at least one processor, a processing circuit or a logic circuit, etc.

[0055] In one implementation manner, the device is an NWDAF network element. When the device is an NWDAF network element, the communication unit may be a transceiver, or an input / output interface; the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0056] In another implementation manner, the device is a chip, a chip system or a circuit in an NWDAF network element. When the device is a chip, a chip system or a circuit in an NWDAF network element, the communication unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc. on the chip, the chip system or the circuit; the processing unit may be at least one processor, a processing circuit or a logic circuit, etc.

[0057] In a fifth aspect, a communication device is provided, which includes: a memory for storing programs; and at least one processor for executing the computer programs or instructions stored in the memory to execute any of the above implementation manners of the first to third aspects, or the method provided by any of the above implementation manners of the first to third aspects.

[0058] In one implementation manner, the device is a terminal device.

[0059] In another implementation manner, the device is a chip, a chip system or a circuit in a terminal device.

[0060] In one implementation manner, the device is an AMF network element.

[0061] In another implementation manner, the device is a chip, a chip system or a circuit in an AMF network element.

[0062] In one implementation manner, the device is an NWDAF network element.

[0063] In another implementation manner, the device is a chip, a chip system or a circuit in an NWDAF network element.

[0064] In a sixth aspect, the present application provides a processor for executing the methods provided in the above aspects.

[0065] For operations such as sending and obtaining / receiving involved in the processor, if there is no special description, or if it does not conflict with its actual role or internal logic in the relevant description, it can be understood as operations such as outputting, receiving, and inputting by the processor, or it can also be understood as sending and receiving operations performed by the radio frequency circuit and the antenna. The present application does not make any limitations in this regard.

[0066] In a seventh aspect, a computer-readable storage medium is provided, which stores program codes for a device to execute. The program codes include methods for executing any of the above implementation manners provided by the first to third aspects.

[0067] In an eighth aspect, a computer program product containing instructions is provided. When the computer program product runs on a computer, it causes the computer to execute the methods provided by any of the above implementation manners of the first to third aspects.

[0068] In a ninth aspect, a chip is provided. The chip includes a processor and a communication interface. The processor reads instructions stored on a memory through the communication interface and executes the methods provided by any of the above implementation manners of the first to third aspects.

[0069] Optionally, as an implementation, the chip further includes a memory, in which computer programs or instructions are stored, and the processor is configured to execute the computer programs or instructions stored on the memory. When the computer programs or instructions are executed, the processor is configured to execute the method provided by any one of the above implementations in the first aspect to the third aspect.

[0070] In a tenth aspect, a communication system is provided, including the AMF network element in the first aspect above and the terminal device in the third aspect above.

[0071] In an eleventh aspect, a communication system is provided, including the AMF network element in the first aspect above, the NWDAF network element in the second aspect above, and the terminal device in the third aspect above. Description of the Drawings

[0072] Figure 1 is a schematic diagram of a network architecture to which the technical solution of the present application can be applied.

[0073] Figure 2 is a schematic diagram of allocating a backoff timer provided by an embodiment of the present application.

[0074] Figure 3 is a schematic diagram of the scenario to which the present application is applied.

[0075] Figure 4 is a schematic flowchart of a communication method provided by an embodiment of the present application.

[0076] Figure 5 is a schematic flowchart of a UE accessing the network in a congestion scenario provided by an embodiment of the present application.

[0077] Figure 6 is a schematic flowchart of another UE accessing the network in a congestion scenario provided by an embodiment of the present application.

[0078] Figure 7 is a schematic flowchart of another UE accessing the network in a congestion scenario provided by an embodiment of the present application.

[0079] Figure 8 is a schematic flowchart of another UE accessing the network in a congestion scenario provided by an embodiment of the present application.

[0080] Figure 9 is a schematic flowchart of another UE accessing the network in a congestion scenario provided by an embodiment of the present application.

[0081] Figure 10 shows a schematic block diagram of the communication device 10 provided by an embodiment of the present application.

[0082] Figure 11 shows a schematic diagram of another communication device 20 provided by an embodiment of the present application.

[0083] Figure 12 FIG. shows a schematic diagram of a chip system 30 provided by an embodiment of the present application. Detailed implementation manners

[0084] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0085] To facilitate understanding of the embodiments of the present application, the following points are explained before introducing the embodiments of the present application.

[0086] In the present application, "for indicating" or "indicating" may include for directly indicating and for indirectly indicating, or in other words, "for indicating" or "indicating" may explicitly and / or implicitly indicate. For example, when describing that a certain piece of information is for indicating information I, it may include that the information directly indicates I or indirectly indicates I, and it does not necessarily mean that I is carried in the information. Another example, implicit indication may be based on the position and / or resources for transmission; explicit indication may be based on one or more parameters, and / or one or more indexes, and / or one or more bit patterns it represents.

[0087] The definitions listed for many characteristics in the present application are only used to explain the functions of the characteristics by way of example, and the detailed content can refer to the prior art.

[0088] In the embodiments shown below, the first, second, third, fourth, and various numerical numbers are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. For example, to distinguish different fields, different information, etc.

[0089] "Pre-defined" can be implemented by pre-saving the corresponding codes, tables or other ways that can be used to indicate relevant information in the device, and the present application does not limit its specific implementation manner. Among them, "saving" may mean saving in one or more memories. The type of memory can be any form of storage medium, and the present application does not limit this.

[0090] The "protocol" involved in the embodiments of the present application may refer to the standard protocols in the communication field. For example, it may include long term evolution (LTE) protocol, new radio (NR) protocol, and related protocols applied to future communication systems. The present application does not limit this.

[0091] The present application will present various aspects, embodiments or features around a system including multiple devices, components, modules, etc. It should be understood and clear that each system may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. In addition, combinations of these solutions can also be used.

[0092] In the embodiments of the present application, words such as "exemplary", "for example", "exemplarily", "as another example", etc. are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of the word "exemplary" is intended to present concepts in a specific manner.

[0093] The terms "comprise", "include", "have" and their variants all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0094] "At least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after. "At least one (item)" or its similar expression refers to any combination of these items, including any combination of single item (s) or plural items (s). For example, at least one (item) of a, b and c can represent: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b and c. Where a, b and c can be single or multiple respectively.

[0095] In the embodiments of the present application, the relevant descriptions regarding the network element A sending messages, information or data to the network element B, and the network element B receiving messages, information or data from the network element A are intended to illustrate which network element the message, information or data is to be sent to, rather than limiting whether they are directly sent or indirectly sent via other network elements.

[0096] In the embodiments of the present application, descriptions such as "when...", "in the case of...", "if" and "when" all refer to the device making corresponding processing under a certain objective situation, not limiting the time, and do not require the device to have a judgment action when implemented, nor does it mean that there are other limitations.

[0097] The technical solutions provided by this application can be applied to various communication systems. For example, the fifth-generation (5G) or NR system, LTE system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, etc. The technical solutions provided by this application can also be applied to non-terrestrial network (NTN) communication systems such as satellite communication systems. The technical solutions provided by this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems. The technical solutions provided by this application can also be applied to future communication systems such as the sixth-generation mobile communication system.

[0098] As an example, Figure 1 shows a schematic diagram of a network architecture.

[0099] Such as Figure 1As shown, this network architecture takes the 5th generation system (5GS) as an example. This network architecture can include three parts, namely the user equipment (UE) part, the data network (DN) part, and the operator network part. Among them, the operator network can include one or more of the following network elements: (radio) access network ((R)AN) equipment, user plane function (UPF) network element, unified data management (UDM) network element, operations, administration and management (OAM) network element, access and mobility management function (AMF) network element, session management function (SMF) network element, network exposure function (NEF) network element, network repository function (NRF) network element, network data analytics function (NWDAF) network element, application function (AF) network element, policy control function (PCF) network element, and unified data repository (UDR) network element. In the above operator network, the part other than the RAN part can be called the core network part.

[0100] In this application, the user equipment, (radio) access network equipment, UPF network element, UDM network element, OAM network element, AMF network element, SMF network element, NEF network element, NRF network element, NWDAF network element, AF network element, PCF network element, and UDR network element are respectively abbreviated as UE, (R)AN, UPF, UDM, OAM, AMF, SMF, NEF, NRF, NWDAF, AF, PCF, and UDR.

[0101] The following will Figure 1 briefly describe each network element involved.

[0102] 1. UE

[0103] The UE in this application may also be referred to as a terminal, user, access terminal, user unit, user station, mobile station, mobile device, remote station, remote terminal, mobile equipment, user terminal, terminal device, wireless communication device, user agent, or user device, etc. For the sake of convenience of description, it will be uniformly referred to as a terminal hereinafter.

[0104] A terminal is a device that can access a network. The terminal and the (R)AN can communicate with each other using a certain radio access technology (such as NR or LTE technology). Terminals can also communicate with each other using a certain radio access technology (such as NR or LTE technology). A terminal can be a mobile phone, a tablet (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a terminal in satellite communication, a terminal in an integrated access and backhaul (IAB) system, a terminal in a WiFi communication system, a terminal in industrial control, a terminal in self-driving, a terminal in remote medical, a terminal in a smart grid, a terminal in transportation safety, a terminal in a smart city, a terminal in a smart home, etc.

[0105] The embodiments of this application do not limit the specific technologies and specific device forms adopted by the UE.

[0106] 2. (R)AN

[0107] The (R)AN in this application can be a device for communicating with a terminal, or a device for connecting a terminal to a wireless network.

[0108] (R)AN can be a node in a radio access network. (R)AN can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a Wi-Fi access point (AP), a mobile switching center, a next generation NodeB (gNB) in a 5G mobile communication system, a next generation NodeB in a sixth generation (6G) mobile communication system, or a base station in a future mobile communication system, etc. The network device can also be a module or unit that completes some functions of the base station. For example, it can be a central unit (CU), a distributed unit (DU), a remote radio unit (RRU), or a baseband unit (BBU), etc. (R)AN can also be a device that undertakes the base station function in a D2D communication system, a V2X communication system, an M2M communication system, and an IoT communication system, etc. (R)AN can also be a network device in NTN, that is, (R)AN can be deployed on a high-altitude platform or a satellite. (R)AN can be a macro base station, a micro base station or an indoor station, and can also be a relay node or a donor node, etc.

[0109] The embodiments of this application do not limit the specific technologies, device forms, and names adopted by (R)AN. For the convenience of description, (R)AN will be uniformly referred to as an access network device hereinafter.

[0110] 3. UPF

[0111] The main functions of UPF are to route and forward data packets, serve as a mobility anchor, an uplink classifier to support routing service flows to a data network, and a branching point to support multi-homed protocol data unit (PDU) sessions, etc.

[0112] 4. DN

[0113] DN is mainly used for the operator network that provides data services for terminals. For example, the Internet, a third-party service network, or an IP multimedia service (IMS) network, etc.

[0114] 5. UDM

[0115] The UDM is mainly responsible for the subscription data management of the terminal, including the storage and management of the terminal identifier, the access authorization of the terminal, etc.

[0116] 6. OAM

[0117] OAM is mainly used to complete the analysis, prediction, planning, and configuration of the network and its services, as well as the daily operation activities for the testing and fault management of the network and its services, etc.

[0118] 7. AMF

[0119] The main functions of the AMF include managing user registration, reachability detection, selection of the SMF node, management of mobile state transition, etc.

[0120] 8. SMF

[0121] The main function of the SMF is to control the establishment, modification, and deletion of the session, the selection of the user plane node, etc.

[0122]

[0123] The NEF is mainly used to externally provide the opening of the network capabilities and events, as well as receive relevant external information.

[0124]

[0125] The NRF is mainly used to provide the registration and discovery capabilities of network elements in the 5G network.

[0126] 11. NWDAF

[0127] The NWDAF is a network element that provides data analysis functions for the 5G core network (5GC) network functions (NF) and OAM. The 5GC NF or OAM can request network data analysis results from the NWDAF. After receiving the request, the NWDAF collects data from relevant network elements and trains an artificial intelligence (AI) model, and finally uses the AI model for data inference and feeds the inference results back to the corresponding 5GC NF or OAM.

[0128] The NWDAF has the functions of data collection, training, analysis, and inference. It can be used to collect relevant data from network elements, third-party service servers, terminal devices, or network management systems, perform analysis and training based on the relevant data, and provide data analysis results to network elements, third-party service servers, terminal devices, or network management systems. The analysis results can assist the network in selecting service quality parameters for services, or assist the network in performing traffic routing, or assist the network in selecting background data transmission strategies, etc.

[0129] According to different functions, NWDAF can be divided into NWDAF with machine learning training function (MTLF) that supports training (i.e., NWDAF(MTLF)) and NWDAF with analytics function (AnLF) that supports inference (i.e., NWDAF(AnLF)). NWDAF(AnLF) can request AI model information from NWDAF(MTLF) for data inference.

[0130] 12. AF

[0131] AF mainly supports transmitting the requirements of the application side to the network side. For example, quality of service (QoS) requirements or user status event subscriptions, etc. AF can be the AF deployed by the operator network itself or a third-party AF.

[0132] 13. PCF

[0133] PCF is mainly responsible for policy control decision-making, providing policy rules for control plane functions, and traffic-based charging control functions, etc.

[0134] 14. UDR

[0135] UDR is mainly responsible for providing the storage capacity of subscription data, policy data, and data related to capability open.

[0136] In Figure 1 In the architecture shown, N2 is the interface between AMF and RAN. N3 is the interface between RAN and UPF. N4 is the interface between SMF and UPF. N6 is the interface between UPF and DN. The service-based interfaces Nnef, Nnrf, Nnwdaf, Naf, Npcf, Nudr, Nudm, Namf, Nsmf are the service-based interfaces provided by the above-mentioned NEF, NRF, NWDAF, AF, PCF, UDR, UDM, AMF, SMF respectively, for invoking corresponding service-based operations. Among them, N2, N3, N4, and N6 are interface sequence numbers, and the meanings of these interface sequence numbers can be referred to the meanings defined in the standard protocol of the 3rd generation partnership project (3GPP), which are not restricted here.

[0137] It should be noted that in Figure 1 In the network architecture shown, the network elements can communicate through interfaces. The interfaces between the network elements can be point-to-point interfaces or service-based interfaces, which are not restricted in this application.

[0138] It should be understood that the network architecture shown above is only for illustrative purposes, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture that can implement the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0139] It should also be understood that Figure 1 The functions or network elements such as UPF, UDM, OAM, AMF, SMF, NEF, NRF, NWDAF, AF, PCF, or UDR shown in Figure 1 can be understood as network elements for implementing different functions. For example, they can be combined into network slices as needed. These network elements can be individual devices, or can be integrated into the same device to implement different functions, or can be network elements in hardware devices, or can be software functions running on dedicated hardware, or can be virtualized functions instantiated on a platform (such as a cloud platform). The present application does not limit the specific forms of the above-mentioned network elements.

[0140] It should also be understood that the above naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation to the present application. The present application does not exclude the possibility of using other names in 6G networks and future other networks. For example, in 6G networks, some or all of the above-mentioned network elements may continue to use the terms in 5G, or may use other names, etc.

[0141] To facilitate the understanding of the technical solution of the present application, the following combines Figure 2 to briefly introduce the scenario where the AMF sends a back-off timer to the UE.

[0142] Figure 2 is a schematic diagram of allocating a back-off timer provided by an embodiment of the present application.

[0143] Currently, the congestion control at the NAS layer is mainly achieved by allocating a back-off timer backoff-timer to the UE. When a large number of UEs simultaneously initiate registration request information to the AMF network element and the AMF is congested, the AMF will be unable to process the requests of these UEs. At this time, the AMF will allocate a back-off timer to each UE or each group of UEs, and carry the back-off timer in the registration rejection information and send it to the UE. When the UE receives the registration rejection information containing the back-off timer, the UE will start the timer locally. Before the timer times out, the UE will not initiate a registration request to the network again. Only after the timer times out will the UE initiate a registration request to the network again.

[0144] It should be understood that the registration request initiated by the UE to the AMF network element includes but is not limited to NAS requests, and the registration request information initiated by the UE to the AMF network element includes but is not limited to NAS request information. The present application does not make special limitations on this.

[0145] It should be understood that in some emergency or special situations, the UE may not perform backoff according to the time setting of the backoff timer, and may initiate a NAS request to the network again before the timer expires. This application does not make special restrictions on such special situations. Specifically, for example, including but not limited to when the UE is performing a deregistration process, high-priority access, emergency access, multimedia priority service (MPS), managed communication services (MCS), and / or message transfer (MT) services, the UE may initiate a NAS request to the network again before the timer expires.

[0146] Generally, the main application scenarios of the medium access control (MAC) message (MM) backoff timer include:

[0147] The first type: When the UE is in the radio measurement (RM) deregistered (RM-DEREGISTERED) state, the initial registration request initiated by the UE.

[0148] It should be understood that the initial registration request initiated by the UE does not carry a NAS congestion control exemption indication, and the request initiated by the UE is a non-emergency service request.

[0149] The second type: When the UE is in the RM-DEREGISTERED state and the UE is in the call manager (CM) connected (CM-Connected) state, the service request information and uplink NAS transport message initiated by the UE. Among them, the request types include but are not limited to: initial request, existing PDU session, mobile access (MA) PDU request, and / or modification request.

[0150] It should be understood that the above PDU session does not include an emergency PDU session.

[0151] The third type: When the UE is in the RM-DEREGISTERED state and the UE is in the call manager idle (CM-IDLE) state, the mobility registration update initiated by the UE.

[0152] When allocating the backoff timer, the factors that the AMF needs to consider include:

[0153] (1) Avoid a large number of UEs initiating delayed requests simultaneously or within a short period of time;

[0154] (2) The communication pattern of the UE.

[0155] As can be seen from the above, generally, when the AMF is congested, the AMF will send rejection information to the UE and carry a backoff timer in the rejection information to delay the access of the UE, so as to achieve control in the AMF congestion scenario. However, when the AMF allocates a backoff timer to the UE, only how to avoid a large number of UEs initiating delayed requests simultaneously and the communication pattern of the UE are considered, which will cause some terminal devices with weak timeliness for accessing the network to access the network in time, and the terminals with strong timeliness for accessing the network will be assigned a backoff timer with a relatively long time, thus resulting in a decline in the user experience. Therefore, how to allocate a reasonable backoff timer for different UEs is still a technical problem that those skilled in the art need to solve.

[0156] In the existing standards, there is no regulation on how the AMF allocates a reasonable backoff timer for the UE. The method provided in this application is used to assist the AMF in setting a reasonable backoff timer, so that when the AMF is congested, it can allocate appropriate backoff timers for different UEs, enabling the UEs to access the network in batches, achieving a relative balance between the urgency of the UEs to access the network and the congestion of the network, reasonably allocating network resources, and comprehensively improving the user experience.

[0157] As a non-limiting example, with the development of technology, more and more IoT terminals need to access the network, but the main purpose of these IoT terminals to access the network is to collect data in the network, and these IoT devices have a low demand for whether to access the network in time. In other words, the priority of these IoT terminals to access the network is relatively low. The priority information of different UEs can be set according to the types of UEs, enabling the UEs to access the network in batches.

[0158] Figure 3 It is a schematic diagram of the scenario to which this application is applied.

[0159] Configure a priority indication for each UE, and the UE carries this priority indication information in the registration request sent to the AMF. Each UE carries this priority indication information in each registration request and / or service request.

[0160] Based on the priority indication information carried in the received registration request message, the AMF allocates a reasonable backoff timer, backoffer-timer, for the UE, and carries this timer in the registration rejection message sent to the UE.

[0161] It should be understood that the priority indication information configured for the UE is used to indicate the priority of the UE accessing the network. When the AMF receives a registration request from the UE, it will make a judgment based on the current processing capacity of the AMF.

[0162] In an alternative implementation, when the AMF is not congested, the AMF makes a judgment based on the number of signaling messages it processes at the same time. When the number of signaling messages it processes at the same time is greater than or equal to the number of requests from the UE, the AMF ignores the priority indication information carried in the UE. When the number of signaling messages it processes at the same time is less than the number of requests from the UE, the AMF processes the requests initiated by the high-priority UEs first according to the priority indication information.

[0163] In another alternative implementation, when the AMF is congested, the AMF determines that it needs to send a registration rejection message to the UE that has received a NAS request. The reason for the rejection is that the AMF is congested, and a backoff timer is carried in the rejection message. The AMF allocates backoff timers of different durations for UEs with different priorities according to the priority indication information of the UEs.

[0164] In another alternative implementation, the AMF allocates a backoff timer with a shorter time for high-priority UEs and a backoff timer with a longer time for low-priority UEs, so that the UEs access the network in batches according to the priority order.

[0165] In some implementations, the priority indication information may also be referred to as priority indication, priority message, priority indication message, etc.; it should be understood that the above names refer to the same information, which is used to indicate the priority of the UE accessing the network. The above are only different names and do not constitute any limitation to the protection scope of this application.

[0166] In some implementations, the registration rejection message may also be referred to as rejection message, rejection notice, registration rejection notice, etc.; it should be understood that the above names refer to the same information, which is used to send a message to the UE to reject the UE's network access request. The above are only different names and do not constitute any limitation to the protection scope of this application.

[0167] Next, in combination with Figure 4 The steps for allocating a backoff timer for the UE will be described in detail.

[0168] Figure 4 is a schematic flowchart of a communication method provided by an embodiment of this application.

[0169] The communication method includes the following steps:

[0170] S409: The first network device receives first indication information sent by the terminal device, where the first indication information is used to indicate the priority of the terminal device.

[0171] In some specific implementation manners, the first network device includes an AMF network element.

[0172] In some optional implementation manners, the terminal device directly sends the first indication information to the first network device, where the first indication information is used to indicate the priority of the terminal device.

[0173] In some other optional implementation manners, the terminal device carries the first indication information in a request message and sends it. After receiving the request message, the first network device obtains the first indication information carried therein and determines the priority of the terminal device through the first indication information.

[0174] S410: The first network device generates first information according to the first indication information. The first information is used to configure a backoff timer for the terminal device.

[0175] It should be understood that in some specific implementation manners, the first indication information is used to indicate the priority of the terminal device, and the correspondence between the first indication information and the terminal device priority is stored in the first network device. The first network device obtains the priority of the terminal device according to the first indication information and then configures a reasonable backoff timer for the terminal device.

[0176] It should be understood that in some other specific implementation manners, the first indication information is used to indicate the priority of the terminal device, and the terminal device priority is directly included in the first indication information. The first network device can determine the priority of the terminal device according to the first indication information and configure a reasonable backoff timer for the terminal device.

[0177] S411: The first network device sends the first information to the terminal device.

[0178] In some optional implementation manners, the first network device allocates a backoff timer for the terminal device according to the priority of the terminal device. The backoff timer is carried in the first information and sent to the terminal device, and the terminal device configures its own backoff timer according to the first information.

[0179] In some other optional implementation manners, the first network device generates first information according to the priority of the terminal device and sends the first information to the terminal device. The terminal device configures its own backoff timer according to the first information.

[0180] Optionally, in another implementation manner, the communication method may further include the following steps:

[0181] S405: The first network device receives second information sent by the terminal device. The second information is used to instruct the first network device to execute the registration process of the terminal device.

[0182] It should be understood that the second information includes but is not limited to registration request information, NAS request information, network access request information, etc. sent by the terminal device.

[0183] S406: The first network device obtains the subscription information of the terminal device.

[0184] The first network device executes the registration process of the terminal device according to the second information, and obtains the subscription information of the terminal device from the UDM network element.

[0185] S407: The first network device generates first indication information.

[0186] The first network device obtains the priority of the terminal device according to the subscription information, and generates first indication information according to the priority of the terminal device.

[0187] S408: The first network device sends third information to the terminal device, and the third information carries the first indication information.

[0188] It should be understood that in some alternative implementation manners, the first network device directly sends the first indication information to the terminal device, and the first indication information is used to indicate the priority information of the terminal.

[0189] In some other alternative implementation manners, the first indication information is carried in the third information, and the first network device sends the third information to the terminal device.

[0190] In the above implementation manner, when the UE sends a message to the AMF for the first time, it does not carry the priority indication information. The priority indication information of the UE is assigned by the operator and stored in the UDM network element. After the UE accesses the network for the first time, it obtains its own priority indication information. When the UE accesses the network again, the request information sent to the AMF carries the priority indication information.

[0191] Optionally, in another implementation manner, the communication method may further include the following steps:

[0192] S401: The first network device receives fourth information sent by the terminal device. The fourth information carries second indication information, and the second indication information is used to indicate the initial priority of the terminal device.

[0193] It should be understood that the second indication information is used to indicate the initial priority of the terminal device. The second indication information may directly include the initial priority information of the terminal device, or may include an indication of the initial priority of the terminal device. This application does not make special limitations on this.

[0194] It should be understood that the initial priority includes the priority information built in when the UE leaves the factory; the initial priority may also include the priority information assigned to the UE when it last accessed the network.

[0195] It should be understood that the mapping relationship between the second indication information and the initial priority of the UE is stored in the first network device.

[0196] S407: The first network device generates first indication information.

[0197] The first network device determines the priority of the terminal device according to the second indication information, and generates first indication information according to the priority of the terminal device.

[0198] It should be understood that the first indication information is used to indicate the latest priority information of the UE, which is the priority indication information updated on the basis of the second indication information.

[0199] It should be understood that in different alternative implementation manners, the first network device generates first indication information according to different information, and the fields and contents included in these first indication information may be different or the same, and this application does not make special limitations on this. These first indication information are all used to indicate the priority of the terminal device.

[0200] S408: The first network device sends third information to the terminal device, and the third information carries the first indication information.

[0201] It should be understood that in different alternative implementation manners, the first network device sends third information to the network device according to different information, and the fields and contents included in these third information may be different or the same, and this application does not make special limitations on this. These third information are all used to carry the first indication information and are sent by the first network device to the terminal device.

[0202] In the above implementation manner, when the UE sends a message to the AMF for the first time, it carries the initial priority indication information. The first network device determines the latest priority information of the UE according to the initial priority information of the UE, and carries the updated priority information of the UE in the third information and sends it to the UE. When the UE accesses the network again, the information sent to the AMF carries the latest priority indication information. This method can prevent the UE from changing its own priority information in order to access the network preferentially, protect the security of the priority information, and ensure the rationality and fairness of the UE's network access priority.

[0203] In the above implementation manner, the priority information of the terminal device can also be uniformly allocated by the operator and stored in the UDM. The following steps may also be included:

[0204] S406: The first network device obtains the subscription information of the terminal device.

[0205] The first network device executes the registration process of the terminal device according to the fourth information and obtains the subscription information of the terminal device. The first network device obtains the priority of the terminal device according to the subscription information. The first network device obtains the first indication information according to the priority of the terminal device and / or the second indication information.

[0206] In the above implementation, even if the initial priority information of the UE is carried in the fourth information, in order to prevent the UE side from tampering with the priority information by itself, the AMF can obtain the subscription information of the terminal device from the UDM again and obtain the priority information of the UE assigned by the operator.

[0207] It should be understood that in different alternative implementations, the first indication information is determined by the type of the terminal device. The first network device determines the priority of the UE according to the type of the UE and generates the first indication information to indicate the priority of the UE.

[0208] Optionally, in another implementation, the communication method may further include the following steps:

[0209] S404: The first network device receives the fifth information from the second network device, and the fifth information is used to indicate the degree of dependence of the terminal device on the network.

[0210] In some specific implementations, the second network device includes an NWDAF network element.

[0211] S407: The first network device generates the first indication information.

[0212] The first network device determines the priority of the terminal device according to the fifth information and determines the first indication information according to the priority of the terminal device.

[0213] S408: The first network device sends the third information to the terminal device, and the third information carries the first indication information.

[0214] In the above implementation, the AMF obtains the degree of dependence of the UE on the network according to the fifth information sent by the NWDAF side, thereby judging the urgency of the UE to access the network to determine the priority of the UE, and generating the first indication information according to the priority of the UE. The first network device sends the priority indication information of the UE to the UE, and the UE carries the latest priority indication information when accessing the network next time. This method can reasonably judge the urgency of the UE to access the network based on the network communication behavior of the UE, which is beneficial for the AMF to more accurately allocate a reasonable backoff timer for the UE. It is beneficial to improve the overall satisfaction of users.

[0215] In the above implementation, the first network device may also subscribe to the network behavior information result of the UE from the second network device. It may further include the following steps:

[0216] S402: The first network device sends the sixth piece of information to the second network device. The sixth piece of information is used to subscribe to the analysis result based on the terminal device behavior information. The analysis result includes the fifth piece of information.

[0217] In the above implementation, the first network device subscribes to the behavior analysis result of the UE from the second network device, and the second network device sends the behavior result of the UE subscribed by the first network device to the first network device.

[0218] It should be understood that after receiving the analysis result of the UE's network behavior, the first network device determines the priority of the UE based on this result and generates the first indication information. The first network device can actively send the priority information based on the behavior analysis to the UE. The first network device can also carry the priority information based on the behavior analysis in the message replied to the UE when the UE accesses the network next time. This application does not make special limitations on this.

[0219] S403: The second network device analyzes the degree of dependence of the terminal device on the network.

[0220] Based on the UE information carried in the received sixth piece of information, the second network device subscribes to the network behavior information of the UE from other network devices, and analyzes the degree of dependence of the UE on the network based on the network behavior information of the UE fed back by other network devices.

[0221] It should be understood that other network devices include but are not limited to AMF network elements, SMF network elements, UPF network elements, UDM network elements, etc.

[0222] It should be understood that in the above optional implementation, different steps can be combined with each other to form optional implementations, which are not elaborated in this application. However, the new optional implementations formed by combining steps should not be considered to exceed the protection scope of this application.

[0223] Figure 5 It is a schematic flowchart of UE accessing the network in a congestion scenario provided by an embodiment of this application.

[0224] The UE accessing the network includes the following steps:

[0225] S501: The UE sends request message 1 to the AMF. Request message 1 is used to indicate the priority information of the UE.

[0226] In an optional implementation, request message 1 is the UE priority indication information (priorityindication), which is used to indicate the priority of the UE.

[0227] In another alternative implementation, the request message 1 includes the priority indication information (priorityindication) of the UE, that is, the request message 1 includes a field for indicating the UE priority.

[0228] It should be understood that step S501 is Figure 4 A specific implementation of step S409 in the described embodiment, and this application does not make special limitations on this.

[0229] It should be understood that the request message 1 is Figure 4 A specific implementation of the first indication information in the described embodiment, and this application does not make special limitations on this.

[0230] It should be understood that the AMF network element is Figure 4 A specific implementation of the first network device in the described embodiment, and this application does not make special limitations on this.

[0231] It should be understood that the request message 1 includes the UE registration request information or the service request information.

[0232] It should be understood that the priority indication information refers to the priority of the UE to access the network. This priority indication information can be uniformly formulated for all UE devices according to a certain rule, or can be uniformly allocated by the operator, and this application does not make special limitations on this.

[0233] In an alternative implementation, the priority indication information can be allocated to the UE according to the type of the UE. For example, according to different UE types in Table 1, the corresponding priority indication information is allocated.

[0234] Table 1 Corresponding relationship between different types of UEs and priority indication information

[0235] UE Type Priority Indication Information Smartphone Level1 Smartwatch Level2 Smart Camera Level3 Smart Water Meter Level4

[0236] It should be understood that the UE types listed in Table 1 are only exemplary examples, and the UEs applicable to the method protected by this application include but are not limited to the UE types listed in Table 1, and this application does not make special limitations on this.

[0237] It should be understood that the corresponding relationship between the UE types listed in Table 1 and the priority indication information is only an exemplary example and an alternative specific implementation provided by this application; in actual use or other scenarios, the priority indication information can be re-allocated for different types of UEs according to the actual scenario, and this application does not make special limitations on this.

[0238] It should be understood that in addition to the type of the UE, the priority indication information of different UEs can also be set according to factors such as the use of the UE or other reference information of the UE, and this application does not make special limitations on this.

[0239] It should be understood that when the AMF is congested, the AMF can set different back-off timers for the UE according to the priority indication information of the UE. The AMF can also preferentially process the indications initiated by high-priority UEs according to the priority indication information of the UE.

[0240] In another alternative implementation, the priority information of the UE is uniformly allocated by the operator; when allocating a subscriber identity module (SIM) card for the UE, the priority information of the UE is written in the SIM card.

[0241] S502: The AMF sets the back-off timer according to the priority indication information carried by the UE.

[0242] After the AMF receives the NAS request of the UE, when there is no high-priority request in the request, the AMF makes a judgment according to the current processing capacity.

[0243] It should be understood that step S502 is Figure 4 a specific implementation manner of step S410 in the described embodiment, and this application does not make special limitations on this.

[0244] It should be understood that high-priority requests include but are not limited to emergency requests, multimedia priority service (MPS) requests, or mission critical service (MCS) requests, etc.

[0245] It should be understood that the NAS request of the UE received by the AMF includes receiving the request information 1 sent by the UE, and the request information 1 is a specific manifestation form of the NAS request of the UE.

[0246] When the AMF is not congested, the AMF makes a judgment according to its own processing capacity. When the processing capacity of the AMF exceeds the current request quantity of the UE, the AMF ignores the priority indication information carried in the request information 1 and processes all the received request signaling of the UE. When the processing capacity of the AMF is lower than the current request quantity of the UE, the AMF can preferentially process the requests sent by UEs with higher priorities according to the priority indication information carried in the request information 1 sent by the UE.

[0247] In a possible implementation, the processing capacity of the AMF includes the number of signaling messages processed by the AMF at the same time. When the processing capacity of the AMF exceeds the number of requests of the current UE, the number of signaling messages processed by the AMF at the same time is greater than or equal to the number of requests of the UE. When the processing capacity of the AMF is lower than the number of requests of the current UE, the number of signaling messages processed by the AMF at the same time is less than the number of requests of the UE.

[0248] When the AMF is congested, the AMF determines that it needs to send a rejection message to the UE that has sent a NAS request, and the reason for the rejection is AMF congestion, and a back-off timer is carried in the rejection message. The AMF sets back-off timers with different durations for UEs with different priority levels according to the priority indication information of the UEs.

[0249] In an alternative implementation, the AMF sets a back-off timer with a relatively short time for UEs with a priority indication information of level 1, and sets a back-off timer with a relatively long time for UEs with a priority indication information of level 4.

[0250] S503: The AMF sends a rejection message 1 to the UE.

[0251] The AMF sends a rejection message 1 to the UE, and the rejection message 1 carries a back-off timer configured according to the priority indication information of the UE.

[0252] It should be understood that step S503 is Figure 4 a specific implementation of step S411 in the above-described embodiment, and the present application does not make any special limitation thereto.

[0253] It should be understood that the rejection message 1 is Figure 4 a specific implementation of the first information in the above-described embodiment, and the present application does not make any special limitation thereto.

[0254] In summary, when the AMF is congested in the network and receives the NAS request information of the UE, without obtaining the subscription information and context information of the UE, the AMF cannot set a reasonable back-off timer for the UE based on more information. In the existing implementation, the AMF randomly generates a back-off timer for the UE in a random manner. In some cases, this may cause the AMF to set a relatively short back-off timer for a UE with less urgent network requirements, and instead set a relatively long back-off timer for a UE with more urgent network requirements, resulting in unreasonable utilization of network resources and poor user experience.

[0255] By Figure 5In the method described above, the AMF can allocate a reasonable backoff timer for the UE according to the priority indication information carried in the UE request information, guide the UE to access the network in batches according to its own priority level, and relieve network congestion. This enables UEs with more urgent network requirements to enter the network as soon as possible, and for users with generally urgent network requirements to access the network during off-peak hours, so as to meet the timely network access requirements of high-priority UEs, achieve a balance in the network access of different types of UEs, keep the impact on user experience within a controllable range when the AMF is congested, and improve user satisfaction.

[0256] Figure 5 In the method described above, different priority indications are configured for the UE according to the type of the UE. The UE carries its own priority indication in the network access request message. When congested, the AMF sets different backoff timers for the UEs that need congestion control according to the priority indication information of the UEs.

[0257] Figure 6 It is a schematic flowchart of UE network access in another congestion scenario provided by an embodiment of the present application.

[0258] UE network access includes the following steps:

[0259] S601: The UE sends request information 2 to the AMF.

[0260] In an optional implementation manner, the request information 2 includes the UE's network access request information. When the UE accesses the network for the first time, it does not carry its own priority indication information in the request information 2.

[0261] It should be understood that step S601 is Figure 4 A specific implementation manner of step S405 in the embodiment described above. The present application does not make special limitations on this.

[0262] It should be understood that the request information 2 is Figure 4 A specific implementation manner of the second information in the embodiment described above. The present application does not make special limitations on this.

[0263] S602: The AMF obtains the subscription information of the terminal device from the UDM.

[0264] After receiving the request from the UE and finding that the request information does not carry the priority indication information in the request information 2, the AMF executes the normal registration process according to the request information 2 and obtains the subscription information of the UE from the UDM. The priority indication of the UE is stored in the subscription information of the UE, and the AMF obtains the subscription information of the UE from the UDM.

[0265] It should be understood that step S602 is Figure 4This is a specific implementation of step S406 in the embodiment, and this application does not make any special limitations on this.

[0266] S603: AMF generates priority indication information.

[0267] The AMF determines the priority of the UE based on the acquired subscription information of the UE, and generates corresponding priority indication information based on the priority of the UE.

[0268] It should be understood that step S603 is Figure 4 This is a specific implementation of step S407 in the embodiment, and this application does not make any special limitations on this.

[0269] It should be understood that the priority indication information is Figure 4 This application does not specifically limit a specific implementation method of the first indication information in the embodiment.

[0270] S604: AMF sends registration approval information 2 to the terminal device.

[0271] The AMF obtains the priority indication information of the UE from the subscription information of the UE, and carries the priority indication information in the registration pass information 2 and sends it to the UE.

[0272] It should be understood that step S604 is Figure 4 This is a specific implementation of step S408 in the embodiment, and this application does not make any special limitations on this.

[0273] It should be understood that the registration information 2 is Figure 4 This is a specific implementation method of the third information in the embodiment, and this application does not make any special limitations on this.

[0274] S605: The UE sends request information 3 to the AMF, where the request information 3 is used to indicate the priority information of the UE.

[0275] After the UE sends uplink signaling to the network device or the UE deregisters in the CM-IDLE state, when the UE initiates a registration request to the network again, the UE carries the latest priority indication information it has received in the request information 3.

[0276] In an optional implementation, the request information 3 is the priority indication information (priority indication) of the UE, which is used to indicate the priority of the UE.

[0277] In another optional implementation manner, the request information 3 includes priority indication information (priority indication) of the UE, that is, the request information 3 includes a field for indicating the priority of the UE.

[0278] It should be understood that step S605 is Figure 4 A specific implementation manner of step S409 in the described embodiment, and this application does not make special limitations thereto.

[0279] It should be understood that the request information 3 is Figure 4 A specific implementation manner of the first indication information in the described embodiment, and this application does not make special limitations thereto.

[0280] It should be understood that step S605 may be the same step as S501 or a different step, and this application does not make special limitations thereto.

[0281] It should be understood that the request information 3 in step S605 and the request information 1 in step S501 may be the same request information or different request information, and this application does not make special limitations thereto.

[0282] S606: The AMF sets a back-off timer according to the priority indication information carried by the UE.

[0283] It should be understood that step S606 is Figure 4 A specific implementation manner of step S410 in the described embodiment, and this application does not make special limitations thereto.

[0284] It should be understood that step S606 may be the same step as S502 or a different step, and this application does not make special limitations thereto.

[0285] It should be understood that the method of configuring the back-off timer in step S606 and the method of configuring the backoff-timer in step S502 may be the same configuration method or different configuration methods, and this application does not make special limitations thereto.

[0286] S607: The AMF sends rejection information 2 to the UE.

[0287] The AMF sends rejection information 2 to the UE, and the rejection information 2 carries a back-off timer configured according to the priority indication information of the UE.

[0288] It should be understood that step S607 is Figure 4 A specific implementation manner of step S411 in the described embodiment, and this application does not make special limitations thereto.

[0289] It should be understood that the rejection information 2 is Figure 4 A specific implementation manner of the first information in the described embodiment, and this application does not make special limitations thereto.

[0290] It should be understood that step S607 may be the same as step S503 or may be a different step, and the present application does not make special limitations on this.

[0291] It should be understood that the rejection information 2 in step S607 and the rejection information 1 in step S503 may be the same information field or may be different information fields, and the present application does not make special limitations on this.

[0292] Through Figure 6 According to the method described above, when the UE does not carry its own priority indication information during the first access to the network, the priority indication can be assigned by the operator and stored in the UDM network element. The AMF obtains the subscription information of the UE from the UDM network element. The AMF generates the priority indication information of the UE according to the priority information in the subscription information, and carries it to the UE in the registration approval information when the UE first accesses the network. The UE carries the priority indication information provided by the AMF in subsequent registration requests or service requests. When the AMF is congested, the AMF can set a reasonable backoff timer value for the UE according to the priority indication.

[0293] Figure 7 It is a schematic flowchart of another scenario where the UE accesses the network under congestion provided by the embodiments of the present application.

[0294] The UE accessing the network includes the following steps:

[0295] S701: The UE sends request information 4 to the AMF.

[0296] In an optional implementation manner, the request information 4 includes the UE's network access request information. When the UE accesses the network for the first time, it carries the initial priority indication information in the request information 4.

[0297] It should be understood that step S701 is Figure 4 A specific implementation manner of step S401 in the above-mentioned embodiment, and the present application does not make special limitations on this.

[0298] It should be understood that the request information 4 is Figure 4 A specific implementation manner of the fourth information in the above-mentioned embodiment, and the present application does not make special limitations on this.

[0299] It should be understood that the initial priority indication information is Figure 4 A specific implementation manner of the second indication information in the above-mentioned embodiment, and the present application does not make special limitations on this.

[0300] Optionally, the AMF can obtain the subscription information of the UE from the UDM according to the request information 4, and step S702 may also be included.

[0301] S702: The AMF obtains the subscription information of the terminal device from the UDM.

[0302] After the AMF network element receives the request information 4 of the UE, it can request the subscription information of the UE from the UDM network element during the registration process. If the subscription information of the UDM also stores the priority of the UE, the UDM will send the subscription information containing the priority indication to the AMF.

[0303] It should be understood that step S702 is Figure 4 a specific implementation manner of step S406 in the described embodiment, and this application does not make special limitations on this.

[0304] It should be understood that step S702 can be the same step as S602, or can be different steps, and this application does not make special limitations on this.

[0305] It should be understood that the subscription information obtained in step S702 and the subscription information obtained in step S602 can be the same information fields, or can be different information fields, and this application does not make special limitations on this.

[0306] S703: The AMF generates priority indication information.

[0307] The AMF determines the current priority of the UE according to the obtained subscription information of the UE or according to the initial priority indication information received from the UE, and generates corresponding priority indication information according to the priority of the UE.

[0308] In an optional implementation manner, the AMF network element generates the priority indication information inside the AMF according to the obtained priority of the UE. This priority indication information is used to indicate the priority of the UE, and the mapping relationship between this priority indication information and the UE priority is stored in the AMF network element.

[0309] It should be understood that the algorithm for the AMF network element to generate corresponding priority indication information according to the priority of the UE is built into the AMF network element. This algorithm can be regularly maintained and updated on the network side, and the updated algorithm is notified to all AMF network elements on the network side. The update algorithm can be completed by the NRF, UDR, or AMF network element on the network side, and this application does not make special limitations on this.

[0310] Regularly updating the algorithm can prevent the UE side from parsing its own priority and congestion level according to the priority indication information, prevent the UE side from tampering with its own priority, and maintain the security of the priority information.

[0311] It should be understood that step S703 is Figure 4 a specific implementation manner of step S407 in the described embodiment, and this application does not make special limitations on this.

[0312] It should be understood that the priority indication information is Figure 4 This application does not specifically limit a specific implementation method of the first indication information in the embodiment.

[0313] It should be understood that step S703 may be the same step as S603 or a different step, and this application does not make any special limitation on this.

[0314] It should be understood that the priority indication information generated in step S703 and the priority indication information generated in step S603 may be the same information field or different information fields, and the present application does not impose any special limitation on this.

[0315] S704: AMF sends registration approval information 3 to the terminal device.

[0316] The AMF obtains the priority indication information of the UE from the subscription information of the UE, and carries the priority indication information in the registration pass information 3 and sends it to the UE.

[0317] It should be understood that step S704 is Figure 4 This is a specific implementation of step S408 in the embodiment, and this application does not make any special limitations on this.

[0318] It should be understood that registration information 3 is Figure 4 This is a specific implementation method of the third information in the embodiment, and this application does not make any special limitations on this.

[0319] It should be understood that step S704 may be the same step as S604 or a different step, and this application does not make any special limitation on this.

[0320] It should be understood that the registration pass information 3 in step S704 and the registration pass information 2 in step S604 may be the same information field or different information fields, and this application does not make any special limitation on this.

[0321] S705: The UE sends request information 5 to the AMF, where the request information 5 is used to indicate the priority information of the UE.

[0322] After the UE sends uplink signaling to the network device or the UE deregisters in the CM-IDLE state, when the UE initiates a registration request to the network again, the UE carries the latest priority indication information it has received in the request information 5.

[0323] In an optional implementation, the request information 5 is the priority indication information (priority indication) of the UE, which is used to indicate the priority of the UE.

[0324] In another alternative implementation, the request message 5 includes the priority indication information (priorityindication) of the UE, that is, the request message 5 includes a field for indicating the UE priority.

[0325] It should be understood that step S705 is Figure 4 A specific implementation of step S409 in the described embodiment, and this application does not make special limitations on this.

[0326] It should be understood that the request message 5 is Figure 4 A specific implementation of the first indication information in the described embodiment, and this application does not make special limitations on this.

[0327] It should be understood that step S705 may be the same step as S501 and S605, or may be different steps, and this application does not make special limitations on this.

[0328] It should be understood that the request message 5 in step S705 and the request message 1 in step S501, or the request message 3 in step S605 may be the same request message or different request messages, and this application does not make special limitations on this.

[0329] S706: The AMF sets a back-off timer according to the priority indication information carried by the UE.

[0330] It should be understood that step S706 is Figure 4 A specific implementation of step S410 in the described embodiment, and this application does not make special limitations on this.

[0331] It should be understood that step S706 may be the same step as S502 and S606, or may be different steps, and this application does not make special limitations on this.

[0332] It should be understood that the method of configuring the back-off timer in step S706 and the method of configuring the back-off timer in step S502 or S606 may be the same configuration method or different configuration methods, and this application does not make special limitations on this.

[0333] S707: The AMF sends a rejection message 3 to the UE.

[0334] The AMF sends a rejection message 3 to the UE, and the rejection message 3 carries a back-off timer configured according to the priority indication information of the UE.

[0335] It should be understood that step S707 is Figure 4 A specific implementation of step S411 in the described embodiment, and this application does not make special limitations on this.

[0336] It should be understood that the rejection information 3 is Figure 4 a specific implementation of the first information in the described embodiment, and this application does not make special limitations thereon.

[0337] It should be understood that step S707 can be the same step as S503 or S607, or can be a different step, and this application does not make special limitations thereon.

[0338] It should be understood that the rejection information 3 in step S707 and the rejection information 1 in step S503 or the rejection information 2 in S607 can be the same information field or different information fields, and this application does not make special limitations thereon.

[0339] Through Figure 7 the described method, the AMF can generate the priority indication information of the UE according to the initial priority information carried in the UE request or the priority information obtained from the UDM, and send the priority indication information to the UE. The AMF side can identify the meaning represented by the priority indication information, which can effectively avoid the UE side tampering with its own priority information, protect the security of the priority information, and maintain the relative fairness of the network access environment.

[0340] Figure 8 It is a schematic flowchart of another scenario where the UE accesses the network in a congestion scenario provided by the embodiment of this application.

[0341] The UE accessing the network includes the following steps:

[0342] S801: The UE sends request information 6 to the AMF.

[0343] In an optional implementation, the request information 6 includes the network access request information of the UE. When the UE accesses the network for the first time, it does not carry its own priority indication information in the request information 6.

[0344] It should be understood that in this implementation, step S801 is Figure 4 a specific implementation of step S405 in the described embodiment, and this application does not make special limitations thereon.

[0345] It should be understood that in this implementation, the request information 6 is Figure 4 a specific implementation of the second information in the described embodiment, and this application does not make special limitations thereon.

[0346] It should be understood that in this implementation, step S801 can be the same step as S601 or can be a different step, and this application does not make special limitations thereon.

[0347] It should be understood that in this implementation manner, the request information 6 and the request information 2 may be the same information fields or different information fields, and the present application does not make special limitations on this.

[0348] In another alternative implementation manner, the request information 6 includes the access request information of the UE. When the UE accesses the network for the first time, the initial priority indication information is carried in the request information 6.

[0349] It should be understood that in this implementation manner, step S801 is Figure 4 A specific implementation manner of step S401 in the described embodiment, and the present application does not make special limitations on this.

[0350] It should be understood that in this implementation manner, the request information 6 is Figure 4 A specific implementation manner of the fourth information in the described embodiment, and the present application does not make special limitations on this.

[0351] It should be understood that in this implementation manner, step S801 may be the same step as S701 or a different step, and the present application does not make special limitations on this.

[0352] It should be understood that in this implementation manner, the request information 6 and the request information 4 may be the same information fields or different information fields, and the present application does not make special limitations on this.

[0353] S802: The AMF sends the registration approval information 4 to the terminal device.

[0354] In an alternative implementation manner, after the AMF interacts with other network elements and decides to accept the registration request of the UE, it sends the registration approval information 4 to the UE, and the registration approval information 4 does not carry the priority indication information of the UE.

[0355] It should be understood that in this implementation manner, other network elements include other network elements such as the UDM, and the interaction process between the AMF and other network elements may be Figure 4 A specific implementation manner of step S406 in the described embodiment, and the present application does not make special limitations on this and will not be elaborated further.

[0356] It should be understood that in this implementation manner, other network elements include other network elements such as the UDM, and the interaction process between the AMF and other network elements may be the same as steps S602 and S702 or different interaction steps, and the present application does not make special limitations on this and will not be elaborated further.

[0357] In another alternative implementation manner, after the AMF interacts with other network elements and decides to accept the registration request of the UE, it sends the registration approval information 4 to the UE, and the registration approval information 4 carries the priority indication information of the UE.

[0358] It should be understood that in this implementation manner, other network elements include other network elements such as UDM, and the interaction process between the AMF and other network elements and the process of generating the priority indication information may be Figure 4 A specific implementation manner of steps S406 and S407 in the above-described embodiment. This application does not make any special limitations on this and will not elaborate further.

[0359] It should be understood that in this implementation manner, other network elements include other network elements such as UDM, and the interaction process between the AMF and other network elements and the process of generating the priority indication information may be the same as steps S602, S603, and S702, S703, or may be different interaction steps. This application does not make any special limitations on this and will not elaborate further.

[0360] It should be understood that in this implementation manner, step S802 is Figure 4 A specific implementation manner of step S408 in the above-described embodiment. This application does not make any special limitations on this.

[0361] It should be understood that in this implementation manner, the registration success information 4 is Figure 4 A specific implementation manner of the third information in the above-described embodiment. This application does not make any special limitations on this.

[0362] It should be understood that in this implementation manner, step S802 may be the same as steps S604 and S704, or may be different steps. This application does not make any special limitations on this.

[0363] It should be understood that the registration success information 4 in step S802 and the registration success information 3 in step S704, or the registration success information 2 in step S604 may be the same information fields or different information fields. This application does not make any special limitations on this.

[0364] S803: The AMF network element sends subscription information 1 to the NWDAF network element.

[0365] The AMF network element sends subscription information 1 to the NWDAF network element for subscribing to the analysis of the UE's dependence on the network, and the analysis carries the AMF list (AMF list) of the target network element or the Area of Interest (AOI).

[0366] In an optional implementation manner, what the AMF provides is the AMF list, and the NWDAF provides the analysis results of all users on the AMF list. This AMF list may include this AMF network element or may not include this AMF network element.

[0367] In another optional implementation manner, what the AMF provides is the AOI, and the NWDAF needs to obtain the analysis results of all users within the AOI.

[0368] It should be understood that step S803 is Figure 4 a specific implementation manner of step S402 in the described embodiment, and this application does not make special limitations thereon.

[0369] It should be understood that subscription information 1 is Figure 4 a specific implementation manner of the fifth information in the described embodiment, and this application does not make special limitations thereon.

[0370] It should be understood that the NWDAF network element is Figure 4 a specific implementation manner of the second network device in the described embodiment, and this application does not make special limitations thereon.

[0371] In an optional implementation manner, the NWDAF obtains UE information by obtaining information from the AMF list or the AMF corresponding to the AOI. The information includes the registration request type of the UE, the behavior of the UE, and the periodic update time, unavailability period time, and priority indication information negotiated between the UE and the AMF.

[0372] It should be understood that Figure 8 For the two AMF network elements shown, one AMF refers to the AMF network element to which the terminal device is currently connected, that is, the AMF (consumer) network element shown in the figure, and the other AMF network element refers to the AMF network element of the network device. These two AMF network elements can be the same AMF network element or different AMF network elements, and this application does not make special limitations thereon.

[0373] In an optional implementation manner, the content that the NWDAF network element obtains UE information from other network elements may specifically include the following:

[0374] The UE behavior information 1 obtained by the NWDAF network element from the AMF network element includes:

[0375] (1) UE identifier (ID): According to different networks and protocols, the UE ID can take different forms, specifically including subscription concealment indication (SUCI), globally unique temporary identifier (GUTI), and subscription permanent identifier (SUPI), etc.

[0376] (2) Types of requests initiated by the UE to the AMF (request type): The UE request type is the type or reason for the request initiated by the UE to the AMF, which depends on the UE's state and network requirements. It mainly includes initial requests, mobility registration updates, periodic registration updates, emergency registrations, etc.

[0377] (3) UE's location (UE location).

[0378] (4) UE's access behavior trend (UE access behavior trend): It includes the UE's access, the UE's registration status, the UE's connection status, etc. Among them, the UE's registration management state (registration management state, RM state) includes states such as registration and deregistration. The UE's connection management state (connection management state, CM state) includes connected state, inactive state, handover, etc.

[0379] (5) Frequency of the UE initiating mobile registration updates (frequent mobility registration update).

[0380] (6) Time of the UE's periodic update (periodic update time) / Time when the UE is not in the network coverage area (unavailability period time).

[0381] (7) UE's priority indication information (priority indication).

[0382] UE behavior information 2 obtained by the NWDAF network element from the SMF network element includes:

[0383] The NWDAF network element obtains information about the PDU session of the UE from the SMF, including the Address Resolution Protocol (ARP) and the communication type. The specific communication types include Time Sensitive Networking (TSN), Time Sensitive Communications (TSC), Time Synchronization, and Deterministic Networking.

[0384] The specific information obtained by the UE from the SMF is as follows:

[0385] (1) Identification information of the UE: UE ID (SUPI).

[0386] (2) Information related to the PDU session of the UE (PDU session information):

[0387] · Request type of the PDU session initiated by the UE: normal service, emergency service, and always-on PDU session.

[0388] · Type of the current PDU session: QoS flow identifier (QFI) or 5G QoS indicator (5QI) information corresponding to the session, indicating the type of the current PDU session. For example, the current PDU session belongs to a session with guaranteed bit rate (such as voice) or a session without guaranteed bit rate (such as data).

[0389] · Type of the current communication (communication type): The current communication is applied to time sensitive networking (TSN), time sensitive communications (TSC), time synchronization, or deterministic networking, etc.

[0390] networking, TSN), time sensitive communications (TSC), time

[0391] synchronization), or deterministic networking, etc.

[0392] · ARP: The preemption level of the current PDU session, indicating whether it can preempt other PDU sessions when resources are scarce or be preempted by a PDU session with a higher priority.

[0393] (3) Inactivity detection time: The idle time of the PDU session. When the idle time of the PDU session exceeds this timer, the network actively releases the PDU session.

[0394] The UE behavior information 3 obtained by the NWDAF network element from the UPF network element includes:

[0395] The NWDAF collects traffic characteristic information on each PDU session of the UE from the UPF, including communication start / stop, uplink / downlink data rate, traffic volume, etc.

[0396] The specific information obtained by the UE from the UPF is as follows:

[0397] (1) UE identification information: UE ID (SUPI).

[0398] (2) Information related to the UE's PDU session (PDU session information):

[0399] · Request type of the PDU session initiated by the UE: normal service, emergency service, and always-on PDU session.

[0400] · Start / stop time of the PDU session, or the status of the PDU session (PDU session

[0401] status).

[0402] · Data volume of the PDU session (PDU session volume): PDU uplink / downlink data volume, communication start / stop status, PDU uplink / downlink data rate (PDU

[0403] volume), communication start / stop status, PDU uplink / downlink data rate (PDU

[0404] uplink / downlink data rate), traffic volume, etc.

[0405] The UE behavior information 4 obtained by the NWDAF network element from the UDM network element includes:

[0406] The NWDAF obtains the behavior information of the PDU session of the expected UE from the UDM, specifically including:

[0407] (1) Identification information of the UE (UE ID).

[0408] (2) Expected PDU session inactivity time.

[0409] (3) Expected UE behavior.

[0410] S804: The NWDAF analyzes the behavior information of the terminal device.

[0411] The NWDAF obtains an analysis of the UE's need for the network based on the collected information, and classifies the UE according to the UE's need for the network.

[0412] In an alternative implementation, the NWDAF classifies the UE according to the UE's need for the network. The method includes the following classifications:

[0413] (1) List of UEs with severe network demand: Includes UEs whose UE request type is emergency registration type, or requests not subject to NAS congestion control constraints, or high-priority requests, or the request type of the PDU session is emergency service.

[0414] (2) List of UEs with high network demand: Includes UEs and the request type of the PDU session is non-emergency or high-priority. For example, the PDU session established by the UE contains a type voice or video session (judged according to the QFI / 5QI of the obtained PDU session) or contains a data volume of the PDU session greater than a certain threshold, and the PDU session has been transmitting data during this event segment.

[0415] (3) List of moderately network-demanding UEs: It includes the UEs and the request type of the PDU session is non-emergency or high-priority. For example, the PDU session associated with the UE does not include a voice or video session type (judged according to the obtained QFI / 5QI of the PDU session), the data volume of the PDU session is within a certain threshold range, the data transmission is continuous, or it is irregular.

[0416] (4) List of lower network-demanding UEs: It includes the UEs and the request type of the PDU session is non-emergency or high-priority. For example, the data volume of all PDU sessions of the UE is less than a certain data volume threshold, and the data transmission is periodic, or all PDU sessions of the UE are in the deactive state.

[0417] (5) List of hardly network-demanding UEs: It includes that the UE is in the RM-deregistered or CM-Idle state during this period, or it is within the unavailability period time of the UE during this period.

[0418] It should be understood that step S804 is Figure 4 A specific implementation manner of step S403 in the described embodiment, and this application does not make special limitations on this.

[0419] S805: The NWDAF sends the behavior information 1 to the AMF network element.

[0420] The NWDAF sends the analysis result to the AMF, and the specific behavior information 1 is used to indicate the degree of dependence of the terminal device on the network.

[0421] In an optional implementation manner, the correspondence between the degree of dependence of the UE on the network and the priority is stored in the AMF network element, and the specific correspondence is shown in Table 2.

[0422] Table 2 Mapping relationship between the network behavior of the UE and the UE priority

[0423]

[0424]

[0425] It should be understood that step S805 is Figure 4 A specific implementation manner of step S404 in the described embodiment, and this application does not make special limitations on this.

[0426] It should be understood that the behavior information 1 is Figure 4 a specific implementation manner of the fifth information in the described embodiment, and this application does not make special limitations on this.

[0427] S806: The AMF generates priority indication information.

[0428] The AMF generates the priority indication information of the UE according to the collected priority of the UE and / or the information analyzing the degree of need of the UE for the network.

[0429] It should be understood that step S806 is Figure 4 a specific implementation manner of step S407 in the described embodiment, and this application does not make special limitations on this.

[0430] It should be understood that the priority indication information is Figure 4 a specific implementation manner of the first indication information in the described embodiment, and this application does not make special limitations on this.

[0431] It should be understood that step S806 may be the same step as S603 and S703, or may be different steps, and this application does not make special limitations on this.

[0432] It should be understood that the priority indication information generated in step S806 and the priority indication information generated in step S603 and / or step S703 may be the same information field or different information fields, and this application does not make special limitations on this.

[0433] Optionally, when the UE is in the connected state, the AMF may send the latest priority indication information to the UE, specifically including steps S807 and S808.

[0434] S807: The AMF network element sends configuration information 1 to the UE.

[0435] When the UE is in the connected state, the AMF sends configuration information 1 to the UE, and the configuration information 1 carries the updated priority indication information of the UE.

[0436] In an optional implementation manner, the configuration information 1 includes a configuration update command.

[0437] In an optional implementation manner, when there is already priority information of the UE in the AMF network element and it is different from the previously stored priority information of the UE, the configuration information 1 carries the updated priority indication information of the UE generated by the AMF according to the analysis of the NWDAF.

[0438] In another alternative implementation, the AMF network element does not have the priority information of the UE, and the configuration information 1 carries the priority indication information of the UE directly generated by the AMF based on the analysis of the NWDAF.

[0439] It should be understood that for the congestion control information maintained by the AMF, the AMF will generate the priority indication information for each or each group of UEs separately according to different times, different network states, etc. The priority indication information sent by the AMF to the UE is randomly generated each time it is updated, and the mapping relationship between the priority indication information and the priority of the UE is maintained by the AMF.

[0440] S808: The UE sends an acknowledgment message to the AMF.

[0441] After the UE receives the updated priority indication information sent by the AMF, it will send an acknowledgment message to the AMF network element to indicate that it has received the updated priority indication information.

[0442] S809: The UE sends request message 7 to the AMF, and request message 7 is used to indicate the priority information of the UE.

[0443] It should be understood that between step S808 and step S809, it may also include the step of the UE initiating registration, which is not elaborated in this application.

[0444] When the UE needs to re-initiate to the AMF after deregistration or when the UE needs to transmit an uplink signaling to initiate a registration request (service request) to the AMF, the UE carries the latest received priority information (priority indication) in request message 7.

[0445] In an alternative implementation, request message 7 is the priority indication information (priority indication) of the UE, which is used to indicate the priority of the UE.

[0446] In another alternative implementation, request message 7 includes the priority indication information (priority indication) of the UE, that is, request message 5 includes a field for indicating the priority of the UE.

[0447] It should be understood that step S809 is Figure 4 A specific implementation of step S409 in the described embodiment, and this application does not make special limitations on this.

[0448] It should be understood that request message 7 is Figure 4 A specific implementation of the first indication information in the described embodiment, and this application does not make special limitations on this.

[0449] It should be understood that step S809 may be the same as steps S501, S605, and S705, or may be different steps. This application does not make special limitations on this.

[0450] It should be understood that the request information 7 in step S809 and the request information 1 in step S501, the request information 3 in step S605, or the request information 5 in step S705 may be the same request information or different request information. This application does not make special limitations on this.

[0451] S810: The AMF sets a back-off timer according to the priority indication information carried by the UE.

[0452] When the AMF receives a NAS request from the UE and there is AMF congestion, for the same request type of a large number of UEs received by the AMF, it can determine which UEs are allowed to access the network according to the priority indication information of the UEs and the value of the back-off timer carried in the message rejecting the UE's access.

[0453] It should be understood that step S810 is Figure 4 A specific implementation manner of step S410 in the described embodiment. This application does not make special limitations on this.

[0454] It should be understood that step S810 may be the same as steps S502, S606, and S706, or may be different steps. This application does not make special limitations on this.

[0455] It should be understood that the method of configuring the back-off timer in step S810 and the method of configuring the back-off timer in step S502, S606, or S706 may be the same configuration method or different configuration methods. This application does not make special limitations on this.

[0456] S811: The AMF sends rejection information 4 to the UE.

[0457] The AMF sends rejection information 4 to the UE, and the rejection information 4 carries a back-off timer configured according to the priority indication information of the UE.

[0458] It should be understood that step S811 is Figure 4 A specific implementation manner of step S411 in the described embodiment. This application does not make special limitations on this.

[0459] It should be understood that the rejection information 4 is Figure 4 A specific implementation manner of the first information in the described embodiment. This application does not make special limitations on this.

[0460] It should be understood that step S811 may be the same as step S503, S607, or S707, or may be a different step, and the present application does not make special limitations on this.

[0461] It should be understood that the rejection information 4 in step S811 and the rejection information 1 in step S503, the rejection information 2 in S607, or the rejection information 3 in S707 may be the same information fields or different information fields, and the present application does not make special limitations on this.

[0462] Through Figure 8 With the method described above, the AMF can generate the priority indication information of the UE according to the analysis of the network dependence degree of the UE obtained by the NWDAF, and can more accurately judge the priority of the UE according to the network access habit of the UE, configure a more reasonable backoff timer for the UE, further improve the overall user experience, and more accurately reflect the actual situation of the UE's priority.

[0463] Figure 9 It is a schematic flowchart of another UE accessing the network in a congestion scenario provided by an embodiment of the present application.

[0464] Figure 9 In the implementation manner described above, in Figure 8 On the basis of the implementation manner described above, the methods executed by steps S901 - S906 and Figure 8 the steps S801 - S806 in the implementation manner described above are the same, and the present application will not elaborate herein.

[0465] Executed according to the above method, after the NWDAF network element generates the priority indication information for the UE, it no longer actively sends the priority indication information to the UE. Instead, when the UE sends a registration request to the AMF next time, it analyzes the priority indication information carried in the registration request information to determine whether the priority information of the UE has changed, and thus carries the updated priority information in the next message sent to the UE. Specifically, it further includes the following steps:

[0466] S907: The UE sends request information 8 to the AMF network element.

[0467] In an optional implementation manner, the request information 8 includes the network access request information of the UE. When the UE accesses the network for the first time, it does not carry its own priority indication information in the request information 8.

[0468] It should be understood that in this implementation manner, step S907 is Figure 4 a specific implementation manner of step S405 in the embodiment described above, and the present application does not make special limitations on this.

[0469] It should be understood that in this implementation manner, the request information 8 is Figure 4A specific implementation of the second information in the described embodiment is not specifically limited in this application.

[0470] It should be understood that in this implementation, step S907 may be the same step as S601 or S801, or may be a different step, which is not specifically limited in this application.

[0471] It should be understood that in this implementation, the request information 8 and the request information 2, and the request information 6 may be the same information fields, or may be different information fields, which is not specifically limited in this application.

[0472] In another alternative implementation, the request information 8 includes the network access request information of the UE. When the UE accesses the network for the first time, the initial priority indication information is carried in the request information 8.

[0473] It should be understood that in this implementation, step S907 is Figure 4 A specific implementation of step S401 in the described embodiment is not specifically limited in this application.

[0474] It should be understood that in this implementation, the request information 8 is Figure 4 A specific implementation of the fourth information in the described embodiment is not specifically limited in this application.

[0475] It should be understood that in this implementation, step S907 may be the same step as S701 or S801, or may be a different step, which is not specifically limited in this application.

[0476] It should be understood that in this implementation, the request information 8 and the request information 4, or the request information 6 may be the same information fields, or may be different information fields, which is not specifically limited in this application.

[0477] In an alternative implementation, at this time, the network of the AMF network element is in a non-congested state. Then the AMF network element sends confirmation information to the UE, specifically including step S908.

[0478] S908: The AMF sends confirmation information 2 to the UE.

[0479] The AMF network element generates the latest priority indication information of the UE according to the subscription information of the NWDAF in step S906. At this time, the AMF network element is in a non-congested state. The AMF network element determines whether the priority information is carried in the request information 8 according to the received request information 8, or determines whether the initial priority indication information of the UE carried in the request information 8 has changed. The AMF network element carries the updated priority indication information of the UE in the confirmation information 2 sent to the UE.

[0480] In another alternative implementation, when the network of the AMF network element is congested, the AMF network element sets a back-off timer for the UE and sends the back-off timer in the rejection message, which specifically includes step S909 and step S910.

[0481] S909: The AMF sets a back-off timer according to the priority indication information of the UE.

[0482] When the AMF receives a NAS request from the UE and there is AMF congestion, for the same request type of a large number of UEs received by the AMF, it can determine which UEs are allowed to access the network according to the priority indication information of the UE and the value of the back-off timer carried in the message rejecting the UE's access.

[0483] It should be understood that step S909 is Figure 4 A specific implementation manner of step S410 in the above-described embodiment, and this application does not make special limitations on this.

[0484] It should be understood that step S909 may be the same step as S502, S606, S706, or S810, or may be a different step, and this application does not make special limitations on this.

[0485] It should be understood that the method of configuring the back-off timer in step S909 and the method of configuring the back-off timer in steps S502, S606, S706, or S810 may be the same configuration method or different configuration methods, and this application does not make special limitations on this.

[0486] S910: The AMF sends a rejection message 5 to the UE.

[0487] The AMF sends a rejection message 5 to the UE, and the rejection message 5 carries a back-off timer configured according to the priority indication information of the UE.

[0488] It should be understood that step S910 is Figure 4 A specific implementation manner of step S411 in the above-described embodiment, and this application does not make special limitations on this.

[0489] It should be understood that the rejection message 5 is Figure 4 A specific implementation manner of the first information in the above-described embodiment, and this application does not make special limitations on this.

[0490] It should be understood that step S910 may be the same step as S503, S607, S707, or S811, or may be a different step, and this application does not make special limitations on this.

[0491] It should be understood that the rejection message 5 in step S910 and the rejection messages 1 in step S503, 2 in step S607, 3 in step S707, or 4 in step S811 may be the same information fields or different information fields, and the present application does not make special limitations on this.

[0492] By Figure 9 Through the method described above, the AMF network element does not need to actively notify the UE of the priority change after being analyzed by the NWDAF. Instead, when receiving the UE's request message next time, the UE's indication information is carried in the received confirmation message, and the UE's priority information can be updated to the UE without increasing the signaling overhead, which is conducive to the existing signaling to implement the notification of the update of the UE priority indication information.

[0493] It should be understood that the magnitudes of the sequence numbers of the above processes do not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0494] It should also be understood that in each embodiment of the present application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0495] It should also be understood that in some of the above embodiments, the devices in the existing network architecture are mainly used as examples for illustrative purposes. It should be understood that the specific forms of the devices are not limited in the embodiments of the present application. For example, devices that can achieve the same functions in the future are applicable to the embodiments of the present application.

[0496] It can be understood that in each of the above method embodiments, the methods and operations implemented by the devices (such as terminal devices, network devices) can also be implemented by components (such as chips or circuits) available for the devices.

[0497] It can also be understood that some optional features in each embodiment of the present application may not depend on other features in some scenarios, and may also be combined with other features in some scenarios, without limitation.

[0498] Above, in combination with Figures 4 to 9 The communication method provided by the embodiments of the present application has been described in detail above. The above communication method has been introduced mainly from the perspective of the interaction between the terminal device and the network device. It can be understood that for the terminal device and the network device to implement the above functions, they include the corresponding hardware structures and / or software modules for executing each function.

[0499] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can 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.

[0500] The following will describe in detail the communication device provided in the embodiments of this application in combination with Figures 10 to 12 It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, for the content not described in detail, reference can be made to the above method embodiments. For the sake of brevity, some content will not be repeated.

[0501] The embodiments of this application can divide the functional modules of the terminal device and the network device according to the above method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiments of this application is illustrative, only a logical function division, and there can be other division methods in actual implementation. The following will take the example of dividing each functional module corresponding to each function for illustration.

[0502] Figure 10 It is a schematic block diagram of a communication device 10 provided in the embodiments of this application. The device 10 includes a transceiver module 11 and a processing module 12.

[0503] Optionally, the device 10 may further include a storage module 13, and the storage module 13 can be used to store instructions and / or data. The processing module 12 can read the instructions and / or data in the storage module to enable the device to implement the actions of the device in the foregoing method embodiments.

[0504] In a possible design, the device 10 can correspond to the terminal device in the above method embodiment, or a component (such as a chip) of the terminal device.

[0505] Correspondingly, the device 10 can implement the steps or processes executed by the terminal device corresponding to the above method embodiment. Specifically, the transceiver module 11 can be used to perform the operations related to the transceiver of the terminal device in the above method embodiment, and the processing module 12 can be used to perform the operations related to the processing of the terminal device in the above method embodiment.

[0506] In a possible implementation, the transceiver module 11 is configured to send first indication information for indicating the priority of the terminal device, and is further configured to receive first information for configuring the backoff timer of the terminal device. The processing module 12 is configured to set its own backoff timer according to the first information, and after the timing ends, initiate an access request to the network device again.

[0507] When the apparatus 10 is configured to execute Figure 4 the method in

[0508] the transceiver module 11 may be configured to execute the steps of transmitting and receiving information in the method, such as steps S401, S405, S408, S409, and S411. Figure 5 When the apparatus 10 is configured to execute

[0509] the method in Figure 6 the transceiver module 11 may be configured to execute the steps of transmitting and receiving information in the method, such as steps S501 and S503.

[0510] When the apparatus 10 is configured to execute Figure 7 the method in

[0511] the transceiver module 11 may be configured to execute the steps of transmitting and receiving information in the method, such as steps S601, S604, S605, and S607. Figure 8 When the apparatus 10 is configured to execute

[0512] the method in Figure 9 the transceiver module 11 may be configured to execute the steps of transmitting and receiving information in the method, such as steps S701, S704, S705, and S707.

[0513] It should be understood that the specific processes of the respective units executing the corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they are not elaborated herein again.

[0514] In another possible design, the apparatus 10 may correspond to the first network device in the above method embodiment, that is, the AMF network element, or a component (such as a chip) of the AMF network element.

[0515] Correspondingly, the apparatus 10 may implement the steps or processes executed by the first network device in the above method embodiment.

[0516] In a possible implementation, a processing module 12 is configured to obtain the subscription information of a terminal device, generate priority indication information, and generate first information carrying a comparison timer. A transceiver module 11 is configured to receive the priority indication information and send the first information, which carries a backoff timer configured for the terminal device.

[0517] When the apparatus 10 is configured to execute Figure 4 the method in, the transceiver module 11 may be configured to execute the steps of sending and receiving information in the method, such as steps S401, S402, S404, S405, S408, S409, S411; and the processing module 12 may be configured to execute the processing steps in the method, such as steps S406, S407, S410.

[0518] When the apparatus 10 is configured to execute Figure 5 the method in, the transceiver module 11 may be configured to execute the steps of sending and receiving information in the method, such as steps S501, S503; and the processing module 12 may be configured to execute the processing steps in the method, such as step S502.

[0519] When the apparatus 10 is configured to execute Figure 6 the method in, the transceiver module 11 may be configured to execute the steps of sending and receiving information in the method, such as steps S601, S604, S605, S607; and the processing module 12 may be configured to execute the processing steps in the method, such as steps S602, S603, S606.

[0520] When the apparatus 10 is configured to execute Figure 7 the method in, the transceiver module 11 may be configured to execute the steps of sending and receiving information in the method, such as steps S701, S704, S705, S707; and the processing module 12 may be configured to execute the processing steps in the method, such as steps S702, S703, S706.

[0521] When the apparatus 10 is configured to execute Figure 8 the method in, the transceiver module 11 may be configured to execute the steps of sending and receiving information in the method, such as steps S801, S802, S803, S805, S807, S808, S809, S811; and the processing module 12 may be configured to execute the processing steps in the method, such as steps S806, S810.

[0522] When the apparatus 10 is configured to execute Figure 9 the method in, the transceiver module 11 may be configured to execute the steps of sending and receiving information in the method, such as steps S901, S902, S903, S905, S907, S908, S910; and the processing module 12 may be configured to execute the processing steps in the method, such as steps S906, S909.

[0523] It should be understood that the specific processes for each unit to execute the above corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they will not be repeated here.

[0524] In another possible design, the device 10 may correspond to the second network device in the above method embodiment, that is, the NWDAF network element, or a component (such as a chip) of the NWDAF network element.

[0525] Correspondingly, the device 10 can implement the steps or processes corresponding to those executed by the second network device in the above method embodiment.

[0526] In a possible implementation manner, the transceiver module 11 is configured to receive the sixth information and is further configured to send the fifth information; the processing module 12 is configured to analyze the degree of dependence of the terminal device on the network according to the behavior information of the terminal device.

[0527] When the device 10 is used to execute Figure 4 the method in, the transceiver module 11 can be used to execute the steps of receiving and sending information in the method, such as steps S402 and S404; the processing module 12 can be used to execute the processing steps in the method, such as step S403.

[0528] When the device 10 is used to execute Figure 8 the method in, the transceiver module 11 can be used to execute the steps of receiving and sending information in the method, such as steps S803 and S805; the processing module 12 can be used to execute the processing steps in the method, such as step S804.

[0529] When the device 10 is used to execute Figure 9 the method in, the transceiver module 11 can be used to execute the steps of receiving and sending information in the method, such as steps S903 and S905; the processing module 12 can be used to execute the processing steps in the method, such as step S904.

[0530] It should be understood that the specific processes for each unit to execute the above corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they will not be repeated here.

[0531] In another possible design, the device 10 may correspond to the UDM network element in the above method embodiment, or a component (such as a chip) of the UDM network element.

[0532] Correspondingly, the device 10 can implement the steps or processes corresponding to those executed by the UDM network element in the above method embodiment.

[0533] In a possible implementation manner, the transceiver module 11 is configured to receive the request information of the AMF network element; the processing module 12 retrieves the subscription information of the corresponding terminal device according to the request information.

[0534] When the device 10 is used to executeFigure 4 When the method in is executed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as step S406; the processing module 12 can be used to execute the processing steps in the method, such as step S406.

[0535] When the device 10 is used to execute Figure 6 When the method in is executed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as step S602; the processing module 12 can be used to execute the processing steps in the method, such as step S602.

[0536] When the device 10 is used to execute Figure 7 When the method in is executed, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as step S702; the processing module 12 can be used to execute the processing steps in the method, such as step S702.

[0537] It should be understood that the specific processes of each unit executing the corresponding steps above have been described in detail in the above method embodiments. For the sake of brevity, they will not be repeated here.

[0538] It should also be understood that the device 10 here is embodied in the form of functional modules. The term "module" here can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor or a group of processors, etc.) for executing one or more software or firmware programs, and a memory, a combined logic circuit and / or other suitable components that support the described functions. In an alternative example, those skilled in the art can understand that the device 10 can specifically be the core network device in the above embodiments, and can be used to execute each process and / or step corresponding to the core network device in the above method embodiments; or, the device 10 can specifically be the terminal device in the above embodiments, and can be used to execute each process and / or step corresponding to the terminal device in the above method embodiments; or, the device 10 can specifically be the access network device in the above embodiments, and can be used to execute each process and / or step corresponding to the access network device in the above method embodiments; to avoid repetition, they will not be repeated here.

[0539] The device 10 in each of the above solutions has the function of implementing the corresponding steps executed by the device in the above method. This function can be implemented by hardware or by hardware executing the corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver module can be replaced by a transceiver (for example, the sending unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as the processing module, etc., can be replaced by a processor, respectively executing the sending and receiving operations and related processing operations in each method embodiment.

[0540] In addition, the above transceiver module 11 may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing module may be a processing circuit.

[0541] Figure 11 It is a schematic diagram of another communication device 20 provided by an embodiment of the present application. The device 20 includes a processor 21, and the processor 21 is configured to execute a computer program or instruction stored in the memory 22, or read data / signaling stored in the memory 22, so as to execute the methods performed by the terminal device, access network device, or core network device in the above method embodiments.

[0542] Among them, the processor 21 may be one or more processors.

[0543] Such as Figure 11 shown, the device 20 may further include a memory 22, and the memory 22 is used to store computer programs or instructions and / or data. The memory 22 may be integrated with the processor 21, or may be separately provided. Among them, the memory 22 may be one or more memories.

[0544] Such as Figure 11 shown, the device 20 may further include a transceiver 23, and the transceiver 23 is used for receiving and / or transmitting signals. For example, the processor 21 is configured to control the transceiver 23 to receive and / or transmit signals.

[0545] Among them, the processor may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0546] Among them, the memory can be a volatile memory and / or a non-volatile memory. 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). For example, the RAM can be used as an external cache. By way of example and not limitation, the RAM includes the following various forms: 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).

[0547] It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, the memory (storage module) can be integrated in the processor.

[0548] Figure 12 It is a schematic diagram of a chip system 30 provided by an embodiment of the present application. The chip system 30 (or can also be referred to as a processing system) includes a logic circuit 31 and an input / output interface 32.

[0549] Among them, the logic circuit 31 can be a processing circuit in the chip system 30. The logic circuit 31 can be coupled to the storage unit and call the instructions in the storage unit, so that the chip system 30 can implement the methods and functions of the various embodiments of the present application. The input / output interface 32 can be an input / output circuit in the chip system 30, output the information processed by the chip system 30, or input the data or signaling information to be processed into the chip system 30 for processing.

[0550] As a solution, the chip system 30 is used to implement the operations performed by the terminal device or the network device in the above method embodiments.

[0551] For example, the logic circuit 31 is used to implement the operations related to the processing performed by the terminal device or the network device in the above method embodiments; the input / output interface 32 is used to implement the operations related to sending and / or receiving performed by the terminal device or the network device in the above method embodiments.

[0552] This application also provides a communication device, including a processor, which is coupled to a memory. The memory is used to store computer programs or instructions and / or data. The processor is used to execute the computer programs or instructions stored in the memory, or read the data stored in the memory, so as to execute the methods performed by the terminal device or the network device in the above method embodiments.

[0553] Optionally, the processor is one or more. The memory is one or more.

[0554] Optionally, the communication device includes a memory. Optionally, the memory is integrated with the processor or is separately provided.

[0555] This application provides a computer-readable storage medium, on which computer instructions are stored. When the computer instructions are executed, the methods performed by the terminal device or the network device in the above method embodiments are implemented.

[0556] This application provides a computer program product, including instructions. When the instructions are executed by a computer, the methods performed by the terminal device or the network device in the above method embodiments are implemented.

[0557] This application provides a communication system, which includes the terminal device and the network device in the above embodiments.

[0558] This application also provides a communication system, which includes at least one of the terminal device and the network device in the above embodiments.

[0559] For the explanations and beneficial effects of the relevant content in any of the above-mentioned devices, reference can be made to the corresponding method embodiments provided above, and details are not elaborated here.

[0560] It can be understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0561] The method steps in the embodiments of the present application may be implemented in a hardware manner or by a processor executing software instructions. The software instructions may be composed of corresponding software modules, and the software modules may be stored in a random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, removable hard disks, compact disc read-only memories (CD-ROMs), or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may be located in an ASIC. Additionally, the ASIC may be located in a core network device, an access network device, an access and mobility management function network element, a terminal, a session management function, or a multicast user plane function network element. Of course, the processor and the storage medium may also exist as discrete components in a core network device, an access network device, an access and mobility management function network element, a terminal, a session management function, or a multicast user plane function network element.

[0562] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable devices. The computer program or instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer program or instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired or wireless manner. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it can also be an optical medium, such as a digital video disc; or it can be a semiconductor medium, such as a solid-state drive.

[0563] In various embodiments of the present application, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be cross-referenced. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0564] It can be understood that the various numerical numbers involved in the embodiments of the present application are only for the convenience of description and do not limit the scope of the embodiments of the present application. The magnitude of the sequence numbers of the above processes does not mean the order of execution. The order of execution of each process should be determined by its function and inherent logic.

[0565] Unless otherwise specified, all technical and scientific terms used in the embodiments of the present application have the same meaning as commonly understood by those skilled in the technical field of the present application. The terms used in the present application are only for the purpose of describing specific embodiments and are not intended to limit the scope of the present application. It should be understood that the above is for illustrative purposes only. The above examples are only to help those skilled in the art understand the embodiments of the present application, rather than to limit the embodiments of the application to the specific numerical values or specific scenarios shown. Those skilled in the art can obviously make various equivalent modifications or changes based on the examples given above, and such modifications and changes also fall within the scope of the embodiments of the present application.

[0566] As described above, it is only the specific implementation manner 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 shall be subject to the protection scope of the claimed rights.

Claims

1. A communication method, characterized in that, it includes: receiving first indication information, where the first indication information is used to indicate the priority of the terminal device; generating first information according to the first indication information, where the first information is used to configure the backoff timer of the terminal device; sending the first information.

2. The method according to claim 1, characterized in that, it further includes: receiving second information, and performing the registration process of the terminal device according to the second information and obtaining the subscription information of the terminal device; obtaining the priority of the terminal device according to the subscription information, and generating the first indication information according to the priority of the terminal device; sending third information, where the third information carries the first indication information.

3. The method according to claim 1, characterized in that, it further includes: receiving fourth information, where the fourth information carries second indication information, and the second indication information is used to indicate the initial priority of the terminal device; determining the priority of the terminal device according to the second indication information, and generating the first indication information according to the priority of the terminal device; sending third information, where the third information carries the first indication information.

4. The method according to claim 3, characterized in that, it further includes: performing the registration process of the terminal device according to the fourth information and obtaining the subscription information of the terminal device; obtaining the priority of the terminal device according to the subscription information, and obtaining the first indication information according to the priority of the terminal device and / or the second indication information.

5. The method according to any one of claims 1 to 4, characterized in that, the first indication information is determined by the type of the terminal device.

6. The method according to claim 1 or 2, characterized in that, it further includes: receiving fifth information, where the fifth information is used to indicate the degree of dependence of the terminal device on the network; judging the priority of the terminal device according to the fifth information, determining the first indication information according to the priority of the terminal device, and sending third information, where the third information carries the first indication information.

7. The method according to claim 6, characterized in that, it further includes: sending sixth information, where the sixth information is used to subscribe to the analysis result based on the behavior information of the terminal device; the analysis result includes the fifth information.

8. A communication method, characterized in that, it includes: receiving sixth information, where the sixth information carries the information of the terminal device; obtaining the behavior information of the terminal device according to the sixth information, and analyzing the degree of dependence of the terminal device on the network according to the behavior information; sending fifth information, where the fifth information is used to indicate the degree of dependence of the terminal device on the network; the fifth information is further used to indicate that a first network device configures a backoff timer for the terminal device.

9. The method according to claim 8, characterized in that, the fifth information is further used to indicate that the first network device generates first indication information, and the first indication information is used to indicate the priority of the terminal device; The first network device generates first information according to the first indication information, and the first information is used to configure a backoff timer of the terminal device.

10. The method according to claim 8 or 9, wherein, the sixth information carries a device list or an area of interest of the terminal device.

11. The method according to any one of claims 9 to 10, wherein, the fifth information includes an analysis of the degree of dependence of the terminal device on the network in different time periods.

12. A communication method, wherein, comprises: sending first indication information for indicating the priority of a terminal device; the priority is used to indicate that a network device allocates a backoff timer for the terminal device; receiving first information and configuring the backoff timer of the terminal device according to the first information.

13. The method according to claim 12, wherein, further comprises: sending second information for indicating to execute a registration process of the terminal device and obtaining subscription information of the terminal device; the subscription information is used to indicate obtaining the priority of the terminal device; receiving third information, where the third information carries priority information of the terminal device; generating the first indication information according to the third information.

14. The method according to claim 12, wherein, further comprises: sending fourth information, where the fourth information carries second indication information for indicating an initial priority of the terminal device; receiving third information, where the third information carries updated priority information of the terminal device; generating the first indication information according to the third information.

15. The method according to claim 14, wherein, the fourth information is further used to indicate to execute a registration process of the terminal device and obtain subscription information of the terminal device; the subscription information is used to indicate obtaining updated priority information of the terminal device.

16. The method according to any one of claims 12 to 15, wherein, the first indication information is determined by the type of the terminal device.

17. The method according to claim 12 or 13, wherein, further comprises: receiving third information, where the third information carries the first indication information determined according to the degree of dependence of the terminal device on the network.

18. A communication device, wherein, comprises: a processor configured to execute a computer program stored in a memory, so that the device executes the method according to any one of claims 1 to 17.

19. The device according to claim 18, wherein, the device further comprises the memory.

20. A computer-readable storage medium, wherein, a computer program is stored on the computer-readable storage medium, and when the computer program runs on a computer, the computer is caused to execute the method according to any one of claims 1 to 17.

21. A computer program product, wherein, The computer program product includes instructions for performing the method according to any one of claims 1 to 17.

22. A communication system, characterized in that it includes: a first network device and a terminal device; the first network device is configured to perform the method according to any one of claims 1 to 7; the terminal device is configured to perform the method according to any one of claims 12 to 17.

23. The communication system according to claim 22, characterized in that it further includes a second network device; the second network device is configured to perform the method according to any one of claims 8 to 11.

Images