WO2021233050A1 - Procédé et appareil de communication - Google Patents

Procédé et appareil de communication Download PDF

Info

Publication number
WO2021233050A1
WO2021233050A1 PCT/CN2021/088655 CN2021088655W WO2021233050A1 WO 2021233050 A1 WO2021233050 A1 WO 2021233050A1 CN 2021088655 W CN2021088655 W CN 2021088655W WO 2021233050 A1 WO2021233050 A1 WO 2021233050A1
Authority
WO
WIPO (PCT)
Prior art keywords
plmn
information
terminal
rejected
indication information
Prior art date
Application number
PCT/CN2021/088655
Other languages
English (en)
Chinese (zh)
Inventor
李岚涛
强鹂
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2021233050A1 publication Critical patent/WO2021233050A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and device.
  • support user equipment according to the current public land mobile network (public land mobile network, PLMN) permitted (allowed) network slice selection assistance information (network slice selection assistance information, NSSAI), current PLMN
  • network slice selection assistance information network slice selection assistance information, NSSAI
  • the configured network slice selection assistance information (configured NSSAI) and/or the default configured network slice selection assistance information (default configured NSSAI) initiates registration in the current PLMN.
  • the aforementioned NSSAI may include at least one single network slice selection auxiliary information (single NSSAI, S-NSSAI), and each S-NSSAI may indicate one network slice.
  • the UE may carry the requested network slice selection assistance information (requested NSSAI) in the registration request message to request registration to the network slice indicated by the requested NSSAI, where the requested NSSAI may be allowed NSSAI, configured NSSAI And/or one or more S-NSSAIs in the default configured NSSAI.
  • the UE receives an instruction from the network side and learns that the S-NSSAI in allowed NSSAI, configured NSSAI, and/or default configured NSSAI belongs to the rejected NSSAI (rejected NSSAI), the UE will no longer choose to belong to the The S-NSSAI of the rejected NSSAI is regarded as the requested NSSAI.
  • the UE in the deregistered state may still choose the rejection indicated by the network side when it initiates registration.
  • the S-NSSAI is used as a requested NSSAI. According to these S-NSSAIs, the result of requesting registration can only be rejected, which reduces the efficiency of the UE registration process.
  • the present application provides a communication method and device to improve the efficiency of the UE registration process.
  • an embodiment of the present application provides a communication method, which may be executed by a UE or a component of the UE (such as a processor, a chip, or a chip system, etc.).
  • the UE can receive at least one rejected network slice information and first indication information from a network device deployed in the first PLMN (the first PLMN is the PLMN that the UE currently requests to register, or it can be Called the current PLMN (current PLMN)).
  • the first indication information after the first PLMN enters the deregistered state (enters state 5GMM-deregistered for the current PLMN), the UE retains the information of the rejected network slice associated with the first PLMN.
  • the UE can still retain the rejected network slice information associated with the first PLMN after the UE enters the deregistered state from the first PLMN according to the first indication information, so as to learn which network slice information is the rejected network
  • the sliced information can avoid repeated requests for registration based on the rejected network slice information, so as to improve registration efficiency.
  • the UE may receive a first registration rejection message from a network device, the first registration rejection message is used to indicate that the first registration request message is rejected, and the first registration rejection message may carry the at least one rejected Network slice information and the first indication information.
  • the UE may receive a first de-registration request message from the network device, where the first de-registration request message is used to instruct the UE to perform de-registration in the first PLMN.
  • the first deregistration request message may carry the information of the at least one rejected network slice and the first indication information.
  • the first indication information may be the re-registration indication information in the first de-registration request message.
  • the above rejected network slices may include network slices rejected because they are unavailable in the first PLMN, and network slices rejected because they are unavailable in the registration area where the UE is located. Or at least one of the network slices that was rejected due to the failure or revocation of authentication and authorization of the network slice.
  • the information of the network slices that are rejected due to being unavailable in the first PLMN may be retained.
  • the reservation is unavailable in the registration area where the UE is located. Information about rejected network slices.
  • the UE determines that the information of the network slice in the available network slice information set is the information of the rejected network slice, then the UE may send a second registration request message to the network device, the second registration request message Does not include network slice information, or in other words, the second registration request message does not carry requested NSSAI.
  • the available network slice information set includes information of network slices permitted by the first PLMN, information of network slices configured by the first PLMN, and information of network slices configured by default.
  • the available network slice information set may include allowed NSSAI (or referred to as allowed NSSAI (allowed NSSAI for the current PLMN) of the current PLMN (i.e., the first PLMN), configured NSSAI (or referred to as the configured NSSAI of the current PLMN). configured NSSAI for the current PLMN)) and default configured NSSAI.
  • allowed NSSAI for the current PLMN and configured NSSAI for the current PLMN can be indicated by the network device.
  • the UE may determine that the network slice information in the available network slice information set is all included in the rejected network slice information associated with the first PLMN.
  • the UE may receive second indication information from the network device, and the second indication information may be used to instruct the UE to turn off the N1 mode capability, and the UE may turn off the N1 mode capability according to the second indication information.
  • the UE After the UE determines that the information of the network slice in the available network slice information set is the information of the rejected network slice and sends the second registration request message, it can turn off the N1 mode capability according to the second indication information.
  • the UE When the network slice is rejected, the UE no longer attempts to register to the 5G network. After that, the UE may request to register to a long-term evolution (LTE) network to improve registration efficiency.
  • LTE long-term evolution
  • the UE may receive third indication information from the network device, and the third indication information is used to indicate that no default network slice is available, and the UE may turn off the N1 mode capability according to the third indication information, and Select from the first PLMN to the second PLMN.
  • the UE may turn off the N1 mode capability after receiving the third indication information for the first time, and select from the first PLMN to the second PLMN, or the UE may determine that the number of times the third indication information has been received reaches a threshold (such as 5 After), turn off the N1 mode capability, and select from the first PLMN to the second PLMN.
  • a threshold such as 5 After
  • the UE After the UE determines that the information of the network slice in the available network slice information set is the information of the rejected network slice and sends the second registration request message, it can turn off the N1 mode capability according to the third instruction information and execute the PLMN Choose not to try to register to the first PLMN but to try to register to other PLMNs to improve registration efficiency.
  • the UE may receive fourth indication information from the network device, where the fourth indication information is used to instruct the UE to perform PLMN selection. Then the UE can select from the first PLMN to the second PLMN according to the fourth indication information.
  • the UE After the UE determines that the network slice information in the available network slice information set is the information of the rejected network slice and sends the second registration request message, it can turn off the N1 mode capability according to the fourth instruction information, and execute PLMN Choose not to try to register to the first PLMN but to try to register to other PLMNs to improve registration efficiency.
  • the UE retains the information of the first PLMN after selecting from the first PLMN to the second PLMN.
  • the UE selects from the first PLMN to the second PLMN, it still retains the information of the first PLMN, so it can identify whether the second PLMN is still the first PLMN (or other PLMNs that were previously selected but failed to register).
  • the UE selects from the first PLMN to the second PLMN, and the first PLMN is different from the second PLMN, so as to avoid repeating requests for registration in the first PLMN.
  • the UE may store the information of the first PLMN in the first PLMN list.
  • the first PLMN list includes PLMNs with no available network slices. In other words, there are no available network slices for the PLMN in the first PLMN list.
  • the UE may determine the second PLMN according to the first PLMN list, where the second PLMN is not included in the first PLMN list. In other words, the UE may determine the second PLMN from the PLMNs that are not included in the first PLMN list, so as to avoid re-selecting PLMNs with no available network slices and improve registration efficiency.
  • the UE determines that the first PLMN is the same as the second PLMN according to the information of the first PLMN, and the UE turns off the N1 mode capability.
  • the UE recognizes that the first PLMN is consistent with the second PLMN, it can turn off the N1 mode capability, and no longer try to register to the first PLMN to improve registration efficiency, and the subsequent UE can perform PLMN selection again.
  • the UE determines that the second PLMN is the PLMN in the first PLMN list according to the information of the first PLMN, or in other words, the UE determines that the first PLMN list includes the second PLMN according to the information of the first PLMN, Then the UE turns off the N1 mode capability.
  • the UE recognizes that the second PLMN is the same as the PLMN in the first PLMN list that the UE tried to register but failed to register, it can turn off the N1 mode capability and no longer try to register to the PLMN to improve registration efficiency.
  • the subsequent UE can Perform PLMN selection again.
  • the UE determines that the candidate PLMNs searched when the N1 mode capability is turned on belong to the first PLMN list, the N1 mode capability is turned off, and the UE does not attempt to register to the PLMN to improve registration efficiency.
  • the UE may receive fifth indication information from the network device, and the fifth indication information may be used to indicate at least one information for guiding the network slice.
  • the UE may send a third registration request message to the network device according to the information for guiding the network slice, where the third registration request message includes at least one information for guiding the network slice.
  • the UE can request registration according to the guided network slice indicated by the network device to improve registration efficiency.
  • the UE may receive sixth indication information from the network device, the sixth indication information is used to indicate that the UE does not need to re-register, or to indicate that the UE does not need to re-register to the first PLMN, then The UE may delete the information of the rejected network slice associated with the first PLMN.
  • the UE can delete the stored information of the rejected network slice associated with the first PLMN according to the non-registration indication information.
  • the sixth indication information may be included in the second de-registration request message, which is used to instruct the UE to perform de-registration in the first PLMN, and the sixth indication information may specifically be non-re-registration indication information.
  • network equipment may include access and mobility management functions (AMF).
  • AMF access and mobility management functions
  • the embodiments of the present application provide a communication method, which may be executed by a UE, or may be executed by a component of the UE (such as a processor, a chip, or a chip system, etc.).
  • the UE can send a second registration request message to the network device.
  • the second registration request message does not include network slice information.
  • the second registration request message does not carry the requested NSSAI, and the network device is deployed in the first One PLMN.
  • the UE may receive the fourth indication information from the network device, and select from the first PLMN to the second PLMN according to the fourth indication information.
  • the UE After the UE sends the second registration request message that does not include network slice information, it shuts down the N1 mode capability according to the fourth instruction information from the network device, and performs PLMN selection, and tries to register under other PLMNs. Improve registration efficiency.
  • the UE retains the information of the first PLMN after selecting from the first PLMN to the second PLMN.
  • the UE selects from the first PLMN to the second PLMN, it still retains the information of the first PLMN, so it can identify whether the second PLMN is still the first PLMN (or other PLMNs that were previously selected but failed to register).
  • the UE selects from the first PLMN to the second PLMN, and the first PLMN is different from the second PLMN, so as to avoid repeating requests for registration in the first PLMN.
  • the UE may store the information of the first PLMN in the first PLMN list.
  • the first PLMN list includes PLMNs with no available network slices. In other words, there are no available network slices for the PLMN in the first PLMN list.
  • the UE may determine the second PLMN according to the first PLMN list, where the second PLMN is not included in the first PLMN list. In other words, the UE may determine the second PLMN from the PLMNs that are not included in the first PLMN list, so as to avoid re-selecting PLMNs with no available network slices and improve registration efficiency.
  • the UE determines that the first PLMN is the same as the second PLMN according to the information of the first PLMN, and the UE turns off the N1 mode capability.
  • the UE recognizes that the first PLMN is consistent with the second PLMN, it can turn off the N1 mode capability, and no longer try to register to the first PLMN to improve registration efficiency, and the subsequent UE can perform PLMN selection again.
  • the UE determines that the second PLMN is the PLMN in the first PLMN list according to the information of the first PLMN, or in other words, the UE determines that the first PLMN list includes the second PLMN according to the information of the first PLMN, Then the UE turns off the N1 mode capability.
  • the UE recognizes that the second PLMN is the same as the PLMN in the first PLMN list that the UE tried to register but failed to register, it can turn off the N1 mode capability and no longer try to register to the PLMN to improve registration efficiency.
  • the subsequent UE can Perform PLMN selection again.
  • the UE determines that the candidate PLMNs searched for when the N1 mode capability is turned on belong to the first PLMN list, the N1 mode capability is turned off, and the UE does not attempt to register to the PLMN to improve registration efficiency.
  • the UE may receive fifth indication information from the network device, and the fifth indication information may be used to indicate at least one information for guiding the network slice.
  • the UE may send a third registration request message to the network device according to the information for guiding the network slice, where the third registration request message includes at least one information for guiding the network slice.
  • the UE can request registration according to the guided network slice indicated by the network device to improve registration efficiency.
  • the UE may receive sixth indication information from the network device, where the sixth indication information is used to indicate that the UE does not need to re-register, or is used to indicate that the UE does not need to re-register with the first PLMN. Then the UE may delete the information of the rejected network slice associated with the first PLMN.
  • the sixth indication information may be included in the second de-registration request message, which is used to instruct the UE to perform de-registration in the first PLMN, and the sixth indication information may specifically be non-re-registration indication information.
  • the UE can delete the stored information of the rejected network slice associated with the first PLMN according to the non-registration indication information.
  • the UE may receive sixth indication information from the network device, the sixth indication information is used to indicate that the UE does not need to re-register, or to indicate that the UE does not need to re-register to the first PLMN, then The UE may delete the information of the rejected network slice associated with the first PLMN.
  • the UE can delete the stored information of the rejected network slice associated with the first PLMN according to the non-registration indication information.
  • the sixth indication information may be included in the second de-registration request message, which is used to instruct the UE to perform de-registration in the first PLMN, and the sixth indication information may specifically be non-re-registration indication information.
  • the above network equipment may include AMF.
  • the embodiments of the present application provide a communication method, which may be executed by a network device, or may be executed by a component of the network device (such as a processor, a chip, or a chip system, etc.).
  • the network device may be AMF.
  • the execution subject is AMF as an example for description.
  • the AMF can send the information of at least one rejected network slice and the first indication information to the UE.
  • AMF is deployed in the first PLMN.
  • the first indication information may be used to instruct the UE to retain the rejected network slice information associated with the first PLMN after the first PLMN enters the de-registration state.
  • the AMF may send a first registration rejection message or a first de-registration request message to the UE, and the first registration rejection message or the first de-registration request message includes information about at least one rejected network slice and The first instruction information.
  • the first registration rejection message is used to indicate that the first registration request message is rejected, and the first de-registration request message is used to instruct the UE to perform de-registration in the first PLMN.
  • the first indication information may be the re-registration indication information in the first de-registration request message.
  • the re-registration indication information may be used to indicate that the UE needs to re-register in the first PLMN after performing de-registration in the first PLMN.
  • the first indication information is specifically used to indicate that after the UE enters the de-registered state in the first PLMN, it retains information about the network slices that are rejected due to being unavailable in the first PLMN.
  • the first indication information may specifically indicate that the UE is in the de-registered state in the first PLMN and the registration area or tracking area where the UE resides remains unchanged. Information about rejected network slices.
  • the AMF may receive a second registration request message from a UE, and the second registration request message does not include network slice information, or in other words, the second registration request message does not carry the requested NSSAI.
  • the AMF may send second indication information to the UE, the second indication information is used to instruct the UE to turn off the N1 mode capability; or, the AMF may send third indication information to the UE, and the third indication information is used to indicate that no default network slice is available, And for instructing the UE to store the information of the first PLMN after the first PLMN performs PLMN selection; or, the AMF sends fourth indication information to the UE, the fourth indication information is used for instructing the UE to perform PLMN selection, and for Instruct the UE to store the information of the first PLMN after performing PLMN selection in the first PLMN.
  • the AMF may send fifth indication information to the UE, and the fifth indication information is used to indicate at least one boot network slice.
  • the AMF may also receive a third registration request message from the UE, where the third registration request message is used to request access to at least one guided network slice.
  • the third registration request message may include at least one piece of information for guiding the network slice.
  • the embodiments of the present application provide a communication method, which may be executed by a network device, or may be executed by a component of the network device (such as a processor, a chip, or a chip system, etc.).
  • the network device may be AMF.
  • the execution subject is AMF as an example for description.
  • the AMF can receive a second registration request message from a UE.
  • the second registration request message does not include network slice information, or in other words, the second registration request message does not carry the requested NSSAI.
  • the AMF may send second indication information to the UE, the second indication information is used to instruct the UE to turn off the N1 mode capability; or, the AMF may send third indication information to the UE, and the third indication information is used to indicate that no default network slice is available, And for instructing the UE to store the information of the first PLMN after the first PLMN performs PLMN selection; or, the AMF sends fourth indication information to the UE, the fourth indication information is used for instructing the UE to perform PLMN selection, and for Instruct the UE to store the information of the first PLMN after performing PLMN selection in the first PLMN.
  • the AMF may send fifth indication information to the UE, and the fifth indication information is used to indicate at least one boot network slice.
  • the AMF may also receive a third registration request message from the UE, where the third registration request message is used to request access to at least one guided network slice.
  • the third registration request message may include at least one piece of information for guiding the network slice.
  • an embodiment of the present application provides a communication device, which is configured to implement the function of the UE in the foregoing first aspect or each possible design example of the first aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the communication device may include a communication module and a processing module, and these modules may perform the corresponding functions of the UE in the first aspect or each possible design example of the first aspect.
  • these modules may perform the corresponding functions of the UE in the first aspect or each possible design example of the first aspect.
  • the first aspect The detailed description in the aspect will not be repeated here.
  • the structure of the communication device includes a processor, and optionally a transceiver and a memory.
  • the transceiver can be used to send and receive information or data, and to communicate and interact with other communication devices in the network system.
  • the processor is configured to support the communication device to perform the corresponding function of the UE in the foregoing first aspect or each possible design example of the first aspect.
  • the memory is coupled with the processor, and is used to store necessary program instructions and data of the first communication device.
  • the communication device is a UE or a component in the UE, such as a chip, a transceiver, and so on.
  • an embodiment of the present application provides a communication device, which is configured to implement the function of the UE in the foregoing second aspect or each possible design example of the second aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the communication device may include a communication module and a processing module, and these modules may perform the corresponding functions of the UE in the second aspect or each possible design example of the second aspect.
  • these modules may perform the corresponding functions of the UE in the second aspect or each possible design example of the second aspect.
  • the structure of the communication device may include a communication module and a processing module, and these modules may perform the corresponding functions of the UE in the second aspect or each possible design example of the second aspect.
  • the structure of the communication device includes a processor, and optionally a transceiver and a memory.
  • the transceiver can be used to send and receive information or data, and to communicate and interact with other communication devices in the network system.
  • the processor is configured to support the communication device to perform the corresponding function of the UE in the foregoing second aspect or each possible design example of the second aspect.
  • the memory is coupled with the processor, and is used to store necessary program instructions and data of the first communication device.
  • the communication device is a UE or a component in the UE, such as a chip, a transceiver, and so on.
  • an embodiment of the present application provides a communication device, which is configured to implement the function of the network device in the foregoing third aspect or each possible design example of the third aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the communication device may include a communication module and a processing module, and these modules can perform the corresponding functions of the network device in the third aspect or each possible design example of the third aspect.
  • these modules can perform the corresponding functions of the network device in the third aspect or each possible design example of the third aspect.
  • the method The detailed description in the example will not be repeated here.
  • the structure of the communication device includes a processor, and optionally a communication interface (such as a wireless transceiver) and a memory.
  • the communication interface can be used to send and receive information or data, and to communicate and interact with other communication devices in the network system.
  • the processor is configured to support the communication device to execute the corresponding function of the network device in the foregoing third aspect or each possible design example of the third aspect.
  • the memory is coupled with the processor, and is used to store necessary program instructions and data of the first communication device.
  • the communication device is a network device or a component in the network device, such as a chip, a transceiver, and so on.
  • the network device can be AMF.
  • an embodiment of the present application provides a communication device, where the communication device is configured to implement the function of the network device in the foregoing fourth aspect or each possible design example of the fourth aspect.
  • the function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the communication device may include a communication module and a processing module, and these modules can perform the corresponding functions of the network device in the fourth aspect or each possible design example of the fourth aspect.
  • these modules can perform the corresponding functions of the network device in the fourth aspect or each possible design example of the fourth aspect.
  • the method The detailed description in the example will not be repeated here.
  • the structure of the communication device includes a processor, and optionally a communication interface (such as a wireless transceiver) and a memory.
  • the communication interface can be used to send and receive information or data, and to communicate and interact with other communication devices in the network system.
  • the processor is configured to support the communication device to perform the corresponding function of the network device in the foregoing fourth aspect or each possible design example of the fourth aspect.
  • the memory is coupled with the processor, and is used to store necessary program instructions and data of the first communication device.
  • the communication device is a network device or a component in the network device, such as a chip, a transceiver, and so on.
  • the network device can be AMF.
  • an embodiment of the present application provides a communication system.
  • the communication system may include the communication device provided in the above fifth aspect and the communication device provided in the above seventh aspect, or the communication system may include the communication device provided in the above sixth aspect and the communication device provided in the above eighth aspect .
  • this application provides a computer storage medium in which a program is stored or, when it is invoked for execution on a computer, the computer can execute any one of the above-mentioned first aspect or the first aspect.
  • this application provides a computer program product.
  • the basic computing product may include a program or instruction.
  • the computer program product runs on a computer, the computer executes any one of the first aspect or the first aspect.
  • One of the possible designs, any one of the second or second aspects, any one of the third or third aspects, or any one of the fourth or fourth aspects The method described.
  • the present application provides a chip or a chip system including the chip, and the chip may include a processor.
  • the chip may also include a memory (or storage module) and/or a transceiver (or communication module).
  • the chip can be used to implement any possible design of the first aspect or the first aspect, any possible design of the second or second aspect, and any possible design of the third aspect or the third aspect. Or the method described in the fourth aspect or any one of the possible designs of the fourth aspect.
  • the chip system may be composed of the above-mentioned chips, or may include the above-mentioned chips and other discrete devices, such as a memory (or storage module) and/or a transceiver (or communication module).
  • beneficial effects of the third aspect to the twelfth aspect and its possible designs can be referred to the beneficial effects of the method described in the first aspect and any of its possible designs or the second aspect and any of its possible designs. describe.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of this application.
  • FIG. 2 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 3 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 4 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 5 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 6 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 7 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 9 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • FIG. 10 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • this application provides a communication method.
  • the application will be further described in detail below in conjunction with the accompanying drawings. It should be understood that the specific operation methods in the method embodiments introduced below may also be applied to the device embodiment or the system embodiment.
  • the communication method provided in this application may include an access network element, a mobility management network element, a network slice selection network element, a policy control network element, a session management network element, a user plane network element, a data management network element, or an application function network.
  • the communication system of some or all of the network elements in the element is realized. It should be understood that this application does not limit the communication system to include other network elements than those listed above.
  • the communication method provided in the embodiment of the present application may be used in the 5G mobile communication system as shown in FIG. 1.
  • the following describes the communication system to which the communication method provided in the embodiment of the present application may be applied according to the architecture shown in FIG. 1.
  • the network architecture shown in Figure 1 may include three parts: UE, data network (DN), and operator network.
  • the operator network may include network slice selection function (NSSF), policy control function (PCF), unified data management (UDM), application function (AF) , Access and mobility management function (access and mobility management function, AMF), session management function (session management function, SMF), (wireless) access network ((radio) access network, (R) AN), UPF, etc.
  • NSF network slice selection function
  • PCF policy control function
  • UDM unified data management
  • AF application function
  • AMF Access and mobility management function
  • AMF Access and mobility management function
  • session management function session management function
  • SMF session management function
  • (wireless) access network ((radio) access network, (R) AN), UPF, etc.
  • core network CN
  • core network CN
  • N1, N2, N3, N4, N6, N9, Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nausf, Namf, and Nsmf identify interfaces.
  • the meanings of these interfaces can be referred to the meanings defined in the 3rd generation partnership project (3rd generation partnership project, 3GPP) related standard protocols, which are not limited here.
  • the above-mentioned mobility management network element may be a control plane network element provided by the operator's network, which is responsible for access control and mobility management when the terminal accesses the operator's network. It has, for example, mobility status management and user allocation. Functions such as temporary identification, authentication and authorization of users.
  • the mobility management network element can be the above-mentioned AMF.
  • future communications such as the 6th generation (6G)
  • the mobility management network element can still be AMF or have other names. The application is not limited.
  • the UE can access the AMF to obtain services provided by the operator's network.
  • the process of the UE accessing the AMF may be referred to as registration in this application, such as initial registration.
  • the UE may send a registration request message to the AMF, and the requested NSSAI may be carried in the registration request message, thereby requesting registration to the network slice indicated by the requested NSSAI.
  • the network slice selection network element can be used to perform functions such as network slice selection, allowed NSSAI determination, and configured NSSAI determination.
  • the network slice selection network element can be NSSF.
  • future communications such as the 6th generation (6G)
  • the network slice selection network element can still be NSSF or have other names, which is not limited in this application. .
  • the policy control network element is a control plane function provided by the operator to provide a PDU session policy to the session management network element.
  • Strategies may include charging-related strategies, quality of service (QoS)-related strategies, data flow identification and orientation (or forwarding) strategies, authorization-related strategies, and the like.
  • QoS quality of service
  • the policy control network element may be PCF.
  • future communications such as 6G, the policy control network element may still be PCF or have other names, which is not limited by this application.
  • the session management network element is a control plane network element provided by the operator's network and is responsible for managing the PDU session of the terminal.
  • the session management network element serves the PDU session of the terminal.
  • the PDU session is a channel used to transmit PDUs, and the terminal needs to transmit PDUs to each other through the PDU session and the DN.
  • SMF is responsible for the establishment, maintenance and deletion of PDU sessions.
  • SMF includes session management (such as session establishment, modification and release, including tunnel maintenance between UPF and RAN), UPF selection and control, service and session continuity (SSC) mode selection, roaming and other session related Function.
  • SMF can be used to select the UPF that serves the user, such as selecting the UPF that is closer to the base station where the user is located, to reduce the user's packet sending and receiving delay.
  • the session management network element may be SMF.
  • the session management network element may still be SMF or have other names, which is not limited by this application.
  • the user plane network element is mainly responsible for the forwarding of user data.
  • the user plane network element may be UPF.
  • future communications such as 6G, the user plane network element may still be UPF or have other names, which is not limited by this application.
  • the data management network element stores the user's subscription data, such as the QoS data of the user's subscription, which is used to provide data storage and query functions.
  • the data management network element may be UDM.
  • future communications such as 6G, the data management network element may still be UDM or have other names, which is not limited by this application.
  • the above application function network elements can be used to select, reselect, locate, and relocate the application server (application service, AS) of the application, and interact with the core network.
  • the application function network element may be AF.
  • future communications such as 6G, the application function network element may still be AF or have other names, which is not limited by this application.
  • the access network elements can be used to support the UE's access to 5G and CN, as well as for the transmission of business data.
  • the access network element may be RAN.
  • future communications such as 6G, the access network element may still be RAN or have other names, which is not limited in this application.
  • an embodiment of the present application provides a communication method to improve the efficiency of UE registration with the network.
  • the communication method may be executed by the UE and the network device.
  • the network device may be a mobility management network element or a device or a network element that has the function of a mobility management network element.
  • the network device may be the AMF shown in FIG. 1.
  • the communication method provided by the embodiment of the present application may include the following steps:
  • the UE receives at least one rejected network slice information and first indication information from the AMF.
  • the AMF is deployed in the first PLMN.
  • Information about rejected network slices can include rejected NSSAI.
  • the UE keeps (keep) the information of the rejected network slice associated with the first PLMN after the first PLMN enters the deregistration state according to the first indication information.
  • the unregistered state refers to a state in which the UE is not registered in any PLMN, the 5GMM context is not established, the location of the UE is unknown to the network device, and the UE is not reachable to the network device.
  • the UE after the UE enters the deregistration state for the first PLMN, it retains the information of the rejected network slices associated with the first PLMN.
  • the information of the rejected network slice associated with the first PLMN includes the information of the rejected network slice indicated by the AMF in the process of the UE requesting to register with the first PLMN (including but not limited to at least the network slice from the AMF in S101).
  • a rejected network slice information includes: after the UE registers with the first PLMN, the information of the rejected network slices indicated by the AMF before the first PLMN goes to register.
  • the first indication information may be used to instruct the UE to retain the information of the rejected network slice associated with the first PLMN after the first PLMN enters the de-registration state.
  • the UE may reserve the information of the rejected network slice associated with the first PLMN after the first PLMN enters the de-registered state by default. That is, the first indication information may not directly indicate that the UE retains the information of the rejected network slice associated with the first PLMN after the first PLMN enters the de-registered state, or may indicate other content, but the UE After receiving the first indication information, after the first PLMN enters the de-registration state, the information of the rejected network slice associated with the first PLMN is retained.
  • the UE can still retain the rejected network slice information associated with the first PLMN after the UE enters the deregistered state from the first PLMN according to the first indication information, so as to learn which network slice information is the rejected network
  • the sliced information can avoid repeated requests for registration based on the rejected network slice information, so as to improve registration efficiency.
  • the UE may delete the rejected network slice information associated with the first PLMN after selecting from the first PLMN to a PLMN other than the first PLMN. Therefore, when the UE requests registration in the first PLMN, it will not The information of the rejected network slice associated with the first PLMN is selected as the requested NSSAI.
  • the UE may receive a first registration rejection message from the AMF, and the first registration rejection message may carry information of at least one rejected network slice and the first indication information.
  • the first registration rejection message may be sent by the AMF after receiving the first registration request message from the UE, and is used to instruct the AMF to reject the first registration request message.
  • the first registration request message may include at least one network slice information, such as at least one requested NSSAI, each NSSAI may provide at least one S-NSSAI, and each S-NSSAI indicates one network slice.
  • the AMF determines that none of the network slices indicated by the S-NSSAI included in the requested NSSAI in the first registration request message is available, it can send a first registration rejection message, where the cause value in the first registration rejection message ) Information element (IE) can be configured as "#62"no network slices available"".
  • IE Information element
  • the first registration rejection message may also carry information about at least one rejected network slice (for example, it carries rejected NSSAI, which is used to indicate at least one S-NSSAI), and the information about at least one rejected network slice may be carried in one or more IE.
  • the first registration rejection message may also carry first indication information, and the first indication information may be carried in one IE.
  • the first registration request message may not carry the information of the rejected network slice.
  • the UE receives a registration rejection message with a reason value of "#62"No network slice available"", it defaults to the first registration sent before.
  • the network slice information carried in the request message is the rejected network slice information. It should be understood that, in this example, the UE may use the network slice information carried in the first registration request message previously sent as the network slice information that is rejected because it is not available in the first PLMN, and because the terminal is located Any one of the information of the network slices that are not available in the registration area of the network slice that is rejected, or the information of the network slices that are rejected because of the verification and authorization failure or revocation of the network slice.
  • the UE may receive a first de-registration request (de-registration request) message from the AMF, and the first de-registration request message may carry information about at least one rejected network slice and The first indication information.
  • the first de-registration request message may be sent by the AMF after the UE is registered to the first PLMN, and is used to instruct the UE to perform de-registration in the first PLMN.
  • the reason why the AMF sends the first de-registration request message may be that the subscription data of the UE is changed and the network slice-specific authentication and authorization (network slice-specific authentication and authorization, NSSAA) fails, and so on.
  • the reason value IE in the first deregistration request message may be configured as "#62"No network slices available"".
  • the first indication information may be the re-registration indication information in the first de-registration request message.
  • the re-registration indication information may be used to indicate that the UE needs to initiate re-registration of the first PLMN after the first PLMN enters the de-registration state.
  • the rejected network slice information associated with the first PLMN in S102 includes but is not limited to the information of at least one rejected network slice shown in S101.
  • the UE receives multiple rejected network slice information from the AMF multiple times, where the information of at least one rejected network slice shown in S101 is part of the information of the multiple rejected network slices. Then the rejected network slice information associated with the first PLMN includes the information of the multiple rejected network slices.
  • the UE may delete the stored information of the rejected network slice associated with the first PLMN according to the indication information.
  • the sixth indication information may be used to indicate that the UE does not need to re-register, or to indicate that the UE does not need to initiate re-registration of the first PLMN, so the UE will not repeatedly request registration to a network slice that has been rejected in the first PLMN.
  • the sixth indication information may be carried in the second de-registration request message.
  • the above re-registration instruction information and non-re-registration instruction information can occupy the same IE in the registration request message.
  • the IE is configured as "1”
  • the IE is the re-registration instruction information.
  • this IE is an indication of no re-registration.
  • the above rejected network slices may include network slices rejected because they are unavailable in the first PLMN, network slices rejected because they are not available in the registration area where the terminal is located, or network slices rejected because they are not available in the first PLMN. At least one of the network slices that was rejected due to authentication and authorization failure or revocation.
  • the UE can learn the rejection reason of the rejected network slice according to the rejection reason information from the AMF, so as to know that the rejected network slice is the network slice rejected because it is not available in the first PLMN (The corresponding rejection reason is not available in the first PLMN), network slices that are rejected because they are not available in the registration area where the terminal is located (the corresponding rejection reason is not available in the registration area where the terminal is located), or Network slices that are rejected due to network slice verification and authorization failure or revocation (corresponding rejection reason is network slice verification and authorization failure or revocation).
  • the rejection reason information corresponds to the S-NSSAI, and is used to indicate that the rejection reason of the network slice corresponding to the S-NSSAI is: rejected because it is not available in the first PLMN, because it is in the registration area where the terminal is located Rejected due to unavailability of the network, or rejected due to failure or revocation of verification and authorization of the network slice.
  • the correspondence between the information of the rejected network slice and the reason for rejection shown in Table 1 can be a registration rejection message, registration acceptance (registration accept) message, configuration update request message or deregistration request message instruct.
  • the information of the rejected network slice and the reason for rejection are carried in the same registration request message or de-registration request message, or the information of the rejected network slice, the reason for rejection, and the information used to indicate the relationship between the two
  • the information of the corresponding relationship is carried in the same registration request message or de-registration request message.
  • the UE may store the rejected network slice information associated with the first PLMN as the rejection reason shown in Table 2.
  • identification 1 indicates that the reason for rejection is unavailable in the first PLMN
  • identification 2 indicates that the reason for rejection is unavailable in the registration area where the terminal is located
  • identification 3 indicates that the reason for rejection is that the verification and authorization of the network slice failed. Or revoke.
  • the UE may store the corresponding relationship shown in Table 2 as the information of the rejected network slice associated with the first PLMN.
  • the UE after the UE enters the de-registered state for the first PLMN, it retains the information of the network slices rejected because it is not available in the first PLMN, for example, retains S-NSSAI_1 and S-NSSAI_1 shown in Table 2. S-NSSAI_2.
  • the first indication information may be used to instruct the UE to retain information about the network slices that are rejected because they are not available in the first PLMN after entering the de-registered state.
  • the UE receives the first indication information by default, after entering the first PLMN and entering the de-registered state, the information of the network slices that are rejected due to being unavailable in the first PLMN is retained.
  • the UE After the UE enters the de-registration state for the first PLMN and determines that the registration area or tracking area where the UE resides has not changed, it retains the information of the network slices that are rejected because they are not available in the registration area where the terminal is located. , For example, keep S-NSSAI_3 and S-NSSAI_4 shown in Table 2. Among them, the registration area or tracking area where the UE resides has not changed, which means that the registration area where the UE is located has not changed after entering the de-registered state with the first PLMN and when the first registration request message is sent to initiate registration, or the UE is located After entering the de-registration state and sending the first registration request message to initiate registration, there is no change in the registration area of.
  • the registration area corresponds to at least one tracking area (in other words, the registration area is composed of at least one tracking area), and the UE does not need to perform mobility registration (ie location registration) when roaming in a certain registration area, in other words, move out of a certain registration area. Mobility registration needs to be performed after each registration area.
  • the tracking area is an area composed of at least one cell and is used to track the location of the UE.
  • the first indication information may be used to instruct the UE to reserve the network rejected because it is unavailable in the registration area where the terminal is located after entering the de-registration state and determining that the registration area or tracking area where the UE resides has not changed Slice information.
  • the UE may enter the de-registration state for the first PLMN by default, and after it is determined that the registration area or tracking area where the UE resides has not changed, the network slices that are rejected because they are not available in the registration area where the terminal is located are reserved. information.
  • the UE may send a second registration request message to the AMF, the second registration request The message does not include network slice information, or in other words, the second registration request message does not carry requested NSSAI.
  • the available network slice information set is specifically an available NSSAI set, including one or more S-NSSAIs.
  • the available NSSAI set includes the information of the network slice permitted by the first PLMN (that is, the allowed NSSAI corresponding to the first PLMN), the information of the network slice configured by the first PLMN (that is, the configured NSSAI corresponding to the first PLMN), and the network configured by default Slice information (ie default configured NSSAI).
  • the UE determines that all the S-NSSAIs in the available network slice information set belong to the rejected NSSAI, the UE sends the second registration request message.
  • the sending of the above second registration request message may be performed after the UE sends the first registration request message.
  • the UE carries the information of the network slice other than the information of the rejected network slice in the available network slice information set in the first registration request message, and sends the first registration request message to the AMF.
  • the UE receives An instruction from AMF (such as the first registration rejection message or the first de-registration request message)
  • AMF an instruction from AMF
  • the UE receives An instruction from AMF (such as the first registration rejection message or the first de-registration request message)
  • the network slice information in the first registration request message is rejected, that is, the network slice information in the network slice information set can be used.
  • the information is the information of the rejected network slice, and the UE may send the second registration request message to the AMF.
  • the UE can send the second registration request message to the AMF, and The first registration request message is no longer sent.
  • the AMF may send the second indication information to the UE.
  • the second indication information may be used to instruct the UE to disable N1 mode capability (disable N1 mode capability).
  • the UE may turn off the N1 mode capability according to the second indication information.
  • the UE no longer attempts to register on the 5G network, and the UE can request registration from a long term evolution (LTE) network, etc., so as to improve the efficiency of the UE's network registration.
  • LTE long term evolution
  • the UE will not re-enable the ability to try the N1 mode in a short period of time (for example, a time length defined by the UE itself).
  • LTE long term evolution
  • the AMF may send the third indication information to the UE.
  • the third indication information may be used to indicate that there is no available default network slice, where there is no available default network slice, for example, no default configured NSSAI, or default configured NSSAI is not available.
  • the UE may turn off the N1 mode capability according to the third indication information, and select from the first PLMN to the second PLMN.
  • the first PLMN and the second PLMN may be the same or different.
  • the UE may save the information of the first PLMN.
  • the information of the first PLMN may be the identity (ID) of the first PLMN.
  • the third indication information is abnormal case indication information, which is used to indicate that the current abnormal situation is present.
  • the UE may turn off the N1 mode capability and select from the first PLMN to the second PLMN after the number of times of receiving the third indication information reaches a threshold (for example, 5 times).
  • the number of times the third indication information is received here may refer to the number of times the UE has received the third indication information during the process of requesting to register with the first PLMN.
  • the UE may increase the count value of the counter of the third indication information (such as the registration attempt counter) each time after receiving the third indication information, and when the count of the counter reaches the threshold, The UE turns off the N1 mode capability and performs PLMN selection. Among them, when the UE is successfully registered (for example, the registration success message is introduced) or PLMN selection is performed, the UE sets the count value of the counter to zero.
  • the UE can also turn off the N1 mode capability after receiving the third indication information for the first time, and select from the first PLMN to the second PLMN, without determining whether the number of times the third indication information has been received reaches the threshold, and further improve the registration efficient.
  • the third indication information may also be used to instruct the UE to turn off the N1 mode capability.
  • the third indication information may also be used to instruct the UE to retain the information of the first PLMN after performing PLMN selection from the first PLMN.
  • the AMF may send fourth indication information to the UE.
  • the fourth indication information may be used to instruct the UE to perform PLMN selection.
  • the UE may select from the first PLMN to the second PLMN according to the fourth indication information.
  • the first PLMN and the second PLMN may be the same or different.
  • the UE may save the information of the first PLMN.
  • the fourth indication information may also be used to instruct the UE to retain the information of the first PLMN after performing PLMN selection from the first PLMN.
  • the information of the first PLMN may be the identity of the first PLMN.
  • the UE may retain the information of the first PLMN after selecting from the first PLMN to the second PLMN.
  • the information of the first PLMN can be used to identify whether the second PLMN is consistent with the first PLMN. After the UE recognizes that the first PLMN is consistent with the second PLMN, the first PLMN can turn off the N1 mode capability to avoid repeated requests for registration in the first PLMN, which can improve registration efficiency.
  • the foregoing third indication information or fourth indication information may also be used to instruct the UE to retain the information of the first PLMN after performing PLMN selection from the first PLMN.
  • the UE may receive the third indication information or the fourth indication information by default, and after selecting from the first PLMN to the second PLMN, the information of the first PLMN is retained.
  • the UE may also turn off the N1 mode capability and select from the first PLMN to the second PLMN after determining that the information of the network slice in the available network slice information set is all the information of the rejected network slice. After selecting the second PLMN, the UE may save the information of the first PLMN.
  • the UE when the UE selects from the first PLMN to the second PLMN, it may also select a PLMN that is different from the first PLMN as the second PLMN according to the information of the first PLMN, so as to avoid repeating requests for registration in the first PLMN.
  • the UE may store the information of the first PLMN in the first PLMN list, and the first PLMN list includes PLMNs with no available network slices, or in other words, there are no available networks among the PLMNs in the first PLMN list. slice. It should be understood that the first PLMN list is retained at least until the UE selects the second PLMN.
  • the UE may store the information of the PLMN that tried to register but failed to register in the first PLMN list.
  • the PLMN that fails to register here refers to a PLMN that cannot be registered because the information of the network slice in the available network slice information set corresponding to the PLMN is rejected.
  • the UE attempts to register in the third PLMN, and because the network slice information in the available network slice information set is rejected by the third PLMN, the UE performs PLMN selection, selects from the third PLMN to the first PLMN, and selects the third PLMN The information is stored in the first PLMN list.
  • the UE may determine the second PLMN according to the first PLMN list, where the second PLMN is not included in the first PLMN list.
  • the UE may determine the second PLMN from the PLMNs that are not included in the first PLMN list, so as to avoid re-selecting PLMNs with no available network slices and improve registration efficiency.
  • the UE When the UE selects a PLMN in the first PLMN list from the first PLMN, the UE can turn off the N1 mode capability to avoid repeated requests to register to the PLMN in the first PLMN list, which can improve registration efficiency.
  • the AMF may also send fifth indication information to the UE, which is used to indicate the information of at least one network slice, and the at least one network slice.
  • the information can be referred to as steering network slice information or other names.
  • the information for guiding the network slice is a network slice that is determined by the AMF according to the slice type (Slice/Service type) and is the same as the type of the network slice that the UE requests to register.
  • the fifth indication information may include at least one guided NSSAI, each guided NSSAI includes at least one guided S-NSSAI, and the number of guided S-NSSAIs does not exceed the number of requested S-NSSAIs carried in the first registration request message.
  • the UE may send a third registration request message to the AMF, which carries at least one S-NSSAI included in the guided NSSAI, and is used to request registration to the network slice indicated by the at least one S-NSSAI.
  • the AMF may send fifth indication information to the UE to instruct the UE to initiate registration by guiding the network slice information, so as to improve registration efficiency.
  • the AMF may also carry the fifth indication information and the information of the at least one rejected network slice shown in S101 and the first indication information in the same message, such as the first registration rejection message or the first deregistration message. Request message.
  • a communication method provided in an embodiment of the present application may include the following steps:
  • S201 The UE sends a first registration request message to the AMF.
  • the requested NSSAI includes multiple S-NSSAIs, and the AMF determines that none of the multiple S-NSSAIs provided by the requested NSSAI are available, then the following steps S202-S204 are executed.
  • the requested NSSAI may include S-NSSAI in allowed NSSAI, configured NSSAI, and/or default configured NSSAI.
  • the AMF determines that there is no S-NSSAI with the default configuration available for the UE, the following steps S205-S206 are executed.
  • the AMF can determine that there is no S-NSSAI with the default configuration available for the UE; or, the UE does not support network-specific slice authentication and authorization.
  • the default subscription S-NSSAI is configured on the network side, all default subscription S-NSSAIs require network-specific slice verification and authorization. Since the UE does not support network-specific slice verification and authorization, AMF can determine that there is no such UE S-NSSAI with default configuration available.
  • S202 The AMF sends a registration rejection message to the UE.
  • the registration rejection message carries the reason value configured as "#62"No network slices available"", rejected NSSAI IE, and first indication information.
  • the rejected NSSAI IE is used to carry the rejected NSSAI
  • the first indication information is used to indicate that the rejected NSSAI carried in the rejected NSSAI IE needs to be saved.
  • S203 The UE stores the rejected NSSAI.
  • the UE can continue to try to register in the first PLMN. If the PLMN selection conditions are met, for example, the number of times the UE has received the third indication information reaches the threshold, or the PLMN selection indication information from the AMF is received, the UE may perform PLMN selection . After the UE performs PLMN selection, the UE will delete the rejected NSSAI.
  • S204 The UE sends a second registration request message to the AMF.
  • the second registration request message sent by the UE to the AMF does not include network slice information, or in other words, the second registration request message does not Carrying the requested NSSAI
  • the AMF determines that there is no S-NSSAI with the default configuration available for the UE according to the second registration request message, the above steps S204-S205 can be performed. If it is determined that the available NSSAI set includes the non-rejected S-NSSAI, the second registration request message sent by the UE to the AMF includes the non-rejected S-NSSAI to request registration to the non-rejected network slice.
  • the available NSSAIs in the NSSAI set include allowed NSSAI and configured NSSAI.
  • the non-rejected S-NSSAI does not belong to the rejected NSSAI.
  • the AMF determines that there is no S-NSSAI with a default configuration available for the UE, and then sends third indication information to the UE.
  • the third indication information is abnormal situation indication information.
  • S206 If the UE determines that the number of times of receiving the third indication information reaches the threshold (5 times), the UE turns off the N1 mode capability to perform PLMN selection. Otherwise, if the UE determines that the number of times the third indication information has been received has not reached the threshold, the UE continues to try to register in the first PLMN, for example, the UE performs S204 again.
  • the UE can determine the rejected NSSAI. If the UE determines that there is no S-NSSAI available in allowed NSSAI and configured NSSAI (such as allowed NSSAI and configured NSSAI, all S-NSSAIs are included in rejected NSSAI, or allowed NSSAI and configured NSSAI do not have S-NSSAI), then the UE The registration request sent when requesting registration does not carry the requested NSSAI.
  • allowed NSSAI and configured NSSAI such as allowed NSSAI and configured NSSAI, all S-NSSAIs are included in rejected NSSAI, or allowed NSSAI and configured NSSAI do not have S-NSSAI
  • the AMF can accept registration and provide new configured NSSAI, or the AMF can reject it and indicate to the UE that an abnormal situation has occurred.
  • the UE closes the N1 mode capability, switches to the S1 mode, performs PLMN reselection, and deletes the saved rejected NSSAI information.
  • a communication method provided by an embodiment of the present application may include the following steps:
  • S301 The UE sends a first registration request message to the AMF.
  • the requested NSSAI may include S-NSSAI in allowed NSSAI, configured NSSAI, and/or default configured NSSAI.
  • the AMF determines that there is no S-NSSAI with the default configuration available for the UE, the following steps S305-S306 are executed.
  • the AMF sends a registration rejection message to the UE.
  • the registration rejection message carries the reason value configured as "#62"No network slices available"", rejected NSSAI IE, and first indication information.
  • the rejected NSSAI IE is used to carry rejected NSSAI
  • the first indication information is used to indicate that the rejected NSSAI carried in the rejected NSSAI IE needs to be stored.
  • S303 The UE stores the rejected NSSAI. After that, the UE continues to try to register in the first PLMN.
  • the UE After the UE performs PLMN selection, the UE will delete the rejected NSSAI.
  • S304 The UE sends a second registration request message to the AMF.
  • the second registration request message sent by the UE to the AMF does not include network slice information, or in other words, the second registration request message does not Carrying the requested NSSAI
  • the AMF determines that there is no S-NSSAI with the default configuration available for the UE according to the second registration request message, steps S305-S306 can be performed. If the UE determines that the available NSSAI set includes the non-rejected S-NSSAI, the second registration request message sent by the UE to the AMF includes the non-rejected S-NSSAI to request registration to the non-rejected network slice.
  • S305 The AMF determines that there is no S-NSSAI with the default configuration available for the UE, and then sends third indication information to the UE.
  • the third indication information is abnormal situation indication information.
  • S306 The UE turns off the N1 mode capability according to the third indication information, and performs PLMN selection.
  • the UE can determine the rejected NSSAI. If the UE determines that there is no S-NSSAI available in allowed NSSAI and configured NSSAI, the registration request sent by the UE when requesting registration does not carry the requested NSSAI. After that, AMF can accept registration and provide new configured NSSAI, or AMF can reject it and send it to The UE indicates that an abnormal situation has occurred. When an abnormal situation occurs, the UE closes the N1 mode capability, switches to the S1 mode, performs PLMN reselection, and deletes the saved rejected NSSAI information.
  • the AMF may also provide a guided NSSAI to the UE, and the UE initiates a registration request according to at least one S-NSSAI in the guided NSSAI to improve registration efficiency.
  • a communication method provided by an embodiment of the present application may include the following steps:
  • S401 The UE sends a first registration request message to the AMF.
  • the requested NSSAI may include S-NSSAI in allowed NSSAI, configured NSSAI, and/or default configured NSSAI.
  • the AMF determines that there is no S-NSSAI with the default configuration available for the UE, the following steps S408-S409 are executed.
  • the AMF determines at least one guided NSSAI according to the requested NSSAI, and each guided NSSAI includes at least one guided S-NSSAI.
  • the type of the network slice indicated by the bootstrap S-NSSAI is the same as the type of the network slice indicated by the requested NSSAI.
  • the AMF sends a registration rejection message to the UE.
  • the registration rejection message includes a guided NSSAI IE, which is used to carry at least one guided NSSAI.
  • the registration rejection message carries the reason value configured as "#62"No network slices available"", rejected NSSAI IE, and first indication information.
  • the rejected NSSAI IE is used to carry rejected NSSAI
  • the first indication information is used to indicate that the rejected NSSAI carried in the rejected NSSAI IE needs to be saved.
  • S404 The UE stores the rejected NSSAI. After that, the UE continues to try to register in the first PLMN.
  • the UE After the UE performs PLMN selection, the UE will delete the rejected NSSAI.
  • S405 The UE adds a guided S-NSSAI to the allowed NSSAI.
  • the UE may replace the S-NSSAI belonging to the rejected NSSAI in the allowed NSSAI with the guided S-NSSAI.
  • the UE determines that the S-NSSAI belongs to rejected NSSAI.
  • the UE sends a third registration request message to the AMF, where the third registration request message includes at least one information for guiding the S-NSSAI.
  • the UE may perform S407. For example, the UE executes S407 after receiving a registration rejection message with a rejection reason of "#62"No network slices available"" for the third registration request message.
  • the AMF may send a registration acceptance message to the UE to indicate successful registration to the network slice corresponding to the guided NSSAI, and S407 is not executed any more.
  • S407 The UE sends a second registration request message to the AMF.
  • the second registration request message sent by the UE to the AMF does not include network slice information, or in other words, the second registration request message does not Carrying the requested NSSAI
  • the AMF determines that there is no S-NSSAI with the default configuration available for the UE according to the second registration request message, steps S408-S409 may be performed. If the UE determines that the available NSSAI set includes the non-rejected S-NSSAI, the second registration request message sent by the UE to the AMF includes the non-rejected S-NSSAI to request registration to the non-rejected network slice.
  • the available NSSAIs in the NSSAI set include allowed NSSAI and configured NSSAI.
  • the non-rejected NSSAI refers to the NSSAI other than the rejected NSSAI stored by the UE.
  • the AMF sends third indication information to the UE.
  • the third indication information is abnormal situation indication information.
  • S409 The UE turns off the N1 mode capability according to the third indication information, and performs PLMN selection.
  • the UE can determine the rejected NSSAI.
  • the AMF can provide the UE with a guided S-NASSI, and the UE will use the guided S-NASSI as the allowed S-NASSI in the NSSAI, and request registration based on the guided S-NASSI first. If the UE still judges that there is no S-NSSAI available in allowed NSSAI and configured NSSAI, the registration request sent by the UE when requesting registration does not carry the requested NSSAI.
  • AMF can accept registration and provide new configured NSSAI, or AMF can reject and Indicates to the UE that an abnormal situation has occurred.
  • the UE closes the N1 mode capability, switches to the S1 mode, performs PLMN reselection, and deletes the saved rejected NSSAI information.
  • a communication method provided by an embodiment of the present application may include the following steps:
  • S501 The UE sends a first registration request message to the AMF.
  • the AMF determines that none of the multiple S-NSSAIs provided by the requested NSSAI are available, then the following steps S502-S505 are executed.
  • the AMF determines that there is no S-NSSAI with the default configuration available for the UE, the following steps S507-S508 are executed.
  • the AMF sends a registration rejection message to the UE.
  • the registration rejection message carries the reason value configured as "#62"No network slices available"", rejected NSSAI IE, and first indication information.
  • the rejected NSSAI IE is used to carry rejected NSSAI
  • the first indication information is used to indicate that the rejected NSSAI carried in the rejected NSSAI IE needs to be stored.
  • S503 The UE stores the rejected NSSAI. After that, the UE continues to try to register in the first PLMN.
  • the UE After the UE performs PLMN selection, the UE will delete the rejected NSSAI.
  • S504-S505 are executed. If the UE determines that the available NSSAI set includes non-rejected S-NSSAI, S506 is executed.
  • S504 The UE selects from the first PLMN to the second PLMN, and retains the information of the first PLMN after the PLMN is selected.
  • the UE can successfully register the second PLMN in the N1 mode, or after the UE turns off the N1 mode, or In the N1 mode, after the UE selects from the second PLMN to another PLMN (may be referred to as the third PLMN), the information of the first PLMN is deleted.
  • the UE can successfully register a certain PLMN in the N1 mode, or delete the first PLMN after the UE turns off the N1 mode List.
  • S505 If the UE determines that the second PLMN is the same as the first PLMN according to the information of the first PLMN, the UE turns off the N1 mode capability, or the UE sends a second registration request message to the AMF, and the second registration request message does not include NSSAI, or That is, the second registration request message does not carry the requested NSSAI. If the AMF determines that there is no S-NSSAI with the default configuration available for the UE according to the second registration request message, S507-S508 can be executed.
  • the second registration request message sent by the UE to the AMF includes the non-rejected S-NSSAI to request registration to the non-rejected network slice. If the AMF determines that the S-NSSAI provided by the second registration request message is not available, steps S502-S505 are executed.
  • the available NSSAIs in the NSSAI set include allowed NSSAI and configured NSSAI.
  • the non-rejected NSSAI refers to the NSSAI other than the rejected NSSAI stored by the UE.
  • the AMF sends third indication information to the UE.
  • the third indication information is abnormal situation indication information.
  • S508 The UE turns off the N1 mode capability according to the third indication information, and performs PLMN selection.
  • the UE can determine the rejected NSSAI. If the UE determines that there is no S-NSSAI available in allowed NSSAI and configured NSSAI, the registration request sent by the UE when requesting registration does not carry the requested NSSAI. After that, AMF can accept registration and provide new configured NSSAI, or AMF can reject it and send it to The UE indicates that an abnormal situation has occurred.
  • the UE When an abnormal situation occurs, the UE closes the N1 mode capability, switches to the S1 mode, performs PLMN reselection, and deletes the saved rejected NSSAI information. In addition, since the UE still stores the information of the first PLMN after performing PLMN reselection, the UE can turn off the N1 mode capability after selecting the first PLMN again, or do not carry network slice information in the registration request message to avoid Repeated registration attempts in the first PLMN.
  • the registration rejection message sent by the AMF according to the first registration request may not carry the rejected NSSAI, and the UE uses the S-NSSAI carried in the first registration request as the rejected NSSAI.
  • a communication method provided by an embodiment of the present application may include the following steps:
  • S601 The UE sends a first registration request message to the AMF.
  • the AMF determines that none of the multiple S-NSSAIs provided by the requested NSSAI are available, then the following steps S302-S304 are executed.
  • the AMF determines that there is no S-NSSAI with the default configuration available for the UE, the following steps S605-S606 are executed.
  • the AMF sends a registration rejection message to the UE.
  • the registration rejection message carries the reason value configured as "#62"No network slices available"" and the first indication information.
  • the first indication information is used to indicate that the rejected NSSAI needs to be saved.
  • the registration rejection message may carry rejected NSSAI IE.
  • the rejected NSSAI IE is used to carry rejected NSSAI, including at least one S-NSSAI, or the UE may default that the S-NSSAI carried in the first registration request message belongs to rejected NSSAI.
  • the reason for rejection of the requested NSSAI is by default that it is unavailable in the registration area where the terminal is located, because it is unavailable in the first PLMN, or the verification and authorization of the network slice fails or is revoked.
  • S603 The UE stores the rejected NSSAI. After that, the UE continues to try to register in the first PLMN.
  • the UE After the UE performs PLMN selection, the UE will delete the rejected NSSAI.
  • S604 The UE sends a second registration request message to the AMF.
  • the UE determines that all S-NSSAIs in the available NSSAI set belong to rejected NSSAIs, the UE sends a second registration request message to AMF.
  • the second registration request message does not include network slice information, or in other words, the second registration request message.
  • the registration request message does not carry the requested NSSAI. If the AMF determines that there is no S-NSSAI with the default configuration available for the UE according to the second registration request message, steps S605-S606 can be performed.
  • the second registration request message sent by the UE to the AMF includes the non-rejected S-NSSAI to request registration to the non-rejected network slice.
  • the available NSSAIs in the NSSAI set include allowed NSSAI and configured NSSAI.
  • the non-rejected NSSAI refers to the NSSAI other than the rejected NSSAI stored by the UE.
  • the AMF sends third indication information to the UE.
  • the third indication information is abnormal situation indication information.
  • S606 The UE turns off the N1 mode capability according to the third indication information to perform PLMN selection.
  • the UE can determine the rejected NSSAI.
  • the rejected NSSAI is indicated by the AMF, or, after the UE receives the registration and message, it uses the requested NSSAI carried in the previous registration request message as the rejected NSSAI.
  • the method and method flow provided in the embodiments of the present application are introduced from the perspective of the functions implemented by the UE and the AMF.
  • the UE and the AMF may include a hardware structure and/or a software module, and the above functions are implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether a certain function among the above-mentioned functions is executed by a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraint conditions of the technical solution.
  • a communication device may include a communication module 801 and a processing module 802, and the communication module 801 and the processing module 802 are coupled with each other.
  • the communication device 800 can be used to perform the steps performed by the UE or the AMF shown in FIGS. 2-7 above.
  • the communication module 801 can be used to support the communication device 800 to communicate.
  • the communication module 801 can also be called a communication unit, a communication interface, a transceiver module or a transceiver unit.
  • the communication module 801 may have a wireless communication function, such as being able to communicate with other communication devices through wireless communication.
  • the processing module 802 can also be referred to as a processing unit, and can be used to support the communication device 800 to perform the processing actions of the session management network element in the above method embodiment, including but not limited to: generating information and messages sent by the communication module 801, and/ Or, demodulate and decode the signal received by the communication module 801 and so on.
  • the communication module 801 may be used to receive at least one rejected network slice information and first indication information from a network device that is deployed in the first PLMN.
  • the processing module 802 may be configured to retain the information of the rejected network slice associated with the first PLMN after the communication device 800 enters the de-registered state for the first PLMN according to the first indication information.
  • the communication module 801 may receive a first registration rejection message from a network device, the first registration rejection message is used to indicate that the first registration request message is rejected, and the first registration rejection message may carry the at least one registered rejection message.
  • the information of the rejected network slice and the first indication information may be received from a network device, the first registration rejection message is used to indicate that the first registration request message is rejected, and the first registration rejection message may carry the at least one registered rejection message.
  • the communication module 801 may receive a first de-registration request message from the network device, where the first de-registration request message is used to instruct the communication device 800 to perform de-registration in the first PLMN.
  • the first deregistration request message may carry the information of the at least one rejected network slice and the first indication information.
  • the first indication information may be the re-registration indication information in the first de-registration request message.
  • the above rejected network slices may include network slices rejected because they are not available in the first PLMN, and rejected because they are not available in the registration area where the communication device 800 is located.
  • the processing module 802 may retain the information of the network slices that are rejected due to being unavailable in the first PLMN after the communication device 800 enters the de-registered state for the first PLMN.
  • the processing module 802 may be in the unregistered state of the first PLMN by the communication device 800, and after it is determined that the registration area or the tracking area where the communication device 800 resides has not changed, the processing module 802 may retain the information on the communication device 800. Information about network slices that are not available and rejected in the registration area where they are located.
  • the processing module 802 determines that the network slice information in the available network slice information set is the information of the rejected network slice, and the communication module 801 may send a second registration request message to the network device. 2.
  • the registration request message does not include network slice information, in other words, the second registration request message does not carry requested NSSAI.
  • the available network slice information set includes information of network slices permitted by the first PLMN, information of network slices configured by the first PLMN, and information of network slices configured by default.
  • the available network slice information set may include allowed NSSAI, configured NSSAI, and default configured NSSAI. Allowed NSSAI and configured NSSAI can be indicated by the network device.
  • the processing module 802 may determine that the information of the network slice in the available network slice information set is all included in the information of the rejected network slice associated with the first PLMN.
  • the communication module 801 may receive second indication information from the network device, and the second indication information may be used to instruct the communication device 800 to turn off the N1 mode capability, and the processing module 802 may turn off according to the second indication information. N1 mode capability.
  • the communication module 801 may receive the third indication information from the network device, and the third indication information is used to indicate that no default network slice is available, and the processing module 802 may close N1 according to the third indication information. Mode capability, and select from the first PLMN to the second PLMN.
  • the processing module 802 may turn off the N1 mode capability after the communication module 801 receives the third indication information for the first time, and select the first PLMN to the second PLMN, or the processing module 802 may determine that the communication module 801 receives the first PLMN. After the number of three indication messages reaches the threshold (for example, 5 times), the N1 mode capability is turned off, and the first PLMN is selected to the second PLMN.
  • the UE may receive fourth indication information from the network device, where the fourth indication information is used to instruct the communication device 800 to perform PLMN selection. Then the processing module 802 can select from the first PLMN to the second PLMN according to the fourth indication information.
  • the processing module 802 may determine the second PLMN according to the information of the first PLMN, and the first PLMN is different from the second PLMN. To avoid repeating the registration request in the first PLMN.
  • the processing module 802 retains the information of the first PLMN after selecting from the first PLMN to the second PLMN.
  • the processing module 802 may store the information of the first PLMN in the first PLMN list.
  • the first PLMN list includes PLMNs with no available network slices. In other words, there are no available network slices for the PLMN in the first PLMN list.
  • the processing module 802 may determine the second PLMN according to the first PLMN list, where the second PLMN is not included in the first PLMN list.
  • the processing module 802 determines that the first PLMN is the same as the second PLMN according to the information of the first PLMN, and the processing module 802 turns off the N1 mode capability.
  • the processing module 802 determines that the second PLMN is the PLMN in the first PLMN list according to the information of the first PLMN, or in other words, the processing module 802 determines that the first PLMN list includes the first PLMN according to the information of the first PLMN. For the second PLMN, the processing module 802 turns off the N1 mode capability.
  • the processing module 802 determines that the candidate PLMNs searched when the N1 mode capability is turned on belong to the first PLMN list, the processing module 802 turns off the N1 mode capability.
  • the communication module 801 may receive fifth indication information from the network device, and the fifth indication information may be used to indicate at least one piece of information for guiding the network slice.
  • the communication module 801 may send a third registration request message to the network device according to the information of the guiding network slicing, where the third registration request message includes at least one guiding network slicing information.
  • the communication module 801 may receive sixth indication information from the network device, the sixth indication information is used to indicate that the UE does not need to re-register, or to indicate that the UE does not need to re-register to the first PLMN . Then the processing module 802 may delete the information of the rejected network slice associated with the first PLMN.
  • the sixth indication information may be included in the second de-registration request message, which is used to instruct the UE to perform de-registration in the first PLMN, and the sixth indication information may specifically be non-re-registration indication information.
  • the above network equipment may include AMF.
  • the communication module 801 may send the information of at least one rejected network slice and the first indication information to the UE.
  • AMF is deployed in the first PLMN.
  • the first indication information may be used to instruct the UE to retain the rejected network slice information associated with the first PLMN after the first PLMN enters the de-registration state.
  • the communication module 801 may send a first registration rejection message or a first de-registration request message to the UE, and the first registration rejection message or the first de-registration request message includes at least one rejected network slice. Information and first instruction information.
  • the first registration rejection message is used to indicate that the first registration request message is rejected, and the first de-registration request message is used to instruct the UE to perform de-registration in the first PLMN.
  • the first indication information may be the re-registration indication information in the first de-registration request message.
  • the re-registration indication information may be used to indicate that the UE needs to re-register the first PLMN after performing de-registration in the first PLMN.
  • the first indication information is specifically used to indicate that after the UE enters the de-registered state in the first PLMN, it retains information about the network slices that are rejected due to being unavailable in the first PLMN.
  • the first indication information may specifically indicate that the UE is in the de-registered state in the first PLMN and the registration area or tracking area where the UE resides remains unchanged. Information about rejected network slices.
  • the communication module 801 may receive a second registration request message from a UE, the second registration request message does not include network slice information, or in other words, the second registration request message does not carry requested NSSAI .
  • the communication module 801 may send second indication information to the UE, the second indication information is used to instruct the UE to turn off the N1 mode capability; or, the communication module 801 may send third indication information to the UE, and the third indication information is used to indicate that there is no available
  • the default network slice and is used to instruct the UE to store the information of the first PLMN after the first PLMN performs PLMN selection; or, the communication module 801 sends fourth indication information to the UE, and the fourth indication information is used to instruct the UE to perform PLMN selection, and used to instruct the UE to store the information of the first PLMN after the first PLMN performs PLMN selection.
  • the communication module 801 may send fifth indication information to the UE, where the fifth indication information is used to indicate at least one boot network slice.
  • the communication module 801 may also receive a third registration request message from the UE, where the third registration request message is used to request access to at least one boot network slice.
  • the third registration request message may include at least one piece of information for guiding the network slice.
  • the communication module 801 may send sixth indication information to the UE, where the sixth indication information is used to indicate that the UE does not need to re-register, or to indicate that the UE does not need to re-register with the first PLMN.
  • the sixth indication information may also be used to instruct the UE to delete the rejected network slice information associated with the first PLMN.
  • the sixth indication information may be included in the second de-registration request message, which is used to instruct the UE to perform de-registration in the first PLMN, and the sixth indication information may specifically be non-re-registration indication information.
  • the communication device provided in the embodiment of the present application may also be composed of hardware components, such as a processor, a memory, or a transceiver, etc., to implement the UPF, the first UE, or the SMF in the present application. Function.
  • FIG. 9 only shows the structure required by the communication device 900 to perform the method shown in the present application, and the present application does not limit the communication device to be provided with more components.
  • the communication device 900 can be used to perform the steps performed by the AMF in the foregoing method embodiments.
  • the communication device 900 may include a communication interface 901, a memory 902, and a processor 903.
  • the communication interface 901 can be used for communication with a communication device, for example, for sending or receiving signals.
  • the memory 902 is coupled with the processor 903 and can be used to store programs and data necessary for the communication device 900 to implement various functions.
  • the processor 903 is configured to support the communication device 900 to perform the processing functions performed by the AMF in the foregoing method, such as determining to generate information and messages sent by the communication interface 901, and/or to demodulate and decode the signals received by the communication interface 901 and many more.
  • the above memory 902 and the processor 903 may be integrated or independent of each other.
  • the communication interface 901 may be a communication port, such as a communication port (or interface) used for communication between network elements.
  • the communication interface 901 may also be referred to as a transceiving unit or a communication unit.
  • the processor 903 can be implemented by a processing chip or a processing circuit.
  • the above communication interface 901 may be used to perform the steps performed by the communication module 801.
  • the processor 903 may be configured to execute the above steps executed by the processing module 802, and details are not described herein again.
  • the communication device 1000 may include a processor 1001, a memory 1002, and a transceiver 1003.
  • the communication device 1000 can be used to perform the steps performed by the UE in the above method embodiments.
  • the above processor 1001 can be used to process the communication protocol and communication data, and to control the first communication device, execute the software program, process the data of the software program, and so on.
  • the memory 1002 may be used to store programs and data, and the processor 1001 may execute the method executed by the first communication device in the embodiment of the present application based on the program.
  • the transceiver 1003 may include a radio frequency unit and an antenna.
  • the radio frequency unit can be used for conversion of baseband signals and radio frequency signals and processing of radio frequency signals.
  • the antenna can be used to send and receive radio frequency signals in the form of electromagnetic waves.
  • the radio frequency unit can also be regarded as the transceiver 1003 only.
  • the communication device 1000 can include a processor 1001, a memory 1002, a transceiver 1003, and an antenna.
  • the communication device 1000 may also include an input and output device, such as a touch screen, a display screen, or a keyboard, etc., which can be used to receive data input by the user and output data to the user. It should be noted that some types of communication devices may not have input and output devices.
  • the processor 1001 can baseband processing the data to be sent and output the baseband signal to the radio frequency unit, and the radio frequency unit performs radio frequency processing on the baseband signal and passes the radio frequency signal through the antenna Send in the form of electromagnetic waves.
  • the radio frequency unit 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 1001, and the processor 1001 converts the baseband signal into data and applies the data to the baseband signal. To process.
  • the processor 1001 may be configured to execute the steps executed by the processing module 802 shown in FIG. 8.
  • the transceiver 1003 can be used to perform the steps performed by the communication module 801 shown in FIG. 8.
  • the communication device may include a processor, and the processor may call an external transceiver and/or memory to implement the above-mentioned functions or steps or operations.
  • the communication device may also include a memory, and the processor can call and execute a program stored in the memory to implement the above-mentioned functions or steps or operations.
  • the communication device may also include a processor and a transceiver (or a communication interface), and the processor calls and executes a program stored in an external memory to implement the above-mentioned functions or steps or operations.
  • the communication device may also include a processor, a memory, and a transceiver.
  • the embodiment of the present application also provides a computer-readable storage medium on which program instructions (or computer programs, instructions) are stored.
  • program instructions or computer programs, instructions
  • the The computer executes the operation performed by the UE or the AMF in the foregoing method embodiment and any one of the possible implementation manners of the method embodiment.
  • an embodiment of the present application also provides a communication method, which can be executed by the UE and the AMF.
  • the method may include the method shown in any one of FIGS. 2-7.
  • this application also provides a computer program product, including program instructions, which when called by a computer for execution, can make the computer implement any of the above method embodiments and method embodiments The operation performed by the UE or AMF in a possible implementation.
  • this application also provides a chip or chip system, which is coupled with a transceiver, and is used to implement the above method embodiment and any one of the possible implementation manners of the method embodiment. Operations performed by AMF.
  • the chip system may include the chip and components such as memory and communication interface.
  • the present application also provides a communication system that can be used to implement the foregoing method embodiment and operations performed by the UE or AMF in any possible implementation manner of the method embodiment.
  • the communication system has an architecture as shown in FIG. 1.
  • this application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Landscapes

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

