WO2022171119A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2022171119A1
WO2022171119A1 PCT/CN2022/075637 CN2022075637W WO2022171119A1 WO 2022171119 A1 WO2022171119 A1 WO 2022171119A1 CN 2022075637 W CN2022075637 W CN 2022075637W WO 2022171119 A1 WO2022171119 A1 WO 2022171119A1
Authority
WO
WIPO (PCT)
Prior art keywords
indication information
registration
request message
registration request
access
Prior art date
Application number
PCT/CN2022/075637
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 华为技术有限公司
Priority to EP22752279.4A priority Critical patent/EP4280697A1/en
Priority to JP2023548550A priority patent/JP2024506092A/ja
Publication of WO2022171119A1 publication Critical patent/WO2022171119A1/zh
Priority to US18/446,988 priority patent/US20230388957A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a communication method and apparatus.
  • the terminal device when the terminal device needs to access the network, it will send a registration request message to the relevant network elements such as the access and mobility management function (AMF), so that the AMF obtains the registration request message, Further, it is determined whether the UE is allowed to access the relevant network, such as the network corresponding to the AMF.
  • the relevant network elements such as the access and mobility management function (AMF)
  • AMF access and mobility management function
  • the present application provides a communication method and device, which can effectively indicate whether it is in a disaster scenario through indication information, thereby improving the efficiency of information interaction.
  • an embodiment of the present application provides a communication method, and the method includes:
  • the terminal device sends a registration request message to an access and mobility management function (AMF) (also referred to as an access and mobility management network element, etc.), where the registration request message includes indication information, and the The indication information indicates whether it is in a disaster scenario; the UE receives a registration response message from the AMF.
  • AMF access and mobility management function
  • the indication information indicates whether it is in a disaster scenario, which can also be understood as: the indication information is used to indicate whether a terminal device (for example, may be referred to as UE for short) is in a disaster scenario.
  • a terminal device for example, may be referred to as UE for short
  • the home public land mobile network (HPLMN) corresponding to the UE is often damaged, so that the UE cannot effectively access the HPLMN.
  • the UE needs to roam to other networks such as the roaming PLMN, and thus the UE needs to interact with the AMF to ensure that it can access the roaming PLMN.
  • the registration request message includes indication information.
  • the AMF can clearly know whether the UE is in a disaster scenario, thereby improving the efficiency of information exchange; on the other hand, the AMF can also be informed of the UE's status. So the reason for accessing a roaming network (such as a roaming PLMN, or a network corresponding to AMF).
  • the registration request message does not include the indication information, the AMF may not be able to distinguish the registration request message sent by the local user or the registration request message sent by the UE in the disaster scenario, which may affect the subsequent registration process of the AMF. .
  • the indication information is a first value, and the indication information indicates that the terminal device is in the disaster scenario; the indication information is a second value, and the indication information indicates the The end device is not in the disaster scenario.
  • the first value may be 1, and the second value may be 0.
  • the method provided by the embodiments of the present application can enable the AMF to know whether the UE is in a disaster scenario through 1-bit information, and can also effectively be compatible with the registration process in which the UE is in the disaster scenario and the UE is not in the disaster scenario.
  • the registration request message further includes a registration type, and the registration type includes: initial registration (initial registration), mobility registration (mobility registration updating), periodic registration (periodic registration updating) or Any of the emergency registrations.
  • an embodiment of the present application provides a communication method, the method comprising:
  • the AMF receives a registration request message from the terminal device, the registration request message includes indication information, and the indication information indicates whether it is in a disaster scenario; the AMF sends a registration response to the terminal device according to the indication information and the load situation information.
  • the AMF can send the registration response message to the UE according to the indication information and its load condition. Therefore, the AMF can perform different processing on the UE in combination with the actual scene in which the UE is located. For example, the AMF may send a registration acceptance message or a registration rejection message to the UE in combination with the scene in which the UE is located.
  • the AMF sends a registration response message to the terminal device according to the indication information and the load condition, including: the AMF determines a threshold according to the indication information; and the AMF according to the load situation and the threshold, send a registration accept message or a registration reject message to the UE.
  • the load condition may include the load condition of the AMF, or the load condition of the network corresponding to the AMF.
  • the indication information indicates that it is in a disaster scenario, and the threshold is a first threshold; the indication information indicates that it is not in a disaster scenario, and the threshold is a second threshold.
  • the AMF may determine different thresholds according to whether the UE is in a disaster scenario. Therefore, a registration acceptance message or a registration rejection message is sent to the UE according to the load condition of the AMF, so that the AMF can adopt different control means for the UE according to the scene where the UE is located.
  • an embodiment of the present application provides a communication method, the method comprising:
  • the terminal device receives a system message from the base station in the roaming network, the system message includes the maximum waiting time; the terminal device determines the waiting time for sending the registration request message according to the identity of the terminal device and the modulus of the maximum waiting time; After the waiting time period expires, the terminal device sends the registration request message to the AMF station.
  • the maximum waiting time is used to determine the waiting time for the UE to send the registration request message.
  • the maximum waiting period can also be understood as the maximum waiting period of the UE.
  • the maximum waiting time may also be referred to as the inbound-waiting-max-time, or the disaster roaming waiting range (disaster roaming wait range), or the maximum roaming waiting time.
  • the specific name of the maximum waiting time is not limited.
  • the waiting time is determined by the modulo of the identifier of the UE and the maximum waiting time, which can improve the situation of a large number of UEs accessing the network corresponding to the AMF at the same time, thereby ensuring that the UE can access the network corresponding to the AMF at the same time while reducing the amount of calculation as much as possible. Access randomness.
  • the terminal device sends the registration request message to the AMF, including:
  • the terminal device If the terminal device is determined to be in a disaster scenario, the terminal device sends the registration request message to the AMF.
  • the registration request message includes indication information, and the indication information indicates that it is in the disaster scenario.
  • the method provided by the embodiment of the present application by combining the indication information with the above-mentioned waiting time, can make the UE in a disaster scenario, and try to avoid the situation that a large number of UEs access the network at the same time at the same time, which will cause the network to become more congested.
  • an embodiment of the present application provides a communication method, the method comprising:
  • the base station in the roaming network determines the maximum waiting time according to the load situation
  • the base station sends a system message to the terminal device, where the system message includes the maximum waiting period.
  • the base station in the roaming network can effectively balance the time for the UE to access the roaming network by determining the maximum waiting time according to the load situation, thereby improving the access time of a large number of UEs. roaming network.
  • an embodiment of the present application provides a communication method, the method comprising:
  • the terminal device sends a registration request message to the access and mobility management network element AMF, and receives a registration refusal message from the AMF; the terminal device determines a list according to the registration refusal message.
  • the network corresponding to the AMF that is allowed to access.
  • the UE can access the network corresponding to the AMF to the list after receiving the registration rejection message of the AMF. Therefore, the situation that the UE repeatedly accesses the AMF is improved, and the situation of network congestion deterioration is effectively improved. For example, generally, after the UE receives the registration rejection message, the UE will access the network corresponding to the AMF to another list, but in a disaster scenario, the UE will be re-allowed to access the network corresponding to the other AMF. If the above method is applied, the UE will continue to access the above-mentioned rejected network even after receiving the registration rejection message, which will not only affect the communication status of the UE, but also worsen the network congestion.
  • the network includes: any one or more of a public land mobile network PLMN, a tracking area or a partial tracking area.
  • an embodiment of the present application provides a communication apparatus for executing the method in the first aspect or any possible implementation manner of the first aspect.
  • the communication apparatus is adapted to perform the method of the second aspect or any possible implementation of the second aspect.
  • the communication apparatus is adapted to perform the method of the third aspect or any possible implementation of the third aspect.
  • the communication device is adapted to perform the method of the fourth aspect.
  • the communication device is configured to perform the method of the fifth aspect or any possible implementation of the fifth aspect.
  • the communication apparatus as described above may include a transceiving unit and a processing unit.
  • a transceiving unit and a processing unit.
  • the transceiver unit and the processing unit reference may also be made to the apparatus embodiments shown below.
  • an embodiment of the present application provides a communication device, where the communication device includes a processor configured to execute the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, or any possible implementation manner method shown.
  • the processor is configured to execute the program stored in the memory, and when the program is executed, the method shown in the above-mentioned first aspect, second aspect, third aspect, fourth aspect, fifth aspect or any possible implementation manner be executed.
  • the process of sending information in the above method may be understood as a process in which the processor outputs the above information, or a process in which the processor receives the above input information.
  • the processor When outputting the above-mentioned information, the processor outputs the above-mentioned information to the transceiver for transmission by the transceiver. After the above-mentioned information is output by the processor, other processing may be required before reaching the transceiver.
  • the transceiver receives the above-mentioned information and inputs it into the processor. Furthermore, after the transceiver receives the above-mentioned information, the above-mentioned information may need to perform other processing before being input to the processor.
  • the sending of the registration request message mentioned in the foregoing method can be understood as the processor outputting the registration request message.
  • the reception of the registration request message mentioned in the foregoing method may be understood as the processor receiving the input registration request message.
  • the above-mentioned processor may be a processor specially used to execute these methods, or may be a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor.
  • the above-mentioned memory can be a non-transitory (non-transitory) memory, such as a read-only memory (Read Only Memory, ROM), which can be integrated with the processor on the same chip, or can be set on different chips respectively.
  • ROM read-only memory
  • the embodiment does not limit the type of the memory and the setting manner of the memory and the processor. It can be understood that the description of the processor and the memory is also applicable to the sixth aspect shown below, and the sixth aspect will not be described in detail for the convenience of repeating the description.
  • the memory is located outside the above-mentioned communication device.
  • the memory is located within the above-mentioned communication device.
  • the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.
  • the communication device further includes a transceiver, which is used for receiving a signal or transmitting a signal.
  • an embodiment of the present application provides a communication device, the communication device includes a logic circuit and an interface, the logic circuit and the interface are coupled;
  • the communication apparatus may be configured to perform steps performed by the UE.
  • the interface is used to output a registration request message and input a registration response message.
  • the logic circuit is configured to determine the waiting time for sending the registration request message.
  • the logic circuit is used to determine and handle disaster scenarios.
  • the communication device may be configured to perform the steps performed by the AMF.
  • the interface is used for inputting a registration request message and outputting a registration response message.
  • the logic circuit is configured to determine a registration response message and the like according to the indication information and the load condition.
  • the communication apparatus may be configured to perform the steps performed by the base station.
  • the logic circuit is used to determine the maximum waiting time according to the load condition, and the interface is used to output system messages and so on.
  • an embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium is used to store a computer program, which, when running on a computer, enables the first aspect or any possible possibility of the first aspect
  • the method shown in the implementation manner is executed; or, the method shown in the second aspect or any possible implementation manner of the second aspect is executed; or, the third aspect or any possible implementation manner of the third aspect is performed. or, the method shown in the fourth aspect above is performed; or, the method shown in the fifth aspect or any possible implementation manner of the fifth aspect is performed.
  • an embodiment of the present application provides a computer program product, the computer program product includes a computer program or computer code, when it is run on a computer, the above-mentioned first aspect or any possible implementation manner of the first aspect is The method shown in the above-mentioned second aspect or any possible implementation manner of the second aspect is executed; or, the method shown in the third aspect or any possible implementation manner of the third aspect is performed is executed; or, the method shown in the fourth aspect is executed; or, the method shown in the fifth aspect or any possible implementation manner of the fifth aspect is executed.
  • an embodiment of the present application provides a computer program.
  • the computer program runs on a computer
  • the method shown in the first aspect or any possible implementation manner of the first aspect is executed;
  • the method shown in the second aspect or any possible implementation manner of the second aspect is executed; or, the method shown in the third aspect or any possible implementation manner of the third aspect is executed; or, the method shown in the fourth aspect above
  • the method is executed; or, the method shown in the fifth aspect or any possible implementation manner of the fifth aspect is executed.
  • an embodiment of the present application provides a wireless communication system, where the wireless communication system includes a UE and an AMF, where the UE is configured to execute the method shown in the first aspect or any possible implementation manner of the first aspect, The AMF is used to execute the method shown in the second aspect or any possible implementation manner of the second aspect.
  • the wireless communication system includes a UE and a base station, the UE is configured to execute the method shown in the third aspect or any possible implementation manner of the third aspect, and the base station is configured to execute the method shown in the fourth aspect;
  • the wireless communication system includes a UE and an AMF connected to the UE, and the UE is configured to execute the method shown in the fifth aspect or any possible implementation manner of the fifth aspect.
  • FIG. 1 is a schematic diagram of a communication system provided by an embodiment of the present application.
  • FIGS. 2 to 5 are schematic flowcharts of a communication method provided by an embodiment of the present application.
  • 6 to 8 are schematic structural diagrams of a communication device provided by an embodiment of the present application.
  • At least one (item) means one or more
  • plural means two or more
  • at least two (item) means two or three and three
  • “and/or” is used to describe the relationship of related objects, indicating that there can be three kinds of relationships, for example, "A and/or B” can mean: only A exists, only B exists, and both A and B exist three A case where A and B can be singular or plural.
  • the character “/” generally indicates that the associated objects are an “or” relationship.
  • At least one of the following” or similar expressions refers to any combination of these items. For example, at least one (a) of a, b or c, can mean: a, b, c, "a and b", “a and c", “b and c", or "a and b and c" ".
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • IoT Internet of Things
  • NB-IoT narrowband Internet of Things
  • WiFi wireless fidelity
  • 5G 5th generation
  • NR new radio
  • the technical solutions provided in this application can also be applied to machine type communication (MTC), Long Term Evolution-machine (LTE-M), and device-to-device (D2D) networks.
  • M2M Machine to Machine
  • IoT Internet of Things
  • the IoT network may include, for example, the Internet of Vehicles.
  • vehicle to X vehicle to X
  • V2X vehicle and vehicle Infrastructure
  • V2I vehicle to pedestrian
  • V2N vehicle to network
  • the terminal device in this application is a device with wireless transceiver function.
  • a terminal device can communicate with one or more core network (core network, CN) devices (or also referred to as an access device) in a radio access network (RAN). to communicate with the core device).
  • core network core network
  • CN core network
  • RAN radio access network
  • Terminal equipment may also be referred to as user equipment (UE), access terminal, terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user Terminal, user agent, or user device, etc.
  • UE user equipment
  • terminal equipment can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites) superior).
  • the terminal device may be a handheld device with a wireless communication function, a vehicle-mounted device, a wearable device, a terminal in the Internet of Things, the Internet of Vehicles, a fifth-generation (5th generation, 5G) network, and a future network Any form of terminal equipment, etc., is not limited in this application.
  • terminal equipment shown in this application may not only include vehicles (such as complete vehicles) in the Internet of Vehicles, but also include in-vehicle devices or vehicle-mounted terminals in the Internet of Vehicles.
  • vehicle such as complete vehicles
  • vehicle-mounted terminals in the Internet of Vehicles.
  • the specific form is not limited.
  • D2D device to device
  • V2X vehicle-to-everything
  • machine to machine machine to machine
  • the 5G network has made network architecture adjustments compared to the 4G network.
  • the 5G network splits the mobility management entity (MME) in the 4G network into two parts including the access and mobility management function (AMF) and the session management function (session management function). , SMF) and other network elements (or can also be called network functions).
  • MME mobility management entity
  • AMF access and mobility management function
  • SMF session management function
  • other network elements or can also be called network functions).
  • the AMF shown in this application is the control plane network function provided by the PLMN, and is responsible for the access control and mobility management of the UE accessing the PLMN, including functions such as mobility state management, assignment of temporary user identities, and authentication and authorization of users. Therefore, with the development of the mobile network, even if the AMF may evolve into other forms or names, as long as the method shown in the present application can be implemented, it falls within the protection scope of the present application.
  • the base station may be a device deployed in a radio access network to provide wireless communication services for terminal equipment.
  • the base station shown in this application may also be referred to as an access network device, an access device, or a RAN device, or the like.
  • the base stations shown in this application may include but are not limited to: next generation node basestations (gNBs) in 5G systems, evolved base stations (evolved node Bs, eNBs) in LTE systems, wireless network control radio network controller (RNC), node B (node B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (home evolved nodeB, or home node) B, HNB), base band unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), small base station equipment (pico), mobile switching center, or future network network equipment, etc.
  • the base station may also be a device carrying base station functions in D2D, V2X, or M2M, or the like. In systems with different wireless access technologies, the names of devices with access network device functions may be different.
  • the base station may include a centralized unit (centralized unit, CU), a distributed unit (distributed unit, DU), and the like.
  • the CU can also be divided into a CU-control plane (CP) and a CU-user plane (UP).
  • the base station may also be an open radio access network (open radio access network, ORAN) architecture, etc. This application does not limit the specific deployment mode of the base station.
  • FIG. 1 is a schematic diagram of a communication system provided by an embodiment of the present application.
  • the communication system may include at least one base station, at least one terminal device, such as UE1 to UE6 in FIG. 1 , and an AMF. It is understandable that the specific description about the AMF, the UE, and the base station may refer to the above, which will not be repeated here.
  • the UEs can communicate directly.
  • direct communication between UEs can be implemented through D2D technology.
  • the D2D technology can be used for direct communication between UE4 and UE5 and between UE4 and UE6.
  • UE4 or UE6 may communicate with UE5 individually or simultaneously.
  • UE4 to UE6 may also communicate with the base station respectively.
  • UE4 or UE6 may communicate with the base station directly, or may communicate with the base station indirectly, for example, UE6 may communicate with the base station via UE5.
  • FIG. 1 exemplarily shows a base station, multiple UEs, and communication links between communication devices.
  • the communication system may include multiple base stations, and the coverage of each base station may include other numbers of UEs, such as more or less UEs. This application does not limit this.
  • the communication system shown in FIG. 1 may also include a unified data management (unified data management, UDM) network element or an authentication server function (authentication server function, AUSF) network element, etc.
  • UDM unified data management
  • AUSF authentication server function
  • the embodiment of the present application is for the communication system.
  • the specific structure is not limited.
  • the unified data management UDM is a control plane function provided by an operator, and is responsible for storing information such as subscriber permanent identifier (SUPI), security context (security context), and subscription data of subscribers in the PLMN.
  • the authentication server function AUSF is a control plane function provided by an operator, and is usually used for authentication, such as authentication between a terminal device (subscriber) and a PLMN.
  • the communication system may further include other network elements such as a network controller and a session management function (session management function, SMF), which are not limited in this embodiment of the present application.
  • SMF session management function
  • the UE needs to roam to other PLMNs that can provide services (even if the user does not have a roaming agreement).
  • the UE can be transferred back to the original PLMN (such as the HPLMN described above). That is to say, in a disaster scenario, the HPLMN with the UE is often damaged, so that the UE cannot effectively access the HPLMN, which will lead to interruption of UE services.
  • the UE can register with a PLMN that provides disaster roaming services.
  • the present application provides a communication method and apparatus, so that the AMF that receives the registration request message sent by the UE can clearly know whether the UE is in a disaster scenario, thereby improving the efficiency of information exchange.
  • the communication method provided by the present application can also effectively reduce the interruption of UE services in a disaster scenario.
  • the communication system to which this application applies may be as shown above (as shown in FIG. 1 ), and will not be described in detail here.
  • FIG. 2 is a schematic flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 2 , the method includes:
  • the UE sends a registration request message to the AMF, where the registration request message includes indication information, where the indication information is used to indicate whether it is in a disaster scenario.
  • the AMF receives the registration request message.
  • a disaster When a disaster occurs, it will cause damage to the base station or core network elements, resulting in interruption of the UE and the network, that is, the disaster will lead to the interruption of communication services.
  • natural disasters such as earthquakes will cause fires or power outages in some wireless access network equipment. , thereby causing the cell between the radio access network and the core network to suddenly disappear or have no route.
  • Man-made disasters such as installing faulty software or mismanaged certificates, can cause abnormal behavior in the wireless access network, resulting in users within the network not being able to exchange signaling or data.
  • the disaster scenarios shown in the embodiments of the present application may also be called disaster roaming (disaster roaming) scenarios, and the specific names thereof are not limited in the embodiments of the present application.
  • the embodiments of the present application do not limit how the UE determines that it is in a disaster scenario.
  • the UE may be that the UE has been unable to access the original PLMN, and thus the UE knows that it is in a disaster scenario.
  • the UE may be interrupted with the original network, and when retrying to access a network such as a roaming network, it may learn that it is in a disaster scenario according to a broadcast message of a base station in the roaming network.
  • the above-described method for the UE to determine that it is in a disaster scenario is only an example, and should not be construed as a limitation on the embodiments of the present application.
  • the UE may send a registration request message to the AMF of the roaming network.
  • the indication information indicates whether it is in a disaster scenario, which can be understood as: the indication information indicates whether the UE is in a disaster scenario, or the indication information indicates whether the HPLMN of the UE is in a disaster scenario, or the indication information indicates the original network corresponding to the UE. Whether it is in a disaster scenario, or whether the indication information indicates whether it is a registration request message initiated in a disaster scenario, or whether the indication information indicates whether the UE is a registration request message initiated in a disaster scenario, etc. limited. That is to say, whether the above-mentioned registration request message belongs to the registration under the disaster scenario can be indicated by the indication information. It is understandable that the above-mentioned indication information may also be called disaster condition indication, etc., and the specific name thereof is not limited in this embodiment of the present application.
  • the indication information when the indication information is the first value, the indication information indicates that it is in a disaster scenario.
  • the indication information when the indication information is the second value, the indication information indicates that it is not in the disaster scenario.
  • whether it is in a disaster scenario can be indicated by 1-bit indication information.
  • the first value may be 1 and the second value may be 0. That is, after the UE determines that it roams from another network to the roaming network due to a disaster, the UE may send a registration request message carrying indication information to the AMF, where the indication information is the first value.
  • the AMF can be made to know whether the UE is in a disaster scenario, and can also be effectively compatible with the registration process that the UE is in the disaster scenario and the UE is not in the disaster scenario.
  • the specific bits of the indication information are not limited in this embodiment of the present application.
  • the content included in the registration request message may be as shown in Table 1. It can be understood that the content included in the registration request message shown below is only an example, and should not be construed as a limitation on the embodiments of the present application.
  • the registration request message further includes a registration type, and the registration type includes: initial registration (initial registration), mobility registration update (mobility registration update), periodic registration update (periodic registration update) ) or emergency registration.
  • the registration type may be represented by 3 bits, as shown in Table 2. It can be understood that the relationship between the bits and the registration type shown in Table 2 is only an example.
  • the AMF can not only know that the UE is in a disaster scenario, but also better know that the above-mentioned registration request message is the initial registration, mobility registration update, period in the disaster scenario Whether it is a sexual registration update or an emergency registration.
  • Table 3 makes the AMF know that the UE is in a disaster scenario by adding disaster roaming initial registration.
  • Table 4 shows that the AMF learns that the UE is in a disaster scenario by adding disaster roaming registration.
  • the type of the registration request message initiated may not be limited to the above-mentioned initial registration for disaster roaming.
  • a disaster roaming registration may have a semantic conflict with the initial registration, mobility registration update, periodic registration update, or emergency registration described above.
  • Tables 3 and 4 when the UE initially registers, it cannot effectively distinguish whether the registration request message includes the type of initial registration or the type of initial registration in disaster. Because semantically initial registration can include disaster initial registration, there will be inconsistencies in logical scope.
  • the AMF may perform an authentication operation or allocate a tracking area. For another example, when the mobility registration is updated, the AMF may not perform authentication or the like.
  • the AMF can also be made to know clearly whether the UE is in a disaster scenario. Even if the AMF can effectively distinguish which type of UE the registration request message it receives is sent by, for example, the AMF can effectively distinguish: the local network access UE (also called the local network access user or the local network access user) roamers, etc.), foreign roaming UEs (also known as foreign roamers or foreign roamers, etc.), or disaster roaming UEs (also known as disaster roamers or disaster roamers). Assuming that the registration request message does not include indication information, it is difficult for the AMF to know whether the registration request message is initiated by a UE user who has roamed over in a disaster scenario, or is initiated by a roaming contracted UE.
  • the local network access UE also called the local network access user or the local network access user
  • foreign roaming UEs also known as foreign roamers or foreign roamers, etc.
  • disaster roaming UEs also known as disaster roamers or disaster roamers.
  • the AMF can know that the UE has not actually signed a contract, but is a UE roaming in a disaster scenario, which will affect the control strategy that the AMF should adopt for the UE in the disaster scenario (for example, the control strategy adopted by the AMF will be Delay).
  • the UE sends the registration request message the above-mentioned indication information is not included in the registration request message, it can indicate that it is not in a disaster scenario.
  • the AMF sends a registration response message to the UE according to the indication information and the load condition.
  • the UE receives the registration response message.
  • the above load condition may include the load condition of the AMF, or the load condition of the network corresponding to the AMF.
  • this embodiment of the present application does not limit it.
  • the registration response message includes a registration acceptance message or a registration rejection message.
  • the AMF determines the registration acceptance message or the registration rejection message according to the indication information and the load situation, so as to send the registration acceptance message or the registration rejection message to the UE.
  • the AMF may determine the threshold according to the indication information, and then determine the registration acceptance message or the registration rejection message according to the load situation and the threshold. If the indication information indicates that it is in a disaster scenario, the above threshold is the first threshold (also referred to as a disaster load threshold, etc.). In another example, if the indication information indicates that it is not in a disaster scenario, the above-mentioned threshold is the second threshold (which may also be referred to as a non-disaster load threshold, etc.).
  • the AMF can take different control measures according to the corresponding threshold and load conditions. For example, after the AMF receives the registration request message, if the indication information is found to be the first value such as 1, it can judge whether to accept the registration of the UE according to the first threshold. For example, if the load condition exceeds the first threshold, the registration request message may be rejected, otherwise the registration request message may be accepted.
  • the indication information is found to be a second value such as 0, or the indication information is not carried, it indicates that it is a UE of the local network or a roaming subscription UE, and it can be judged whether to accept the registration of the UE according to the second threshold.
  • the embodiments of the present application do not limit the specific standards of the first threshold and the second threshold.
  • the load situation may be measured by the number of access UEs, and the first threshold and the second threshold may be set according to the standard of access UEs.
  • the load situation can be measured by the load percentage of the network (or the load of the AMF), then the first threshold and the second threshold can be set by the load percentage of the network.
  • This embodiment of the present application does not limit the load condition, the specific standards of the first threshold and the second threshold.
  • the first threshold may be greater than the second threshold.
  • the UE in the disaster scenario can be preferentially guaranteed to access the network. For example, by ensuring that a UE in a disaster scenario preferentially accesses the network, the UE can communicate with the outside world quickly or in a timely manner.
  • the first threshold may be smaller than the second threshold.
  • the first threshold since the UE in the disaster scenario is a roaming non-subscription UE, the first threshold may be smaller than the second threshold in order to ensure the communication quality of the local network UE and the roaming subscription UE.
  • the size relationship between the first threshold and the second threshold is not limited in this embodiment of the present application.
  • the registration request message includes indication information.
  • the AMF can clearly know whether the UE is in a disaster scenario, thereby improving the efficiency of information exchange; on the other hand, the AMF can also know the reason why the UE has received The reason for entering a roaming network (such as a roaming PLMN, or a network corresponding to AMF).
  • FIG. 3 is a schematic flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 3 , the method includes:
  • the base station in the roaming network determines the maximum waiting time according to the load situation.
  • the above-mentioned maximum waiting time may also be referred to as the inbound-waiting-max-time, or the disaster roaming waiting range (disaster roaming wait range), or the maximum roaming waiting time.
  • the specific name of the waiting time is not limited.
  • the load condition may be the load condition of the base station, or the load condition of the network corresponding to the base station.
  • the base station determines the maximum waiting time according to the load situation, that is, the base station can dynamically adjust the maximum waiting time according to the load situation. For example, when the load is higher (it can also be understood as a heavier load), the maximum waiting time is longer; when the load is lower (it can also be understood as a lighter load), the maximum waiting time is shorter.
  • the load situation of the base station can be effectively improved, or the load situation of the network can be improved. This ensures that UEs are evenly distributed in different time ranges. For example, when the load is light, the UE can access densely for a short time, and when the load is heavy, the UE can access sparsely for a long time, which can effectively improve the network congestion.
  • the embodiment of the present application does not limit the specific relationship between the load and the maximum waiting time.
  • the measurement unit of the maximum waiting time is not limited.
  • the maximum wait time can be measured in s, such as 5s or 255s.
  • the base station sends a system message to the UE, where the system message includes the maximum waiting duration. Accordingly, the UE receives the system message.
  • system message may include a system information block (system information block) 1, or other SIBs (hereinafter referred to as SIB-vX), etc., which are not limited in this embodiment of the present application.
  • SIB-vX system information block
  • SIB-vX system information block
  • the signaling format of SIB1 may be as follows:
  • SIB1-v17XX-IEs represents the version (version, v) number of the system message
  • inbound-waiting-max-time represents the maximum waiting time
  • INTEGER represents the specific value of the maximum waiting time
  • the signaling format of SIB-vX may be as follows:
  • SIB-vX-IEs indicates the version number of the system message
  • inbound-waiting-max-time indicates the maximum waiting time
  • INTEGER indicates the specific value of the maximum waiting time
  • the system message does not include the SIB-vX, it means that the UE can immediately send the registration request message. That is, when the UE does not need to wait, the SIB-vX may not be included in the system message.
  • the UE determines the waiting time for sending the registration request message according to the modulo of the identifier of the UE and the maximum waiting time.
  • the identifier of the UE may include a 5th generation system (5GS) mobile identity (5GS mobile identity), such as an encrypted subscription identifier (SUCI) of the UE, a globally unique temporary UE identity (globally unique temporary UE identity, GUTI), user permanent identity (subscription permanent identifier, SUPI), international mobile equipment identity (international mobile equipment identity, IMEI) or international mobile subscriber identity (international mobile subscriber identity, IMSI) Wait.
  • 5GS mobile identity 5th generation system
  • SUCI encrypted subscription identifier
  • GUTI globally unique temporary UE identity
  • SUPI subscription permanent identifier
  • SUPI subscription permanent identifier
  • IMEI international mobile equipment identity
  • IMSI international mobile subscriber identity
  • the UE may use a timer to time the waiting time for the registration request message when camping on the cell.
  • the UE may also use a timer to time the waiting time for the registration request message. This embodiment of the present application does not limit when the UE starts timing.
  • the IMSI since the IMSI may be unique in each UE (similar to a phone number), it is randomly and uniformly distributed in the network from a statistical point of view.
  • the random number mod maximum waiting time ensures that the result after the modulo is also randomly and uniformly distributed from 0 to the maximum waiting time, which ensures that the UE is uniformly distributed in different time ranges.
  • the UE After the waiting time period expires, the UE sends a registration request message to the AMF. Correspondingly, the AMF receives the registration request message.
  • the specific content of the registration request message is not limited. That is to say, the methods provided in the embodiments of the present application can be applied not only in a non-disaster scenario, for example, the above-mentioned UE may be a roaming subscription UE; but also in a disaster scenario, for example, the above-mentioned UE may be a disaster roaming UE.
  • a non-disaster scenario for example, the above-mentioned UE may be a roaming subscription UE; but also in a disaster scenario, for example, the above-mentioned UE may be a disaster roaming UE.
  • a disaster roaming UE for specific instructions not in a disaster scenario, you can refer to relevant standards or protocols, etc., which will not be repeated here.
  • the UE determines that it is in a disaster scenario, and the UE sends a registration request message to the AMF.
  • the registration request message may not include the indication information, for example, the registration request message may include the registration type.
  • the registration request message may include indication information, whereby whether it is in a disaster scenario is clearly indicated through the indication information.
  • indication information For a specific description of being in a disaster scenario, for example, the method shown in FIG. 2 above may be referred to. That is, the method shown in FIG. 3 may be combined with the method shown in FIG. 2 above. The specific description of the indication information and the like will not be repeated here. At the same time, the specific description of the AMF sending the registration response message to the UE according to the indication information and the load situation will not be repeated.
  • the base station in the roaming network can effectively balance the time for the UE to access the roaming network by determining the maximum waiting time according to the load situation, thereby improving the access time of a large number of UEs. roaming network.
  • the waiting time is determined by the modulus of the UE's identity and the maximum waiting time, which can improve the situation of a large number of UEs accessing the network corresponding to the AMF at the same time, thereby ensuring the randomness of UE access while reducing the amount of calculation as much as possible.
  • FIG. 4 is a schematic flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 4 , the method includes:
  • the terminal device sends a registration request message to the AMF, and the AMF receives the registration request message.
  • the AMF sends a registration rejection message to the UE, and the UE receives the registration rejection message.
  • step 401 and step 402 reference may be made to relevant standards or protocols, and the embodiment of the present application does not limit the registration request message and the registration rejection message.
  • the UE determines a list according to the registration rejection message, where the list includes a network corresponding to the AMF that is not allowed to access in a disaster scenario.
  • the UE may add the network corresponding to the AMF that it is not allowed to access to the list, so as to avoid the UE from repeatedly accessing the network.
  • the above registration request message may be the initial registration initiated by the UE (eg, the UE initially attempts to access the AMF in the roaming network), and thus the UE may add the network corresponding to the AMF that the UE attempts to initially access to the list.
  • the above-mentioned registration request message may not be a registration initially initiated by the UE, but a registration request message re-initiated after the UE has been rejected one or more times.
  • the UE since the UE has tried to access the AMF for many times and failed, the UE can access the network corresponding to the AMF to the above-mentioned list. Effectively avoid the situation that the UE tries to access again and is rejected again, causing the UE to waste resources or time.
  • the above network includes: any one or more of a PLMN, a tracking area or a partial tracking area.
  • the list includes a disaster forbidden PLMN List, a disaster forbidden tracking areas list (also known as a disaster forbidden tracking areas of roaming list), or Disaster forbidden tracking areas for regional provision of list (also known as disaster forbidden tracking areas for regional provision of service list).
  • the method provided in this embodiment of the present application may also be combined with the method shown in FIG. 2 .
  • the registration request message includes indication information, so that the AMF can send a registration rejection message to the UE according to the indication information and load conditions.
  • the method provided in this embodiment of the present application may also be combined with the method shown in FIG. 3 .
  • the base station in the roaming network determines the maximum waiting time according to the load situation, and sends the maximum waiting time to the UE. Then the UE determines the waiting time for sending the registration request message according to the modulus of the UE's identity and the maximum waiting time, and sends the registration request message to the AMF after the waiting time expires.
  • the methods provided in the embodiments of the present application may also be combined with the methods shown in FIG. 2 and FIG. 3 .
  • FIG. 5 shown below, which will not be described in detail here.
  • the UE will access the network corresponding to the AMF to other lists, such as the forbidden list in the relevant standard or protocol. However, in a disaster scenario, the UE will be allowed to access again. The network corresponding to the other AMF. If the above method is applied, the UE will continue to access the above-mentioned rejected network even after receiving the registration rejection message, which will not only affect the communication status of the UE, but also worsen the network congestion.
  • the UE can access the network corresponding to the AMF to the list after receiving the registration rejection message of the AMF. Therefore, the situation that the UE repeatedly accesses the AMF is improved, and the situation of network congestion deterioration is effectively improved.
  • the various embodiments shown above may be independent solutions, or may be combined according to internal logic, and these solutions all fall within the protection scope of the present application.
  • the various embodiments shown above can be combined with each other.
  • the methods of Figures 2 and 3 shown above may be combined.
  • the methods of FIGS. 2 and 4 shown above may be combined.
  • the methods of FIGS. 3 and 4 shown above may be combined.
  • the methods of FIGS. 2 , 3 and 4 shown above may be combined.
  • FIG. 5 is a schematic flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 5 , the method includes:
  • the base station in the roaming network determines the maximum waiting period according to the load situation.
  • the base station sends a system message to the UE, where the system message includes the maximum waiting duration.
  • the UE receives the system message.
  • the UE determines the waiting time for sending the registration request message according to the modulus of the UE's IMSI and the maximum waiting time.
  • the UE After the waiting time period expires, the UE sends a registration request message to the AMF.
  • the AMF receives the registration request message.
  • the registration request message includes indication information, and the indication information indicates whether it is in a disaster scenario.
  • the AMF sends a registration rejection message to the UE according to the indication information and the load condition.
  • the UE receives the registration rejection message.
  • the UE determines a list according to the registration rejection message, where the list includes a network corresponding to the AMF that is not allowed to access in a disaster scenario.
  • authentication can also be performed between the AMF and the AUSF in the HPLMN of the UE.
  • the AMF can send an authentication request (authenticate to the AUSF in the HPLMN). request), the AUSF sends an authentication request to the UDM in the HPLMN, the UDM sends an authentication response to the AUSF, the AUSF sends an authentication response to the AMF, and the AMF sends an authentication response to the UE.
  • the AMF sends an authentication response to the UE.
  • the method provided by the embodiments of the present application not only enables the AMF in the roaming network to know whether the UE is in a disaster scenario, but also enables the AMF to determine whether to send a registration rejection message to the UE in combination with the scenario in which the UE is located, so that the UE receives the registration rejection message. After rejecting the message, the network corresponding to the AMF is added to the list, so as to avoid the situation that the UE tries to access multiple times, which leads to waste of resources.
  • the present application divides the communication device into functional modules according to the above method embodiments.
  • 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, and can also be implemented in the form of software function modules. It should be noted that the division of modules in this application is schematic, and is only a logical function division, and other division methods may be used in actual implementation.
  • the communication apparatus according to the embodiment of the present application will be described in detail below with reference to FIG. 6 to FIG. 8 .
  • FIG. 6 is a schematic structural diagram of a communication device provided by an embodiment of the present application. As shown in FIG. 6 , the communication device includes a processing unit 601 and a transceiver unit 602 .
  • the communication apparatus may be the terminal device shown above or a chip in the terminal device, or the like. That is, the communication apparatus may be used to perform the steps or functions performed by the terminal device in the above method embodiments.
  • the transceiver unit 602 is configured to output a registration request message, where the registration request message includes indication information indicating whether it is in a disaster scenario; the transceiver unit 602 is further configured to input a registration response message.
  • the transceiver unit 602 configured to output the registration request message includes: the transceiver unit 602 configured to send the registration request message to the AMF.
  • the transceiver unit 602 for inputting the registration response message includes: a transceiver unit 602 for receiving the registration response message from the AMF.
  • the transceiving unit 602 can also be used to perform the sending step in the step 201 shown in FIG. 2 , and the transceiving unit 602 can also be used to perform the receiving step in the step 202 shown in FIG. 2 .
  • the transceiver unit 602 can also be used to execute the sending step in the step 502 shown in FIG. 5
  • the processing unit 601 can also be used to execute the step 503 shown in FIG. 5
  • the transceiver unit 602 can also be used to execute the step shown in FIG. 5 .
  • the sending step in step 504 and the receiving step in step 505 are shown, and the processing unit 601 may also be configured to execute step 506 shown in FIG. 5 .
  • the processing unit 601 may use the transceiver unit 602 to perform the above-mentioned steps of outputting the registration request message, and the step of inputting the registration response message, and the like.
  • the transceiver unit 602 is used for inputting a system message, the system message includes the maximum waiting time; the processing unit 601 is used for determining the waiting time for sending the registration request message according to the identifier of the communication device and the maximum waiting time; the transceiver unit 602, It is also used for outputting a registration request message after the waiting time period expires.
  • the transceiver unit 602 for inputting system messages includes a transceiver unit 602 for receiving system messages from base stations in the roaming network.
  • the transceiver unit 602 is further configured to output a registration request message after the waiting time expires.
  • the transceiver unit 602 is further configured to send a registration request message to the AMF after the waiting time expires.
  • the transceiving unit 602 can also be used to perform the receiving step in the step 302 shown in FIG. 3
  • the processing unit 601 can also be used to perform the step 303 shown in FIG. 3
  • the transceiving unit 602 can also be used to perform The sending step in step 304 shown in FIG. 3 .
  • the transceiver unit 602 is configured to output a registration request message and input a registration rejection message; the processing unit 601 is configured to determine a list according to the registration rejection message, and the list includes the network corresponding to the AMF that is not allowed to be accessed under the disaster scenario. .
  • the transceiver unit 602 can also be used to perform the sending step in step 401 shown in FIG. 4 and the receiving step in step 402
  • the processing unit 601 can also be used to perform step 403 shown in FIG. 4 .
  • the communication device may be the AMF shown above or a chip in the AMF, or the like. That is, the communication apparatus may be used to perform the steps or functions performed by the AMF in the above method embodiments.
  • the transceiver unit 602 is used for inputting a registration request message, the registration request message includes indication information, and the indication information is used to indicate whether it is in a disaster scenario; the processing unit 601 is used for, according to the indication information and load conditions, through the The transceiver unit 602 outputs a registration response message.
  • the processing unit 601 is configured to determine the registration response message according to the indication information and the load situation, and then output the registration response message through the transceiver unit 602 .
  • the processing unit 601 is configured to determine a threshold according to the indication information; and output a registration acceptance message or a registration rejection message through the transceiver unit 602 according to the load situation and the threshold.
  • the transceiver unit 602 may also be used to perform the receiving step in step 201 shown in FIG. 2 and the sending step in step 202, etc., which will not be described in detail here.
  • the transceiver unit 602 may also be configured to perform the receiving step in step 504 and the sending step in step 505 shown in FIG. 5 .
  • the communication device may be the base station shown above or a chip in the base station, or the like. That is, the communication apparatus may be used to perform the steps or functions performed by the base station in the above method embodiments.
  • the processing unit 601 is used to determine the maximum waiting time according to the load condition; the transceiver unit is used to output a system message, where the system message includes the maximum waiting time.
  • the processing unit 601 may also be configured to perform step 301 shown in FIG. 3
  • the transceiver unit 602 may also be configured to perform the sending step in step 302 shown in FIG. 3 and the receiving step in step 304 and the like.
  • the processing unit 601 can also be used to perform step 501 shown in FIG. 5
  • the transceiver unit 602 can also be used to perform the sending step of step 502 shown in FIG. 5 .
  • transceiver unit and the processing unit shown in the above embodiments are only examples.
  • specific functions or execution steps of the transceiver unit and the processing unit reference may be made to the above method embodiments, which will not be described in detail here.
  • the processing unit 601 may be one or more processors
  • the transceiver unit 602 may be a transceiver, or the transceiver unit 602 may also be a sending unit and a receiving unit
  • the sending unit may be a transmitter
  • the receiving unit may be a receiver
  • the sending unit and the receiving unit are integrated into one device, such as a transceiver.
  • the processor and the transceiver may be coupled, etc., and the connection manner of the processor and the transceiver is not limited in the embodiment of the present application.
  • the communication device 70 includes one or more processors 720 and transceivers 710 .
  • the transceiver 710 when the communication apparatus is used to perform the steps, methods or functions performed by the terminal device, the transceiver 710 is used to send a registration request message to the AMF, and receive a registration response message from the AMF. Alternatively, the transceiver 710 is configured to receive system messages from base stations in the roaming network.
  • the processor 720 is configured to determine the waiting time for sending the registration request message according to the identifier of the terminal device and the maximum waiting time. Alternatively, the processor 720 is configured to determine a list according to the registration rejection message, where the list includes networks corresponding to AMFs that are not allowed to access in a disaster scenario.
  • the transceiver 710 is configured to receive a registration request message from the terminal device, and send a registration response message (including a registration accept message) to the terminal device. or registration rejection message).
  • the processor 720 is configured to determine the registration response message according to the indication information and the load situation.
  • the processor 720 is used to determine the maximum waiting time according to the load condition, and the transceiver 710 is used to send a system message to the terminal device, the System messages include the maximum wait time.
  • the transceiver may include a receiver for performing the function (or operation) of receiving and a transmitter for performing the function (or operation) of transmitting ). And transceivers are used to communicate with other devices/devices over the transmission medium.
  • the communication apparatus 70 may further include one or more memories 730 for storing program instructions and/or data (for example, when the communication apparatus is used to perform steps performed by the terminal device, the memory may include a list, so FIG. 7 The list shown is shown in dashed lines).
  • Memory 730 is coupled to processor 720 .
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • Processor 720 may cooperate with memory 730 .
  • the processor 720 may execute program instructions stored in the memory 730 .
  • at least one of the above-mentioned one or more memories may be included in the processor.
  • the specific connection medium between the transceiver 710, the processor 720, and the memory 730 is not limited in the embodiments of the present application.
  • the memory 730, the processor 720, and the transceiver 710 are connected through a bus 740 in FIG. 7.
  • the bus is represented by a thick line in FIG. 7, and the connection between other components is only for schematic illustration. , is not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used in FIG. 7, but it does not mean that there is only one bus or one type of bus.
  • the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc.
  • a general purpose processor may be a microprocessor or any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor, or the like.
  • the memory may include, but is not limited to, a non-volatile memory such as a hard disk drive (HDD) or a solid-state drive (SSD), a random access memory (Random Access Memory, RAM), Erasable Programmable Read-Only Memory (Erasable Programmable ROM, EPROM), Read-Only Memory (Read-Only Memory, ROM) or Portable Read-Only Memory (Compact Disc Read-Only Memory, CD-ROM) and so on.
  • a memory is any storage medium that can be used to carry or store program codes in the form of instructions or data structures, and can be read and/or written by a computer (such as the communication devices shown in this application, etc.), but is not limited thereto.
  • the memory in this embodiment of the present application may also be a circuit or any other device capable of implementing a storage function, for storing program instructions and/or data.
  • the processor 720 is mainly used for processing communication protocols and communication data, and controlling the entire communication apparatus, executing software programs, and processing data of the software programs.
  • the memory 730 is mainly used to store software programs and data.
  • the transceiver 710 may include a control circuit and an antenna, and the control circuit is mainly used for converting baseband signals to radio frequency signals and processing radio frequency signals.
  • Antennas are mainly used to send and receive radio frequency signals in the form of electromagnetic waves.
  • Input and output devices such as touch screens, display screens, and keyboards, are mainly used to receive data input by users and output data to users.
  • the processor 720 can read the software program in the memory 730, interpret and execute the instructions of the software program, and process the data of the software program.
  • the baseband signal is output to the radio frequency circuit, and the radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal through the antenna in the form of electromagnetic waves.
  • the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 720.
  • the processor 720 converts the baseband signal into data and processes the data. deal with.
  • the radio frequency circuit and antenna can be provided independently of the processor that performs baseband processing. For example, in a distributed scenario, the radio frequency circuit and antenna can be arranged remotely from the communication device. .
  • the communication device shown in the embodiment of the present application may also have more components and the like than that in FIG. 7 , which is not limited in the embodiment of the present application.
  • the method performed by the processor and the transceiver shown above is only an example, and for the specific steps performed by the processor and the transceiver, reference may be made to the method described above.
  • the processing unit 601 may be one or more logic circuits, and the transceiver unit 602 may be an input and output interface, also called a communication interface, or an interface circuit , or interfaces, etc.
  • the transceiver unit 602 may also be a sending unit and a receiving unit, the sending unit may be an output interface, and the receiving unit may be an input interface, the sending unit and the receiving unit are integrated into one unit, such as an input and output interface.
  • the communication device shown in FIG. 8 includes a logic circuit 801 and an interface 802 .
  • the above-mentioned processing unit 601 can be implemented by the logic circuit 801
  • the transceiver unit 602 can be implemented by the interface 802 .
  • the logic circuit 801 can be a chip, a processing circuit, an integrated circuit or a system on chip (SoC) chip, etc.
  • the interface 802 can be a communication interface, an input and output interface, a pin, and the like.
  • FIG. 8 takes the above communication device as a chip as an example, and the chip includes a logic circuit 801 and an interface 802 .
  • the logic circuit and the interface may also be coupled to each other.
  • the specific connection manner of the logic circuit and the interface is not limited in the embodiment of the present application.
  • the communication apparatus when used to execute the above-mentioned method, function or step performed by the terminal device, such as the interface 802, it is used to output a registration request message and input a registration response message.
  • the interface 802 is used for inputting system messages; the logic circuit 801 is used for determining the waiting time for sending the registration request message according to the identifier of the terminal device and the maximum waiting time.
  • the logic circuit 801 is configured to determine a list according to the registration rejection message, and so on.
  • the interface 802 is used for inputting a registration request message and outputting a registration response message.
  • the logic circuit 801 is used to determine the registration response message according to the indication information and the load condition; the interface 802 is used to output the registration response message.
  • the logic circuit 801 is used to determine the maximum waiting time according to the load condition, and the interface 802 is used to output the system message.
  • the communication apparatus shown in the embodiments of the present application may implement the methods provided in the embodiments of the present application in the form of hardware, and may also implement the methods provided in the embodiments of the present application in the form of software, etc., which are not limited in the embodiments of the present application.
  • An embodiment of the present application further provides a wireless communication system, where the wireless communication system includes a terminal device and an AMF, and the terminal device and the AMF can be used to execute the method in any of the foregoing embodiments.
  • the wireless communication system further includes a base station, and the base station can be used to execute the method in any of the foregoing embodiments.
  • the terminal device, the AMF and the base station reference may be made to the foregoing embodiments, which will not be described in detail here.
  • the present application also provides a computer program for implementing the operations and/or processing performed by the terminal device in the method provided by the present application.
  • the present application also provides a computer program for implementing the operations and/or processing performed by the AMF in the methods provided by the present application.
  • the present application also provides a computer program for implementing the operations and/or processing performed by a base station (eg, a base station in a roaming network of a UE) in the method provided by the present application.
  • a base station eg, a base station in a roaming network of a UE
  • the present application also provides a computer-readable storage medium, where computer codes are stored in the computer-readable storage medium, and when the computer codes are run on the computer, the computer is made to perform the operations performed by the terminal device in the method provided by the present application and/or the terminal device. or processing.
  • the present application also provides a computer-readable storage medium, where computer codes are stored in the computer-readable storage medium, and when the computer codes are executed on the computer, the computer executes the operations and/or operations performed by the AMF in the methods provided by the present application. deal with.
  • the present application also provides a computer-readable storage medium, where computer code is stored in the computer-readable storage medium, and when the computer code runs on the computer, the computer executes the method provided in the present application by a base station (such as a roaming network of a UE) operations and/or processing performed by the base station in the .
  • a base station such as a roaming network of a UE
  • the present application also provides a computer program product, the computer program product includes computer code or computer program, when the computer code or computer program is run on a computer, the operation performed by the terminal device in the method provided by the present application and/or Processing is executed.
  • the present application also provides a computer program product, the computer program product includes computer code or computer program, when the computer code or computer program is run on a computer, the operation and/or processing performed by the AMF in the method provided by the present application is made. be executed.
  • the present application also provides a computer program product, the computer program product includes computer code or computer program, when the computer code or computer program is run on a computer, the method provided by the present application is executed by a base station (such as in a roaming network of a UE) The operations and/or processes performed by the base station) are performed.
  • a base station such as in a roaming network of a UE
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the technical effects of the solutions provided by the embodiments of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium.
  • a computer-readable storage medium includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned readable storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, etc. that can store program codes medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Alarm Systems (AREA)

