WO2023213112A1 - 通信方法和装置 - Google Patents

通信方法和装置 Download PDF

Info

Publication number
WO2023213112A1
WO2023213112A1 PCT/CN2023/077195 CN2023077195W WO2023213112A1 WO 2023213112 A1 WO2023213112 A1 WO 2023213112A1 CN 2023077195 W CN2023077195 W CN 2023077195W WO 2023213112 A1 WO2023213112 A1 WO 2023213112A1
Authority
WO
WIPO (PCT)
Prior art keywords
access
terminal device
network slice
network element
mobility management
Prior art date
Application number
PCT/CN2023/077195
Other languages
English (en)
French (fr)
Inventor
孙海洋
朱方园
许胜锋
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023213112A1 publication Critical patent/WO2023213112A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information

Definitions

  • the embodiments of the present application relate to the field of communication, and more specifically, to a communication method and device.
  • the core network has a limit on the number of terminal devices that can be accessed.
  • the network slice admission control function (NSACF) network element can monitor the access to each network slice.
  • the number of terminal devices At present, the following scenario may occur: a large number of terminal devices may request to access the network slice, but the corresponding protocol data unit (PDU) session will not necessarily be established.
  • PDU protocol data unit
  • NSACF may refuse the terminal device to access the network slice due to the limit on the number of terminal devices connected to the network slice.
  • the PDU session resources cannot be reasonably configured and used, reducing user experience. Business experience.
  • Embodiments of the present application provide a communication method and device. If the access and mobility management function network element determines that the protocol data unit PDU session status of the terminal device does not meet the first condition of network slicing after a first time has elapsed (wherein, in this application (the first condition is a condition related to the PDU session status of the terminal device), it is determined that the terminal device is denied access to the network slice, so that the PDU session resources in the network slice can be reasonably configured and used.
  • the first condition is a condition related to the PDU session status of the terminal device
  • the first aspect provides a communication method, which can be executed by the access and mobility management function network element, or can also be executed by the component (such as a chip or circuit) of the access and mobility management function network element. This is not a limitation.
  • the method includes: the access and mobility management function network element determines the first time; after the first time times out, if the session state of the protocol data unit PDU of the terminal device does not meet the first condition of network slicing, the access and mobility management The functional network element denies the terminal device access to the network slice, where the first condition includes at least one of the following: the terminal device establishes a PDU session for the network slice; or the PDU session established by the terminal device for the network slice has an activated user plane; or , the PDU session established by the terminal device for the network slice contains data for transmitting the first service.
  • the access and mobility management function network element starts a timer, and the duration of the timer is the first time; after the timer times out, the access and mobility management function network element determines Whether the first condition is met, wherein the first condition includes at least one of the following: the terminal device establishes a PDU session for the first network slice, or the PDU session established by the terminal device for the first network slice exists Activated user interface, or; The PDU session established by the terminal device for the first network slice contains data for transmitting the first service; if the access and mobility management function network element determination result does not meet the first condition, the access and mobility management function The network element denies the terminal device access to the first network slice.
  • the time when the access and mobility management function network element starts the timer may be, for example, the time when the access and mobility management function network element receives a message from the terminal device requesting access to the network slice.
  • the access and mobility management function network element can determine whether the terminal device has established a PDU session for the network slice after the timer times out; or whether there is an activated user plane in the PDU session established for the network slice; or Whether the data of the first service is transmitted in the PDU session established by the network slice.
  • the time to start the timer may be the time when the access and mobility management function network element senses that the terminal device releases one of the PDU sessions (for example, PDU session #12) established for the network slice.
  • the access and mobility management function network element can determine whether the terminal device has established a PDU session for the network slice after the timer times out; or whether there is an activated user plane in the PDU session established for the network slice; or Whether the data of the first service is transmitted in the PDU session established by the network slice.
  • the time to start the timer may be the time when the access and mobility management function network element senses that the terminal device completes the establishment of a PDU session (for example, PDU session #1) for the network slice for the first time (in this scenario, the first condition It may be that the PDU session established by the terminal device for the network slice has an activated user plane; or that the PDU session established by the terminal device for the network slice contains data for transmitting the first service).
  • the access and mobility management function network element can determine whether there is an activated user plane in the PDU session established for the network slice after the timer expires; or whether there is an active user plane in the PDU session established for the network slice.
  • a business data may be the time when the access and mobility management function network element senses that the terminal device completes the establishment of a PDU session (for example, PDU session #1) for the network slice for the first time (in this scenario, the first condition It may be that the PDU session established by the terminal device for the network slice has an activated user plane; or that the PDU
  • the time to start the timer may be the time when the access and mobility management function network element senses the deactivated user plane in the PDU session established by the terminal device for the network slice (in this scenario, the first condition may be: The PDU session established by the terminal device for the network slice has an activated user plane; or the PDU session established by the terminal device for the network slice includes data for transmitting the first service).
  • the access and mobility management function network element can determine whether there is an activated user plane in the PDU session established for the network slice after the timer expires; or whether there is an active user plane in the PDU session established for the network slice.
  • a business data may be the time when the access and mobility management function network element senses the deactivated user plane in the PDU session established by the terminal device for the network slice (in this scenario, the first condition may be: The PDU session established by the terminal device for the network slice has an activated user plane; or the PDU session established by the terminal device for the network slice includes data for transmitting the first service).
  • the time when starting the timer may be the time when the access and mobility management function network element determines the end time of the first service (for example, the access and mobility management function network element may determine the first time based on the end time of the subscribed first service). end of business).
  • the first condition may be: the PDU session established by the terminal device for the network slice has an activated user plane; or the PDU session established by the terminal device for the network slice has a transmission third a business data).
  • the access and mobility management function network element can determine whether there is an activated user plane in the PDU session established for the network slice after the timer expires; or whether there is an active user plane in the PDU session established for the network slice.
  • a business data may be the time when the access and mobility management function network element determines the end time of the first service (for example, the access and mobility management function network element may determine the first time based on the end time of the subscribed first service). end of business).
  • the first condition may be: the PDU session established by the terminal device for the network slice
  • This method can also be understood as: before the first time expires, if the session state of the PDU of the terminal device meets the first condition of network slicing, the access and mobility management function network element allows the terminal device to access the network slice.
  • the first condition may also include at least one of the following: the terminal device does not establish a PDU session for the network slice; or, the terminal device does not have an activated user plane in the PDU session established for the network slice; or, the terminal device does not have an activated user plane in the PDU session established for the network slice.
  • the data of the first service is not transmitted in the PDU session established by the terminal device for the network slice.
  • This method can also be understood as: after the first timeout, if the session state of the PDU of the terminal device meets the first condition of network slicing, the access and mobility management function network element refuses the terminal device to access the network slice.
  • first condition in this application may be a condition related to whether the terminal device establishes a PDU session for the network slice and the status of the established PDU session, and is not limited to the conditions listed in this application.
  • the "first time” can be understood as a time period, for example; and for another example, the “first time” can be a time unit.
  • a “time unit” may be one or more radio frames, one or more subframes, one or more time slots, one or more mini-slots, one or more symbols, etc.
  • the symbols can be orthogonal frequency division multiplexing (OFDM) symbols, discrete fourier transform spread spectrum orthogonal frequency division multiplexing (DFT-S- OFDM) symbols, etc.
  • the first time can also be 1 second (second, "s” for short) or multiple seconds, 1 millisecond (millisecond, "ms” for short) or multiple milliseconds, etc.
  • one network slice can allow access to multiple terminal devices, and each accessed terminal device can establish multiple PDU sessions for the network slice.
  • the terminal device establishes a PDU session for the network slice in the first condition can be understood to mean that the terminal device can satisfy the first condition as long as it establishes any PDU session for the network slice.
  • the terminal device for the network slice contains data for transmitting the first service
  • any PDU session established by the terminal device for the network slice contains data for transmitting the first service, that is, The first condition can be satisfied.
  • the user plane is activated in the established PDU session can be understood to mean that there is data transmission in the established PDU session.
  • the “first service” in this application may refer to any one of the multiple data transmission services of the terminal device, or may refer to a specific service among the multiple data transmission services of the terminal device (it may also be understood as a specific service). application), are not limited.
  • the access and mobility management function network element can subscribe to the session management function network element or the policy control management network element for the start event or end time of the first service.
  • the access and mobility management function network element can determine the PDU session status of the terminal device after the first time and the first condition, that is, if the access and mobility management function network element determines the PDU session status of the terminal device after the first time. If the first condition of network slicing is not met, it is determined that the terminal device is denied access to the network slicing. This ensures that no terminal device will access the network slice for a long time without establishing/activating a PDU session, which improves the usage efficiency of PDU session resources in the network slice and improves the user's business experience.
  • the method further includes: the access and mobility management function network element obtains information indicating the first time.
  • the access and mobility management function network element can obtain the information indicating the first time from the NSACF; or the access and mobility management function network element can obtain the information indicating the first time from the UDM; or the access and mobility management function network element can obtain the information indicating the first time from the NSACF.
  • Information indicating the first time can be pre-configured, etc. are not limited.
  • the access and mobility management function network element can obtain information indicating the first time through multiple methods, making the method for the access and mobility management function network element to determine the first time more flexible.
  • the method further includes: the access and mobility management function network element obtains attribute information of the network slice, and the access and mobility management function network element determines the first condition based on the attribute information.
  • the attribute information includes at least one of the following: after the first timeout, if the terminal If the device does not establish a PDU session for the network slice, the access and mobility management function network element refuses the terminal device to access the network slice; or, after the first timeout, if the PDU session established by the terminal device for the network slice is not activated user plane, the access and mobility management function network element refuses the terminal device to access the network slice; or, after the first timeout, if the terminal device does not transmit the data of the first service in the PDU session established for the network slice , then the access and mobility management function network element refuses the terminal device to access the network slice.
  • the attribute information of the network slice may include at least one of the following: before the first time times out, if the terminal device establishes a PDU session for the network slice, the terminal device is allowed to access the network slice. ; Or, before the first time times out, if the PDU session established by the terminal device for the network slice has an activated user plane, the access and mobility management function network element allows the terminal device to access the network slice; or , before the first time times out, if the PDU session established by the terminal device for the network slice contains data for transmitting the first service, the access and mobility management function network element allows the terminal device to access the network slice.
  • the access and mobility management function network element can determine the first condition based on the attribute information. Different attribute information corresponds to different first conditions, making the implementation of the access and mobility management function network element more efficient. flexible. Moreover, the access and mobility management function network element can determine whether it is necessary to deny access to the terminal device on the network slice based on different attribute control of the network slice, that is, the access and mobility management function network element can control the terminals accessing the network slice. The control of the equipment is more flexible.
  • the method further includes: before the access and mobility management function network element refuses the terminal device to access the network slice, the access and mobility management function network element sends the first time to the terminal device.
  • the terminal device can sense that if the PDU session has not been established after the first time, or there is no activated user plane in the established PDU session, or the data of the first service is transmitted in the established PDU session, will be denied access to the network slice.
  • the method further includes: the access and mobility management function network element sends a reason value to the terminal device for the access and mobility management function network element rejecting the terminal device to access the network slice, where the reason value includes At least one of the following: the terminal device does not establish a PDU session for the network slice; or the PDU session established by the terminal device for the network slice does not have an activated user plane; or the PDU session established by the terminal device for the network slice does not transmit the third A business data.
  • the access and mobility management function network element can send the reason value for denying the terminal device access to the network slice to the terminal device, so that the terminal device can learn the reason for being denied access to the network slice, and subsequently You can establish a PDU session before the first timeout and re-request access to the network slice.
  • the access and mobility management function network element receives indication information from the terminal device that the terminal device is about to establish a PDU session; the access and mobility management function network element determines the first time based on the indication information.
  • the indication information may be a follow on indication, and the indication information is used to indicate that the terminal device is about to establish a PDU session.
  • the access and mobility management function network element can determine to extend the first time based on the indication information, or reset the first time to a value greater than the initially determined first time, or set the first time in multiple preconfigured first times. The value in which the determined time is greater than the first time initially determined, and so on.
  • this application introduces a "new PDU session state" (that is, the state in which the terminal device is about to establish a PDU session), so that the access and mobility management function network element can be based on the state in which the terminal device is about to establish a PDU session. status to ensure that the terminal device will not be denied access to the network slice.
  • This not only improves the configuration and usage efficiency of PDU sessions in network slicing, but also improves the efficiency of terminal devices accessing network slicing.
  • the second aspect provides a communication method, which can be executed by a terminal device (for example, a UE), or can also be executed by a component of the terminal device (for example, a chip or a circuit), which is not limited.
  • a terminal device for example, a UE
  • a component of the terminal device for example, a chip or a circuit
  • the method includes: the terminal device sends information requesting access to network slicing to the access and mobility management function network element; the terminal device receives the first time from the access and mobility management function network element; after the first time times out, if the terminal If the session status of the protocol data unit PDU of the device does not meet the first condition, the terminal device receives information rejecting access to the network slice from the access and mobility management function network element, where the first condition includes at least one of the following: the terminal device is The network slice establishes a PDU session; or the PDU session established by the terminal device for the network slice has an activated user plane; or the PDU session established by the terminal device for the network slice contains data for transmitting the first service.
  • the terminal device can send request access network slicing information to the access and mobility management function network element. If the PDU session status of the terminal device does not comply with the attributes of the network device, it will be denied access to the network. Slicing ensures that no UE will access the network slice for a long time without establishing/activating a PDU session, which improves the usage efficiency of PDU session resources in the network slice and improves the user's business experience.
  • the method further includes: the terminal device sending indication information that the terminal device will establish a PDU session to the access and mobility management function network element, and the indication information is used for the access and mobility management function network element to determine first timing.
  • this application introduces a "new PDU session state" (that is, the state in which the terminal device is about to establish a PDU session), so that the access and mobility management function network element can be based on the state in which the terminal device is about to establish a PDU session. status to ensure that the terminal device will not be denied access to the network slice.
  • This not only improves the configuration and usage efficiency of PDU sessions in network slicing, but also improves the efficiency of terminal devices accessing network slicing.
  • a communication method is provided, which method can be executed by the access and mobility management function network element, or can also be executed by the component (such as a chip or circuit) of the access and mobility management function network element. This is not a limitation.
  • the access and mobility management function network element determines the attribute information of the network slice; the access and mobility management function network element determines the attribute information of the network slice according to the attribute information of the network slice and the protocol data unit PDU session status of the terminal device.
  • the access and mobility management function network element sends the number N to the network slice admission control function network element;
  • the attribute information of the network slice includes at least one of the following: if the terminal device does not establish a PDU session for the network slice, the access and mobility management function network element refuses the terminal device to access the network slice; or, if the terminal device establishes a PDU session for the network slice, If there is no activated user plane in the PDU session, the access and mobility management function network element refuses the terminal device to access the network slice; or if the PDU session established by the terminal device for the network slice does not transmit data of the first service, the access and mobility management function network element refuses the terminal device to access the network slice. The access and mobility management function network element refuses the terminal device to access the network slice.
  • the access and mobility management function network element can set the number of terminal devices that report this access network slice according to the PDU session status and the attribute information of the network slice. It can effectively avoid occupying the quota of the terminal device accessing the network slice when the terminal device requests access to the network slice without establishing/activating the PDU session. That is, it improves the configuration and use efficiency of PDU session resources in the network slice and improves the user experience. business experience.
  • the access and mobility management function network element determines the number N of terminal devices accessing the network slice based on the attribute information of the network slice and the PDU session status of the terminal device, including: if the access and mobility The management function network element determines that the PDU session state of the terminal device does not comply with the attributes of the network slice, and the AMF determines that N is less than 1.
  • the AMF can set N to a real number less than 1, thereby avoiding When requesting access to a network slice without establishing/activating a PDU session, the quota of the terminal device accessing the network slice is occupied.
  • the method further includes: the access and mobility management function network element receiving indication information from the terminal device that the terminal device is about to establish the PDU session; the access and mobility management function network element according to the network slicing
  • the attribute information of the network slice and the PDU session status of the terminal device are determined to determine the number N of terminal devices accessing the network slice, including: the access and mobility management function network element is based on the attribute information of the network slice, the PDU session status of the terminal device and the indication information. It is determined that N is greater than 0.
  • this application introduces a "new PDU session state" (that is, the state in which the terminal device is about to establish a PDU session), so that the access and mobility management function network element can establish a PDU session based on the terminal device. status to ensure that the terminal device will not be denied access to the network slice.
  • This not only improves the configuration and usage efficiency of PDU sessions in network slicing, but also improves the efficiency of terminal devices accessing network slicing.
  • the fourth aspect provides a communication method, which can be executed by a network slice admission control function network element, or can also be executed by a component (such as a chip or circuit) of a network slice admission control function network element. In this regard Not limited.
  • the method includes: the network slice admission control function network element obtains the protocol data unit PDU session status of the terminal device, wherein the network slice admission control function network element is configured with attribute information of the network slice; the network slice admission control function network element Determine whether to access and trigger the mobility management function network element to deny the terminal device access to the network slice according to the PDU session status of the terminal device and/or the attribute information of the network slice; wherein the attribute information of the network slice includes at least one of the following Item: If the terminal device does not establish a PDU session for the network slice, the access and mobility management function network element refuses the terminal device to access the network slice; or if the terminal device does not establish an activated user plane in the PDU session for the network slice, then The network element with the access and mobility management function refuses the terminal device to access the network slice; or, if the PDU session established by the terminal device for the network slice does not transmit the data of the first service, the network element with the access and mobility management function refuses the terminal device to access the network slice. into the network slice.
  • the network element with the network slice access control function can deny the terminal device access to the network slice based on the obtained PDU session status and determines that the PDU session status of the terminal device does not meet the attributes of the network slice. . This ensures that no terminal device will register for a long time without establishing/activating a PDU session, improves the usage efficiency of PDU session resources in network slicing, and improves the service experience of user equipment.
  • the network slice admission control function network element obtains the PDU session status of the terminal device, including: the network slice admission control function network element obtains the PDU session of the terminal device from the access and mobility management function network element status; or, the network slice admission control function network element obtains the PDU session status of the terminal device from the session management function network element through the access and mobility management function network element; or, the network slice admission control function network element obtains the PDU session status of the terminal device from the network opening function network element Get the PDU session status of the terminal device.
  • the network slice admission control function network element is a first network slice admission control function network element, and the network slice admission control function network element obtains the PDU session status of the terminal device, including: the first network The slice admission control function network element obtains the address information of the second network slice admission control function network element, where the first network slice admission control function network element is used to manage the number of terminal devices, and the second network slice admission control function The network element is used to manage the number of PDU sessions; the first network slice admission control function network element is based on the second network slice admission control function network element.
  • the address information of the network slice is requested to the second network slice admission control function network element to obtain the PDU session status of the terminal device; the first network slice admission control function network element receives the PDU session status of the terminal device from the second network slice admission control function network element. PDU session status.
  • the first network slice admission control function network element obtains the address information of the second network slice admission control function network element, including: the first network slice admission control function network element sends a request to the access and The mobility management function network element requests or subscribes to the address information of the second network slice admission control function network element; the first network slice admission control function network element receives the second network slice admission control from the access and mobility management function network element Address information of functional network elements.
  • the network slice admission control function network element acquisition can flexibly obtain the PDU session status of the terminal device in a variety of ways.
  • the network slice admission control function network element determines whether to trigger the access and mobility management function network element to deny the terminal device access to the network slice based on the PDU session status of the terminal device and the attribute information of the network slice. Including: when the PDU session status of the terminal device does not meet the attributes of the network slice, the network slice admission control function network element determines to trigger the mobility management function network element to deny the terminal device access to the network slice.
  • the network slice access control function network element determines that the PDU session status of the terminal device does not meet the attributes of the network slice, thereby denying the terminal device access to the network slice, and the usage efficiency of PDU session resources is improved. Service experience of user equipment.
  • the method also includes: the network slice admission control function network element receives indication information from the access and mobility management function network element that the terminal device is about to establish a PDU session; the network slice admission control function network element The network element determines whether to trigger the access and mobility management function according to the PDU session status of the terminal device and the attribute information of the network slice. The network element refuses the terminal device to access the network slice, including: when the session status of the PDU of the terminal device does not meet the network slice In the case of attributes, the network slice admission control function network element determines according to the indication information not to trigger the mobility management function network element to deny the terminal device access to the network slice.
  • the access and mobility management function network element can determine that the terminal device will not be denied access to the network slice based on the status of the terminal device about to establish a PDU session. This not only improves the configuration and usage efficiency of PDU sessions in network slicing, but also improves the efficiency of terminal devices accessing network slicing.
  • the network slice admission control function network element that manages the terminal device can update the threshold of the number of terminal devices allowed to register on the network slice according to the PDU session status of the access terminal device. For example, when there are too many terminal devices that have not established a PDU session or have not activated the user plane, the network slice admission control function network element can increase the threshold of the number of terminal devices allowed to register on the network slice (for example, increase the number of terminal devices allowed to register on the network slice).
  • the number of terminal devices allowed to register is 30% of the number of terminal devices that have not established a PDU session or the number of terminal devices that have not activated the user plane, etc.).
  • the network slice admission control function network element that manages terminal devices may not change the threshold, but the number of terminal devices allowed to access exceeds the threshold of the number of terminal devices allowed to register on the network slice. (For example, it may exceed at most 30% of the number of terminal devices without establishing a PDU session or the number of terminal devices without activating the user plane, etc.). Further, if the number of actually registered terminal devices has exceeded the updated threshold, at this time the network slice admission control function network element can notify the access and mobility management control function network element that "the maximum number of registered terminal devices in the network slice has been reached.” quantity". At this time, it can also be understood that the network slice access control function network element that manages the terminal device can determine whether to trigger the access and mobility management function network element to deny the terminal device access to the network based only on the PDU session status of the terminal device. slice.
  • the network slice admission control function network element that manages the terminal device can reset the maximum number of terminal devices allowed to be registered on the network slice.
  • the network slice access control function network element that manages the terminal device can check the PDU session status (for example, it can be reported by the access and mobility management control function network element), and can based on the reported PDU session status of each terminal device.
  • the number of terminal devices allowed to register on the network slice is increased to 30% of the number of terminal devices that have not established a PDU session or that have not activated the user plane.
  • the network element with the network slice admission control function that manages terminal devices can maintain a counter to record the number of actual registered users exceeding the maximum number of terminal devices allowed to be registered in the network slice. If the network element that manages the network slice admission control function of the terminal device finds based on this counter (or based on the operator's policy) that the number of actual registered terminal devices exceeds the maximum number of terminal devices allowed to be registered in the network slice, it has reached the point where no PDU is established.
  • the threshold of the number of terminal devices in the session or the number of terminal devices without activated user plane for example, 30%.
  • the network element with the network slice access control function that manages the terminal device can determine whether to provide access to the access and mobility management control function network. Meta notification "The maximum number of registered end devices for the network slice has been reached".
  • a fifth aspect provides a communication method, which may be executed by a terminal device (eg, UE), or may be executed by a component of the terminal device (eg, chip or circuit), which is not limited.
  • a terminal device eg, UE
  • a component of the terminal device eg, chip or circuit
  • the method includes: the terminal device sends information about the network slice that the terminal device requests to access to the access and mobility management function network element; the terminal device sends to the access and mobility management function network element that the terminal device will establish a PDU session for the network slice. Instruction information; wherein, the instruction information is used for the access and mobility management function network element to determine the number N of terminal devices accessing the network slice, wherein the N is greater than 0; or, the instruction information is used for network slice admission
  • the control function network element determines not to trigger the mobility management function network element to deny the terminal device access to the network slice.
  • this application introduces a "new PDU session state" (that is, the state in which the terminal device is about to establish a PDU session), so that the access and mobility management function network element can establish a PDU session based on the terminal device. status to ensure that the terminal device will not be denied access to the network slice.
  • This not only improves the configuration and usage efficiency of PDU sessions in network slicing, but also improves the efficiency of terminal devices accessing network slicing.
  • a communication device which is used to perform the method in any of the possible implementation modes of the above-mentioned first to fifth aspects.
  • the device may include units and/or modules for performing the method in any possible implementation of the first to fifth aspects, such as a transceiver unit and/or a processing unit.
  • the device is a communication device (for example: an access and mobility management function network element, or a terminal device, or a network slice admission control function network element).
  • the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the device is a chip, chip system or circuit used for communication equipment (for example: access and mobility management function network element, or terminal equipment, or network slice admission control function network element).
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit, etc.
  • the processing unit may be at least one processor, processing circuit or logic circuit, etc.
  • a communication device in a seventh aspect, includes: at least one processor for executing computer programs or instructions stored in a memory to perform any of the possible implementations of the first aspect and the third aspect. method.
  • the device further includes a memory for storing computer programs or instructions.
  • the device also includes a Communication interface, the processor reads the computer program or instructions stored in the memory through the communication interface.
  • the device is an access and mobility management function network element.
  • the device is a chip, chip system or circuit used for access and mobility management function network elements.
  • a communication device in an eighth aspect, includes: at least one processor for executing computer programs or instructions stored in a memory to perform any of the possible implementations of the second aspect or the fifth aspect. method.
  • the device further includes a memory for storing computer programs or instructions.
  • the device further includes a communication interface, through which the processor reads the computer program or instructions stored in the memory.
  • the device is a terminal device.
  • the device is a chip, a chip system or a circuit for a terminal device.
  • a ninth aspect provides a communication device, which includes: at least one processor configured to execute computer programs or instructions stored in a memory to execute the method in any of the possible implementations of the fourth aspect.
  • the device further includes a memory for storing computer programs or instructions.
  • the device further includes a communication interface, through which the processor reads the computer program or instructions stored in the memory.
  • the device is a network slice admission control function network element.
  • the device is a chip, chip system or circuit used for network slicing admission control functional network elements.
  • this application provides a processor, including: an input circuit, an output circuit and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in any one of the possible implementations of any one of the first to fifth aspects. .
  • the above-mentioned processor can be one or more chips
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a flip-flop and various logic circuits, etc.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, a transceiver.
  • the signal output by the output circuit may be, for example, but not limited to, output to a transmitter and transmitted by the transmitter, and the input circuit and the output A circuit may be the same circuit that functions as an input circuit and an output circuit at different times.
  • the embodiments of this application do not limit the specific implementation methods of the processor and various circuits.
  • processor output, reception, input and other operations can be understood as processor output, reception, input and other operations.
  • transmitting and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in this application.
  • a processing device including a processor and a memory.
  • the processor is used to read instructions stored in the memory, and can receive signals through a transceiver and transmit signals through a transmitter to execute the method in any possible implementation manner of any one of the first to fifth aspects.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated on the same chip as the processor, or can be set in different On the chip, the embodiment of the present application does not limit the type of memory and the arrangement of the memory and the processor.
  • ROM read-only memory
  • the relevant data interaction process such as sending instruction information
  • Receiving capability information may be a process in which the processor receives input capability information.
  • the data output by the processor can be output to the transmitter, and the input data received by the processor can be from the transceiver.
  • the transmitter and the transceiver can be collectively referred to as the transceiver.
  • the processing device in the above eleventh aspect may be one or more chips.
  • the processor in the processing device can be implemented by hardware or software.
  • the processor can be a logic circuit, an integrated circuit, etc.;
  • the processor can be a general processor, which is implemented by reading software codes stored in a memory, and the memory can Integrated in the processor, it can be located outside the processor and exist independently.
  • a computer-readable storage medium stores a program code for device execution.
  • the program code includes a program code for executing any of the possible implementations of the above-mentioned first to fifth aspects. Methods.
  • a computer program product containing instructions is provided.
  • the computer program product When the computer program product is run on a computer, it causes the computer to execute the method in any of the possible implementation modes of the first to fifth aspects.
  • a communication system in a fifteenth aspect, includes: an access and mobility management functional network element and a terminal device.
  • the access and mobility management functional network element is used to perform any one of the above first aspects.
  • the method in any possible implementation manner of the second aspect, the terminal device is configured to perform the method in any possible implementation manner of the second aspect.
  • a communication system in a sixteenth aspect, includes: an access and mobility management functional network element and a terminal device.
  • the access and mobility management functional network element is used to perform any one of the above third aspects.
  • the method in any possible implementation manner, the terminal device is configured to perform the method in any possible implementation manner of the fifth aspect.
  • a communication system in a seventeenth aspect, includes: an access and mobility management function network element and a terminal device.
  • the access and mobility management function network element is used to perform any one of the above fourth aspects.
  • the method in any possible implementation manner, the terminal device is configured to perform the method in any possible implementation manner of the fifth aspect.
  • Figure 1 is a schematic diagram of a system architecture applicable to this application.
  • FIG. 2 is a schematic block diagram of the communication method 200 proposed in this application.
  • Figure 3 is a schematic flow chart of the communication method 300 proposed in this application.
  • Figure 4 is a schematic block diagram of the communication method 400 proposed in this application.
  • Figure 5 is a schematic flow chart of the communication method 500 proposed in this application.
  • Figure 6 is a schematic block diagram of the communication method 600 proposed in this application.
  • Figure 7 is a schematic flow chart of the communication method 700 proposed in this application.
  • FIG. 8 is a schematic block diagram of the communication device 100 proposed in this application.
  • Figure 9 is a schematic block diagram of the communication device 200 proposed in this application.
  • the wireless communication systems mentioned in this application include but are not limited to: global system of mobile communication (GSM) system, long term evolution (LTE) frequency division duplex (FDD) system, LTE Time division duplex (TDD), LTE system, advanced long-term evolution (LTE-Advanced, LTE-A) system, next-generation communication system (for example, 6G communication system), A converged system of multiple access systems, or an evolutionary system.
  • GSM global system of mobile communication
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD LTE Time division duplex
  • LTE-A advanced long-term evolution
  • next-generation communication system for example, 6G communication system
  • a converged system of multiple access systems or an evolutionary system.
  • the technical solution provided by this application can also be applied to machine type communication (MTC), long term evolution-machine (LTE-M), and device to device (D2D) networks.
  • M2M machine to machine
  • IoT Internet of things
  • the IoT network may include, for example, the Internet of Vehicles.
  • the communication methods in the Internet of Vehicles system are collectively called vehicle to other devices (vehicle to X, V2X, X can represent anything).
  • the V2X can include: vehicle to vehicle (vehicle to vehicle, V2V) communication.
  • the technical solution proposed in this application can be applied to the 5th generation (5G) mobile communication technology and other future mobile communication technologies, such as non-roaming scenarios and roaming scenarios in 5G.
  • 5G 5th generation
  • other future mobile communication technologies such as non-roaming scenarios and roaming scenarios in 5G.
  • service-oriented system architecture and reference point-based architecture in 5G etc.
  • Figure 1 is a schematic diagram of a system architecture applicable to this application.
  • Figure 1 shows a schematic diagram of a non-roaming 5G system architecture (based on reference points).
  • the system architecture applicable to the embodiments of the present application is first described in detail with reference to FIG. 1 .
  • the system architecture may specifically include the following network elements:
  • User equipment can also be called terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication Device, user agent, or user device.
  • the terminal device may be a device that provides voice/data to users, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc.
  • some examples of terminals are: mobile phones, tablets, laptops, PDAs, mobile internet devices (MID), virtual reality (VR) devices, augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grid, Wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocol (SIP) phones , wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, terminal in 5G network Equipment or terminal equipment in a future evolved public land mobile communication network (public land mobile network, PLMN), etc., the embodiments of the present application are not limited to this.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones.
  • the terminal device may also be a terminal device in the IoT system.
  • IoT is a future information system. It is an important part of the development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-computer interconnection and object interconnection.
  • terminal equipment and access network equipment can communicate with each other using certain air interface technology (such as NR or LTE technology, etc.).
  • Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE technology, etc.).
  • the device used to implement the functions of the terminal device may be a terminal device, or may be a device capable of supporting the terminal device to implement the function, such as a chip system or a chip, and the device may be installed in the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • Radio access network (R)AN: It is used to provide network access functions for authorized users in a specific area, and can use transmission tunnels of different qualities according to the user's level, business needs, etc.
  • (R)AN)AN network elements can manage wireless resources, provide access services to terminal devices, and then complete the forwarding of control signals and user data between terminal devices and the core network.
  • (R)AN can also be understood as a traditional network base station in .
  • Access and mobility management function mainly used for mobility management and access management.
  • AMF can be used to implement other functions besides session management among the functions of the mobility management entity (MME), such as legal interception, or access authorization (or authentication) and other functions.
  • MME mobility management entity
  • access authorization or authentication
  • RAN equipment may adopt different radio access technologies.
  • 3GPP access technologies for example, wireless access technologies used in third generation (3G), fourth generation (4G) or 5G systems
  • non-3GPP non- 3GPP (non-3GPP) access technology.
  • 3GPP access technology refers to access technology that complies with 3GPP standard specifications.
  • the access network equipment in the 5G system is called next generation Node Base station (gNB) or RAN equipment.
  • Non-3GPP access technologies can include air interface technology represented by access point (AP) in wireless fidelity (WiFi), global interoperability for microwave access (WiMAX), code Code division multiple access (CDMA), etc.
  • AP access point
  • WiFi wireless fidelity
  • WiMAX global interoperability for microwave access
  • CDMA code Code division multiple access
  • AN equipment can allow interconnection and interworking between terminal equipment and the 3GPP core network using non-3GPP technologies.
  • RAN equipment can be responsible for functions such as wireless resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • AN equipment provides access services to terminal equipment, thereby completing the forwarding of control signals and user data between the terminal equipment and the core network.
  • RAN equipment may include, for example, but is not limited to: macro base station, micro base station (also known as small station), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), AP in WiFi system, wireless relay Node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., can also be a gNB or transmission point (TRP or TP) in the 5G (such as NR) system , one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also be a network node that constitutes a gNB or transmission point, such as a distributed unit (DU), or next-generation communications Base stations in 6G systems, etc.
  • RNC radio network controller
  • Session Management Function Mainly used for session management and terminal Allocation and management of the Internet Protocol (IP) address of the device, selection of endpoints that can manage user plane functions, policy control, or charging function interfaces, and downlink data notifications, etc.
  • IP Internet Protocol
  • UPF User plane function
  • I-UPF intermediate-UPF
  • anchor UPF anchor-UPF
  • A-UPF anchor-UPF
  • I-UPF is connected to the access network RAN
  • A-UPF is the UPF of the session anchor.
  • A-UPF can also be called PDU session anchor (PSA).
  • PSA PDU session anchor
  • Data network used to provide a network for transmitting data, such as the Internet network, etc.
  • the PSA accesses the remote DN, and the L-PSA can access the local DN.
  • AUSF Authentication server function
  • PCF Policy control function
  • Unified data management used to process user identification, access authentication, registration, or mobility management, etc.
  • Application function Mainly supports interaction with the 3rd generation partnership project (3GPP) core network to provide services, such as affecting data routing decisions, policy control functions, or providing services to the network side. Provide some services from third parties. It can be understood as a third-party server, for example, an application server in the Internet, which provides relevant business information, including providing the service quality requirement information corresponding to the business to the PCF, and sending the user plane data information of the business to the PSA-UPF.
  • AF can be a service provider (content provider, CP).
  • NSSF Network slice selection function
  • Network slice admission control function (NSACF) network element can support monitoring and controlling the number of registered users of each network slice, support monitoring and controlling the number of PDU sessions established by each network slice, and support based on Network slice status notification of events and reporting to other NFs.
  • NSACF Network slice admission control function
  • NSSAAF Network Slicing and SNPN Authentication and Authorization Function supports the following features: Can support the use of AAA Server (AAA-S) for specific authentication and authorization of designated network slices. If the AAA-S belongs to a third party, NSSAAF can contact the AAA-S through the AAA proxy (AAA-P). Supports accessing SNPN using credentials of AAA server (AAA-S). If the credential holder belongs to a third party, NSSAAF can contact the AAA server through the AAA proxy (AAA-P).
  • the system architecture may also include: network data analytics function (NWDAF).
  • NWDAF has at least one of the following functions: data collection function and data analysis function.
  • the data collection function refers to collecting relevant data from network elements, third-party business servers, terminal equipment or network management systems
  • the data analysis function refers to analyzing and training based on relevant input data to obtain a model, and making inferences based on the model. Determine the data analysis results, and then provide the data analysis results to network elements, third-party service servers, terminal equipment or network management systems.
  • the analysis results can assist the network in selecting service quality parameters for the business, or assist the network in performing traffic routing, or assist the network choose a background traffic delivery policy and more.
  • the NWDAF may be a separate network element or may be co-located with other core network elements.
  • the NWDAF network element can be co-located with the access and mobility management function (AMF) network element or with the session management function (SMF) network element.
  • AMF access and mobility management function
  • SMF session management function
  • the N1 interface is the reference point between the terminal device and the AMF;
  • the N2 interface is the reference point between (R)AN and AMF, and is used for sending non-access stratum (NAS) messages, etc. ;
  • the N3 interface is the reference point between (R)AN and I-UPF, used to transmit user plane data, etc.;
  • the N4 interface is the reference point between SMF and I-UPF, used to transmit tunnel identifiers such as N3 connections information, data cache indication information, and downlink data notification messages;
  • the N5 interface is the reference point between PCF and AF;
  • the N6 interface is the reference point between UPF and DN, used to transmit user plane data, etc.;
  • the N7 interface It is the reference point between SMF and PCF;
  • the N8 interface is the reference point between AMF and UDM;
  • the N9 interface is the reference point between UPF;
  • the N10 interface is the reference point between SMF and UDM;
  • the N11 interface is the reference point between A
  • interface names between the various network elements in Figure 1 are just an example.
  • the names of the interfaces may be other names, which are not specifically limited in this embodiment of the present application.
  • this application does not rule out that with the evolution of technology, various core network elements can be co-located.
  • each network element such as SMF, AF, UPF, etc.
  • each of the above network elements may also have other names, which are not specifically limited in the embodiments of this application.
  • some or all of the above-mentioned network elements may use the terminology used in 5G, or may adopt other names, etc., which will be described uniformly here and will not be described in detail below.
  • the names of the above-mentioned messages (or signaling) transmitted between various network elements are only examples and do not constitute any limitation on the function of the messages themselves.
  • Protocol data unit (PDU) session can refer to the communication process between a terminal device and the data network DN. After the PDU session is established, a data transmission channel between the UE and the DN is established.
  • the PDU session is similar to the 2/3G packet data protocol (PDP) context (contex) and the 4G bearer context.
  • PDP packet data protocol
  • the PDU session information includes number, international mobile subscriber identity (IMSI), international mobile equipment identity (International Mobile Equipment Identity, IMEI), PDU session identifier (identifier, ID), session type (IPv4, IPv6, IPv4v6, Ethenet, Unstructured), uplink and downlink rates, billing ID, roaming status information, UE Internet protocol (internet protocol, IP) information, PCF information, quality of service (Qos) information, tunnel information, Destination address, SMF identification, slice information (if supported), default data radio bearer (DRB) information, data network name, AMF information, user location information, session management information, UPF ID, online charging identification, Offline billing identification and other related information.
  • IMSI international mobile subscriber identity
  • IMEI International Mobile Equipment Identity
  • PDU session identifier identifier, ID
  • session type IPv4, IPv6, IPv4v6, Ethenet, Unstructured
  • uplink and downlink rates billing ID
  • roaming status information UE Internet protocol (internet protocol, IP) information
  • the PDU session saves important information related to user plane data routing, Qos, charging, network slicing, rate, etc. that may be related to charging.
  • Network slicing uses slicing technology to virtualize multiple end-to-end networks based on a common hardware. Each network has different network functions and adapts to different types of service requirements. For example, after an operator purchases physical resources, it uses the physical resources to virtualize an enhanced mobile broadband (eMBB) slice network for mass Internet services, and then uses the physical resources to meet the smart meter reading needs of certain manufacturers in vertical industries. The physical resources then virtualize a massive machine type communication (mMTC) slicing network and an ultra-reliable and low-latency communication (uRRLC) slicing network. The three slicing networks are respectively Provide services in different business scenarios.
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • uRRLC ultra-reliable and low-latency communication
  • S-NSSAI Single network slice selection assistance information
  • S-NSSAI can be used to identify a network slice. According to the operator’s operation or deployment needs, one S-NSSAI can be associated with one or more A network slicing instance (instance), and a network slicing instance can be associated with one or more S-NSSAI.
  • NSSAI Network slice selection assistance information
  • the NSSAI used in 5G networks include Requested NSSAI, Allowed NSSAI, Configured NSSAI, etc.
  • Requested NSSAI can be understood as the NSSAI that the terminal device expects to use.
  • the terminal device provides it to the network side during the registration process.
  • Allowed NSSAI can be understood as the S-NSSAI value provided by the serving PLMN to the terminal device during registration and other processes, indicating the S-NSSAI value that the terminal device can use in the current registration area of the serving PLMN.
  • it can include up to 8 S-NSSAI.
  • ConfiguredNSSAI can be understood as NSSAI applicable to one or more PLMNs.
  • the AMF sends it to the terminal device in a registration acceptance or configuration update command message. For example, it can include up to 16 S-NSSAI and is saved locally by the terminal device.
  • the NSACF network element can monitor the number of terminal devices connected to each network slice. Moreover, operators currently do not have the ability to immediately allow the terminal device to access the network slice based on the actual usage request of each terminal device (for example, a certain terminal device currently needs to establish a PDU session to transmit data). At this time, the following scenario may occur: a large number of terminal devices may request access to the network slice, but these terminal devices may not necessarily establish a PDU session.
  • the NSACF may refuse the terminal device to access the network slice due to the limit on the number of terminal devices connected to the network slice, thus causing the PDU session to fail. Resources cannot be allocated and used reasonably, which reduces the user's business experience.
  • this application proposes a communication method and device. If the access and mobility management function network element determines that the protocol data unit PDU session status of the terminal device does not meet the first condition of network slicing after a first time (wherein, the If one condition is a condition related to the PDU session status of the terminal device), it is determined that the terminal device is denied access to the network slice, so that the PDU session resources in the network slice can be reasonably configured and used.
  • Figure 2 is a schematic block diagram of a communication method 200 proposed in this application. Each step shown in Figure 2 will be described below. It should be noted that the steps indicated by dotted lines in Figure 2 are optional and will not be described again in the following text.
  • the method includes:
  • Step 201 The access and mobility management function network element determines the first time.
  • the "first time” can be understood as a time period, for example; and for another example, the "first time” can be a time unit.
  • a “time unit” may be one or more radio frames, one or more subframes, one or more A time slot, one or more mini-slots, one or more symbols, etc.
  • the symbols may be orthogonal frequency division multiplexing (OFDM) symbols, discrete fourier transform spread spectrum orthogonal frequency division multiplexing (DFT-S- OFDM) symbols, etc.
  • the first time can also be 1 second (second, "s” for short) or multiple seconds, 1 millisecond (millisecond, "ms” for short) or multiple milliseconds, etc.
  • step 202 is also included, in which the access and mobility management function network element obtains information indicating the first time.
  • the access and mobility management function network element can obtain information indicating the first time from the NSACF.
  • the NSACF may send indication information #1 to the access and mobility management function network element, and the indication information #1 may be used to indicate the first time.
  • the access and mobility management function network element may obtain information indicating the first time from the UDM.
  • NSACF may send indication information #2 to the access and mobility management function network element, and indication information #2 may be used to indicate the first time.
  • a field indicating the first time is preconfigured on the access and mobility management function network element, and the AMF can obtain the first time from the local configuration.
  • Step 203 After the first timeout, if the session state of the PDU of the terminal device does not meet the first condition of network slicing, the access and mobility management function network element refuses the terminal device to access the network slicing.
  • network slice mentioned in this application can also be understood as S-NSSAI, and the S-NSSAI can uniquely identify the network slice. It can also be understood that “network slicing” in this application can be replaced by “S-NSSAI”, which will not be described again below.
  • the access and mobility management function network element can send a UE configuration update command to the terminal device through the user configuration update (UCU) process.
  • the UE configuration update command can update the network slice requested by the terminal device to "Rejected NSSAI" means that the access and mobility management function network element refuses the terminal device to access the network slice.
  • the first condition of the network slice may include at least one of the following: the terminal device establishes a PDU session for the network slice; or, the terminal device establishes a PDU session for the network slice
  • the PDU session established by the slice has an activated user plane; or the PDU session established by the terminal device for the network slice has data for transmitting the first service.
  • one network slice can allow access to multiple terminal devices, and each accessed terminal device can establish multiple PDU sessions for the network slice.
  • the terminal device establishes a PDU session for the network slice in the first condition can be understood to mean that the terminal device can satisfy the first condition as long as it establishes any PDU session for the network slice.
  • the terminal device for the network slice contains data for transmitting the first service
  • any PDU session established by the terminal device for the network slice contains data for transmitting the first service, that is, The first condition can be satisfied.
  • the user plane is activated in the established PDU session can be understood to mean that there is data transmission in the established PDU session.
  • the "first service” in this application may refer to any one of the multiple data transmission services of the terminal device, or it may Therefore, it refers to a specific service (which can also be understood as a specific application) among multiple data transmission services of the terminal device, and is not limited.
  • the access and mobility management function network element can start a timer at a specific moment, and the timer's timing length is a first time (for example, the first time can be 20 seconds).
  • the time when the access and mobility management function network element starts the timer may be, for example, the time when the access and mobility management function network element receives a message from the terminal device requesting access to the network slice.
  • the access and mobility management function network element can determine whether the terminal device has established a PDU session for the network slice after the timer times out; or whether there is an activated user plane in the PDU session established for the network slice; or Whether the data of the first service is transmitted in the PDU session established by the network slice.
  • the time to start the timer may be when the access and mobility management function network element senses that the terminal device releases one of the PDU sessions established for the network slice (for example, the time when the access and mobility management function network element senses that the terminal The moment when the device releases the last PDU established for this network slice (session release).
  • the access and mobility management function network element can determine whether the terminal device has established a PDU session for the network slice after the timer times out; or whether there is an activated user plane in the PDU session established for the network slice; or Whether the data of the first service is transmitted in the PDU session established by the network slice.
  • the time to start the timer may be the time when the access and mobility management function network element senses that the terminal device completes the establishment of a PDU session (for example, PDU session #1) for the network slice for the first time (in this scenario, the first The conditions may be: the PDU session established by the terminal device for the network slice has an activated user plane; or the PDU session established by the terminal device for the network slice contains data for transmitting the first service).
  • the access and mobility management function network element can determine whether there is an activated user plane in the PDU session established for the network slice after the timer expires; or whether there is an active user plane in the PDU session established for the network slice.
  • a business data may be the time when the access and mobility management function network element senses that the terminal device completes the establishment of a PDU session (for example, PDU session #1) for the network slice for the first time (in this scenario, the first The conditions may be: the PDU session established by the terminal device for the network slice has an activated user plane; or the PDU session established
  • the time to start the timer may be when the access and mobility management function network element senses the deactivated user plane in the PDU session established by the terminal device for the network slice (for example, the access and mobility management function network element may The moment when the last PDU session with an activated user plane established by the terminal device is detected to be deactivated (in this scenario, the first condition may be: there is an activated user plane in the PDU session established by the terminal device for the network slice) ; Or, the PDU session established by the terminal device for the network slice contains data for transmitting the first service).
  • the access and mobility management function network element can determine whether there is an activated user plane in the PDU session established for the network slice after the timer expires; or whether there is an active user plane in the PDU session established for the network slice.
  • a business data may be when the access and mobility management function network element senses the deactivated user plane in the PDU session established by the terminal device for the network slice.
  • the time when starting the timer may be the time when the access and mobility management function network element determines the end time of the first service (for example, the access and mobility management function network element may determine the end time of the first service based on the subscription). the end of a transaction).
  • the first condition may be: the PDU session established by the terminal device for the network slice has an activated user plane; or the PDU session established by the terminal device for the network slice has a transmission third a business data).
  • the access and mobility management function network element can determine whether there is an activated user plane in the PDU session established for the network slice after the timer expires; or whether there is an active user plane in the PDU session established for the network slice.
  • a business data may be the time when the access and mobility management function network element determines the end time of the first service (for example, the access and mobility management function network element may determine the end time of the first service based on the subscription). the end of a transaction).
  • the first condition may be: the PDU session established by the terminal device for the network slice
  • step 203 can also be understood as, before the first timeout, if the session state of the PDU of the terminal device meets the first condition of network slicing, the access and mobility management function network element allows the terminal device to access the network slicing. (That is, the S-NSSAI still belongs to Allowed NSSAI).
  • the first condition may include at least one of the following: the terminal device does not have the The network slice establishes a PDU session; or the terminal device does not have an activated user plane in the PDU session established for the network slice; or the terminal device does not transmit the first service data in the PDU session established for the network slice.
  • step 203 can be understood as: after the first timeout, if the session state of the PDU of the terminal device meets the first condition of network slicing, the access and mobility management function network element refuses the terminal device to access the network slice.
  • the first condition may be that the terminal device has an activated user plane in the PDU session established for the network slice, and the PDU session established by the terminal device for the network slice has data for transmitting the first service.
  • the first condition may be that the terminal device establishes a PDU session for the network slice, and the PDU session established for the network slice contains data for transmitting the first service, and so on.
  • the "first condition" in this application may be, for example, that the access and mobility management function network element obtains it from NSACF, or that the access and mobility management function network element obtains it from UDM, or that the access and mobility management function network element obtains it locally. , not limited.
  • the access and mobility management function network element may subscribe to the session management function network element for the start event of the first service.
  • the access and mobility management function network element may subscribe to the policy control management network element for the start event of the first service.
  • the access and mobility management function network element can also subscribe to the session management function network element for the end event of the first service.
  • start event of the first service can be understood as an event that starts transmitting the data of the first service
  • end event of the first service can be understood as an event that ends transmitting the data of the first service
  • a timer (for example, timer timer) can be configured on the access and mobility management function network element, and the access and mobility management function network element can start the timer. After 30s), if the terminal device still does not establish a PDU session, the access and mobility management function network element may deny the terminal device access to the network slice.
  • step 204 is also included, in which the access and mobility management function network element obtains attribute information of the network slice, and determines the first condition based on the attribute information.
  • the attribute information of the network slice may include at least one of the following: after the first timeout, if the terminal device does not establish a PDU session for the network slice, deny the terminal device access to the network Slice; or, after the first timeout, if there is no activated user plane in the PDU session established by the terminal device for the network slice, the access and mobility management function network element refuses the terminal device to access the network slice; Alternatively, after the first time expires, if the PDU session established by the terminal device for the network slice does not transmit the data of the first service, the access and mobility management function network element refuses the terminal device to access the network slice.
  • the attribute information of the network slice and the PDU session state of the terminal device may also include the identification information of the specific application or the specific service.
  • the data flow template of the service for example, Internet Protocol (IP) five-tuple (i.e., source IP address, source port, destination IP address, destination port and transport layer protocol), etc.).
  • the attribute information of the network slice may include at least one of the following: before the first time times out, if the terminal device establishes a PDU session for the network slice, the terminal device is allowed to access the network. Slice; or, before the first time times out, if there is an activated user plane in the PDU session established by the terminal device for the network slice, the access and mobility management function network element allows the terminal device to access the network slice; Or, in the first moment Before timeout, if the PDU session established by the terminal device for the network slice contains data for transmitting the first service, the access and mobility management function network element allows the terminal device to access the network slice.
  • the attribute information of the network slice can be obtained by the access and mobility management function network element from NSACF, or can be obtained by the access and mobility management function network element from UDM, or can be obtained by the access and mobility management function network element.
  • Meta local configuration is not limited.
  • step 204 there may be no sequence between step 204, step 201, and step 202.
  • step 201 and step 203 can be executed simultaneously. That is, while determining the first time, the terminal device can also obtain attribute information of the network slice, which is not limited.
  • step 205 is also included.
  • the access and mobility management function network element receives indication information from the terminal equipment that the terminal equipment is going to establish a PDU session, and determines the first time based on the indication information.
  • the first time determined by the access and mobility management function network element in step 201 is time #A. If the access and mobility management function network element receives the terminal device from the terminal device, the terminal device will be established. PDU session indication information, the access and mobility management function network element has extended time #A. This application records the extended time as time #B. Time #B is greater than time #A, and finally uses time #B as the third time. For a while.
  • the access and mobility management function network element is pre-configured with multiple timers. Once the access and mobility management function network element receives indication information from the terminal device that the terminal device is about to establish a PDU session , then the access and mobility management function network element will select the timer with a larger timing time from multiple timers as the first timer.
  • the access and mobility management function network element can directly perform step 201. Modify the determined first time (“modify” can also be understood as “update” or “reset”) so that the modified first time is greater than the first time determined in step 201.
  • the network device when setting up the first time, takes into account that the terminal device will subsequently establish a PDU session. For the terminal The first time the equipment can be relatively comfortable.
  • the first time determined by the access and mobility management function network element in step 201 is time #A. If the access and mobility management function network element receives the terminal device from the terminal device, it will Instruction information for establishing a PDU session. Even if the PDU session status of the terminal device does not meet the first condition, the access and mobility management function network element will not deny the terminal device access to the network slice (that is, the S-NSSAI still belongs to Allowed NSSAI). Further, if the S-NSSAI becomes Allowed NSSAI, the terminal device can establish a PDU session before the first time is exceeded.
  • the terminal device subsequently establishes a PDU session and sends the corresponding instruction information, the above monitoring of the slice can be abolished, even if the PDU session status of the terminal device does not meet the first requirement.
  • Conditions, access and mobility management function network elements will not deny the terminal device access to the network slice.
  • this application introduces a "new PDU session state" (that is, the state in which the terminal device is about to establish a PDU session), so that the access and mobility management function network element can be based on the state in which the terminal device is about to establish a PDU session. status to ensure that the terminal device will not be denied access to the network slice.
  • This not only improves the configuration and usage efficiency of PDU sessions in network slicing, but also improves the efficiency of terminal devices accessing network slicing.
  • step 206 is also included, in which the access and mobility management function network element refuses the terminal device to access the network. Before chipping, the access and mobility management function network element sends the first time to the terminal device.
  • the access and mobility management function network element can also send the first time to the terminal device, so that the terminal device can sense that if the PDU session has not been established after the first time, or there is no PDU session in the established PDU session If the activated user plane or the established PDU transmits the data of the first service, it will be denied access to the network slice.
  • the terminal device can receive the first time from the access and mobility management function network element. After the first time times out, if the session status of the PDU of the terminal device does not meet the first condition, the terminal device will exit from the mobility management function.
  • the functional network element receives information rejecting access to the network slice.
  • the first condition includes at least one of the following: the terminal device establishes a PDU session for the network slice; or the terminal device has an activated user plane in the PDU session established for the network slice; or the terminal device establishes a PDU session for the network slice.
  • the PDU session established by the network slice contains data for transmitting the first service.
  • the terminal device may receive the first time from the access and mobility management function network element. After the first time times out, if the session status of the PDU of the terminal device meets the first condition, the terminal device will receive the first time from the mobility management function network element. The element receives information denying access to the network slice.
  • the first condition includes at least one of the following: the terminal device has not established a PDU session for the network slice; or, the terminal device does not have an activated user plane in the PDU session established for the network slice; or, the terminal device is The data of the first service is not transmitted in the PDU session established by the network slice.
  • step 207 is also included.
  • the access and mobility management function network element After the access and mobility management function network element refuses the terminal device to access the network slice, the access and mobility management function network element sends the access and mobility management information to the terminal device.
  • the terminal device can receive the cause value.
  • the "reason value" may include at least one of the following: the terminal device does not establish a PDU session for the network slice; or, the terminal device does not have an active user in the PDU session established for the network slice. surface; or, the data of the first service is not transmitted in the PDU session established by the terminal device for the network slice.
  • the "reason value" may include at least one of the following: the terminal device needs to establish a PDU session for the network slice; or, the terminal device needs to have activation in the PDU session established for the network slice. user plane; or, the PDU session established by the terminal device for the network slice needs to transmit data of the first service.
  • the "reason value" may include at least one of the following: the terminal device does not establish a PDU session for the network slice after the first time expires; or the terminal device fails to establish a PDU session for the network slice after the first time expires; There is no activated user plane in the PDU session established by the network slice; or, the terminal device does not transmit data of the first service in the PDU session established for the network slice after the first time has elapsed.
  • the terminal device can sense that the PDU session needs to be established before the first time, or that there is an activated user plane in the PDU session established for the network slice before the first time; or, after the first time, the PDU session needs to be established; Only if the PDU session established for the network slice before the first time transmits data of the first service will not be denied access to the network slice. Specifically, it is assumed that terminal device #1 is accessed and the mobility management function network element refuses to access network slice #1, and terminal device #1 receives the reason value. Then the terminal device #1 can still request access to network slice #1 from the access and mobility management function network element.
  • terminal device #1 will establish a PDU session for the network slice before the first time, or the user plane will be activated in the PDU session established for the network slice before the first time; or, after more than the first time, the user plane will be activated;
  • the data of the first service will be transmitted in the PDU session established for the network slice some time ago.
  • the terminal device determines that the PDU session will not be established before the first time is exceeded, the terminal device does not request the S-NSSAI (that is, the Requested NSSAI does not contain the S-NSSAI); or, if the terminal device determines that the PDU session will be established before the first time is exceeded, it will request the S-NSSAI (that is, the Requested NSSAI can include the S-NSSAI). -NSSAI). For example, the terminal device can determine whether a PDU session will be established for the network slice later based on the saved historical information.
  • the terminal device determines that the user plane will not be activated in the established PDU session before the first time is exceeded, the S-NSSAI will not be requested (that is, the Requested NSSAI does not contain the S-NSSAI); or, if the terminal device If it is judged that there will be an activated user plane in the established PDU session before the first time is exceeded, then the S-NSSAI is requested (that is, the Requested NSSAI can include the S-NSSAI). For example, the terminal device can determine whether there will be an activated user plane in the subsequent PDU session established for the network slice based on the saved historical information. For example, terminal device #1 may determine based on configuration information or historical information that a video conference needs to be conducted at eight o'clock in the evening. At this time, you can request access to the network slice.
  • the terminal device determines that no data of the first service will be transmitted in the established PDU session before the first time is exceeded, it does not request the S-NSSAI (that is, the Requested NSSAI does not include the S-NSSAI); or, if The terminal device determines that the PDU session established before the first time will contain data for transmitting the first service, and then requests the S-NSSAI (that is, the Requested NSSAI may include the S-NSSAI). For example, the terminal device may determine, based on the saved historical information, whether there will be data for transmitting the first service in the subsequent PDU session established for the network slice. For example, terminal device #2 can determine based on configuration information or historical information that a certain application (application, APP) will be used at six o'clock in the morning. At this time, you can request access to the network slice.
  • application application
  • the access and mobility management function network element can determine the PDU session status of the terminal device after the first time and the first condition, that is, if the access and mobility management function network element determines the PDU session status of the terminal device after the first time. If the first condition of network slicing is not met, it is determined that the terminal device is denied access to the network slicing. This ensures that no terminal device will access the network slice for a long time without establishing/activating a PDU session, which improves the usage efficiency of PDU session resources in the network slice and improves the user's business experience.
  • Figure 3 is a specific embodiment of the communication method 300 proposed by this application. This method shows the technical solution of this application from the perspective of interaction between various network elements.
  • the terminal device is UE#1 as an example, and network slicing is used as Network slicing #1 is taken as an example for illustration.
  • the method 300 includes:
  • Step 301 UE#1 requests to register with network slice #1 and obtains S-NSSAI#1.
  • registration in step 301 can also be understood as “access”.
  • S-NSSAI#1 can be used to identify network slice #1.
  • step 301 For the specific implementation of step 301, please refer to Technical Specification (TS) 23.501, Chapter 5.15.
  • TS Technical Specification
  • the UE when it registers with the public land mobile network PLMN through an access type, it can send a registration request message to the RAN.
  • RAN can select the terminal device's initial (Initial) AMF according to the Requested NSSAI.
  • Initial AMF can determine whether it can provide services to the UE based on the received Requested NSSAI, Subscribed S-NSSAI and local configuration. If the AMF can serve the UE, the Initial AMF is still the serving AMF of the UE, and then the AMF constructs the Allowed NSSAI based on the Subscribed S-NSSAI and the Requested NSSAI, and sends it to the UE through the registration acceptance message.
  • the UE can access network slice #1.
  • Step 302 AMF reports the information on the number of UEs accessing network slice #1 this time to NSACF. corresponding NSACF receives this information.
  • Step 303 NSACF sends the attribute information of network slice #1 and information indicating the first time to the AMF.
  • AMF receives the attribute information of network slice #1 and the information indicating the first time.
  • the NSACF can send the attribute information of network slice #1 and the information indicating the first time to the AMF.
  • attribute information of network slice #1 and the information indicating the first time sent by the NSACF to the AMF may be in the same message, or may be sent separately in different messages, which is not limited by this application.
  • attribute information and “first time” in step 303 may refer to the description of "attribute information" in step 204 in method 200.
  • Step 304 After the first time expires, if the session state of the PDU of UE#1 does not meet the first condition of network slice #1, the AMF sends a message to UE#1 denying access to network slice #1 for UE#1. Correspondingly, UE#1 receives the information.
  • the AMF may determine the first condition based on the attribute information of network slice #1, and determine the first time based on the information indicating the first time.
  • step 304 For understanding of the “first condition” in step 304, refer to the description of the “first condition” in step 203 of method 200.
  • the AMF can sense the status of the PDU session of UE#1.
  • the AMF can also obtain the PDU session status of the UE corresponding to each subscription permanent identifier (SUPI) from the NWDAF.
  • the specific implementation method of NWDAF providing PDU session status can be found in step 601 of method 600.
  • the AMF may also obtain the PDU session status of UE#1 from the SMF.
  • the AMF may obtain the PDU session status of UE#1 from the NEF. etc. The description will not be repeated in the following embodiments.
  • the AMF determines that the first condition is that UE#1 needs to have an activated user plane in the PDU session established for network slice #1. At this time, AMF can subscribe to SMF whether there is data in the PDU session. Alternatively, the AMF can be aware of deactivated PDU sessions.
  • the AMF determines that the first condition is that UE#1 needs to transmit the data of service #1 in the PDU session established for network slice #1. At this time, AMF can subscribe to the SMF or PCF for the start time and end event of service #1.
  • the AMF may determine the first time through information indicating the first time.
  • the information indicating the first time is field #1 in downlink control information (DCI)
  • the AMF can determine the value of time #A (an example of the first time) by parsing field #1 in the DCI.
  • time #A is 30ms.
  • step 301 UE #1 carries a follow on indication (instruction information that the terminal device is about to establish a PDU session) when requesting to register in network slice #1, then AMF can Instructions for information to be re-established for the first time.
  • AMF may request an extension of time #A.
  • AMF can request an extension of time #A from NSACF or UDM.
  • the extended time is time #B (an example of the first time) which is 100ms; or, the AMF can select a timer with a timing longer than time #A among multiple preconfigured timers as a method to determine whether to reject the UE# 1 The basis for accessing network slice #1;
  • AMF can directly reset the first time to time #C, which time #C Greater than time #A.
  • time #C is 200ms; or, even if the PDU session status of UE#1 does not meet the first condition, the AMF will not deny the terminal device access to the network slice #1.
  • the access and mobility management function network element does not impose any restrictions on the PDU session state when the terminal device requests access to the network slice.
  • the access and mobility management function network element allows the terminal device to access the network slice (ie, S-NSSAI #1 in step 301 It is still Allowed NSSAI), but compared with the existing process, all terminal devices connected to the network slice can effectively utilize the PDU session resources in the network, improving the user's business experience.
  • AMF refuses UE#1 to access network slice #1. Specifically, AMF sends a message to UE#1 denying UE#1 access to network slice #1. Correspondingly, UE#1 receives the information.
  • this information may also include a reason value for denying access to UE#1.
  • the information may also include the first time.
  • the AMF may send a UE configuration update command to UE#1, and the UE configuration update command indicates that UE#1 is denied access to network slice #1.
  • the AMF can also deny UE#1 access to network slice #1 based on the existing reason value, which has no impact on UE#1, but UE#1 does not know the reason for being denied access to network slice #1.
  • cause value please refer to the description of the "cause value” in step 207 of the method 200.
  • the AMF can determine to deny the UE access to the network slice based on the first time and the first condition. That is, if the AMF determines that the UE does not meet the first condition of the network slice after the first time, the AMF determines to deny the UE access to the network slice. This ensures that no UE will access the network slice for a long time without establishing/activating a PDU session, which improves the usage efficiency of PDU session resources in the network slice and improves the user's business experience.
  • the method may also include:
  • Step 305 UE#1 determines the reason for being refused access to network slice #1 by the AMF, and can establish a PDU session before the first timeout, and re-request access to network slice #1.
  • Figure 4 is a schematic block diagram of a communication method 400 provided by this application. The method includes:
  • Step 401 The access and mobility management function network element determines the attribute information of the network slice.
  • the attribute information of the network slice in this embodiment can be understood as the attribute information of the network slice described in step 204 of the method 200.
  • the attribute information of the network slice in this embodiment can also be understood to include at least one of the following: If the terminal device does not establish a PDU session for the network slice, the access and mobility management functions The network element refuses the terminal device to access the network slice; or, if the terminal device does not have an activated user plane in the PDU session established for the network slice, the access and mobility management function network element refuses the terminal device to access the described network slice. network slice; or, if the PDU session established by the terminal device for the network slice does not transmit the data of the first service, the access and mobility management function network element refuses the terminal device to access the network slice.
  • the attribute information of the network slice in this embodiment can also be understood to include at least one of the following: if the terminal device establishes a PDU session for the network slice, the access and mobility management function network element allows the terminal device to access the network slice. Network slice; or, if the terminal device has an activated user plane in the PDU session established for the network slice, the access and mobility management function network element allows the terminal device to access the network slice; or, if the terminal device If the PDU session established for the network slice contains data for transmitting the first service, then the access and mobility management function network element allows the terminal device to access the network slice.
  • the attribute information of the network slice is compared with the "attribute information of the network slice" mentioned in step 204.
  • the access and mobility management function network element is based on the PDU session status of the terminal device and the network slice.
  • the attribute information does not need to consider the "first time” factor when determining whether to deny the terminal device access to the network slice. For example, after the access and mobility management function network element determines the attribute information of the network slice, if it senses that the terminal device has not established a PDU session, it will immediately deny the terminal device access to the network slice.
  • Step 402 The access and mobility management function network element determines the number N of terminal devices that access the network slice this time based on the attribute information of the network slice and the PDU session status of the terminal device, where N is greater than or equal to 0 and less than Or equal to 1.
  • the access and mobility management function network element may determine the number N of terminal devices that access the network slice this time when receiving a message from the terminal device requesting access to the network slice. For another example, the access and mobility management function network element can determine the number N of terminal devices that access the network slice this time when it senses that the terminal device releases one of the PDU sessions established for the network slice. For another example, the access and mobility management function network element can determine the number N of terminal devices that access the network slice this time when it senses that the terminal device completes the establishment of a PDU session (for example, PDU session #1) for the network slice for the first time. .
  • a PDU session for example, PDU session #1
  • the access and mobility management function network element may determine the number N of terminal devices accessing the network slice this time when it senses that the user plane is deactivated in the PDU session established by the terminal device for the network slice. For example, the access and mobility management function network element may determine the number N of terminal devices accessing the network slice this time when determining the end time of the first service.
  • the access and mobility management function network element can update the number N of terminal devices accessing the network slice this time.
  • the terminal device can determine the value of N in the following ways:
  • the attribute information of the network slice is: after the first timeout, if the terminal device does not establish a PDU session for the network slice, the access and mobility management function network element refuses access to the terminal device. The network slice. At this time, if the access and mobility management function network element senses that the terminal device has not established a PDU session, it can be determined that N is 0. If the access and mobility management function network element senses that the terminal device has established a PDU session, it can be determined that N is 1. Specifically: If the access and mobility management function network element senses that the terminal device has established a PDU session, but there is no activated user plane in the PDU session, it can be determined that N is 1.
  • the access and mobility management function network element senses that the terminal device has established a PDU session, and there is an activated user plane in the PDU session, it can be determined that N is 1. If the access and mobility management function network element senses that the terminal device has established a PDU session but does not transmit the data of the first service, it can be determined that N is 1. If the access and mobility management function network element senses that the terminal device has established a PDU session and transmits data of the first service, it can be determined that N is 1.
  • N 1
  • the attribute information of the network slice is: if there is no activated user plane in the PDU session established by the terminal device for the network slice, the access and mobility management function network element refuses the terminal device to access the described Network slicing. At this time, if the access and mobility management function network element senses that the terminal device has not established a PDU session, it can be determined that N is 0. If the access and mobility management function network element senses that the terminal device has established a PDU session, but there is no active user plane in the PDU session, it can be determined that N is 0.5. If the access and mobility management function network element senses that the terminal device has established a PDU session, and there is an activated user plane in the PDU session, it can be determined that N is 1.
  • the access and mobility management function network element senses that the terminal device has established a PDU session and transmits data of the first service, it can be determined that N is 1.
  • the attribute information of the network slice is: if the PDU session established by the terminal device for the network slice does not transmit the data of the first service, the access and mobility management function network element refuses access to the terminal device. The network slice. At this time, if the access and mobility management function network element senses that the terminal device has not established a PDU session, it can be determined that N is 0. If the access and mobility management function network element senses that the terminal device has established a PDU session, but there is no active user plane in the PDU session, it can be determined that N is 0.5. If the access and mobility management function network element senses that the terminal device has established a PDU session and has an activated user plane, but no data of the first service is transmitted, it can be determined that N is 0.7. If the access and mobility management function network element senses that the terminal device has established a PDU session and is transmitting data of the first service, it can be determined that N is 1.
  • the value of N is a decimal between 0 and 1
  • the resources of the PDU session that the terminal device needs to occupy are the resources multiplied by the multiple of the decimal between 0 and 1.
  • the above implementation manner can also be understood as: if the access and mobility management function network element determines that the PDU session state of the terminal device does not comply with the attributes of the network slice, the AMF determines that N is greater than 0 and less than 1. Based on the method provided by this application, it is proposed that the value of N can be a decimal between 0 and 1.
  • the terminal device does not need to occupy the quota or occupies a relatively smaller quota, thereby allowing more Terminal devices that meet the attributes of a network slice are connected to the network slice, which improves the usage efficiency of PDU session resources.
  • the access and mobility management function network element can update the value of N in real time according to the status of the PDU session of the terminal device.
  • the attribute information of the network slice is: after the first timeout, if the terminal device does not establish a PDU session for the network slice, the access and mobility management function network element refuses the terminal device to access the network slice.
  • the access and mobility management function network element at time #1 senses that the terminal device has not established a PDU session, it can be determined that N is 0. That is, the access and mobility management function network element can report the value of N once to the network slice admission control function network element. If the access and mobility management function network element senses that the terminal device has established a PDU session at time #2 after time #1, it can be determined that N is 1. That is, the access and mobility management function network element can update the value of N to the network slice admission control function network element again.
  • the method also includes step 403.
  • the access and mobility management function network element receives indication information from the terminal device that the terminal device is going to establish a PDU session, and determines that N is greater than 0.
  • the access and mobility management function network element receives indication information from the terminal device that the terminal device is about to establish a PDU session. If the attribute information of the network slice is: after the first timeout, if the terminal device does not establish a PDU for the network slice. session, the access and mobility management function network element refuses the terminal device to access the network slice. At this time, even if the access and mobility management function network element senses that the terminal device has not established a PDU session, it will determine N as 1, or determine N as 0.5, or determine N as 0.8, and so on.
  • the access and mobility management function network element receives indication information from the terminal device that the terminal device is about to establish a PDU session. If the attribute information of the network slice is: If there is no active user in the PDU session established by the terminal device for the network slice, interface, the access and mobility management function network element denies the terminal device access to the network slice. At this time, even if the access and mobility management function network element senses that the terminal device has not established a PDU session, or the PDU session established by the terminal device does not have an activated user plane, or the PDU session established by the terminal does not transmit the data of the first service, It will also determine N to be 1, or N to be 0.5, or N to be 0.8, and so on.
  • the access and mobility management function network element receives indication information from the terminal device that the terminal device is about to establish a PDU session. If the attribute information of the network slice is: If the terminal device does not transmit the first PDU session in the PDU session established for the network slice, If the service data is not available, the access and mobility management function network element will deny the terminal device access to the network slice. At this time, even if the access and mobility management function network element senses that the terminal device has not established a PDU session, or the PDU session established by the terminal device does not have an activated user plane, or the PDU session established by the terminal does not transmit the data of the first service, It will also determine N to be 1, or N to be 0.5, or N to be 0.8, and so on.
  • Step 404 The access and mobility management function network element sends the number N to the network slice admission control function network element.
  • the network slice admission control function network element receives the number N.
  • the access and mobility management function network element can set the number of terminal devices that report this access network slice according to the PDU session status of the terminal device and the attribute information of the network slice. It can effectively avoid occupying the quota of the terminal device accessing the network slice when the terminal device requests access to the network slice without establishing/activating the PDU session. That is, it improves the configuration and use efficiency of PDU session resources in the network slice and improves the user experience. business experience.
  • this embodiment proposes that the value of N can be a number greater than 0 and less than 1, indicating that the terminal device may not occupy the quota or occupy less configuration, thereby allowing more terminal devices that meet the network slice attributes to access the network slice. , improving the usage efficiency of PDU session resources.
  • step 405 is also included, in which the network slice admission control function network element controls the terminal device according to the number N.
  • the network slice admission control function network element monitors (or the network slice admission control function network element can also determine based on other operator policies) the number of terminal devices accessing the network slice reaches the limit allowed by the network slice. If the upper limit of the number of accessed terminal devices is reached, the network slice admission control function network element can provide access and mobility management function network element #2 (it should be noted that the access and mobility management function network element #2 here can The same as the access and mobility management function network element (recorded as "access and mobility management function network element #1") in step 402, or it can be different) sends information to notify the access and mobility management function network element that the access and mobility management function network element has reached The maximum number of terminal devices registered in this network slice.
  • the access and mobility management function network element #1 can provide services for terminal equipment #1 to terminal equipment #20
  • the access and mobility management function network element #2 can provide services for terminal equipment #30 to terminal equipment #60
  • Service, mobility management function network element #3 can provide services for terminal equipment #21 to terminal equipment #29.
  • 60 terminal devices are currently connected to this network slice, namely terminal device #1 to terminal device #60.
  • the network element with the network slice admission control function determines that the upper limit of the number of terminal devices allowed to access the network slice has been reached.
  • the network slice admission control function network element can instruct the access and mobility management function network element #2 to deny access to terminal device #49 (for example, terminal device #49 has not established a PDU session) The network slice.
  • the network slice admission control function network element can also notify the access and mobility management function network element #1 that the maximum number of registered terminal devices in the network slice has been reached, and at the same time, it can also notify the access and mobility management function network element #1
  • the access and mobility management function network element #1 instructs the terminal device #10 (for example, the terminal device #10 has established a PDU session but has not yet activated the user plane) to access the network slice.
  • step 406 is also included, in which the network slice admission control function network element sends information triggering the access and mobility management function network element to deny the terminal device access to the network slice to the access and mobility management function network element.
  • the access and mobility management function network element receives this information.
  • step 407 is also included, in which the access and mobility management function network element sends information to the terminal device denying the terminal device access to the network slice.
  • the terminal device receives the information.
  • this information may also include a reason value for denying access to the terminal device.
  • step 407 For understanding of the "cause value” in step 407, please refer to the description of the "cause value” in step 207 in the method 200.
  • step 408 is also included, in which the terminal device determines the reason why it is denied access to the network slice by the AMF, establishes a PDU session, and re-requests access to the network slice.
  • access and mobility management function network element in steps 406 to 408 can be understood as the "access and mobility management function network element #1" mentioned in step 405, and can also be understood as “access and mobility management function network element #1".
  • Mobility management function network element #2 is not limited.
  • Figure 5 is a specific embodiment of the communication method 500 proposed by this application. This method shows the technical solution of this application from the perspective of interaction between various network elements.
  • the terminal device is UE#2 as an example, and network slicing is used as Network slicing #2 is taken as an example for illustration.
  • the method 500 includes:
  • Step 501 UE#2 requests to register with network slice #2 and obtains S-NSSAI#2.
  • step 501 please refer to the description of step 301 in method 300.
  • step 502 is also included, in which the AMF reports information on the number of UEs accessing network slice #2 this time to the NSACF.
  • the corresponding NSACF receives this information.
  • the AMF may report the number M of UEs accessing network slice #2 this time to the NSACF for the first time. For example, the AMF may first directly report M as 1. Or, if the AMF does not report to the NSACF, it means that the number of UEs accessing network slice #2 this time is 0.
  • UE#2 carries a follow on indication (instruction information that the terminal device is about to establish a PDU session) when requesting to register in network slice #2, even if the PDU session status of UE#2 does not meet the requirements of network slice #3 attribute, AMF can also determine that M is greater than 0 based on the indication information.
  • Step 503 NSACF sends the attribute information of network slice #2 to AMF.
  • AMF receives the attribute information of network slice #2.
  • attribute information in step 503, please refer to the description of “attribute information” in step 401 in method 400.
  • step 502 there may be no restriction on the sequence between step 502 and step 503.
  • Step 504 AMF determines the number N of UEs accessing network slice #2 this time based on the attribute information of network slice #2 and the PDU session status of UE #2.
  • step 504 can be understood as that the AMF can update the number of UEs accessing network slice #2 this time based on the attribute information of network slice #2 and the PDU session status of UE #2 again. Furthermore, if the value of N determined by the AMF in step 504 is different from the value of M initially determined by the AMF in step 502, the subsequent AMF will send the number of UEs accessing network slice #2 to the NSACF again.
  • AMF can sense whether UE#2 has established a PDU session, or AMF can subscribe to SMF whether data is transmitted in the PDU session, or AMF can subscribe to SMF or PCF for the start event of service #2 and end events.
  • step 504 the implementation method in which the AMF determines the number N of UEs accessing network slice #2 this time can refer to the description of step 402 in method 400.
  • Step 505 AMF sends the number N of UEs accessing network slice #2 this time to NSACF.
  • the corresponding NSACF receives the number N of UEs accessing network slice #2 this time.
  • the AMF may update the number of UEs accessing network slice #2 this time.
  • Step 506 NSACF controls the terminal device according to the number N.
  • step 506 may refer to the description of step 405 in method 400.
  • the method may also include: the AMF may deny UE#2 access to network slice #2, and send a reason value for denying access to network slice #2 to UE#2.
  • the AMF may deny UE#2 access to network slice #2, and send a reason value for denying access to network slice #2 to UE#2.
  • the AMF can set the number of UEs reporting this access to network slice #2 based on the PDU session status and the attribute information of network slice #2. It can effectively avoid occupying the quota of the UE accessing network slice #2 when the UE requests access to network slice #2 without establishing/activating a PDU session. That is, it improves the configuration and use efficiency of PDU session resources in network slice #2. , improving the user’s business experience.
  • network slice access control function network elements can be understood as network slice access control function network elements that manage terminal devices.
  • Figure 6 is a schematic block diagram of a communication method 600 provided by this application. The method includes:
  • Step 601 The network element that manages the network slice admission control function of the terminal device obtains the PDU session status of the terminal device.
  • the network slice admission control function network element that manages the terminal device can obtain the PDU session status of the terminal device from the access and mobility management function network element.
  • the network slice admission control function network element that manages the terminal device obtains the PDU session status of the terminal device from the session management function network element through the access and mobility management function network element.
  • the access and mobility management function network element can subscribe to the SMF for the status of the PDU session corresponding to each network slice (optionally, it can also obtain the status of the PDU session corresponding to a terminal device on the network slice.
  • the network slice The status of the PDU session of UE#7 corresponding to SUPI#7 on #4).
  • the subscription process please refer to the description related to step 703a in method 700.
  • the network slice admission control function network element that manages the terminal device can obtain the PDU session status of the terminal device from the network opening function network element.
  • the network slice admission control function network element that manages the terminal device can obtain the network slice admission control function network element that manages the PDU session. (denoted as the second network slice admission control function network element), and obtain the status of the PDU session through the second network slice admission control function network element.
  • the network element with the network slice admission control function that manages PDU sessions can subscribe to the SMF for the status of the PDU session corresponding to each S-NSSAI (optionally, it can also obtain the status of the PDU session corresponding to a terminal device on the network slice). .For example, the status of the PDU session of UE#10 corresponding to SUPI#10 on network slice #5).
  • the management terminal device network slice access control function network element can also obtain the PDU session status of the end device from the network data analysis function network element.
  • the management terminal device network slice access control function network element can obtain at least one of the following information from the network data analysis function network element: slice load level information, service experience (Observed Service Experience) information, distribution Analysis (Dispersion Analytics) information, at least one of the following, etc.
  • slice load level information For details, please refer to the corresponding chapter of TS 23.288.
  • the network data analysis function network element can obtain the status of the PDU session corresponding to each network slice (can Optionally, you can also obtain the status of the PDU session corresponding to a terminal device on the network slice. For example, the status of the PDU session of UE#10 corresponding to SUPI#10 on network slice #5).
  • the network slice admission control function network element that manages the terminal device can directly obtain the PDU session status of the terminal device corresponding to each SUPI from the network data analysis function network element.
  • the network data analysis function network element can send information to the network slice admission control function network element that manages the PDU session (or to the session management network element; or to the operation, administration and maintenance (operation, administration and maintenance, OAM))
  • the network slice identification for example, S-NSSAI
  • terminal device SUPI terminal device SUPI
  • service identification Application ID
  • service data flow template service data flow template
  • the network element with the network slice admission control function can be configured with attribute information of the network slice.
  • attribute information please refer to the description of the attribute information in step 401 of method 400.
  • Step 602 The network slice access control function network element that manages the terminal device determines whether to trigger the access and mobility management function network element to deny access to the terminal device based on the PDU session status of the terminal device and/or the attribute information of the network slice. This network slice.
  • the network slice admission control function network element of the management terminal device determines to trigger the access and mobility management function network element to reject The terminal device accesses the network slice.
  • the network slice admission control function network element can notify the access and mobility management control function network element that "the maximum number of terminal devices registered in the network slice has been reached."
  • the network slice admission control function network element that manages the terminal device determines not to trigger access and the mobility management function network element refuses the terminal device to access the network slice. .
  • the network slice admission control function network element that manages the terminal device can update the threshold of the number of terminal devices allowed to register on the network slice according to the PDU session status of the access terminal device. For example, when there are too many terminal devices that have not established a PDU session or have not activated the user plane, the network slice admission control function network element can increase the threshold of the number of terminal devices allowed to register on the network slice (for example, increase the number of terminal devices allowed to register on the network slice).
  • the number of terminal devices allowed to register is 30% of the number of terminal devices that have not established a PDU session or the number of terminal devices that have not activated the user plane, etc.).
  • the network element that manages the network slice admission control function of the terminal device may not change the threshold, but the number of terminal devices allowed to access exceeds the threshold of the number of terminal devices originally configured on the network slice that is allowed to register. . (For example, it may exceed at most 30% of the number of terminal devices without establishing a PDU session or the number of terminal devices without activating the user plane, etc.). Further, if the number of actually registered terminal devices has exceeded the updated threshold, at this time the network slice admission control function network element can notify the access and mobility management control function network element that "the maximum number of registered terminal devices in the network slice has been reached.” quantity". At this time, it can also be understood that the network slice access control function network element that manages the terminal device can determine whether to trigger the access and mobility management function network element to deny the terminal device access to the network based only on the PDU session status of the terminal device. slice.
  • the network slice admission control function network element that manages the terminal device can reset the maximum number of terminal devices allowed to be registered on the network slice.
  • the network slice access control function network element that manages the terminal device can check the PDU session status (for example, it can be reported by the access and mobility management control function network element), and can based on the reported PDU of each terminal device. Session state, increase the number of terminal devices allowed to register on the network slice to 30% of the number of terminal devices that have not established a PDU session or that have not activated the user plane.
  • the network element with the network slice admission control function that manages terminal devices can maintain a counter to record the number of actual registered users exceeding the maximum number of terminal devices allowed to be registered in the network slice. If the network element that manages the network slice admission control function of the terminal device finds based on this counter (or based on the operator's policy) that the number of actual registered terminal devices exceeds the maximum number of terminal devices allowed to be registered in the network slice, it has reached the point where no PDU is established.
  • the threshold of the number of terminal devices in the session or the number of terminal devices without activated user plane for example, 30%.
  • the network element with the network slice access control function that manages the terminal device can determine whether to provide access to the access and mobility management control function network. Meta notification "The maximum number of registered end devices for the network slice has been reached".
  • the network slice admission control function network element that manages the terminal device can receive indication information from the access and mobility management function network element that the terminal device is going to establish a PDU session. At this time, when the session status of the PDU of the terminal device does not meet the attributes of the network slice, the network slice admission control function network element of the management terminal device determines not to trigger the access and mobility management function network based on the indication information. The terminal device is denied access to the network slice.
  • the method also includes the steps of: the access and mobility management function network element refuses the terminal device to access the network slice, and sends a reason value for rejecting access to the terminal device.
  • the access and mobility management function network element refuses the terminal device to access the network slice, and sends a reason value for rejecting access to the terminal device.
  • the network element with the network slice access control function can deny the terminal device access to the network slice based on the obtained PDU session status and determines that the PDU session status of the terminal device does not meet the attributes of the network slice. . This ensures that no terminal device will register for a long time without establishing/activating a PDU session, improves the usage efficiency of PDU session resources in network slicing, and improves the service experience of user equipment.
  • Figure 7 is a specific embodiment of the communication method 700 proposed by this application. This method shows the technical solution of this application from the perspective of interaction between various network elements.
  • the terminal device is UE#3 as an example, and network slicing is used as Network slicing #3 is taken as an example for illustration.
  • the method 700 includes:
  • Step 701 UE#3 requests to register with network slice #3 and obtains S-NSSAI#3.
  • step 701 For understanding of step 701, please refer to the description of step 301 in method 300.
  • Step 702 The AMF reports information on the number of UEs accessing network slice #3 this time to the NSACF that manages the terminal device (ie, the first NSACF). Correspondingly, the NSACF receives the information.
  • the AMF can report the PDU session status of the terminal device after the NSACF subscribes to the PDU session status of the terminal device.
  • Step 703a The NSACF that manages the terminal device sends subscription request information to the AMF for subscribing to the PDU session status information of UE#3. Correspondingly, AMF receives this information.
  • NSACF can send subscription request information to AMF to subscribe to PDU session status. For example. NSACF can subscribe to AMF to see whether a PDU session is established; or, NSACF can subscribe to SMF to see whether there is an activated user plane; or, NSACF can subscribe to SMF or PCF for the start event and end event of service #3.
  • the NSACF that manages the terminal device sends subscription request information to the AMF.
  • the information may include the identification of UE#3; if the information is Subscribing to UE#3, whether there is an activated user plane in the established PDU session.
  • the information can include The identifier of the PDU session of UE#3; if this information is to subscribe to whether UE#3 transmits data of the first service in the established PDU session, the information may include the identifier of the first service of UE#3.
  • AMF#1 can send the context information of the PDU session status of the terminal device to AMF#2, thereby avoiding the duplication of AMF#2 when the PDU session status of the terminal device has not changed. Report PDU session status to NSACF.
  • it can be predefined that as long as the AMF providing services for the terminal device changes, the PDU session status of the terminal device needs to be reported to the NSACF again.
  • the NSACF can subscribe to the AMF for the PDU session status of all UEs served by the S-NSSAI (if previously If you don’t have a subscription).
  • the above technical solution can also be understood as the NSACF that manages the terminal device sends subscription request information to the AMF for subscribing to the PDU status of all terminal devices served by the AMF. At this time, the information only needs to contain the identification information of the AMF. In this scenario, AMF reports the PDU session status of all terminal devices it serves each time, which can reduce signaling interactions between core network elements.
  • Step 703b The NSACF that manages the terminal device sends subscription request information to the AMF for subscribing to the address information of the NSACF that manages the PDU session (ie, the second NSACF). Correspondingly, AMF receives this information.
  • the "subscription" process in step 703b can be understood as the NSACF that may manage the PDU session before subscribing may not yet exist, so it can be subscribed first. For example, after step 703b, UE#3 may establish a PDU session.
  • Step 703c The AMF sends information about the address of the NSACF that subscribes to the management PDU session to the SMF. Correspondingly, SMF receives the information.
  • Step 703d The SMF sends the address information of the NSACF that manages the PDU session to the AMF. Correspondingly, AMF receives this information.
  • Step 703e The AMF sends the address information of the NSACF that manages the PDU session to the NSACF that manages the terminal device.
  • the NSACF that manages the terminal device receives the information.
  • Step 703f The NSAC that manages the terminal device sends information about subscribing to the PDU session status of UE#3 to the NSACF that manages the PDU session based on the address information. Correspondingly, the NSACF that manages the PDU session receives this information.
  • Step 703g The NSACF that manages the PDU session sends the status information of the PDU session of UE#3 to the NSACF that manages the terminal device.
  • the NSACF that manages the terminal device receives the information.
  • Step 704 The NSACF that manages the terminal device determines whether to trigger the AMF to deny UE#3 access to the network slice #3 based on the PDU session status of the UE#3 and/or the attribute information of the network slice.
  • the NSACF determines to trigger the AMF to deny UE#3 access to the network slice #3.
  • the method also includes: the AMF refuses the UE#3 to access the network slice #3, and the UE#3 sends a reason value for denying access.
  • the AMF refuses the UE#3 to access the network slice #3, and the UE#3 sends a reason value for denying access.
  • UE#3 carries a follow on indication (instruction information that the terminal device is about to establish a PDU session) when requesting to register in network slice #3, even if UE#3 is currently of If the PDU session does not comply with the attributes of network slice #3, AMF can determine based on the indication information and not trigger AMF to deny UE #3 access to network slice #3.
  • the NSACF can deny UE#3 access to network slice #3 based on the obtained PDU session status and determines that the PDU session status of UE#3 does not meet the attributes of network slice #3. This ensures that no terminal device will register for a long time without establishing/activating a PDU session, improves the usage efficiency of PDU session resources in network slicing, and improves the service experience of user equipment.
  • step 502 and step 503 may not be limited. That is, step 502 or step 503 may be performed first.
  • pre-definition in this application can be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, solidification, or pre-firing.
  • each node such as access and mobility management function network elements, terminal equipment, and network slice admission control function network elements, in order to realize the above functions, includes corresponding hardware structures and/or software modules that perform each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.
  • the embodiments of the present application can divide the access and mobility management function network elements and each involved core network element into functional modules according to the above method examples.
  • each functional module can be divided corresponding to each function, or two or two More than one function is integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiment of this application It is schematic and is only a logical function division. There may be other division methods in actual implementation. The following is an example of dividing each functional module according to each function.
  • FIG. 8 is a schematic block diagram of the communication device 100 provided by the embodiment of the present application. As shown in the figure, the device 100 may include: a transceiver unit 110 and a processing unit 120.
  • the device 100 may be the access and mobility management function network element in the above method embodiment, or may be a network element used to implement the access and mobility management function network element in the above method embodiment. Functional chip. It should be understood that the device 100 may correspond to the access and mobility management function network element in the methods 200 to 700 according to the embodiment of the present application, and the device 100 may perform the access in the methods 200 to 700 of the embodiment of the present application. and the steps corresponding to the mobility management function network element.
  • the processing unit is used to determine the first time; after the first time times out, if the session status of the protocol data unit PDU of the terminal device does not meet the first condition of the network slicing, the processing unit is used to reject all The terminal device described above accesses the network slice.
  • the processing unit is configured to obtain information indicating the first time.
  • the processing unit is configured to obtain attribute information of a network slice, and the processing unit is configured to determine the first condition based on the attribute information.
  • the transceiver unit before the processing unit refuses the terminal device to access the network slice, the transceiver unit is configured to send the first time to the terminal device.
  • the transceiver unit is configured to send a reason value for the access and mobility management function network element to the terminal device for refusing the terminal device to access the network slice.
  • the transceiver unit is configured to receive indication information from the terminal device that the terminal device is about to establish a PDU session; and the processing unit is configured to determine the first time according to the indication information.
  • the processing unit is configured to instruct the transceiver unit to subscribe to the start event of the first service to a session management function network element or a policy control management network element.
  • the processing unit is also used to determine the attribute information of the network slice; the processing unit is used to determine the current connection based on the attribute information of the network slice and the protocol data unit PDU session status of the terminal device.
  • the processing unit is configured to determine the number N of terminal devices accessing the network slice according to the attribute information of the network slice and the PDU session status of the terminal device, including: if the processing unit determines that the terminal The PDU session state of the device does not comply with the attributes of the network slice, and the processing unit determines that N is less than 1.
  • the transceiver unit is configured to receive indication information from the terminal device that the terminal device is about to establish a PDU session; the processing unit is configured to perform the processing according to the attribute information of the network slice and the PDU session status of the terminal device. Determining the number N of terminal devices accessing the network slice includes: the processing unit is configured to determine that N is greater than 0 based on attribute information of the network slice, PDU session status and indication information of the terminal device.
  • the device 100 may be the network slice admission control functional network element in the above method embodiment, or may be used to implement the network slice admission control functional network element in the above method embodiment.
  • Functional chip It should be understood that the device 100 may correspond to the network slice admission control function network element in the methods 200 to 700 according to the embodiment of the present application, and the device 100 may perform the network slicing in the methods 200 to 700 of the embodiment of the present application. Steps corresponding to the admission control function network element.
  • the processing unit is configured to obtain the protocol data unit PDU session status of the terminal device, wherein the attribute information configured with network slices is installed; the processing unit is configured to obtain the PDU session status according to the terminal device.
  • the PDU session status of the device and the attribute information of the network slice determine whether the access and mobility management function network element is triggered to deny the terminal device access to the network slice.
  • the processing unit is configured to obtain the PDU session status of the terminal device, including: the processing unit is configured to obtain the PDU session status of the terminal device from the access and mobility management function network element; or, The processing unit obtains the PDU session status of the terminal device from the session management function network element through the access and mobility management function network element; or, the processing unit is configured to obtain the PDU session status of the terminal device from the network opening function network element .
  • the processing unit is a first processing unit, and the processing unit is used to obtain the PDU session status of the terminal device, including: the first processing unit is used to obtain the address of the second processing unit Information, wherein the first processing unit is used to manage the number of the terminal devices, the second processing unit is used to manage the number of PDU sessions; the first processing unit is used to manage the number of PDU sessions according to the second processing
  • the address information of the unit instructs the transceiver unit to request the second processing unit network element to obtain the PDU session status of the terminal device; the transceiver unit is used to receive the PDU session status of the terminal device from the second processing unit.
  • the first processing unit is configured to obtain the address information of the second processing unit, including: the transceiver unit is configured to request or subscribe to the second processing unit from the access and mobility management function network element.
  • the address information of the processing unit; the transceiver unit is used to receive the address information of the second processing unit from the access and mobility management function network element.
  • the processing unit is configured to determine whether to trigger the access and mobility management function network element to deny the terminal device access to the network slice based on the PDU session status of the terminal device and the attribute information of the network slice, including: When the PDU session status of the terminal device does not meet the attributes of the network slice, the processing unit is used to determine to trigger the mobility management function network element to deny the terminal device access to the network slice.
  • the transceiver unit is configured to receive indication information from the access and mobility management function network element that the terminal device is about to establish the PDU session; the processing unit is configured to perform the PDU session according to the terminal device. status and attribute information of the network slice to determine whether to trigger the access and mobility management function network element to refuse the terminal device to access the network slice, including: in the case where the session status of the PDU of the terminal device does not meet the attributes of the network slice, the processing The unit is configured to determine, according to the indication information, not to trigger the mobility management function network element to deny the terminal device access to the network slice.
  • the device 100 may be the terminal device in the above method embodiment, or may be a chip used to implement the functions of the terminal device in the above method embodiment. It should be understood that the device 100 may correspond to the terminal device in the methods 200 to 700 according to the embodiment of the present application, and the device 100 may perform steps corresponding to the terminal device in the methods 200 to 700 of the embodiment of the present application.
  • the transceiver unit is configured to send information that the device requests access to network slicing to the access and mobility management function network element; the transceiver unit is configured to receive information from the access and mobility management function.
  • the first time of the management function network element after the first time expires, if the session state of the protocol data unit PDU of the device does not meet the first condition, the transceiver unit is used to obtain the message from the mobile management function network
  • the element receives information denying access to the network slice.
  • the transceiver unit is configured to send indication information that the device will establish a PDU session to the access and mobility management function network element, and the indication information is used for the access and mobility management function network element to determine the third For a while.
  • the transceiver unit is configured to send the device to the access and mobility management function network element.
  • Set the information of the network slice requesting access the transceiver unit is used to send indication information that the device will establish a PDU session for the network slice to the access and mobility management function network element; wherein the indication information is used for access and the mobility management function network element determines the number N of terminal devices accessing the network slice, where N is greater than 0; or, the indication information is used by the network slice admission control function network element to determine not to trigger the mobility management function network element to reject all The device accesses the network slice.
  • the device 100 here is embodied in the form of a functional unit.
  • the term "unit” as used herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor, or a group of processors) used to execute one or more software or firmware programs. processor, etc.) and memory, merged logic circuitry, and/or other suitable components to support the described functionality.
  • ASIC application specific integrated circuit
  • processor such as a shared processor, a proprietary processor, or a group of processors
  • memory merged logic circuitry, and/or other suitable components to support the described functionality.
  • the apparatus 100 can be specifically the first terminal device in the above embodiments, and can be used to execute various processes corresponding to the first terminal device in the above method embodiments and/or or steps, or the apparatus 100 can be specifically a second terminal device in the above embodiments, and can be used to perform various processes and/or steps corresponding to the second terminal device in the above method embodiments. To avoid duplication, here No longer.
  • the device 100 of each of the above solutions has the function of realizing the corresponding steps performed by the wireless access network equipment in the above method, or the device 100 of each of the above solutions has the function of realizing the access and mobility management functions of the network element, terminal equipment, network in the above method.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiving unit. (machine replacement), other units, such as processing units, etc., can be replaced by processors to respectively perform the sending and receiving operations and related processing operations in each method embodiment.
  • transceiver unit 110 may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.
  • the device in Figure 8 may be the network element or device in the aforementioned embodiment, or it may be a chip or a chip system, such as a system on chip (SoC).
  • the transceiver unit may be an input-output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip. No limitation is made here.
  • Figure 9 is a schematic block diagram of a communication device 200 provided by an embodiment of the present application.
  • the device 200 includes: at least one processor 220.
  • the processor 220 is coupled to the memory and is used to execute instructions stored in the memory to send signals and/or receive signals.
  • the device 200 also includes a memory 230 for storing instructions.
  • the device 200 also includes a transceiver 210, and the processor 220 controls the transceiver 210 to send signals and/or receive signals.
  • processor 220 and the memory 230 can be combined into one processing device, and the processor 220 is used to execute the program code stored in the memory 230 to implement the above functions.
  • the memory 230 may also be integrated in the processor 220 or independent of the processor 220 .
  • the transceiver 210 may include a transceiver (or receiver) and a transmitter (or transmitter).
  • the transceiver may further include an antenna, and the number of antennas may be one or more.
  • the transceiver 210 may be a communication interface or an interface circuit.
  • the transceiver 210 in the device 200 may correspond to the transceiver unit 110 in the device 100
  • the processor 220 in the device 200 may correspond to the processing unit 120 in the device 200 .
  • the device 200 is used to implement the steps performed by the radio access network equipment in each of the above method embodiments. OK operation.
  • the processor 220 is configured to execute computer programs or instructions stored in the memory 230 to implement related operations of the access and mobility management function network elements in each of the above method embodiments.
  • the device 200 is used to implement the operations performed by the terminal device in each of the above method embodiments.
  • the processor 220 is used to execute computer programs or instructions stored in the memory 230 to implement related operations of the terminal device in each of the above method embodiments. For example, the method executed by the terminal device in any one of the embodiments shown in FIG. 2 to FIG. 7 .
  • the device 200 is used to implement the operations performed by the network slice admission control function network element in each of the above method embodiments.
  • the processor 220 is used to execute computer programs or instructions stored in the memory 230 to implement related operations of the network slice admission control function network element in each of the above method embodiments.
  • each step of the above method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware processor for execution, or can be executed by a combination of hardware and software modules in the processor.
  • the software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capabilities.
  • each step of the above method embodiment can be completed through an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or Other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories.
  • the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM), It is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM direct memory bus random access memory
  • direct ram-bus RAM direct ram-bus RAM
  • the present application also provides a computer program product.
  • the computer program product stores computer program code.
  • the computer program code is run on a computer, the computer is caused to execute methods 200 to 700.
  • the computer when the computer program code is executed by a computer, the computer can implement the methods executed by the terminal device in the above-mentioned method 200 to method 700 embodiments.
  • the computer when the computer program code is executed by a computer, the computer can implement the methods executed by the network slice admission control function network element in the above-mentioned method 200 to method 700 embodiments.
  • the present application also provides a computer-readable medium.
  • the computer-readable medium stores program code.
  • the program code When the program code is run on a computer, it causes the computer to execute the steps in the above embodiment. Methods for executing access and mobility management function network elements, terminal equipment, and network slice access control function network elements.
  • the present application also provides a communication system, including an access and mobility management functional network element and a terminal device.
  • the access and mobility management functional network element is used to perform methods 200 to 700.
  • the method executed by the access and mobility management function network element in any one of the embodiments, the terminal device is used to execute the method executed by the terminal device in any one of the embodiments in methods 200 to 700.
  • the communication system may also include a network slice admission control function network element, which is used to perform network slicing in any one of the embodiments in methods 200 to 700. The method performed by the admission control function network element.
  • the present application also provides a communication system, including a network slice admission control function network element and a terminal device.
  • the network slice admission control function network element is used to perform methods 200 to 700.
  • the method executed by the network slice admission control function network element in any one of the embodiments, and the terminal device is used to execute the method executed by the terminal device in any one of the embodiments of methods 200 to 700. .
  • the communication system may also include an access and mobility management function network element.
  • the access and mobility management function network element is used to perform access in any one of the embodiments in methods 200 to 700. Methods performed by network elements with access and mobility management functions.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in a computer-readable storage medium in, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center through wires (such as coaxial cables, optical fiber, digital subscriber Transmit to another website, computer, server or data center via digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated.
  • the usable media may be magnetic media (e.g., floppy disks, hard disks, tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks). SSD)) etc.
  • magnetic media e.g., floppy disks, hard disks, tapes
  • optical media e.g., high-density digital video discs (DVD)
  • DVD digital video discs
  • semiconductor media e.g., solid state disks). SSD
  • transceiver performs the steps of receiving or sending in the method embodiment. Other steps except sending and receiving may be performed by the processing unit (processing unit). device) execution.
  • processing unit processing unit
  • device execution.
  • processors There can be one or more processors.
  • a component may be, but is not limited to, a process, a processor, an object, an executable file, a thread of execution, a program and/or a computer running on a processor.
  • applications running on the computing device and the computing device may be components.
  • One or more components can reside in a process and/or thread of execution and a component can be localized on one computer and/or distributed between 2 or more computers. Additionally, these components can execute from various computer-readable media having various data structures stored thereon.
  • a component may, for example, be based on a signal having one or more data packets (eg, data from two components interacting with another component, a local system, a distributed system, and/or a network, such as the Internet, which interacts with other systems via signals) Communicate through local and/or remote processes.
  • data packets eg, data from two components interacting with another component, a local system, a distributed system, and/or a network, such as the Internet, which interacts with other systems via signals
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, or Each unit physically exists alone, or two or more units can be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

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