Abstract

L'invention concerne un procédé et un appareil de communication qui sont utilisés pour améliorer l'efficacité d'un processus d'enregistrement d'un équipement utilisateur (UE). Dans la présente invention, après qu'un UE entre dans un état de désenregistrement par rapport à un réseau mobile terrestre public, l'UE réserve encore des informations de tranches de réseau rejetées associées au réseau mobile terrestre public, afin d'apprendre quels éléments d'informations de tranches de réseau sont des informations relatives à des tranches de réseau rejetées, et d'éviter ainsi de faire des demandes répétées d'enregistrement selon les informations relatives à ces tranches de réseau rejetées, ce qui améliore l'efficacité d'enregistrement.
PCT/CN2021/088655 2020-05-21 2021-04-21 Procédé et appareil de communication WO2021233050A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010437539.9 2020-05-21
CN202010437539.9A CN113709764B (zh) 2020-05-21 2020-05-21 一种通信方法及装置

Publications (1)

Publication Number Publication Date
WO2021233050A1 true WO2021233050A1 (fr) 2021-11-25

Family

ID=78645866

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/088655 WO2021233050A1 (fr) 2020-05-21 2021-04-21 Procédé et appareil de communication

Country Status (2)

Country Link
CN (1) CN113709764B (fr)
WO (1) WO2021233050A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113950141A (zh) * 2021-11-30 2022-01-18 新华三技术有限公司成都分公司 一种终端ue注册方法、装置及设备
CN115412434A (zh) * 2022-08-26 2022-11-29 哲库科技(北京)有限公司 一种切片请求方法和终端设备

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116456389A (zh) * 2022-01-10 2023-07-18 维沃移动通信有限公司 资源控制方法、装置、终端、网络侧设备及可读存储介质
CN114302469B (zh) * 2022-01-14 2024-02-13 Oppo广东移动通信有限公司 小区搜索方法及装置、设备、存储介质
KR20240013566A (ko) * 2022-07-22 2024-01-30 삼성전자주식회사 이동 통신 시스템에서 단말의 이동성을 지원하기 위한 방법 및 장치

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180324576A1 (en) * 2016-04-29 2018-11-08 Motorola Mobility Llc Procedures to support network slicing in a wireless communication system
CN109076446A (zh) * 2016-09-07 2018-12-21 华为技术有限公司 接入控制方法和装置
CN109392038A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 通信方法及源基站、目标基站、核心网设备、终端设备
US20190159115A1 (en) * 2017-11-17 2019-05-23 Blackberry Limited PLMN Selection for Mission Critical Devices
CN110945900A (zh) * 2017-06-19 2020-03-31 夏普株式会社 终端装置、核心网装置
CN110999431A (zh) * 2017-06-17 2020-04-10 Lg电子株式会社 用于在无线通信系统中注册终端的方法及其设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019120109A1 (fr) * 2017-12-20 2019-06-27 华为技术有限公司 Procédé et dispositif de mise à jour d'informations de tranche
CN110391926B (zh) * 2018-04-20 2023-01-13 中国移动通信有限公司研究院 网络切片应用控制方法及装置、通信设备及存储介质
CN114615703A (zh) * 2018-10-09 2022-06-10 华为技术有限公司 一种网络切片接入控制的方法及装置
GB2593436B (en) * 2020-02-12 2022-08-17 Samsung Electronics Co Ltd Slice-specific authentication and authorization

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180324576A1 (en) * 2016-04-29 2018-11-08 Motorola Mobility Llc Procedures to support network slicing in a wireless communication system
CN109076446A (zh) * 2016-09-07 2018-12-21 华为技术有限公司 接入控制方法和装置
CN110999431A (zh) * 2017-06-17 2020-04-10 Lg电子株式会社 用于在无线通信系统中注册终端的方法及其设备
CN110945900A (zh) * 2017-06-19 2020-03-31 夏普株式会社 终端装置、核心网装置
CN109392038A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 通信方法及源基站、目标基站、核心网设备、终端设备
US20190159115A1 (en) * 2017-11-17 2019-05-23 Blackberry Limited PLMN Selection for Mission Critical Devices

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113950141A (zh) * 2021-11-30 2022-01-18 新华三技术有限公司成都分公司 一种终端ue注册方法、装置及设备
CN113950141B (zh) * 2021-11-30 2023-05-26 新华三技术有限公司 一种终端ue注册方法、装置及设备
CN115412434A (zh) * 2022-08-26 2022-11-29 哲库科技(北京)有限公司 一种切片请求方法和终端设备
CN115412434B (zh) * 2022-08-26 2024-02-09 哲库科技(北京)有限公司 一种切片请求方法和终端设备