Abstract

本申请公开了一种通信方法及装置，该方法包括：UE向AMF发送注册请求消息，该注册请求消息包括指示信息，该指示信息指示是否处于灾难场景下；AMF接收该注册请求消息，根据指示信息和负载情况，向UE发送注册响应消息；该UE接收该注册响应消息。本申请提供的方法可以明确指示是否处于灾难场景，提供信息交互的效率。

Description

通信方法及装置
本申请要求于2021年02月10日提交中国专利局、申请号为202110184233.1、申请名称为“通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
在移动通信系统中，终端设备需要接入网络时，会向相关网元如接入与移动性管理功能(access and mobility management function，AMF)发送注册请求消息，从而使得AMF获得该注册请求消息，进而确定是否允许UE接入相关网络，如AMF对应的网络。
由此可见，如何通过注册请求消息明确指示相关信息亟待解决。
发明内容
本申请提供一种通信方法及装置，通过指示信息，可有效指示是否处于灾难场景下，提高信息交互的效率。
第一方面，本申请实施例提供一种通信方法，所述方法包括：
终端设备向接入与移动性管理功能(access and mobility management function，AMF)(也可以称为接入与移动性管理网元等)发送注册请求消息，所述注册请求消息包括指示信息，所述指示信息指示是否处于灾难场景下；所述UE接收来自所述AMF的注册响应消息。
本申请实施例中，指示信息指示是否处于灾难场景下，也可以理解为：指示信息用于指示终端设备(如可以简称为UE)是否处于灾难场景下。一般的，当处于灾难场景时，与UE对应的归属地公共陆地移动网络(home public land mobile network，HPLMN)常常会被破坏，使得UE无法有效接入该HPLMN。该情况下，为尽量避免业务中断，UE就需要漫游到其他网络如漫游PLMN，由此UE需要与AMF交互，从而来保证其能够接入漫游PLMN。
本申请实施例提供的方法，注册请求消息中通过包括指示信息，一方面，使得AMF明确获知UE是否处于灾难场景下，从而提高了信息交互的效率；另一方面，还可以使得AMF获知UE之所以接入到漫游网络(如漫游PLMN，或与AMF对应的网络)的原因。另外，如果注册请求消息不包括该指示信息，那么AMF可能就无法区分是本地用户发送的注册请求消息，还是处于灾难场景下的UE发送的注册请求消息，从而很可能会影响AMF后续的注册过程。
在一种可能的实现方式中，所述指示信息为第一值，所述指示信息指示所述终端设备处于所述灾难场景下；所述指示信息为第二值，所述指示信息指示所述终端设备不处于所述灾难场景下。
示例性的，第一值可以为1，第二值可以为0。
本申请实施例提供的方法，通过1比特的信息，就可以使得AMF获知UE是否处于灾难场景，还能够有效兼容UE处于灾难场景下，与UE不处于灾难场景下的注册流程。
在一种可能的实现方式中，所述注册请求消息还包括注册类型，所述注册类型包括：初始注册(initial registration)、移动性注册(mobility registration updating)、周期性注册(periodic  registration updating)或紧急注册(emergency registration)中的任一项。
第二方面，本申请实施例提供一种通信方法，所述方法包括：
AMF接收来自终端设备的注册请求消息，所述注册请求消息包括指示信息，所述指示信息指示是否处于灾难场景下；所述AMF根据所述指示信息和负载情况，向所述终端设备发送注册响应消息。
本申请实施例中，注册请求消息中通过包括指示信息，可使得AMF根据该指示信息以及其负载情况向UE发送注册响应消息。从而使得AMF可以结合UE实际所处的场景，对该UE进行不同的处理。例如，AMF可以结合UE所处的场景，向UE发送注册接受消息或注册拒绝消息。
在一种可能的实现方式中，所述AMF根据指示信息和负载情况，向所述终端设备发送注册响应消息，包括：所述AMF根据所述指示信息确定门限；以及所述AMF根据所述负载情况和所述门限，向所述UE发送注册接受消息或注册拒绝消息。
本申请实施例中，负载情况可以包括AMF的负载情况，或者AMF对应的网络的负载情况。
在一种可能的实现方式中，所述指示信息指示处于灾难场景下，所述门限为第一门限；所述指示信息指示不处于灾难场景下，所述门限为第二门限。
本申请实施例中，AMF可以根据UE是否处于灾难场景，来确定不同的门限。从而根据该AMF的负载情况向UE发送注册接受消息或注册拒绝消息，使得AMF可以根据UE所处的场景对UE采用不同的控制手段。
第三方面，本申请实施例提供一种通信方法，所述方法包括：
终端设备接收来自漫游网络中的基站的系统消息，所述系统消息包括所述最大等待时长；所述终端设备根据所述终端设备的标识和最大等待时长的模确定发送注册请求消息的等待时长；在所述等待时长超时后，所述终端设备向AMF站发送所述注册请求消息。
本申请实施例中，最大等待时长即用于确定UE发送注册请求消息的等待时长。如该最大等待时长还可以理解为UE所等待的最大时长。例如，该最大等待时长还可以称为入网等待最大时间(inbound-waiting-max-time)，或者，灾难漫游等待范围(disaster roaming wait range)，或者，漫游等待最大时长等，本申请实施例对于该最大等待时长的具体名称不作限定。
本申请实施例提供的方法，通过UE的标识和最大等待时长的模来确定等待时长，可以改善大量UE同时接入AMF对应的网络的情况，从而在尽可能减少计算量的基础上保证了UE接入的随机性。
在一种可能的实现方式中，所述终端设备向AMF发送所述注册请求消息，包括：
若所述终端设备确定处于灾难场景下，所述终端设备向所述AMF发送所述注册请求消息。
在一种可能的实现方式中，所述注册请求消息包括指示信息，所述指示信息指示处于所述灾难场景下。
本申请实施例提供的方法，通过将指示信息与上述等待时长结合，可使得UE处于灾难场景下，尽可能避免同一时间大量UE同时接入网络，而导致网络更加拥塞的情况。
第四方面，本申请实施例提供一种通信方法，所述方法包括：
漫游网络中的基站根据负载情况确定最大等待时长；
所述基站向终端设备发送系统消息，所述系统消息包括所述最大等待时长。
本申请实施例提供的方法，当UE需要接入漫游网络时，该漫游网络中的基站通过根据负载情况确定最大等待时长，可有效均衡UE接入该漫游网络的时间，从而改善大量UE接入漫游网络的情况。
第五方面，本申请实施例提供一种通信方法，所述方法包括：
终端设备向接入与移动性管理网元AMF发送注册请求消息，以及接收来自所述AMF的注册拒绝消息；所述终端设备根据所述注册拒绝消息，确定列表，所述列表包括灾难场景下不允许接入的所述AMF对应的网络。
本申请实施例提供的方法，通过上述列表，可使得UE再接收到AMF的注册拒绝消息后，将该AMF对应的网络接入该列表。从而，改善了UE重复接入该AMF的情况，有效改善了网络拥塞恶化的情况。例如，一般的，UE接收到注册拒绝消息后，UE会将AMF对应的网络接入其他列表，但是，在灾难场景下，会重新允许UE接入该其他AMF对应的网络。如果应用上述方法，会导致UE即使是接收到了注册拒绝消息，仍不断地去接入上述已被拒绝的网络，从而不仅会影响UE的通信状况，而且还会导致网络拥塞情况恶化。
在一种可能的实现方式，所述网络包括：公共陆地移动网络PLMN、跟踪区或部分跟踪区中的任一项或多项。
第六方面，本申请实施例提供一种通信装置，用于执行第一方面或第一方面的任意可能的实现方式中的方法。或者，通信装置用于执行第二方面或第二方面的任意可能的实现方式中的方法。或者，通信装置用于执行第三方面或第三方面的任意可能的实现方式中的方法。或者，通信装置用于执行第四方面中的方法。或者，通信装置用于执行第五方面或第五方面的任意可能的实现方式中的方法。
如上述通信装置可以包括收发单元和处理单元。对于收发单元和处理单元的具体描述还可以参考下文示出的装置实施例。
第七方面，本申请实施例提供一种通信装置，该通信装置包括处理器，用于执行上述第一方面、第二方面、第三方面、第四方面、第五方面或任意可能的实现方式所示的方法。或者，该处理器用于执行存储器中存储的程序，当该程序被执行时，上述第一方面、第二方面、第三方面、第四方面、第五方面或任意可能的实现方式所示的方法被执行。
在执行上述方法的过程中，上述方法中有关发送信息的过程，可以理解为由处理器输出上述信息的过程，或者处理器接收输入的上述信息的过程。在输出上述信息时，处理器将该上述信息输出给收发器，以便由收发器进行发射。该上述信息在由处理器输出之后，还可能需要进行其他的处理，然后才到达收发器。类似的，处理器接收输入的上述信息时，收发器接收该上述信息，并将其输入处理器。更进一步的，在收发器收到该上述信息之后，该上述信息可能需要进行其他的处理，然后才输入处理器。
基于上述原理，举例来说，前述方法中提及的发送注册请求消息可以理解为处理器输出该注册请求消息。又如，前述方法中提及的接收注册请求消息可以理解为处理器接收输入的注册请求消息。
对于处理器所涉及的发射、发送和接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则均可以更加一般性的理解为处理器输出和接收、输入等操作，而不是直接由射频电路和天线所进行的发射、发送和接收操作。
在实现过程中，上述处理器可以是专门用于执行这些方法的处理器，也可以是执行存储器中的计算机指令来执行这些方法的处理器，例如通用处理器。上述存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(Read Only Memory，ROM)，其可以与处理器集 成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。可理解，对于处理器和存储器的说明同样适用于下文示出的第六方面，为便于赘述第六方面不再详述。
在一种可能的实现方式中，存储器位于上述通信装置之外。
在一种可能的实现方式中，存储器位于上述通信装置之内。
本申请实施例中，处理器和存储器还可以集成于一个器件中，即处理器和存储器还可以被集成在一起。在一种可能的实现方式中，通信装置还包括收发器，该收发器，用于接收信号或发送信号。
可理解，对于各个通信装置的具体说明还可以参考下文实施例，这里不再详述。
第八方面，本申请实施例提供一种通信装置，该通信装置包括逻辑电路和接口，所述逻辑电路和所述接口耦合；
在本申请的一些实施例中，所述通信装置可以用于执行UE执行的步骤。例如，所述接口，用于输出注册请求消息以及输入注册响应消息。又例如，所述逻辑电路，用于确定发送注册请求消息的等待时长。又例如，所述逻辑电路，用于确定处理灾难场景下。
在本申请的另一些实施例中，所述通信装置可以用于执行AMF执行的步骤。例如，所述接口，用于输入注册请求消息以及输出注册响应消息。又例如，所述逻辑电路，用于根据指示信息和负载情况，确定注册响应消息等。
在本申请的又一些实施例中，所述通信装置可以用于执行基站执行的步骤。例如，所述逻辑电路，用于根据负载情况确定最大等待时长，所述接口，用于输出系统消息等。
可理解，关于注册请求消息、注册响应消息、指示信息、等待时长、最大等待时长以及UE的标识等的描述，可以参考上述第一方面至第五方面的描述；或者，还可以参考下文示出的各个实施例，这里不再详述。
第九方面，本申请实施例提供一种计算机可读存储介质，该计算机可读存储介质用于存储计算机程序，当其在计算机上运行时，使得上述第一方面或第一方面的任意可能的实现方式所示的方法被执行；或者，使得上述第二方面或第二方面的任意可能的实现方式所示的方法被执行；或者，上述第三方面或第三方面的任意可能的实现方式所示的方法被执行；或者，上述第四方面所示的方法被执行；或者，上述第五方面或第五方面的任意可能的实现方式所示的方法被执行。
第十方面，本申请实施例提供一种计算机程序产品，该计算机程序产品包括计算机程序或计算机代码，当其在计算机上运行时，使得上述第一方面或第一方面的任意可能的实现方式所示的方法被执行；或者，使得上述第二方面或第二方面的任意可能的实现方式所示的方法被执行；或者，上述第三方面或第三方面的任意可能的实现方式所示的方法被执行；或者，上述第四方面所示的方法被执行；或者，上述第五方面或第五方面的任意可能的实现方式所示的方法被执行。
第十一方面，本申请实施例提供一种计算机程序，该计算机程序在计算机上运行时，上述第一方面或第一方面的任意可能的实现方式所示的方法被执行；或者，使得上述第二方面或第二方面的任意可能的实现方式所示的方法被执行；或者，上述第三方面或第三方面的任意可能的实现方式所示的方法被执行；或者，上述第四方面所示的方法被执行；或者，上述第五方面或第五方面的任意可能的实现方式所示的方法被执行。
第十二方面，本申请实施例提供一种无线通信系统，该无线通信系统包括UE和AMF，所述UE用于执行上述第一方面或第一方面的任意可能的实现方式所示的方法，所述AMF用 于执行上述第二方面或第二方面的任意可能的实现方式所示的方法。或者该无线通信系统包括UE和基站，所述UE用于执行上述第三方面或第三方面的任意可能的实现方式所示的方法，所述基站用于执行上述第四方面所示的方法；或者，该无线通信系统包括UE和与所述UE连接的AMF，所述UE用于执行上述第五方面或第五方面的任意可能的实现方式所示的方法。
附图说明
图1是本申请实施例提供的一种通信系统示意图；
图2至图5是本申请实施例提供的一种通信方法的流程示意图；
图6至图8是本申请实施例提供的一种通信装置的结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地描述。
本申请的说明书、权利要求书及附图中的术语“第一”和“第二”等仅用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们的任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备等，没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元等，或可选地还包括对于这些过程、方法、产品或设备等固有的其它步骤或单元。
在本文中提及的“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本申请的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员可以显式地和隐式地理解的是，本文所描述的实施例可以与其它实施例相结合。
在本申请中，“至少一个(项)”是指一个或者多个，“多个”是指两个或两个以上，“至少两个(项)”是指两个或三个及三个以上，“和/或”，用于描述关联对象的关联关系，表示可以存在三种关系，例如，“A和/或B”可以表示：只存在A，只存在B以及同时存在A和B三种情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指这些项中的任意组合。例如，a，b或c中的至少一项(个)，可以表示：a，b，c，“a和b”，“a和c”，“b和c”，或“a和b和c”。
本申请提供的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、物联网(internet of things，IoT)系统、窄带物联网系统(narrow band-internet of things，NB-IoT)、无线保真(wireless fidelity，WiFi)、第五代(5th generation，5G)通信系统或新无线(new radio，NR)以及未来的其他通信系统等。
本申请提供的技术方案还可以应用于机器类通信(machine type communication，MTC)、机器间通信长期演进技术(Long Term Evolution-machine，LTE-M)、设备到设备(device-todevice，D2D)网络、机器到机器(machine to machine，M2M)网络、物联网(internet of things，IoT)网络或者其他网络。其中，IoT网络例如可以包括车联网。其中，车联网系统中的通信方式统称为车到其他设备(vehicle to X，V2X，X可以代表任何事物)，例如，该 V2X可以包括：车辆到车辆(vehicle to vehicle，V2V)通信，车辆与基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。
以下详细介绍本申请涉及的术语。
1、终端设备
本申请中的终端设备是一种具有无线收发功能的装置。终端设备可以经无线接入网(radio access network，RAN)中的接入网设备(或者也可以称为接入设备)与一个或多个核心网(core network，CN)设备(或者也可以称为核心设备)进行通信。
终端设备也可以称为用户设备(user equipment，UE)、接入终端、终端(terminal)、用户单元(subscriber unit)、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、用户代理或用户装置等。在一种可能的实现方式中，终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。在一种可能的实现方式中，终端设备可以是具有无线通信功能的手持设备、车载设备、可穿戴设备、物联网、车联网中的终端、第五代(5th generation，5G)网络以及未来网络中的任意形态的终端设备等，本申请对此不作限定。
可理解，本申请示出的终端设备不仅可以包括车联网中的车(如整车)、而且还可以包括车联网中的车载设备或车载终端等，本申请对于该终端设备应用于车联网时的具体形态不作限定。
可理解，本申请示出的终端设备与终端设备之间还可以通过设备到设备(device to device，D2D)、车与任何事物(vehicle-to-everything，V2X)或机器到机器(machine to machine，M2M)等技术进行通信，本申请对于终端设备与终端设备之间的通信方法不作限定。
2、AMF
随着移动带宽接入服务的扩展，移动网络也会随之发展以便更好地支持多样化的商业模式，满足更加多样化的应用业务以及更多行业的需求。例如，为了给更多的行业提供更好、更完善的服务，5G网络相对于4G网络做了网络架构调整。如5G网络将4G网络中的移动管理实体(mobility management entity，MME)进行拆分，拆分为包括接入与移动性管理功能(access and mobility management function，AMF)和会话管理功能(session management function，SMF)等多个网元(或也可以称为网络功能)。
本申请所示的AMF是由PLMN提供的控制面网络功能，负责UE接入PLMN的接入控制和移动性管理，例如包括移动状态管理，分配用户临时身份标识，认证和授权用户等功能。因此，随着移动网络的发展，即使AMF可能会演进为其他形式或名称等，但是只要可以实现本身本申请所示的方法，均属于本申请的保护范围之内。
3、基站
基站可以是一种部署在无线接入网中，为终端设备提供无线通信服务的装置。本申请所示的基站还可以称为接入网设备、接入设备或RAN设备等。
示例性的，本申请所示的基站可以包括但不限于：5G系统中的下一代基站(next generation node basestation，gNB)、LTE系统中的演进型基站(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(home evolved nodeB，或home node B，HNB)、基带单元(base band unit，BBU)、传输接收点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、小基站设备(pico)、移动交换中心，或者未来网络 中的网络设备等。该基站还可以为D2D、V2X或M2M中承载基站功能的设备等。在不同的无线接入技术的系统中，具备接入网设备功能的设备的名称可能会有所不同。
可选的，在基站的一些部署中，基站可以包括集中式单元(centralized unit，CU)和分布式单元(distributed unit，DU)等。在基站的另一些部署中，CU还可以划分为CU-控制面(control plane，CP)和CU-用户面(user plan，UP)等。在基站的又一些部署中基站还可以是开放的无线接入网(openradioaccessnetwork，ORAN)架构等，本申请对于基站的具体部署方式不作限定。
基于上述所示的UE、AMF和基站，本申请实施例提供了一种通信系统，如图1所示。图1是本申请实施例提供的一种通信系统的示意图。如图1所示，该通信系统可以包括至少一个基站，至少一个终端设备，如图1中的UE1至UE6，以及AMF。可理解，关于AMF、UE以及基站的具体说明可以参考上文，这里不再赘述。
示例性的，UE之间可以直接通信。例如可以通过D2D技术实现UE之间的直接通信。如图1所示，UE4与UE5之间、UE4与UE6之间，可以利用D2D技术直接通信。UE4或UE6可以单独或同时与UE5进行通信。又例如，UE4至UE6也可以分别与基站通信。如UE4或UE6可以直接与基站通信，也可以间接地与基站通信，如UE6可以经由UE5与基站通信。应理解，图1示例性地示出了一个基站和多个UE，以及各通信设备之间的通信链路。可选地，该通信系统可以包括多个基站，并且每个基站的覆盖范围内可以包括其它数量的UE，例如更多或更少的UE。本申请对此不做限定。
可选的，图1所示的通信系统还可以包括统一数据管理(unified data management，UDM)网元或认证服务器功能(authentication server function，AUSF)网元等，本申请实施例对于该通信系统的具体结构不作限定。示例性的，统一数据管理UDM是由运营商提供的控制面功能，负责存储PLMN中签约用户的用户永久标识符(subscriber permanent identifier，SUPI)、安全上下文(security context)、签约数据等信息。认证服务器功能AUSF是由运营商提供的控制面功能，通常用于认证，如终端设备(签约用户)与PLMN之间的认证。可选地，该通信系统还可以包括网络控制器、会话管理功能(session management function，SMF)等其他网元，本申请实施例不限于此。
如果UE当前接入的HPLMN网络发生了灾害等突发情况，为减少UE业务的中断，UE需要漫游到其它可以提供业务的PLMN(即使用户没有开通漫游协议)上。当故障解除时，该UE可以再转移回原PLMN(如上述HPLMN)。也就是说，当处于灾难场景时，与UE的HPLMN常常会被破坏，使得UE无法有效接入该HPLMN，会导致UE业务的中断。为保证UE业务的连续性，UE可以向提供灾难漫游服务的PLMN注册。
鉴于此，本申请提供一种通信方法及装置，使得接收UE发送的注册请求消息的AMF明确获知UE是否处于灾难场景下，提高信息交互的效率。同时，通过本申请提供的通信方法，还能够有效减少灾难场景下，UE业务的中断。关于本申请所适用的通信系统可以如上文所示(如图1)，这里不再详述。
图2是本申请实施例提供的一种通信方法的流程示意图，如图2所示，该方法包括：
201、UE向AMF发送注册请求消息，该注册请求消息包括指示信息，该指示信息用于指示是否处于灾难场景下。相应的，AMF接收该注册请求消息。
当灾难发生时会对基站或核心网网元等造成损害，从而导致UE与网络发生中断，即灾害会导致通信服务中断，例如：地震等自然灾害会导致一些无线接入网设备发生火灾或停电， 由此会导致无线接入网和核心网之间的小区突然消失或没有路由。人为的灾难，如安装有缺陷的软件或管理不当的证书，可能会导致无线接入网的异常行为，导致网络内的用户不能交换信令或数据。可理解，本申请实施例所示的灾难场景还可以称为灾难漫游(disaster roaming)场景等，本申请实施例对其具体名称不作限定。
可理解，本申请实施例对于UE如何确定其处于灾难场景不作限定。示例性的，可以是UE已经无法接入原PLMN，由此，UE获知其处于灾难场景。或者，可以是UE与原网络发生中断，重新尝试接入网络如漫游网络时，根据漫游网络中的基站广播消息获知其处于灾难场景。以上所示的UE确定其处于灾难场景下的方法仅为示例，不应将其理解为对本申请实施例的限定。由此，UE可以向漫游网络的AMF发送注册请求消息。
本申请实施例中，指示信息指示是否处于灾难场景，可以理解为：指示信息指示UE是否处于灾难场景，或者，指示信息指示UE的HPLMN是否处于灾难场景，或者，指示信息指示UE对应的原网络是否处于灾难场景，或者，指示信息指示是否是由处于灾难场景下发起的注册请求消息，或者，指示信息指示UE是否是处于灾难场景下而发起的注册请求消息等，本申请实施例对此不作限定。也就是说，通过指示信息可以表明上述注册请求消息是否属于灾难场景下的注册。可理解，上述指示信息还可以称为灾情指示(disaster condition indication)等，本申请实施例对其具体名称不作限定。
示例性的，指示信息为第一值时，指示信息指示处于灾难场景下。指示信息为第二值时，指示信息指示不处于所述灾难场景下。如可以通过1比特的指示信息来指示是否处于灾难场景。举例来说，第一值可以为1，第二值为0。也就是说，UE确定其是因为灾难而从其他网络漫游到漫游网络后，该UE可以向AMF发送携带指示信息的注册请求消息，该指示信息为第一值。通过1比特的信息，就可以使得AMF获知UE是否处于灾难场景，还能够有效兼容UE处于灾难场景下，与UE不处于灾难场景下的注册流程。当然，对于指示信息的具体比特位，本申请实施例不作限定。
示例性的，注册请求消息中所包括的内容可以如表1所示。可理解，以下所示的注册请求消息中包括的内容仅为示例，不应将其理解为对本申请实施例的限定。
表1
Figure PCTCN2022075637-appb-000001
Figure PCTCN2022075637-appb-000002
在一种可能的实现方式中，所述注册请求消息还包括注册类型，所述注册类型包括：初始注册(initial registration)、移动性注册更新(mobility registration updating)、周期性注册更新(periodic registration updating)或紧急注册(emergency registration)中的任一项。
示例性的，可以通过3个比特位来表示注册类型，如表2所示。可理解，表2所示的比特位与注册类型之间的关系仅为示例。
表2
比特(bits) 注册类型
001 初始注册
010 移动性注册更新
011 周期性注册更新
100 紧急注册
111 预留(reserved)
本申请实施例提供中，结合指示信息和注册类型，不仅可以使得AMF获知UE处于灾难场景，而且还可以更好地获知上述注册请求消息是在灾难场景下的初始注册、移动性注册更新、周期性注册更新还是紧急注册。
示例性的，表3是通过增加灾难漫游初始注册(disaster roaming initial registration)使得AMF获知UE处于灾难场景。表4是通过增加灾难漫游注册(disaster roaming registration)使得AMF获知UE处于灾难场景。然而，UE处于灾难场景下，发起的注册请求消息的类型 可能不局限于上述灾难漫游初始注册。或者，灾难漫游注册可能会与上述初始注册、移动性注册更新、周期性注册更新或紧急注册存在语义冲突。如表3和表4所示的方法，当UE初始注册时，无法有效区分注册请求消息中包括初始注册的类型，还是灾难初始注册的类型。因为从语义上初始注册可以包含灾难初始注册，因此会存在逻辑范围的不一致。
然而，本申请实施例通过在注册请求消息中增加指示信息，相对于通过表3或表4所示的注册类型来说，不仅仅可以指示灾难场景下更多的注册类型，使得AMF可以针对不同类型的注册请求消息采用不同的注册接入控制方法。示例性的，初始注册时，AMF可以进行鉴权操作或分配跟踪区等。又例如，移动性注册更新时，AMF可以不进行鉴权等。
而且还能够使得AMF明确获知UE是否处于灾难场景。即使得AMF能够有效区分其所接收到的注册请求消息是由哪种类型的UE发送的，如AMF能够有效区分出：本网接入UE(也可以称为本网接入用户或本网接入者等)、国外漫游UE(也可以称为国外漫游用户或国外漫游者等)或灾难漫游UE(也可以称为灾难漫游用户或灾难漫游者)。假设注册请求消息中不包括指示信息，则AMF很难知道该注册请求消息是一个在灾难场景下漫游过来的UE用户发起的，还是漫游签约的UE发起的。从而会导致HPLMN鉴权后，AMF才能知道UE实际没有签约，而是灾难场景下漫游的UE，进而会影响AMF对灾难场景下的UE所应该采取的控制策略(如AMF采取的控制策略会被延迟)。
表3
比特(bits) 注册类型
001 初始注册
010 移动性注册更新
011 周期性注册更新
100 紧急注册
101 灾难漫游初始注册
111 预留
表4
比特(bits) 注册类型
001 初始注册
010 移动性注册更新
011 周期性注册更新
100 紧急注册
101 灾难漫游注册
111 预留
可理解，如果UE发送注册请求消息时，该注册请求消息中未包括上述指示信息，则可以表示不处于灾难场景。
202、AMF根据指示信息和负载情况，向UE发送注册响应消息。相应的，UE接收该注册响应消息。
上述负载情况可以包括AMF的负载情况，或者，AMF对应的网络的负载情况。至于该AMF如何获知其对应的网络的负载情况，本申请实施例不作限定。
本申请实施例中，注册响应消息包括注册接受消息或注册拒绝消息。示例性的，AMF根据指示信息和负载情况确定注册接受消息或注册拒绝消息，从而向UE发送注册接受消息或 注册拒绝消息。例如，AMF可以根据指示信息确定门限，然后根据负载情况和该门限确定注册接受消息或注册拒绝消息。如指示信息指示处于灾难场景下，上述门限为第一门限(也可以称为灾难负载门限等)。又如指示信息指示不处于灾难场景下，则上述门限为第二门限(也可以称为非灾难负载门限等)。
也就是说，本申请实施例可以根据是否处于灾难场景的不同，来确定不同的门限。从而可以使得AMF根据相应的门限以及负载情况采取不同的控制手段。如AMF收到注册请求消息后，如果发现指示信息为第一值如1，则可以根据第一门限来判断是否接受该UE的注册。例如，负载情况超过第一门限，则可以拒绝该注册请求消息，否则接受该注册请求消息。如果发现指示信息为第二值如0，或没有携带该指示信息，则说明是本网UE或者是漫游签约UE，则可以根据第二门限来判断是否接受该UE的注册。
可理解，本申请实施例对于上述第一门限和第二门限的具体标准不作限定。示例性的，负载情况可以用接入UE的数量来衡量，则第一门限和第二门限可以以接入UE的标准来设置。又如负载情况可以用网络的负载(或AMF的负载)百分比来衡量，则第一门限和第二门限可以以网络的负载百分比来设置。本申请实施例对于负载情况、第一门限和第二门限的具体标准不作限定。
可选的，第一门限可以大于第二门限。该情况下，当处于灾难场景时，可以优先保证处于灾难场景下的UE接入网络。例如，通过保证处于灾难场景下的UE优先接入网络，可使得该UE能够快速或及时地能够与外界进行通信等。可选的，第一门限可以小于第二门限。该情况下，由于处于灾难场景下的UE为漫游非签约UE，因此为保证本网UE以及漫游签约UE的通信质量，则第一门限可以小于第二门限。对于第一门限和第二门限的大小关系，本申请实施例不作限定。
本申请实施例中，注册请求消息中通过包括指示信息，一方面，使得AMF明确获知UE是否处于灾难场景下，从而提高了信息交互的效率；另一方面，还可以使得AMF获知UE之所以接入到漫游网络(如漫游PLMN，或与AMF对应的网络)的原因。
图3是本申请实施例提供的一种通信方法的流程示意图，如图3所示，该方法包括：
301、漫游网络中的基站根据负载情况确定最大等待时长。
上述最大等待时长还可以称为入网等待最大时间(inbound-waiting-max-time)，或者，灾难漫游等待范围(disaster roaming wait range)，或者，漫游等待最大时长等，本申请实施例对于该最大等待时长的具体名称不作限定。
本申请实施例中，负载情况可以为基站的负载情况，或者基站对应的网络的负载情况。基站根据负载情况确定最大等待时长，也就是说，基站可以根据负载情况来动态调整该最大等待时长。例如，负载情况越高时(也可以理解为负载越重时)，最大等待时长越大；负载情况越低时(也可以理解为负载越轻时)，最大等待时长越小。通过将负载情况与最大等待时长相关联，可以有效改善基站的负载情况，或者改善网络的负载情况。即保证了UE在不同的时间范围内均匀分布，如在负载轻时UE可以短时密集接入，而在负载重时，UE可以长时稀疏接入，能够有效改善网络的拥塞情况。
可理解，对于负载与最大等待时长的具体关系，本申请实施例不作限定。同样的，对于最大等待时长的衡量单位也不作限定。例如，最大等待时长可以以s为单位来衡量，如5s或255s。
302、基站向UE发送系统消息，该系统消息包括最大等待时长。相应的，UE接收该系 统消息。
示例性的，系统消息可以包括系统信息块(system information block)1，或者其他SIB(如下文称为SIB-vX)等，本申请实施例对此不作限定。
示例性的，SIB1的信令格式可以如下所示：
SIB1-v17XX-IEs::＝           SEQUENCE{
inbound-waiting-max-time    INTEGER(1..255)    OPTIONAL}
其中，SIB1-v17XX-IEs表示系统消息的版本(version，v)号，inbound-waiting-max-time表示最大等待时长，INTEGER表示最大等待时长的具体取值。
示例性的，SIB-vX的信令格式可以如下所示：
SIB-vX-IEs::＝               SEQUENCE{
inbound-waiting-max-time    INTEGER(1..255)OPTIONAL}
可理解，SIB-vX-IEs表示系统消息的版本号，inbound-waiting-max-time表示最大等待时长，INTEGER表示最大等待时长的具体取值。
如最大等待时长包含于SIB-vX中时，若系统消息未包括该SIB-vX，则说明UE可以立即发送注册请求消息。即UE不需要等待时，系统消息中可以不包括该SIB-vX。
303、UE根据UE的标识和最大等待时长的模确定发送注册请求消息的等待时长。
本申请实施例中，UE的标识可以包括第五代系统(5th generation system，5GS)移动身份(5GS mobile identity)，如可以包括UE的加密的签约标识(subscription concealed identifier，SUCI)、全球唯一临时UE标识(globally unique temporary UE identity，GUTI)、用户永久标识(subscription permanent identifier，SUPI)、国际移动设备识别码(international mobile equipment identity，IMEI)或国际移动用户识别码(international mobile subscriber identity，IMSI)等。例如，以IMSI为例，UE可以根据IMSI和最大等待时长确定发送注册请求消息的等待时长。例如，最大等待时长为30，UE1的IMSI为460011234567891，UE2的IMSI为460011234567898。则对IMSI和最大等待时长取模(如IMSI mod(inbound-waiting-max-time))，如460011234567891 mod 30＝21，460011234567898 mod 30＝28。则UE1在发起注册请求消息之前需要等待21s，UE2在发起注册请求消息之前需要等待28s。由于UE1和UE2的等待时长不同，可以有效避免UE1和UE2同时发起注册请求而造成网络拥塞。
可理解，UE可以在驻留小区时，通过计时器来对注册请求消息的等待时长进行计时。或者，UE还可以在获取到漫游网络中的基站的广播消息时，通过计时器来对注册请求消息的等待时长进行计时。本申请实施例对于UE是何时开始计时的不作限定。
本申请实施例中，由于IMSI可以在每个UE中是唯一的(类似电话号码)，因此从统计上看它在网络中是随机均匀分布的。而随机数mod最大等待时长，保证了取模之后的结果在0到最大等待时长也是随机均匀分布的，保证了UE在不同的时间范围内均匀分布。
304、在等待时长超时后，UE向AMF发送注册请求消息。相应的，该AMF接收该注册请求消息。
本申请实施例中，对于注册请求消息的具体内容不作限定。也就是说，本申请实施例提供的方法，既可以应用于不处于灾难场景，如上述UE可以是漫游签约UE；又可以应用于处于灾难场景，如上述UE可以是灾难漫游UE。对于不处于灾难场景的具体说明，可以参考相关标准或协议等，这里不再赘述。
例如，UE确定其处于灾难场景下，UE向AMF发送注册请求消息。对于UE如何确定其处于灾难场景下的具体描述，可以参考图2所示的方法，这里不再赘述。该情况下，注册 请求消息中可以不包括指示信息，如注册请求消息中可以包括注册类型。
又例如，注册请求消息中可以包括指示信息，由此，通过指示信息明确指示是否处于灾难场景。对于处于灾难场景的具体说明，如可以参考上文图2所示的方法。也就是说，图3所示的方法可以与上述图2所示的方法结合。对于指示信息等的具体说明，这里不再赘述。同时，对于AMF根据指示信息和负载情况向UE发送注册响应消息的具体说明，也不再赘述。
本申请实施例提供的方法，当UE需要接入漫游网络时，该漫游网络中的基站通过根据负载情况确定最大等待时长，可有效均衡UE接入该漫游网络的时间，从而改善大量UE接入漫游网络的情况。同时，通过UE的标识和最大等待时长的模来确定等待时长，可以改善大量UE同时接入AMF对应的网络的情况，从而在尽可能减少计算量的基础上保证了UE接入的随机性。
图4是本申请实施例提供的一种通信方法的流程示意图，如图4所示，该方法包括：
401、终端设备向AMF发送注册请求消息，AMF接收该注册请求消息。
402、AMF向UE发送注册拒绝消息，UE接收该注册拒绝消息。
可理解，关于步骤401和步骤402的具体说明，可以参考相关标准或协议等，本申请实施例对于注册请求消息和注册拒绝消息不作限定。
403、UE根据注册拒绝消息，确定列表，该列表包括灾难场景下不允许接入的所述AMF对应的网络。
本申请实施例中，UE接收到注册拒绝消息之后，可以将不允许其接入的AMF对应的网络加入该列表中，从而避免UE不断重复接入该网络。示例性的，上述注册请求消息可以是UE所发起的初始注册(如UE初始尝试接入漫游网络中的AMF)，由此，UE可以将其尝试初始接入的AMF对应的网络加入该列表。示例性的，上述注册请求消息还可以不是UE初始发起的注册，而是UE已经被拒绝一次或多次后，重新发起的注册请求消息。该情况下，由于UE已经尝试多次接入AMF失败，因此，UE可以将该AMF对应的网络接入上述列表。有效避免UE再次尝试接入，再次被拒绝，导致UE浪费资源或时间的情况。
可理解，上述网络包括：PLMN、跟踪区或部分跟踪区中的任一项或多项。例如，列表包括灾难禁止PLMN列表(disaster forbidden PLMN List)、灾难禁止跟踪区列表(disaster forbidden tracking areas list)(也可以称为灾难禁止跟踪区的漫游列表(disaster forbidden tracking areas of roaming list))或灾难禁止部分跟踪区的列表(disaster forbidden tracking areas for regional provision of list)(也可以称为灾难禁止部分跟踪区的服务列表(disaster forbidden tracking areas for regional provision of service list))。
在一种可能的实现方式中，本申请实施例提供的方法还可以结合图2所示的方法。如注册请求消息中包括指示信息，从而AMF可以根据指示信息和负载情况，向UE发送注册拒绝消息。
在一种可能的实现方式中，本申请实施例提供的方法还可以结合图3所示的方法。如漫游网络中的基站根据负载情况确定最大等待时长，向UE发送该最大等待时长。然后UE根据UE的标识和最大等待时长的模确定发送注册请求消息的等待时长，在该等待时长超时后，向AMF发送注册请求消息。
在一种可能的实现方式中，本申请实施例提供的方法还可以结合图2和图3所示的方法。对于图2、图3和图4结合的方法的具体说明，可以参考下文所示的图5，这里先不详述。
一般的，UE接收到注册拒绝消息后，UE会将AMF对应的网络接入其他列表，如相关 标准或协议中的禁止列表(forbidden list)，但是，在灾难场景下，会重新允许UE接入该其他AMF对应的网络。如果应用上述方法，会导致UE即使是接收到了注册拒绝消息，仍不断地去接入上述已被拒绝的网络，从而不仅会影响UE的通信状况，而且还会导致网络拥塞情况恶化。
然而，本申请实施例提供的方法，通过上述列表，可使得UE再接收到AMF的注册拒绝消息后，将该AMF对应的网络接入该列表。从而，改善了UE重复接入该AMF的情况，有效改善了网络拥塞恶化的情况。
可理解，上文所示的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。示例性的，以上所示的各个实施例，相互之间可以结合。如，以上所示的图2和图3的方法可以结合。又例如，以上所示的图2和图4的方法可以结合。又例如，以上所示的图3和图4的方法可以结合。又例如，以上所示的图2、图3和图4的方法可以结合。对于图2至图4的结合的示例可以参考图5所示的方法。
图5是本申请实施例提供的一种通信方法的流程示意图，如图5所示，该方法包括：
501、漫游网络中的基站根据负载情况确定最大等待时长。
502、基站向UE发送系统消息，该系统消息包括最大等待时长。相应的，UE接收该系统消息。
503、UE根据UE的IMSI和最大等待时长的模确定发送注册请求消息的等待时长。
504、在等待时长超时后，UE向AMF发送注册请求消息。相应的，AMF接收该注册请求消息。其中，该注册请求消息包括指示信息，指示信息指示是否处于灾难场景下。
505、AMF根据指示信息和负载情况，向UE发送注册拒绝消息。相应的，UE接收该注册拒绝消息。
506、UE根据注册拒绝消息确定列表，该列表包括灾难场景下不允许接入AMF对应的网络。
可理解，关于图5所示的方法的具体说明，可以参考上述图2至图4，这里不再一一详述。示例性的，对于上述步骤501至步骤504，可以参考上述图3所示的方法。对于步骤504中所示的注册请求消息以及步骤505，可以参考上述图2所示的方法。对于上述步骤506可以参考上述图4所示的方法。
可理解，以上所示的各个实施例中，AMF与UE的HPLMN中的AUSF之间还可以进行鉴权，如AMF在接收到注册请求消息之后，可以向HPLMN中的AUSF发送鉴权请求(authenticate request)，AUSF向HPLMN中的UDM发送鉴权请求，UDM向该AUSF发送鉴权响应，AUSF向AMF发送鉴权响应(authenticate response)，AMF向UE发送鉴权响应。可理解，关于UE与AMF之间的鉴权过程，以及AMF与HPLMN中的AUSF之间的鉴权过程，可以参考相关标准或协议等，本申请实施例对此不作限定。
本申请实施例提供的方法，不仅可以使得漫游网络中的AMF获知UE是否处于灾难场景，还可以使得AMF能够结合UE所处的场景确定是否向UE发送注册拒绝消息，从而，使得UE接收到注册拒绝消息之后，将该AMF对应的网络加入列表，避免UE多次尝试接入，导致资源浪费的情况。
以下将介绍本申请实施例提供的通信装置。
本申请根据上述方法实施例对通信装置进行功能模块的划分，例如，可以对应各个功能 划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面将结合图6至图8详细描述本申请实施例的通信装置。
图6是本申请实施例提供的一种通信装置的结构示意图，如图6所示，该通信装置包括处理单元601和收发单元602。
在本申请的一些实施例中，该通信装置可以是上文示出的终端设备或终端设备中的芯片等。即该通信装置可以用于执行上文方法实施例中由终端设备执行的步骤或功能等。
示例性的，如收发单元602，用于输出注册请求消息，该注册请求消息包括指示信息，该指示信息指示是否处于灾难场景下；收发单元602，还用于输入注册响应消息。
本申请实施例中，收发单元602，用于输出注册请求消息包括：收发单元602，用于向AMF发送注册请求消息。收发单元602，用于输入注册响应消息包括：收发单元602，用于接收来自AMF的注册响应消息。
示例性的，该收发单元602还可以用于执行图2所示的步骤201中的发送步骤，收发单元602还可以用于执行图2所示的步骤202中的接收步骤。又如，收发单元602还可以用于执行图5所示的步骤502中的发送步骤，处理单元601还可以用于执行图5所示的步骤503，收发单元602还可以用于执行图5所示的步骤504中的发送步骤以及步骤505中的接收步骤，处理单元601还可以用于执行图5所示的步骤506。
关于收发单元和处理单元的具体描述，这里不再一一详述。例如，处理单元601，可以通过收发单元602执行上述输出注册请求消息的步骤，以及输入注册响应消息的步骤等。
可理解，本申请实施例中，关于注册请求消息、指示信息、注册类型、灾难场景等的描述，可以参考上文方法实施例(如图2和图5)的介绍，这里不再一一详述。
示例性的，收发单元602，用于输入系统消息，该系统消息包括最大等待时长；处理单元601，用于根据通信装置的标识和最大等待时长确定发送注册请求消息的等待时长；收发单元602，还用于在所述等待时长超时后，输出注册请求消息。
可理解，收发单元602，用于输入系统消息包括：收发单元602，用于接收来自漫游网络中的基站的系统消息。收发单元602，还用于在等待时长超时后，输出注册请求消息包括：收发单元602，还用于在等待时长超时后，向AMF发送注册请求消息。
示例性的，该收发单元602还可以用于执行图3所示的步骤302中的接收步骤，处理单元601还可以用于执行图3所示的步骤303，以及收发单元602还可以用于执行图3所示的步骤304中的发送步骤。
可理解，本申请实施例中，关于系统消息、最大等待时长、通信装置的标识(包括IMSI)、注册请求消息、灾难场景等的描述，可以参考上文方法实施例(如图3或图5)的介绍，这里不再一一详述。
示例性的，收发单元602，用于输出注册请求消息，以及输入注册拒绝消息；处理单元601，用于根据该注册拒绝消息确定列表，该列表包括灾难场景下不允许接入的AMF对应的网络。
示例性的，该收发单元602还可以用于执行图4所示的步骤401中的发送步骤以及步骤402中的接收步骤，处理单元601还可以用于执行图4所示的步骤403。
可理解，关于注册请求消息、注册拒绝消息以及列表等的描述，可以参考上文方法实施例(如图4或图5)的介绍，这里不再一一详述。
复用图6，在本申请的另一些实施例中，该通信装置可以是上文示出的AMF或AMF中的 芯片等。即该通信装置可以用于执行上文方法实施例中由AMF执行的步骤或功能等。
示例性的，如收发单元602，用于输入注册请求消息，该注册请求消息包括指示信息，该指示信息用于指示是否处于灾难场景下；处理单元601，用于根据指示信息和负载情况，通过收发单元602输出注册响应消息。本申请实施例中，处理单元601，用于根据指示信息和负载情况确定注册响应消息，然后通过收发单元602输出注册响应消息。
又如，处理单元601，用于根据指示信息确定门限；以及根据负载情况和门限，通过收发单元602输出注册接受消息或注册拒绝消息。
示例性的，该收发单元602还可以用于执行图2所示的步骤201中的接收步骤以及步骤202中的发送步骤等，这里不再详述。又如收发单元602还可以用于执行图5所示的步骤504中的接收步骤以及步骤505中的发送步骤。
可理解，本申请实施例中，关于注册请求消息、指示信息、注册类型、灾难场景、负载情况、门限(包括第一门限和第二门限)等的描述，可以参考上文方法实施例(如图2或图5)的介绍，这里不再一一详述。
复用图6，在本申请的又一些实施例中，该通信装置可以是上文示出的基站或基站中的芯片等。即该通信装置可以用于执行上文方法实施例中由基站执行的步骤或功能等。
示例性的，处理单元601，用于根据负载情况确定最大等待时长；收发单元，用于输出系统消息，该系统消息包括最大等待时长。
示例性的，处理单元601还可以用于执行图3所示的步骤301，收发单元602还可以用于执行图3所示的步骤302中的发送步骤以及步骤304中的接收步骤等。又如，处理单元601还可以用于执行图5所示的步骤501，收发单元602还可以用于执行图5所示的步骤502的发送步骤等。
可理解，本申请实施例中，关于负载情况、最大等待时长、灾难场景等的描述，可以参考上文方法实施例(如图3或图5)的介绍，这里不再一一详述。
可理解，以上各个实施例示出的收发单元和处理单元的具体说明仅为示例，对于收发单元和处理单元的具体功能或执行的步骤等，可以参考上述方法实施例，这里不再详述。
以上介绍了本申请实施例的发送端设备和接收端设备，以下介绍所述发送端设备和接收端设备可能的产品形态。应理解，但凡具备上述图6所述的发送端设备的功能的任何形态的产品，或者，但凡具备上述图6所述的接收端设备的功能的任何形态的产品，都落入本申请实施例的保护范围。还应理解，以下介绍仅为举例，不限制本申请实施例的发送端设备和接收端设备的产品形态仅限于此。
在一种可能的实现方式中，图6所示的通信装置中，处理单元601可以是一个或多个处理器，收发单元602可以是收发器，或者收发单元602还可以是发送单元和接收单元，发送单元可以是发送器，接收单元可以是接收器，该发送单元和接收单元集成于一个器件，例如收发器。本申请实施例中，处理器和收发器可以被耦合等，对于处理器和收发器的连接方式，本申请实施例不作限定。
如图7所示，该通信装置70包括一个或多个处理器720和收发器710。
示例性的，当该通信装置用于执行上述终端设备执行的步骤或方法或功能时，收发器710，用于向AMF发送注册请求消息，以及接收来自AMF的注册响应消息等。或者，收发器710，用于接收来自漫游网络中的基站的系统消息。处理器720，用于根据终端设备的标识和最大等待时长确定发送注册请求消息的等待时长。或者，处理器720，用于根据注册拒绝消息确定列表，该列表包括灾难场景下不允许接入的AMF对应的网络。
示例性的，当该通信装置用于执行上述AMF执行的步骤或方法或功能时，收发器710，用于接收来自终端设备的注册请求消息，以及向终端设备发送注册响应消息(包括注册接受消息或注册拒绝消息)。处理器720，用于根据指示信息和负载情况确定注册响应消息。
示例性的，当该通信装置用于执行上述基站执行的步骤或方法或功能时，处理器720，用于根据负载情况确定最大等待时长，收发器710，用于向终端设备发送系统消息，该系统消息包括最大等待时长。
可理解，关于收发器和处理器的具体描述，可以参考图6所示的通信装置，或者参考上述方法实施例，这里不再赘述。
在图7所示的通信装置的各个实现方式中，收发器可以包括接收机和发射机，该接收机用于执行接收的功能(或操作)，该发射机用于执行发射的功能(或操作)。以及收发器用于通过传输介质和其他设备/装置进行通信。
可选的，通信装置70还可以包括一个或多个存储器730，用于存储程序指令和/或数据(如当通信装置用于执行终端设备执行的步骤时，存储器中可以包括列表，因此图7示出的列表以虚线示出)。存储器730和处理器720耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器720可能和存储器730协同操作。处理器720可可以执行存储器730中存储的程序指令。可选的，上述一个或多个存储器中的至少一个可以包括于处理器中。
本申请实施例中不限定上述收发器710、处理器720以及存储器730之间的具体连接介质。本申请实施例在图7中以存储器730、处理器720以及收发器710之间通过总线740连接，总线在图7中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图7中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成等。
本申请实施例中，存储器可包括但不限于硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等非易失性存储器，随机存储记忆体(Random Access Memory，RAM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、只读存储器(Read-Only Memory，ROM)或便携式只读存储器(Compact Disc Read-Only Memory，CD-ROM)等等。存储器是能够用于携带或存储具有指令或数据结构形式的程序代码，并能够由计算机(如本申请示出的通信装置等)读和/或写的任何存储介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
示例性的，当通信装置用于执行终端设备执行的步骤时，处理器720主要用于对通信协议以及通信数据进行处理，以及对整个通信装置进行控制，执行软件程序，处理软件程序的数据。存储器730主要用于存储软件程序和数据。收发器710可以包括控制电路和天线，控制电路主要用于基带信号与射频信号的转换以及对射频信号的处理。天线主要用于收发电磁波形式的射频信号。输入输出装置，例如触摸屏、显示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。当通信装置开机后，处理器720可以读取存储器730中的软件程序，解释并执行软件程序的指令，处理软件程序的数据。当需要通过无线发送数据时，处理 器720对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到通信装置时，射频电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器720，处理器720将基带信号转换为数据并对该数据进行处理。在另一种实现中，所述的射频电路和天线可以独立于进行基带处理的处理器而设置，例如在分布式场景中，射频电路和天线可以与独立于通信装置，呈拉远式的布置。
可理解，本申请实施例示出的通信装置还可以具有比图7更多的元器件等，本申请实施例对此不作限定。以上所示的处理器和收发器所执行的方法仅为示例，对于该处理器和收发器具体所执行的步骤可参照上文介绍的方法。
在另一种可能的实现方式中，图6所示的通信装置中，处理单元601可以是一个或多个逻辑电路，收发单元602可以是输入输出接口，又或者称为通信接口，或者接口电路，或接口等等。或者收发单元602还可以是发送单元和接收单元，发送单元可以是输出接口，接收单元可以是输入接口，该发送单元和接收单元集成于一个单元，例如输入输出接口。如图8所示，图8所示的通信装置包括逻辑电路801和接口802。即上述处理单元601可以用逻辑电路801实现，收发单元602可以用接口802实现。其中，该逻辑电路801可以为芯片、处理电路、集成电路或片上系统(system on chip，SoC)芯片等，接口802可以为通信接口、输入输出接口、管脚等。示例性的，图8是以上述通信装置为芯片为例出的，该芯片包括逻辑电路801和接口802。
本申请实施例中，逻辑电路和接口还可以相互耦合。对于逻辑电路和接口的具体连接方式，本申请实施例不作限定。
示例性的，当通信装置用于执行上述终端设备执行的方法或功能或步骤时，如接口802，用于输出注册请求消息，以及输入注册响应消息。又如，接口802，用于输入系统消息；逻辑电路801，用于根据终端设备的标识和最大等待时长确定发送注册请求消息的等待时长。又如，逻辑电路801，用于根据注册拒绝消息确定列表等。
示例性的，当通信装置用于执行上述AMF执行的方法或功能或步骤时，如接口802，用于输入注册请求消息，以及输出注册响应消息。又如，逻辑电路801，用于根据指示信息和负载情况，确定注册响应消息；接口802，用于输出注册响应消息。
示例性的，当通信装置用于执行上述AMF执行的方法或功能或步骤时，如逻辑电路801，用于根据负载情况确定最大等待时长，接口802，用于输出系统消息。
可理解，关于接口和逻辑电路的具体描述，可以参考上文各个实施例，这里不再一一详述。
可理解，本申请实施例示出的通信装置可以采用硬件的形式实现本申请实施例提供的方法，也可以采用软件的形式实现本申请实施例提供的方法等，本申请实施例对此不作限定。
对于图8所示的各个实施例的具体实现方式，还可以参考上述各个实施例，这里不再详述。
本申请实施例还提供了一种无线通信系统，该无线通信系统包括终端设备和AMF，该终端设备和AMF可以用于执行前述任一实施例中的方法。可选的，该无线通信系统还包括基站，该基站可以用于执行前述任一实施例中的方法。关于终端设备、AMF和基站的具体描述，可以参考前述各个实施例，这里不再详述。
此外，本申请还提供一种计算机程序，该计算机程序用于实现本申请提供的方法中由终端设备执行的操作和/或处理。
本申请还提供一种计算机程序，该计算机程序用于实现本申请提供的方法中由AMF执 行的操作和/或处理。
本申请还提供一种计算机程序，该计算机程序用于实现本申请提供的方法中由基站(如UE的漫游网络中的基站)执行的操作和/或处理。
本申请还提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机代码，当计算机代码在计算机上运行时，使得计算机执行本申请提供的方法中由终端设备执行的操作和/或处理。
本申请还提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机代码，当计算机代码在计算机上运行时，使得计算机执行本申请提供的方法中由AMF执行的操作和/或处理。
本申请还提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机代码，当计算机代码在计算机上运行时，使得计算机执行本申请提供的方法中由基站(如UE的漫游网络中的基站)执行的操作和/或处理。
本申请还提供一种计算机程序产品，该计算机程序产品包括计算机代码或计算机程序，当该计算机代码或计算机程序在计算机上运行时，使得本申请提供的方法中由终端设备执行的操作和/或处理被执行。
本申请还提供一种计算机程序产品，该计算机程序产品包括计算机代码或计算机程序，当该计算机代码或计算机程序在计算机上运行时，使得本申请提供的方法中由AMF执行的操作和/或处理被执行。
本申请还提供一种计算机程序产品，该计算机程序产品包括计算机代码或计算机程序，当该计算机代码或计算机程序在计算机上运行时，使得本申请提供的方法中由基站(如UE的漫游网络中的基站)执行的操作和/或处理被执行。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例提供的方案的技术效果。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分，或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个可读存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的可读存储介质包括：U盘、移动硬盘、只读存储器(read-only memory,ROM)、随机存取存储器(random access memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介 质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种通信方法，其特征在于，所述方法包括：
    终端设备向接入与移动性管理网元发送注册请求消息，所述注册请求消息包括指示信息，所述指示信息指示是否处于灾难场景下；
    所述终端设备接收来自所述接入与移动性管理网元的注册响应消息。
  2. 根据权利要求1所述的方法，其特征在于，
    所述指示信息为第一值，所述指示信息指示处于所述灾难场景下；
    所述指示信息为第二值，所述指示信息指示不处于所述灾难场景下。
  3. 根据权利要求1或2所述的方法，其特征在于，所述注册请求消息还包括注册类型，所述注册类型包括：初始注册、移动性注册、周期性注册或紧急注册中的任一项。
  4. 一种通信方法，其特征在于，所述方法包括：
    接入与移动性管理网元接收来自终端设备的注册请求消息，所述注册请求消息包括指示信息，所述指示信息指示是否处于灾难场景下；
    所述接入与移动性管理网元根据所述指示信息和负载情况，向所述终端设备发送注册响应消息。
  5. 根据权利要求4所述的方法，其特征在于，所述接入与移动性管理网元根据指示信息和负载情况，向所述终端设备发送注册响应消息，包括：
    所述接入与移动性管理网元根据所述指示信息确定门限；
    所述接入与移动性管理网元根据所述负载情况和所述门限，向所述终端设备发送注册接受消息或注册拒绝消息。
  6. 根据权利要求5所述的方法，其特征在于，
    所述指示信息指示处于灾难场景下，所述门限为第一门限；
    所述指示信息指示不处于灾难场景下，所述门限为第二门限。
  7. 一种通信方法，其特征在于，所述方法包括：
    终端设备接收来自漫游网络中的基站的系统消息，所述系统消息包括最大等待时长；
    所述终端设备根据所述终端设备的标识和所述最大等待时长的模确定发送注册请求消息的等待时长；
    在所述等待时长超时后，所述终端设备向接入与移动性管理网元发送所述注册请求消息。
  8. 根据权利要求7所述的方法，其特征在于，所述注册请求消息包括指示信息，所述指示信息指示是否处于灾难场景下。
  9. 根据权利要求8所述的方法，其特征在于，所述指示信息为第一值，所述指示信息指示处于所述灾难场景下；
    所述指示信息为第二值，所述指示信息指示不处于所述灾难场景下。
  10. 根据权利要求7-9任一项所述的方法，其特征在于，所述终端设备向接入与移动性管理网元发送所述注册请求消息，包括：
    若所述终端设备确定处于灾难场景下，所述终端设备向所述接入与移动性管理网元发送所述注册请求消息。
  11. 根据权利要求10所述的方法，其特征在于，所述注册请求消息包括指示信息，所述指示信息为第一值。
  12. 根据权利要求7-11任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收来自所述接入与移动性管理网元的注册拒绝消息；
    所述终端设备根据所述注册拒绝消息，确定列表，所述列表包括所述灾难场景下不允许接入的所述接入与移动性管理网元对应的网络。
  13. 根据权利要求12所述的方法，其特征在于，所述网络包括：公共陆地移动网络PLMN、跟踪区或部分跟踪区中的任一项或多项。
  14. 一种通信装置，其特征在于，所述通信装置包括：
    收发单元，用于收发信号；
    处理单元，用于通过所述收发单元执行：
    向接入与移动性管理网元发送注册请求消息，所述注册请求消息包括指示信息，所述指示信息指示是否处于灾难场景下；
    接收来自所述接入与移动性管理网元的注册响应消息。
  15. 根据权利要求14所述的通信装置，其特征在于，
    所述指示信息为第一值，所述指示信息指示处于所述灾难场景下；
    所述指示信息为第二值，所述指示信息指示不处于所述灾难场景下。
  16. 根据权利要求14或15所述的通信装置，其特征在于，所述注册请求消息还包括注册类型，所述注册类型包括：初始注册、移动性注册、周期性注册或紧急注册中的任一项。
  17. 一种通信装置，其特征在于，所述通信装置包括：
    收发单元，用于接收来自终端设备的注册请求消息，所述注册请求消息包括指示信息，所述指示信息指示是否处于灾难场景下；
    处理单元，用于根据所述指示信息和负载情况，通过所述收发单元向所述终端设备发送注册响应消息。
  18. 根据权利要求17所述的通信装置，其特征在于，
    所述处理单元，具体用于根据所述指示信息确定门限；以及根据所述负载情况和所述门限，通过所述收发单元向所述终端设备发送注册接受消息或注册拒绝消息。
  19. 根据权利要求18所述的通信装置，其特征在于，
    所述指示信息指示处于灾难场景下，所述门限为第一门限；
    所述指示信息指示不处于灾难场景下，所述门限为第二门限。
  20. 一种通信装置，其特征在于，所述通信装置包括：
    收发单元，用于接收来自漫游网络中的基站的系统消息，所述系统消息包括最大等待时长；
    处理单元，用于根据所述通信装置的标识和所述最大等待时长的模确定发送注册请求消息的等待时长；
    所述收发单元，还用于在所述等待时长超时后，向接入与移动性管理网元发送所述注册请求消息。
  21. 根据权利要求20所述的通信装置，其特征在于，所述注册请求消息包括指示信息，所述指示信息指示是否处于灾难场景下。
  22. 根据权利要求21所述的通信装置，其特征在于，所述指示信息为第一值，所述指示信息指示处于所述灾难场景下；
    所述指示信息为第二值，所述指示信息指示不处于所述灾难场景下。
  23. 根据权利要求20-22任一项所述的通信装置，其特征在于，
    所述收发单元，具体用于若所述通信装置处于灾难场景下，向所述接入与移动性管理网元发送所述注册请求消息。
  24. 根据权利要求23所述的通信装置，其特征在于，所述注册请求消息包括指示信息，所述指示信息为第一值。
  25. 根据权利要求20-24任一项所述的通信装置，其特征在于，
    所述收发单元，还用于接收来自所述接入与移动性管理网元的注册拒绝消息；
    所述处理单元，用于根据所述注册拒绝消息，确定列表，所述列表包括所述灾难场景下不允许接入的所述接入与移动性管理网元对应的网络。
  26. 根据权利要求25所述的通信装置，其特征在于，所述网络包括：公共陆地移动网络PLMN、跟踪区或部分跟踪区中的任一项或多项。
  27. 一种通信装置，其特征在于，所述通信装置包括：
    处理单元，用于根据负载情况确定最大等待时长；
    收发单元，用于向终端设备发送系统消息，所述系统消息包括所述最大等待时长。
  28. 一种通信装置，其特征在于，包括处理器和存储器；
    所述处理器用于存储计算机执行指令；
    所述处理器用于执行所述计算机执行指令，以使权利要求1-3任一项所述的方法被执行；或者，所述处理器用于执行所述计算机执行指令，以使权利要求4-6任一项所述的方法被执行；或者，所述处理器用于执行所述计算机执行指令，以使权利要求7-13任一项所述的方法被执行。
  29. 一种通信装置，其特征在于，包括逻辑电路和接口，所述逻辑电路和接口耦合；
    所述接口用于输入和/或输出代码指令，所述逻辑电路用于执行所述代码指令，以使权利要求1-3任一项所述的方法被执行；或者，所述逻辑电路用于执行所述代码指令，以使权利要求4-6任一项所述的方法被执行；或者，所述逻辑电路用于执行所述代码指令，以使权利要求7-13任一项所述的方法被执行。
  30. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质用于存储计算机程序，当所述计算机程序被执行时，权利要求1-3任一项所述的方法被执行；或者，当所述计算机程序被执行时，权利要求4-6任一项所述的方法被执行；或者，当所述计算机程序被执行时，权利要求7-13任一项所述的方法被执行。
PCT/CN2022/075637 2021-02-10 2022-02-09 通信方法及装置 WO2022171119A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP22752279.4A EP4280697A1 (en) 2021-02-10 2022-02-09 Communication method and device
JP2023548550A JP2024506092A (ja) 2021-02-10 2022-02-09 通信方法及び装置
US18/446,988 US20230388957A1 (en) 2021-02-10 2023-08-09 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110184233.1 2021-02-10
CN202110184233.1A CN114916037A (zh) 2021-02-10 2021-02-10 通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/446,988 Continuation US20230388957A1 (en) 2021-02-10 2023-08-09 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2022171119A1 true WO2022171119A1 (zh) 2022-08-18

Family

ID=82761410

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/075637 WO2022171119A1 (zh) 2021-02-10 2022-02-09 通信方法及装置

Country Status (5)

Country Link
US (1) US20230388957A1 (zh)
EP (1) EP4280697A1 (zh)
JP (1) JP2024506092A (zh)
CN (1) CN114916037A (zh)
WO (1) WO2022171119A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024061075A1 (zh) * 2022-09-19 2024-03-28 大唐移动通信设备有限公司 网络注册方法及装置
WO2024098329A1 (zh) * 2022-11-10 2024-05-16 Oppo广东移动通信有限公司 通信方法和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101640575A (zh) * 2008-07-31 2010-02-03 中兴通讯股份有限公司 一种地震海啸报警系统中重要通知信息的发送方法
CN110366241A (zh) * 2018-04-09 2019-10-22 华为技术有限公司 通信方法、装置和系统
CN110636604A (zh) * 2018-06-25 2019-12-31 华为技术有限公司 一种注册状态的管理方法及装置
WO2021007447A1 (en) * 2019-07-09 2021-01-14 Ofinno, Llc Network reselection during a disaster

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101640575A (zh) * 2008-07-31 2010-02-03 中兴通讯股份有限公司 一种地震海啸报警系统中重要通知信息的发送方法
CN110366241A (zh) * 2018-04-09 2019-10-22 华为技术有限公司 通信方法、装置和系统
CN110636604A (zh) * 2018-06-25 2019-12-31 华为技术有限公司 一种注册状态的管理方法及装置
WO2021007447A1 (en) * 2019-07-09 2021-01-14 Ofinno, Llc Network reselection during a disaster

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Discussion on solutions Key issues for MINT #3, #4, #5,#7,#8", 3GPP DRAFT; C1-210259, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Electronic meeting; 20210125 - 20210129, 18 January 2021 (2021-01-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051969978 *
HUAWEI, HISILICON: "Solution for KI#4", 3GPP DRAFT; C1-210426, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Electronic meeting; 20210125 - 20210129, 28 January 2021 (2021-01-28), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051975539 *
QUALCOMM INCORPORATED: "Solution to MINT Key Issue #7 (Prevention of signalling overload in PLMNs without Disaster Condition) – Alternative 1: providing disaster roaming assistance information to distribute roamers, and congestion mitigation", 3GPP DRAFT; C1-210116, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Electronic meeting; 20210125 - 20210129, 18 January 2021 (2021-01-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051969859 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024061075A1 (zh) * 2022-09-19 2024-03-28 大唐移动通信设备有限公司 网络注册方法及装置
WO2024098329A1 (zh) * 2022-11-10 2024-05-16 Oppo广东移动通信有限公司 通信方法和设备

Also Published As

Publication number Publication date
JP2024506092A (ja) 2024-02-08
US20230388957A1 (en) 2023-11-30
EP4280697A1 (en) 2023-11-22
CN114916037A (zh) 2022-08-16

Similar Documents

Publication Publication Date Title
US20230180274A1 (en) Data scheduling method, base station, and system
CN109315016B (zh) 一种系统信息传输方法及装置
CN107231623B (zh) 一种数据调度方法、基站及系统
WO2016161623A1 (zh) 发现信号的传输方法、装置以及通信系统
WO2020248202A1 (zh) 直连链路资源配置方法、装置、系统及可读存储介质
US10034173B2 (en) MTC service management using NFV
WO2022171119A1 (zh) 通信方法及装置
WO2021136211A1 (zh) 授权结果的确定方法及装置
WO2018176422A1 (zh) 资源调度的方法和装置以及基站
WO2020221223A1 (zh) 通信方法、装置和系统
WO2017193370A1 (zh) 信息传输装置、方法以及通信系统
WO2020206582A1 (zh) 一种用于中继通信的方法和装置
WO2021249430A1 (zh) 一种通信方法及相关设备
JP2023531580A (ja) サイドリンク中継通信に関するシグナリング伝送のためのシステムおよび方法
CN112752297A (zh) 一种通信方法及设备
WO2021174377A1 (zh) 切换方法和通信装置
WO2021180098A1 (zh) 无线通信方法和通信装置
WO2021197029A1 (zh) 一种先听后说lbt失败指示方法及装置
JP6096305B2 (ja) セルラーネットワークにおけるノード、システム、および方法
CN111988772A (zh) 终端发现方法及设备
WO2023142981A1 (zh) 通信方法及相关装置
WO2022104689A1 (zh) 一种小区频域带宽切换的方法、相关装置以及设备
US11191010B2 (en) System information transmission method and apparatus
WO2023131156A1 (zh) 随机接入的方法和通信装置
WO2024094160A1 (zh) 链路配置方法、通信装置及存储介质

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: 22752279

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023548550

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 2022752279

Country of ref document: EP

Effective date: 20230818

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 11202306027Y

Country of ref document: SG