WO2023155618A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2023155618A1
WO2023155618A1 PCT/CN2022/144283 CN2022144283W WO2023155618A1 WO 2023155618 A1 WO2023155618 A1 WO 2023155618A1 CN 2022144283 W CN2022144283 W CN 2022144283W WO 2023155618 A1 WO2023155618 A1 WO 2023155618A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
network element
request
request information
management network
Prior art date
Application number
PCT/CN2022/144283
Other languages
English (en)
French (fr)
Inventor
杨樊
黄泽旭
何龙
陈阳
李帮丽
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023155618A1 publication Critical patent/WO2023155618A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints

Definitions

  • the present application relates to the technical field of communication, and in particular to a communication method and device.
  • the 4th generation mobile communication system Take the 4th generation mobile communication system (the 4th generation, 4G) system as an example.
  • the mobility management entity (MME) of different sites is in the form of an MME pool (pool) deploy.
  • the user signaling (such as a service request) of the failed MME will be connected to the normal MME in the pool by the evolved network base station (eNodeB).
  • eNodeB evolved network base station
  • Embodiments of the present application provide a communication method and device, which are used to adopt differentiated control modes for different signaling to reduce service impact on users.
  • a communication method is provided, which can be executed by a mobility management network element, or by other devices including mobility management network element functions, or by a chip system or other functional modules, and the chip system or functional modules can implement The function of the mobility management network element, for example, the chip system or functional module is set in the mobility management network element.
  • the mobility management network element is, for example, MME or AMF.
  • the method includes: receiving first request information from a terminal device, where the first request information is used to request a first service, or the first request information is attachment request information or registration request information of the terminal device; when the The first request information belongs to the first type of information, the original receiving network element of the first type of information is a faulty mobility management network element, and the first request information is processed according to the flow control policy for the first type of information deal with.
  • the mobility management network element can perform flow control on the first type of information, so after receiving the first request information, it can determine whether the first request information belongs to the first type of information, and if so, it can follow the first
  • the flow control policy corresponding to the class information processes the first request information.
  • the first type of information includes, for example, information that should be processed by the faulty mobility management network element. In this way, the impact on users who originally access the mobility management network element can be reduced, so that the services of these users can be guaranteed .
  • the original receiving network element indicated by the first information included in the first request information is different from the mobility management network element, it is determined that the first request information belongs to the first A class of information.
  • the original receiving network element of the first request information is the mobility management network element that should originally process the first request information.
  • the mobility management network element also configures first information locally, and the first information locally configured by the mobility management network element indicates the mobility management network element.
  • the mobility management network element indicated by the first information included in the first request information is different from the mobility management network element, it means that the mobility management network element that should originally process the first request information is not the mobility management network element, so the Indicates that the first request information belongs to the first type of information, and if the mobility management network element indicated by the first information included in the first request information is the same network element as the mobility management network element, it means that the mobile network element that should originally process the first request information
  • the management network element is the mobility management network element, so it indicates that the first requested information does not belong to the first type of information. In this way, the disaster recovery information can be distinguished more simply and clearly.
  • the first information includes MMEC, or includes AMF set ID information and an AMF pointer.
  • the first information may also be different, and the above is just an example and not specifically limited.
  • processing the first request information according to a flow control policy for the first type of information includes: If the amount of information belonging to the first type of information is less than a first threshold, sending first rejection information to the terminal device to reject the service requested by the first request information; or, if the information belonging to the first type of information The amount of information is greater than or equal to the first threshold, and the first request information is ignored.
  • the first request information is attachment request information or registration request information of the terminal device
  • the first information includes GUMMEI, or includes GUAMI.
  • the first request information is attachment request information or registration request information of the terminal device
  • the first request information is processed according to the flow control policy for the first type of information Processing, including: if the amount of information belonging to the first type of information is less than a second threshold, sending first response information to the terminal device, the first response information is first acceptance information, and the first acceptance information It is used to indicate the acceptance of the attachment request information or the acceptance of the registration request information, or, the first response information is used to indicate the refusal to process the first request information; or, if it belongs to the first type of information If the amount of information is greater than or equal to the second threshold, the first request information is ignored.
  • the first threshold may be used for flow control
  • the second threshold may be used for flow control.
  • differentiated flow control measures can be taken for different types of signaling, so that the flow control process is more in line with the characteristics of the corresponding signaling, so as to achieve better flow control effects.
  • the method further includes: if the amount of information belonging to the first type of information is less than a second threshold, sending first response information to the terminal device, including: if the information belonging to the first type The information quantity of one type of information is less than the second threshold and belongs to the first event, and the first response information is sent to the terminal device, where the first response information is used to indicate that processing of the first request information is refused. If the amount of information belonging to the first type of information is less than the second threshold, the mobility management network element may continue to determine whether it belongs to the first event, and if it belongs to the first event, it may indicate to the terminal device that it refuses to process the first request information.
  • the first event is used to determine the state of the user management network element, or to determine the processing capability of the user management network element. Through the first event, it can be determined whether the user management network element can process information related to the first request information, thereby reducing the User management network element pressure.
  • the first event includes: no response is received after sending the second request information to the user management network element, and the second request information is used to request to obtain the subscription data of the terminal device , or used to request to update the location information of the terminal device. If the mobility management network element does not receive a response after sending the second request information to the user management network element, it may indicate that the user management network element cannot process the second request information, for example, the user management network element may be congested. Therefore, the mobility management network element can reply a rejection to the terminal device.
  • the first event includes: after multiple pieces of third request information are sent to the user management network element, the third request information that has not received a response accounts for the multiple pieces of third request information
  • the ratio is greater than or equal to a third threshold, and the third request information is used for requesting to acquire the subscription data of the terminal device, or for requesting to update the location information of the terminal device.
  • the mobility management network element may have received multiple pieces of information for requesting attachment or registration from multiple UEs, and the mobility management network element may also have sent multiple pieces of third request information to the user management network element.
  • the mobility management network element may reply a rejection to the terminal device, so as to reduce the amount of information that the user management network element needs to process.
  • the first event includes: sending multiple pieces of fourth request information to the user management network element;
  • the proportion of the fourth request information is greater than or equal to the fourth threshold; the fourth request information is used to request to obtain the subscription data of the terminal device, or to request to update the location information of the terminal device.
  • the mobility management network element may have received multiple pieces of information for requesting attachment or registration from multiple UEs, and the mobility management network element may also have sent multiple pieces of fourth request information to the user management network element. If too much fourth request information is rejected, it may indicate that the user management network element is unable to process more information, so the mobility management network element may reply a rejection to the terminal device, so as to reduce the amount of information that the user management network element needs to process.
  • the first event includes: the amount of information for acquiring subscription data sent to the user management network element is greater than or equal to a fifth threshold.
  • the mobility management network element may have received multiple pieces of information for requesting attachment or registration from multiple UEs, and the mobility management network element may also have sent multiple pieces of information for obtaining subscription data to the user management network element. If the mobility management network element sends too much information for obtaining subscription data to the user management network element, the user management network element may already have a large processing pressure, so the mobility management network element can reply a rejection to the terminal device to reduce The amount of information that needs to be processed by the user management network element.
  • the first response information is used to indicate refusal to process the first request information
  • the first response information includes a first rejection reason value
  • the first rejection reason value is represented by to instruct the terminal device to continue trying to connect.
  • the probability of terminal equipment falling back to a low-standard network due to flow control or network congestion can be reduced, and the terminal equipment can be kept on the current network as much as possible to reduce the time for service recovery.
  • the value of the first rejection reason is, for example, #22, or it may also be other values.
  • the method further includes: if the amount of information belonging to the first type of information is less than a second threshold, obtaining the subscription data of the terminal device from a user management network element;
  • the device sending first response information includes: after obtaining the subscription data of the terminal device, sending the first response information to the terminal device, where the first response information is first acceptance information, and the first acceptance
  • the information is used to indicate the acceptance of the attach request information or the acceptance of the registration request information.
  • the second threshold is related to the performance of the user management network element.
  • the second threshold may be set according to the capability (or performance) of the user management network element, or in other words, the second threshold is related to the performance of the user management network element.
  • the second threshold By setting the second threshold, it can be ensured that the first type of information (such as information used to request attachment or registration to the core network) passed through the flow control of the mobility management network element can be successfully processed by the user management network element at the back end. Reduce the probability of user management network element congestion, improve network processing efficiency, and enable the service of terminal equipment to resume as soon as possible.
  • the first type of information such as information used to request attachment or registration to the core network
  • the user management network element is an HSS or a UDM.
  • the user management network element may be an HSS, and for a 5G system, the user management network element may be a UDM. If the method of the embodiment of this application is applied to other communication systems, the user management network element may have other implementations.
  • the first threshold is related to the second threshold, or in other words, the first threshold is set according to the second threshold.
  • the first threshold can be used for flow control for the first type of information used to request services
  • the second threshold can be used for flow control for the first type of information used for UE requesting attachment or registration.
  • the terminal device will then send the information used to request attachment or registration to the core network, that is, the information used to request services is the same as the information used to request services.
  • the information requested to attach or register to the core network is related.
  • the first threshold may be related to the second threshold, so as to ensure that the converted information for requesting attachment or registering to the core network is not ignored by the mobility management network element as much as possible. Ignored by the mobility management network element, reducing the waste of network resources.
  • the first type of information corresponds to a first type of service session, and the first type is a data type or a voice type. If the information requested by the terminal device to establish the first type of session is rejected, the terminal device may not fall back to the low-standard network, but will continue to try repeatedly on the current network; and if the information requested by the terminal device to establish other types of sessions is rejected If rejected, the end device may fall back to the low standard network.
  • the first type of information corresponds to the first type of service session, that is, the mobility management network element can perform flow control on the information used to request the first type of service session, even if the information is ignored due to flow control, the terminal device does not It will fall back to the low-standard network, which will not have much impact on the service recovery time of the terminal equipment. It can also reduce the probability of the terminal equipment falling back to the low-standard network and improve the service recovery efficiency of the terminal equipment.
  • processing the first request information according to a flow control policy for the first type of information includes: if the amount of information belonging to the first type of information is less than a sixth threshold, Sending first response information to the terminal device to indicate session establishment success or failure; or, if the number of information belonging to the first type of information is greater than or equal to a sixth threshold, ignoring the first request information.
  • the mobility management network element can use the sixth threshold to control the flow of the first type of information, which can effectively control the amount of information processed by the mobility management network element.
  • the mobility management network element may also use other methods to control the flow of the first type of information, which is not specifically limited.
  • a communication method which can be executed by a session management network element, or by other devices including the function of a session management network element, or by a chip system or other functional modules, and the chip system or functional modules can realize The function of the session management network element, for example, the chip system or the functional module is set in the session management network element.
  • the session management network element is, for example, an SGW or an SMF.
  • the method includes: receiving first request information from a terminal device, where the first request information is used to request establishment of a session; if the session requested by the first request information is a first type of session, the first Request information for flow control.
  • the first type is a data type or a voice type.
  • a communication method is provided, which can be executed by a mobility management network element, or by other devices including mobility management network element functions, or by a chip system or other functional modules, and the chip system or functional modules can implement The function of the mobility management network element, for example, the chip system or functional module is set in the mobility management network element.
  • the mobility management network element is, for example, MME or AMF.
  • the method includes: receiving first request information from a terminal device, where the first request information is attachment request information or registration request information of the terminal device; if it belongs to the first event, sending second rejection information to the terminal device , the second rejection information includes a first rejection reason value, where the first rejection reason value is used to instruct the terminal device to continue trying to connect on the current network.
  • the mobility management network element may consider the capacity of the user management network element. For example, the mobility management network element may determine whether the user management network element can process the first request information through the first event, and if the user management network element cannot currently process the first request information, the mobility management network element may refuse to process the first request information , to protect user management network elements. There may be many kinds of the first event, which is more flexible.
  • the first event includes: no response is received after sending the second request information to the user management network element, and the second request information is used to request to obtain the subscription data of the terminal device , or used to request to update the location information of the terminal device. If the mobility management network element does not receive a response after sending the second request information to the user management network element, it may indicate that the user management network element cannot process the second request information, for example, the user management network element may be congested. Therefore, the mobility management network element can reply a rejection to the terminal device.
  • the first event includes: after multiple pieces of third request information are sent to the user management network element, the third request information that has not received a response accounts for the multiple pieces of third request information
  • the ratio is greater than or equal to a third threshold, and the third request information is used for requesting to acquire the subscription data of the terminal device, or for requesting to update the location information of the terminal device.
  • the mobility management network element may have received multiple pieces of information for requesting attachment or registration from multiple UEs, and the mobility management network element may also have sent multiple pieces of third request information to the user management network element.
  • the mobility management network element may reply a rejection to the terminal device, so as to reduce the amount of information that the user management network element needs to process.
  • the first event includes: sending multiple pieces of fourth request information to the user management network element;
  • the proportion of the fourth request information is greater than or equal to the fourth threshold; the fourth request information is used to request to obtain the subscription data of the terminal device, or to request to update the location information of the terminal device.
  • the mobility management network element may have received multiple pieces of information for requesting attachment or registration from multiple UEs, and the mobility management network element may also have sent multiple pieces of fourth request information to the user management network element. If too much fourth request information is rejected, it may indicate that the user management network element is unable to process more information, so the mobility management network element may reply a rejection to the terminal device, so as to reduce the amount of information that the user management network element needs to process.
  • the first event includes: the amount of information for acquiring subscription data sent to the user management network element is greater than or equal to a fifth threshold.
  • the mobility management network element may have received multiple pieces of information for requesting attachment or registration from multiple UEs, and the mobility management network element may also have sent multiple pieces of information for obtaining subscription data to the user management network element. If the mobility management network element sends too much information for obtaining subscription data to the user management network element, the user management network element may already have a large processing pressure, so the mobility management network element can reply a rejection to the terminal device to reduce The amount of information that needs to be processed by the user management network element.
  • the method further includes: determining that the first request information belongs to the first type of information, the original receiving network element of the first type of information is a faulty mobility management network element, and the The above-mentioned first type of information is the object of flow control. For example, if the mobility management network element determines that the first request information belongs to the first type of information, it can determine whether it belongs to the first event, and if the first request information does not belong to the first type of information, the mobility management network element does not need to determine whether it meets The first event, but can directly process the first request message. In this way, it can be ensured that the information of the users originally accessing the mobility management network element can be processed as far as possible, and the service continuity of these users can be improved.
  • the second rejection information is sent to the terminal device, including: if the received attach request information or registration information of the UE that belongs to the first type of information The amount of information is less than the second threshold and belongs to the first event, and the second rejection information is sent to the terminal device.
  • the second threshold is related to the performance of the user management network element, and the user management network element is used to store the subscription data of the terminal device.
  • a fourth communication method is provided, and the method can be executed by a mobility management network element, or by other devices including mobility management network element functions, or by a chip system or other functional modules, and the chip system or functional modules can To realize the function of the mobility management network element, the chip system or the functional module is set in the mobility management network element, for example.
  • the mobility management network element is, for example, MME or AMF.
  • the method includes: receiving first request information from a terminal device, where the first request information is used to request a first service; if the received information for requesting a service is less than a first threshold, sending a message to the terminal device First rejection information, to reject the service requested by the first request information; receive second request information from the terminal device, where the second request information is attachment request information or registration request information of the terminal device; Determine whether to ignore the second request information according to the second threshold.
  • the method further includes: if the amount of received information for requesting services is greater than or equal to the first threshold, ignoring the first request information.
  • the method further includes: determining that the first request information belongs to the first type of information, the original receiving network element of the first type of information is a faulty mobility management network element, and the The above-mentioned first type of information is the object of flow control.
  • determining that the first request information belongs to the first type of information includes: if the original receiving network element indicated by the first information included in the first request information is not related to the mobility management The network elements are different, and it is determined that the first requested information belongs to the first type of information.
  • the first information includes MMEC, or, the first information includes an AMF set ID and an AMF pointer.
  • the method further includes: determining that the second request information belongs to the first type of information.
  • determining that the second request information belongs to the first type of information includes: if the original receiving network element indicated by the first information included in the second request information is not related to the mobility management The network elements are different, and it is determined that the second requested information belongs to the first type of information.
  • the second information includes GUMMEI, or includes MMEC; or, the second information includes GUAMI, or includes AMF set ID information and an AMF pointer.
  • the second threshold is related to the performance of the user management network element, and the user management network element is used to store the subscription data of the terminal device.
  • the first threshold is related to the second threshold.
  • determining whether to ignore the second request information according to the second threshold includes: if the number of received UE attachment request information or registration request information is less than the second threshold, not ignoring The second request information; or, if the number of received UE attachment request information or registration request information is greater than or equal to the second threshold, ignoring the second request information.
  • the method further includes: if the second request information is not ignored, sending first response information to the terminal device, where the first response information is first acceptance information, and the The first acceptance information is used to indicate the acceptance of the attachment request information or the acceptance of the registration request information; or, if the second request information is not ignored and the first event is satisfied, send the second Reject information.
  • the second rejection information includes a first rejection reason value
  • the first rejection reason value is used to instruct the terminal device to continue trying to connect on the current network.
  • the first event includes: no response is received after sending the second request information to the user management network element, and the second request information is used to request to obtain the subscription data of the terminal device , or used to request to update the location information of the terminal device. If the mobility management network element does not receive a response after sending the second request information to the user management network element, it may indicate that the user management network element cannot process the second request information, for example, the user management network element may be congested. Therefore, the mobility management network element can reply a rejection to the terminal device.
  • the first event includes: after multiple pieces of third request information are sent to the user management network element, the third request information that has not received a response accounts for the multiple pieces of third request information
  • the ratio is greater than or equal to a third threshold, and the third request information is used for requesting to acquire the subscription data of the terminal device, or for requesting to update the location information of the terminal device.
  • the mobility management network element may have received multiple pieces of information for requesting attachment or registration from multiple UEs, and the mobility management network element may also have sent multiple pieces of third request information to the user management network element.
  • the mobility management network element may reply a rejection to the terminal device, so as to reduce the amount of information that the user management network element needs to process.
  • the first event includes: sending multiple pieces of fourth request information to the user management network element;
  • the proportion of the fourth request information is greater than or equal to the fourth threshold; the fourth request information is used to request to obtain the subscription data of the terminal device, or to request to update the location information of the terminal device.
  • the mobility management network element may have received multiple pieces of information for requesting attachment or registration from multiple UEs, and the mobility management network element may also have sent multiple pieces of fourth request information to the user management network element. If too much fourth request information is rejected, it may indicate that the user management network element is unable to process more information, so the mobility management network element may reply a rejection to the terminal device, so as to reduce the amount of information that the user management network element needs to process.
  • the first event includes: the amount of information for acquiring subscription data sent to the user management network element is greater than or equal to a fifth threshold.
  • the mobility management network element may have received multiple pieces of information for requesting attachment or registration from multiple UEs, and the mobility management network element may also have sent multiple pieces of information for obtaining subscription data to the user management network element. If the mobility management network element sends too much information for obtaining subscription data to the user management network element, the user management network element may already have a large processing pressure, so the mobility management network element can reply a rejection to the terminal device to reduce The amount of information that needs to be processed by the user management network element.
  • a communication device may be the mobility management network element described in any one of the first aspect to the fourth aspect.
  • the communication device has the functions of the mobility management network element described above.
  • the communication device is, for example, a mobility management network element, or a functional module in the mobility management network element, such as a baseband device or a chip system.
  • the communication device includes a baseband device and a radio frequency device.
  • the communication device includes a processing unit (also called a processing module sometimes) and a transceiver unit (also called a transceiver module sometimes). The transceiver unit can realize the sending function and the receiving function.
  • the transceiver unit When the transceiver unit realizes the sending function, it can be called the sending unit (sometimes also called the sending module). When the transceiver unit realizes the receiving function, it can be called the receiving unit (sometimes also called receiving module).
  • the sending unit and the receiving unit can be the same functional module, which is called the transceiver unit, and this functional module can realize the sending function and the receiving function; or, the sending unit and the receiving unit can be different functional modules, and the transceiver unit is for these A general term for functional modules.
  • the transceiving unit is configured to receive first request information from a terminal device, where the first request information is used to request a first service, or is the attachment request information of the terminal device or registration request information; the processing unit is configured to, when the first request information belongs to the first type of information, process the first request information according to the flow control strategy for the first type of information, and the first type of information
  • the original receiving network element of a type of information is a faulty mobility management network element.
  • the transceiving unit is configured to receive first request information from a terminal device, where the first request information is attachment request information or registration request information of the terminal device; the transceiving The unit is further configured to send second rejection information to the terminal device if it belongs to the first event, the second rejection information includes a first rejection reason value, and the first rejection reason value is used to indicate that the terminal device is in the The current network continues to try to connect (or, the processing unit is configured to, if it belongs to the first event, send second rejection information to the terminal device through the transceiver unit, where the second rejection information includes a first rejection reason value, The first rejection reason value is used to instruct the terminal device to continue trying to connect on the current network).
  • the transceiving unit is configured to receive first request information from a terminal device, and the first request information is used to request a first service; the transceiving unit is also configured to The amount of received information for requesting services is less than a first threshold, sending first rejection information to the terminal device to reject the services requested by the first request information (or, the processing unit is configured to The amount of received information for requesting services is less than a first threshold, sending first rejection information to the terminal device through the transceiver unit to reject the services requested by the first request information); the transceiver unit, It is further configured to receive second request information from the terminal device, where the second request information is attachment request information or registration request information of the terminal device; the processing unit is configured to determine whether to ignore the the second request information.
  • the communication device further includes a storage unit (sometimes also referred to as a storage module), and the processing unit is used to be coupled with the storage unit and execute the program or An instruction to enable the communication device to execute the function of the mobility management network element described in any one of the first aspect to the fourth aspect.
  • a storage unit sometimes also referred to as a storage module
  • a communication device may be the session management network element described in any one of the first aspect to the fourth aspect.
  • the communication device has the function of the above-mentioned session management network element.
  • the communication device is, for example, a session management network element, or a functional module in the session management network element, such as a baseband device or a chip system.
  • the communication device includes a baseband device and a radio frequency device.
  • the communication device includes a processing unit (also called a processing module sometimes) and a transceiver unit (also called a transceiver module sometimes).
  • a processing unit also called a processing module sometimes
  • a transceiver unit also called a transceiver module sometimes
  • the transceiving unit is configured to receive first request information from a terminal device, and the first request information is used to request session establishment; the processing unit is configured to if the first The session requested by the request information is a session of the first type, and flow control is performed on the first request information.
  • the communication device further includes a storage unit (sometimes referred to as a storage module), and the processing unit is configured to be coupled with the storage unit and execute programs or An instruction to enable the communication device to perform the function of the access network device described in the first aspect and/or the second aspect.
  • a storage unit sometimes referred to as a storage module
  • the processing unit is configured to be coupled with the storage unit and execute programs or An instruction to enable the communication device to perform the function of the access network device described in the first aspect and/or the second aspect.
  • a seventh aspect provides a communication system, including the communication device described in the fifth aspect and the communication device described in the sixth aspect.
  • a computer-readable storage medium is provided.
  • the computer-readable storage medium is used to store a computer program or an instruction, and when it is executed, the mobility management network element or the session management network element in the above aspects executes the method is implemented.
  • a computer program product containing instructions, which, when run on a computer, enable the methods described in the above aspects to be implemented.
  • a chip system including a processor and an interface, and the processor is used to call and execute instructions from the interface, so that the chip system implements the methods in the above aspects.
  • FIG. 1A is a schematic structural diagram of a communication system provided by the present application.
  • FIG. 1B is a schematic diagram of an application scenario of an embodiment of the present application.
  • FIG. 2, FIG. 4 to FIG. 10 are flowcharts of several communication methods provided by the embodiments of the present application.
  • FIG. 3 is a schematic diagram of a threshold set in an embodiment of the present application.
  • Fig. 11 is a schematic diagram of a device provided in an embodiment of the present application.
  • Fig. 12 is a schematic diagram of another device provided by the embodiment of the present application.
  • the communication device for realizing the function of the network device may be a network device, or a device capable of supporting the network device to realize the function, such as a chip system, and the device may be installed in the network device.
  • the technical solution provided by the embodiment of the present application the technical solution provided by the embodiment of the present application is described by taking the network device as an example for realizing the function of the network device.
  • nouns for the number of nouns, unless otherwise specified, it means “singular noun or plural noun", that is, “one or more". “At least one” means one or more, and “plurality” means two or more. "And/or” describes the association relationship of associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist at the same time, and B exists alone, where A, B can be singular or plural. The character “/" generally indicates that the contextual objects are an "or” relationship. For example, A/B means: A or B. “At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • At least one item (piece) of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c Can be single or multiple.
  • first and second mentioned in this embodiment of the application are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority, or importance of multiple objects.
  • first request information and the second request information may be the same information or different information.
  • this name does not mean that the content, size, sending end and/or receiving end, sending time, priority or importance of the two pieces of information are different.
  • the numbering of the steps in the various embodiments introduced in this application is only for distinguishing different steps, and is not used to limit the order of the steps. For example, S201 may occur before S202, or may occur after S202, or may occur simultaneously with S202.
  • FIG. 1A shows the architecture of a possible communication system to which the communication method provided in the present application is applicable.
  • the architecture of the communication system may include: a radio access network, a terminal device, and a core network.
  • the wireless access network may include access network equipment.
  • the terminal device is a device with wireless transceiver function, which can be a fixed device, a mobile device, a handheld device (such as a mobile phone), a wearable device, a vehicle-mounted device, or a wireless device built into the above-mentioned devices (such as , communication module, modem, or chip system, etc.).
  • the terminal device is used to connect people, things, machines, etc., and can be widely used in various scenarios, including but not limited to the following scenarios: cellular communication, device-to-device communication (device-to-device, D2D), car-to-everything (vehicle to everything, V2X), machine-to-machine/machine-type communications (machine-to-machine/machine-type communications, M2M/MTC), Internet of things (Internet of things, IoT), virtual reality (virtual reality, VR) , augmented reality (augmented reality, AR), industrial control (industrial control), unmanned driving (self driving), telemedicine (remote medical), smart grid (smart grid), smart furniture, smart office, smart wear, smart transportation , Terminal equipment for smart cities, drones, robots and other scenarios.
  • cellular communication device-to-device communication
  • D2D device-to-device, D2D
  • car-to-everything vehicle to everything
  • V2X machine-to-machine/mach
  • the terminal equipment may sometimes be referred to as user equipment (user equipment, UE), terminal, access station, UE station, remote station, wireless communication device, or user device, etc.
  • user equipment user equipment
  • UE user equipment
  • access station UE station
  • remote station wireless communication device
  • wireless communication device or user device, etc.
  • the terminal device is taken as an example for description.
  • the access network device is a device with a wireless transceiver function, and is used for communicating with the terminal device.
  • the access network equipment includes but is not limited to a base station (base transceiver station (BTS), Node B, eNodeB/eNB, or gNodeB/gNB), a transmission reception point (TRP), a third generation 3rd generation partnership project (3GPP) subsequent evolution base station, wireless fidelity (wireless fidelity, Wi-Fi) system access node, wireless relay node, wireless backhaul node, etc.
  • the base station may be: a macro base station, a micro base station, a pico base station, a small station, a relay station, and the like.
  • a base station may contain one or more co-sited or non-co-sited transmission and reception points.
  • the access network device may also be a wireless controller, a centralized unit (centralized unit, CU), and/or a distributed unit (distributed unit, DU) in a cloud radio access network (cloud radio access network, CRAN) scenario.
  • the access network device in the vehicle to everything (V2X) technology may be a road side unit (RSU).
  • the base station is used as an example for the access network device to be described.
  • the base station can communicate with the terminal equipment, and can also communicate with the terminal equipment through the relay station.
  • a terminal device can communicate with multiple base stations in different access technologies.
  • the core network equipment may include a network exposure function (network exposure function, NEF) network element, a policy control function (policy control function, PCF) network element, a unified data management (unified data management, UDM), Application function (application function, AF) network element, access and mobility management function (access and mobility management function, AMF) network element, session management function (session management function, SMF) network element, user plane function (user plane function) , UPF) network elements, etc.
  • NEF network exposure function
  • policy control function policy control function
  • PCF policy control function
  • UDM unified data management
  • Application function application function, AF
  • access and mobility management function access and mobility management function
  • AMF session management function
  • SMF session management function
  • UPF user plane function
  • the access and mobility management functional network element can be used to manage the access control and mobility of the UE. In practical applications, it includes the mobility management entity (mobility management) in the network framework of long term evolution (LTE). entity, MME) in the mobility management function, and added the access management function, which can be responsible for UE registration, mobility management, tracking area update process, reachability detection, SMF network element selection, mobility state transition management wait.
  • MME mobility management entity
  • the access and mobility management function network element can be an AMF network element, as shown in Figure 1A; in future communication systems, such as a 6G system, the access and mobility management function network element can still be
  • the AMF network element may have other names, which are not limited in this embodiment of the present application.
  • the AMF network element can provide the Namf service.
  • the session management function network element can be used to be responsible for the session management of the terminal equipment (including the establishment, modification and release of the session, maintaining the tunnel between the user plane function network element and the access network device), the selection and reset of the user plane function network element Selection, UE's internet protocol (internet protocol, IP) address allocation (including optional authorization), configuration of traffic routing in user plane functional network elements, quality of service (quality of service, QoS) control, etc.
  • the session management function network element is the termination point of the session management part of the non-access stratum (non-access stratum, NAS) message.
  • the session management function network element can be an SMF network element, as shown in Figure 1A; in a future communication system, such as a 6G system, the session management function network element can still be an SMF network element, or there may be other
  • the session management function network element can provide the Nsmf service.
  • the user plane functional network element is responsible for forwarding and receiving user data of the UE.
  • the UPF network element can receive user data from the data network and send it to the UE through the access network device; the UPF network element can also receive user data from the UE through the access network device, and forward the received user data to the data network.
  • the user plane functional network element can be a UPF network element, as shown in Figure 1A; in a future communication system, such as a 6G system, the user plane functional network element can still be a UPF network element, or there may be other
  • the name of this application is not limited.
  • the unified data management function network element is used to generate authentication credentials, user identification processing (such as storing and managing user permanent identities, etc.), access authorization control, and contract data management.
  • the network element with the unified data management function can be a UDM network element, as shown in Figure 1A; in a future communication system, such as a 6G system, the network element with the unified data management function can still be a UDM network element, or may There are other names, which are not limited in the embodiment of this application.
  • the UDM network element can provide the Nudm service.
  • Data network refers to a service network that provides data transmission services for users, such as IP multimedia service (IP multi-media service, IMS), Internet (Internet), etc.
  • IP multimedia service IP multi-media service, IMS
  • Internet Internet
  • FIG. 1A also involves other network elements, which will not be introduced here.
  • the UE accesses the DN through a protocol data unit (protocol data unit, PDU) session established between the UE and the DN.
  • protocol data unit protocol data unit
  • each network element in the core network can also be called a functional entity or device, which can be a network element implemented on dedicated hardware, or a software instance running on dedicated hardware, or a virtualized network element on a suitable platform.
  • An example of the function, for example, the above-mentioned virtualization platform may be a cloud platform.
  • the AMF network element and the access network device can be connected through the N2 interface
  • the access network device and the UPF network element can be connected through the N3 interface
  • the SMF network element and the UPF network element can be connected through the N4 interface
  • the AMF The network element and the UE can be connected through the N1 interface
  • the UPF and the DN can be connected through the N6 interface.
  • the name of the interface is just an example, which is not specifically limited in this embodiment of the present application. It should be understood that the embodiment of the present application is not limited to the communication system shown in FIG. 1A, and the name of the network element shown in FIG. 1A is only used as an example here, and does not serve as a communication system architecture applicable to the method of the embodiment of the present application. Restrictions on the network elements included in . The functions of some network elements or devices in the communication system are introduced below. The names of devices implementing core network functions in systems with different access technologies may be different, which is not limited in this embodiment of the present application.
  • the communication system shown in FIG. 1A does not constitute a limitation to the applicable communication system of the embodiment of the present application.
  • the communication system architecture shown in Figure 1A is a 5G system architecture.
  • the technical solution provided by the embodiment of the present application can be applied to the fourth generation mobile communication technology (the 4th generation, 4G) in addition to the 5G system.
  • the 4th generation 4G
  • an LTE system or may also be applied to a next-generation mobile communication system or other similar communication systems, which are not specifically limited.
  • FIG. 1A the architecture of the communication system shown in FIG. 1A is not limited to include only the network elements shown in the figure, and may also include other devices not shown in the figure, which will not be listed here in detail.
  • the embodiments of the present application will be described by taking the network element shown in Figure 1A as an example, and the XX network element will be directly referred to as XX, for example, the SMF network element will be referred to as SMF, and the AMF network element will be referred to as AMF wait.
  • XX the SMF network element
  • AMF AMF wait.
  • the names of all network elements in the embodiments of the present application are only examples, and may be called other names in future communications, or the network elements involved in the embodiments of the present application may also be referred to by other entities with the same function in future communications Or equipment, etc., which are not limited in this embodiment of the present application. A unified explanation is made here, and no further details will be given later.
  • FIG. 1B is a schematic diagram of an application scenario of an embodiment of the present application.
  • Figure 1B takes two sites as an example, and actual deployment may include multiple sites.
  • the MME/AMF can be deployed in the form of a pool
  • the gateway/SMF can also be deployed in the form of a pool.
  • the gateways/SMFs of different sites can also be deployed in the form of a pool.
  • internet protocol multimedia subsystems IMS
  • IMS internet protocol multimedia subsystem
  • UE1-UE4 in Figure 1B all access site 1, and when site 1 fails, the radio access network (radio access network, RAN) sends the MME of site 1 to the MME/AMF of site 2 /AMF user signaling.
  • the user signaling on the gateway/SMF of site 1 will also be accessed by the RAN to the gateway/SMF of site 2, and the signaling of UE1-UE4 will be accessed by the gateway/SMF of site 2.
  • relay equipment may be used between IMS and HSS/UDM, relay equipment may be used between SGW/PGW/SMF and HSS/UDM, and relay equipment may be used between MME/AMF and HSS/UDM
  • the relay devices are used for relaying, and the three relay devices may be the same relay device or different relay devices, and the relay devices are not shown in FIG. 1B .
  • the mobility management network element or mobility management network element 2 involved in each embodiment of the present application is is the MME or AMF of station 2 in Figure 1B
  • the mobility management network element 1 involved in various embodiments of the present application is the MME or AMF of station 1 in Figure 1B
  • the user management network element involved in various embodiments of the present application It is the HSS or UDM of site 2 in Figure 1B
  • the session management network element involved in each embodiment of the present application is the gateway or SMF of site 2 in Figure 1B
  • the access network involved in each embodiment of the present application The network element is the RAN in Figure 1B.
  • some or all of the embodiments of this application may involve the concept of "low-standard” network, which is uniformly explained here: if the UE is currently camped on a 4G network, then if the UE falls back to a low-standard network, the low-standard network It may refer to a 3G network or a 2G network; correspondingly, a "high standard” network corresponding to a 2G network or a 3G network as a low standard network may be a 4G network.
  • the low-standard network may refer to a 4G network; correspondingly, the "high-standard” network corresponding to the 4G network as a low-standard network, It could be a 5G network.
  • Figure 2 is a schematic diagram of a communication method provided by the embodiment of the present application. It should be noted that the mobile management network element 1 in the figure is a faulty network element, and the symbol " ⁇ " represents a fault or malfunction Work. The method may include the steps of:
  • the UE sends first request information.
  • the UE sends the first request information to the mobility management network element 2 through an access network element.
  • the mobility management network element accessed by the UE is the mobility management network element 1, but the mobility management network element 1 fails. If the access network element determines that mobility management NE 1 is faulty, the access network element can reselect a normal mobility management NE from the mobility management NE pool. For example, if mobility management NE 2 is selected, the access network The network element may send the first request information to the normal working mobility management network element 2 .
  • the transmission of heartbeat packets can be maintained between the access network element and the mobility management network element, and the access network element can determine the mobility management network element 1 through the abnormality of the heartbeat packet between the access network element and the mobility management network element 1. Fault.
  • the first request information is used to request a service, and the service requested by the first request information is called the first service.
  • the first request information is service request.
  • the first request information may be used for the UE to request attachment (or understood that the first request information is the UE's attachment request information), for example, the first request information is used for the UE to request to attach (attach) to the mobility management network element 2 , for example, the first request information is an attach request (attach request).
  • the first request information may be used for the UE to request registration (registration), or it may be understood that the first request information is the registration request information of the UE, for example, the first request information is used for the UE to request registration to the mobility management network element 2,
  • the first request information is a registration request (registration request).
  • the first request information may be used to request to establish a session (or be understood as, the first request information is the session establishment request information of the UE), for example, the first request information is used to request to establish a public data network (public data network, PDN) connection , or used to request the establishment of a protocol data unit (protocol data unit, PDU) session.
  • the embodiment of the present application is applied to a 4G system, and the first request information is, for example, used to request the establishment of a voice PDN connection or a data PDN connection; for another example, the embodiment of the present application is applied to a 5G system, and the first request information is, for example, used to request the establishment of a data PDU Session or Voice PDU Session.
  • the mobility management network element 2 determines that the first requested information belongs to the first type of information.
  • the first type of information may be disaster recovery information.
  • the first type of information is information that should be processed by other mobility management network elements except the mobility management network element 2, or in other words, the original receiving network element of the first type of information is not the mobility management network element 2.
  • the original receiving network element of the first type of information is the faulty mobility management network element. If a mobility management network element is broken, or a mobility management network element is overloaded due to capacity limitation, it can be regarded as a failure of the mobility management network element.
  • the receiving network element of the first type of information does not refer to the access network element as a transit network element, but refers to the source network element to which the first type of information is originally planned to be sent and receives the first type of information. Mobility management network element. Therefore, in the embodiment of the present application, the original receiving network element of the first type of information is a faulty mobility management network element.
  • the mobility management network element 2 may determine that the first information included in the first request information indicates The mobility management network element of , and the mobility management network element 2 are not the same network element.
  • the mobility management network element indicated by the first information is the original receiving network element of the first request information.
  • the first information may include an MME code (MME code, MMEC), or the first information may include an AMF set ID (AMF set ID) and an AMF pointer (AMF pointer).
  • the first information may include a globally unique MME identity (globally unique MME identity, GUMMEI) or MMEC; or, the first information includes a globally unique AMF identity (globally unique AMF identifier, GUAMI ), or include AMF set ID and AMF pointer.
  • GUMMEI globally unique MME identity
  • MMEC globally unique MME identity
  • AMF identity global unique AMF identifier
  • the mobility management network element 2 may determine that the mobility management network element indicated by the information corresponding to the first request information is not the same as the mobility management network element 2 A network element, and the session corresponding to the first request information is a session of the first type.
  • the first type of information corresponds to the first type of service session.
  • the service session is referred to as a session for short in the following.
  • a correspondence manner between the first type of information and the first type of session is that the first type of information is information for requesting establishment of the first type of session.
  • the embodiment of the present application is applied to a 4G system, and the first request information is, for example, used to request establishment of a voice PDN connection, that is, the first type is a voice type.
  • the embodiment of the present application is applied to a 5G system, and the first request information is, for example, used to request establishment of a data PDU session, that is, the first type is a data type.
  • the information corresponding to the first request information is, for example, the information received by the mobility management network element 2 from the sender of the first request information before receiving the first request information.
  • the information corresponding to the first request information includes information for requesting a service, and/or includes information for requesting attachment or registration to the core network.
  • the information used to request a service is, for example, a service request; the information used to request attachment or registration to the core network is, for example, an attach request or a registration request.
  • the mobility management network element 2 first receives the information corresponding to the first request information from the UE, and the mobility management network element 2 may determine the mobility management network element indicated by the information corresponding to the first request information (the determination method may be Refer to the foregoing), and the mobility management network element indicated by the information corresponding to the first request information can be regarded as the mobility management network element corresponding to the first request information. Therefore, the mobility management network element 2 can determine whether the first request information belongs to the first type of information according to the mobility management network element indicated by the information corresponding to the first request information and according to the session type corresponding to the first request information.
  • the mobility management network element 2 processes the first request information according to the traffic control policy for the first type of information.
  • the mobility management network element 2 can perform flow control on the first type of information, that is, the first type of information is an object of flow control. Therefore, if the first request information belongs to the first type of information, S203 may be executed.
  • the first type of information is disaster recovery information
  • the mobility management network element 2 controls the flow of the first type of information to reduce service impact on users who originally access the mobility management network element 2 .
  • the mobility management network element 2 may set a threshold A, through which flow control is performed on the first type of information used to request services. For example, the first request information is used to request a service, then, if the quantity of the first type of information (or the first type of information used to request the service) received by the mobility management network element 2 is less than the threshold A, the mobility management network element 2 may process the first request information, or in other words, the mobility management network element 2 does not ignore the first request information. For example, the mobility management network element 2 processes the first request information by querying the context of the UE corresponding to the request information A (that is, the UE sending the request information A), so as to determine the processing method for the request information A.
  • MME2 may send first rejection information to the UE, so as to reject the service requested by the first request information.
  • ignoring can also be understood as discarding, or not processing, which is not limited in this application.
  • the amount of this type of information is, for example, the type of information received by the mobility management network element 2 from the start of the flow control policy The number of , or the number of this type of information received by the mobility management network element 2 since it starts up (or starts to work).
  • the mobility management network element 2 wants to compare the quantity of the received first-type information with the threshold A, then the quantity of the first-type information participating in the comparison is, for example, the amount received by the mobility management network element 2 from the start of the traffic control strategy The quantity of the first type of information, or the quantity of the first type of information received by the mobility management network element 2 since it is started.
  • the quantity of a certain type of information used for comparison with a certain threshold may be counted in a specific period, and the embodiment of the present application does not limit the length of the period and the start time of the period. .
  • the quantity of a certain type of information used for comparison with a certain threshold can be counted within a specific time period.
  • the embodiment of this application is not limited. In the following, similar features will not be described in detail.
  • the mobility management network element 2 can ignore the first request information, that is , MME2 will not process the request information A, and will not send a response related to the request information A to the UE.
  • the first request information as a service request as an example, regardless of whether it is a 4G system or a 5G system, if the UE does not receive a response after sending the service request, the UE can resend the service request every 5 seconds (second, s). If no response is received after resending 4 times, the UE will resend every 60 seconds.
  • the mobility management network element 2 performs flow control on the first type of information used to request services, and the threshold involved in the flow control strategy may not use the quantity threshold (for example, threshold A), but use the rate threshold.
  • the mobility management network element 2 compares the received rate of the first type of information (or the first type of information used to request the service) with the threshold D.
  • the comparison method and the processing method after the comparison please refer to the comparison corresponding to the threshold A. methods and processing methods, etc.
  • the quantity threshold is used as an example for introduction.
  • the mobility management network element 2 may set a threshold B, through which flow control is performed on the first type of information used for the UE to request attachment or registration. For example, the first request information is used for the UE to request attachment or registration, then, if the quantity of the first type of information (or the first type of information used for the UE to request attachment or registration) received by the mobility management network element 2 is less than the threshold B , then the mobility management network element 2 can process the first request information, or in other words, the mobility management network element 2 does not ignore the first request information; and if the first type of information received by the mobility management network element 2 (or, for the UE requesting to attach or the number of registered first-type information) is greater than or equal to the threshold B, then the mobility management network element 2 may ignore the first request information.
  • the threshold B through which flow control is performed on the first type of information used for the UE to request attachment or registration. For example, the first request information is used for the UE to request attachment or registration, then, if the quantity of the first type of information
  • the mobility management network element 2 processes the first request information
  • one processing method is, for example, the mobility management network element 2 sends the first response information to the UE, wherein, if the mobility management network element 2 does not consider the first event, or if it does not If the first event is satisfied (or "not satisfying" the first event can also be described as "does not belong to” the first event), the first response information can also be called the first acceptance information, and the first acceptance information can indicate the attach request The acceptance of the information (at this time, the first request information is the attach request information), or indicates the acceptance of the registration request information (at this time, the first request information is the registration request information); or, if the first event ( Alternatively, "satisfying" the first event may also be described as "belonging to" the first event), then the first response information may indicate that processing of the first request information is refused. The first event will be introduced later.
  • the mobility management network element 2 performs flow control on the first type of information used for UE requesting attachment or registration, and the threshold involved in the flow control strategy may not use the quantity threshold (for example, threshold B), but use the rate threshold.
  • the mobility management network element 2 compares the received rate of the first type of information (or the first type of information used for UE requesting attachment or registration) with the threshold E.
  • the threshold B Corresponding comparison methods and processing methods, etc.
  • the quantity threshold is used as an example for introduction.
  • the mobility management network element 2 may also request the user management network element to obtain the subscription data of the UE, or request the UE to The location update of the UE (or in other words, request to update the location information of the UE). If the mobility management network element 2 obtains the subscription data of the UE from the user management network element, or successfully executes the location update of the UE, then the mobility management network element 2 may send the first response message to the UE to indicate the acceptance of the attach request message or acceptance of registration request information.
  • the mobility management network element 2 processes the first request information, if the first event is satisfied (or "satisfied" the first event may also be described as "belonging to” the first event, or may also be described as the first Time occurs, this application is not limited), then the mobility management network element 2 may not be able to obtain the subscription data of the UE from the user management network element, or may not be able to perform the location update of the UE through the user management network element, then the first response information is The rejection response information, for example, the first response information may be referred to as the second rejection information.
  • the second rejection information may further include a first rejection reason value, and the first rejection reason value may indicate that the UE continues to try to connect, so that the UE does not have to fall back to the low-standard network.
  • the first event may include one or more of the following: event 1, event 2, event 3, or event 4. These events are introduced below.
  • Event 1 is an event that the mobility management network element 2 does not receive a response after sending the second request information to the user management network element.
  • the second request information may be used to request to acquire the subscription data of the UE, or to request to perform location update.
  • the second request information is, for example, information sent by the mobility management network element 2 to the user management network element after receiving the first request information. If no response is received from the user management network element, the mobility management network element 2 may send a rejection message to the UE. Response message.
  • One possible situation is that user management network elements are congested or faulty.
  • Event 2 is that after the mobility management network element 2 sends multiple pieces of third request information to the user management network element, the proportion of the number of third request information that has not received a response to the multiple pieces of third request information is greater than or equal to the third Threshold events.
  • the third request information may be used to request to acquire subscription data of the UE, or to request to perform location update.
  • the mobility management network element 2 may have received information for requesting attachment or registration from one or more UEs, and the mobility management network element 2 may also have sent one or more pieces of third request information to the user management network element.
  • the UE corresponding to the information requested by the third request information is the UE sending the first request information; or the third request information corresponding to the first request information may not be included.
  • Event 3 is that the mobility management network element 2 sends a plurality of pieces of fourth request information to the user management network element, and the mobility management network element 2 indicates the response corresponding to the rejection in the response received from the user management network element.
  • the mobility management network element 2 may have received information for requesting attachment or registration from one or more UEs, and the mobility management network element 2 may also have sent one or more pieces of fourth request information to the user management network element.
  • the mobility management network element After the mobility management network element sends the fourth request information to the user management network element, if the user management network element can process the received information, the user management network element should reply to the mobility management network element with a response to the fourth request information, the The response includes, for example, the subscription data of the UE; and if the user management network element cannot handle it, for example, the user management network element is congested, the user management network element may not reply to the mobility management network element with a response to the fourth request information, Alternatively, the user management network element may also reply a response to the fourth request information to the mobility management network element, where the response is, for example, a rejection response, or the response indicates rejection. It should be noted that, among the multiple pieces of fourth request information used for discrimination with the fourth threshold, the fourth request information corresponding to the first request information may be included; or the fourth request information corresponding to the first request information may not be included. request information.
  • Event 4 is that the amount of information sent by the mobility management network element 2 to the user management network element for obtaining subscription data or for requesting location update is greater than or equal to the fifth threshold. If the number of information sent by the mobility management network element 2 to the user management network element for obtaining subscription data or requesting location updates is greater than or equal to the fifth threshold, that is, the information received by the user management network element for obtaining subscription data or requesting The location update information has exceeded the processing capability of the user management network element. Therefore, in this case, the mobility management network element 2 may also reply a rejection to the UE.
  • the flow control strategy for the first type of information is introduced above when the first type of information is used to request services or for the UE to request attachment or registration.
  • the first type of information may also request the establishment of a session.
  • a corresponding flow control policy may also be used to control the flow of the first type of information.
  • the mobility management network element 2 may set a threshold C, through which flow control is performed on the first type of information used to request session establishment. For example, the first request information is used to request to establish a session, then, if the quantity of the first type of information (or the first type of information used to request the establishment of a session) received by the mobility management network element 2 is less than the threshold C, the mobility management The network element 2 may process the first request information.
  • the manner in which the mobility management network element 2 processes the first request information is that the mobility management network element 2 sends the first response information to the UE to indicate the success or failure of the session establishment; and if the mobile If the quantity of the first type of information (or the first type of information used to request session establishment) received by the management network element 2 is greater than or equal to the threshold C, then the mobility management network element 2 may ignore the first request information.
  • the threshold C may also be called the sixth threshold.
  • the mobility management network element 2 performs flow control on the first type of information used to request session establishment, and the threshold involved in the flow control strategy may not use the quantity threshold (for example, threshold C), but the rate threshold.
  • the mobile management network element 2 compares the rate of the received first-type information (or the first-type information used to request session establishment) with the threshold F, and the comparison method and the processing method after the comparison can refer to the corresponding threshold C Comparing methods and processing methods, etc.
  • the quantity threshold is used as an example for introduction.
  • a certain threshold is a rate threshold
  • the rate of the first type of information compared with the threshold is, for example, the rate of one first type of information, or the rate of multiple first type information average rate.
  • the threshold A is a rate threshold
  • the rate of the first-type information compared with the threshold A is, for example, the rate of one first-type information, or the average rate of multiple first-type information.
  • Threshold A, threshold B, and threshold C may be the same threshold, or they may be different thresholds, or any two of them may be the same threshold, and the other may be a different threshold.
  • threshold A and threshold B are different thresholds, in some optional implementation manners, for example, threshold A may also be called a first threshold, and threshold B may also be called a second threshold.
  • the embodiments of the present application set different traffic control policies for different types of signaling. For example, for the information used to request a service, the adopted flow control strategy is to perform flow control according to the first threshold. For another example, for the signaling for the UE to request attachment or registration, the adopted flow control strategy is, for example, to perform flow control according to the second threshold. In this way, differentiated flow control measures can be taken for different types of signaling, so that the flow control process is more in line with the characteristics of the corresponding signaling, so as to achieve better flow control effects.
  • a manner for a network element to ignore certain information is, for example, that the network element discard the information, which will not be described in detail below.
  • the mobility management network element ignores the first request information is that the mobility management network element 2 discards the first request information.
  • the mobility management network element 2 performs flow control on the first type of information, some information may be processed continuously (or some information may not be ignored), and during the process of continuing processing, It will involve the processing of user management network elements. Then, for the user management network element, it needs to process a large amount of information, which may exceed the processing capacity of the user management network element, which may cause congestion, and may even cause a large amount of information to be blocked by the user due to the excessive amount of information. If the management network element is neglected, the network processing efficiency is reduced, and the service of the UE cannot be restored for a long time.
  • the embodiment of the present application proposes that the second threshold may be set according to the capability (or performance) of the user management network element, or in other words, the second threshold is related to the performance of the user management network element.
  • the second threshold is set according to the performance of the user management network element, which is only an optional solution. In other solutions, the second threshold can also be set according to other factors, which is not limited in the embodiment of this application .
  • the UE may send the information corresponding to the second threshold again.
  • the first threshold can be set according to the second threshold, so that after the information corresponding to the first threshold is determined by the mobility management network element 2 to continue processing, the amount of information corresponding to the second threshold sent by the UE will be less than or equal to the second threshold.
  • Two thresholds that is, try to ensure that after the information corresponding to the first threshold is continued to be processed by the mobility management network element 2, the information corresponding to the second threshold sent by the UE can also be continued by the mobility management network element 2 and the user management network element as much as possible deal with. For example, if the UE does not receive a response after sending the information for requesting attachment or registration, the UE will resend the information for requesting attachment or registration every 15 seconds + 10 seconds. If the response is still not received after resending 4 times, the UE will fall back to the low standard network and try to return to the current network after 12 to 20 minutes.
  • the information used to request attachment or registration can be processed by the mobility management network element 2 and the user management network element as much as possible, reducing the situation that the UE does not get a response, thereby reducing The probability that the UE falls back to a low standard network is reduced.
  • the first threshold is within the first range, the lower limit of the first range is N 1 times the second threshold, the upper limit is N 2 times the second threshold, and N 2 is greater than N 1 .
  • the mobility management network element 2 determines to continue processing A1 pieces of information for requesting services according to flow control, there may also be A1 pieces of information for requesting attachment or registration re-initiated by the UE, where A1 is, for example, the second threshold N 2 times. During this processing, the mobility management network element 2 may ignore the A 2 pieces of information used to request attachment or registration to the core network according to the second threshold, and A 2 is, for example, (N 2 -N 1 ) times.
  • the UE will try to send the information for requesting attachment or registration again. For example, the UE can have 4 attempts. If the 4 attempts are unsuccessful, it will fall back to the low-standard network, and the If the value is set to N 1 to N 2 times the second threshold, it can ensure that the information used to request attachment or registration will be continued to be processed by the mobility management network element 2 during the 4 attempts of the UE, thereby reducing the number of UEs.
  • the first threshold and/or the second threshold may be predefined by a protocol, or set by the mobility management network element 2 itself, or may also be manually set in the mobility management network element 2 .
  • FIG. 3 is a schematic diagram of the first threshold and the second threshold.
  • the blank boxes in it represent the first type of information used to request services, and the diagonally drawn boxes represent the first type of information used for the UE to request attachment or registration.
  • the mobility management network element such as the mobility management network element 2
  • the first threshold and the second threshold can be set. By setting these two thresholds, it is possible to implement flow control for different types of information respectively, and since the second threshold is It is set according to the performance of the user management network element, so that the information for UE requesting attachment or registration determined by the mobility management network element 2 to continue processing according to the flow control can be successfully processed by the user management network element.
  • FIG. 3 is an example in which the first threshold is greater than the second threshold, and it is not limited to this in practical applications.
  • the first threshold may also be less than or equal to the second threshold.
  • the mobility management network element 2 may perform flow control on the first type of information, and the first type of information may be information that should be originally processed by the mobility management network element 1 .
  • This method can enable the information of users who originally access the mobility management network element 2 to be processed, reduce the impact on users, and ensure services.
  • the first request information is used for requesting a service, or for a UE to request attachment or registration.
  • FIG. 4 is a flow chart of this embodiment.
  • the mobility management network element is an MME
  • the access network element is an eNB as an example.
  • the method may include the steps of:
  • the UE sends request information A.
  • request information A reference may be made to the description of the first request information in the embodiment shown in FIG. 2 . Therefore, for the manner in which the UE sends the request information A, reference may also be made to S201 in the embodiment shown in FIG. 2 .
  • request information A is used to request a service, and the service requested by request information A may be called a first service.
  • the request information A is a service request, or it may be other information.
  • the MME2 sends first rejection information to the UE.
  • MME2 sends the first rejection information to the UE through the eNB.
  • the first rejection information may be service rejection (service reject).
  • service reject carries a rejection reason value #10, where #10 indicates implicitly detached.
  • the request information A belongs to the first type of information as an example.
  • the MME2 may determine that the requested information A belongs to the first type of information according to the first information included in the requested information A.
  • the first information may include an MME code.
  • MME2 can obtain the system architecture evolution temporary mobile subscriber identity (SAE-temporary mobile subscriber identity, S-TMSI) information element of the UE from the service request, where the SAE is the system architecture evolution (system architecture evolution) ).
  • SAE system architecture evolution
  • S-TMSI system architecture evolution
  • the S-TMSI information element includes MMEC and mobile management entity temporary mobile subscriber identity (MME-temporary mobile subscriber identity, M-TMSI).
  • MME-temporary mobile subscriber identity, M-TMSI mobile management entity temporary mobile subscriber identity
  • the MME2 may control the flow of the request information A according to the threshold A introduced in the embodiment shown in FIG. 2 .
  • the flow control manner of MME2 reference may be made to S203 in the embodiment shown in FIG. 2 .
  • the MME2 may have different processing methods for the request information A after the flow control, and S402 is an example that the MME2 does not ignore the request information A.
  • the UE sends request information B.
  • request information B reference may be made to the description of the first request information in the embodiment shown in FIG. 2 . Therefore, for the manner in which the UE sends the request information B, reference may also be made to S201 in the embodiment shown in FIG. 2 .
  • the request information B is used for the UE to request to attach (attach) to the MME2, for example, the request information B is an attach request (attach request).
  • the request information B is an attach request (attach request).
  • the mobile management network element B receives the attach request, it can obtain the globally unique temporary UE identity (GUTI) information element of the UE from the attach request, and the GUTI information element includes GUMMEI and M-TMSI.
  • the first information may include MMEC. Taking request information B as an attach request as an example, MMEC can be included in GUMMEI.
  • S202 for how the MME2 determines according to the first information that the requested information A belongs to the first type of information.
  • the MME2 may control the flow of the request information B according to the threshold B introduced in the embodiment shown in FIG. 2 .
  • the flow control manner of MME2 reference may also be made to S203 in the embodiment shown in FIG. 2 .
  • the MME2 may have different processing methods for the request information B after the flow control, and S404 is an example that the MME2 does not ignore the request information B.
  • the MME2 acquires the subscription data of the UE from the HSS.
  • MME2 sends an attach success message to the UE.
  • MME2 sends the attach success message to the eNB, and the eNB can send the attach success message to the UE, so the UE can receive the attach success message from the eNB.
  • the UE may continue to request to create a data PDN connection, or to create a data PDN connection and a voice PDN connection, etc., and there is no restriction on subsequent operations.
  • FIG. 5 is a flow chart of this situation.
  • the mobility management network element is an AMF
  • the access network element is a gNB as an example.
  • the method may include the following steps:
  • the UE sends request information C.
  • request information C refer to the description of the first request information in the embodiment shown in FIG. 2 . Therefore, for the manner in which the UE sends the request information C, refer to the description of S201 in the embodiment shown in FIG. 2 .
  • request information C is used to request a service, and the service requested by request information A may be called a first service.
  • the request information C is a service request, or it may be other information.
  • the AMF2 sends first rejection information to the UE.
  • AMF2 sends the first rejection information to the gNB, and the gNB sends the first rejection information to the UE.
  • the first rejection information may be service reject.
  • the service reject can carry reason value #10.
  • the request information A belongs to the first type of information as an example.
  • AMF2 may determine that the request information A belongs to the first type of information according to the first information included in the request information A.
  • the first information may include AMF set ID and AMF pointer.
  • AMF2 receives the service request, it can obtain the 5G-S-TMSI information element of the UE from the service request, and the 5G-S-TMSI information element includes AMF set ID, AMF pointer and 5G-TMSI.
  • AMF2 determines according to the first information that the request information C belongs to the first type of information, reference may be made to the description of S202 in the embodiment shown in FIG. 2 .
  • AMF2 determines that the request information C belongs to the first type of information, it can control the flow of the request information C according to the threshold A introduced in the embodiment shown in FIG. 2 .
  • the threshold A introduced in the embodiment shown in FIG. 2 .
  • S203 in the embodiment shown in FIG. 2 .
  • the AMF2 may have different processing methods for the request information C, and S502 is an example that the AMF2 does not ignore the request information C.
  • the UE sends request information D.
  • request information D For the request information D, reference may be made to the description of the first request information in the embodiment shown in FIG. 2 . Therefore, for the manner in which the UE sends the request information D, reference may also be made to S201 in the embodiment shown in FIG. 2 .
  • the request information D is used for the UE to request to register with AMF2, for example, the request information D is a registration request.
  • AMF2 acquires the subscription data of the UE from the UDM.
  • the request information D belongs to the first type of information as an example.
  • AMF2 may determine that the request information D belongs to the first type of information according to the first information included in the request information D.
  • the first information may include GUAMI. Take the request information D as a registration request as an example. When AMF2 receives the registration request, it can obtain the 5G-GUTI information element of the UE from the registration request, and the 5G-GUTI information element includes GUAMI and 5G-TMSI.
  • the first information may include AMF set ID and AMF pointer. Taking the request information D as a registration request as an example, GUAMI also includes AMF set ID and AMF pointer, which can be included in GUAMI.
  • AMF2 determines according to the first information that the request information D belongs to the first type of information, reference may be made to the description of S202 in the embodiment shown in FIG. 2 .
  • AMF2 may perform flow control on the request information D according to the threshold B introduced in the embodiment shown in FIG. 2 .
  • the flow control manner of AMF2 reference may also be made to S203 in the embodiment shown in FIG. 2 .
  • AMF2 may have different processing methods for request information D after flow control, and S504 is an example where AMF2 does not ignore request information D.
  • AMF2 sends a registration success message to the UE.
  • AMF2 sends the registration success message to UE through gNB.
  • the UE may continue to request to create a data PDU session and/or a voice PDU session, etc., and there is no restriction on subsequent operations.
  • the first type of information may include various types of information, for example, information for requesting a service, or information for a UE to request attachment or registration, and the like.
  • information for requesting a service or information for a UE to request attachment or registration, and the like.
  • an embodiment of the present application provides a communication method, in which different flow control strategies can be adopted for different types of information, so as to achieve better control effects.
  • the mobility management network element may be an MME; or if the embodiment of the present application is applied to a 5G system, the mobility management network element may be an AMF.
  • the mobility management network element 2 in FIG. 6 may refer to the description of the mobility management network element 2 in the embodiment shown in FIG. 2, and the method may include the following steps:
  • the UE sends request information E.
  • the mobility management network element 2 receives the request information E.
  • the request information E is, for example, the first request information in the embodiment shown in FIG. 2 .
  • the request information E can be used to request a service, for example, to request a first service.
  • the request information E is, for example, a service request.
  • For the manner in which the UE sends the request information E to the mobility management network element refer to the introduction of the UE sending the first request information to the mobility management network element in S201 of the embodiment shown in FIG. 2 .
  • the mobility management network element 2 If the amount of information for requesting services received by the mobility management network element 2 is less than the first threshold, the mobility management network element 2 sends first rejection information to the UE. Correspondingly, the UE receives first rejection information from the mobility management network element 2 .
  • the first rejection information may be used to reject the service requested by the first request information.
  • the mobility management network element 2 may initiate a traffic control policy.
  • a flow control strategy is to control the flow of information used to request services according to the first threshold.
  • the flow control policy and the first threshold, etc. reference may be made to the description of the embodiment shown in FIG. 2 .
  • the mobility management network element 2 may first determine that the request information E belongs to the first type of information, and then perform flow control on the request information E according to the first threshold.
  • the mobility management network element 2 determines whether the request information E belongs to the first type of information refer to the description of S202 in the embodiment shown in FIG.
  • S203 For different processing modes of the request information E after control, etc., reference may be made to the description of S203 in the embodiment shown in FIG. 2 .
  • the UE sends request information F.
  • the request information F can be used for the UE to request attachment, for example, the request information F is an attach request; or, if the embodiment of the present application is applied to a 5G system, the request information F can be used for the UE to request registration , for example, the request information F is registration request.
  • request information F reference may be made to the description of the first request information for the UE to request attachment or registration in the embodiment shown in FIG. 2 .
  • the UE receives the first rejection information, then the UE considers that the previous attachment (or registration) in the core network failed, so the UE can delete the local session information, and send the request information F to request to attach or register to the Mobility management network element 2.
  • the mobility management network element 2 obtains subscription data of the UE from the user management network element. It can be understood that if the amount of information received by the mobility management network element 2 for requesting attachment or registration is less than the second threshold, the mobility management network element 2 may obtain the subscription data of the UE or request the location of the UE from the user management network element Update, etc., the embodiments of the present application mainly take the acquisition of subscription data of the UE as an example.
  • the user management network element is, for example, an HSS; if the technical solution of the embodiment of the present application is applied to a 5G system, the user management network element is, for example, a UDM.
  • the flow control strategy adopted by the mobility management network element 2 is to perform flow control according to the second threshold.
  • the second threshold reference may be made to the description of the second threshold in the embodiment shown in FIG. 2 .
  • the mobility management network element 2 may first determine that the requested information F belongs to the first type of information, and then perform flow control on the requested information F according to the second threshold.
  • the description of S202 in the embodiment shown in FIG. For different processing modes of the request information F after control, etc., reference may be made to the description of S203 in the embodiment shown in FIG. 2 .
  • the mobility management network element 2 sends the first response information to the UE.
  • the mobility management network element 2 may send the first response information to the UE through the network element of the access network.
  • the mobility management network element 2 may send first response information to the UE, for example, the first response information may also be referred to as first acceptance information.
  • the first acceptance information may indicate that the UE attaches successfully, or the first acceptance information may indicate Acceptance of the attachment request information; and if the first request information is used for the UE to request registration (or in other words, the first request information includes the UE's registration request information), the first acceptance information may indicate that the UE registration is successful, or , the first acceptance information may indicate acceptance of the registration request information.
  • the mobility management network element 2 may ignore the service request information exceeding the first threshold. As for the information used to request a service, even if it is ignored, the UE will continue to stay in the current network and try again and again, and will not fall back to a low-standard network. For the information for requesting services within the first threshold, the mobility management network element 2 can continue to process, so that the UE can continue to send the information for requesting attachment or registration. As for the information for the UE to request attachment or registration, the mobility management network element 2 will continue to process it according to the second threshold, and these information can also be successfully processed by the user management network element.
  • the embodiment of the present application may not distinguish the first type of information, and may perform flow control on all information to reduce the pressure on the core network as a whole; or may only perform flow control on the first type of information, and the first type of information For example, it is disaster recovery information, so as to reduce the impact on users who originally access the mobility management network element 2 and ensure the service continuity of these users.
  • HSS/UDM is one of the network elements with the most centralized signaling. It is a GUL (global system for mobile communications (GSM)/universal mobile telecommunications system (UMTS) /LTE)/5G/IMS three-domain simultaneous intersection network element.
  • GSM global system for mobile communications
  • UMTS universalal mobile telecommunications system
  • IMS three-domain simultaneous intersection network element.
  • the MME/AMF perceives that a large amount of information sent to the HSS/UDM has failed, and will start flow control, and reject the UE's attach request/registration by carrying a special reason value request, to control the amount of signaling information sent to HSS/UDM, reduce the signaling impact on HSS/UDM, and protect HSS/UDM.
  • Table 2 for the relationship between the special cause value and the UE behavior.
  • the current rejection reason value of the MME/AMF reply is #111.
  • the rejection reason value indicates "protocol error (unspecified)"
  • the UE receives the rejection reason value #111 it will fall back to the low standard network, and after dozens of minutes Only then will it return and re-connect again, which causes the service of the UE to not be restored for a long time.
  • the embodiment of this application provides a communication method, please refer to Figure 7, the method includes the following steps:
  • the UE sends first request information.
  • the first request information reference may be made to the description of the first request information in FIG. 2 , where the first request information is, for example, the first request information in FIG. 2 for the UE to request attachment or registration.
  • the first request information is, for example, the first request information in FIG. 2 for the UE to request attachment or registration.
  • this step reference may be made to the description of step 201 in FIG. 2 .
  • the mobility management network element 2 determines whether the first event is satisfied.
  • the mobility management network element 2 may process the first request information, for example, the mobility management network element 2 may request the UE's subscription data and/or request location update, etc. from the user management network element; and if If the first event is met, the mobility management network element 2 may reply a rejection to the UE, so as to refuse to process the first request information.
  • the first event reference may be made to the description of the first event in S203 of the embodiment shown in FIG. 2 .
  • the mobility management network element 2 sends the first response information to the UE.
  • the mobility management network element 2 sends the first response information to the network element of the access network, and the network element of the access network sends the first response information to the UE, and then the UE can receive the first response information from the network element of the access network.
  • the first response information may include a first rejection cause value.
  • the value of the first rejection reason is, for example, #22, or it may also be other values.
  • the first rejection reason value #22 can also be applied to the embodiment shown in FIG. 2 , or the embodiment shown in FIG. 2 is different from the first rejection reason value used in the embodiment shown in FIG. 7 . Please refer to Table 3 for the relationship between the rejection reason value #22 and the UE behavior.
  • the UE can retry every 10 seconds, and if it still fails after 4 consecutive retries, the It will fall back to the low-standard network, return to the high-standard network again after 12 to 20 minutes, and reconnect to the core network in the high-standard network.
  • the low-standard network that the UE falls back to is a 2G network or a 3G network
  • the high-standard network returned by the UE is, for example, a 4G network
  • the low-standard network that the UE falls back to is a 4G network
  • the high-standard network returned by the UE is, for example, a 5G network .
  • the probability of the UE falling back to a low-standard network due to flow control or network congestion can be reduced, and the UE can be kept in the current network as much as possible to reduce the service recovery time.
  • UEs at the failed site reconnect to the network at other sites.
  • the UE may send a large amount of session activation information (such as information for requesting session establishment) to the network, which will affect the session management network element (such as SGW or SMF, etc.) have an impact, causing the session management network element to start flow control, and reject the session activation request that exceeds its own processing capacity.
  • session management network element such as SGW or SMF, etc.
  • a UE in the network does not actually access the network until the network completes data domain access and voice domain access.
  • the UE has two voice modes in the 4G network: circuit switched fallback (CSFB) and IMS.
  • CSFB circuit switched fallback
  • IMS IMS
  • the UE has one voice mode on the 5G network: IMS, where the IMS voice mode requires the UE to activate the IMS voice session.
  • 4G UE and 5G UE behave differently after different session activation request information is rejected, refer to Table 4.
  • the UE may initiate an attach request, and simultaneously request to establish (or activate) a data PDN connection during the attach process. If the establishment (or activation) of the data PDN connection initiated by the UE fails, the UE will fail to attach, and the UE will retry to attach 4 times. If all 4 attempts fail, the UE will fall back to a low-standard network (such as a 2G network or 3G network) and reinitiate the attach. Then, the previous process of attach request brings network delay, and the UE cannot return to the 4G network for a long time, which prolongs the service recovery time of the UE. In the 5G network, the UE can request the core network to establish an IMS voice PDU session.
  • a low-standard network such as a 2G network or 3G network
  • the UE If the UE fails to establish the IMS voice PDU session, the UE will fall back to the 4G network to re-initiate the attachment. This will lead to a waste of the processing of the registration request in the early stage, and the UE cannot return to the 5G network for a long time, prolonging the service recovery time of the UE.
  • an embodiment of the present application provides a communication method.
  • the UE can perform differentiated flow control on information corresponding to different types of sessions, so as to reduce the probability of the UE falling back to a low-standard network.
  • the mobility management network element is the MME
  • the session management network element is the SGW, or if the control plane and user plane separation (CUPS) of the SGW
  • the session management network element is a control plane service gateway (serving gateway for control plane, SGW-C)
  • the mobility management network element is an AMF
  • the session The management NE is the SMF.
  • the method shown in Figure 8 may include the following steps:
  • the UE sends first request information to a session management network element.
  • the UE's first request information may be transmitted to the session management network element through the access network element and the mobility management network element.
  • the first request message may request to establish a session.
  • the embodiment of the present application is applied to a 4G system, and the first request information is, for example, used for requesting establishment of a data PDN connection, or for requesting establishment of a voice PDN connection.
  • the first request information is used, for example, to request to establish a data PDU session, or to request to establish a voice PDU session.
  • the session management network element processes the first request information according to a traffic control policy corresponding to the first-type session.
  • the session management network element may process the first request information according to the flow control policy corresponding to the request information for requesting establishment of the first type of session.
  • the first type is, for example, a data type or a voice type.
  • the first request information is, for example, used to request establishment of a voice PDN connection, that is, the first type is a voice type.
  • the session management network element can respond to requests to establish a voice PDN connection.
  • Request information (for example, the first request information) performs flow control. Even if the first request information is rejected due to flow control, the UE will not fall back to the low-standard network, and the service recovery time of the UE can be guaranteed to a certain extent.
  • the session management network element processes the first request information according to the flow control policy corresponding to the first type of session. For example, in one way, a seventh threshold is set in the session management network element. The amount of information requesting the establishment of the first type of session is less than the seventh threshold, the session management network element continues to process the first request information; and if the amount of information received by the SGW for requesting the establishment of the first type of session is greater than or is equal to the seventh threshold, the session management network element may send rejection information to the UE.
  • the above processing method of the session management network element may only be aimed at a single UE, for example, flow control may be performed for the first type of request information sent by a certain UE, so that differentiated control of a single UE may be realized; or , the above processing method of the session management network element can also be aimed at multiple UEs.
  • the session management network element does not pay attention to which UE the information comes from, as long as it is the first type of request information (or in other words, it is used in the 4G network to request the establishment of a voice PDN connection information, or the information used to request the establishment of a data PDU session in the 5G network), the session management network element performs flow control, which can prevent more UEs from falling back to the low-standard network to a large extent, and can ensure that a large number of UEs Business recovery time.
  • the mobility management network element may also perform flow control on information used to request establishment of a session of the first type. That is to say, different network elements can perform flow control on the information used to request the establishment of the first type of session, for example, the mobility management network element and/or the session management network element can control the information used to request the establishment of the first type of session Information flow control, wherein, the flow control policy (such as the threshold) used by the mobility management network element and the session management network element in the flow control can be the same or different, so that the impact of signaling on the backend network can be further reduced. Yuan impact, improve network reliability.
  • the flow control policy such as the threshold
  • FIG. 9 is a flowchart of this situation.
  • the session management network element is the SGW and the mobility management network element is the MME as an example.
  • the method may include the steps of:
  • the UE requests to establish a voice PDN connection.
  • the UE may send a first PDN activation request to the MME.
  • the UE's first PDN activation request may reach the MME via the eNB.
  • the first PDN activation request is, for example, a PDN connection request (PDN connectivity request), and the first PDN activation request may be used to request establishment of a voice PDN connection.
  • PDN connectivity request PDN connectivity request
  • the MME may also send a session establishment request to the SGW.
  • the SGW performs flow control on the first PDN activation request.
  • the SGW may obtain an access point name (access point name, APN) from the session establishment request from the MME, and according to the APN, it may be determined that the first PDN activation request is for requesting establishment of a voice PDN connection.
  • APN access point name
  • the first PDN activation request may be regarded as the first request information for requesting establishment of a session of the first type described in the embodiment shown in FIG. 10 .
  • the SGW sends rejection information to the UE.
  • the rejection information sent by the SGW to the MME is the third rejection information
  • the third rejection information is, for example, a session establishment response
  • the session establishment response may carry a rejection reason value A
  • the rejection reason value A is #68, which may indicate that the service does not support ( service not supported);
  • the MME may send fourth rejection information to the UE.
  • the fourth rejection information is, for example, PDN connectivity reject (PDN connectivity reject).
  • the PDN connectivity reject may carry a rejection reason value B, and the rejection reason value B is, for example, #32 , which indicates that the service option is not supported.
  • the SGW may send a create session response to the MME, and accordingly, the MME sends a PDN connection accept (PDN connectivity accept) to the UE ) and other information.
  • PDN connectivity accept PDN connectivity accept
  • the UE continues to request to establish a voice PDN connection on the current network, and will not fall back to a low-standard network. That is, it is equivalent to repeatedly executing S901.
  • the session management network element can perform flow control on the request information (such as the first PDN activation request) requesting to establish a voice PDN connection. Even if the first PDN activation request is rejected due to flow control, the UE will not It will fall back to the low-standard network, and can continue to guarantee the service recovery time of the UE to a certain extent. In the 4G system, if the UE fails to establish a data PDN connection, the UE can try 4 more times.
  • the session management network element can reduce the probability of flow control, for example, the session management network element can continue to process the information used to request the establishment of a data PDN connection, so as to reduce the rejection of such information probability, which reduces the probability of the UE falling back to a low standard network.
  • FIG. 10 is a method for applying the solution of the embodiment shown in FIG. 8 to a 5G system.
  • the session management network element is an SMF
  • the mobility management network element is an AMF as an example for description.
  • the method may include the steps of:
  • the UE sends a registration request to the AMF.
  • the AMF receives the registration request.
  • the UE sends a registration request to the AMF through the gNB.
  • the UE requests to establish a data PDU session.
  • the UE may send a first PDU session establishment request to the AMF.
  • the UE's first PDU session establishment request may reach the AMF via the gNB.
  • the first PDU session establishment request is, for example, a PDU session establishment request, and the first PDU session establishment request may be used to request establishment of a data PDU session.
  • the AMF may also send a session management context request to the SMF, the session management context request, for example, establishing a session management context request (Nsmf_PDUSession_CreateSMContext request) for the SMF service PDU session.
  • this session management context request is referred to as a first session management context request.
  • the SMF performs flow control on the first PDU session establishment request.
  • the first PDU session establishment request is used to request establishment of a data PDU session, and the first PDU session establishment request can be regarded as the first request information for requesting establishment of a first type of session described in the embodiment shown in FIG. 10 .
  • the SMF can control the flow of information used to request the establishment of a data PDU session, so that the UE will not fall back to a low-standard network, and the amount of information processed by the SMF can be effectively controlled.
  • the flow control mode of the SMF to the first PDU session establishment request reference may be made to the introduction of the embodiment shown in FIG. 8 .
  • the seventh threshold involved in the embodiment shown in FIG. 9 may be equal to or not equal to the seventh threshold involved in the embodiment shown in FIG. 10 .
  • the SMF sends rejection information to the UE.
  • the result of the flow control is that the SMF sends rejection information to the UE as an example.
  • the rejection information sent by the SMF to the AMF is fifth rejection information
  • the fifth rejection information is, for example, the SMF service PDU session establishment session management context response (Nsmf_PDUSession_CreateSMContext response).
  • the SMF service PDU session establishment session management context response may carry a rejection reason value C, because the SMF rejects the UE because of flow control, indicating that the SMF needs to process a relatively large amount of information and cannot process the first PDU session establishment request. Therefore, the rejection reason value C is, for example, #26, and #26 can be used to indicate insufficient resources (insufficient resources), where the resources are, for example, processing resources of the SMF.
  • the AMF may send sixth rejection information to the UE, where the sixth rejection information is, for example, a PDU session establishment rejection (PDU session establishment reject). If the fifth rejection information carries the rejection reason value C, then optionally, the PDU session establishment reject may also carry the rejection reason value C.
  • PDU session establishment reject may also carry the rejection reason value C.
  • the SMF may send information such as a PDU session establishment response (PDU session establishment response) to the UE.
  • PDU session establishment response PDU session establishment response
  • the UE performs continuous retry.
  • the UE continues to request the establishment of the data PDU session in the current network, which is equivalent to going back to S1002 to start repeated execution.
  • This step is that the UE does not fall back to the low standard network.
  • the UE requests to establish a voice PDU session.
  • the UE may send a second PDU session establishment request to the AMF.
  • the UE may send a second PDU session establishment request to the AMF through the gNB.
  • the second PDU session establishment request is, for example, a PDU session establishment request, and the second PDU session establishment request can be used to request to establish a voice PDU session.
  • the UE may perform S1206 after the data PDU session is successfully established, or even if the data PDU session is not successfully established, the UE may also perform S1206.
  • the AMF may also send a session management context request to the SMF, where the session management context request is, for example, Nsmf_PDUSession_CreateSMContext response.
  • the session management context request in S1006 is called a second session management context request.
  • the SMF sends an N4 session establishment request to the UPF.
  • the UPF sends an N4 session establishment response to the SMF.
  • the second PDU session establishment request is used to request to establish a voice PDU session.
  • the SMF can continue to process the information used to request the establishment of a voice PDU session, so as to prevent the UE from falling back to the low-standard network.
  • the SMF may send an N4 session establishment request to the UPF to request the establishment of an N4 session, and the N4 session establishment request is, for example, an N4 session establishment request (N4 session establishment request).
  • N4 session establishment request is, for example, an N4 session establishment request (N4 session establishment request).
  • the N4 session establishment response is, for example, an N4 session establishment response (N4 session establishment response).
  • the SMF may send the SMF service PDU session establishment session management context response to the AMF.
  • the AMF sends a PDU session establishment accept/reject (PDU session establishment accept/reject) to the UE to indicate the success or failure of the voice PDU session establishment.
  • PDU session establishment accept/reject PDU session establishment accept/reject
  • the session management network element can perform flow control on the request information (for example, the first PDU session establishment request) requesting to establish a data PDU session, even if the first PDU session establishment request is rejected due to flow control, the UE It will not fall back to the low-standard network, and can continue to guarantee the service recovery time of the UE to a certain extent.
  • the UE if the UE fails to establish a voice PDU session, the UE will fall back to the 4G network.
  • the session management network element can reduce the probability of flow control, for example, the session management network element can continue to process the information used to request the establishment of a voice PDU session, so as to reduce the rejection of such information probability, which reduces the probability of the UE falling back to a low standard network.
  • the embodiment of the present application considers the different response modes of the UE to different types of information, and by performing differentiated flow control on different types of information, the probability of the UE falling back to a low-standard network is reduced, and the service recovery of the UE is improved. efficiency.
  • FIG. 11 shows a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 1100 may be the mobility management network element (for example, the mobility management network element 2 ) or the circuit system of the mobility management network element, used to implement the method corresponding to the mobility management network element in the foregoing method embodiments.
  • the communication device 1100 may be the session management network element described in the embodiment shown in FIG. 8 to the embodiment shown in FIG. 10 or the circuit system of the session management network element, which is used to implement the corresponding A method for session management network elements.
  • a circuit system is a chip system.
  • the communication device 1100 includes at least one processor 1101 .
  • the processor 1101 may be used for internal processing of the device to realize certain control processing functions.
  • processor 1101 includes instructions.
  • processor 1101 may store data.
  • different processors may be separate devices, may be located in different physical locations, and may be located on different integrated circuits.
  • different processors may be integrated within one or more processors, for example, on one or more integrated circuits.
  • the communication device 1100 includes one or more memories 1103 for storing instructions.
  • data may also be stored in the memory 1103 .
  • the processor and memory can be set separately or integrated together.
  • the communication device 1100 includes a communication line 1102 and at least one communication interface 1104 .
  • the communication line 1102 and the communication interface 1104 are all indicated by dotted lines in FIG. 11 .
  • the communication device 1100 may further include a transceiver and/or an antenna.
  • a transceiver may be used to send information to or receive information from other devices.
  • the transceiver may be referred to as a transceiver, a transceiver circuit, an input-output interface, etc., and is used to realize the transceiver function of the communication device 1100 through an antenna.
  • the transceiver includes a transmitter (transmitter) and a receiver (receiver).
  • the transmitter can be used to generate a radio frequency (radio frequency) signal from a baseband signal
  • the receiver can be used to convert the radio frequency signal into a baseband signal.
  • the processor 1101 may include a general-purpose central processing unit (central processing unit, CPU), a microprocessor, a specific application integrated circuit (application specific integrated circuit, ASIC), or one or more integrated circuits for controlling the execution of the program program of this application. circuit.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • Communications link 1102 may include a pathway for communicating information between the components described above.
  • Communication interface 1104 using any device such as a transceiver, for communicating with other devices or communication networks, such as Ethernet, radio access network (radio access network, RAN), wireless local area networks (wireless local area networks, WLAN), Wired access network, etc.
  • a transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (radio access network, RAN), wireless local area networks (wireless local area networks, WLAN), Wired access network, etc.
  • Memory 1103 may be read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory, RAM) or other types that can store information and instructions It can also be an electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be programmed by a computer Any other medium accessed, but not limited to.
  • the memory 1103 may exist independently, and is connected to the processor 1101 through the communication line 1102 . Alternatively, the memory 1103 may also be integrated with the processor 1101 .
  • the memory 1103 is used to store computer-executed instructions for implementing the solutions of the present application, and the execution is controlled by the processor 1101 .
  • the processor 1101 is configured to execute computer-executed instructions stored in the memory 1103, so as to implement the communication method provided by the above-mentioned embodiments of the present application.
  • the computer-executed instructions in the embodiments of the present application may also be referred to as application program codes, which is not specifically limited in the embodiments of the present application.
  • the processor 1101 may include one or more CPUs, for example, CPU0 and CPU1 in FIG. 11 .
  • the communication device 1100 may include multiple processors, for example, the processor 1101 and the processor 1108 in FIG. 11 .
  • Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the chip When the device shown in FIG. 11 is a chip, such as a chip of a mobility management network element, or a chip of a session management network element, the chip includes a processor 1101 (may also include a processor 1108), a communication line 1102, and a memory 1103 and communication interface 1104 .
  • the communication interface 1104 may be an input interface, a pin, or a circuit.
  • the memory 1103 may be a register, a cache, and the like.
  • the processor 1101 and the processor 1108 may be a general-purpose CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling program execution of the communication method in any of the above-mentioned embodiments.
  • the embodiment of the present application may divide the device into functional modules according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation. For example, in the case of dividing each functional module corresponding to each function, FIG.
  • the apparatus 1200 may be a mobility management network element or a session management network element involved in each method embodiment above, or It is a chip in a mobility management network element or a chip in a session management network element.
  • the apparatus 1200 includes a sending unit 1201 , a processing unit 1202 and a receiving unit 1203 .
  • apparatus 1200 may be used to implement the steps performed by the mobility management network element or the session management network element in the method of the embodiment of the present application, and related features may refer to the above embodiments, and details are not repeated here.
  • the functions/implementation process of the sending unit 1201, the receiving unit 1203, and the processing unit 1202 in FIG. 12 may be implemented by the processor 1101 in FIG. 11 invoking computer-executed instructions stored in the memory 1103.
  • the function/implementation process of the processing unit 1202 in FIG. 12 can be realized by calling the computer execution instructions stored in the memory 1103 by the processor 1101 in FIG. The process can be implemented through the communication interface 1104 in FIG. 11 .
  • the functions/implementation process of the sending unit 1201 and the receiving unit 1203 may also be implemented through pins or circuits.
  • the present application also provides a computer-readable storage medium.
  • the computer-readable storage medium stores computer programs or instructions. When the computer programs or instructions are executed, the session management network element or mobility management network The method performed by the element. In this way, the functions described in the above embodiments can be realized in the form of software function units and sold or used as independent products. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or the part that contributes to it or the part of the technical solution.
  • the computer software product is stored in a storage medium, including several instructions for So that a computer device (which may be a personal computer, a server, or a network device, etc.) executes all or part of the steps of the methods described in the various embodiments of the present application.
  • the storage medium includes: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.
  • the present application also provides a computer program product, the computer program product including: computer program code, when the computer program code is run on the computer, the computer is made to execute the session management network element or mobility management method in any of the foregoing method embodiments. The method performed by the network element.
  • the embodiment of the present application also provides a processing device, including a processor and an interface; the processor is configured to execute the method performed by the mobility management network element or the session management network element involved in any one of the above method embodiments.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (such as a floppy disk, a hard disk, or a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (solid state disk, SSD)), etc.
  • the various illustrative logic units and circuits described in the embodiments of the present application can be programmed through general-purpose processors, digital signal processors (digital signal processors, DSPs), application specific integrated circuits (application specific integrated circuits, ASICs), field programmable A field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to implement or operate the described functions.
  • the general-purpose processor may be a microprocessor, and optionally, the general-purpose processor may also be any conventional processor, controller, microcontroller or state machine.
  • a processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration to accomplish.
  • the steps of the method or algorithm described in the embodiments of the present application may be directly embedded in hardware, a software unit executed by a processor, or a combination of both.
  • the software unit may be stored in RAM, flash memory, ROM, erasable programmable read-only memory (EPROM), EEPROM, registers, hard disk, removable disk, CD-ROM or any other form in the art in the storage medium.
  • the storage medium can be connected to the processor, so that the processor can read information from the storage medium, and can write information to the storage medium.
  • the storage medium can also be integrated into the processor.
  • the processor and the storage medium can be set in the ASIC, and the ASIC can be set in the terminal device.
  • the processor and the storage medium may also be disposed in different components in the terminal device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请涉及一种通信方法及装置。移动管理网元接收来自终端设备的第一请求信息，第一请求信息用于请求第一业务，或为该终端设备的附着请求信息或注册请求信息。当第一请求信息属于第一类信息，第一类信息的原接收网元为故障的移动管理网元，移动管理网元根据对第一类信息的流量控制策略对第一请求信息进行处理。移动管理网元可对第一类信息进行流量控制，第一类信息例如包括本应由故障的移动管理网元处理的信息，通过这种方式，可以减小对用户的影响，使得用户的业务能够得到保障。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2022年02月21日提交中国国家知识产权局、申请号为202210158599.6、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
以第四代移动通信系统(the 4th generation，4G)系统为例。在建设4G系统的演进分组核心网(evolved packet core，EPC)时，为了确保站点故障场景下业务不中断，不同站点的移动性管理实体(mobility management entity，MME)以MME池(pool)的形式部署。当一个站点的MME故障，故障MME的用户信令(例如服务请求(service request))会被演进型网络基站(eNodeB)接入到pool内正常的MME上。大量的信令涌入正常的MME，该MME既要处理正常信令，也要处理本应由故障的MME处理的信令，这可能导致该MME启动信令流量控制机制，对超出自身处理能力的信令进行丢弃，确保设备可以安全平稳运行。但是这种方法会导致原本接入该MME的用户的业务受到影响。
发明内容
本申请实施例提供一种通信方法及装置，用于对不同信令采用差异化的控制方式，减小对用户的业务影响。
第一方面，提供一种通信方法，该方法可由移动管理网元执行，或由包括移动管理网元功能的其他设备执行，或由芯片系统或其他功能模块执行，该芯片系统或功能模块能够实现移动管理网元的功能，该芯片系统或功能模块例如设置在移动管理网元中。可选的，移动管理网元例如为MME或AMF等。该方法包括：接收来自终端设备的第一请求信息，所述第一请求信息用于请求第一业务，或所述第一请求信息为所述终端设备的附着请求信息或注册请求信息；当所述第一请求信息属于第一类信息，所述第一类信息的原接收网元为故障的移动管理网元，根据对所述第一类信息的流量控制策略对所述第一请求信息进行处理。
本申请实施例中，移动管理网元可对第一类信息进行流量控制，因此在接收第一请求信息后，可以确定第一请求信息是否属于第一类信息，如果属于，则可按照第一类信息对应的流量控制策略对第一请求信息进行处理。第一类信息例如包括本应由故障的移动管理网元处理的信息，通过这种方式，可以减小对原本接入所述移动管理网元的用户的影响，使得这些用户的业务能够得到保障。
在一种可选的实施方式中，当所述第一请求信息包括的第一信息所指示的原接收网元，与所述移动管理网元不同，确定所述第一请求信息属于所述第一类信息。第一请求信息的 原接收网元即为原本应该处理第一请求信息的移动管理网元。而所述移动管理网元本地也会配置第一信息，所述移动管理网元本地配置的第一信息指示的就是所述移动管理网元。那么，如果第一请求信息包括的第一信息指示的移动管理网元与所述移动管理网元不同，说明原本应该处理第一请求信息的移动管理网元不是所述移动管理网元，因此就表明第一请求信息属于第一类信息，而如果第一请求信息包括的第一信息指示的移动管理网元与所述移动管理网元是同一网元，说明原本应该处理第一请求信息的移动管理网元就是所述移动管理网元，因此就表明第一请求信息不属于第一类信息。通过这种方式能够较为简单明确地区分容灾信息。
在一种可选的实施方式中，若所述第一请求信息用于请求所述第一业务，所述第一信息包括MMEC，或包括AMF集合ID信息和AMF指针。
当第一请求信息的类型不同时，第一信息也可能有所不同，如上只是举例，具体不做限制。
在一种可选的实施方式中，若所述第一请求信息用于请求所述第一业务，根据对所述第一类信息的流量控制策略对所述第一请求信息进行处理，包括：如果属于所述第一类信息的信息数量小于第一门限，向所述终端设备发送第一拒绝信息，以拒绝所述第一请求信息所请求的业务；或，如果属于所述第一类信息的信息数量大于或等于第一门限，忽略所述第一请求信息。
在一种可选的实施方式中，若所述第一请求信息为所述终端设备的附着请求信息或注册请求信息，所述第一信息包括GUMMEI，或包括GUAMI。
在一种可选的实施方式中，若所述第一请求信息为所述终端设备的附着请求信息或注册请求信息，根据对所述第一类信息的流量控制策略对所述第一请求信息进行处理，包括：如果属于所述第一类信息的信息数量小于第二门限，向所述终端设备发送第一响应信息，所述第一响应信息为第一接受信息，所述第一接受信息用于指示所述附着请求信息的接受或者所述注册请求信息的接受，或，所述第一响应信息用于指示拒绝处理所述第一请求信息；或，如果属于所述第一类信息的信息数量大于或等于第二门限，忽略所述第一请求信息。
对于用于请求业务的第一类信息，可采用第一门限进行流量控制，而对于用于该UE请求附着或注册到核心网的第一类信息，可采用第二门限进行流量控制。通过这种方式，可以对不同类型的信令采取差异化的流量控制措施，使得流量控制过程更为符合相应信令的特征，以取得更好的流量控制效果。
在一种可选的实施方式中，所述方法还包括：如果属于所述第一类信息的信息数量小于第二门限，向所述终端设备发送第一响应信息，包括：如果属于所述第一类信息的信息数量小于所述第二门限，且属于第一事件，向所述终端设备发送所述第一响应信息，所述第一响应信息用于指示拒绝处理所述第一请求信息。如果属于第一类信息的信息数量小于第二门限，移动管理网元还可以继续确定是否属于第一事件，如果属于第一事件，则可以向终端设备指示拒绝处理第一请求信息。第一事件例如用于确定用户管理网元的状态，或者用于确定用户管理网元的处理能力，通过第一事件能够确定用户管理网元是否能够处理与第一请求信息相关的信息，从而减轻用户管理网元的压力。
在一种可选的实施方式中，所述第一事件包括：向用户管理网元发送第二请求信息后未收到响应，所述第二请求信息用于请求获取所述终端设备的签约数据，或用于请求更新 所述终端设备的位置信息。如果移动管理网元向用户管理网元发送第二请求信息后未收到响应，可能表明用户管理网元已无法处理第二请求信息，例如用户管理网元可能拥塞等。因此移动管理网元可以向终端设备回复拒绝。
在一种可选的实施方式中，所述第一事件包括：向用户管理网元发送多条第三请求信息后，未收到响应的第三请求信息占所述多条第三请求信息的比例大于或等于第三门限，所述第三请求信息用于请求获取所述终端设备的签约数据，或用于请求更新所述终端设备的位置信息。移动管理网元可能接收了来自多个UE的多个用于请求附着或注册的信息，则移动管理网元也可能向用户管理网元发送了多条第三请求信息。如果未收到响应的第三请求信息过多，可能表明用户管理网元已无法处理更多信息，因此移动管理网元可以向终端设备回复拒绝，以减少用户管理网元需要处理的信息数量。
在一种可选的实施方式中，所述第一事件包括：向用户管理网元发送多条第四请求信息；所述第四请求信息的响应为拒绝响应的第四请求信息占所述多条第四请求信息的比例大于或等于第四门限；所述第四请求信息用于请求获取所述终端设备的签约数据，或用于请求更新所述终端设备的位置信息。移动管理网元可能接收了来自多个UE的多个用于请求附着或注册的信息，则移动管理网元也可能向用户管理网元发送了多条第四请求信息。如果被拒绝的第四请求信息过多，可能表明用户管理网元已无法处理更多信息，因此移动管理网元可以向终端设备回复拒绝，以减少用户管理网元需要处理的信息数量。
在一种可选的实施方式中，所述第一事件包括：向用户管理网元发送的用于获取签约数据的信息的数量大于或等于第五门限。移动管理网元可能接收了来自多个UE的多个用于请求附着或注册的信息，则移动管理网元也可能向用户管理网元发送了多条用于获取签约数据的信息。如果移动管理网元向用户管理网元发送的用于获取签约数据的信息过多，则用户管理网元可能已经有较大的处理压力，因此移动管理网元可以向终端设备回复拒绝，以减少用户管理网元需要处理的信息数量。
在一种可选的实施方式中，若所述第一响应信息用于指示拒绝处理所述第一请求信息，所述第一响应信息包括第一拒绝原因值，所述第一拒绝原因值用于指示所述终端设备继续尝试连接。由于采用第一拒绝原因值，可以降低终端设备由于流量控制或网络拥塞等原因而回落到低制式网络的概率，将终端设备尽量留在当前网络，减少业务恢复的时间。可选的，第一拒绝原因值例如为#22，或者也可以是其他值。
在一种可选的实施方式中，所述方法还包括：如果属于所述第一类信息的信息数量小于第二门限，从用户管理网元获得所述终端设备的签约数据；向所述终端设备发送第一响应信息，包括：在获得所述终端设备的签约数据后，向所述终端设备发送所述第一响应信息，所述第一响应信息为第一接受信息，所述第一接受信息用于指示所述附着请求信息的接受或者所述注册请求信息的接受。其中，所述第二门限与所述用户管理网元的性能相关。第二门限可以根据用户管理网元的能力(或，性能)来设置，或者说，第二门限与用户管理网元的性能相关。通过设置第二门限，可以尽量保证被移动管理网元流量控制通过的第一类信息(例如用于请求附着或注册到核心网的信息)，在后端都能够被用户管理网元成功处理，减小用户管理网元的拥塞情况出现的概率，提高网络处理效率，也使得终端设备的业务能够尽快恢复。
在一种可选的实施方式中，所述用户管理网元为HSS或UDM。例如对于4G系统，用户管理网元可以是HSS，对于5G系统，用户管理网元可以是UDM。如果将本申请实施 例的方法应用于其他通信系统，则用户管理网元可能还有其他实现方式。
在一种可选的实施方式中，所述第一门限与所述第二门限相关，或者说，所述第一门限是根据所述第二门限设置的。在前文介绍了，对于用于请求业务的第一类信息可采用第一门限进行流量控制，而对于用于UE请求附着或注册的第一类信息可采用第二门限进行流量控制。一般来说，如果移动管理网元不忽略用于请求业务的第一类信息，则终端设备会再发送用于请求附着或注册到核心网的信息，即，用于请求业务的信息与用于请求附着或注册到核心网的信息之间是有关联的。因此，第一门限可以与第二门限相关，这样可以尽量保证在用于请求业务的信息未被移动管理网元忽略后，所转化的用于请求附着或注册到核心网的信息也尽量能够不被移动管理网元忽略，减少网络资源的浪费。
在一种可选的实施方式中，所述第一类信息对应于第一类型的业务会话，所述第一类型为数据类型或语音类型。如果终端设备请求建立第一类型的会话的信息被拒绝，则终端设备可能不会回落到低制式的网络，而是继续在当前网络反复尝试；而如果终端设备请求建立其他类型的会话的信息被拒绝，终端设备可能会回落到低制式的网络。因此第一类信息对应于第一类型的业务会话，即，移动管理网元可以对用于请求第一类型的业务会话的信息进行流量控制，即使这些信息因为流量控制被忽略，终端设备也不会回落到低制式的网络，对于终端设备的业务恢复时间不会有太大影响，也可以减小终端设备回落到低制式网络的概率，提高终端设备的业务恢复效率。
在一种可选的实施方式中，根据对所述第一类信息的流量控制策略对所述第一请求信息进行处理，包括：如果属于所述第一类信息的信息数量小于第六门限，向所述终端设备发送第一响应信息，以指示会话建立成功或失败；或，如果属于所述第一类信息的信息数量大于或等于第六门限，忽略所述第一请求信息。移动管理网元可采用第六门限对第一类信息进行流量控制，这样能够有效控制移动管理网元所处理的信息数量。或者移动管理网元还可以采用其他方式对第一类信息进行流量控制，具体不做限制。
第二方面，提供一种通信方法，该方法可由会话管理网元执行，或由包括会话管理网元功能的其他设备执行，或由芯片系统或其他功能模块执行，该芯片系统或功能模块能够实现会话管理网元的功能，该芯片系统或功能模块例如设置在会话管理网元中。可选的，会话管理网元例如为SGW或SMF等。该方法包括：接收来自终端设备的第一请求信息，所述第一请求信息用于请求建立会话；如果所述第一请求信息所请求建立的会话为第一类型的会话，对所述第一请求信息进行流量控制。
在一种可选的实施方式中，所述第一类型为数据类型或语音类型。
关于第二方面或第二方面的可选实施方式的技术效果，可参考对于第一方面或相应的实施方式的技术效果的介绍。
第三方面，提供一种通信方法，该方法可由移动管理网元执行，或由包括移动管理网元功能的其他设备执行，或由芯片系统或其他功能模块执行，该芯片系统或功能模块能够实现移动管理网元的功能，该芯片系统或功能模块例如设置在移动管理网元中。可选的，移动管理网元例如为MME或AMF等。该方法包括：接收来自终端设备的第一请求信息，所述第一请求信息为所述终端设备的附着请求信息或注册请求信息；如果属于第一事件，向所述终端设备发送第二拒绝信息，所述第二拒绝信息包括第一拒绝原因值，所述第一拒绝原因值用于指示所述终端设备在当前网络继续尝试连接。
移动管理网元在接收第一请求信息后，由于第一请求信息的处理需要用户管理网元的 协助，因此移动管理网元可以考虑用户管理网元的承受能力。例如，移动管理网元可以通过第一事件来确定用户管理网元是否能处理第一请求信息，如果用户管理网元当前无法处理第一请求信息，则移动管理网元可以拒绝处理第一请求信息，以保护用户管理网元。第一事件可能有多种，较为灵活。
在一种可选的实施方式中，所述第一事件包括：向用户管理网元发送第二请求信息后未收到响应，所述第二请求信息用于请求获取所述终端设备的签约数据，或用于请求更新所述终端设备的位置信息。如果移动管理网元向用户管理网元发送第二请求信息后未收到响应，可能表明用户管理网元已无法处理第二请求信息，例如用户管理网元可能拥塞等。因此移动管理网元可以向终端设备回复拒绝。
在一种可选的实施方式中，所述第一事件包括：向用户管理网元发送多条第三请求信息后，未收到响应的第三请求信息占所述多条第三请求信息的比例大于或等于第三门限，所述第三请求信息用于请求获取所述终端设备的签约数据，或用于请求更新所述终端设备的位置信息。移动管理网元可能接收了来自多个UE的多个用于请求附着或注册的信息，则移动管理网元也可能向用户管理网元发送了多条第三请求信息。如果未收到响应的第三请求信息过多，可能表明用户管理网元已无法处理更多信息，因此移动管理网元可以向终端设备回复拒绝，以减少用户管理网元需要处理的信息数量。
在一种可选的实施方式中，所述第一事件包括：向用户管理网元发送多条第四请求信息；所述第四请求信息的响应为拒绝响应的第四请求信息占所述多条第四请求信息的比例大于或等于第四门限；所述第四请求信息用于请求获取所述终端设备的签约数据，或用于请求更新所述终端设备的位置信息。移动管理网元可能接收了来自多个UE的多个用于请求附着或注册的信息，则移动管理网元也可能向用户管理网元发送了多条第四请求信息。如果被拒绝的第四请求信息过多，可能表明用户管理网元已无法处理更多信息，因此移动管理网元可以向终端设备回复拒绝，以减少用户管理网元需要处理的信息数量。
在一种可选的实施方式中，所述第一事件包括：向用户管理网元发送的用于获取签约数据的信息的数量大于或等于第五门限。移动管理网元可能接收了来自多个UE的多个用于请求附着或注册的信息，则移动管理网元也可能向用户管理网元发送了多条用于获取签约数据的信息。如果移动管理网元向用户管理网元发送的用于获取签约数据的信息过多，则用户管理网元可能已经有较大的处理压力，因此移动管理网元可以向终端设备回复拒绝，以减少用户管理网元需要处理的信息数量。
在一种可选的实施方式中，所述方法还包括：确定所述第一请求信息属于第一类信息，所述第一类信息的原接收网元为故障的移动管理网元，且所述第一类信息为流量控制的对象。例如，移动管理网元如果确定第一请求信息属于第一类信息，则可确定是否属于第一事件，而如果第一请求信息不属于第一类信息，移动管理网元就可以不必确定是否满足第一事件，而是可以直接处理第一请求信息。通过这种方式，可以尽量保证原本接入该移动管理网元的用户的信息能够得到处理，提高这些用户的业务连续性。
在一种可选的实施方式中，如果属于第一事件，向所述终端设备发送第二拒绝信息，包括：如果所接收的且属于所述第一类信息的UE的附着请求信息或注册信息的信息数量小于第二门限，且属于第一事件，向所述终端设备发送第二拒绝信息。
在一种可选的实施方式中，所述第二门限与用户管理网元的性能相关，所述用户管理网元用于存储终端设备的签约数据。
关于第三方面或第三方面的可选实施方式所带来的技术效果，可参考对于第一方面或相应的实施方式的技术效果的介绍。
第四方面，提供第四种通信方法，该方法可由移动管理网元执行，或由包括移动管理网元功能的其他设备执行，或由芯片系统或其他功能模块执行，该芯片系统或功能模块能够实现移动管理网元的功能，该芯片系统或功能模块例如设置在移动管理网元中。可选的，移动管理网元例如为MME或AMF等。该方法包括：接收来自终端设备的第一请求信息，所述第一请求信息用于请求第一业务；如果所接收的用于请求业务的信息的数量小于第一门限，向所述终端设备发送第一拒绝信息，以拒绝所述第一请求信息所请求的业务；接收来自所述终端设备的第二请求信息，所述第二请求信息为所述终端设备的附着请求信息或注册请求信息；根据第二门限确定是否忽略所述第二请求信息。
在一种可选的实施方式中，所述方法还包括：如果所接收的用于请求业务的信息的数量大于或等于所述第一门限，忽略所述第一请求信息。
在一种可选的实施方式中，所述方法还包括：确定所述第一请求信息属于第一类信息，所述第一类信息的原接收网元为故障的移动管理网元，且所述第一类信息为流量控制的对象。
在一种可选的实施方式中，确定所述第一请求信息属于第一类信息，包括：如果所述第一请求信息包括的第一信息指示的所述原接收网元与所述移动管理网元不同，确定所述第一请求信息属于所述第一类信息。
在一种可选的实施方式中，所述第一信息包括MMEC，或，所述第一信息包括AMF集合ID和AMF指针。
在一种可选的实施方式中，所述方法还包括：确定所述第二请求信息属于第一类信息。
在一种可选的实施方式中，确定所述第二请求信息属于第一类信息，包括：如果所述第二请求信息包括的第一信息指示的所述原接收网元与所述移动管理网元不同，确定所述第二请求信息属于所述第一类信息。
在一种可选的实施方式中，所述第二信息包括GUMMEI，或包括MMEC；或，所述第二信息包括GUAMI，或包括AMF集合ID信息和AMF指针。
在一种可选的实施方式中，所述第二门限与用户管理网元的性能相关，所述用户管理网元用于存储终端设备的签约数据。
在一种可选的实施方式中，所述第一门限与所述第二门限相关。
在一种可选的实施方式中，根据第二门限确定是否忽略所述第二请求信息，包括：如果所接收的UE的附着请求信息或注册请求信息的数量小于所述第二门限，不忽略所述第二请求信息；或，如果所接收的UE的附着请求信息或注册请求信息的数量大于或等于所述第二门限，忽略所述第二请求信息。
在一种可选的实施方式中，所述方法还包括：如果不忽略所述第二请求信息，向所述终端设备发送第一响应信息，所述第一响应信息为第一接受信息，所述第一接受信息用于指示所述附着请求信息的接受或者所述注册请求信息的接受；或，如果不忽略所述第二请求信息，且满足第一事件，向所述终端设备发送第二拒绝信息。
在一种可选的实施方式中，所述第二拒绝信息包括第一拒绝原因值，所述第一拒绝原因值用于指示所述终端设备在当前网络继续尝试连接。
在一种可选的实施方式中，所述第一事件包括：向用户管理网元发送第二请求信息后 未收到响应，所述第二请求信息用于请求获取所述终端设备的签约数据，或用于请求更新所述终端设备的位置信息。如果移动管理网元向用户管理网元发送第二请求信息后未收到响应，可能表明用户管理网元已无法处理第二请求信息，例如用户管理网元可能拥塞等。因此移动管理网元可以向终端设备回复拒绝。
在一种可选的实施方式中，所述第一事件包括：向用户管理网元发送多条第三请求信息后，未收到响应的第三请求信息占所述多条第三请求信息的比例大于或等于第三门限，所述第三请求信息用于请求获取所述终端设备的签约数据，或用于请求更新所述终端设备的位置信息。移动管理网元可能接收了来自多个UE的多个用于请求附着或注册的信息，则移动管理网元也可能向用户管理网元发送了多条第三请求信息。如果未收到响应的第三请求信息过多，可能表明用户管理网元已无法处理更多信息，因此移动管理网元可以向终端设备回复拒绝，以减少用户管理网元需要处理的信息数量。
在一种可选的实施方式中，所述第一事件包括：向用户管理网元发送多条第四请求信息；所述第四请求信息的响应为拒绝响应的第四请求信息占所述多条第四请求信息的比例大于或等于第四门限；所述第四请求信息用于请求获取所述终端设备的签约数据，或用于请求更新所述终端设备的位置信息。移动管理网元可能接收了来自多个UE的多个用于请求附着或注册的信息，则移动管理网元也可能向用户管理网元发送了多条第四请求信息。如果被拒绝的第四请求信息过多，可能表明用户管理网元已无法处理更多信息，因此移动管理网元可以向终端设备回复拒绝，以减少用户管理网元需要处理的信息数量。
在一种可选的实施方式中，所述第一事件包括：向用户管理网元发送的用于获取签约数据的信息的数量大于或等于第五门限。移动管理网元可能接收了来自多个UE的多个用于请求附着或注册的信息，则移动管理网元也可能向用户管理网元发送了多条用于获取签约数据的信息。如果移动管理网元向用户管理网元发送的用于获取签约数据的信息过多，则用户管理网元可能已经有较大的处理压力，因此移动管理网元可以向终端设备回复拒绝，以减少用户管理网元需要处理的信息数量。
关于第四方面或第四方面的可选实施方式所带来的技术效果，可参考对于第一方面或相应的实施方式的技术效果的介绍。
第五方面，提供一种通信装置。所述通信装置可以为上述第一方面至第四方面的任一方面所述的移动管理网元。所述通信装置具备上述移动管理网元的功能。所述通信装置例如为移动管理网元，或为移动管理网元中的功能模块，例如基带装置或芯片系统等。一种可选的实现方式中，所述通信装置包括基带装置和射频装置。另一种可选的实现方式中，所述通信装置包括处理单元(有时也称为处理模块)和收发单元(有时也称为收发模块)。收发单元能够实现发送功能和接收功能，在收发单元实现发送功能时，可称为发送单元(有时也称为发送模块)，在收发单元实现接收功能时，可称为接收单元(有时也称为接收模块)。发送单元和接收单元可以是同一个功能模块，该功能模块称为收发单元，该功能模块能实现发送功能和接收功能；或者，发送单元和接收单元可以是不同的功能模块，收发单元是对这些功能模块的统称。
在一种可选的实施方式中，所述收发单元，用于接收来自终端设备的第一请求信息，所述第一请求信息用于请求第一业务，或为所述终端设备的附着请求信息或注册请求信息；所述处理单元，用于当所述第一请求信息属于第一类信息，根据对所述第一类信息的流量控制策略对所述第一请求信息进行处理，所述第一类信息的原接收网元为故障的移动管理 网元。
在一种可选的实施方式中，所述收发单元，用于接收来自终端设备的第一请求信息，所述第一请求信息为所述终端设备的附着请求信息或注册请求信息；所述收发单元，还用于如果属于第一事件，向所述终端设备发送第二拒绝信息，所述第二拒绝信息包括第一拒绝原因值，所述第一拒绝原因值用于指示所述终端设备在当前网络继续尝试连接(或者，所述处理单元，用于如果属于第一事件，通过所述收发单元向所述终端设备发送第二拒绝信息，所述第二拒绝信息包括第一拒绝原因值，所述第一拒绝原因值用于指示所述终端设备在当前网络继续尝试连接)。
在一种可选的实施方式中，所述收发单元，用于接收来自终端设备的第一请求信息，所述第一请求信息用于请求第一业务；所述收发单元，还用于如果所接收的用于请求业务的信息的数量小于第一门限，向所述终端设备发送第一拒绝信息，以拒绝所述第一请求信息所请求的业务(或者，所述处理单元，用于如果所接收的用于请求业务的信息的数量小于第一门限，通过所述收发单元向所述终端设备发送第一拒绝信息，以拒绝所述第一请求信息所请求的业务)；所述收发单元，还用于接收来自所述终端设备的第二请求信息，所述第二请求信息为所述终端设备的附着请求信息或注册请求信息；所述处理单元，用于根据第二门限确定是否忽略所述第二请求信息。
在一种可选的实施方式中，所述通信装置还包括存储单元(有时也称为存储模块)，所述处理单元用于与所述存储单元耦合，并执行所述存储单元中的程序或指令，使能所述通信装置执行上述第一方面至第四方面中的任一方面所述的移动管理网元的功能。
第六方面，提供一种通信装置。所述通信装置可以为上述第一方面至第四方面中的任一方面所述的会话管理网元。所述通信装置具备上述会话管理网元的功能。所述通信装置例如为会话管理网元，或为会话管理网元中的功能模块，例如基带装置或芯片系统等。一种可选的实现方式中，所述通信装置包括基带装置和射频装置。另一种可选的实现方式中，所述通信装置包括处理单元(有时也称为处理模块)和收发单元(有时也称为收发模块)。关于收发单元的实现方式可参考第五方面的介绍。
在一种可选的实现方式中，所述收发单元，用于接收来自终端设备的第一请求信息，所述第一请求信息用于请求建立会话；所述处理单元，用于如果所述第一请求信息所请求建立的会话为第一类型的会话，对所述第一请求信息进行流量控制。
在一种可选的实现方式中，所述通信装置还包括存储单元(有时也称为存储模块)，所述处理单元用于与所述存储单元耦合，并执行所述存储单元中的程序或指令，使能所述通信装置执行上述第一方面和/或第二方面所述的接入网设备的功能。
第七方面，提供一种通信系统，包括第五方面所述的通信装置和第六方面所述的通信装置。
第八方面，提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序或指令，当其被运行时，使得上述各方面中移动管理网元或会话管理网元所执行的方法被实现。
第九方面，提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得上述各方面所述的方法被实现。
第十方面，提供一种芯片系统，包括处理器和接口，所述处理器用于从所述接口调用并运行指令，以使所述芯片系统实现上述各方面的方法。
附图说明
图1A为本申请提供的一种通信系统的架构示意图；
图1B为本申请实施例的一种应用场景示意图；
图2、图4～图10为本申请实施例提供的几种通信方法的流程图；
图3为本申请实施例中设置的门限的一种示意图；
图11为本申请实施例提供的一种装置的示意图；
图12为本申请实施例提供的又一种装置的示意图。
具体实施方式
为了使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施例作进一步地详细描述。
以下，对本申请实施例中的部分用语或概念进行解释说明，以便于本领域技术人员理解。本申请实施例中，用于实现网络设备功能的通信装置可以是网络设备，也可以是能够支持网络设备实现该功能的装置，例如芯片系统，该装置可以被安装在网络设备中。在本申请实施例提供的技术方案中，以用于实现网络设备的功能的装置是网络设备为例，描述本申请实施例提供的技术方案。
本申请实施例中，对于名词的数目，除非特别说明，表示“单数名词或复数名词”，即"一个或多个”。“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A,B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。例如，A/B，表示：A或B。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个)，表示：a,b,c,a和b,a和c,b和c,或a和b和c，其中a,b,c可以是单个，也可以是多个。
本申请实施例提及“第一”、“第二”等序数词是用于对多个对象进行区分，不用于限定多个对象的大小、内容、顺序、时序、优先级或者重要程度等。例如，第一请求信息和第二请求信息，可以是同一个信息，也可以是不同的信息。且，这种名称也并不是表示这两个信息的内容、大小、发送端和/或接收端、发送时间、优先级或者重要程度等的不同。另外，本申请所介绍的各个实施例中对于步骤的编号，只是为了区分不同的步骤，并不用于限定步骤之间的先后顺序。例如，S201可以发生在S202之前，或者可能发生在S202之后，或者也可能与S202同时发生。
图1A示出了本申请提供的通信方法适用的一种可能的通信系统的架构，该通信系统的架构可以包括：无线接入网络、终端设备和核心网。示例性的，该通信系统的架构中，无线接入网络中可以包括接入网设备。
本申请实施例中，终端设备是一种具有无线收发功能的设备，可以是固定设备，移动设备、手持设备(例如手机)、穿戴设备、车载设备，或内置于上述设备中的无线装置(例如，通信模块，调制解调器，或芯片系统等)。所述终端设备用于连接人，物，机器等，可广泛用于各种场景，例如包括但不限于以下场景：蜂窝通信、设备到设备通信(device-to-device，D2D)、车到一切(vehicle to everything，V2X)、机器到机器/机器类通 信(machine-to-machine/machine-type communications，M2M/MTC)、物联网(internet of things，IoT)、虚拟现实(virtual reality，VR)、增强现实(augmented reality，AR)、工业控制(industrial control)、无人驾驶(self driving)、远程医疗(remote medical)、智能电网(smart grid)、智能家具、智能办公、智能穿戴、智能交通，智慧城市(smart city)、无人机、机器人等场景的终端设备。所述终端设备有时可称为用户设备(user equipment，UE)、终端、接入站、UE站、远方站、无线通信设备、或用户装置等等。为描述方便，本申请实施例中将终端设备以UE为例进行说明。
接入网设备为具有无线收发功能的设备，用于与所述终端设备进行通信。所述接入网设备包括但不限于基站(基站收发信站点(base transceiver station，BTS)，Node B,eNodeB/eNB，或gNodeB/gNB)、收发点(transmission reception point，TRP)，第三代合作伙伴计划(3rd generation partnership project，3GPP)后续演进的基站，无线保真(wireless fidelity，Wi-Fi)系统中的接入节点，无线中继节点，无线回传节点等。所述基站可以是：宏基站，微基站，微微基站，小站，中继站等。多个基站可以支持同一种接入技术的网络，也可以支持不同接入技术的网络。基站可以包含一个或多个共站或非共站的传输接收点。所述接入网设备还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、集中单元(centralized unit，CU)，和/或分布单元(distributed unit，DU)。例如，车到一切(vehicle to everything，V2X)技术中的接入网设备可以为路侧单元(road side unit，RSU)。以下对接入网设备以为基站为例进行说明。基站可以与终端设备进行通信，也可以通过中继站与终端设备进行通信。终端设备可以与不同接入技术中的多个基站进行通信。
核心网中的设备包括但不限于用于实现移动管理，数据处理，会话管理，策略和计费等功能的设备。以5G系统为例，所述核心网设备可以包括网络开放功能(network exposure function，NEF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management，UDM)、应用功能(application function，AF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、用户面功能(user plane function，UPF)网元等。
接入与移动性管理功能网元，可用于对UE的接入控制和移动性进行管理，在实际应用中，其包括了长期演进(long term evolution，LTE)中网络框架中移动管理实体(mobility management entity，MME)里的移动性管理功能，并加入了接入管理功能，具体可以负责UE的注册、移动性管理、跟踪区更新流程、可达性检测、SMF网元的选择、移动状态转换管理等。例如，在5G系统中，接入与移动性管理功能网元可以是AMF网元，如图1A所示；在未来通信系统，如6G系统中，接入与移动性管理功能网元仍可以是AMF网元，或可能有其它的名称，本申请实施例不做限定。当接入与移动性管理功能网元是AMF网元时，AMF网元可以提供Namf服务。
会话管理功能网元，可用于负责终端设备的会话管理(包括会话的建立、修改和释放，维护用户面功能网元和接入网设备之间的隧道)，用户面功能网元的选择和重选、UE的互联网协议(internet protocol，IP)地址分配(包括可选的授权)、在用户面功能网元中配置流量路由、服务质量(quality of service，QoS)控制等。会话管理功能网元是非接入层(non-access stratum，NAS)消息的会话管理部分终结点。例如，在5G系统中，会话管理功能网元可以是SMF网元，如图1A所示；在未来通信系统，如6G系统中，会话管理功能网元仍可以是SMF网元，或可能有其它的名称，本申请实施例不做限定。当会话管理 功能网元是SMF网元时，SMF网元可以提供Nsmf服务。
用户面功能网元，负责UE的用户数据的转发和接收。UPF网元可以从数据网络接收用户数据，通过接入网设备发送给UE；UPF网元还可以通过接入网设备从UE接收用户数据，并将接收的用户数据转发到数据网络。例如，在5G系统中，用户面功能网元可以是UPF网元，如图1A所示；在未来通信系统，如6G系统中，用户面功能网元仍可以是UPF网元，或可能有其它的名称，本申请实施例不做限定。
统一数据管理功能网元，用于生成认证信任状，用户标识处理(如存储和管理用户永久身份等)，接入授权控制和签约数据管理等。例如，在5G系统中，统一数据管理功能网元可以是UDM网元，如图1A所示；在未来通信系统，如6G系统中，统一数据管理功能网元仍可以是UDM网元，或可能有其它的名称，本申请实施例不做限定。当统一数据管理功能网元是UDM网元时，UDM网元可以提供Nudm服务。
数据网络(data network，DN)，指的是为用户提供数据传输服务的服务网络，如IP多媒体业务(IP multi-media service,IMS)、互联网(Internet)等。
如上主要介绍了本申请的各个实施例可能涉及的一些网元，另外图1A还涉及其他网元，在此不做过多介绍。
UE通过UE到DN之间建立的协议数据单元(protocol data unit，PDU)会话，来访问DN。
其中，核心网中的各个网元也可以称为功能实体或者设备，既可以是在专用硬件上实现的网络元件，也可以是在专用硬件上运行的软件实例，或者是在适当平台上虚拟化功能的实例，例如，上述虚拟化平台可以为云平台。
其中，AMF网元与接入网设备之间可以通过N2接口相连，接入网设备与UPF网元之间可以通过N3接口相连，SMF网元与UPF网元之间可以通过N4接口相连，AMF网元与UE之间可以通过N1接口相连，UPF与DN之间可通过N6接口相连。接口名称只是一个示例说明，本申请实施例对此不作具体限定。应理解，本申请实施例并不限于图1A所示通信系统，图1A中所示的网元的名称在这里仅作为一种示例说明，并不作为对本申请实施例的方法适用的通信系统架构中包括的网元的限定。下面对通信系统中的一些网元或设备的功能进行介绍。不同接入技术的系统中实现核心网功能的设备名称可以不同，本申请实施例并不对此进行限定。
需要说明的是，图1A所示的通信系统并不构成本申请实施例能够适用的通信系统的限定。图1A所示的通信系统架构为5G系统架构，可选的，本申请实施例提供的技术方案除了可应用于5G系统外，还可以应用于第四代移动通信技术(the 4th generation，4G)系统中，例如LTE系统，或者还可以应用于下一代移动通信系统或其他类似的通信系统，具体的不做限制。
需要说明的是，图1A所示的通信系统的架构中不限于仅包含图中所示的网元，还可以包含其它未在图中表示的设备，具体在此处不再一一列举。
需要说明的是，本申请实施例并不限定各个网元的分布形式，图1A所示的分布形式只是示例性的，本申请实施例不作限定。
为方便说明，本申请实施例后续均以图1A所示的网元为例进行说明，并将XX网元直接简称为XX，例如，将SMF网元简称为SMF，将AMF网元简称为AMF等。应理解，本申请实施例中所有网元的名称仅仅作为示例，在未来通信中还可以称为其它名称，或者 在未来通信中本申请实施例涉及的网元还可以通过其它具有相同功能的实体或者设备等来替代，本申请实施例对此均不作限定。这里做统一说明，后续不再赘述。
请再参考图1B，为本申请实施例的一种应用场景示意图。图1B以两个站点为例，实际部署可包括多个站点。不仅MME/AMF可以按照pool的形式部署，网关/SMF也可以以pool的形式部署，例如图1B中，不同站点的网关/SMF也可以部署为pool的形式。另外，不同站点的互联网协议多媒体子系统(internet protocol multimedia subsystem，IMS)也可以以pool的形式部署，对此可参考图1B。例如，在站点1故障之前，图1B中的UE1～UE4均接入站点1，在站点1故障时，无线接入网(radio access network，RAN)向站点2的MME/AMF发送站点1的MME/AMF的用户信令。相应的，站点1的网关/SMF上的用户信令也会被RAN接入站点2的网关/SMF，则UE1～UE4的信令会被接入站点2的网关/SMF。另外，IMS与HSS/UDM之间可能通过中继设备进行中转，SGW/PGW/SMF与HSS/UDM之间可能通过中继设备进行中转，MME/AMF与HSS/UDM之间也可能通过中继设备进行中转，这三种中继设备可以是相同的中继设备，或者是不同的中继设备，在图1B中未画出中继设备。
为了更好地介绍本申请实施例，下面结合附图介绍本申请实施例所提供的方法。在本申请的各个实施例对应的附图中，凡是可选的步骤均用虚线表示。本申请的各个实施例所提供的方法均可应用于图1B所示的网络架构。例如，本申请的各个实施例所涉及的UE即为图1B中的UE1～UE4中的任一个或多个UE，本申请的各个实施例所涉及的移动管理网元或移动管理网元2即为图1B中站点2的MME或AMF，本申请的各个实施例所涉及的移动管理网元1即为图1B中站点1的MME或AMF；本申请的各个实施例所涉及的用户管理网元即为图1B中的站点2的HSS或UDM，本申请的各个实施例所涉及的会话管理网元即为图1B中站点2的网关或SMF，本申请的各个实施例所涉及的接入网网元即为图1B中的RAN。另外，本申请的部分或全部实施例中可能涉及到“低制式”网络这种概念，在此统一说明：如果UE当前驻留在4G网络，那么如果UE回落到低制式网络，该低制式网络可以是指3G网络或2G网络；相应的，与作为低制式网络的2G网络或3G网络所对应的“高制式”网络，可以是4G网络。或者，如果UE当前驻留在5G网络，那么如果UE回落到低制式网络，该低制式网络可以是指4G网络；相应的，与作为低制式网络的4G网络所对应的“高制式”网络，可以是5G网络。
请参见图2，图2为本申请实施例提供的一种通信方法的示意图，应说明的是，图中的移动管理网元1为故障的网元，该符号“×”代表故障或不能正常工作。该方法可以包括以下步骤：
S201、UE发送第一请求信息。
例如，UE通过接入网网元向移动管理网元2发送该第一请求信息。具体的，该UE接入的移动管理网元为移动管理网元1，但是移动管理网元1故障。接入网网元如果确定移动管理网元1故障，则接入网网元可以在移动管理网元池中重新选择正常的移动管理网元，例如选择了移动管理网元2，那么接入网网元可将第一请求信息发送给正常工作的移动管理网元2。可选的，接入网网元与移动管理网元之间可以维持心跳包的传输，接入网网元可通过与移动管理网元1之间的心跳包的异常情况确定移动管理网元1故障。
例如第一请求信息用于请求业务，第一请求信息所请求的业务称为第一业务。可选的，第一请求信息为service request。
或者，第一请求信息可用于该UE请求附着(或者理解为，第一请求信息为该UE的附着请求信息)，例如第一请求信息用于该UE请求附着(attach)到移动管理网元2，例如第一请求信息为附着请求(attach request)。或者，第一请求信息可用于该UE请求注册(registration)，或者理解为，第一请求信息为该UE的注册请求信息，例如第一请求信息用于该UE请求注册到移动管理网元2，例如第一请求信息为注册请求(registration request)。
或者，第一请求信息可用于请求建立会话(或者理解为，第一请求信息为该UE的会话建立请求信息)，例如第一请求信息用于请求建立公共数据网(public data network，PDN)连接，或用于请求建立协议数据单元(protocol data unit，PDU)会话。例如本申请实施例应用于4G系统，第一请求信息例如用于请求建立语音PDN连接或数据PDN连接；又例如，本申请实施例应用于5G系统，第一请求信息例如用于请求建立数据PDU会话或语音PDU会话。
S202、移动管理网元2确定第一请求信息属于第一类信息。
第一类信息可以为容灾信息。例如，第一类信息为本应由除了移动管理网元2之外的其他移动管理网元所处理的信息，或者说，第一类信息的原接收网元并非移动管理网元2。其中，第一类信息的原接收网元为故障的移动管理网元。一个移动管理网元如果坏了，或者一个移动管理网元因为容量限制而超负荷运转，都可视为该移动管理网元故障。需要注意的是，第一类信息的接收网元，并不是指作为中转网元的接入网网元，而是指作该第一类信息原计划发送到的接收该第一类信息的原移动管理网元。因此本申请实施例中，第一类信息的原接收网元为故障的移动管理网元。
如果第一请求信息用于请求业务，或用于UE请求附着或请求注册，则该步骤的一种可能的方式，移动管理网元2可以确定，第一请求信息所包括的第一信息所指示的移动管理网元，与移动管理网元2不是同一个网元。其中，第一信息所指示的移动管理网元，也就是第一请求信息的原接收网元。其中，如果第一请求信息用于请求业务，第一信息可包括MME码(MME code，MMEC)，或者，第一信息可包括AMF集合标识(AMF set ID)和AMF指针(AMF pointer)。如果第一请求信息用于UE请求附着或注册，第一信息可包括全局唯一MME标识(globally unique MME identity，GUMMEI)或MMEC；或者，第一信息包括全局唯一AMF标识(globally unique AMF identifier，GUAMI)，或包括AMF set ID和AMF pointer。
如果第一请求信息用于请求建立会话，则该步骤的一种可能的方式为，移动管理网元2可以确定第一请求信息对应的信息指示的移动管理网元与移动管理网元2不是同一个网元，且第一请求信息所对应的会话是第一类型的会话。其中，如果第一请求信息用于请求建立会话，则第一类信息对应于第一类型的业务会话。后续将业务会话简称为会话。例如第一类信息与第一类型的会话的一种对应方式为，第一类信息为用于请求建立第一类型的会话的信息。例如本申请实施例应用于4G系统，第一请求信息例如用于请求建立语音PDN连接，即，第一类型为语音类型。又例如，本申请实施例应用于5G系统，第一请求信息例如用于请求建立数据PDU会话，即，第一类型为数据类型。
其中，第一请求信息对应的信息，例如是，移动管理网元2在接收第一请求信息之前从第一请求信息的发送端所接收的信息。例如，第一请求信息所对应的信息包括用于请求业务的信息，和/或包括用于请求附着或注册到核心网的信息。其中，用于请求业务的信息例如为service request；用于请求附着或注册到核心网的信息例如为attach request或 registration request。对此可以理解为，移动管理网元2首先从该UE接收了第一请求信息对应的信息，移动管理网元2可以确定第一请求信息对应的信息所指示的移动管理网元(确定方式可参考前文)，而第一请求信息对应的信息所指示的移动管理网元，可以认为也就是第一请求信息所对应的移动管理网元。因此移动管理网元2根据第一请求信息对应的信息所指示的移动管理网元，以及根据第一请求信息所对应的会话的类型，就可以确定第一请求信息是否属于第一类信息。
S203、移动管理网元2根据对第一类信息的流量控制策略，对第一请求信息进行处理。
移动管理网元2可对第一类信息进行流量控制，即，第一类信息是流量控制的对象。因此如果第一请求信息属于第一类信息，则可执行S203。
例如第一类信息为容灾信息，则移动管理网元2通过对第一类信息进行流量控制以减小对原本接入移动管理网元2的用户的业务影响。
可选的，移动管理网元2可设置门限A，通过门限A对用于请求业务的第一类信息进行流量控制。例如第一请求信息用于请求业务，那么，如果移动管理网元2所接收的第一类信息(或，用于请求业务的第一类信息)的数量小于该门限A，则移动管理网元2可以处理第一请求信息，或者说移动管理网元2不忽略第一请求信息。例如移动管理网元2处理第一请求信息的方式为，可以查询请求信息A所对应的UE(即，发送请求信息A的UE)的上下文，以确定对请求信息A的处理方式。但是该UE原本接入的是故障的MME1，该UE的上下文维护在MME1中，则MME2无法查询到该UE的上下文。此时MME2可向该UE发送第一拒绝信息，以拒绝第一请求信息所请求的业务。此处，忽略也可以理解为丢弃，或者理解为不处理，本申请并不限定。
本申请的各个实施例中，如果要将所接收的某类信息的数量与某个门限比较，则该类信息的数量例如为移动管理网元2从启动流量控制策略开始所接收的该类信息的数量，或者为移动管理网元2从启动(或者说，开始工作)开始所接收的该类信息的数量。例如，移动管理网元2要将所接收的第一类信息的数量与门限A比较，则参与比较的第一类信息的数量，例如为移动管理网元2从启动流量控制策略开始所接收的第一类信息的数量，或者为移动管理网元2从启动开始所接收的第一类信息的数量。或者，用于与某个门限相比较的某类信息的数量，可以是在某一个特定的周期内统计的，对于该周期的长短以及该周期的起始时刻等，本申请实施例并不限定。或者，用于与某个门限相比较的某类信息的数量，可以是在某一个特定的时间段内进行统计的，同样，对于该时间段的长短以及该时间段的计时起始时刻等，本申请实施例并不限定。在后文中，对于类似特征不再赘述。
而如果移动管理网元2所接收的第一类信息(或，用于请求业务的第一类信息)的数量大于或等于该门限A，则移动管理网元2可以忽略第一请求信息，即，MME2并不会处理请求信息A，也并不会向UE发送有关请求信息A的响应。以第一请求信息是service request为例，无论对于4G系统还是5G系统，UE在发送service request之后如果收不到响应，则UE可以每隔5秒(second，s)重新发送一次service request。如果在重新发送4次后依然收不到响应，则UE每隔60秒再重新发送一次。
或者，移动管理网元2对用于请求业务的第一类信息进行流量控制，流量控制策略所涉及的门限也可能不使用数量门限(例如门限A)，而是使用速率门限。例如移动管理网元2将所接收的第一类信息(或，用于请求业务的第一类信息)的速率与门限D比较，比较方式以及比较之后的处理方式，可参考门限A对应的比较方式以及处理方式等。在本申请 的各个实施例中，以数量门限为例来介绍。
可选的，移动管理网元2可设置门限B，通过门限B对用于UE请求附着或注册的第一类信息进行流量控制。例如第一请求信息用于UE请求附着或注册，那么，如果移动管理网元2所接收的第一类信息(或，用于UE请求附着或注册的第一类信息)的数量小于该门限B，则移动管理网元2可以处理第一请求信息，或者说移动管理网元2不忽略第一请求信息；而如果移动管理网元2所接收的第一类信息(或，用于UE请求附着或注册的第一类信息)的数量大于或等于该门限B，则移动管理网元2可以忽略第一请求信息。
如果移动管理网元2处理第一请求信息，一种处理方式例如为，移动管理网元2向该UE发送第一响应信息，其中，如果移动管理网元2不考虑第一事件，或者如果不满足第一事件(或者也可将“不满足”第一事件描述为，“不属于”第一事件)，则第一响应信息也可称为第一接受信息，第一接受信息可指示附着请求信息的接受(此时，第一请求信息为所述附着请求信息)，或者指示注册请求信息的接受(此时，第一请求信息为所述注册请求信息)；或者，如果满足第一事件(或者也可将“满足”第一事件描述为，“属于”第一事件)，则第一响应信息可指示拒绝处理第一请求信息。关于第一事件将在后文介绍。
或者，移动管理网元2对用于UE请求附着或注册的第一类信息进行流量控制，流量控制策略所涉及的门限也可能不使用数量门限(例如门限B)，而是使用速率门限。例如移动管理网元2将所接收的第一类信息(或，用于UE请求附着或注册的第一类信息)的速率与门限E比较，比较方式以及比较之后的处理方式，可参考门限B对应的比较方式以及处理方式等。在本申请的各个实施例中，以数量门限为例来介绍。
其中，如果移动管理网元2处理第一请求信息，则在移动管理网元2向该UE发送第一响应信息前，还可以向用户管理网元请求获得该UE的签约数据，或者请求该UE的位置更新(或者说，请求更新该UE的位置信息)。如果移动管理网元2从用户管理网元获得了该UE的签约数据，或者成功执行UE的位置更新，那么移动管理网元2可以向该UE发送第一响应信息，以指示附着请求信息的接受或注册请求信息的接受。
而在移动管理网元2处理第一请求信息的情况下，如果满足第一事件(或者也可将“满足”第一事件描述为，“属于”第一事件，或者也可以描述为，第一时间发生，本申请并不限定)，则移动管理网元2可能无法从用户管理网元获得该UE的签约数据，或者无法通过用户管理网元执行该UE的位置更新，那么第一响应信息为拒绝响应信息，例如第一响应信息可以称为第二拒绝信息。可选的，在这种情况下，第二拒绝信息还可以包括第一拒绝原因值，第一拒绝原因值可指示UE继续尝试连接，使得UE不必回落到低制式网络。
可选的，第一事件可包括如下一项或多项：事件1，事件2，事件3，或事件4。下面对这几种事件进行介绍。
事件1为，移动管理网元2向用户管理网元发送第二请求信息后未收到响应的事件。其中，第二请求信息可用于请求获取该UE的签约数据，或用于请求进行位置更新。第二请求信息例如为移动管理网元2在接收第一请求信息后向用户管理网元发送的信息，如果未收到来自用户管理网元的响应，因此移动管理网元2可以向UE发送拒绝响应信息。一种可能的情况是，用户管理网元拥塞或故障。
事件2为，移动管理网元2向用户管理网元发送多条第三请求信息后，未收到响应的第三请求信息的数量占所述多条第三请求信息的比例大于或等于第三门限的事件。其中，第三请求信息可用于请求获取UE的签约数据，或用于请求进行位置更新。例如移动管理 网元2可能已从一个或多个UE接收了用于请求附着或注册的信息，移动管理网元2可能也向用户管理网元发送了一条或多条第三请求信息。需注意的是，该第三请求信息用于请求的信息所对应的UE是发送第一请求信息的UE；或者也可能不包括对应于第一请求信息的第三请求信息。
事件3为，移动管理网元2向用户管理网元发送多条第四请求信息，移动管理网元2从用户管理网元收到的第四请求信息的响应中，指示拒绝的响应所对应的第四请求信息占所述多条第四请求信息的比例大于或等于第四门限的事件。其中，移动管理网元2可能已从一个或多个UE接收了用于请求附着或注册的信息，移动管理网元2可能也向用户管理网元发送了一条或多条第四请求信息。移动管理网元在向用户管理网元发送第四请求信息后，如果用户管理网元能够对接收的信息进行处理，则用户管理网元应该向移动管理网元回复第四请求信息的响应，该响应例如包括该UE的签约数据等；而如果用户管理网元无法处理，例如用户管理网元出现拥塞等情况，则用户管理网元可能不会向移动管理网元回复第四请求信息的响应，或者，用户管理网元也可能会向移动管理网元回复第四请求信息的响应，该响应例如为拒绝响应，或者说该响应指示拒绝。需注意的是，用于与第四门限进行判别的多条第四请求信息中，可能包括对应于第一请求信息的第四请求信息；或者也可能不包括对应于第一请求信息的第四请求信息。
事件4为，移动管理网元2向用户管理网元发送的用于获取签约数据或用于请求位置更新的信息的数量大于或等于第五门限。如果移动管理网元2向用户管理网元发送的用于获取签约数据或请求位置更新的信息的数量大于或等于第五门限，也即，用户管理网元接收到的用于获取签约数据或请求位置更新的信息已经超出用户管理网元的处理能力。因此在这种情况下，移动管理网元2也可以向UE回复拒绝。
前面介绍了在第一类信息用于请求业务或用于UE请求附着或注册等情况下，对第一类信息的流量控制策略，除此之外，第一类信息还可能请求建立会话，在这种情况下，也可采用相应的流量控制策略对第一类信息进行流量控制。可选的，移动管理网元2可设置门限C，通过门限C对用于请求建立会话的第一类信息进行流量控制。例如第一请求信息用于请求建立会话，那么，如果移动管理网元2所接收的第一类信息(或，用于请求建立会话的第一类信息)的数量小于该门限C，则移动管理网元2可以处理第一请求信息，例如移动管理网元2处理第一请求信息的方式为，移动管理网元2向该UE发送第一响应信息，以指示会话建立成功或失败；而如果移动管理网元2所接收的第一类信息(或，用于请求建立会话的第一类信息)的数量大于或等于该门限C，则移动管理网元2可以忽略第一请求信息。其中，门限C也可以称为第六门限。
或者，移动管理网元2对用于请求建立会话的第一类信息进行流量控制，流量控制策略所涉及的门限也可能不使用数量门限(例如门限C)，而是使用速率门限。例如移动管理网元2将所接收的第一类信息(或，用于请求建立会话的第一类信息)的速率与门限F比较，比较方式以及比较之后的处理方式，可参考门限C对应的比较方式以及处理方式等。在本申请的各个实施例中，以数量门限为例来介绍。
在本申请的各个实施例中，如果某个门限为速率门限，那么与该门限进行比较的第一类信息的速率，例如为一个第一类信息的速率，或者是多个第一类信息的平均速率。例如门限A为速率门限，则与该门限A进行比较的第一类信息的速率，例如为一个第一类信息的速率，或者是多个第一类信息的平均速率。
门限A、门限B与门限C，这三者可能是同一门限，或者分别是不同的门限，或者其中任意两个是同一个门限，另一个是不同的门限。其中，如果门限A与门限B是不同的门限，在一些可选的实施方式中，例如门限A也可称为第一门限，门限B也可称为第二门限。可理解为，本申请实施例针对不同类型的信令设置了不同的流量控制策略。例如对于用于请求业务的信息，所采用的流量控制策略为根据第一门限来进行流量控制。又例如，对于用于UE请求附着或注册的信令，所采用的流量控制策略例如为根据第二门限进行流量控制。通过这种方式，可以对不同类型的信令采取差异化的流量控制措施，使得流量控制过程更为符合相应信令的特征，以取得更好的流量控制效果。
可选的，在本申请的各个实施例中，网元忽略某个信息的一种方式例如为，该网元丢弃该信息，在后文不再多赘述。例如移动管理网元忽略第一请求信息的一种方式为，移动管理网元2丢弃第一请求信息。
根据前文的介绍可知，移动管理网元2在对第一类信息进行流量控制后，可能有一部分信息会被继续处理(或者说可能有一部分信息不会被忽略)，在继续处理的过程中，会涉及到用户管理网元的处理。那么对于用户管理网元来说，就需要处理大量的信息，这些信息的数量很可能会超过用户管理网元的处理能力，可能造成拥塞，甚至可能因为信息数量过多而导致大量的信息被用户管理网元忽略，造成网络处理效率降低，UE的业务长时间得不到恢复。可见，即使移动管理网元2根据流量控制确定继续处理第一类信息，也很可能因为用户管理网元的处理瓶颈而导致一部分信息最终处理失败，这对于网络资源来说也是一种浪费。
鉴于此，本申请实施例提出，第二门限可以根据用户管理网元的能力(或，性能)来设置，或者说，第二门限与用户管理网元的性能相关。通过设置第二门限，可以尽量保证被移动管理网元2根据第二门限所确定的继续处理的第一类信息(例如用于UE请求附着或注册的信息)，能够被用户管理网元成功处理，减小用户管理网元的拥塞情况出现的概率，提高网络处理效率，也使得UE的业务能够尽快恢复。需要注意的是，第二门限根据用户管理网元的性能来设置，这只是一种可选的方案，在其他方案中，第二门限还可以根据其他因素来设置，本申请实施例不做限制。
因为第一门限所对应的信息与第二门限所对应的信息之间有一定的关联。例如，在第一门限所对应的信息被移动管理网元2确定继续处理后，UE可能会再次发送第二门限所对应的信息。例如，第一门限可根据第二门限来设置，使得在第一门限对应的信息被移动管理网元2确定继续处理后，UE所发送的与第二门限对应的信息的数量会小于或等于第二门限，即，尽量保证在第一门限对应的信息被移动管理网元2继续处理后，UE所发送的与第二门限对应的信息也尽量能够被移动管理网元2和用户管理网元继续处理。举例来说，UE在发送用于请求附着或注册的信息之后如果收不到响应，则UE每隔15秒+10秒会重新发送一次用于请求附着或注册的信息。如果在重新发送4次后依然收不到响应，则UE会回落到低制式的网络，在12～20分钟后再尝试返回当前网络。通过本申请实施例的技术方案，可以使得用于请求附着或注册的信息尽量都能够得到移动管理网元2和用户管理网元的处理，减少UE得不到响应的情况，从而也就减小了UE回落到低制式网络的概率。
可选的，第一门限位于第一范围内，第一范围的下限为第二门限的N 1倍，上限为第二门限的N 2倍，N 2大于N 1。例如，移动管理网元2根据流量控制确定继续处理A 1个用于请求 业务的信息，则UE重新发起的用于请求附着或注册的信息也可能有A 1个，A 1例如为第二门限的N 2倍。在本次处理过程中，移动管理网元2根据第二门限，可能会忽略其中的A 2个用于请求附着或注册到核心网的信息，A 2例如为第二门限的(N 2-N 1)倍。但是被忽略之后UE会再次尝试发送用于请求附着或注册的信息，举例来说，UE可以有4次尝试机会，如果4次都不成功才会回落到低制式网络，而将第一门限的取值设置为第二门限的N 1～N 2倍，就能够尽量保证在UE的4次尝试过程中，用于请求附着或注册的信息会被移动管理网元2继续处理，从而减小UE回落到低制式网络的概率。例如，N 1＝1，N 2＝1.2。
可选的，第一门限和/或第二门限可通过协议预定义，或者由移动管理网元2自行设置，或者也可以通过人工方式设置在移动管理网元2中。
可参考图3，为第一门限和第二门限的一种示意图。其中的空白方框表示用于请求业务的第一类信息，画斜线的方框表示用于UE请求附着或注册的第一类信息。对于移动管理网元(例如移动管理网元2)来说可设置第一门限和第二门限，通过设置这两个门限，可以实现对于不同类型的信息分别进行流量控制，并且由于第二门限是根据用户管理网元的性能设置的，因此可以使得被移动管理网元2根据流量控制确定继续处理的用于UE请求附着或注册的信息能够得到用户管理网元的成功处理。
另外，图3是以第一门限大于第二门限为例，在实际应用中不限于此，例如第一门限也可能小于或等于第二门限。
在本申请实施例中，移动管理网元2可对第一类信息进行流量控制，第一类信息可以为原本应由移动管理网元1处理的信息。该方法可以使得原本接入移动管理网元2的用户的信息能够得到处理，减小对用户的影响，业务能够得到保障。
在下面的介绍过程中，以第一请求信息用于请求业务、或用于UE请求附着或注册为例。首先介绍将图2所示的实施例提供的方案应用于4G系统的情况，请参考图4，为该实施例的流程图。在图4所示的实施例中，以移动管理网元是MME、接入网网元是eNB为例。该方法可以包括以下步骤：
S401、UE发送请求信息A。该请求信息A可以参考图2所示的实施例中的第一请求信息的描述，因此UE发送请求信息A的方式也可参考图2所示的实施例中的S201。
例如请求信息A用于请求业务，可将请求信息A所请求的业务称为第一业务。可选的，请求信息A为service request，或者也可能是其他信息。
S402、MME2向UE发送第一拒绝信息。
例如，MME2通过eNB将第一拒绝信息发送给UE。
第一拒绝信息可以为服务拒绝(service reject)。可选的，service reject携带拒绝原因值#10，#10指示隐式去附着(implicitly detached)。
本申请实施例以请求信息A属于第一类信息为例。其中，MME2可根据请求信息A所包括的第一信息确定请求信息A属于第一类信息。可选的，第一信息可包括MME码。以请求信息A是service request为例。MME2接收该service request后，可以从该service request中获取该UE的系统架构演进临时移动用户标识(SAE-temporary mobile subscriber identity，S-TMSI)信元，其中的SAE为系统架构演进(system architecture evolution)。S-TMSI信元就包括MMEC和移动管理实体临时移动用户标识(MME-temporary mobile subscriber identity，M-TMSI)。关于MME2如何根据第一信息确定请求信息A属于第一类信息，可参考图2所示的实施例中的S202。
MME2如果确定请求信息A属于第一类信息，则可根据图2所示的实施例介绍的门限A对请求信息A进行流量控制。关于MME2的流量控制方式可参考图2所示的实施例中的S203。其中，在流量控制后MME2对请求信息A可能有不同的处理方式，S402是以MME2不忽略请求信息A为例。
S403、UE发送请求信息B。该请求信息B可以参考图2所示的实施例中的第一请求信息的描述，因此UE发送请求信息B的方式也可参考图2所示的实施例中的S201。
例如请求信息B用于该UE请求附着(attach)到MME2，例如请求信息B为附着请求(attach request)。以请求信息B是attach request为例。移动管理网元B接收该attach request时，可以从该attach request中获取该UE的全局唯一临时UE标识(globally unique temporary UE identity，GUTI)信元，GUTI信元就包括GUMMEI和M-TMSI。或者，第一信息可包括MMEC。以请求信息B是attach request为例，MMEC可包括在GUMMEI中。另外，关于MME2如何根据第一信息确定请求信息A属于第一类信息，可参考图2所示的实施例中的S202。
MME2如果确定请求信息B属于第一类信息，则可根据图2所示的实施例介绍的门限B对请求信息B进行流量控制。关于MME2的流量控制方式也可参考图2所示的实施例的S203。其中，在流量控制后MME2对请求信息B可能有不同的处理方式，S404是以MME2不忽略请求信息B为例。
S404、MME2从HSS获取该UE的签约数据。
S405、MME2向该UE发送附着成功消息。
例如，MME2向eNB发送该附着成功消息，eNB可将该附着成功消息发送给该UE，因此该UE可以从eNB接收该附着成功消息。
接着，UE可以继续请求创建数据PDN连接，或创建数据PDN连接和语音PDN连接等，对于后续操作不做限制。
图4所示的方法的有益效果可以参考图2所示的实施例的描述，此处不再赘述。
下面介绍将图2所示的实施例的方案应用于5G系统的情况。请参考图5，为该情况的流程图。在图5所示的实施例中，以移动管理网元是AMF、接入网网元是gNB为例。结合图2所示的方法，该方法可以包括以下步骤：
S501、UE发送请求信息C。
该请求信息C可以参考图2所示的实施例中的第一请求信息的描述，因此UE发送请求信息C的方式也可参考图2所示的实施例中的S201的描述。
例如请求信息C用于请求业务，可将请求信息A所请求的业务称为第一业务。可选的，请求信息C为service request，或者也可能是其他信息。
S502、AMF2向UE发送第一拒绝信息。
例如，AMF2向gNB发送第一拒绝信息，gNB再将第一拒绝信息发送给UE。第一拒绝信息可以为service reject。可选的，该service reject可携带原因值#10。
本申请实施例以请求信息A属于第一类信息为例。其中，AMF2可根据请求信息A所包括的第一信息确定请求信息A属于第一类信息。可选的，第一信息可包括AMF set ID和AMF pointer。以请求信息C是service request为例。AMF2接收该service request时，可以从该service request中获取该UE的5G-S-TMSI信元，5G-S-TMSI信元包括AMF set ID、AMF pointer和5G-TMSI。关于AMF2如何根据第一信息确定请求信息C属于第一类信息， 可参考图2所示的实施例的S202的描述。
AMF2如果确定请求信息C属于第一类信息，则可根据图2所示的实施例介绍的门限A对请求信息C进行流量控制。关于AMF2的流量控制方式也可参考图2所示的实施例的S203。其中，在流量控制后AMF2对请求信息C可能有不同的处理方式，S502是以AMF2不忽略请求信息C为例。
S503、UE发送请求信息D。
该请求信息D可以参考图2所示的实施例中的第一请求信息的描述，因此UE发送请求信息D的方式也可参考图2所示的实施例中的S201。
例如请求信息D用于该UE请求注册到AMF2，例如请求信息D为registration request。
S504、AMF2从UDM获取该UE的签约数据。
本申请实施例以请求信息D属于第一类信息为例。其中，AMF2可根据请求信息D所包括的第一信息确定请求信息D属于第一类信息。可选的，第一信息可包括GUAMI。以请求信息D是registration request为例。AMF2接收该registration request时，可以从该registration request中获取该UE的5G-GUTI信元，5G-GUTI信元包括GUAMI和5G-TMSI。或者，第一信息可包括AMF set ID和AMF pointer。以请求信息D是registration request为例，GUAMI又包括AMF set ID和AMF pointer可包括在GUAMI中。另外，关于AMF2如何根据第一信息确定请求信息D属于第一类信息，可参考图2所示的实施例的S202的描述。
AMF2如果确定请求信息D属于第一类信息，则可根据图2所示的实施例介绍的门限B对请求信息D进行流量控制。关于AMF2的流量控制方式也可参考图2所示的实施例的S203。其中，在流量控制后AMF2对请求信息D可能有不同的处理方式，S504是以AMF2不忽略请求信息D为例。
S505、AMF2向该UE发送注册成功消息。例如，AMF2通过gNB向UE发送该注册成功消息。
接着，UE可以继续请求创建数据PDU会话和/或语音PDU会话等，对于后续操作不做限制。
图5所示的方法的有益效果可以参考图2所示的实施例的描述，此处不再赘述。
根据前文可知，第一类信息可能包括多种类型的信息，例如包括用于请求业务的信息，还可能包括用于UE请求附着或注册的信息等。在service request和attach request/registration request信息超时无响应后，UE的行为是不同的，可参考表1。
表1
Figure PCTCN2022144283-appb-000001
Figure PCTCN2022144283-appb-000002
可见，无论是4G系统还是5G系统，在attach request/registration request信息超时后，UE经过4次重试，若仍未收到响应，就会回落到低制式网络，在一段时间后才会再次返回并重新接入；而在service request信息超时后，UE会留在原制式网络中反复重试，不会回落到低制式网络。应理解的是，本申请中表1展示的是多种情况中的一种情况，本申请并不限定。
因此如果对于不同类型的信息都采用同样的流量控制策略，则控制粒度较粗，无法达到较好的控制效果，很可能导致UE回落到低制式的网络，使得业务恢复的时间过长。为此，本申请实施例提供一种通信方法，在该方法中，可以对不同类型的信息采用不同的流量控制策略，以达到更好的控制效果。例如本申请实施例应用于4G系统，则该移动管理网元可以为MME；或者本申请实施例应用于5G系统，则该移动管理网元可以为AMF。结合图2所示的方法，请参考图6，该图6中的移动管理网元2可以参考图2所示的实施例中的移动管理网元2的描述，该方法可以包括以下步骤：
S601、UE发送请求信息E。
相应的，移动管理网元2接收请求信息E。
请求信息E例如为图2所示的实施例中的第一请求信息。请求信息E可用于请求业务，例如请求第一业务。请求信息E例如为service request。UE向移动管理网元发送请求信息E的方式，可参考图2所示的实施例的S201中对于UE向移动管理网元发送第一请求信息的介绍。
S602、如果移动管理网元2接收的用于请求业务的信息的数量小于第一门限，移动管理网元2向该UE发送第一拒绝信息。相应的，UE从移动管理网元2接收第一拒绝信息。
其中，第一拒绝信息可用于拒绝第一请求信息所请求的业务。可选的，对于第一拒绝信息的介绍可参考图4所示的实施例中的S402的描述。
如果移动管理网元2接收到超过该移动管理网元2处理能力的数量的信令，则移动管理网元2可以启动流量控制策略。例如一种流量控制策略为，根据第一门限对用于请求业务的信息进行流量控制。关于该流量控制策略以及则第一门限等内容，可参考图2所示的实施例的描述。
例如，移动管理网元2可以先确定请求信息E属于第一类信息，然后再根据第一门限对请求信息E进行流量控制。关于移动管理网元2确定请求信息E是否属于第一类信息的方式可参考图2所示的实施例的S202的描述，关于移动管理网元2根据第一门限进行流量控制的策略、以及流量控制后对于请求信息E的不同处理方式等，可参考图2所示的实施例的S203的描述。
S603、UE发送请求信息F。
UE向移动管理网元2发送请求信息F的方式，可参考图2所示的实施例中对于UE向移动管理网元发送第一请求信息的介绍。
例如本申请实施例应用于4G系统，则请求信息F可用于该UE请求附着，例如请求信息F为attach request；或者，本申请实施例应用于5G系统，则请求信息F可用于该UE请求注册，例如请求信息F为registration request。
该请求信息F可以参考图2所示的实施例中用于UE请求附着或注册的第一请求信息的描述。
也就是说，通过S602，UE接收了第一拒绝信息，那么UE认为之前在核心网的附着(或注册)失败，因此UE可以删除本地的会话信息，并发送请求信息F以请求附着或注册到移动管理网元2。
S604、如果移动管理网元2接收的用于请求附着或注册的信息的数量小于第二门限，移动管理网元2从用户管理网元获取该UE的签约数据。可以理解的，如果移动管理网元2接收的用于请求附着或注册的信息的数量小于第二门限，移动管理网元2可从用户管理网元获取该UE的签约数据或请求该UE的位置更新等，本申请实施例主要以获取UE的签约数据为例。如果将本申请实施例的技术方案应用于4G系统，则该用户管理网元例如为HSS；如果将本申请实施例的技术方案应用于5G系统，则该用户管理网元例如为UDM。
可理解为，因请求信息F是用于请求附着或注册到核心网的信息，对于此类信息，移动管理网元2所采用的流量控制策略为，根据第二门限进行流量控制。第二门限可以参考图2所示的实施例中第二门限的描述。另外，移动管理网元2可以先确定请求信息F属于第一类信息，然后再根据第二门限对请求信息F进行流量控制。关于移动管理网元2确定请求信息F是否属于第一类信息的方式可参考图2所示的实施例的S202的描述，关于移动管理网元2根据第二门限进行流量控制的策略、以及流量控制后对于请求信息F的不同处理方式等，可参考图2所示的实施例的S203的描述。
另外，对于第一门限和第二门限的设置方式等，也可参考图2所示的实施例的介绍。
S605、移动管理网元2向UE发送第一响应信息。例如，移动管理网元2可通过接入网网元向UE发送第一响应信息。
在获得该UE的签约数据后，移动管理网元2可以向该UE发送第一响应信息，例如，也可将第一响应信息称为第一接受信息。其中，如果第一请求信息用于该UE请求附着(或者说，第一请求信息包括该UE的附着请求信息)，则第一接受信息可指示该UE附着成功，或者，第一接受信息可指示所述附着请求信息的接受；而如果第一请求信息用于该UE请求注册(或者说，第一请求信息包括该UE的注册请求信息)，则第一接受信息可指示该UE注册成功，或者，第一接受信息可指示所述注册请求信息的接受。
根据本申请实施例的技术方案，对于超过第一门限的用于请求业务的信息，移动管理网元2可以将其忽略。而对于用于请求业务的信息，即使被忽略，UE也会继续停留在当前的网络反复尝试，而不会回落到低制式网络。对于在第一门限之内的用于请求业务的信息，移动管理网元2可继续处理，从而UE可以继续发送用于请求附着或注册的信息。而对于这些用于UE请求附着或注册的信息，移动管理网元2按照第二门限也会对其继续处理，而这些信息也能够得到用户管理网元的成功处理。因此，通过本申请实施例的技术方案，可以实现对于不同类型的信息分别进行流量控制，细化流量控制粒度，减小UE回落到低制式网络的概率，提高业务恢复的效率。另外，本申请实施例可以不区分第一类信息，对所有信息都可进行流量控制以在整体上减小核心网的压力；或者也可以只是对第一类信息进行流量控制，第一类信息例如为容灾信息，以减小对原本接入移动管理网元2的用户的冲击，保证这些用户的业务连续性。
在移动网络中，HSS/UDM是信令最为集中化的网元之一，是一个GUL(全球移动通信系统(global system for mobile communications，GSM)/通用移动通信系统(universal mobile telecommunications system，UMTS)/LTE)/5G/IMS三域同时交汇的网元。在网络出现信令冲击时，特别是站点故障倒换产生信令浪涌时，HSS/UDM往往最先成为信令处理的瓶 颈网元。当HSS/UDM过载或者通往HSS/UDM的链路拥塞时，MME/AMF感知到发往HSS/UDM的大量信息失败，会启动流量控制，通过携带特殊原因值来拒绝UE的attach request/registration request，以控制发往HSS/UDM的信令信息数量，减少对HSS/UDM的信令冲击，对HSS/UDM进行保护。可参考表2，为特殊原因值与UE行为之间的关系。
表2
Figure PCTCN2022144283-appb-000003
根据表2可知，无论是4G还是5G UE，如果attach request/registration request信息被拒绝，目前MME/AMF一般回复的拒绝原因值都是#111。在拒绝原因值为#111时，指示的是“协议错误(protocol error)，不明确(unspecified)”，UE如果收到拒绝原因值#111，则会回落到低制式网络，在几十分钟后才会再次返回并重新接入，这导致UE的业务长时间得不到恢复。
鉴于此，本申请实施例提供一种通信方法，请参考图7，该方法包括以下步骤：
S701、UE发送第一请求信息。
该第一请求信息可以参考图2中的第一请求信息的描述，其中，该第一请求信息例如为图2中用于该UE请求附着或注册的第一请求信息。该步骤可以参考图2中的步骤201的描述。
S702、移动管理网元2确定是否满足第一事件。
其中，如果不满足第一事件，则移动管理网元2可以处理第一请求信息，例如移动管理网元2可以向用户管理网元请求该UE的签约数据和/或请求位置更新等；而如果满足第一事件，则移动管理网元2可以向UE回复拒绝，以拒绝处理第一请求信息。关于第一事件，可参考图2所示的实施例的S203中对于第一事件的描述。
S703、如果满足第一事件，移动管理网元2向UE发送第一响应信息。例如，移动管理网元2向接入网网元发送第一响应信息，接入网网元再将第一响应信息发送给UE，则UE可以从接入网网元接收第一响应信息。
第一响应信息可包括第一拒绝原因值。可选的，第一拒绝原因值例如为#22，或者也可以是其他取值。第一拒绝原因值#22，也可以应用于图2所示的实施例，或者图2所示的实施例与图7所示的实施例所使用的第一拒绝原因值不同。请参考表3，为拒绝原因值#22与UE行为之间的关系。
表3
Figure PCTCN2022144283-appb-000004
根据表3可知，如果attach request或registration request被拒绝，且拒绝原因值是“#22拥塞(congestion)”，则UE可以每隔10秒进行重试，连续重试4次后若仍然失败，才会回落到低制式网络，在12～20分钟后再次返回高制式网络，并重新在高制式网络内接入核心网。其中，如果UE回落的低制式网络为2G网络或3G网络，则UE返回的高制式网络例如为4G网络；如果UE回落的低制式网络为4G网络，则UE返回的高制式网络例如为5G网络。
本申请实施例由于采用第一拒绝原因值，可以降低UE由于流量控制或网络拥塞等原因而回落到低制式网络的概率，将UE尽量留在当前网络，减少业务恢复的时间。
在站点故障倒换时，故障站点的UE在其他站点重新接入网络。在大量移动性信令(例如service request/attach request/registration request)之后，UE可能会向网络发送大量的会话激活信息(例如用于请求建立会话的信息)，这会对会话管理网元(例如SGW或SMF等)产生冲击，导致会话管理网元启动流量控制，对超出自身处理能力的会话激活请求进行拒绝处理。
例如网络中的UE在网络完成数据域接入和语音域接入后，才真正接入网络。UE在4G网络具有2种语音方式：电路域回落(circuit switched fallback，CSFB)和IMS。UE在5G网络具有1种语音方式：IMS，其中IMS语音方式要求UE激活IMS语音会话。4G UE和5G UE在不同的会话激活请求信息被拒绝后，各自的行为是不同的，可参考表4。
表4
Figure PCTCN2022144283-appb-000005
在4G网络中，UE可以可发起attach request，而在附着过程中可同时请求建立(或，激活)数据PDN连接。如果UE发起的数据PDN连接建立(或者说，激活)失败，则UE附着失败，那么UE会重新尝试附着4次，如果4次尝试均失败，UE会回落到低制式网络(例如2G网络或3G网络)并重新发起附着。那么前期的attach request的处理过程带来网络延时，且UE长时间无法返回4G网络，延长了UE的业务回复时间。在5G网络中，UE可以向核心网请求建立IMS语音PDU会话，如果UE建立IMS语音PDU会话失败，则UE会回落到4G网络重新发起附着。这会导致前期的registration request的处理过程被浪费，且UE长时间无法返回5G网络，延长了UE的业务回复时间。
鉴于此，本申请实施例提供一种通信方法。在该方法中，UE可以对不同类型的会话所对应的信息进行差异化流量控制，以减小UE回落到低制式网络的概率。请参考图8，若图8所示的实施例应用于4G系统，则该移动管理网元为MME，该会话管理网元为SGW，或者如果在SGW的控制面和用户面分离(CUPS)的场景下，则该会话管理网元为控制面服务网关(serving gateway for control plane，SGW-C)；若图8所示的实施例应用于5G系统，则该移动管理网元为AMF，该会话管理网元为SMF。该图8所示的方法可以包括以下步骤：
S801、UE向会话管理网元发送第一请求信息。例如，UE的第一请求信息可通过接入网网元和移动管理网元传递给会话管理网元。
第一请求信息可请求建立会话。
例如本申请实施例应用于4G系统，则第一请求信息例如用于请求建立数据PDN连接，或者用于请求建立语音PDN连接。或者本申请实施例应用于5G系统，则第一请求信息例如用于请求建立数据PDU会话，或者用于请求建立语音PDU会话。
S802、如果第一请求信息所请求建立的会话为第一类型的会话，会话管理网元根据第一类型的会话对应的流量控制策略，对第一请求信息进行处理。
该步骤的一种可能的替代方式，会话管理网元可以根据用于请求建立第一类型的会话的请求信息对应的流量控制策略，对第一请求信息进行处理。
第一类型例如为数据类型或语音类型。以本申请实施例应用于4G系统为例，第一请求信息例如用于请求建立语音PDN连接，即，第一类型为语音类型。在4G系统中，如果UE建立语音PDN连接失败，则UE会继续在4G网络采用CSFB方式进行语音业务，而不会回落到低制式的网络，因此会话管理网元可以对请求建立语音PDN连接的请求信息(例如第一请求信息)进行流量控制，即使第一请求信息因为流量控制而被拒绝，UE也不会回落低制式网络，能够在一定程度上继续保证UE的业务恢复时间。
会话管理网元根据第一类型的会话对应的流量控制策略对第一请求信息进行处理，例如一种方式为，会话管理网元内设置有第七门限，如果会话管理网元所接收的用于请求建立第一类型的会话的信息的数量小于第七门限，则会话管理网元对第一请求信息继续处理；而如果SGW所接收的用于请求建立第一类型的会话的信息的数量大于或等于第七门限，则会话管理网元可以向UE发送拒绝信息。
可选的，会话管理网元的如上处理方式，可以只是针对单个UE，例如对于某个UE发来的第一类型的请求信息可以执行流量控制，这样可以实现对单个UE的差异化控制；或者，会话管理网元的如上处理方式也可以针对多个UE，例如会话管理网元并不关注信息来自哪个UE，只要是第一类型的请求信息(或者说，4G网络中用于请求建立语音PDN连接的信息，或5G网络中用于请求建立数据PDU会话的信息)，会话管理网元就执行流量控制，这样可以在较大程度上避免更多UE回落到低制式网络，能够保证大量UE的业务恢复时间。
根据图2所示的实施例可知，移动管理网元也可以对用于请求建立第一类型的会话的信息进行流量控制。也就是说，可由不同的网元对用于请求建立第一类型的会话的信息进行流量控制，例如移动管理网元和/或会话管理网元都可以对用于请求建立第一类型的会话的信息进行流量控制，其中，移动管理网元与会话管理网元在进行流量控制时所使用的流量控制策略(例如门限)可以相同，也可以不同，由此可以进一步减小信令对后端网元的 冲击，提高网络可靠性。
下面分别以4G系统和5G系统为例，来介绍图8所示的实施例提供的方案。首先介绍将图8所示的实施例的方案应用于4G系统的情况。请参考图9，为该情况的流程图。在图9所示的实施例中，以会话管理网元是SGW、移动管理网元是MME为例。该方法可以包括以下步骤：
S901、UE请求建立语音PDN连接。
在S901中，UE可以向MME发送第一PDN激活请求。
例如，UE的第一PDN激活请求可经过eNB到达MME。第一PDN激活请求例如为PDN连接请求(PDN connectivity request)，第一PDN激活请求可用于请求建立语音PDN连接。
在S901中，MME在接收第一PDN激活请求后，还可以向SGW发送会话建立请求。
S902、SGW对第一PDN激活请求进行流量控制。
例如，SGW可以从来自MME的会话建立请求中获取接入点名称(access point name，APN)，根据该APN可以确定第一PDN激活请求是用于请求建立语音PDN连接。第一PDN激活请求可视为是图10所示的实施例所述的用于请求建立第一类型的会话的第一请求信息。
关于SGW对第一PDN激活请求的流量控制方式，可参考图8所示的实施例的介绍。
S903、SGW向UE发送拒绝信息。
S903以流量控制结果是SGW向UE发送拒绝信息为例进行描述。例如，SGW向MME发送的拒绝信息为第三拒绝信息，第三拒绝信息例如为会话建立响应，会话建立响应可携带拒绝原因值A，例如拒绝原因值A为#68，可指示服务不支持(service not supported)；接着，MME可以向UE发送第四拒绝信息，第四拒绝信息例如为PDN连接拒绝(PDN connectivity reject)，PDN connectivity reject可携带拒绝原因值B，拒绝原因值B例如为#32，可指示服务选择不支持(service option not supported)。
其中，如果S902中的流量控制结果为SGW对第一PDN激活请求继续处理，则SGW可以向MME发送建立会话响应(create session response)，相应的，MME再向UE发送PDN连接接受(PDN connectivity accept)等信息。
S904、UE进行持续重试。
例如，UE继续在当前网络请求建立语音PDN连接，而并不会回落到低制式的网络。即，相当于重复执行S901。
在4G系统中，如果UE建立语音PDN连接失败，则UE会继续在4G网络采用CSFB方式进行语音业务，而不会回落到低制式的网络。因此本申请实施例中，会话管理网元可以对请求建立语音PDN连接的请求信息(例如第一PDN激活请求)进行流量控制，即使第一PDN激活请求因为流量控制而被拒绝处理，UE也不会回落低制式网络，能够在一定程度上继续保证UE的业务恢复时间。而在4G系统中，如果UE建立数据PDN连接失败，则UE可以再尝试4次，如果依然失败，UE会回落到低制式网络(例如2G网络或3G网络)。因此，对于用于请求建立数据PDN连接的信息，会话管理网元可以降低流量控制的概率，例如会话管理网元可以继续处理用于请求建立数据PDN连接的信息，以减少对此类信息拒绝处理的概率，也就减小了UE回落到低制式网络的概率。
请参考图10，图10为一种将图8所示的实施例的方案应用于5G系统的方法。该方法 中以会话管理网元是SMF、移动管理网元是AMF为例进行描述。该方法可以包括以下步骤：
S1001、UE向AMF发送注册请求。
相应的，AMF接收该注册请求。例如该UE通过gNB向AMF发送注册请求。
S1002、UE请求建立数据PDU会话。
在S1002中，UE可以向AMF发送第一PDU会话建立请求。例如，UE的第一PDU会话建立请求可经过gNB到达AMF。第一PDU会话建立请求例如为PDU session establishment request，第一PDU会话建立请求可用于请求建立数据PDU会话。
在S1002中，AMF接收第一PDU会话建立请求后，还可以向SMF发送会话管理上下文请求，该会话管理上下文请求例如为SMF服务PDU会话建立会话管理上下文请求(Nsmf_PDUSession_CreateSMContext request)。例如将该会话管理上下文请求称为第一会话管理上下文请求。
S1003、SMF对第一PDU会话建立请求进行流量控制。
第一PDU会话建立请求是用于请求建立数据PDU会话，第一PDU会话建立请求可视为是图10所示的实施例所述的用于请求建立第一类型的会话的第一请求信息。根据图10所示的实施例可知，SMF可以对用于请求建立数据PDU会话的信息进行流量控制，这样既不会使得UE回落到低制式的网络，也能有效控制SMF所处理的信息的数量。关于SMF对第一PDU会话建立请求的流量控制方式，可参考图8所示的实施例的介绍。其中，图9所示的实施例所涉及的第七门限，与图10所示的实施例所涉及的第七门限，可以相等，也可以不相等。
S1004、SMF向UE发送拒绝信息。
该步骤以流量控制结果为SMF向UE发送拒绝信息为例。例如，SMF向AMF发送的拒绝信息为第五拒绝信息，第五拒绝信息例如为SMF服务PDU会话建立会话管理上下文响应(Nsmf_PDUSession_CreateSMContext response)。可选的，SMF服务PDU会话建立会话管理上下文响应可携带拒绝原因值C，因SMF拒绝该UE是因为流量控制，说明SMF需要处理的信息量比较大，无法再处理第一PDU会话建立请求，因此该拒绝原因值C例如为#26，#26可以用于指示资源不足(insufficient resources)，这里的资源例如为SMF的处理资源。
AMF接收第五拒绝信息后，可以向UE发送第六拒绝信息，第六拒绝信息例如为PDU会话建立拒绝(PDU session establishment reject)。如果第五拒绝信息携带了拒绝原因值C，则可选的，PDU session establishment reject也可携带拒绝原因值C。
其中，如果S1003中的流量控制结果为SMF对第一PDU会话建立请求继续处理，则SMF可以向UE发送PDU会话建立响应(PDU session establishment response)等信息。
S1005、UE进行持续重试。
例如，UE继续在当前网络请求建立数据PDU会话，这相当于回到S1002开始重复执行。
该步骤的目的是UE不回落到低制式的网络。
S1006、UE请求建立语音PDU会话。
在S1006中，UE可以向AMF发送第二PDU会话建立请求。
例如，UE可通过gNB向AMF发送第二PDU会话建立请求。第二PDU会话建立请 求例如为PDU session establishment request，第二PDU会话建立请求可用于请求建立语音PDU会话。例如，UE可以在数据PDU会话建立成功后再执行S1206，或者即使数据PDU会话未建立成功，UE也可以执行S1206。
在S1006中，AMF接收第二PDU会话建立请求后，还可以向SMF发送会话管理上下文请求，该会话管理上下文请求例如为Nsmf_PDUSession_CreateSMContext response。例如将S1006中的会话管理上下文请求称为第二会话管理上下文请求。
S1007、SMF向UPF发送N4会话建立请求。相应的，UPF向SMF发送N4会话建立响应。
第二PDU会话建立请求是用于请求建立语音PDU会话，根据图8所示的实施例可知，SMF可以继续处理用于请求建立语音PDU会话的信息，以避免UE回落到低制式网络。例如，SMF可以向UPF发送N4会话建立请求，以请求建立N4会话，该N4会话建立请求例如为N4会话建立请求(N4session establishment request)。UPF接收N4会话建立请求后，可以向SMF发送N4会话建立响应，该N4会话建立响应例如为N4会话建立响应(N4session establishment response)。SMF接收N4会话建立响应后，可以向AMF发送SMF服务PDU会话建立会话管理上下文响应。相应的，AMF再向UE发送PDU会话建立接受/拒绝(PDU session establishment accept/reject)，以指示语音PDU会话建立成功或失败。对于SMF与AMF之间的交互，图10没有示出。
在5G系统中，如果UE建立数据PDU会话失败，则UE会继续驻留在5G网络反复尝试，而不会回落到低制式的网络(例如4G网络)。因此本申请实施例中，会话管理网元可以对请求建立数据PDU会话的请求信息(例如第一PDU会话建立请求)进行流量控制，即使第一PDU会话建立请求因为流量控制而被拒绝处理，UE也不会回落低制式网络，能够在一定程度上继续保证UE的业务恢复时间。而在5G系统中，如果UE建立语音PDU会话失败，则UE会回落到4G网络。因此，对于用于请求建立语音PDU会话的信息，会话管理网元可以降低流量控制的概率，例如会话管理网元可以继续处理用于请求建立语音PDU会话的信息，以减少对此类信息拒绝处理的概率，也就减小了UE回落到低制式网络的概率。
综上，本申请实施例考虑了UE对于不同类型的信息的不同响应方式，通过对不同类型的信息进行差异化流量控制，减小了UE回落到低制式网络的概率，提高了UE的业务恢复效率。
图11给出了本申请实施例提供的一种通信装置的结构示意图。所述通信装置1100可以是图2所示的实施例、图4所示的实施例至图10所示的实施例中的任一个实施例所述的移动管理网元(例如移动管理网元2)或该移动管理网元的电路系统，用于实现上述方法实施例中对应于移动管理网元的方法。或者，所述通信装置1100可以是图8所示的实施例至图10所示的实施例所述的会话管理网元或该会话管理网元的电路系统，用于实现上述方法实施例中对应于会话管理网元的方法。具体的功能可以参见上述方法实施例中的说明。其中，例如一种电路系统为芯片系统。
该通信装置1100包括至少一个处理器1101。处理器1101可以用于装置的内部处理，实现一定的控制处理功能。可选地，处理器1101包括指令。可选地，处理器1101可以存储数据。可选地，不同的处理器可以是独立的器件，可以位于不同物理位置，可以位于不同的集成电路上。可选地，不同的处理器可以集成在一个或多个处理器中，例如，集成在 一个或多个集成电路上。
可选地，通信装置1100包括一个或多个存储器1103，用以存储指令。可选地，所述存储器1103中还可以存储有数据。所述处理器和存储器可以单独设置，也可以集成在一起。
可选地，通信装置1100包括通信线路1102，以及至少一个通信接口1104。其中，因为存储器1103、通信线路1102以及通信接口1104均为可选项，因此在图11中均以虚线表示。
可选地，通信装置1100还可以包括收发器和/或天线。其中，收发器可以用于向其他装置发送信息或从其他装置接收信息。所述收发器可以称为收发机、收发电路、输入输出接口等，用于通过天线实现通信装置1100的收发功能。可选地，收发器包括发射机(transmitter)和接收机(receiver)。示例性地，发射机可以用于将基带信号生成射频(radio frequency)信号，接收机可以用于将射频信号转换为基带信号。
处理器1101可以包括一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路1102可包括一通路，在上述组件之间传送信息。
通信接口1104，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)，有线接入网等。
存储器1103可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器1103可以是独立存在，通过通信线路1102与处理器1101相连接。或者，存储器1103也可以和处理器1101集成在一起。
其中，存储器1103用于存储执行本申请方案的计算机执行指令，并由处理器1101来控制执行。处理器1101用于执行存储器1103中存储的计算机执行指令，从而实现本申请上述实施例提供的通信方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器1101可以包括一个或多个CPU，例如图11中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信装置1100可以包括多个处理器，例如图11中的处理器1101和处理器1108。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
当图11所示的装置为芯片时，例如是移动管理网元的芯片，或会话管理网元的芯片，则该芯片包括处理器1101(还可以包括处理器1108)、通信线路1102、存储器1103和通 信接口1104。具体地，通信接口1104可以是输入接口、管脚或电路等。存储器1103可以是寄存器、缓存等。处理器1101和处理器1108可以是一个通用的CPU，微处理器，ASIC，或一个或多个用于控制上述任一实施例的通信方法的程序执行的集成电路。
本申请实施例可以根据上述方法示例对装置进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。比如，在采用对应各个功能划分各个功能模块的情况下，图12示出了一种装置示意图，该装置1200可以是上述各个方法实施例中所涉及的移动管理网元或会话管理网元，或者为移动管理网元中的芯片或会话管理网元中的芯片。该装置1200包括发送单元1201、处理单元1202和接收单元1203。
应理解，该装置1200可以用于实现本申请实施例的方法中由移动管理网元或会话管理网元执行的步骤，相关特征可以参照上文的各个实施例，此处不再赘述。
可选的，图12中的发送单元1201、接收单元1203以及处理单元1202的功能/实现过程可以通过图11中的处理器1101调用存储器1103中存储的计算机执行指令来实现。或者，图12中的处理单元1202的功能/实现过程可以通过图11中的处理器1101调用存储器1103中存储的计算机执行指令来实现，图12中的发送单元1201和接收单元1203的功能/实现过程可以通过图11中的通信接口1104来实现。
可选的，当该装置1200是芯片或电路时，则发送单元1201和接收单元1203的功能/实现过程还可以通过管脚或电路等来实现。
本申请还提供一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序或指令，当该计算机程序或指令被运行时，实现前述方法实施例中由会话管理网元或移动管理网元所执行的方法。这样，上述实施例中所述功能可以软件功能单元的形式实现并作为独立的产品销售或使用。基于这样的理解，本申请的技术方案本质上或者说对做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行前述任一方法实施例中由会话管理网元或移动管理网元所执行的方法。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器用于执行上述任一方法实施例所涉及的移动管理网元或会话管理网元所执行的方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、 数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器(digital signal processor，DSP)，专用集成电路(application specific integrated circuit，ASIC)，现场可编程门阵列(field-programmable gate array，FPGA)，或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于RAM、闪存、ROM、可擦除可编程只读存储器(erasable programmable read-only memory，EPROM)、EEPROM、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中，ASIC可以设置于终端设备中。可选地，处理器和存储媒介也可以设置于终端设备中的不同的部件中。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本申请实施例进行了描述，显而易见的，在不脱离本申请实施例的范围的情况下，可对其进行各种修改和组合。相应地，本申请实施例和附图仅仅是所附权利要求所界定的本申请实施例的示例性说明，且视为已覆盖本申请实施例范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的范围。这样，倘若本申请实施例的这些修改和变型属于本申请实施例权利要求及其等同技术的范围之内，则本申请实施例也意图包含这些改动和变型在内。

Claims (26)

  1. 一种通信方法，其特征在于，应用于移动管理网元，所述方法包括：
    接收来自终端设备的第一请求信息，所述第一请求信息用于请求第一业务，或为所述终端设备的附着请求信息或注册请求信息；
    当所述第一请求信息属于第一类信息，所述第一类信息的原接收网元为故障的移动管理网元；
    根据对所述第一类信息的流量控制策略对所述第一请求信息进行处理。
  2. 根据权利要求1所述的方法，其特征在于，
    当所述第一请求信息包括的第一信息所指示的原接收网元，与所述移动管理网元不同，确定所述第一请求信息属于所述第一类信息。
  3. 根据权利要求2所述的方法，其特征在于，若所述第一请求信息用于请求所述第一业务，所述第一信息包括移动性管理实体码MMEC，或，包括接入与移动性管理功能AMF集合标识ID信息和AMF指针。
  4. 根据权利要求3所述的方法，其特征在于，若所述第一请求信息用于请求所述第一业务，所述根据对所述第一类信息的流量控制策略对所述第一请求信息进行处理，包括：
    如果属于所述第一类信息的信息数量小于第一门限，向所述终端设备发送第一拒绝信息，以拒绝所述第一请求信息所请求的业务；或，
    如果属于所述第一类信息的信息数量大于或等于第一门限，忽略所述第一请求信息。
  5. 根据权利要求2所述的方法，其特征在于，若所述第一请求信息为所述终端设备的附着请求信息或注册请求信息，所述第一信息包括全局唯一移动性管理实体标识GUMMEI，或包括全局唯一访问和移动管理功能标识GUAMI。
  6. 根据权利要求5所述的方法，其特征在于，若所述第一请求信息为所述终端设备的附着请求信息或注册请求信息，根据对所述第一类信息的流量控制策略，对所述第一请求信息进行处理，包括：
    如果属于所述第一类信息的信息数量小于第二门限，向所述终端设备发送第一响应信息，所述第一响应信息为第一接受信息，所述第一接受信息用于指示所述附着请求信息的接受或者所述注册请求信息的接受，或，所述第一响应信息用于指示拒绝处理所述第一请求信息；或，
    如果属于所述第一类信息的信息数量大于或等于第二门限，忽略所述第一请求信息。
  7. 根据权利要求6所述的方法，其特征在于，如果属于所述第一类信息的信息数量小于第二门限，向所述终端设备发送第一响应信息，包括：
    如果属于所述第一类信息的信息数量小于所述第二门限，且属于第一事件，向所述终端设备发送所述第一响应信息，所述第一响应信息用于指示拒绝处理所述第一请求信息。
  8. 根据权利要求7所述的方法，其特征在于，所述第一事件包括：
    向用户管理网元发送第二请求信息后未收到响应，所述第二请求信息用于请求获取所述终端设备的签约数据，或用于请求更新所述终端设备的位置信息。
  9. 根据权利要求7所述的方法，其特征在于，所述第一事件包括：
    向用户管理网元发送多条第三请求信息后，未收到响应的第三请求信息占所述多条第三请求信息的比例大于或等于第三门限，所述第三请求信息用于请求获取所述终端设备的 签约数据，或用于请求更新所述终端设备的位置信息。
  10. 根据权利要求7所述的方法，其特征在于，所述第一事件包括：
    向用户管理网元发送多条第四请求信息；
    所述第四请求信息的响应为拒绝响应的第四请求信息占所述多条第四请求信息的比例大于或等于第四门限；所述第四请求信息用于请求获取所述终端设备的签约数据，或用于请求更新所述终端设备的位置信息。
  11. 根据权利要求7所述的方法，其特征在于，所述第一事件包括：
    向用户管理网元发送的用于获取签约数据的信息的数量大于或等于第五门限。
  12. 根据权利要求6～11任一项所述的方法，其特征在于，若所述第一响应信息用于指示拒绝处理所述第一请求信息，所述第一响应信息包括第一拒绝原因值，所述第一拒绝原因值用于指示所述终端设备继续尝试连接。
  13. 根据权利要求6～12任一项所述的方法，其特征在于，
    所述方法还包括：如果属于所述第一类信息的信息数量小于第二门限，从用户管理网元获得所述终端设备的签约数据；
    向所述终端设备发送第一响应信息，所述第一响应信息为第一接受信息，所述第一接受信息用于指示所述附着请求信息的接受或者所述注册请求信息的接受，包括：在获得所述终端设备的签约数据后，向所述终端设备发送所述第一响应信息，所述第一响应信息为所述第一接受信息，所述第一接受信息用于指示所述附着请求信息的接受或者所述注册请求信息的接受；
    其中，所述第二门限与所述用户管理网元的性能相关。
  14. 根据权利要求8～13任一项所述的方法，其特征在于，所述用户管理网元为归属签约服务器HSS或统一数据管理UDM网元。
  15. 一种通信装置，其特征在于，包括：
    收发单元，用于接收来自终端设备的第一请求信息，所述第一请求信息用于请求第一业务，或为所述终端设备的附着请求信息或注册请求信息；
    处理单元，用于当所述第一请求信息属于第一类信息，根据对所述第一类信息的流量控制策略对所述第一请求信息进行处理，所述第一类信息的原接收网元为故障的移动管理网元。
  16. 根据权利要求15所述的通信装置，其特征在于，所述处理单元还用于：
    当所述第一请求信息包括的第一信息所指示的原接收网元，与所述通信装置不同，确定所述第一请求信息属于所述第一类信息。
  17. 根据权利要求15或16所述的通信装置，其特征在于，若所述第一请求信息用于请求所述第一业务，所述处理单元用于通过如下方式根据对所述第一类信息的流量控制策略对所述第一请求信息进行处理：
    如果属于所述第一类信息的信息数量小于第一门限，通过所述收发单元向所述终端设备发送第一拒绝信息，以拒绝所述第一请求信息所请求的业务；或，
    如果属于所述第一类信息的信息数量大于或等于第一门限，忽略所述第一请求信息。
  18. 根据权利要求15或16所述的通信装置，其特征在于，若所述第一请求信息为所述终端设备的附着请求信息或注册请求信息，所述处理单元用于通过如下方式根据对所述第一类信息的流量控制策略对所述第一请求信息进行处理：
    如果属于所述第一类信息的信息数量小于第二门限，通过所述收发单元向所述终端设备发送第一响应信息，所述第一响应信息为第一接受信息，所述第一接受信息用于指示所述附着请求信息的接受或者所述注册请求信息的接受，或，所述第一响应信息用于指示拒绝处理所述第一请求信息；或，
    如果属于所述第一类信息的信息数量大于或等于第二门限，忽略所述第一请求信息。
  19. 根据权利要求18所述的通信装置，其特征在于，所述处理单元用于通过如下方式执行如果属于所述第一类信息的信息数量小于第二门限，通过所述收发单元向所述终端设备发送第一响应信息：
    如果属于所述第一类信息的信息数量小于第二门限，且属于第一事件，通过所述收发单元向所述终端设备发送所述第一响应信息，所述第一响应信息用于指示拒绝处理所述第一请求信息。
  20. 根据权利要求18或19所述的通信装置，其特征在于，
    所述处理单元还用于：如果属于所述第一类信息的信息数量小于第二门限，从用户管理网元获得所述终端设备的签约数据；
    所述处理单元用于通过如下方式执行通过所述收发单元向所述终端设备发送第一响应信息，所述第一响应信息为第一接受信息，所述第一接受信息用于指示所述附着请求信息的接受或者所述注册请求信息的接受：在获得所述终端设备的签约数据后，通过所述收发单元向所述终端设备发送所述第一响应信息，所述第一响应信息为所述第一接受信息，所述第一接受信息用于指示所述附着请求信息的接受或者所述注册请求信息的接受；
    其中，所述第二门限与所述用户管理网元的性能相关。
  21. 一种通信装置，其特征在于，包括处理器和存储器，所述存储器和所述处理器耦合，所述处理器用于执行如权利要求1～14任一项所述的方法。
  22. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1～14任一项所述的方法。
  23. 一种芯片系统，其特征在于，所述芯片系统包括：
    处理器和接口，所述处理器用于从所述接口调用并运行指令，当所述处理器执行所述指令时，实现如权利要求1～14任一项所述的方法。
  24. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1～14任一项所述的方法。
  25. 一种系统，其特征在于，所述系统包括用户管理网元和移动管理网元，所述移动管理网元用于执行如权利要求1～14任一项所述的方法。
  26. 根据权利要求25所述的系统，其特征在于，所述用户管理网元为归属签约服务器HSS或统一数据管理UDM网元。
PCT/CN2022/144283 2022-02-21 2022-12-30 一种通信方法及装置 WO2023155618A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210158599.6A CN116669063A (zh) 2022-02-21 2022-02-21 一种通信方法及装置
CN202210158599.6 2022-02-21

Publications (1)

Publication Number Publication Date
WO2023155618A1 true WO2023155618A1 (zh) 2023-08-24

Family

ID=87577473

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/144283 WO2023155618A1 (zh) 2022-02-21 2022-12-30 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN116669063A (zh)
WO (1) WO2023155618A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106465094A (zh) * 2015-01-30 2017-02-22 华为技术有限公司 一种业务容灾的方法、相关装置和通信系统
US9608860B1 (en) * 2016-03-28 2017-03-28 Affirmed Networks Communications Technologies, Inc. Synchronized MME pool
US20180324784A1 (en) * 2017-05-02 2018-11-08 Affirmed Networks, Inc. Flexible load distribution and management in an mme pool
CN111224800A (zh) * 2018-11-23 2020-06-02 大唐移动通信设备有限公司 一种数据处理方法和装置
US20200187048A1 (en) * 2014-07-22 2020-06-11 Parallel Wireless, Inc. Signaling Storm Reduction From Radio Networks

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200187048A1 (en) * 2014-07-22 2020-06-11 Parallel Wireless, Inc. Signaling Storm Reduction From Radio Networks
CN106465094A (zh) * 2015-01-30 2017-02-22 华为技术有限公司 一种业务容灾的方法、相关装置和通信系统
US9608860B1 (en) * 2016-03-28 2017-03-28 Affirmed Networks Communications Technologies, Inc. Synchronized MME pool
US20180324784A1 (en) * 2017-05-02 2018-11-08 Affirmed Networks, Inc. Flexible load distribution and management in an mme pool
CN111224800A (zh) * 2018-11-23 2020-06-02 大唐移动通信设备有限公司 一种数据处理方法和装置

Also Published As

Publication number Publication date
CN116669063A (zh) 2023-08-29

Similar Documents

Publication Publication Date Title
US11889465B2 (en) Paging cause value
US11917498B2 (en) Communication method and communications apparatus
US11381956B2 (en) Obtaining of UE policy
US11224084B2 (en) Method for registering terminal in wireless communication system and apparatus therefor
US20210274575A1 (en) Application Triggering for a Wireless Device
US20220248318A1 (en) Control of Network Slice
US11528591B2 (en) Network slicing-based communication method and network slicing-based communications apparatus
CN111629450B (zh) 一种数据传输方法、相关设备以及存储介质
US20220264258A1 (en) Communications Method and Apparatus, and Device
US20220191765A1 (en) Communication method, apparatus, and system
US20210385284A1 (en) Session establishment method and apparatus
WO2019033796A1 (zh) 会话处理方法及相关设备
WO2019223526A1 (zh) 上下文管理方法及装置
US10999768B2 (en) Session context handling method, network element, and terminal device
WO2019096306A1 (zh) 一种处理请求的方法以及相应实体
WO2021134167A1 (zh) 一种漫游的方法、装置及系统
WO2020155972A1 (zh) 一种移动性管理方法及装置
US20230232196A1 (en) Data communication method and communication apparatus
WO2024037611A1 (zh) 注册信息同步方法、装置、设备及介质
US11412355B2 (en) Method, device, and system for optimizing short message signaling
WO2020173146A1 (zh) 一种切换处理的方法、相关设备、程序产品以及存储介质
WO2023155618A1 (zh) 一种通信方法及装置
WO2021189496A1 (zh) 用于网络切片的数据传输方法及设备
WO2021134175A1 (zh) 一种漫游的方法、装置及系统
WO2021081712A1 (zh) 一种dns查询方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22926915

Country of ref document: EP

Kind code of ref document: A1