Also Published As

Publication number Publication date
CN113709764B (zh) 2023-06-27
CN113709764A (zh) 2021-11-26

Similar Documents

Publication Publication Date Title
EP3576458B1 (fr) Procédé de communication, station de base source, station de base cible, dispositif de réseau central et dispositif terminal
WO2021233050A1 (fr) Procédé et appareil de communication
US11979818B2 (en) Communication method and communications apparatus
KR102436804B1 (ko) 세션 관리 방법, 장치 및 시스템
EP4124112B1 (fr) Établissement de contexte initial dans un cadre de tranches de réseau sur la base d'un identificateur nssai trasmis par un dispositif de réseau central vers un dispositif de réseau d'accès
US11800481B2 (en) Communication method and communication apparatus
US20190274181A1 (en) Method and apparatus for initiating user plane path re-establishment and communications system
CN112771903B (zh) 用于会话建立的方法及终端设备
WO2022067643A1 (fr) Procédé et appareil de sélection de cellule et procédé et appareil de radiomessagerie
US20140308966A1 (en) Communications method and system, access network device, terminal, and core network device
US20220353756A1 (en) Communication method, apparatus, and system
US20230388908A1 (en) Network slice-based communication method and apparatus
US20240137891A1 (en) Method for performing onboarding and apparatus
CN111757312A (zh) 一种会话的处理方法及装置
US20220141763A1 (en) Managing mode of access to a compatible set of network slices
WO2018203258A1 (fr) Cause d'établissement de tranchage et informations de tranchage demandées
US20230292386A1 (en) Method, apparatus and computer program
WO2022214094A1 (fr) Procédé et appareil de transfert de réseau
US20230328501A1 (en) Method, apparatus and computer program
WO2024012304A1 (fr) Procédé et appareil de réception de service de multidiffusion, terminal et dispositif côté réseau

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21808852

Country of ref document: EP

Kind code of ref document: A1