Abstract

一种通信方法和装置，该方法包括：如果接入和移动管理功能网元确定超过第一时间后终端设备的协议数据单元PDU会话状态不满足网络切片的第一条件(其中，本申请中的第一条件是与终端设备的PDU会话状态相关的条件)，则确定拒绝该终端设备接入网络切片，从而可以合理的配置和使用网络切片中的PDU会话资源。

Description

通信方法和装置
本申请要求于2022年5月6日提交中国专利局、申请号为202210488467.X、申请名称为“通信方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且更具体的，涉及一种通信方法和装置。
背景技术
核心网(例如，网络切片)对终端设备的接入数量是有限制的，例如，网络切片准入控制功能(network slice admission control function，NSACF)网元可以监控每个网络切片上所接入的终端设备的数量。目前，可能会出现如下场景：大量的终端设备可能会请求接入网络切片，但是并不一定会建立对应的协议数据单元(protocol data unit，PDU)会话，当其它还没有接入到网络切片的终端设备确实需要建立PDU会话时，NSACF却有可能因为网络切片上终端设备接入数量的限制，拒绝该终端设备接入到该网络切片，从而使得PDU会话资源不能合理配置和使用，降低用户的业务体验。
因此，针对上述场景终端设备如何更为有效的配置和使用网络中的PDU会话资源，成为需要解决的技术问题。
发明内容
本申请实施例提供一种通信方法和装置，如果接入和移动管理功能网元确定超过第一时间后终端设备的协议数据单元PDU会话状态不满足网络切片的第一条件(其中，本申请中的第一条件是与终端设备的PDU会话状态相关的条件)，则确定拒绝该终端设备接入网络切片，从而可以合理的配置和使用网络切片中的PDU会话资源。
第一方面，提供了一种通信方法，该方法可以由接入和移动管理功能网元执行，或者，也可以由接入和移动管理功能网元的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法包括：接入和移动管理功能网元确定第一时间；在第一时间超时后，若终端设备的协议数据单元PDU的会话状态不满足网络切片的第一条件，则接入和移动管理功能网元拒绝终端设备接入网络切片，其中，第一条件包括以下至少一项：终端设备为网络切片建立PDU会话；或者，终端设备为网络切片建立的PDU会话中有激活的用户面；或者，终端设备为网络切片建立的PDU会话中有传输第一业务的数据。
上述技术方案也可以理解为，接入和移动管理功能网元启动定时器，所述定时器的时长为第一时间；在所述定时器超时后，所述接入和移动管理功能网元判定第一条件是否满足，其中，所述第一条件包括以下至少一项：所述终端设备为第一网络切片建立PDU会话，或者所述终端设备为所述第一网络切片建立的PDU会话中存在激活的用户面，或者； 所述终端设备为所述第一网络切片建立的PDU会话中有传输第一业务的数据；如果接入和移动管理功能网元判定结果不满足第一条件，则所述接入和移动管理功能网元拒绝所述终端设备接入所述第一网络切片。
其中，接入和移动管理功能网元启动定时器的时刻，例如可以是接入和移动管理功能网元接收到终端设备请求接入网络切片的消息的时刻。此时，接入和移动管理功能网元在该定时器超时后可以判断终端设备是否为该网络切片建立PDU会话；或者，为该网络切片建立的PDU会话中是否有激活的用户面；或者为该网络切片建立的PDU会话中是否有传输第一业务的数据。
又例如，启动定时器的时刻可以是接入和移动管理功能网元感知到终端设备释放为该网络切片建立的其中一条PDU会话(例如，PDU会话#12)的时刻。此时，接入和移动管理功能网元在该定时器超时后可以判断终端设备是否为该网络切片建立PDU会话；或者，为该网络切片建立的PDU会话中是否有激活的用户面；或者为该网络切片建立的PDU会话中是否有传输第一业务的数据。
再例如，启动定时器的时刻可以是接入和移动管理功能网元感知到终端设备首次为该网络切片完成一条PDU会话(例如，PDU会话#1)建立的时刻(该场景下，第一条件可能为：所述终端设备为所述网络切片建立的PDU会话中有激活的用户面；或者，所述终端设备为所述网络切片建立的PDU会话中有传输第一业务的数据)。此时，接入和移动管理功能网元在该定时器超时后可以判断为该网络切片建立的PDU会话中是否有激活的用户面；或者，为该网络切片建立的PDU会话中是否有传输第一业务的数据。
例如，启动定时器的时刻可以是接入和移动管理功能网元感知到终端设备为该网络切片建立的PDU会话中去激活的用户面的时刻(该场景下，第一条件可能为：所述终端设备为所述网络切片建立的PDU会话中有激活的用户面；或者，所述终端设备为所述网络切片建立的PDU会话中有传输第一业务的数据)。此时，接入和移动管理功能网元在该定时器超时后可以判断为该网络切片建立的PDU会话中是否有激活的用户面；或者，为该网络切片建立的PDU会话中是否有传输第一业务的数据。
又例如，启动定时器的时刻可以是接入和移动管理功能网元确定第一业务的结束时刻(例如，接入和移动管理功能网元可以基于订阅的第一业务的结束时间，确定第一业务的结束时刻)。(该场景下，第一条件可能为：所述终端设备为所述网络切片建立的PDU会话中有激活的用户面；或者，所述终端设备为所述网络切片建立的PDU会话中有传输第一业务的数据)。此时，接入和移动管理功能网元在该定时器超时后可以判断为该网络切片建立的PDU会话中是否有激活的用户面；或者，为该网络切片建立的PDU会话中是否有传输第一业务的数据。
该方法也可以理解为，在第一时间超时前，若终端设备的PDU的会话状态满足网络切片的第一条件，则接入和移动管理功能网元允许该终端设备接入网络切片。
本申请中，第一条件也可以包括以下至少一项：该终端设备没有为该网络切片建立PDU会话；或者，该终端设备为该网络切片建立的PDU会话中没有激活的用户面；或者，该终端设备为该网络切片建立的PDU会话中没有传输第一业务的数据。该方法也可以理解为，在第一时间超时后，若终端设备的PDU的会话状态满足网络切片的第一条件，则接入和移动管理功能网元拒绝该终端设备接入网络切片。
需要说明的是，本申请中的“第一条件”可以是与终端设备为该网络切片是否建立PDU会话以及建立的PDU会话状态相关的条件，不局限于本申请所列举的这些条件。
本申请中，“第一时间”例如可以理解为一个时间段；又例如，“第一时间”可以是时间单元。例如，“时间单元”可以是一个或多个无线帧，一个或多个子帧，一个或多个时隙，一个或多个微时隙，一个或多个符号等。其中，符号可以是正交频分复用(orthogonal frequency division multiplexing，OFDM)符号、离散傅里叶变换扩频的正交频分复用(discrete fourier transform spread spectrum orthogonal frequency division multiplexing，DFT-S-OFDM)符号等。例如，第一时间还可以是1秒(second，简称“s”)或多秒，1毫秒(millisecond，简称“ms”)或多毫秒等。
本申请中，一个网络切片上可以允许接入多个终端设备，并且接入的每个终端设备都可以为该网络切片建立多条PDU会话。本申请中，第一条件中的“所述终端设备为所述网络切片建立PDU会话”可以理解为，终端设备只要为该网络切片建立任一条PDU会话就可以满足第一条件。同样的，“所述终端设备为所述网络切片建立的PDU会话中有激活的用户面”也可以理解为，终端设备为所述网络切片建立的任一条PDU会话中有激活的用户面，即可以满足第一条件。“所述终端设备为所述网络切片建立的PDU会话中有传输第一业务的数据”可以理解为，终端设备为所述网络切片建立的任一条PDU会话中有传输第一业务的数据，即可以满足第一条件。
本申请中，“建立的PDU会话中有激活的用户面激活”可以理解为，建立的PDU会话中有数据传输。
本申请中的“第一业务”可以指终端设备多个数据传输业务中的任意一个业务，也可以是指终端设备多个数据传输业务中的某个特定的业务(也可以理解为是，特定的应用)，不予限定。
本申请中，接入和移动管理功能网元可以向会话管理功能网元或者策略控制管理网元订阅第一业务的开始事件或者结束时间。
基于上述技术方案，本申请中，接入和移动管理功能网元可以根据第一时间和第一条件，即，如果接入和移动管理功能网元确定超过第一时间后终端设备的PDU会话状态不满足网络切片的第一条件，则确定拒绝该终端设备接入网络切片。从而保证不会有终端设备长时间接入该网络切片而不建立/激活PDU会话，提高了网络切片中PDU会话资源的使用效率，提高了用户的业务体验。
在一种可能的实现方式中，该方法还包括：接入和移动管理功能网元获取指示第一时间的信息。
例如，接入和移动管理功能网元可以从NSACF获取指示第一时间的信息；或者接入和移动管理功能网元可以从UDM获取指示第一时间的信息；或者接入和移动管理功能网元上可以预配置指示第一时间的信息，等等不予限定。
基于上述技术方案，本申请中，接入和移动管理功能网元可以通过多种方式获取指示第一时间的信息，使得接入和移动管理功能网元确定第一时间的方式更为灵活。
在一种可能的实现方式中，该方法还包括：接入和移动管理功能网元获取网络切片的属性信息，接入和移动管理功能网元根据属性信息确定第一条件。
在一种可能的实现方式中，属性信息包括以下至少一项：在第一时间超时后，若终端 设备没有为网络切片建立PDU会话，则接入和移动管理功能网元拒绝终端设备接入所述网络切片；或者，在第一时间超时后，若终端设备为网络切片建立的PDU会话中没有激活的用户面，则接入和移动管理功能网元拒绝终端设备接入所述网络切片；或者，在第一时间超时后，若终端设备为网络切片建立的PDU会话中没有传输第一业务的数据，则接入和移动管理功能网元拒绝终端设备接入网络切片。
在一种可能的实现方式中，网络切片的属性信息可以包括以下至少一项：在第一时间超时前，若该终端设备为该网络切片建立PDU会话，则允许终端设备接入所述网络切片；或者，在第一时间超时前，若该终端设备为所述网络切片建立的PDU会话中有激活的用户面，则接入和移动管理功能网元允许终端设备接入所述网络切片；或者，在第一时间超时前，若终端设备为网络切片建立的PDU会话中有传输第一业务的数据，则接入和移动管理功能网元允许该终端设备接入所述网络切片。
基于上述技术方案，本申请中，接入和移动管理功能网元可以根据属性信息确定第一条件，不同的属性信息对应不同的第一条件，使得接入和移动管理功能网元的实现更为灵活。并且，接入和移动管理功能网元可以基于网络切片的不同的属性控制确定是否需要拒绝接入该网络切片上的终端设备，即使得接入和移动管理功能网元对接入网络切片的终端设备的控制更为灵活。
在一种可能的实现方式中，该方法还包括：在接入和移动管理功能网元拒绝终端设备接入网络切片之前，接入和移动管理功能网元向终端设备发送第一时间。
基于上述技术方案，本申请中，使得终端设备可以感知如果超过第一时间还未建立PDU会话，或者建立的PDU会话中没有激活的用户面，或者建立的PDU会中传输第一业务的数据，则会被拒绝接入该网络切片。
在一种可能的实现方式中，该方法还包括：接入和移动管理功能网元向终端设备发送接入和移动管理功能网元拒绝终端设备接入网络切片的原因值，其中，原因值包括以下至少一项：终端设备没有为网络切片建立PDU会话；或者，终端设备为网络切片建立的PDU会话中没有激活的用户面；或者，终端设备为所述网络切片建立的PDU会话中没有传输第一业务的数据。
基于上述技术方案，本申请中，接入和移动管理功能网元可以向终端设备发送拒绝该终端设备接入网络切片的原因值，使得该终端设备可以获知被拒绝接入网络切片的原因，后续可以在第一时间超时前建立PDU会话，并重新请求接入该网络切片。
在一种可能的实现方式中，接入和移动管理功能网元接收来自终端设备的终端设备将要建立PDU会话的指示信息；接入和移动管理功能网元根据指示信息确定第一时间。
例如，该指示信息可以为follow on指示，指示信息用于指示终端设备将要建立PDU会话。此时，接入和移动管理功能网元可以根据该指示信息确定延长第一时间，或者重新设置第一时间的值大于初始确定的第一时间的值，或者在预配置的多个第一时间中确定时间大于初始确定的第一时间的值，等等。
基于上述技术方案，本申请中引入了一种“新的PDU会话状态”(即，终端设备即将建立PDU会话的状态)，使得接入和移动管理功能网元可以根据终端设备即将建立PDU会话的状态，确定不会拒绝该终端设备接入网络切片。不仅提高了网络切片中PDU会话的配置使用效率，也提高了终端设备接入网络切片的效率。
第二方面，提供一种通信方法，该方法可以由终端设备设备(例如，UE)执行，或者，也可以由终端设备的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法包括：终端设备向接入和移动管理功能网元发送请求接入网络切片的信息；终端设备接收来自接入和移动管理功能网元的第一时间；在第一时间超时后，若终端设备的协议数据单元PDU的会话状态不满足第一条件，则终端设备从接入和移动管理功能网元接收拒绝接入网络切片的信息，其中，第一条件包括以下至少一项：终端设备为网络切片建立PDU会话；或者，终端设备为网络切片建立的PDU会话中有激活的用户面；或者，终端设备为网络切片建立的PDU会话中有传输第一业务的数据。
基于上述技术方案，本申请中，终端设备可以向接入和移动管理功能网元发送请求接入网络切片信息，如果该终端设备的PDU会话状态不符合网络设备的属性，则被拒绝接入网络切片，从而保证不会有UE长时间接入该网络切片而不建立/激活PDU会话，提高了网络切片中PDU会话资源的使用效率，提高了用户的业务体验。
在一种可能的实现方式中，该方法还包括：终端设备向接入和移动管理功能网元发送终端设备将要建立PDU会话的指示信息，该指示信息用于接入和移动管理功能网元确定第一时间。
基于上述技术方案，本申请中引入了一种“新的PDU会话状态”(即，终端设备即将建立PDU会话的状态)，使得接入和移动管理功能网元可以根据终端设备即将建立PDU会话的状态，确定不会拒绝该终端设备接入网络切片。不仅提高了网络切片中PDU会话的配置使用效率，也提高了终端设备接入网络切片的效率。
第三方面，提供了一种通信方法，该方法可以由接入和移动管理功能网元执行，或者，也可以由接入和移动管理功能网元的组成部件(例如芯片或者电路)执行，对此不作限定。
在一种可能的实现方式中，接入和移动管理功能网元确定网络切片的属性信息；接入和移动管理功能网元根据网络切片的属性信息和终端设备的协议数据单元PDU会话状态，确定本次接入网络切片的终端设备的数量N，所述N大于或者等于0，并且小于或者等于1；接入和移动管理功能网元向网络切片准入控制功能网元发送所述数量N；其中，网络切片的属性信息包括以下至少一项：若终端设备没有为网络切片建立PDU会话，则接入和移动管理功能网元拒绝终端设备接入网络切片；或者，若终端设备为网络切片建立的PDU会话中没有激活的用户面，则接入和移动管理功能网元拒绝终端设备接入网络切片；或者，若终端设备为网络切片建立的PDU会话中没有传输第一业务的数据，则接入和移动管理功能网元拒绝终端设备接入网络切片。
基于上述技术方案，本申请中，使得接入和移动管理功能网元可以根据PDU会话状态以及网络切片的属性信息，设置上报本次接入网络切片的终端设备的数量。可以有效避免在终端设备请求接入到网络切片而不建立/激活PDU会话时，占用终端设备接入网络切片的配额，即，提高了网络切片中PDU会话资源的配置和使用效率，提高了用户的业务体验。
在一种可能的实现方式中，接入和移动管理功能网元根据网络切片的属性信息和终端设备的PDU会话状态，确定接入网络切片的终端设备的数量N，包括：如果接入和移动管理功能网元确定终端设备的PDU会话状态不符合网络切片的属性，AMF确定N小于1。
基于上述技术方案，本申请中，如果接入和移动管理功能网元确定终端设备的PDU会话状态不符合网络切片的属性，则AMF可以将N设置为小于1的实数，从而可以避免在终端设备请求接入到网络切片而不建立/激活PDU会话时，占用终端设备接入网络切片的配额。
在一种可能的实现方式中，该方法还包括：接入和移动管理功能网元接收来自终端设备的终端设备将要建立所述PDU会话的指示信息；接入和移动管理功能网元根据网络切片的属性信息和终端设备的PDU会话状态，确定接入网络切片的终端设备的数量N，包括：接入和移动管理功能网元根据网络切片的属性信息、终端设备的PDU会话状态以及指示信息，确定所述N大于0。
基于上述技术方案，本申请中，引入了一种“新的PDU会话状态”(即，终端设备即将建立PDU会话的状态)，使得接入和移动管理功能网元可以根据终端设备即将建立PDU会话的状态，确定不会拒绝该终端设备接入网络切片。不仅提高了网络切片中PDU会话的配置使用效率，也提高了终端设备接入网络切片的效率。
第四方面，提供一种通信方法，该方法可以由网络切片准入控制功能网元执行，或者，也可以由网络切片准入控制功能网元的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法包括：网络切片准入控制功能网元获取终端设备的协议数据单元PDU会话状态，其中，网络切片准入控制功能网元上配置有网络切片的属性信息；网络切片准入控制功能网元根据终端设备的PDU会话状态和/或所述网络切片的属性信息，确定是否接入和触发移动管理功能网元拒绝终端设备接入所述网络切片；其中，网络切片的属性信息包括以下至少一项：若终端设备没有为网络切片建立PDU会话，则接入和移动管理功能网元拒绝终端设备接入网络切片；或者，若终端设备为网络切片建立的PDU会话中没有激活的用户面，则接入和移动管理功能网元拒绝终端设备接入网络切片；或者，若终端设备为网络切片建立的PDU会话中没有传输第一业务的数据，则接入和移动管理功能网元拒绝终端设备接入所述网络切片。
基于上述技术方案，本申请中，使得网络切片准入控制功能网元可以根据获取的PDU会话状态，并且确定终端设备的PDU会话状态不满足网络切片的属性时，可以拒绝终端设备接入网络切片。从而保证不会有终端设备长时间注册而不建立/激活PDU会话，提高了网络切片中，PDU会话资源的使用效率，提高了用户设备的业务体验。
在一种可能的实现方式中，网络切片准入控制功能网元获取终端设备的PDU会话状态，包括：网络切片准入控制功能网元从接入和移动管理功能网元获取终端设备的PDU会话状态；或者，网络切片准入控制功能网元通过接入和移动管理功能网元从会话管理功能网元获取终端设备的PDU会话状态；或者，网络切片准入控制功能网元从网络开放功能网元获取终端设备的PDU会话状态。
在一种可能的实现方式中，网络切片准入控制功能网元为第一网络切片准入控制功能网元，网络切片准入控制功能网元获取终端设备的PDU会话状态，包括：第一网络切片准入控制功能网元获取第二网络切片准入控制功能网元的地址信息，其中，第一网络切片准入控制功能网元用于管理终端设备的数量，第二网络切片准入控制功能网元用于管理PDU会话的数量；第一网络切片准入控制功能网元根据第二网络切片准入控制功能网元 的地址信息，向第二网络切片准入控制功能网元请求获取终端设备的PDU会话状态；第一网络切片准入控制功能网元接收来自第二网络切片准入控制功能网元的终端设备的PDU会话状态。
在一种可能的实现方式中，第一网络切片准入控制功能网元获取第二网络切片准入控制功能网元的地址信息，包括：第一网络切片准入控制功能网元向接入和移动管理功能网元请求或订阅第二网络切片准入控制功能网元的地址信息；第一网络切片准入控制功能网元接收来自接入和移动管理功能网元的第二网络切片准入控制功能网元的地址信息。
基于上述技术方案，本申请中，网络切片准入控制功能网元获取可以通过多种方式灵活获取终端设备的PDU会话状态。
在一种可能的实现方式中，网络切片准入控制功能网元根据终端设备的PDU会话状态和网络切片的属性信息，确定是否触发接入和移动管理功能网元拒绝终端设备接入网络切片，包括：在终端设备的PDU会话状态不满足网络切片的属性的情况下，网络切片准入控制功能网元确定触发移动管理功能网元拒绝终端设备接入网络切片。
基于上述技术方案，本申请中，网络切片准入控制功能网元通过确定终端设备的PDU会话状态不满足网络切片的属性，从而可以拒绝该终端设备接入网络切片，PDU会话资源的使用效率和用户设备的业务体验。
在一种可能的实现方式中，还方法还包括：网络切片准入控制功能网元接收来自接入和移动管理功能网元的终端设备将要建立PDU会话的指示信息；网络切片准入控制功能网元根据终端设备的PDU会话状态以及网络切片的属性信息，确定是否触发接入和移动管理功能网元拒绝终端设备接入所述网络切片，包括：在终端设备的PDU的会话状态不满足网络切片的属性的情况下，网络切片准入控制功能网元根据指示信息确定不触发所述移动管理功能网元拒绝终端设备接入所述网络切片。
基于上述技术方案，本申请中，使得接入和移动管理功能网元可以根据终端设备即将建立PDU会话的状态，确定不会拒绝该终端设备接入网络切片。不仅提高了网络切片中PDU会话的配置使用效率，也提高了终端设备接入网络切片的效率。
在一种可能的实现方式中，管理终端设备的网络切片准入控制功能网元可以根据接入终端设备的PDU会话状态更新网络切片上允许注册的终端设备的数量的阈值。例如，没有建立PDU会话的终端设备或没激活用户面的终端设备太多时，网络切片准入控制功能网元可以增加该网络切片上允许注册的终端设备的数量的阈值(例如，增加网络切片上允许注册的终端设备的数量为没有建立PDU会话的终端设备的数量或没有激活用户面的终端设备数量的30％等)。或者，在这种情况下，管理终端设备的网络切片准入控制功能网元可以不改变阈值，但允许接入的终端设备的数量超过网络切片上允许注册的终端设备的数量的阈值。(例如，最多可以超过没有建立PDU会话的终端设备的数量或没有激活用户面的终端设备的数量的30％等)。进一步的，如果实际实际注册的终端设备的数量已经超过更新后的阈值，此时网络切片准入控制功能网元可以通知接入和移动管理控制功能网元“已达到网络切片最大注册的终端设备的数量”。此时，也可以理解为，管理终端设备的网络切片准入控制功能网元可以只根据该终端设备的PDU会话状态，确定是否触发接入和移动管理功能网元拒绝该终端设备接入该网络切片。
具体的，如果接入和移动管理控制功能网元请求增加在S-NSSAI上注册的终端设备 的数量，并且当前已经达到该网络切片允许注册的最大终端设备的数量。此时，管理终端设备的网络切片准入控制功能网元可以重新设置该网络切片上允许注册的最大终端设备的数量。例如，管理终端设备的网络切片准入控制功能网元可以检查PDU会话状态(如可以是接入和移动管理控制功能网元上报的)，并且可以根据上报的各个终端设备的PDU会话状态，将网络切片上允许注册的终端设备的数量增加到没有建立PDU会话的终端设备的数量或没有激活用户面的终端设备数量的30％。又例如，管理终端设备的网络切片准入控制功能网元可以维护一个计数器，用于记录实际注册用户数超过该网络切片允许注册的最大终端设备的数量。如果管理终端设备的网络切片准入控制功能网元根据该计数器(或者基于运营商策略)发现，实际注册的终端设备的数量超过该网络切片允许注册的最大终端设备的数量，已经达到没有建立PDU会话的终端设备的数量或没有激活用户面的终端设备数量的阈值，例如，30％，此时，管理终端设备的网络切片准入控制功能网元可以判断是否向接入和移动管理控制功能网元通知“已达到网络切片最大注册的终端设备的数量”。
第五方面，提供了一种通信方法，该方法可以由终端设备(例如，UE)执行，或者，也可以由终端设备的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法包括：终端设备向接入和移动管理功能网元发送终端设备请求接入的网络切片的信息；终端设备所述向接入和移动管理功能网元发送终端设备将要为网络切片建立PDU会话的指示信息；其中，指示信息用于接入和移动管理功能网元确定接入所述网络切片的终端设备的数量N，其中，所述N大于0；或者，指示信息用于网络切片准入控制功能网元确定不触发所述移动管理功能网元拒绝终端设备接入所述网络切片。
基于上述技术方案，本申请中，引入了一种“新的PDU会话状态”(即，终端设备即将建立PDU会话的状态)，使得接入和移动管理功能网元可以根据终端设备即将建立PDU会话的状态，确定不会拒绝该终端设备接入网络切片。不仅提高了网络切片中PDU会话的配置使用效率，也提高了终端设备接入网络切片的效率。
第六方面，提供了一种通信装置，该装置用于执行上述第一方面至第五方面任一种可能实现方式中的方法。具体地，该装置可以包括用于执行第一方面至第五方面任一种可能实现方式中的方法的单元和/或模块，如收发单元和/或处理单元。
在一种实现方式中，该装置为通信设备(例如：接入和移动管理功能网元，或者，终端设备，或者网络切片准入控制功能网元)。当该装置为通信设备时，通信单元可以是收发器，或，输入/输出接口；处理单元可以是至少一个处理器。可选地，收发器可以为收发电路。可选地，输入/输出接口可以为输入/输出电路。
在另一种实现方式中，该装置为用于通信设备(例如：接入和移动管理功能网元，或者，终端设备，或者网络切片准入控制功能网元)的芯片、芯片系统或电路。当该装置为用于通信设备的芯片、芯片系统或电路时，通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是至少一个处理器、处理电路或逻辑电路等。
第七方面，提供了一种通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第一方面和第三方面中任一种可能实现方式中的方法。可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通 信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为接入和移动管理功能网元。
在另一种实现方式中，该装置为用于接入和移动管理功能网元的芯片、芯片系统或电路。
第八方面，提供了一种通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第二方面或者第五方面中任一种可能实现方式中的方法。可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为终端设备。
在另一种实现方式中，该装置为用于终端设备的芯片、芯片系统或电路。
第九方面，提供了一种通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第四方面中任一种可能实现方式中的方法。可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为网络切片准入控制功能网元。
在另一种实现方式中，该装置为用于网络切片准入控制功能网元的芯片、芯片系统或电路。
第十方面，本申请提供一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行第一方面至第五方面中任一方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为一个或多个芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于收发器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则可以理解为处理器输出和接收、输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第十一方面，提供了一种处理设备，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过收发器接收信号，通过发射器发射信号，以执行第一方面至第五方面中任一方面中任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程， 接收能力信息可以为处理器接收输入能力信息的过程。具体地，处理器输出的数据可以输出给发射器，处理器接收的输入数据可以来自收发器。其中，发射器和收发器可以统称为收发器。
上述第十一方面中的处理设备可以是一个或多个芯片。该处理设备中的处理器可以通过硬件来实现也可以通过软件来实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第十二方面，提供一种计算机可读存储介质，该计算机可读介质存储用于设备执行的程序代码，该程序代码包括用于执行上述第一方面至第五方面任一种可能实现方式中的方法。
第十三方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第五方面任一种可能实现方式中的方法。
第十五方面，提供了一种通信系统，所述通信系统包括：接入和移动管理功能网元和终端设备，所述接入和移动管理功能网元，用于执行上述第一方面任一种可能实现方式中的方法，所述终端设备，用于执行上述第二方面任一种可能实现方式中的方法。
第十六方面，提供了一种通信系统，所述通信系统包括：接入和移动管理功能网元和终端设备，所述接入和移动管理功能网元，用于执行上述第三方面任一种可能实现方式中的方法，所述终端设备，用于执行上述第五方面任一种可能实现方式中的方法。
第十七方面，提供了一种通信系统，所述通信系统包括：接入和移动管理功能网元和终端设备，所述接入和移动管理功能网元，用于执行上述第四方面任一种可能实现方式中的方法，所述终端设备，用于执行上述第五方面任一种可能实现方式中的方法。
附图说明
图1是本申请适用的一种系统架构的示意图。
图2是本申请提出的通信方法200的示意性框图。
图3是本申请提出的通信方法300的示意性流程图。
图4是本申请提出的通信方法400的示意性框图。
图5是本申请提出的通信方法500的示意性流程图。
图6是本申请提出的通信方法600的示意性框图。
图7是本申请提出的通信方法700的示意性流程图。
图8是本申请提出的通信装置100的示意性框图。
图9是本申请提出的通信装置200的示意性框图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请提及的无线通信系统包括但不限于：全球移动通信(global system of mobile communication，GSM)系统、长期演进(long term evolution，LTE)频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、LTE系统、先进的长期演进(LTE-Advanced，LTE-A)系统、下一代通信系统(例如，6G通信系统)、 多种接入系统的融合系统，或演进系统。
本申请提供的技术方案还可以应用于机器类通信(machine type communication，MTC)、机器间通信长期演进技术(long term evolution-machine，LTE-M)、设备到设备(device to device，D2D)网络、机器到机器(machine to machine，M2M)网络、物联网(internet of things，IoT)网络或者其他网络。其中，IoT网络例如可以包括车联网。其中，车联网系统中的通信方式统称为车到其他设备(vehicle to X，V2X，X可以代表任何事物)，例如，该V2X可以包括：车辆到车辆(vehicle to vehicle，V2V)通信，车辆与基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。
需要说明的是本申请提出的技术方案可以适用于第5代(the 5th generation，5G)移动通信技术以及未来的其他移动通信技术例如，5G中的非漫游场景和漫游场景。例如，5G中的服务化的系统架构和基于参考点的架构，等等。
图1是本申请适用的一种系统架构的示意图，图1示出的是非漫游5G系统架构(基于参考点)的示意图。为了便于理解本申请实施例，首先结合图1对适用于本申请实施例的系统架构进行详细说明。该系统架构具体可以包括下列网元：
1、用户设备(user equipment，UE)：也可以称为终端设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。
终端设备可以是一种向用户提供语音/数据的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，终端设备还可以是IoT系统中的终端设备，IoT是未来信 息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物互连的智能化网络。
需要指出的是，终端设备与接入网设备之间可以采用某种空口技术(如NR或LTE技术等)相互通信。终端设备与终端设备之间也可以采用某种空口技术(如NR或LTE技术等)相互通信。
本申请实施例中，用于实现终端设备的功能的装置可以是终端设备，也可以是能够支持终端设备实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在终端设备中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
2、(无线)接入网(radio access network，(R)AN)：用于为特定区域的授权用户提供入网功能，并能够根据用户的级别，业务的需求等使用不同质量的传输隧道。(R)AN)AN网元能够管理无线资源，为终端设备提供接入服务，进而完成控制信号和用户数据在终端设备和核心网之间的转发，(R)AN)也可以理解为传统网络中的基站。
3、接入和移动性管理功能(access and mobility management function，AMF)：主要用于移动性管理和接入管理等。具体地，AMF可以用于实现移动性管理实体(mobility management entity，MME)的功能中除会话管理之外的其它功能，例如，合法监听、或接入授权(或鉴权)等功能。
例如，RAN设备可以为采用不同的无线接入技术。目前的无线接入技术有两种类型：3GPP接入技术(例如，第三代(3rd generation，3G)、第四代(4th generation，4G)或5G系统中采用的无线接入技术)和非3GPP(non-3GPP)接入技术。3GPP接入技术是指符合3GPP标准规范的接入技术，例如，5G系统中的接入网设备称为下一代基站节点(next generation Node Base station，gNB)或者RAN设备。非3GPP接入技术可以包括以无线保真(wireless fidelity，WiFi)中的接入点(access point，AP)为代表的空口技术、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)、码分多址(code division multiple access，CDMA)等。AN设备可以允许终端设备和3GPP核心网之间采用非3GPP技术互连互通。
RAN设备能够负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。AN设备为终端设备提供接入服务，进而完成控制信号和用户数据在终端设备和核心网之间的转发。
RAN设备例如可以包括但不限于：宏基站、微基站(也称为小站)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)，WiFi系统中的AP、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G(如，NR)系统中的gNB或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如分布式单元(distributed unit，DU)，或者下一代通信6G系统中的基站等。本申请实施例对RAN设备所采用的具体技术和具体设备形态不做限定。
4、会话管理功能(Session Management Function，SMF)：主要用于会话管理、终端 设备的网络互连协议(Internet Protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。
5、用户平面功能(user plane function，UPF)：用于分组路由和转发、或用户面数据的服务质量(quality of service，QoS)处理等。UPF具体分为中间-UPF(intermediate-UPF，I-UPF)和锚点UPF(anchor-UPF，A-UPF)。其中，I-UPF与接入网RAN连接，A-UPF为会话锚点的UPF，A-UPF又可以称为PDU会话锚点(PDU session anchor，PSA)。
6、数据网络(data network，DN)：用于提供传输数据的网络，例如，Internet网络等。在本申请实施例的架构中，PSA接入远端DN，L-PSA可以接入本地DN。
7、认证服务功能(authentication server function，AUSF)：主要用于用户鉴权等。
8、策略控制功能(policy control function，PCF)：用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF、SMF网元等)提供策略规则信息等。
9、统一数据管理(unified data management，UDM)：用于处理用户标识、接入鉴权、注册、或移动性管理等。
10、应用功能(application function，AF)：主要支持与第三代合作伙伴计划(3rd generation partnership project，3GPP)核心网交互来提供服务，例如，影响数据路由决策、策略控制功能、或者向网络侧提供第三方的一些服务。可理解为第三方服务器，例如，Internet中的应用服务器，提供相关业务信息，包括向PCF提供业务对应的服务质量需求信息，以及向PSA-UPF发送业务的用户面数据信息。AF可以是服务提供商(content provider，CP)。
11、网络切片选择功能(network slice selection function，NSSF)：用于进行网络切片的选择。
12、网络切片准入控制功能(network slice admission control function，NSACF)网元：可以支持监控和控制每个网络切片的注册用户数、支持监控和控制每个网络切片建立的PDU会话数、支持基于事件的网络切片状态通知并向其他NF报告。
13、网络切片和SNPN身份验证和授权功能(NSSAAF)支持以下功能：可以支持使用AAA服务器(AAA-S)对指定的网络切片特定身份验证和授权，。如果AAA-S属于第三方，NSSAAF可以通过AAA代理(AAA-P)联系AAA-S。支持使用AAA服务器(AAA-S)的凭据访问SNPN。如果凭据持有者属于第三方，NSSAAF可以通过AAA代理(AAA-P)联系AAA服务器。
可选的，该系统架构中还可以包括：网络数据分析功能网元(network data analytics function，NWDAF)，NWDAF具备以下至少一种功能：数据收集功能、数据分析功能。其中，数据收集功能是指用于收集来自网络网元、第三方业务服务器、终端设备或网管系统中的相关数据；数据分析功能是指基于相关输入数据做分析训练得到模型，并基于模型做推理确定数据分析结果，然后向网络网元、第三方业务服务器、提供终端设备或网管系统提供数据分析结果，该分析结果可协助网络选择业务的服务质量参数，或协助网络执行流量路由，或协助网络选择背景流量传输策略等。
在本申请的实施例中，NWDAF可以是一个单独的网元，也可以与其它核心网网元合设。例如，NWDAF网元可以与接入和移动性管理功能网元(access and mobility management function，AMF)网元合设或者与会话管理功能网元(session management function，SMF) 网元合设。
在该系统架构中，N1接口为终端设备与AMF之间的参考点；N2接口为(R)AN和AMF的参考点，用于非接入层(non-access stratum，NAS)消息的发送等；N3接口为(R)AN和I-UPF之间的参考点，用于传输用户面的数据等；N4接口为SMF和I-UPF之间的参考点，用于传输例如N3连接的隧道标识信息、数据缓存指示信息、以及下行数据通知消息等信息；N5接口为PCF与AF之间的参考点；N6接口为UPF和DN之间的参考点，用于传输用户面的数据等；N7接口为SMF和PCF之间的参考点；N8接口为AMF和UDM之间的参考点；N9接口为UPF之间的参考点；N10接口为SMF与UDM之间的参考点；N11接口为AMF与SMF之间的参考点；N12接口为AMF与AUSF之间的参考点；N22接口为AMF与NSSF之间的参考点；N80接口为NASCF与AMF之间的参考点；N81接口为NSACF与SMF之间的参考点；N59接口为NSSAAF与UDM之间的参考点；N58接口为NSSAAF与AMF之间的参考点。
应理解，上述图1应用于本申请实施例的系统架构仅是举例说明的从参考点架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
需要说明的是，图1中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请实施例对此不作具体限定。并且，本申请也不排除随着技术的演进，各个核心网网元之间可以合设。
需要说明的是，图1中包括的各个网元(比如SMF、AF、UPF等)的名称也仅是一个示例，对网元本身的功能不构成限定。在5G网络以及未来其它的网络中，上述各个网元也可以是其他的名称，本申请实施例对此不作具体限定。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称，等等，在此进行统一说明，以下不再赘述。此外，应理解，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
为便于理解本申请实施例，首先对本申请中涉及到的术语作简单说明。
1、协议数据单元(protocol data unit，PDU)会话：一个PDU会话可以是指一个终端设备与数据网络DN之间进行通讯的过程。PDU会话建立后，也就是建立了一条UE和DN的数据传输通道。PDU会话的类似于2/3G的数据包协议(packet data protocol，PDP)上下文(contex)、4G的承载上下文。
其中，PDU会话信息包括号码、国际移动用户识别码(international mobile subscriber identity，IMSI)、国际移动设备识别码(International Mobile Equipment Identity，IMEI)、PDU会话标识(identifier，ID)、会话类型(IPv4、IPv6、IPv4v6、Ethenet、Unstructured)、上下行速率、计费ID、漫游状态信息、UE的互联网协议(internet protocol，IP)信息、PCF信息、服务质量(quality of service，Qos)信息、隧道信息、目的地地址、SMF标识、切片信息(如果支持)、默认数据无线承载(data radio bearer，DRB)信息、数据网名、AMF信息、用户位置信息、会话管理信息、UPF ID、在线计费标识、离线计费标识等相关信息。
从PDU会话信息可以看到，PDU会话保存有用户面的数据路由、Qos、计费、网络切片、速率等可能与计费相关的重要信息。
2、网络切片(network slicing)：网络切片是通过切片技术在一个通用硬件基础上虚拟出多个端到端的网络，每个网络具有不同网络功能，适配不同类型服务需求。例如，运营商购买物理资源后，针对大众上网业务使用物理资源虚拟出一个增强型移动宽带业务(enhanced mobile broadband，eMBB)切片网络，之后再针对垂直行业中某些厂商的智能抄表需求，使用物理资源再虚拟出一个大规模机器通信业务(massive machine type communication，mMTC)切片网络以及超可靠低时延通信(ultra-reliable and low-latency communication，uRRLC)切片网络，该三个切片网络分别为不同业务场景提供服务。
2.1、单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)：S-NSSAI可以用来标识一个网络切片，根据运营商的运营或部署需要，一个S-NSSAI可以关联一个或多个网络切片实例(instance)，一个网络切片实例又可以关联一个或多个S-NSSAI。
2.2、网络切片选择辅助信息(network slice selection assistance information，NSSAI)指的是S-NSSNI的集合。5G网络中使用到的NSSAI有请求(Requested)NSSAI、允许(Allowed)NSSAI、配置(Configured)NSSAI，等等。
其中，Requested NSSAI可以理解为，是终端设备期望使用的NSSAI，终端设备在注册流程中提供给网络侧的，例如可以最多包括8个S-NSSAI。Allowed NSSAI可以理解为，是服务PLMN在注册等流程中提供的给终端设备的，指示终端设备在服务PLMN的当前注册区域可以使用的S-NSSAI值，例如可以最多包括8个S-NSSAI，终端设备本地保存。ConfiguredNSSAI可以理解为，是适用于一个或多个PLMN的NSSAI，AMF在注册接受或配置更新命令等消息中下发给终端设备，例如可以最多包括16个S-NSSAI，终端设备本地保存。
由于网络切片对终端设备的接入数量是有限制，NSACF网元可以监控每个网络切片上所接入的终端设备的数量。并且，目前运营商没有能力实现基于每个终端设备的实际使用请求(例如，某个终端设备当前需要建立PDU会话传输数据)，便立即允许该终端设备接入到网络切片上。此时，可能会出现如下场景：大量的终端设备可能会请求接入到网络切片，但是这些终端设备并不一定建立PDU会话。当其它还没有接入到网络切片的终端设备确实需要建立PDU会话时，NSACF却又可能因为网络切片上终端设备接入数量的限制，拒绝该终端设备接入到该网络切片，从而使得PDU会话资源不能合理的配置和使用，降低用户的业务体验。
有鉴于此，本申请提出一种通信方法和装置，如果接入和移动管理功能网元确定超过第一时间后终端设备的协议数据单元PDU会话状态不满足网络切片的第一条件(其中，第一条件是与终端设备的PDU会话状态相关的条件)，则确定拒绝该终端设备接入网络切片，从而可以合理的配置和使用网络切片中的PDU会话资源。
图2是本申请提出的一种通信方法200的示意性框图，下面对图2所示的各步骤进行说明。需要说明的是，图2中用虚线表示的步骤是可选的，在后文中不多赘述。该方法包括：
步骤201，接入和移动管理功能网元确定第一时间。
本申请中，“第一时间”例如可以理解为一个时间段；又例如，“第一时间”可以是时间单元。例如，“时间单元”可以是一个或多个无线帧，一个或多个子帧，一个或多个 时隙，一个或多个微时隙，一个或多个符号等。其中，符号可以是正交频分复用(orthogonal frequency division multiplexing，OFDM)符号、离散傅里叶变换扩频的正交频分复用(discrete fourier transform spread spectrum orthogonal frequency division multiplexing，DFT-S-OFDM)符号等。例如，第一时间还可以是1秒(second，简称“s”)或多秒，1毫秒(millisecond，简称“ms”)或多毫秒等。
可选的，在步骤201之前，还包括步骤202，接入和移动管理功能网元获取指示第一时间的信息。
在一种可能的实现方式中，接入和移动管理功能网元可以从NSACF获取指示第一时间的信息。具体的，例如，NSACF可以向接入和移动管理功能网元发送指示信息#1，指示信息#1可以用于指示第一时间。
在另一种可能的实现方式中，接入和移动管理功能网元可以从UDM获取指示第一时间的信息。具体的，NSACF可以向接入和移动管理功能网元发送指示信息#2，指示信息#2可以用于指示第一时间。
在又一种可能的实现方式中，接入和移动管理功能网元上预配置了指示第一时间的字段，AMF可以从本地配置中获取第一时间。
步骤203，在第一时间超时后，若终端设备的PDU的会话状态不满足网络切片的第一条件，则接入和移动管理功能网元拒绝该终端设备接入网络切片。
需要说明的是，本申请中提到的“网络切片”也可以理解为S-NSSAI，该S-NSSAI可以唯一标识该网络切片。也可以理解为，本申请中“网络切片”可以替换为“S-NSSAI”进行理解，以下不再赘述。
例如，接入和移动管理功能网元可以通过用户配置更新(user configuration update，UCU)流程，向终端设备发送UE配置更新命令，该UE配置更新命令中可以将该终端设备请求的网络切片更新为“Rejected NSSAI”，从而表示接入和移动管理功能网元拒绝该终端设备接入该网络切片。
在一种可能的实现方式中，网络切片的第一条件(以下简称“第一条件”)可以包括以下至少一项：该终端设备为该网络切片建立PDU会话；或者，该终端设备为该网络切片建立的PDU会话中有激活的用户面；或者，该终端设备为该网络切片建立的PDU会话中有传输第一业务的数据。
本申请中，一个网络切片上可以允许接入多个终端设备，并且接入的每个终端设备都可以为该网络切片建立多条PDU会话。本申请中，第一条件中的“所述终端设备为所述网络切片建立PDU会话”可以理解为，终端设备只要为该网络切片建立任一条PDU会话就可以满足第一条件。同样的，“所述终端设备为所述网络切片建立的PDU会话中有激活的用户面”也可以理解为，终端设备为所述网络切片建立的任一条PDU会话中有激活的用户面，即可以满足第一条件。“所述终端设备为所述网络切片建立的PDU会话中有传输第一业务的数据”可以理解为，终端设备为所述网络切片建立的任一条PDU会话中有传输第一业务的数据，即可以满足第一条件。
本申请中，“建立的PDU会话中有激活的用户面激活”可以理解为，建立的PDU会话中有数据传输。
本申请中的“第一业务”可以指终端设备多个数据传输业务中的任意一个业务，也可 以是指终端设备多个数据传输业务中的某个特定的业务(也可以理解为是，特定的应用)，不予限定。
例如，接入和移动管理功能网元在可以在某个特定的时刻开始启动定时器，该定时器的定时时长为第一时间(例如，第一时间可以为20秒)。
示例性的，接入和移动管理功能网元启动定时器的时刻，例如可以是接入和移动管理功能网元接收到终端设备请求接入网络切片的消息的时刻。此时，接入和移动管理功能网元在该定时器超时后可以判断终端设备是否为该网络切片建立PDU会话；或者，为该网络切片建立的PDU会话中是否有激活的用户面；或者为该网络切片建立的PDU会话中是否有传输第一业务的数据。
示例性的，启动定时器的时刻可以是接入和移动管理功能网元感知到终端设备释放为该网络切片建立的其中一条PDU会话(例如，可以是接入和移动管理功能网元感知到终端设备释放为该网络切片建立的最后一条PDU会话释放)的时刻。此时，接入和移动管理功能网元在该定时器超时后可以判断终端设备是否为该网络切片建立PDU会话；或者，为该网络切片建立的PDU会话中是否有激活的用户面；或者为该网络切片建立的PDU会话中是否有传输第一业务的数据。
示例性的，启动定时器的时刻可以是接入和移动管理功能网元感知到终端设备首次为该网络切片完成一条PDU会话(例如，PDU会话#1)建立的时刻(该场景下，第一条件可能为：所述终端设备为所述网络切片建立的PDU会话中有激活的用户面；或者，所述终端设备为所述网络切片建立的PDU会话中有传输第一业务的数据)。此时，接入和移动管理功能网元在该定时器超时后可以判断为该网络切片建立的PDU会话中是否有激活的用户面；或者，为该网络切片建立的PDU会话中是否有传输第一业务的数据。
示例性的，启动定时器的时刻可以是接入和移动管理功能网元感知到终端设备为该网络切片建立的PDU会话中去激活的用户面(例如，可以是接入和移动管理功能网元感知到终端设备建立的最后一个有激活用户面的PDU会话去激活)的时刻(该场景下，第一条件可能为：所述终端设备为所述网络切片建立的PDU会话中有激活的用户面；或者，所述终端设备为所述网络切片建立的PDU会话中有传输第一业务的数据)。此时，接入和移动管理功能网元在该定时器超时后可以判断为该网络切片建立的PDU会话中是否有激活的用户面；或者，为该网络切片建立的PDU会话中是否有传输第一业务的数据。
示例性的，启动定时器的时刻可以是接入和移动管理功能网元确定第一业务的结束时刻(例如，接入和移动管理功能网元可以基于订阅的第一业务的结束时间，确定第一业务的结束时刻)。(该场景下，第一条件可能为：所述终端设备为所述网络切片建立的PDU会话中有激活的用户面；或者，所述终端设备为所述网络切片建立的PDU会话中有传输第一业务的数据)。此时，接入和移动管理功能网元在该定时器超时后可以判断为该网络切片建立的PDU会话中是否有激活的用户面；或者，为该网络切片建立的PDU会话中是否有传输第一业务的数据。
此时，步骤203也可以理解为，在第一时间超时前，若终端设备的PDU的会话状态满足网络切片的第一条件，则接入和移动管理功能网元允许该终端设备接入网络切片(即该S-NSSAI仍然属于Allowed NSSAI)。
在另一种可能的实现方式中，第一条件可以包括以下至少一项：该终端设备没有为该 网络切片建立PDU会话；或者，该终端设备为该网络切片建立的PDU会话中没有激活的用户面；或者，该终端设备为该网络切片建立的PDU会话中没有传输第一业务的数据。
此时，步骤203可以理解为，在第一时间超时后，若终端设备的PDU的会话状态满足网络切片的第一条件，则接入和移动管理功能网元拒绝该终端设备接入网络切片。
具体的，第一条件可以为该终端设备为该网络切片建立的PDU会话中有激活的用户面，以及，该终端设备为该网络切片建立的PDU会话中有传输第一业务的数据。又例如，第一条件可以为，终端设备为该网络切片建立PDU会话，并且在该网络切片建立的PDU会话中有传输第一业务的数据，等等。
本申请中的“第一条件”例如可以是接入和移动管理功能网元从NSACF获取的，或者接入和移动管理功能网元从UDM获取的，或者接入和移动管理功能网元本地配置的，不予限定。
在一种可能的实现方式中，接入和移动管理功能网元可以向会话管理功能网元订阅该第一业务的开始事件。
在一种可能的实现方式中，接入和移动管理功能网元可以向策略控制管理网元订阅该第一业务的开始事件。
可选的，接入和移动管理功能网元还可以向会话管理功能网元订阅该第一业务的结束事件。
本申请中，“第一业务的开始事件”可以理解为开始传输第一业务的数据的事件；“第一业务的结束事件”可以理解为结束传输第一业务的数据的事件。
例如，接入和移动管理功能网元上可以配置定时器(例如，timer定时器)，接入和移动管理功能网元可以启动该定时器，如果在定时器启动后30s(例如，第一时间为30s)后，终端设备仍然没有建立PDU会话，则接入和移动管理功能网元可以拒绝该终端设备接入网络切片。
可选的，在步骤203之前还包括步骤204，接入和移动管理功能网元获取网络切片的属性信息，并根据属性信息确定第一条件。
在一种可能的实现方式中，网络切片的属性信息可以包括以下至少一项：在第一时间超时后，若该终端设备没有为该网络切片建立PDU会话，则拒绝终端设备接入所述网络切片；或者，在第一时间超时后，若该终端设备为所述网络切片建立的PDU会话中没有激活的用户面，则接入和移动管理功能网元拒绝终端设备接入所述网络切片；或者，在第一时间超时后，若终端设备为网络切片建立的PDU会话中没有传输第一业务的数据，则接入和移动管理功能网元拒绝该终端设备接入所述网络切片。
需要说明的是，如果终端设备订阅的是多个数据传输业务中的某个特定的业务，则在网络切片的属性信息和终端设备的PDU会话状态中还可以包含该特定应用的标识信息或者特定业务的数据流模板(例如，互联网协议(internet protocol，IP)五元组(即，源IP地址、源端口、目的IP地址、目的端口和传输层协议)等)。
在另一种可能的实现方式中，网络切片的属性信息可以包括以下至少一项：在第一时间超时前，若该终端设备为该网络切片建立PDU会话，则允许终端设备接入所述网络切片；或者，在第一时间超时前，若该终端设备为所述网络切片建立的PDU会话中有激活的用户面，则接入和移动管理功能网元允许终端设备接入所述网络切片；或者，在第一时 间超时前，若终端设备为网络切片建立的PDU会话中有传输第一业务的数据，则接入和移动管理功能网元允许该终端设备接入所述网络切片。
本申请中，网络切片的属性信息可以是接入和移动管理功能网元从NSACF获取的，或者可以是接入和移动管理功能网元从UDM获取的，或者可以是接入和移动管理功能网元本地配置的，不予限定。
应理解，步骤204和步骤201、步骤202之间可以没有先后顺序。例如步骤201和步骤203可以同时执行。即，终端设备在确定第一时间的同时，还可以获取网络切片的属性信息，不予限定。
可选的，还包括步骤205，接入和移动管理功能网元接收来自该终端设备的终端设备将要建立PDU会话的指示信息，并且根据该指示信息确定第一时间。
在一种可能的实现方式中，接入和移动管理功能网元在步骤201中确定的第一时间为时间#A，如果接入和移动管理功能网元接收来自该终端设备的终端设备将要建立PDU会话的指示信息，则接入和移动管理功能网元延长了时间#A，本申请将延长后的时间记为时间#B，时间#B大于时间#A，并最终将时间#B作为第一时间。
在另一种可能的实现方式中，接入和移动管理功能网元预配置了多个定时器，一旦接入和移动管理功能网元接收来自该终端设备的终端设备将要建立PDU会话的指示信息，则接入和移动管理功能网元会在多个定时器中选择定时时间较大的定时器作为第一时间的定时器。
在又一种可能的实现方式中，如果接入和移动管理功能网元接收来自该终端设备的终端设备将要建立PDU会话的指示信息，则接入和移动管理功能网元可以直接将步骤201中确定的第一时间进行修改(“修改”也可以理解为“更新”或者“重新设置”)，使得修改后的第一时间大于步骤201中确定的第一时间。
也就是说，对于上述的几种实现方式，通过来自该终端设备的终端设备将要建立PDU会话的指示信息，网络设备在设置第一时间的时候，考虑到终端设备后续将要建立PDU会话，对于终端设备的第一时间可以相对宽裕一点。
在另一种可能的实现方式中，接入和移动管理功能网元在步骤201中确定的第一时间为时间#A，如果接入和移动管理功能网元接收来自该终端设备的终端设备将要建立PDU会话的指示信息，后续即便终端设备的PDU会话状态不满足第一条件，接入和移动管理功能网元也不会拒绝该终端设备接入该网络切片(即该S-NSSAI仍然属于Allowed NSSAI)。进一步的，如果该S-NSSAI成为Allowed NSSAI，终端设备可以在超过第一时间前建立PDU会话。
也就是说，对于上述最后一种实现方式，只要终端设备后续将要建立PDU会话并发送了相应的指示信息，就可以废除对于该切片的上述监控，后续即便终端设备的PDU会话状态不满足第一条件，接入和移动管理功能网元也不会拒绝该终端设备接入该网络切片。
也可以理解为，本申请中引入了一种“新的PDU会话状态”(即，终端设备即将建立PDU会话的状态)，使得接入和移动管理功能网元可以根据终端设备即将建立PDU会话的状态，确定不会拒绝该终端设备接入网络切片。不仅提高了网络切片中PDU会话的配置使用效率，也提高了终端设备接入网络切片的效率。
可选的，还包括步骤206，在接入和移动管理功能网元拒绝该终端设备接入该网络切 片之前，接入和移动管理功能网元向该终端设备发送第一时间。
也可以理解为，本申请中，接入和移动管理功能网元还可以向终端设备发送第一时间，使得终端设备可以感知如果超过第一时间还未建立PDU会话，或者建立的PDU会话中没有激活的用户面，或者建立的PDU会中传输第一业务的数据，则会被拒绝接入该网络切片。
此时，终端设备可以接收来自接入和移动管理功能网元的第一时间，在第一时间超时后，若该终端设备的PDU的会话状态不满足第一条件，则该终端设备从移动管理功能网元接收拒绝接入所述网络切片的信息。此时，第一条件至少包括以下一项：该终端设备为该网络切片建立PDU会话；或者，该终端设备为该网络切片建立的PDU会话中有激活的用户面；或者，该终端设备为该网络切片建立的PDU会话中有传输第一业务的数据。
或者，终端设备可以接收来自接入和移动管理功能网元的第一时间，在第一时间超时后，若该终端设备的PDU的会话状态满足第一条件，则该终端设备从移动管理功能网元接收拒绝接入所述网络切片的信息。此时，第一条件至少包括以下一项：该终端设备没有为该网络切片建立PDU会话；或者，该终端设备为该网络切片建立的PDU会话中没有激活的用户面；或者，该终端设备为该网络切片建立的PDU会话中没有传输第一业务的数据。
可选的，还包括步骤207，在接入和移动管理功能网元拒绝该终端设备接入该网络切片之后，接入和移动管理功能网元向所述终端设备发送所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片的原因值。对应的，终端设备可以接收该原因值。
在一种可能的实现方式中，“原因值”可以包括以下至少一项：该终端设备没有为该网络切片建立PDU会话；或者，该终端设备为该网络切片建立的PDU会话中没有激活的用户面；或者，该终端设备为该网络切片建立的PDU会话中没有传输第一业务的数据。
在另一种可能的实现方式中，“原因值”可以包括以下至少一项：该终端设备需要为该网络切片建立PDU会话；或者，该终端设备为该网络切片建立的PDU会话中需要有激活的用户面；或者，该终端设备为该网络切片建立的PDU会话中需要有传输第一业务的数据。
在又一种可能的实现方式中，“原因值”可以包括以下至少一项：该终端设备超过第一时间后没有为该网络切片建立PDU会话；或者，该终端设备超过第一时间后为该网络切片建立的PDU会话中没有激活的用户面；或者，该终端设备超过第一时间后为该网络切片建立的PDU会话中没有传输第一业务的数据。
在上述最后一种实现方式中，终端设备可以感知到需要在超过第一时间前建立PDU会话，或者超过第一时间前为该网络切片建立的PDU会话中有激活的用户面；或者，在超过第一时间前为该网络切片建立的PDU会话中有传输第一业务的数据，才不会被拒绝接入该网络切片。具体的，假设终端设备#1被接入和移动管理功能网元拒绝接入网络切片#1，并且终端设备#1收到了原因值。则该终端设备#1仍然可以向接入和移动管理功能网元请求接入网络切片#1。但是，此时终端设备#1将会在超过第一时间前为该网络切片建立PDU会话，或者超过第一时间前为该网络切片建立的PDU会话中将会激活用户面；或者，在超过第一时间前为该网络切片建立的PDU会话中将会传输第一业务的数据。
进一步的，如果终端设备判断在超过第一时间前将不会建立PDU会话，则不请求该 S-NSSAI(即Requested NSSAI中不包含该S-NSSAI)；或者，如果终端设备判断在超过第一时间前将会建立PDU会话，则会请求该S-NSSAI(即Requested NSSAI中可以包含该S-NSSAI)。例如，终端设备可以根据保存的历史信息确定后面会不会为该网络切片建立PDU会话。
或者，如果终端设备判断在超过第一时间前在建立的PDU会话中将不会激活用户面，则不请求该S-NSSAI(即Requested NSSAI中不包含该S-NSSAI)；或者，如果终端设备判断在超过第一时间前在建立的PDU会话中将会有激活的用户面，则请求该S-NSSAI(即Requested NSSAI中可以包含该S-NSSAI)。例如，终端设备可以根据保存的历史信息确定后续在为该网络切片建立的PDU会话中是否会有激活的用户面。示例性的，终端设备#1可以基于配置信息或者历史信息确定，晚上八点需要进行视频会议。此时，可以请求接入该网络切片。
或者，如果终端设备判断在超过第一时间前在建立的PDU会话中将没有传输第一业务的数据，则不请求该S-NSSAI(即Requested NSSAI中不包含该S-NSSAI)；或者，如果终端设备判断在超过第一时间前建立PDU会话的PDU会话中将会有传输第一业务的数据，则请求该S-NSSAI即Requested NSSAI中可以包含该S-NSSAI)。例如，终端设备可以根据保存的历史信息确定后续在为该网络切片建立的PDU会话中是否会有传输第一业务的数据。示例性的，终端设备#2可以基于配置信息或者历史信息确定，早上六点会使用某个应用程序(application，APP)。此时，可以请求接入该网络切片。
基于上述技术方案，本申请中，接入和移动管理功能网元可以根据第一时间和第一条件，即，如果接入和移动管理功能网元确定超过第一时间后终端设备的PDU会话状态不满足网络切片的第一条件，则确定拒绝该终端设备接入网络切片。从而保证不会有终端设备长时间接入该网络切片而不建立/激活PDU会话，提高了网络切片中PDU会话资源的使用效率，提高了用户的业务体验。
图3是本申请提出的一个具体实施例通信方法300，该方法从各个网元交互的角度示出了本申请技术方案的，方法300中以终端设备是UE#1为例，以网络切片为网络切片#1为例进行说明，该方法300包括：
步骤301，UE#1请求注册到网络切片#1，并获取S-NSSAI#1。
其中，步骤301中的“注册”也可以理解为“接入”。其中，S-NSSAI#1可以用于标识网络切片#1。
步骤301的具体实现方式参照技术规范(technical specification，TS)23.501，5.15章节。
例如，UE通过一种接入类型注册到公共陆地移动网PLMN上时，可以发送注册请求消息给RAN。RAN可以根据Requested NSSAI为选择终端设备初始(Initial)AMF。Initial AMF可以根据收到的Requested NSSAI、Subscribed S-NSSAI及本地配置判断是否可以为UE提供服务。如果AMF可以为UE服务，则Initial AMF仍然是UE的服务AMF，然后AMF基于Subscribed S-NSSAI和Requested NSSAI构造出Allowed NSSAI，并通过注册接受消息发送给UE。
即，也可以理解为，步骤301中UE可以接入到网络切片#1。
步骤302，AMF向NSACF上报本次接入网络切片#1的UE的数量的信息。对应的 NSACF接收该信息。
步骤303，NSACF向AMF发送网络切片#1的属性信息和指示第一时间的信息。对应的，AMF接收网络切片#1的属性信息和指示第一时间的信息。
例如，NSACF收到AMF发送上报本次接入网络切片#1的UE的数量的信息后，可以将网络切片#1的属性信息和指示第一时间的信息发送给AMF。
应理解，NSACF向AMF发送的网络切片#1的属性信息和指示第一时间的信息可以在同一条信息中，也可以在不同的信息中分别发送，本申请不予限定。
具体的，步骤303中的“属性信息”和“第一时间”的理解可以参照方法200中步骤204中“属性信息”的描述。
步骤304，在第一时间超时后，若UE#1的PDU的会话状态不满足网络切片#的第一条件，则AMF向UE#1发送拒绝该UE#1接入网络切片#1的信息。对应的，UE#1接收该信息。
具体的，AMF可以根据网络切片#1的属性信息确定第一条件，并根据指示第一时间的信息确定第一时间。
具体的，步骤304中关于“第一条件”的理解可以参照方法200中步骤203中“第一条件”的描述。
本申请中，例如，AMF可以感知UE#1的PDU会话的状态。又例如，AMF还可以从NWDAF获取各个签约永久标识(subscription permanent identifier，SUPI)对应的UE的PDU会话状态。其中，NWDAF提供PDU会话状态的具体实现方式可以参见方法600中的步骤601所示。再例如，AMF还可以从SMF获取UE#1的PDU会话状态。再例如，AMF可以从NEF获取UE#1的PDU会话状态。等等。以下各个实施例中不再重复说明。
示例性的，如果网络切片#1的属性信息为在第一时间超时后，若UE#1在为网络切片#1建立的PDU会话中没有激活的用户面，则拒绝UE接入网络切片#1，则AMF确定第一条件为UE#1需要在为网络切片#1建立的PDU会话中有激活的用户面。此时，AMF可以向SMF订阅PDU会话中是否有数据。或者，AMF可以感知去激活的PDU会话。
示例性的，如果网络切片#1的属性信息为在第一时间超时后，若UE#1在为网络切片#1建立的PDU会话中没有传输业务#1的数据，则拒绝UE接入网络切片#1，则AMF确定第一条件为UE#1需要在为网络切片#1建立的PDU会话中有传输业务#1的数据。此时，AMF可以向SMF或PCF订阅业务#1的开始时间和结束事件。
例如，AMF可以通过指示第一时间的信息，确定第一时间。例如，指示第一时间的信息为下行控制信息(downlink control information，DCI)中的字段#1，则AMF可以通过解析DCI中的字段#1确定时间#A(第一时间的示例)的值。例如，时间#A为30ms。
在另一种可能的实现方式中，如果步骤301中，UE#1在请求注册到网络切片#1中时携带了follow on指示(终端设备将要建立PDU会话的指示信息)，则AMF可以根据该指示信息重新确定第一时间。
例如，AMF可以请求延长时间#A。具体的，AMF可以向NSACF或者UDM请求延长时间#A。例如，延长后的时间为时间#B(第一时间的示例)为100ms；或者，AMF可以在预配置的多个定时器中选择定时时间长于时间#A的定时器，作为判断是否拒绝UE#1接入网络切片#1的依据；或者，AMF可以直接将第一时间重新设置为时间#C，该时间#C 大于时间#A。例如时间#C为200ms；或者，后续即便UE#1的PDU会话状态不满足第一条件，AMF也不会拒绝该终端设备接入该网络切片#1。
需要说明的的，现有技术中，接入和移动管理功能网元并未对终端设备请求接入网络切片时的PDU会话状态做任何限制。而本申请中，在终端设备的PDU会话状态满足网络切片的第一条件时，虽然接入和移动管理功能网元允许该终端设备接入网络切片(即，步骤301中的S-NSSAI#1仍然是Allowed NSSAI)，但是和现有的流程相比，使得接入该网络切片的终端设备都可以有效的利用网络中的PDU会话资源，提高了用户的业务体验。
本申请中，AMF拒绝UE#1接入网络切片#1，具体可以是，AMF向UE#1发送拒绝该UE#1接入网络切片#1的信息。对应的，UE#1接收该信息。
可选的，该信息还可以包括拒绝UE#1接入的原因值。可选的，该信息中还可以包括第一时间。
例如，AMF可以向UE#1发送UE配置更新命令，UE配置更新命令表示拒绝UE#1接入网络切片#1。
当然，AMF也可以按照现有原因值拒绝UE#1接入网络切片#1，这样对UE#1没有影响，但UE#1不知道是被拒绝接入网络切片#1的原因。
关于上述“原因值”的理解可以参照方法200中步骤207中“原因值”的描述。
基于上述技术方案，本申请中，AMF可以根据第一时间和第一条件，即，如果AMF确定超过第一时间后UE不满足网络切片的第一条件，则确定拒绝该UE接入网络切片。从而保证不会有UE长时间接入该网络切片而不建立/激活PDU会话，提高了网络切片中PDU会话资源的使用效率，提高了用户的业务体验。
此外可选的，该方法还可以包括：
步骤305，UE#1确定被AMF拒绝接入网络切片#1的原因，并可以在第一时间超时前建立PDU会话，并重新请求接入该网络切片#1。
图4是本申请提供的一种通信方法400的示意框图，该方法包括：
步骤401，接入和移动管理功能网元确定网络切片的属性信息。
在一种可能的实现方式中，本实施例中的网络切片的属性信息可以理解为方法200中步骤204中描述的网络切片的属性信息。
在另一种可能的实现方式中，本实施例中的网络切片的属性信息也可以理解为包括以下至少一项：若该终端设备没有为该网络切片建立PDU会话，则接入和移动管理功能网元拒绝该终端设备接入该网络切片；或者，若该终端设备为该网络切片建立的PDU会话中没有激活的用户面，则接入和移动管理功能网元拒绝该终端设备接入所述网络切片；或者，若该终端设备为该网络切片建立的PDU会话中没有传输第一业务的数据，则该接入和移动管理功能网元拒绝该终端设备接入该网络切片。
或者，本实施例中的网络切片的属性信息也可以理解为包括以下至少一项：若该终端设备为该网络切片建立PDU会话，则接入和移动管理功能网元允许该终端设备接入该网络切片；或者，若该终端设备为该网络切片建立的PDU会话中有激活的用户面，则接入和移动管理功能网元允许该终端设备接入所述网络切片；或者，若该终端设备为该网络切片建立的PDU会话中有传输第一业务的数据，则该接入和移动管理功能网元允许该终端设备接入该网络切片。
换句话说，该实现方式中，网络切片的属性信息与步骤204中提到的“网络切片的属性信息”相比，接入和移动管理功能网元根据终端设备的PDU会话状态和网络切片的属性信息判断是否拒绝该终端设备接入网络切片时不用考虑“第一时间”的因素。例如，接入和移动管理功能网元确定网络切片的属性信息后，如果感知到终端设备并没有建立PDU会话，则会立刻拒绝该终端设备接入网络切片。
步骤402，接入和移动管理功能网元根据网络切片的属性信息和该终端设备的PDU会话状态，确定本次接入网络切片的终端设备的数量N，其中，N大于或者等于0，并且小于或者等于1。
例如，接入和移动管理功能网元可以在接收到终端设备请求接入网络切片的消息的时刻，确定本次接入网络切片的终端设备的数量N。又例如，接入和移动管理功能网元可以在感知到终端设备释放为该网络切片建立的其中一条PDU会话的时刻，确定本次接入网络切片的终端设备的数量N。再例如，接入和移动管理功能网元可以在感知到终端设备首次为该网络切片完成一条PDU会话(例如，PDU会话#1)建立的时刻确定本次接入网络切片的终端设备的数量N。例如，接入和移动管理功能网元可以是在感知到终端设备为该网络切片建立的PDU会话中去激活的用户面的时刻，确定本次接入网络切片的终端设备的数量N。例如，接入和移动管理功能网元可以是在确定第一业务的结束时刻，确定本次接入网络切片的终端设备的数量N。
也可以理解为，本申请中，只要该终端设备的PDU会话状态发生变化，接入和移动管理功能网元就可以更新一下本次接入网络切片的终端设备的数量N。
具体的，终端设备确定N的取值的可以有以下实现方式：
在一种可能的实现方式中，例如，网络切片的属性信息为：在第一时间超时后，若终端设备没有为网络切片建立PDU会话，则接入和移动管理功能网元拒绝终端设备接入所述网络切片。此时，如果接入和移动管理功能网元感知到终端设备没有建立PDU会话，则可以确定N为0。如果接入和移动管理功能网元感知到终端设备建立了PDU会话，则可以确定N为1。具体的：如果接入和移动管理功能网元感知到终端设备建立了PDU会话，但该PDU会话中没有激活的用户面，则可以确定N为1。如果接入和移动管理功能网元感知到终端设备建立了PDU会话，并且该PDU会话中有激活的用户面，则可以确定N为1。如果接入和移动管理功能网元感知到终端设备建立了PDU会话，却没有传输第一业务的数据，则可以确定N为1。如果接入和移动管理功能网元感知到终端设备建立了PDU会话，并且有传输第一业务的数据，则可以确定N为1。也就是说，只要接入和移动管理功能网元感知到终端设备建立了PDU会话，无论该PDU会话中是否有激活的用户面，或者，无论该PDU会话中是否传输第一业务的数据，都可以确定N为1。
在另一种可能的实现方式中，网络切片的属性信息为：若终端设备为网络切片建立的PDU会话中没有激活的用户面，则接入和移动管理功能网元拒绝终端设备接入所述网络切片。此时，如果接入和移动管理功能网元感知到终端设备没有建立PDU会话，则可以确定N为0。如果接入和移动管理功能网元感知到终端设备建立了PDU会话，但该PDU会话中没有激活的用户面，则可以确定N为0.5。如果接入和移动管理功能网元感知到终端设备建立了PDU会话，并且该PDU会话中有激活的用户面，则可以确定N为1。可以理解的是，如果该PDU会话上有传输第一业务的数据，这表示了该PDU会话中一定有激 活的用户面。如果接入和移动管理功能网元感知到终端设备建立了PDU会话，并且有传输第一业务的数据，则可以确定N为1。
在又一种可能的实现方式中，网络切片的属性信息为：若终端设备为网络切片建立的PDU会话中没有传输第一业务的数据，则接入和移动管理功能网元拒绝终端设备接入所述网络切片。此时，如果接入和移动管理功能网元感知到终端设备没有建立PDU会话，则可以确定N为0。如果接入和移动管理功能网元感知到终端设备建立了PDU会话，但该PDU会话中没有激活的用户面，则可以确定N为0.5。如果接入和移动管理功能网元感知到终端设备建立了PDU会话，并且有激活的用户面，但是没有传输第一业务的数据，则可以确定N为0.7。如果接入和移动管理功能网元感知到终端设备建立了PDU会话，并且正在传输第一业务的数据，则可以确定N为1。
当N的取值为0～1之间的小数时，此时可以理解为，该终端设备需要占用的PDU会话的资源为乘以0～1之间的小数的倍数后的资源。上述实现方式也可以理解为，如果接入和移动管理功能网元确定该终端设备的PDU会话状态不符合该网络切片的属性，则AMF确定所述N大于0小于1。基于本申请提供的方法，提出了N的取值可以为0～1之间的小数，也可以理解为，此时，终端设备不用占用配额或者占用配额相对少一点的配额，从而允许更多的符合网络切片的属性的终端设备接入该网络切片，提高了PDU会话资源的使用效率。
应理解，本实施例中，接入和移动管理功能网元可以根据终端设备的PDU会话的状态，实时更新N的取值。
假设，网络切片的属性信息为：在第一时间超时后，若终端设备没有为网络切片建立PDU会话，则接入和移动管理功能网元拒绝终端设备接入所述网络切片。此时，如果时刻#1接入和移动管理功能网元感知到终端设备没有建立PDU会话，则可以确定N为0。即，接入和移动管理功能网元可以向网络切片准入控制功能网元上报一次N的取值。如果时刻#1之后接入和移动管理功能网元在时刻#2感知到终端设备建立了PDU会话，则可以确定N为1。即，接入和移动管理功能网元可以再次向网络切片准入控制功能网元更新一次N的取值。
可选的，该方法还包括步骤403，接入和移动管理功能网元接收来自该终端设备的终端设备将要建立PDU会话的指示信息，并确定N大于0。
例如，接入和移动管理功能网元接收来自该终端设备的终端设备将要建立PDU会话的指示信息，如果网络切片的属性信息为：在第一时间超时后，若终端设备没有为网络切片建立PDU会话，则接入和移动管理功能网元拒绝终端设备接入所述网络切片。此时，即便接入和移动管理功能网元感知到终端设备没有建立PDU会话，也会确定N为1，或者确定N为0.5，或者确定N为0.8，等等。
又例如，接入和移动管理功能网元接收来自该终端设备的终端设备将要建立PDU会话的指示信息，如果网络切片的属性信息为：若终端设备为网络切片建立的PDU会话中没有激活的用户面，则接入和移动管理功能网元拒绝终端设备接入所述网络切片。此时，即便接入和移动管理功能网元感知到终端设备没有建立PDU会话，或者终端设备建立的PDU会话中没有激活的用户面，或者终端建立的PDU会话中没有传输第一业务的数据，也会确定N为1，或者确定N为0.5，或者确定N为0.8，等等。
再例如，接入和移动管理功能网元接收来自该终端设备的终端设备将要建立PDU会话的指示信息，如果网络切片的属性信息为：若终端设备为网络切片建立的PDU会话中没有传输第一业务的数据，则接入和移动管理功能网元拒绝终端设备接入所述网络切片。此时，即便接入和移动管理功能网元感知到终端设备没有建立PDU会话，或者终端设备建立的PDU会话中没有激活的用户面，或者终端建立的PDU会话中没有传输第一业务的数据，也会确定N为1，或者确定N为0.5，或者确定N为0.8，等等。
步骤404，接入和移动管理功能网元向网络切片准入控制功能网元发送该数量N。对应的，网络切片准入控制功能网元接收该数量N。
基于上述技术方案，本申请中，使得接入和移动管理功能网元可以根据终端设备的PDU会话状态以及网络切片的属性信息，设置上报本次接入网络切片的终端设备的数量。可以有效避免在终端设备请求接入到网络切片而不建立/激活PDU会话时，占用终端设备接入网络切片的配额，即，提高了网络切片中PDU会话资源的配置和使用效率，提高了用户的业务体验。
并且，本实施例提出了N的取值可以为大于0小于1的数，表示终端设备可以不占用配额或者占用配置相少一些，从而使得更多符合网络切片属性的终端设备接入该网络切片，提高了PDU会话资源的使用效率。
可选的，还包括步骤405，网络切片准入控制功能网元根据该数量N对终端设备进行控制。
例如，如果网络切片准入控制功能网元监控到(或者，网络切片准入控制功能网元也可以基于其他的运营商策略确定)接入该网络切片的终端设备的数目达到了该网络切片允许接入的终端设备的数量的上限，则网络切片准入控制功能网元可以向接入和移动管理功能网元#2(需要说明的是，这里的接入和移动管理功能网元#2可以与步骤402中的接入和移动管理功能网元(记为“接入和移动管理功能网元#1”)相同，也可以不同)发送信息，通知接入和移动管理功能网元，已经达到该网络切片最大注册的终端设备的数量。
具体的，假设接入和移动管理功能网元#1可以为终端设备#1～终端设备#20提供服务，接入和移动管理功能网元#2可以为终端设备#30～终端设备#60提供服务，移动管理功能网元#3可以为终端设备#21～终端设备#29提供服务。假设，该网络切片上目前已经接入了60个终端设备，分别为，终端设备#1～终端设备#60。网络切片准入控制功能网元确定已经达到了该网络切片允许接入的终端设备的数量的上限。在一种可能的实现方式中，网络切片准入控制功能网元可以向接入和移动管理功能网元#2指示拒绝终端设备#49(例如，终端设备#49还没有建立PDU会话)接入该网络切片。在另一种可能的实现方式中，网络切片准入控制功能网元也可以向接入和移动管理功能网元#1通知已经达到该网络切片最大注册终端设备的数量，同时，也可以向接入和移动管理功能网元#1指示拒绝终端设备#10(例如，终端设备#10建立了PDU会话但还没有激活的用户面)接入该网络切片。
可选的，还包括步骤406，网络切片准入控制功能网元向接入和移动管理功能网元发送触发接入和移动管理功能网元拒绝该终端设备接入网络切片的信息。对应的，接入和移动管理功能网元接收该信息。
可选的，还包括步骤407，接入和移动管理功能网元向终端设备发送拒绝该终端设备接入网络切片的信息。对应的，终端设备接收该信息。
可选的，该信息还可以包括拒绝终端设备接入的原因值。
步骤407中关于“原因值”的理解可以参照方法200中步骤207中“原因值”的描述。
可选的，还包括步骤408，终端设备确定被AMF拒绝接入网络切片的原因，并可以建立PDU会话，并重新请求接入该网络切片。
应理解，步骤406～步骤408中的“接入和移动管理功能网元”可以理解为上述步骤405中提到的“接入和移动管理功能网元#1”也可以理解为“接入和移动管理功能网元#2”，不予限定。
图5是本申请提出的一个具体实施例通信方法500，该方法从各个网元交互的角度示出了本申请技术方案的，方法500中以终端设备是UE#2为例，以网络切片为网络切片#2为例进行说明，该方法500包括：
步骤501，UE#2请求注册到网络切片#2，并获取S-NSSAI#2。
具体的，步骤501的理解可以参见方法300中步骤301中的描述。
可选的，还包括步骤502，AMF向NSACF上报本次接入网络切片#2的UE的数量的信息。对应的NSACF接收该信息。
例如，AMF可以向初次先向NSACF上报本次接入网络切片#2的UE的数量M，例如AMF可先直接上报M为1。或者，如果AMF不向NSACF上报，则表明本次接入网络切片#2的UE数量为0。
如果步骤501中，UE#2在请求注册到网络切片#2中时携带了follow on指示(终端设备将要建立PDU会话的指示信息)，即便UE#2的PDU会话状态不符合网络切片#3的属性，则AMF也可以根据该指示信息确定M大于0。
步骤503，NSACF向AMF发送网络切片#2的属性信息。对应的，AMF接收网络切片#2的属性信息。
具体的。步骤503中的“属性信息”的理解可以参见方法400中步骤401“属性信息”的描述。
需要说明的是，本实施例中，步骤502和步骤503之间可以没有先后顺序的限制。
步骤504，AMF根据网络切片#2的属性信息和UE#2的PDU会话状态，确定本次接入网络切片#2的UE的数量N。
应理解，如果执行了502，此时步骤504可以理解为，AMF可以根据网络切片#2的属性信息和UE#2的PDU会话状态，再次更新本次接入网络切片#2的UE的数量。进一步的，如果步骤504中AMF确定的N和步骤502中AMF初次确定的M的值不相同时，后续AMF会再次向NSACF发送接入网络切片#2的UE的数量。
在一种可能的实现方式中，例如，AMF可以感知UE#2是否建立了PDU会话，或者AMF可以向SMF订阅PDU会话中是否传输数据，或者AMF可以向SMF或者PCF订阅业务#2的开始事件和结束事件。
具体的，步骤504中AMF确定本次接入网络切片#2的UE的数量N的实现方式可以参见方法400中步骤402的描述。
步骤505，AMF向NSACF发送本次接入网络切片#2的UE的数量N。对应的NSACF接收本次接入网络切片#2的UE的数量N。
在一种可能的实现方式中，如果步骤501中AMF向NSACF上报的M与步骤504中 AMF确定的本次接入网络切片#2的UE的数量N不相等，则AMF可以对本次接入网络切片#2的UE的数量进行更新。
步骤506，NSACF根据该数量N对终端设备进行控制。
具体的，步骤506可以参照方法400中步骤405的描述。
可选的，该方法还可以包括：AMF可以拒绝UE#2接入网络切片#2，并向UE#2发送拒绝接入网络切片#2的原因值。具体的可以参照方法400中的步骤406～步骤408。
基于上述技术方案，本申请中，使得AMF可以根据PDU会话状态以及网络切片#2的属性信息，设置上报本次接入网络切片#2的UE的数量。可以有效避免在UE请求接入到网络切片#2而不建立/激活PDU会话时，占用UE接入网络切片#2的配额，即，提高了网络切片#2中PDU会话资源的配置和使用效率，提高了用户的业务体验。
需要说明的是，上述网络切片准入控制功能网元都可以理解为，管理终端设备的网络切片准入控制功能网元。
图6是本申请提供的一种通信方法600的示意性框图，该方法包括：
步骤601，管理终端设备的网络切片准入控制功能网元获取终端设备的PDU会话状态。
在一种可能的实现方式中，管理终端设备的网络切片准入控制功能网元可以从接入和移动管理功能网元获取所述终端设备的PDU会话状态。
在另一种可能的实现方式中，管理终端设备的网络切片准入控制功能网元通过接入和移动管理功能网元从会话管理功能网元获取该终端设备的PDU会话状态。例如，接入和移动管理功能网元可以向SMF订阅各个网络切片对应的PDU会话的状态(可选的，还可以获取该网络切片上某个终端设备对应的PDU会话的状态。例如，网络切片#4上SUPI#7对应的UE#7的PDU会话的状态)。关于订阅过程的描述具体可以参见方法700中的步骤703a相关的描述。
在又一种可能的实现方式中，管理终端设备的网络切片准入控制功能网元可以从网络开放功能网元获取终该端设备的PDU会话状态。
在另一种可能的实现方式，管理终端设备的网络切片准入控制功能网元(记为，第一网络切片准入控制功能网元)可以获取管理PDU会话的网络切片准入控制功能网元(记为，第二网络切片准入控制功能网元)的地址信息，并通过该第二网络切片准入控制功能网元获取PDU会话的状态。例如，管理PDU会话的网络切片准入控制功能网元可以向SMF订阅各个S-NSSAI对应的PDU会话的状态(可选的，还可以获取该网络切片上某个终端设备对应的PDU会话的状态。例如，网络切片#5上SUPI#10对应的UE#10的PDU会话的状态)。
在一种可能的实现方式中，管理终端设备网络切片准入控制功能网元还可以从网络数据分析功能网元获取该端设备的PDU会话状态。
例如，管理终端设备网络切片准入控制功能网元可以从网络数据分析功能网元获取以下至少一项信息：切片负载级别(slice load level)信息，，业务体验(Observed Service Experience)信息，，分布分析(Dispersion Analytics)信息，等等中的至少一项，具体可以参考TS 23.288对应章节。
又例如，网络数据分析功能网元可以获取各个网络切片对应的PDU会话的状态(可 选的，还可以获取该网络切片上某个终端设备对应的PDU会话的状态。例如，网络切片#5上SUPI#10对应的UE#10的PDU会话的状态)。此时，管理终端设备的网络切片准入控制功能网元可以直接从网络数据分析功能网元获取各个SUPI对应的终端设备的PDU会话状态。
再例如，网络数据分析功能网元可以向管理PDU会话的网络切片准入控制功能网元(或者向会话管理网元；或者向操作、管理和维护(operation,administration and maintenance，OAM)发送的信息中包括以下信息中至少一项：网络切片的标识(例如，S-NSSAI)信息，终端设备的SUPI信息，业务标识(Application ID)信息、业务数据流模板(service data flow template)信息，等等，从而可以使得网络切片准入控制功能网元获取该终端设备的PDU会话状态。
需要说明的是，网络切片准入控制功能网元上可以配置有网络切片的属性信息。该属性信息可以参照方法400中步骤401中对属性信息的说明。
步骤602，管理终端设备的网络切片准入控制功能网元根据该终端设备的PDU会话状态和/或该网络切片的属性信息，确定是否触发接入和移动管理功能网元拒绝该终端设备接入该网络切片。
在一种可能的实现方式中，例如，如果该终端设备的PDU会话状态不满足网络切片的属性，则管理终端设备的网络切片准入控制功能网元确定触发接入和移动管理功能网元拒绝该终端设备接入该网络切片。此时，网络切片准入控制功能网元可以通知接入和移动管理控制功能网元“已达到网络切片最大注册的终端设备的数量”。又例如，如果该终端设备的PDU会话状态满足网络切片的属性，则管理终端设备的网络切片准入控制功能网元确定不触发接入和移动管理功能网元拒绝该终端设备接入该网络切片。
在一种可能的实现方式中，管理终端设备的网络切片准入控制功能网元可以根据接入终端设备的PDU会话状态更新网络切片上允许注册的终端设备的数量的阈值。例如，没有建立PDU会话的终端设备或没激活用户面的终端设备太多时，网络切片准入控制功能网元可以增加该网络切片上允许注册的终端设备的数量的阈值(例如，增加网络切片上允许注册的终端设备的数量为没有建立PDU会话的终端设备的数量或没有激活用户面的终端设备数量的30％等)。或者，在这种情况下，管理终端设备的网络切片准入控制功能网元可以不改变阈值，但允许接入的终端设备的数量超过网络切片上原来配置的允许注册的终端设备的数量的阈值。(例如，最多可以超过没有建立PDU会话的终端设备的数量或没有激活用户面的终端设备的数量的30％等)。进一步的，如果实际实际注册的终端设备的数量已经超过更新后的阈值，此时网络切片准入控制功能网元可以通知接入和移动管理控制功能网元“已达到网络切片最大注册的终端设备的数量”。此时，也可以理解为，管理终端设备的网络切片准入控制功能网元可以只根据该终端设备的PDU会话状态，确定是否触发接入和移动管理功能网元拒绝该终端设备接入该网络切片。
具体的，如果接入和移动管理控制功能网元请求增加在S-NSSAI上注册的终端设备的数量，并且当前已经达到该网络切片允许注册的最大终端设备的数量。此时，管理终端设备的网络切片准入控制功能网元可以重新设置该网络切片上允许注册的最大终端设备的数量。例如，管理终端设备的网络切片准入控制功能网元可以检查PDU会话状态(如可以是接入和移动管理控制功能网元上报的)，并且可以根据上报的各个终端设备的PDU 会话状态，将网络切片上允许注册的终端设备的数量增加到没有建立PDU会话的终端设备的数量或没有激活用户面的终端设备数量的30％。又例如，管理终端设备的网络切片准入控制功能网元可以维护一个计数器，用于记录实际注册用户数超过该网络切片允许注册的最大终端设备的数量。如果管理终端设备的网络切片准入控制功能网元根据该计数器(或者基于运营商策略)发现，实际注册的终端设备的数量超过该网络切片允许注册的最大终端设备的数量，已经达到没有建立PDU会话的终端设备的数量或没有激活用户面的终端设备数量的阈值，例如，30％，此时，管理终端设备的网络切片准入控制功能网元可以判断是否向接入和移动管理控制功能网元通知“已达到网络切片最大注册的终端设备的数量”。
在另一种可能的实现方式中，管理终端设备的网络切片准入控制功能网元可以接收来自接入和移动管理功能网元的该终端设备将要建立PDU会话的指示信息。此时，在该终端设备的PDU的会话状态不满足该网络切片的属性的情况下，该管理终端设备的网络切片准入控制功能网元根据该指示信息确定不触发接入和移动管理功能网元拒绝所述终端设备接入所述网络切片。
可选的，该方法还包括步骤：接入和移动管理功能网元拒绝该终端设备接入该网络切片，并向终端设备发送拒绝接入的原因值。具体的可以参照方法400中的步骤406～步骤408进行理解。
基于上述技术方案，本申请中，使得网络切片准入控制功能网元可以根据获取的PDU会话状态，并且确定终端设备的PDU会话状态不满足网络切片的属性时，可以拒绝终端设备接入网络切片。从而保证不会有终端设备长时间注册而不建立/激活PDU会话，提高了网络切片中，PDU会话资源的使用效率，提高了用户设备的业务体验。
图7是本申请提出的一个具体实施例通信方法700，该方法从各个网元交互的角度示出了本申请技术方案的，方法700中以终端设备是UE#3为例，以网络切片为网络切片#3为例进行说明，该方法700包括：
步骤701，UE#3请求注册到网络切片#3，并获取S-NSSAI#3。
具体的，步骤701的理解可以参见方法300中步骤301中的描述。
步骤702，AMF向管理终端设备的NSACF(即，第一NSACF)上报本次接入网络切片#3的UE的数量的信息。对应的，该NSACF接收该信息。
可选的，AMF可以在NSACF订阅终端设备的PDU会话状态之后进行再上报终端设备的PDU会话状态。
方式1：
步骤703a，管理终端设备的NSACF向AMF发送订阅请求信息，用于订阅UE#3的PDU会话状态的信息。对应的，AMF接收该信息。
例如，NSACF可以向AMF发送订阅请求信息，订阅PDU会话状态。例如。NSACF可以向AMF订阅是否有PDU会话建立；或者，NSACF可以向SMF订阅是否有激活的用户面；或者，NSACF可以向SMF或PCF订阅业务#3的开始事件和结束事件。
具体的，例如，管理终端设备的NSACF向AMF发送订阅请求信息，如果该信息如果是订阅UE#3是否建立了PDU会话，此时该信息中可以包括UE#3的标识；如果该信息如果是订阅UE#3在建立的PDU会话中，是否有激活的用户面，此时该信息中可以包括 UE#3的PDU会话的标识；如果该信息是订阅UE#3在建立的PDU会话中，是否有传输第一业务的数据，此时该信息中可以包括UE#3的第一业务的标识。
进一步的，考虑到终端设备移动性，如果终端设备在移动过程中，为其提供服务的AMF发生变化(例如，原始AMF记为AMF#1，终端设备移动后为其提供服务的新的AMF记为AMF#2)。此时，在一种可能的实现方式中，AMF#1可以将终端设备的PDU会话状态的上下文信息发送给AMF#2，从而避免载终端设备PDU会话状态未发生变化的情况下AMF#2重复向NSACF上报PDU会话状态。在另一种可能的实现方式中，可以预定义，只要为该终端设备提供服务的AMF发生变化，就需要重新再次向NSACF上报该终端设备的PDU会话状态。
如果AMF没有上报该S-NSSAI的所有服务的UE的PDU会话状态，但是NSACF基于配置需要使用上述信息，此时NSACF可以向AMF订阅该S-NSSAI的所有服务的UE的PDU会话状态(如果之前没有订阅的话)。
应理解，上述技术方案也可以理解为，管理终端设备的NSACF向AMF发送订阅请求信息，用于订阅该AMF上所服务的所有终端设备的PDU状态。此时该信息中，只需包含AMF的标识信息即可。该场景中，AMF每次上报的均是其服务的所有终端设备的PDU会话状态，可以减少核心网网元之间的信令交互。
方式2：
步骤703b，管理终端设备的NSACF向AMF发送订阅请求信息，用于订阅管理PDU会话的NSACF(即，第二NSACF)的地址信息。对应的，AMF接收该信息。
步骤703b中“订阅”的流程可以理解为，在订阅之前可能管理PDU会话的NSACF可能还不存在，因此可以先订阅。例如，在步骤703b后，UE#3可以建立PDU会话。
步骤703c，AMF向SMF发送订阅管理PDU会话的NSACF的地址的信息。对应的，SMF接收该信息。
步骤703d，SMF向AMF发送管理PDU会话的NSACF的地址的信息。对应的，AMF接收该信息。
步骤703e，AMF向管理终端设备的NSACF发送管理PDU会话的NSACF的地址的信息。对应的，管理终端设备的NSACF接收该信息。
步骤703f，管理终端设备的NSAC根据该地址信息向管理PDU会话的NSACF发送订阅UE#3的PDU会话状态的信息。对应的，管理PDU会话的NSACF接收该信息。
步骤703g，管理PDU会话的NSACF向管理终端设备的NSACF发送UE#3的PDU会话的状态信息。对应的，管理终端设备的NSACF接收该信息。
步骤704，管理终端设备的NSACF根据该UE#3的PDU会话状态和/或该网络切片的属性信息，确定是否触发AMF拒绝UE#3接入该网络切片#3。
在一种可能的实现方式中，如果UE#3的PDU会话状态不满足网络切片#3的属性，则NSACF确定触发AMF拒绝UE#3接入该网络切片#3。
可选的，该方法还包括：即AMF拒绝该UE#3接入该网络切片#3，并UE#3发送拒绝接入的原因值。具体的可以参照方法400中的步骤406～步骤408进行理解。
在另一种可能的实现方式中，如果步骤701中，UE#3在请求注册到网络切片#3中时携带了follow on指示(终端设备将要建立PDU会话的指示信息)，即便UE#3当前的 PDU会话不符合网络切片#3的属性，则AMF可以根据该指示信息确定，不触发AMF拒绝UE#3接入该网络切片#3。
基于上述技术方案，本申请中，使得NSACF可以根据获取的PDU会话状态，并且确定UE#3的PDU会话状态不满足网络切片#3的属性时，可以拒绝UE#3接入网络切片#3。从而保证不会有终端设备长时间注册而不建立/激活PDU会话，提高了网络切片#中，PDU会话资源的使用效率，提高了用户设备的业务体验。
可以理解，本申请实施例中的图2至图7中的例子仅仅是为了便于本领域技术人员理解本申请实施例，并非要将本申请实施例限于例示的具体场景。本领域技术人员根据图2至图7的例子，显然可以进行各种等价的修改或变化，这样的修改或变化也落入本申请实施例的范围内。
还可以理解，本申请的各实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，也可以在某些场景下，与其他特征进行结合，不作限定。
还可以理解，本申请中描述的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。并且实施例中出现的各个术语的解释或说明可以在各个实施例中互相参考或解释，对此不作限定。
还可以理解，在本申请的各实施例中的各种数字序号的大小并不意味着执行顺序的先后，仅为描述方便进行的区分，不应对本申请实施例的实施过程构成任何限定。例如，方法500中，步骤502可以与步骤503可以没有先后顺序的限制。即，可以先执行步骤502也可以先执行步骤503。
应该理解，本申请中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
可以理解，在本申请中，“在…情况下”、“若”以及“如果”均指在某种客观情况下装置会做出相应的处理，并非是限定时间，且也不要求装置实现时一定要有判断的动作，也不意味着存在其它限定。
可以理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
上述主要从各个节点之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个节点，例如接入和移动管理功能网元、终端设备以及网络切片准入控制功能网元，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对接入和移动管理功能网元以及涉及的各个核心网网元进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分 是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
图8是本申请实施例提供的通信装置100的示意性框图。如图所示，该装置100可以包括：收发单元110和处理单元120。
在一种可能的设计中，该装置100可以是上文方法实施例中的接入和移动管理功能网元，也可以是用于实现上文方法实施例中接入和移动管理功能网元的功能的芯片。应理解，该装置100可对应于根据本申请实施例的方法200～方法700中的接入和移动管理功能网元，该装置100可以执行本申请实施例的方法200～方法700中的接入和移动管理功能网元所对应的步骤。
在一种实现方式中，处理单元用于确定第一时间；在第一时间超时后，若终端设备的协议数据单元PDU的会话状态不满足网络切片的第一条件，则处理单元用于拒绝所述终端设备接入网络切片。
在一种实现方式中，所述处理单元用于获取指示第一时间的信息。
在一种实现方式中，所述处理单元用于获取网络切片的属性信息，所述处理单元用于根据属性信息确定所述第一条件。
在一种实现方式中，在所述处理单元拒绝终端设备接入网络切片之前，所述收发单元用于向终端设备发送第一时间。
在一种实现方式中，所述收发单元用于向终端设备发送接入和移动管理功能网元拒绝终端设备接入所述网络切片的原因值。
在一种实现方式中，所述收发单元用于接收来自终端设备的终端设备将要建立PDU会话的指示信息；所述处理单元用于根据指示信息确定第一时间。
在一种实现方式中，所述处理单元用于指示所述收发单元向会话管理功能网元或者策略控制管理网元订阅所述第一业务的开始事件。
在一种可能的实现方式中，所述处理单元还用于确定网络切片的属性信息；所述处理单元用于根据网络切片的属性信息和终端设备的协议数据单元PDU会话状态，确定本次接入网络切片的终端设备的数量N，所述N大于或者等于0，并且小于或者等于1；所述收发单元用于向网络切片准入控制功能网元发送所述数量N。
在一种可能的实现方式中，所述处理单元用于根据网络切片的属性信息和终端设备的PDU会话状态，确定接入网络切片的终端设备的数量N，包括：如果所述处理单元确定终端设备的PDU会话状态不符合所述网络切片的属性，所述处理单元确定所述N小于1。
在一种可能的实现方式中，所述收发单元用于接收来自终端设备的终端设备将要建立PDU会话的指示信息；所述处理单元用于根据网络切片的属性信息和终端设备的PDU会话状态，确定接入网络切片的终端设备的数量N，包括：所述处理单元用于根据网络切片的属性信息、终端设备的PDU会话状态以及指示信息，确定所述N大于0。
在一种可能的设计中，该装置100可以是上文方法实施例中的网络切片准入控制功能网元，也可以是用于实现上文方法实施例中网络切片准入控制功能网元的功能的芯片。应理解，该装置100可对应于根据本申请实施例的方法200～方法700中的网络切片准入控制功能网元，该装置100可以执行本申请实施例的方法200～方法700中的网络切片准入控制功能网元所对应的步骤。
在一种可能的实现方式中，所述处理单元用于获取终端设备的协议数据单元PDU会话状态，其中，所述装上配置有网络切片的属性信息；所述处理单元用于根据所述终端设备的PDU会话状态和网络切片的属性信息，确定是否触发接入和移动管理功能网元拒绝终端设备接入所述网络切片。
在一种可能的实现方式中，所述处理单元用于获取终端设备的PDU会话状态，包括：所述处理单元用于从接入和移动管理功能网元获取终端设备的PDU会话状态；或者，所述处理单元通过接入和移动管理功能网元从会话管理功能网元获取终端设备的PDU会话状态；或者，所述处理单元用于从网络开放功能网元获取所述终端设备的PDU会话状态。
在一种可能的实现方式中，所述处理单元为第一处理单元，所述处理单元用于获取终端设备的PDU会话状态，包括：所述第一处理单元用于获取第二处理单元的地址信息，其中，所述第一处理单元用于管理所述终端设备的数量，所述第二处理单元用于管理所述PDU会话的数量；所述第一处理单元用于根据所述第二处理单元的地址信息指示收发单元，向所述第二处理单元网元请求获取终端设备的PDU会话状态；所述收发单元用于接收来自所述第二处理单元的所述终端设备的PDU会话状态。
在一种可能的实现方式中，所述第一处理单元用于获取第二处理单元的地址信息，包括：所述收发单元用于向接入和移动管理功能网元请求或订阅所述第二处理单元的地址信息；所述收发单元用于接收来自所述接入和移动管理功能网元的所述第二处理单元的地址信息。
在一种可能的实现方式中，所述处理单元用于根据终端设备的PDU会话状态和网络切片的属性信息，确定是否触发接入和移动管理功能网元拒绝终端设备接入网络切片，包括：在终端设备的PDU会话状态不满足网络切片的属性的情况下，所述处理单元用于确定触发移动管理功能网元拒绝终端设备接入网络切片。
在一种可能的实现方式中，所述收发单元用于接收来自接入和移动管理功能网元的终端设备将要建立所述PDU会话的指示信息；所述处理单元用于根据终端设备的PDU会话状态以及网络切片的属性信息，确定是否触发接入和移动管理功能网元拒绝终端设备接入网络切片，包括：在终端设备的PDU的会话状态不满足网络切片的属性的情况下，所述处理单元用于根据所述指示信息确定不触发移动管理功能网元拒绝终端设备接入网络切片。
在一种可能的设计中，该装置100可以是上文方法实施例中的终端备，也可以是用于实现上文方法实施例中终端设备的功能的芯片。应理解，该装置100可对应于根据本申请实施例的方法200～方法700中的终端设备，该装置100可以执行本申请实施例的方法200～方法700中的终端设备所对应的步骤。
在一种可能的实现方式中，所述收发单元用于向接入和移动管理功能网元发送所述装置请求接入网络切片的信息；所述收发单元用于接收来自所述接入和移动管理功能网元的第一时间；在所述第一时间超时后，若所述装置的协议数据单元PDU的会话状态不满足第一条件，则所述收发单元用于从所述移动管理功能网元接收拒绝接入网络切片的信息。
在一种可能的实现方式中，所述收发单元用于向接入和移动管理功能网元发送所述装置将要建立PDU会话的指示信息，指示信息用于接入和移动管理功能网元确定第一时间。
在一种可能的实现方式中，所述收发单元用于向接入和移动管理功能网元发送所述装 置请求接入的网络切片的信息；所述收发单元用于向接入和移动管理功能网元发送所述装置将要为网络切片建立PDU会话的指示信息；其中，所述指示信息用于接入和移动管理功能网元确定接入网络切片的终端设备的数量N，其中，N大于0；或者，指示信息用于网络切片准入控制功能网元确定不触发所述移动管理功能网元拒绝所述装置接入所述网络切片。
还应理解，这里的装置100以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，装置100可以具体为上述实施例中的第一终端设备，可以用于执行上述各方法实施例中与第一终端设备对应的各个流程和/或步骤，或者，装置100可以具体为上述实施例中的第二终端设备，可以用于执行上述各方法实施例中与第二终端设备对应的各个流程和/或步骤，为避免重复，在此不再赘述。
上述各个方案的装置100具有实现上述方法中无线接入网设备所执行的相应步骤的功能，或者，上述各个方案的装置100具有实现上述方法中接入和移动管理功能网元、终端设备、网络切片准入控制功能网元所执行的相应步骤的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块；例如收发单元可以由收发机替代(例如，收发单元中的发送单元可以由发送机替代，收发单元中的接收单元可以由接收机替代)，其它单元，如处理单元等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
此外，上述收发单元110还可以是收发电路(例如可以包括接收电路和发送电路)，处理单元可以是处理电路。
需要指出的是，图8中的装置可以是前述实施例中的网元或设备，也可以是芯片或者芯片系统，例如：片上系统(system on chip，SoC)。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。在此不做限定。
图9是本申请实施例提供的通信装置200的示意性框图。如图所示，该装置200包括：至少一个处理器220。该处理器220与存储器耦合，用于执行存储器中存储的指令，以发送信号和/或接收信号。可选地，该设备200还包括存储器230，用于存储指令。可选的，该设备200还包括收发器210，处理器220控制收发器210发送信号和/或接收信号。
应理解，上述处理器220和存储器230可以合成一个处理设备，处理器220用于执行存储器230中存储的程序代码来实现上述功能。具体实现时，该存储器230也可以集成在处理器220中，或者独立于处理器220。
还应理解，收发器210可以包括收发器(或者称，接收机)和发射器(或者称，发射机)。收发器还可以进一步包括天线，天线的数量可以为一个或多个。收发器210有可以是通信接口或者接口电路。
具体地，该设备200中的收发器210可以对应于设备100中的收发单元110，该设备200中的处理器220可对应于设备200中的处理单元120。
作为一种方案，该装置200用于实现上文各个方法实施例中由无线接入网设备执 行的操作。
例如，处理器220用于执行存储器230存储的计算机程序或指令，以实现上文各个方法实施例中接入和移动管理功能网元的相关操作。例如，图2至图7中任意一个所示实施例中的接入和移动管理功能网元的执行的方法。
作为一种方案，该装置200用于实现上文各个方法实施例中由终端设备执行的操作。
例如，处理器220用于执行存储器230存储的计算机程序或指令，以实现上文各个方法实施例中终端设备的相关操作。例如，图2至图7中任意一个所示实施例中的终端设备的执行的方法。
作为一种方案，该装置200用于实现上文各个方法实施例中由网络切片准入控制功能网元执行的操作。
例如，处理器220用于执行存储器230存储的计算机程序或指令，以实现上文各个方法实施例中网络切片准入控制功能网元的相关操作。例如，图2至图7中任意一个所示实施例中的网络切片准入控制功能网元的执行的方法。
应理解，各收发器、处理器执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application-specific integrated circuit，ASIC)、现场可编程门阵列(field-programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)， 其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch-link DRAM，SLDRAM)和直接内存总线随机存取存储器(direct ram-bus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品上存储有计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行方法200～方法700实施例中任意一个实施例中由接入和移动管理功能网元执行的方法。
例如，该计算机程序代码被计算机执行时，使得该计算机可以实现上述方法200～方法700实施例中由终端设备执行的方法。
又例如，该计算机程序代码被计算机执行时，使得该计算机可以实现上述方法200～方法700实施例中由网络切片准入控制功能网元执行的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行上述实施例中由接入和移动管理功能网元、终端设备、网络切片准入控制功能网元执行的方法。
根据本申请实施例提供的方法，本申请还提供一种通信系统，包括接入和移动管理功能网元和终端设备，所述接入和移动管理功能网元，用于执行方法200～700中实施例中的任意一个实施例中接入和移动管理功能网元所执行的方法，所述终端设备用于执行方法200～700中实施例中的任意一个实施例中终端设备所执行的方法。
可选的，所述通信系统还可以包括网络切片准入控制功能网元，所述网络切片准入控制功能网元，用于执行方法200～700中实施例中的任意一个实施例中网络切片准入控制功能网元所执行的方法。
根据本申请实施例提供的方法，本申请还提供一种通信系统，包括网络切片准入控制功能网元和终端设备，所述网络切片准入控制功能网元，用于执行方法200～700中中实施例中的任意一个实施例中网络切片准入控制功能网元所执行的方法，所述终端设备用于执行方法200～700中实施例中的任意一个实施例中终端设备所执行的方法。
可选的，所述通信系统中还可以包括接入和移动管理功能网元，所述接入和移动管理功能网元，用于执行方法200～700中实施例中的任意一个实施例中接入和移动管理功能网元所执行的方法。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程设备。所述计算机指令可以存储在计算机可读存储介质 中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
上述各个装置实施例中，由相应的模块或单元执行相应的步骤，例如收发单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在2个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所述领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、设备和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、设备和方法，可以通过其它的方式实现。例如，以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以 是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准

Claims (26)

  1. 一种通信方法，其特征在于，包括：
    接入和移动管理功能网元确定第一时间；
    在所述第一时间超时后，若终端设备的协议数据单元PDU的会话状态不满足网络切片的第一条件，则所述接入和移动管理功能网元拒绝所述终端设备接入网络切片，其中，所述第一条件包括以下至少一项：
    所述终端设备为所述网络切片建立PDU会话；或者，
    所述终端设备为所述网络切片建立的PDU会话中有激活的用户面；或者，
    所述终端设备为所述网络切片建立的PDU会话中有传输第一业务的数据。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：所述接入和移动管理功能网元获取指示所述第一时间的信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述接入和移动管理功能网元获取所述网络切片的属性信息，
    所述接入和移动管理功能网元根据所述属性信息确定所述第一条件。
  4. 根据权利要求3所述的方法，其特征在于，所述属性信息包括以下至少一项：
    在所述第一时间超时后，若所述终端设备没有为所述网络切片建立PDU会话，则所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片；或者，
    在所述第一时间超时后，若所述终端设备为所述网络切片建立的PDU会话中没有激活的用户面，则所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片；或者，
    在所述第一时间超时后，若所述终端设备为所述网络切片建立的PDU会话中没有传输第一业务的数据，则所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    在所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片之前，所述接入和移动管理功能网元向所述终端设备发送所述第一时间。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：所述接入和移动管理功能网元向所述终端设备发送所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片的原因值，其中，所述原因值包括以下至少一项：
    所述终端设备没有为所述网络切片建立PDU会话；或者，
    所述终端设备为所述网络切片建立的PDU会话中没有激活的用户面；或者，
    所述终端设备为所述网络切片建立的PDU会话中没有传输第一业务的数据。
  7. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：所述接入和移动管理功能网元接收来自所述终端设备的所述终端设备将要建立PDU会话的指示信息；
    所述接入和移动管理功能网元根据所述指示信息确定所述第一时间。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入和移动管理功能网元向会话管理功能网元或者策略控制管理网元订阅所述 第一业务的开始事件。
  9. 一种通信方法，其特征在于，包括：
    终端设备向接入和移动管理功能网元发送请求接入网络切片的信息；
    所述终端设备接收来自所述接入和移动管理功能网元的第一时间；
    在所述第一时间超时后，若所述终端设备的协议数据单元PDU的会话状态不满足第一条件，则所述终端设备从所述移动管理功能网元接收拒绝接入所述网络切片的信息，其中，所述第一条件包括以下至少一项：
    所述终端设备为所述网络切片建立PDU会话；或者，
    所述终端设备为所述网络切片建立的PDU会话中有激活的用户面；或者，
    所述终端设备为所述网络切片建立的PDU会话中有传输第一业务的数据。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述接入和移动管理功能网元发送所述终端设备将要建立PDU会话的指示信息，所述指示信息用于所述接入和移动管理功能网元确定所述第一时间。
  11. 一种通信方法，其特征在于，包括：
    接入和移动管理功能网元确定网络切片的属性信息；
    所述接入和移动管理功能网元根据所述网络切片的属性信息和所述终端设备的协议数据单元PDU会话状态，确定本次接入所述网络切片的终端设备的数量N，所述N大于或者等于0，并且小于或者等于1；
    所述接入和移动管理功能网元向网络切片准入控制功能网元发送所述数量N；
    其中，所述网络切片的属性信息包括以下至少一项：
    若所述终端设备没有为所述网络切片建立PDU会话，则所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片；或者，
    若所述终端设备为所述网络切片建立的PDU会话中没有激活的用户面，则所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片；或者，
    若所述终端设备为所述网络切片建立的PDU会话中没有传输第一业务的数据，则所述接入和移动管理功能网元拒绝终端设备接入所述网络切片。
  12. 根据权利要求11所述的方法，其特征在于，所述接入和移动管理功能网元根据所述网络切片的属性信息和所述终端设备的PDU会话状态，确定所述接入网络切片的终端设备的数量N，包括：
    如果所述接入和移动管理功能网元确定所述终端设备的PDU会话状态不符合所述网络切片的属性，所述AMF确定所述N小于1。
  13. 根据权利要求11或12所述的方法，其特征在于，所述方法还包括：所述接入和移动管理功能网元接收来自所述终端设备的所述终端设备将要建立所述PDU会话的指示信息；
    所述接入和移动管理功能网元根据所述网络切片的属性信息和所述终端设备的PDU会话状态，确定所述接入网络切片的终端设备的数量N，包括：
    所述接入和移动管理功能网元根据所述网络切片的属性信息、所述终端设备的PDU会话状态以及所述指示信息，确定所述N大于0。
  14. 根据权利要求11至13中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入和移动管理功能网元向会话管理功能网元或者策略控制管理网元订阅所述第一业务的开始事件。
  15. 一种通信方法，其特征在于，包括：
    网络切片准入控制功能网元获取终端设备的协议数据单元PDU会话状态，其中，所述网络切片准入控制功能网元上配置有网络切片的属性信息；
    所述网络切片准入控制功能网元根据所述终端设备的PDU会话状态和/或所述网络切片的属性信息，确定是否触发接入移动管理功能网元拒绝所述终端设备接入所述网络切片；
    其中，所述网络切片的属性信息包括以下至少一项：
    若所述终端设备没有为所述网络切片建立PDU会话，则所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片；或者，
    若所述终端设备为所述网络切片建立的PDU会话中没有激活的用户面，则所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片；或者，
    若所述终端设备为所述网络切片建立的PDU会话中没有传输第一业务的数据，则所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片。
  16. 根据权利要求15所述的方法，其特征在于，所述网络切片准入控制功能网元获取终端设备的PDU会话状态，包括：
    所述网络切片准入控制功能网元从接入和移动管理功能网元获取所述终端设备的PDU会话状态；或者，
    所述网络切片准入控制功能网元通过接入和移动管理功能网元从会话管理功能网元获取所述终端设备的PDU会话状态；或者，
    所述网络切片准入控制功能网元从网络开放功能网元获取所述终端设备的PDU会话状态。
  17. 根据权利要求15所述的方法，其特征在于，所述网络切片准入控制功能网元为第一网络切片准入控制功能网元，所述网络切片准入控制功能网元获取终端设备的PDU会话状态，包括：
    所述第一网络切片准入控制功能网元获取第二网络切片准入控制功能网元的地址信息，其中，所述第一网络切片准入控制功能网元用于管理所述终端设备的数量，所述第二网络切片准入控制功能网元用于管理所述PDU会话的数量；
    所述第一网络切片准入控制功能网元根据所述第二网络切片准入控制功能网元的地址信息，向所述第二网络切片准入控制功能网元请求获取所述终端设备的PDU会话状态；
    所述第一网络切片准入控制功能网元接收来自所述第二网络切片准入控制功能网元的所述终端设备的PDU会话状态。
  18. 根据权利要求17所述的方法，其特征在于，所述第一网络切片准入控制功能网元获取第二网络切片准入控制功能网元的地址信息，包括：
    所述第一网络切片准入控制功能网元向所述接入和移动管理功能网元请求或订阅所述第二网络切片准入控制功能网元的地址信息；
    所述第一网络切片准入控制功能网元接收来自所述接入和移动管理功能网元的所述 第二网络切片准入控制功能网元的地址信息。
  19. 根据权利要求15至18中任一项所述的方法，其特征在于，所述网络切片准入控制功能网元根据所述终端设备的PDU会话状态和所述网络切片的属性信息，确定是否触发接入和移动管理功能网元拒绝所述终端设备接入所述网络切片，包括：
    在所述终端设备的PDU会话状态不满足所述网络切片的属性的情况下，所述网络切片准入控制功能网元确定触发接入和移动管理功能网元拒绝所述终端设备接入所述网络切片。
  20. 根据权利要求15至18中任一项所述的方法，其特征在于，所述方法还包括：所述网络切片准入控制功能网元接收来自所述接入和移动管理功能网元的终端设备将要建立所述PDU会话的指示信息；
    所述网络切片准入控制功能网元根据所述终端设备的PDU会话状态和所述网络切片的属性信息，确定是否触发接入和移动管理功能网元拒绝所述终端设备接入所述网络切片，包括：
    在所述终端设备的PDU的会话状态不满足所述网络切片的属性的情况下，所述网络切片准入控制功能网元根据所述指示信息确定不触发所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片。
  21. 一种通信方法，其特征在于，包括：
    终端设备向接入和移动管理功能网元发送所述终端设备请求接入的网络切片的信息；
    所述终端设备所述向所述接入和移动管理功能网元发送所述终端设备将要为所述网络切片建立PDU会话的指示信息；
    其中，所述指示信息用于所述接入和移动管理功能网元确定所述接入所述网络切片的终端设备的数量N，其中，所述N大于0；或者，所述指示信息用于网络切片准入控制功能网元确定不触发所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片。
  22. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至21中任意一项所述的方法。
  23. 一种计算机程序产品，其特征在于，所述计算机程序产品包括用于执行如权利要求1至21中任一项所述的方法的指令。
  24. 一种通信系统，其特征在于，包括：接入和移动管理功能网元和终端设备，
    所述接入和移动管理功能网元，用于执行如权利要求1至8中任一项所述的方法；
    所述终端设备，用于执行如权利要求如权利要求9至10中任一项所述的方法。
  25. 一种通信系统，其特征在于，包括：接入和移动管理功能网元和终端设备，
    所述接入和移动管理功能网元，用于执行如权利要求11至14中任一项所述的方法；
    所述终端设备，用于向所述接入和移动管理功能网元发送所述终端设备请求接入的网络切片的信息；所述终端设备向所述接入和移动管理功能网元发送所述终端设备将要为所述网络切片建立PDU会话的指示信息；其中，所述指示信息用于所述接入和移动管 理功能网元确定所述接入所述网络切片的终端设备的数量N，其中，所述N大于0。
  26. 一种通信系统，其特征在于，包括：网络切片准入控制功能网元和终端设备，
    所述网络切片准入控制功能网元，用于执行如权利要求15至20中任一项所述的方法；
    所述终端设备，用于向所述接入和移动管理功能网元发送所述终端设备请求接入的网络切片的信息；所述终端设备向所述接入和移动管理功能网元发送所述终端设备将要为所述网络切片建立PDU会话的指示信息；所述指示信息用于网络切片准入控制功能网元确定不触发所述接入和移动管理功能网元拒绝所述终端设备接入所述网络切片。
PCT/CN2023/077195 2022-05-06 2023-02-20 通信方法和装置 WO2023213112A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210488467.XA CN117062189A (zh) 2022-05-06 2022-05-06 通信方法和装置
CN202210488467.X 2022-05-06

Publications (1)

Publication Number Publication Date
WO2023213112A1 true WO2023213112A1 (zh) 2023-11-09

Family

ID=88646216

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/077195 WO2023213112A1 (zh) 2022-05-06 2023-02-20 通信方法和装置

Country Status (2)

Country Link
CN (1) CN117062189A (zh)
WO (1) WO2023213112A1 (zh)

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180324577A1 (en) * 2017-05-08 2018-11-08 Qualcomm Incorporated Mobility between areas with heterogeneous network slices
CN111201811A (zh) * 2017-10-09 2020-05-26 瑞典爱立信有限公司 建立用于无线通信设备的分组数据传送的连接的方法
CN111586772A (zh) * 2019-02-18 2020-08-25 华为技术有限公司 一种通信方法及装置
CN112543486A (zh) * 2019-09-23 2021-03-23 华为技术有限公司 网络切片选择的方法、设备及系统
US20210227392A1 (en) * 2018-10-09 2021-07-22 Huawei Technologies Co., Ltd. Network slice access control method and apparatus
WO2021203947A1 (zh) * 2020-04-10 2021-10-14 华为技术有限公司 一种通信方法及装置
CN113891427A (zh) * 2020-07-01 2022-01-04 华为技术有限公司 通信方法和装置
CN114143903A (zh) * 2021-12-27 2022-03-04 中国电信股份有限公司 一种网络切片pdu会话的配置方法、装置、设备及介质
CN114223235A (zh) * 2019-12-26 2022-03-22 日本电气株式会社 Amf节点及其方法

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180324577A1 (en) * 2017-05-08 2018-11-08 Qualcomm Incorporated Mobility between areas with heterogeneous network slices
CN111201811A (zh) * 2017-10-09 2020-05-26 瑞典爱立信有限公司 建立用于无线通信设备的分组数据传送的连接的方法
US20210227392A1 (en) * 2018-10-09 2021-07-22 Huawei Technologies Co., Ltd. Network slice access control method and apparatus
CN111586772A (zh) * 2019-02-18 2020-08-25 华为技术有限公司 一种通信方法及装置
CN112543486A (zh) * 2019-09-23 2021-03-23 华为技术有限公司 网络切片选择的方法、设备及系统
CN114223235A (zh) * 2019-12-26 2022-03-22 日本电气株式会社 Amf节点及其方法
WO2021203947A1 (zh) * 2020-04-10 2021-10-14 华为技术有限公司 一种通信方法及装置
CN113891427A (zh) * 2020-07-01 2022-01-04 华为技术有限公司 通信方法和装置
CN114143903A (zh) * 2021-12-27 2022-03-04 中国电信股份有限公司 一种网络切片pdu会话的配置方法、装置、设备及介质

Also Published As

Publication number Publication date
CN117062189A (zh) 2023-11-14

Similar Documents

Publication Publication Date Title
KR102692951B1 (ko) 5g 네트워크에서의 로컬 영역 데이터 네트워크(ladn)에 대한 접속들을 관리하는 방법들
JP7118237B2 (ja) 通信方法及び通信装置
US11838747B2 (en) Uplink congestion control based on sip messaging
EP4362512A1 (en) Communication method and apparatus
KR101673831B1 (ko) 무선 통신 시스템에서 디바이스 간 통신 인가 및 데이터 스니핑
WO2023280121A1 (zh) 一种获取边缘服务的方法和装置
US11483801B2 (en) Resource configuration method and apparatus
US20230164591A1 (en) Communication method and apparatus
US20200296575A1 (en) Method and apparatus for determining status of terminal device, and device
US20230035694A1 (en) Service guarantee method and apparatus
WO2019029568A1 (zh) 通信方法、终端设备和网络设备
US11910475B2 (en) Systems and methods for enabling efficient establishment of policy control associations
US20220103482A1 (en) Maximum data burst volume (mdbv) determining method, apparatus, and system
US20230047783A1 (en) Data transmission method and apparatus
WO2023016006A1 (zh) 一种通信控制方法和通信设备
WO2023213177A1 (zh) 一种通信方法及装置
US20220338100A1 (en) Communication Method and Communication Apparatus
WO2022237778A1 (zh) 异常检测的方法、通信装置及通信系统
WO2023213112A1 (zh) 通信方法和装置
JP2024503095A (ja) アプリケーション関連機能のためのリソース割り当てステータスサブスクリプション
WO2024001897A1 (zh) 通信方法和装置
US20240155325A1 (en) Information obtaining method and apparatus, and system
US20240291849A1 (en) Method for obtaining security classification result and communication apparatus
WO2022174780A1 (zh) DDoS攻击检测的方法和装置
WO2024001765A1 (zh) 一种通信方法及装置

Legal Events

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

Ref document number: 23799102

Country of ref document: EP

Kind code of ref document: A1