WO2023133838A1 - 确定注册用户数量的方法、装置、通信设备及存储介质 - Google Patents

确定注册用户数量的方法、装置、通信设备及存储介质 Download PDF

Info

Publication number
WO2023133838A1
WO2023133838A1 PCT/CN2022/072120 CN2022072120W WO2023133838A1 WO 2023133838 A1 WO2023133838 A1 WO 2023133838A1 CN 2022072120 W CN2022072120 W CN 2022072120W WO 2023133838 A1 WO2023133838 A1 WO 2023133838A1
Authority
WO
WIPO (PCT)
Prior art keywords
access
slice
network
registered users
access type
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2022/072120
Other languages
English (en)
French (fr)
Inventor
沈洋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
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 Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to CN202280000182.5A priority Critical patent/CN116803111A/zh
Priority to US18/728,007 priority patent/US20250113285A1/en
Priority to PCT/CN2022/072120 priority patent/WO2023133838A1/zh
Priority to EP22919488.1A priority patent/EP4465669A4/en
Publication of WO2023133838A1 publication Critical patent/WO2023133838A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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
    • H04W48/06—Access restriction performed under specific conditions based on traffic conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/084—Load balancing or load distribution among network function virtualisation [NFV] entities; among edge computing entities, e.g. multi-access edge computing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies

Definitions

  • the present disclosure relates to but not limited to the technical field of wireless communication, and in particular relates to a method, device, communication device and storage medium for determining the number of registered users.
  • Network slicing can provide complete network functions, such as radio access network functions, core network functions, and Internet Protocol (IP, Internet Protocol) multimedia system functions.
  • a network can support one or more network slices. Network slices can provide different committed services and be dedicated to users.
  • network slices include registered users of multiple access types. Statistics of all access types will be performed in the network slice. This statistical method cannot accurately locate and meet the needs of operational services, especially the requirements of service characteristics in specific scenarios, and it is impossible to configure resources accordingly according to the network status. Trigger and execute related services, and even improve user service experience.
  • the embodiment of the present disclosure discloses a method, a device, a communication device and a storage medium for determining the number of registered users.
  • a method for determining the number of registered users is provided, wherein the method is performed by a first network device, and the method includes:
  • the access type information indicates an access type for the terminal to access the network slice.
  • the access type information includes at least one of the following:
  • Access type information obtained from consumer network capabilities
  • Access type information configured by the operation and maintenance management system OAM
  • Access type information obtained from the Access and Mobility Management Function AMF.
  • the access type information indicates at least one of the following:
  • Access auxiliary information addAccessInfo addAccessInfo
  • the access type includes at least one of the following:
  • the wireless access type includes at least one of the following: new air interface access NR, evolved universal mobile communication system terrestrial radio access EUTRA, wireless local area network access WLAN, virtual network access VIRTUAL, narrowband IoT access to NBIOT, wired network access to WIRELINE, wired and cable network access to WIRELINE_CABLE, wired broadband network access to WIRELINE_BBF, urban rail transit vehicle-ground integrated communication system access to LTE-M, new air interface unlicensed spectrum access to NR_U, evolution Universal Mobile Telecommunications System Terrestrial Unlicensed Spectrum Wireless Access EUTRA_U, Trusted N3GA Access TRUSTED_N3GA, Trusted Wireless Local Area Network Access TRUSTED_WLAN, Universal Terrestrial Radio Access UTRA, Global System for Mobile Communications Edge Radio Access Network GERA, NR_LEO for low orbit, NR_MEO for medium and high orbit, NR_GEO for geostationary earth orbit and NR_OTHER_SAT for other satellites.
  • new air interface access NR evolved universal mobile communication system terrestrial radio access EUTRA
  • the method also includes:
  • the predetermined process includes one of the following:
  • the updating the number of registered users for different access types in response to the terminal executing a predetermined process includes:
  • the slice user quantity update request message indicates: increase or decrease the registered user quantity.
  • the method also includes:
  • the response message carries information that the number of registered users of the access type reaches a predetermined threshold and/or the number of registered users associated with the access type.
  • the method also includes:
  • a method for determining the number of registered users is provided, wherein the method is performed by a second network device, and the method includes:
  • the access type includes at least one of the following:
  • the wireless access type includes at least one of the following: new air interface access NR, evolved universal mobile communication system terrestrial radio access EUTRA, wireless local area network access WLAN, virtual network access VIRTUAL, narrowband IoT access to NBIOT, wired network access to WIRELINE, wired and cable network access to WIRELINE_CABLE, wired broadband network access to WIRELINE_BBF, urban rail transit vehicle-ground integrated communication system access to LTE-M, new air interface unlicensed spectrum access to NR_U, evolution Universal Mobile Telecommunications System Terrestrial Unlicensed Spectrum Wireless Access EUTRA_U, Trusted N3GA Access TRUSTED_N3GA, Trusted Wireless Local Area Network Access TRUSTED_WLAN, Universal Terrestrial Radio Access UTRA, Global System for Mobile Communications Edge Radio Access Network GERA, NR_LEO for low orbit, NR_MEO for medium and high orbit, NR_GEO for geostationary earth orbit and NR_OTHER_SAT for other satellites.
  • new air interface access NR evolved universal mobile communication system terrestrial radio access EUTRA
  • the method also includes:
  • the determining whether to reject the registration request message of the terminal according to the number of registered users includes:
  • a backup network slice In response to the number of registered users of all requested network slices reaching the predetermined threshold and a backup network slice is configured, determine to accept the registration request message of the terminal;
  • a method for determining the number of registered users is provided, wherein the method is performed by a third network device, and the method includes:
  • the slice event subscription request is used to obtain an event report of the access type; the event report at least indicates the connection with the slice event subscription request The number of registered users associated with the entry type;
  • the event report sent by the first network device in response to the slice event subscription request is received.
  • the access type includes at least one of the following:
  • the wireless access type includes at least one of the following: new air interface access NR, evolved universal mobile communication system terrestrial radio access EUTRA, wireless local area network access WLAN, virtual network access VIRTUAL, narrowband IoT access to NBIOT, wired network access to WIRELINE, wired and cable network access to WIRELINE_CABLE, wired broadband network access to WIRELINE_BBF, urban rail transit vehicle-ground integrated communication system access to LTE-M, new air interface unlicensed spectrum access to NR_U, evolution Universal Mobile Telecommunications System Terrestrial Unlicensed Spectrum Wireless Access EUTRA_U, Trusted N3GA Access TRUSTED_N3GA, Trusted Wireless Local Area Network Access TRUSTED_WLAN, Universal Terrestrial Radio Access UTRA, Global System for Mobile Communications Edge Radio Access Network GERA, NR_LEO for low orbit, NR_MEO for medium and high orbit, NR_GEO for geostationary earth orbit and NR_OTHER_SAT for other satellites.
  • new air interface access NR evolved universal mobile communication system terrestrial radio access EUTRA
  • an apparatus for determining the number of registered users wherein the apparatus includes:
  • a determining module configured to determine the number of registered users for different access types based on the access type information
  • the access type information indicates the access type associated with the network slice.
  • an apparatus for determining the number of registered users wherein the apparatus includes:
  • a sending module configured to send a slice user quantity update request message to the first network device
  • a receiving module configured to receive a response message sent by the first network device in response to the slice user quantity update request message, where the response message carries the number of registered users of the access type of the slice reaching a predetermined threshold information and/or number of registered users.
  • an apparatus for determining the number of registered users wherein the apparatus includes:
  • a sending module configured to send a slice event subscription request indicating an access type to the first network device; wherein, the slice event subscription request is used to obtain an access type event report; the event report at least indicates the same as the slice event subscription request the number of registered users associated with the indicated access type;
  • a receiving module configured to receive the event report sent by the first network device in response to the slice event subscription request.
  • a communication device includes:
  • the processor is configured to implement the method described in any embodiment of the present disclosure when executing the executable instruction.
  • a computer storage medium stores a computer executable program, and when the executable program is executed by a processor, the method described in any embodiment of the present disclosure is implemented.
  • the number of registered users for different access types is determined; wherein the access type information indicates the access type of the terminal accessing the network slice.
  • the number of registered users is determined based on the access type of the terminal access network slice, the number of registered users of different access types can be determined, compared with the method of only determining the total number of registered users of all access types , determining the number of registered users corresponding to different access types in units of a single access type can more accurately determine the number of registered users corresponding to a single access type, so that resources can be configured based on the number of registered users corresponding to the single access type, Trigger and execute related services to better meet user needs.
  • Fig. 1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment.
  • Fig. 2 is a schematic flowchart of a method for determining the number of registered users according to an exemplary embodiment.
  • Fig. 3 is a schematic flowchart of a method for determining the number of registered users according to an exemplary embodiment.
  • Fig. 4 is a schematic flowchart of a method for determining the number of registered users according to an exemplary embodiment.
  • Fig. 5 is a schematic flowchart of a method for determining the number of registered users according to an exemplary embodiment.
  • Fig. 6 is a schematic flowchart of a method for determining the number of registered users according to an exemplary embodiment.
  • Fig. 7 is a schematic flowchart of a method for determining the number of registered users according to an exemplary embodiment.
  • Fig. 8 is a schematic flowchart of a method for determining the number of registered users according to an exemplary embodiment.
  • Fig. 9 is a schematic flowchart of a method for determining the number of registered users according to an exemplary embodiment.
  • Fig. 10 is a schematic flowchart of a method for determining the number of registered users according to an exemplary embodiment.
  • Fig. 11 is a schematic flowchart of a method for determining the number of registered users according to an exemplary embodiment.
  • Fig. 12 is a schematic flowchart of a method for determining the number of registered users according to an exemplary embodiment.
  • Fig. 13 is a schematic flowchart of a method for determining the number of registered users according to an exemplary embodiment.
  • Fig. 14 is a schematic flowchart of a method for determining the number of registered users according to an exemplary embodiment.
  • Fig. 15 is a schematic structural diagram of an apparatus for determining the number of registered users according to an exemplary embodiment.
  • Fig. 16 is a schematic structural diagram of an apparatus for determining the number of registered users according to an exemplary embodiment.
  • Fig. 17 is a schematic structural diagram of an apparatus for determining the number of registered users according to an exemplary embodiment.
  • Fig. 18 is a schematic structural diagram of a terminal according to an exemplary embodiment.
  • Fig. 19 is a block diagram of a base station according to an exemplary embodiment.
  • first, second, third, etc. may use the terms first, second, third, etc. to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of the embodiments of the present disclosure, first information may also be called second information, and similarly, second information may also be called first information. Depending on the context, the word “if” as used herein may be interpreted as “at” or "when” or "in response to a determination.”
  • the term “greater than” or “less than” is used herein when characterizing a size relationship. However, those skilled in the art can understand that the term “greater than” also covers the meaning of “greater than or equal to”, and “less than” also covers the meaning of "less than or equal to”.
  • FIG. 1 shows a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure.
  • the wireless communication system is a communication system based on mobile communication technology, and the wireless communication system may include: several user equipments 110 and several base stations 120 .
  • the user equipment 110 may be a device that provides voice and/or data connectivity to the user.
  • the user equipment 110 can communicate with one or more core networks via a radio access network (Radio Access Network, RAN), and the user equipment 110 can be an Internet of Things user equipment, such as a sensor device, a mobile phone, and a computer with an Internet of Things user equipment , for example, may be a fixed, portable, pocket, hand-held, computer built-in, or vehicle-mounted device.
  • RAN Radio Access Network
  • Station For example, Station (Station, STA), subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station), mobile station (mobile), remote station (remote station), access point, remote user equipment (remote terminal), access user equipment (access terminal), user device (user terminal), user agent (user agent), user equipment (user device), or user equipment (user equipment).
  • the user equipment 110 may also be equipment of an unmanned aerial vehicle.
  • the user equipment 110 may also be a vehicle-mounted device, for example, a trip computer with a wireless communication function, or a wireless user device connected externally to the trip computer.
  • the user equipment 110 may also be a roadside device, for example, may be a street lamp, a signal lamp, or other roadside devices with a wireless communication function.
  • the base station 120 may be a network side device in a wireless communication system.
  • the wireless communication system may be a 5G system, also known as a new air interface system or a 5G NR system.
  • the wireless communication system may also be a next-generation system of the 5G system.
  • the access network in the 5G system can be called NG-RAN (New Generation-Radio Access Network, New Generation Radio Access Network).
  • the base station 120 may be an evolved base station (eNB) adopted in a 4G system.
  • the base station 120 may also be a base station (gNB) adopting a centralized distributed architecture in the 5G system.
  • eNB evolved base station
  • gNB base station
  • the base station 120 adopts a centralized distributed architecture it generally includes a centralized unit (central unit, CU) and at least two distributed units (distributed unit, DU).
  • the centralized unit is provided with a packet data convergence protocol (Packet Data Convergence Protocol, PDCP) layer, radio link layer control protocol (Radio Link Control, RLC) layer, media access control (Media Access Control, MAC) layer protocol stack;
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC media access control
  • a physical (Physical, PHY) layer protocol stack is set in the unit, and the embodiment of the present disclosure does not limit the specific implementation manner of the base station 120 .
  • a wireless connection may be established between the base station 120 and the user equipment 110 through a wireless air interface.
  • the wireless air interface is a wireless air interface based on the fifth-generation mobile communication network technology (5G) standard, for example, the wireless air interface is a new air interface; or, the wireless air interface can also be a wireless air interface based on a 5G next-generation mobile communication network technology standard .
  • 5G fifth-generation mobile communication network technology
  • an E2E (End to End, end-to-end) connection may also be established between user equipment 110.
  • V2V vehicle to vehicle, vehicle-to-vehicle
  • V2I vehicle to Infrastructure, vehicle-to-roadside equipment
  • V2P vehicle to pedestrian, vehicle-to-person communication in vehicle to everything (V2X) communication Wait for the scene.
  • the above user equipment may be regarded as the terminal equipment in the following embodiments.
  • the foregoing wireless communication system may further include a network management device 130 .
  • the network management device 130 may be a core network device in a wireless communication system, such as an access and mobility management function (AMF, Access and Mobility Management Function), a session management function (SMF, Session Management Function), a user plane function (UPF , User Plane Function), policy control function (PCF, Policy Control Function), network storage function (NRF, Network Repository Function), etc.
  • AMF access and mobility management function
  • SMF Session Management Function
  • UPF User Plane Function
  • PCF Policy Control Function
  • NRF Network Repository Function
  • the embodiments of the present disclosure list a plurality of implementation manners to clearly illustrate the technical solutions of the embodiments of the present disclosure.
  • those skilled in the art can understand that the multiple embodiments provided by the embodiments of the present disclosure can be executed independently, or combined with the methods of other embodiments in the embodiments of the present disclosure, and can also be executed alone or in combination It is then executed together with some methods in other related technologies; this is not limited in the embodiment of the present disclosure.
  • multiple network slices deployed by a mobile network operator may provide exactly the same functionality.
  • such network slices may have different single network slice selection assistance information (S-NSSAI, Single Network Slice Selection Assistance Information) for the same slice or different Slice specifier.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • the selection of a group of network slice instances of the terminal is usually by interacting with the Network Slice Selection Function (NSSF, Network Slice Selection Function), and the access and mobility management function ( AMF, Access and Mobility Management Function) triggers and may cause changes to AMF.
  • NSF Network Slice Selection Function
  • AMF Access and Mobility Management Function
  • Each public land mobile network (PLMN, Public Land Mobile Network), protocol data unit (PDU, Protocol Data Unit) session belongs to one and only one specific network slice instance.
  • PLMN Public Land Mobile Network
  • PDU Protocol Data Unit
  • DNN Data Network Name
  • different network slice instances do not share PDU sessions.
  • the source AMF selects the target AMF by interacting with the network registration function (NRF, NF Repository Function).
  • NRF Network Registration Function
  • the network slicing type (NEST, Generic Network Slice Template) is applied to network slicing, and usually network slicing is supported by multiple network slicing instances.
  • the general network slice template (GST, Network Slice Type) defines the attributes supported by network slices.
  • the Network Slice Admission Control function (NSACF, Network Slice Admission Control function) is used to monitor the number of registered terminal terminals and the number of PDU sessions of the network slice supporting the NSAC function.
  • the NSACF also configures the access type information of the S-NSSAI performing the NSAC function.
  • each NSACF configures the maximum number of terminals allowed to be accessed by the network slice and the maximum number of PDU sessions allowed to be activated.
  • NSACF supports the monitoring and admission control of the maximum number of terminals and the maximum number of PDU sessions in the PLMN. If the number of terminals registered to the current slice exceeds a certain threshold (for example, the maximum number of terminals in the slice), NSAC will reject terminal registration to control the number of terminals served by the network to not exceed the maximum number of terminals configured in the network. When the number of active PDU sessions in a slice exceeds a certain threshold (for example, the maximum number of active sessions), NSAC will reject the activation of PDU sessions to control the current number of sessions not to exceed the maximum number of sessions configured by the network.
  • a certain threshold for example, the maximum number of active sessions
  • multiple NSACFs may be deployed in the operator network.
  • One NSACF can serve one or more S-NSSAI slices in one service area.
  • one S-NSSAI is only processed by one NSACF, which can be one NSACF instance or one NSACF set.
  • a PLMN can have one or more service areas.
  • the application function (AF, Application Function) has the requirement to obtain the status information of the network slice based on the guarantee or improvement of user experience, such as the current number of registered users in the slice, the number of currently activated PDU sessions, slice Information such as the ratio of the current number of registered users and/or the number of active PDU sessions to the overall threshold of the slice.
  • a method for determining the number of registered users is provided in this embodiment, wherein the method is performed by a first network device, and the method includes:
  • Step 21 Based on the access type information, determine the number of registered users for different access types
  • the access type information indicates an access type for the terminal to access the network slice.
  • the terminals involved in the present disclosure may be, but not limited to, mobile phones, wearable devices, vehicle-mounted terminals, Road Side Units (RSU, Road Side Unit), smart home terminals, industrial sensing devices, and/or medical devices.
  • the number of registered users may also have the meaning of "number of registered terminals”.
  • slice may also have the meaning of "network slice or network slice instance”.
  • the first network device involved in this disclosure may be an NSACF. It should be noted that the first network device in the present disclosure is not limited to the NSACF, and may also be other communication nodes in the core network, which is not limited here. Here, one NSACF may be deployed for each network slice, or multiple NSACFs may be deployed for each network slice. If multiple NSACFs are deployed for each network slice, the NSACF involved in the present disclosure is a certain NSACF in the multiple NSACFs.
  • the second network device in the present disclosure may be an AMF, but the second network device in the present disclosure is not limited to the AMF, and may also be other communication nodes in the core network.
  • the third network device in the present disclosure may be an AF.
  • determining the number of registered users for different access types may include: counting the number of registered users for different access types.
  • the access type information indicates at least one of the following:
  • Access Type (Access Type);
  • the access type indication information may include at least one item of the access type, the wireless access type, and the access type auxiliary information, where the access type auxiliary information includes the access type and the wireless access type.
  • the access type includes at least one of the following: 3GPP access, non-3GPP access, 3GPP and non-3GPP access.
  • the wireless access type includes at least one of the following: NR access, EUTRA access, WLAN access, VIRTUAL access, NBIOT access, WIRELINE access, WIRELINE_CABLE access, WIRELINE_BBF access, LTE- M access, NR_U access, EUTRA_U access, TRUSTED_N3GA access, TRUSTED_WLAN access, UTRA access, GERA access, NR_LEO access, NR_MEO access, NR_GEO access, and NR_OTHER_SAT access.
  • the access type information may be configured on the NSACF; or, the NSACF may obtain the access type information from the consumer network function; or obtain the access type information from the operation and maintenance management system (OAM, Operation Administration and Maintenance) Enter type information.
  • consumer network functions can include one of the following: Network Exposure Function (NEF, Network Exposure Function), Policy Decision Function (PCF, Policy Control Function), primary NSACF in multiple NSACF deployment scenarios, and operation and maintenance management System OAM.
  • the number of registered users of different access types may be the number of registered users of multiple access types or the number of registered users of a single access type.
  • the number of registered users for different access types is determined based on the access type information; wherein the access type information indicates the access type of the terminal accessing the network slice. In this way, the number of registered users of different access types can be counted.
  • the number of registered users for different access types is determined based on the access type information; wherein the access type information indicates the access type of the terminal accessing the network slice. In this way, the number of registered users of different access types can be counted.
  • the number of registered users for different access types is determined based on the access type information; wherein the access type information indicates the access type of the terminal accessing the network slice. In this way, the number of registered users of different access types can be counted.
  • the access type here may be the access type of the terminal currently accessing the network slice.
  • the access type may be an access type for which the network slice needs to perform NSAC statistics.
  • the number of registered users of each access type of the network slice is determined. In this way, the number of registered users of different access types can be counted.
  • the number of registered users for different access types may be updated before the number of registered users for different access types is determined. In this way, updates can be made in a timely manner.
  • the registration process includes initial registration or a mobile registration update type registration process caused by cross-AMF handover.
  • the number of registered users for different access types is updated before transmitting the registration acceptance message; or, in the EAC inactive state, the number of registered users for different access types is updated after the registration acceptance message is transmitted. The number of registered users is updated.
  • the number of registered users for different access types is updated.
  • the NSSAA slice-specific authentication process or the subscription S-NSSAI change process triggers the configuration update
  • the EAC mode before the configuration update message
  • the The number of registered users of is updated.
  • the EAC mode is activated and the update flag indicates an increase number, the update of the number of registered users for different access types is performed before the terminal configuration update message; or, if the EAC mode is activated but the update flag indicates a decrease number, in The number of registered users for different access types is updated after the terminal configuration update message; or, if the EAC mode is not activated, the number of registered users for different access types is updated after the terminal configuration update message.
  • updating the number of registered users may be to increase or decrease the number of registered users.
  • the NSACF may receive a request message (for example, Nnsacf_NSAC_NumOfUEsUpdate_Request) sent by the AMF, where the request message includes an update identifier.
  • the update flag indicates that the number of registered users has increased or decreased.
  • the update identifier indicates that the number of registered users increases; or, when the user deregisters from the slice or the registration cannot continue, the update identifier indicates that the number of registered users decreases.
  • the request message may also indicate the terminal identifier, the access type, the relevant slice S-NSSAIs and/or the AMF identifier for which NSAC is requested to be performed, and the like.
  • the access type information may be locally generated by the AMF, or obtained from a request message sent by the base station to the AMF.
  • AMF when AMF and NSACF interact to perform updates for the first time, AMF will carry the relevant node NF information that the early validity check EAC needs to notify to in the request message, thus implicitly from NSACF Subscribe to EAC-related notifications for slices.
  • the NSACF is also configured with a slice-based maximum number of registered users allowed based on the access type.
  • the NSACF When updating the number of registered users based on the access type for a slice, if the slice reaches the maximum number of registered users in the one or more access types, NSACF will carry the information that the maximum number of users has reached the maximum number of users in the response message returned to the AMF . It should be noted that, if the EAC notification endpoint information is received from the AMF, the NSACF stores the EAC notification endpoint information associated with the S-NSSAI, so as to update the EAC mode by using the stored notification endpoint information subsequently.
  • the NSACF sends a response message (for example, Nnsacf_NSAC_NumOfUEsUpdate_Response) to the AMF for the request message, wherein the response message carries the number of registered users of the access type of the terminal access slice Slice identifiers S-NSSAI(s) that reach the set threshold or maximum value and related result parameters indicating that the maximum value has been reached.
  • a response message for example, Nnsacf_NSAC_NumOfUEsUpdate_Response
  • the AMF in the terminal registration process, after the AMF receives the response message, if only a part of the requested slice reaches the maximum number of registered users, the AMF will send a registration acceptance message to the registered terminal.
  • the registration acceptance message the slice identification rejected due to update is carried in the reject slice list, and the corresponding rejection reason is set as the maximum number of users in the area of the slice has reached.
  • a timer can be set to initiate a re-request.
  • the AMF may decide to put these default slices into the Allow NSSAI as authorized slices. Otherwise, the AMF will reject the UE's registration request (for example, the registration request of the access type).
  • the AMF carries a list of rejected slice identifiers, and each slice carries a corresponding rejection reason value, for example, the maximum number of registered users allowed in the area of the slice has been reached.
  • a timer is set that can initiate a re-request.
  • the number of registered users for different access types is determined; wherein, the access type information indicates the access type of the terminal accessing the network slice.
  • the number of registered users is determined based on the access type of the terminal access network slice, the number of registered users of different access types can be determined, compared with the method of only determining the total number of registered users of all access types , determining the number of registered users corresponding to different access types in units of a single access type can more accurately determine the number of registered users corresponding to a single access type, so that resources, triggers, and Carry out relevant business to better meet the needs of users.
  • the access type includes at least one of the following:
  • the wireless access type includes at least one of the following: new air interface access NR, evolved universal mobile communication system terrestrial radio access EUTRA, wireless local area network access WLAN, virtual network access VIRTUAL, narrowband IoT access to NBIOT, wired network access to WIRELINE, wired and cable network access to WIRELINE_CABLE, wired broadband network access to WIRELINE_BBF, urban rail transit vehicle-ground integrated communication system access to LTE-M, new air interface unlicensed spectrum access to NR_U, evolution Universal Mobile Telecommunications System Terrestrial Unlicensed Spectrum Wireless Access EUTRA_U, Trusted N3GA Access TRUSTED_N3GA, Trusted Wireless Local Area Network Access TRUSTED_WLAN, Universal Terrestrial Radio Access UTRA, Global System for Mobile Communications Edge Radio Access Network GERA, NR_LEO for low orbit, NR_MEO for medium and high orbit, NR_GEO for geostationary earth orbit and NR_OTHER_SAT for other satellites.
  • new air interface access NR evolved universal mobile communication system terrestrial radio access EUTRA
  • a method for determining the number of registered users is provided in this embodiment, wherein the method is performed by the first network device, and the method includes:
  • Step 41 updating the number of registered users of different access types in response to the execution of the predetermined process by the terminal;
  • the predetermined process includes one of the following:
  • determining and updating the number of registered users of different access types may be triggered in the above scenario.
  • the registration process includes initial registration or a mobile registration update type registration process caused by cross-AMF handover.
  • the EAC active state the number of registered users for different access types is updated before transmitting the registration acceptance message; or, in the EAC inactive state, the number of registered users for different access types is updated after the registration acceptance message is transmitted. The number of registered users is updated.
  • the number of registered users for different access types is updated.
  • the NSSAA slice-specific authentication process or the subscription S-NSSAI change process triggers the configuration update
  • the EAC mode before the configuration update message
  • the The number of registered users of is updated.
  • the EAC mode is activated and the update flag indicates an increase number, the update of the number of registered users for different access types is performed before the terminal configuration update message; or, if the EAC mode is activated but the update flag indicates a decrease number, in The number of registered users for different access types is updated after the terminal configuration update message; or, if the EAC mode is not activated, the number of registered users for different access types is updated after the terminal configuration update message.
  • updating the number of registered users may be to increase or decrease the number of registered users of a corresponding access type or wireless access type.
  • Step 51 During the registration process of the terminal, the terminal initiates a registration process to one or some network slices to the network.
  • the terminal may send a registration request message to the AMF; the registration request message may carry parameters such as a slice identifier and NSACF characteristics.
  • AMF performs discovery and selection of NSACF based on parameters such as slice identification and NSACF characteristics.
  • the validity check and update process includes: determining the number of registered users for different access types based on the access type information.
  • Step 52 AMF sends Nnsacf_NSAC_NumOfUEsUpdate_Request to NSACF.
  • Step 53 NSACF determines the number of registered users for different access types based on the access type information. Here, it may be to check and update the number of registered users for different access types.
  • Step 54 NSACF sends Nnsacf_NSAC_NumOfUEsUpdate_Response to AMF.
  • the Nnsacf_NSAC_NumOfUEsUpdate_Response includes the number of registered users for different access types determined by the NSACF.
  • Step 55 AMF sends a registration request rejection message to the terminal.
  • the AMF will refuse the UE to register with the relevant For network slicing, the registration rejection message is sent while carrying relevant rejection reason values, such as threshold arrival. Otherwise, go to step 56.
  • step 56 the AMF sends a registration request acceptance message to the terminal.
  • Step 61 the terminal has been registered, and the terminal or the network triggers a de-registration process.
  • Step 62 the terminal sends a de-registration request to the AMF.
  • Step 63 execute the de-registration process and complete the de-registration process.
  • step 64 the AMF sends a de-registration acceptance message to the terminal. It should be noted that, step 62 to step 64 are performed according to the conventional de-registration process, and the de-registration process is completed.
  • the AMF triggers a slice-based validity check and update process based on the number of registered users of the access type.
  • Step 65 AMF sends Nnsacf_NSAC_NumOfUEsUpdate_Request to NSACF.
  • the NSACF determines the number of registered users for different access types based on the access type information. Here, it may be to check and update the number of registered users for different access types.
  • Step 67 NSACF sends Nnsacf_NSAC_NumOfUEsUpdate_Response to AMF.
  • the Nnsacf_NSAC_NumOfUEsUpdate_Response includes the number of registered users for different access types determined by the NSACF.
  • NSACF may receive a request message (for example, Nnsacf_NSAC_NumOfUEsUpdate_Request) sent by AMF, wherein the request message includes an update logo.
  • the update flag indicates that the number of registered users has increased or decreased.
  • this embodiment provides a method for determining the number of registered users, wherein the method is performed by the first network device, and the method includes:
  • Step 71 Update the number of registered users of different access types in response to the terminal executing a predetermined process and receiving the update request message of the number of slice users sent by the AMF; wherein the update request message of the number of slice users indicates to increase or decrease the number of registered users.
  • the number of registered users of different access types is increased.
  • the number of registered users of different access types is reduced.
  • a method for determining the number of registered users is provided in this embodiment, wherein the method is performed by a first network device, and the method includes:
  • Step 81 sending a response message to the request message for updating the number of slice users to the AMF;
  • the response message carries information that the number of registered users of the access type reaches a predetermined threshold and/or the number of registered users.
  • the first network device receives the slice user number update request message sent by the AMF; in response to the terminal executing a predetermined process and the slice user number update request message indicating to increase the number of registered users, increase the number of registered users of different access types.
  • a response message carrying the increased number of registered users of different access types is sent to the AMF. Please refer to step 54 in FIG. 5 and step 67 in FIG. 6, which may be to send a Nnsacf_NSAC_NumOfUEsUpdate_Response response message. It should be noted that, if the added number of registered users of different access types reaches a predetermined threshold, the response message also carries information that the number of registered users of an access type reaches a predetermined threshold.
  • the number of registered users of different access types is reduced.
  • a method for determining the number of registered users is provided in this embodiment, wherein the method is performed by a first network device, and the method includes:
  • Step 91 In response to receiving a slice event subscription request indicating an access type sent by the application function AF, send an event report of the access type to the AF.
  • a slice event subscription request of the application function AF is received, wherein the slice event subscription request carries access type information; and an event report of the access type indicated by the access type information is sent to the AF.
  • the slice event subscription request of the AF is received through the NEF; and the event report is sent to the AF through the NEF.
  • the NEF when the NEF receives the slice event subscription request sent by the AF and sends the event report to the AF through the NEF, if the access type indicated by the access type information is associated with multiple NSACFs, the NEF will report to the multiple NSACFs Send slice event subscription request; NEF will perform aggregation statistics after receiving event information, and report the aggregated information to AF.
  • the NEF performs the discovery and selection of the NSASF through the network registration function NRF, or the NEF performs the discovery and selection of the NSACF through the local configuration.
  • NEF executes the mapping between the application or service identifier of AF and the slice identifier; when NEF receives the slice event subscription request of AF, it maps the application or service identifier to the slice identifier and sends it to NSACF; When receiving the time report from the NSACF, map the slice ID to an application or service ID and send it to the AF. Exemplarily, in the response message, the slice identifier is mapped to an application or service identifier and sent to the AF.
  • the slice event subscription request includes an event to be subscribed to, and the event includes at least one of the following: the number of registered terminals and the ratio of the number of registered terminals to the maximum number of registered terminals allowed.
  • the slice event subscription request includes a request to subscribe to event screening information, wherein the screening information indicates features that need to be reported.
  • screening information indicates access type information.
  • the access type information includes at least one of the following: access type, wireless access type.
  • the filtering information may also indicate at least one of the following: a slice identifier, a combination of a slice identifier and a data network name.
  • the slice event subscription request may also include an event report mode for requesting subscription.
  • the reporting mode includes at least one of the following: a threshold for triggering reporting, and a periodic time interval for triggering reporting.
  • an event report is reported when the threshold is reached or when the periodic time interval is reached.
  • the slice event subscription request includes an immediate report flag that reports the requested event report immediately upon receipt of the request.
  • the AF in order to subscribe to or cancel the reporting notification of the number of terminals related to the network slice type to the NEF, the AF sends a Nnef_EventExposure subscribe/unsubscribe Request message to the NEF, and the message includes event ID, event filter, and event report information.
  • the event ID parameter defines the subscribed event ID, that is, the number of registered terminals, or the ratio of the number of registered terminals to the maximum allowed number of registered terminals, or the number of registered terminals and the number of registered terminals to the maximum allowed The ratio of the number of registered terminals.
  • the event filter parameter defines the scope for reporting. Each range corresponds to an access type.
  • the access type information includes at least one of the following items: access type, wireless access type, and access assistance information including the access type and the wireless access type.
  • the event filter parameter further includes one of the following items: a slice identifier S-NSSAI, a combination of a slice identifier S-NSSAI and a data network name DNN.
  • the event reporting information parameter defines the reporting mode, includes a threshold, or includes periodic reporting at periodic time intervals. If the report information parameter is a threshold that triggers reporting, when the threshold is reached, an event report is reported. If the report information parameter is a periodic time interval for triggering reporting, when the periodic time interval arrives, an event report is reported. Subscription requests may also include a report-immediate flag indicating that the requested incident report is reported immediately upon receipt of the request.
  • the NEF when multiple NSACFs are requested to be deployed in a slice, after receiving the information reported by the corresponding NSACFs, the NEF performs aggregate statistics on the reported messages, and reports the aggregated information to the requesting application function AF. In one embodiment, when there are multiple NSACFs, according to the operation policy or NEF configuration, one of the NSACFs can be selected as the master NSACF or proxy NSACF of the corresponding NSACF, and perform subscription, collection and aggregation of related NSACF status information.
  • the NSACF When the NSACF is the master NSACF, other NSACFs in the slice are slave NSACFs; when the NSACF is a proxy NSACF, the NSACF does not have a master-slave relationship with other NSACFs in the slice.
  • the NEF sends a Nnef_EventExposure_Subscribe/usubsubscribe Response response message to the AF.
  • the NEF subscribes to each NSACF requesting the slice for the event report of the slice, and after receiving the event report of each NSACF, sends the event report to the AF.
  • the NEF may query the NSACF(s) corresponding to the access type information of the slice request through the NRF, or discover and select the NSACF(s) corresponding to the access type information of the slice request through local configuration.
  • the NEF if the NEF has not subscribed to the NSACF(s) corresponding to the slice request access type information for the reporting event of the related Requested S-NSSAI, the NEF initiates a subscription to the NSACF that supports the Requested S-NSSAI request access type information Request, send Nnef_SliceEventExposure_Subscribe/Unsubscribe request request message, the message includes event ID, event filter, event report information, etc.
  • the NEF stores event report information requested by the AF. If the Requested S-NSSAI is performed by multiple NSACFs to perform UE slice admission control, the NEF can set the time report information as a periodic report in the subscription request to each NSACF.
  • the event report information set by the NEF itself is the same as the request received from the AF.
  • the NEF will set the event ID and event filter information according to the content in the request message received by the AF.
  • the NSACF sends a Nnsacf_SliceEventExposure_Subscribe/usubsubscribe response message to the NEF to confirm the subscription request.
  • the NSACF when the subscribed report condition is met and the report event is triggered, the NSACF sends a trigger notification to the NEF to perform the report of the information related to the subscription event.
  • NSACF sends Nnsacf_SliceEvent Exposure_Notify message to NEF, and the message carries parameters such as event ID, event filter, and event report information.
  • NEF collects the reports of all NFACFs corresponding to the requested access type, and performs slice S-NSSAI in requesting event filtering Aggregation of quantities within a device (such as 3GPP/non-3GPP access types).
  • the NEF performs the reporting of the number of slice S-NSSAIs in the requested event filter (such as 3GPP/non-3GPP access type).
  • NEF When the requested NSSAI request access type information corresponds to a single NSACF to perform UE slice admission control, NEF immediately returns a report notification to AF, reports its own statistical usage report, or performs periodic reporting to AF according to periodic subscription.
  • the subscription report when the condition of the event report subscribed by the AF is triggered/satisfied, the subscription report is triggered.
  • the NEF sends a notification to the AF to report the subscription-related usage and information according to the subscription requirements, such as the number of UEs of the 3GPP access type of the slice, the number of UEs of the non-3GPP access type of the slice, or the 3GPP access type of the slice The number of UEs corresponding to internal satellite access, etc., or the proportion of the corresponding number of UEs to the maximum allowed number reported at the same time.
  • NEF executes the mapping request for the AF application or service identifier and the slice identifier; when NEF receives the AF subscription request, it maps the application or service identifier to The slice ID is sent to the NSACF; when the NEF receives the subscription event notification from the NSACF, it maps the slice ID to an application or service ID and sends it to the AF.
  • a method for determining the number of registered users is provided in this embodiment, wherein the method is performed by a second network device, and the method includes:
  • Step 101 sending a slice user quantity update request message to the first network device
  • Step 102 Receive a response message sent by the first network device in response to the slice user quantity update request message, wherein the response message carries information that the number of registered users of different access types of the slice reaches a predetermined threshold and/or Or the number of registered users of different access types.
  • the terminals involved in the present disclosure may be, but not limited to, mobile phones, wearable devices, vehicle-mounted terminals, Road Side Units (RSU, Road Side Unit), smart home terminals, industrial sensing devices, and/or medical devices.
  • the number of registered users may also have the meaning of "number of registered terminals”.
  • slice may also have the meaning of "network slice or network slice instance”.
  • the first network device involved in this disclosure may be an NSACF. It should be noted that the first network device in the present disclosure is not limited to the NSACF, and may also be other communication nodes in the core network, which is not limited here. Here, one NSACF may be deployed for each network slice, or multiple NSACFs may be deployed for each network slice. If multiple NSACFs are deployed for each network slice, the NSACF involved in the present disclosure is a certain NSACF in the multiple NSACFs.
  • the second network device in the present disclosure may also be an AMF, but the second network device in the present disclosure is not limited to the AMF, and may also be other communication nodes in the core network.
  • the number of registered users for different access types may be determined or counted by the first network device.
  • the access type includes an access type (Access Type) and a wireless access type (RAT Radio Access Type).
  • the wireless access type includes at least one of the following: NR access, EUTRA access, WLAN access, VIRTUAL access, NBIOT access, WIRELINE access, WIRELINE_CABLE access, WIRELINE_BBF access, LTE- M access, NR_U access, EUTRA_U access, TRUSTED_N3GA access, TRUSTED_WLAN access, UTRA access, GERA access, NR_LEO access, NR_MEO access, NR_GEO access, and NR_OTHER_SAT access.
  • a slice user quantity update request message is sent to the first network device; and a response message sent by the first network device in response to the slice user quantity update request message is received, wherein the The response message carries information that the number of registered users of different access types of the slice reaches a predetermined threshold and/or the number of registered users of different access types.
  • the number of registered users for different access types is determined based on the access type information; wherein the access type information indicates the access type of the terminal accessing the network slice. In this way, the number of registered users of different access types can be counted.
  • the number of registered users for different access types is determined based on the access type information; wherein the access type information indicates the access type of the terminal accessing the network slice. In this way, the number of registered users of different access types can be counted.
  • the AMF may send a request message (for example, Nnsacf_NSAC_NumOfUEsUpdate_Request) to the NSACF, where the request message includes an update identifier.
  • the update flag indicates that the number of registered users has increased or decreased.
  • the update identifier indicates that the number of registered users increases; or, when the user deregisters from the slice or registration cannot continue, the update identifier indicates that the number of registered users decreases.
  • the request message may also include indicating terminal identifier, access type, relevant slice S-NSSAIs for which NSAC is requested to be performed, and/or AMF identifier, etc.
  • the access type information may be locally generated by the AMF, or obtained from a request message sent by the base station to the AMF.
  • AMF when AMF and NSACF interact to perform updates for the first time, AMF will carry the relevant node NF information that the early validity check EAC needs to notify to in the request message, thus implicitly from NSACF Subscribe to EAC-related notifications for slices.
  • the NSACF is also configured with a slice-based maximum number of registered users allowed based on the access type.
  • the NSACF When updating the number of registered users based on the access type for a slice, if the slice reaches the maximum number of registered users in the one or more access types, NSACF will carry the information that the maximum number of users has reached the maximum number of users in the response message returned to the AMF . It should be noted that, if the EAC notification endpoint information is received from the AMF, the NSACF stores the EAC notification endpoint information associated with the S-NSSAI, so as to update the EAC mode by using the stored notification endpoint information subsequently.
  • the AMF receives the response message (for example, Nnsacf_NSAC_NumOfUEsUpdate_Response) sent by the NSACF for the request message, wherein the response message carries the number of registered users of the access type of the slice to the set A slice identifier S-NSSAI(s) with a threshold or maximum value and an associated result parameter indicating that the maximum value has been reached.
  • the response message for example, Nnsacf_NSAC_NumOfUEsUpdate_Response
  • the AMF in the terminal registration process, after the AMF receives the response message, if only a part of the requested slice reaches the maximum number of registered users, the AMF will send a registration acceptance message to the registered terminal.
  • the registration acceptance message the slice identification rejected due to update is carried in the reject slice list, and the corresponding rejection reason is set as the maximum number of users in the area of the slice has reached.
  • a timer can be set to initiate a re-request.
  • the AMF may decide to put these default slices into the Allow NSSAI as authorized slices. Otherwise, the AMF will reject the UE's registration request (for example, the registration request of the access type).
  • the AMF carries a list of rejected slice identifiers, and each slice carries a corresponding value of the reason for rejection, for example, the maximum number of registered users allowed in the area of the slice has been reached.
  • a timer is set that can initiate a re-request.
  • this embodiment provides a method for determining the number of registered users, wherein the method is performed by the second network device, and the method includes:
  • Step 111 receiving the registration request message sent by the terminal
  • Step 112 according to the number of registered users, determine whether to reject the registration request message of the terminal.
  • the AMF in the terminal registration process, after the AMF receives the response message, if only a part of the requested slice reaches the maximum number of registered users, the AMF will send a registration acceptance message to the registered terminal.
  • the registration acceptance message the slice identification rejected due to update is carried in the reject slice list, and the corresponding rejection reason is set as the maximum number of users in the area of the slice has reached.
  • a timer can be set that can initiate a re-request.
  • the AMF may decide to put these default slices into the Allow NSSAI as authorized slices. Otherwise, the AMF will reject the UE's registration request (for example, the registration request of the access type).
  • the AMF carries a list of rejected slice identifiers, and each slice carries a corresponding rejection reason value, for example, the maximum number of registered users allowed in the area of the slice has been reached.
  • a timer is set that can initiate a re-request.
  • this embodiment provides a method for determining the number of registered users, wherein the method is performed by the second network device, and the method includes:
  • Step 121 in response to the number of registered users of the requested part of the network slice reaching the predetermined threshold, determine to accept the registration request message of the terminal;
  • a backup network slice In response to the number of registered users of all requested network slices reaching the predetermined threshold and a backup network slice is configured, determine to accept the registration request message of the terminal;
  • a registration request message of the terminal may be received, for example, it may be rejected when the number of registered users of the terminal reaches the predetermined threshold and accepting the registration of the terminal on the network slice whose number of registered users does not reach the predetermined threshold.
  • the terminal requests to register on 4 slices, and the 4 slices are slice A, slice B, slice C, and slice D. If the number of registered users of slice A, slice B, and slice C reaches the predetermined threshold, you can The registration request message of the terminal is accepted. At this time, the registration of the terminal on the D slice can be accepted, but the registration of the terminal on the A slice, B slice and C slice will be rejected.
  • the predetermined threshold may be the maximum number of registered users or the number of sessions. Exemplarily, it may be an actual value, such as an absolute value. It may also be a value corresponding to the ratio of the maximum number of users or the maximum capacity of the number of sessions in the network, for example, a relative value.
  • the predetermined threshold may be determined according to the required network communication quality. Exemplarily, when the required network communication quality is better and more guaranteed, the predetermined threshold may be set to a smaller value; or, when the required network communication quality is lowered, the predetermined threshold may be set to a larger value .
  • a method for determining the number of registered users is provided in this embodiment, wherein the method is performed by a third network device, and the method includes:
  • Step 131 Send a slice event subscription request indicating the access type to the first network device; wherein, the slice event subscription request is used to obtain an event report of the access type; the event report at least indicates the same as the slice event subscription request the number of registered users associated with the indicated access type;
  • Step 132 Receive the event report sent by the first network device in response to the slice event subscription request.
  • the terminals involved in the present disclosure may be, but not limited to, mobile phones, wearable devices, vehicle-mounted terminals, Road Side Units (RSU, Road Side Unit), smart home terminals, industrial sensing devices, and/or medical devices.
  • the number of registered users may also have the meaning of "number of registered terminals”.
  • slice may also have the meaning of "network slice or network slice instance”.
  • the first network device involved in this disclosure may be an NSACF. It should be noted that the first network device in the present disclosure is not limited to the NSACF, and may also be other communication nodes in the core network, which is not limited here. Here, one NSACF may be deployed for each network slice, or multiple NSACFs may be deployed for each network slice. If multiple NSACFs are deployed for each network slice, the NSACF involved in the present disclosure is a certain NSACF in the multiple NSACFs.
  • the third network device in the present disclosure may be an application function AF, but the third network device in the present disclosure is not limited to the AF, and may also be other communication nodes in the core network.
  • the access type includes at least one of the following:
  • the wireless access type includes at least one of the following: new air interface access NR, evolved universal mobile communication system terrestrial radio access EUTRA, wireless local area network access WLAN, virtual network access VIRTUAL, narrowband IoT access to NBIOT, wired network access to WIRELINE, wired and cable network access to WIRELINE_CABLE, wired broadband network access to WIRELINE_BBF, urban rail transit vehicle-ground integrated communication system access to LTE-M, new air interface unlicensed spectrum access to NR_U, evolution Universal Mobile Telecommunications System Terrestrial Unlicensed Spectrum Wireless Access EUTRA_U, Trusted N3GA Access TRUSTED_N3GA, Trusted Wireless Local Area Network Access TRUSTED_WLAN, Universal Terrestrial Radio Access UTRA, Global System for Mobile Communications Edge Radio Access Network GERA, NR_LEO for low orbit, NR_MEO for medium and high orbit, NR_GEO for geostationary earth orbit and NR_OTHER_SAT for other satellites.
  • new air interface access NR evolved universal mobile communication system terrestrial radio access EUTRA
  • the application function AF sends a slice event subscription request to the NSACF, wherein the slice event subscription request carries access type information; and receives an event report of the access type indicated by the access type information sent by the NSACF.
  • slice event subscription requests are sent through NEF; event reports are received through NEF.
  • NEF when sending slice event subscription requests through NEF and receiving event reports through NEF, if the access type indicated by the access type information is associated with multiple NSACFs, NEF will send slice event subscription requests to multiple NSACFs ; After receiving the event information, the NEF will perform aggregated statistics and report the aggregated information to the AF.
  • the NEF performs the discovery and selection of the NSASF through the network registration function NRF, or the NEF performs the discovery and selection of the NSACF through the local configuration.
  • NEF executes the mapping between the application or service identifier of AF and the slice identifier; when NEF receives the slice event subscription request of AF, it maps the application or service identifier to the slice identifier and sends it to NSACF; When receiving the time report from the NSACF, map the slice ID to an application or service ID and send it to the AF.
  • the slice event subscription request includes an event to be subscribed to, and the event includes at least one of the following: the number of registered terminals and the ratio of the number of registered terminals to the maximum number of registered terminals allowed.
  • the slice event subscription request includes a request to subscribe to event screening information, wherein the screening information indicates features that need to be reported.
  • screening information indicates access type information.
  • the access type information includes at least one of the following: access type, wireless access type.
  • the filtering information may also indicate at least one of the following: a slice identifier, a combination of a slice identifier and a data network name.
  • the slice event subscription request may also include an event report mode for requesting subscription.
  • the reporting mode includes at least one of the following: a threshold for triggering reporting, and a periodic time interval for triggering reporting.
  • an event report is reported when the threshold is reached or when the periodic time interval is reached.
  • the slice event subscription request includes an immediate report flag that reports the requested event report immediately upon receipt of the request.
  • the AF in order to subscribe to or cancel the reporting notification of the number of terminals related to the network slice type to the NEF, the AF sends a Nnef_EventExposure subscribe/unsubscribe Request message to the NEF, and the message includes event ID, event filter, and event report information.
  • the event ID parameter defines the subscribed event ID, that is, the number of registered terminals, or the ratio of the number of registered terminals to the maximum allowed number of registered terminals, or the number of registered terminals and the number of registered terminals to the maximum allowed The ratio of the number of registered terminals.
  • the event filter parameter defines the scope for reporting. Each range corresponds to an access type.
  • the access type information includes at least one of the following items: access type, wireless access type, and access assistance information including the access type and the wireless access type.
  • the event filter parameter further includes one of the following items: a slice identifier S-NSSAI, a combination of a slice identifier S-NSSAI and a data network name DNN.
  • the event reporting information parameter defines the reporting mode, includes a threshold, or includes periodic reporting at periodic time intervals. If the report information parameter is a threshold that triggers reporting, when the threshold is reached, an event report is reported. If the report information parameter is a periodic time interval for triggering reporting, when the periodic time interval arrives, an event report is reported. Subscription requests may also include a report-immediate flag indicating that the requested incident report is reported immediately upon receipt of the request.
  • the NEF when multiple NSACFs are requested to be deployed in a slice, after receiving the information reported by the corresponding NSACFs, the NEF performs aggregate statistics on the reported messages, and reports the aggregated information to the requesting application function AF. In one embodiment, when there are multiple NSACFs, according to the operation policy or NEF configuration, one of the NSACFs can be selected as the master NSACF or proxy NSACF of the corresponding NSACF, and perform subscription, collection and aggregation of related NSACF status information.
  • the NSACF When the NSACF is the master NSACF, other NSACFs in the slice are slave NSACFs; when the NSACF is a proxy NSACF, the NSACF does not have a master-slave relationship with other NSACFs in the slice.
  • the NEF sends a Nnef_EventExposure_Subscribe/usubsubscribe Response response message to the AF.
  • the NEF subscribes to each NSACF requesting the slice for the event report of the slice, and after receiving the event report of each NSACF, sends the event report to the AF.
  • the NEF may query the NSACF(s) corresponding to the access type information of the slice request through the NRF, or discover and select the NSACF(s) corresponding to the access type information of the slice request through local configuration.
  • the NEF if the NEF has not subscribed to the NSACF(s) corresponding to the slice request access type information for the reporting event of the related Requested S-NSSAI, the NEF initiates a subscription to the NSACF that supports the Requested S-NSSAI request access type information Request, send Nnef_SliceEventExposure_Subscribe/Unsubscribe request request message, the message includes event ID, event filter, event report information, etc.
  • the NEF stores event report information requested by the AF. If the Requested S-NSSAI is performed by multiple NSACFs to perform UE slice admission control, the NEF can set the time report information as a periodic report in the subscription request to each NSACF.
  • the event report information set by the NEF itself is the same as the request received from the AF.
  • the NEF will set the event ID and event filter information according to the content in the request message received by the AF.
  • the NSACF sends a Nnsacf_SliceEventExposure_Subscribe/usubsubscribe response message to the NEF to confirm the subscription request.
  • the NSACF when the subscribed report condition is met and the report event is triggered, the NSACF sends a trigger notification to the NEF to perform the report of the information related to the subscription event.
  • NSACF sends Nnsacf_SliceEvent Exposure_Notify message to NEF, and the message carries parameters such as event ID, event filter, and event report information.
  • NEF collects the reports of all NFACFs corresponding to the requested access type, and performs slice S-NSSAI in requesting event filtering Aggregation of quantities within a device (such as 3GPP/non-3GPP access types).
  • the NEF performs the reporting of the number of slice S-NSSAIs in the requested event filter (such as 3GPP/non-3GPP access type).
  • NEF When the requested NSSAI request access type information corresponds to a single NSACF to perform UE slice admission control, NEF immediately returns a report notification to AF, reports its own statistical usage report, or performs periodic reporting to AF according to periodic subscription.
  • the subscription report when the condition of the event report subscribed by the AF is triggered/satisfied, the subscription report is triggered.
  • the NEF sends a notification to the AF to report the subscription-related usage and information according to the subscription requirements, such as the number of UEs of the 3GPP access type of the slice, the number of UEs of the non-3GPP access type of the slice, or the 3GPP access type of the slice The number of UEs corresponding to internal satellite access, etc., or the proportion of the corresponding number of UEs to the maximum allowed number reported at the same time.
  • NEF executes the mapping request for the AF application or service identifier and the slice identifier; when NEF receives the AF subscription request, it maps the application or service identifier to The slice ID is sent to the NSACF; when the NEF receives the subscription event notification from the NSACF, it maps the slice ID to an application or service ID and sends it to the AF.
  • the notification process of the method for determining the number of registered users may include:
  • Step 141 AF sends Nnef_EventExposure subscribe or unsubscribe Request message to NEF.
  • AF sends Nnef_EventExposure subscribe/unsubscribe Request message to NEF, and the message includes event ID, event filter, and event report information.
  • the reporting notification of the number of related terminals includes: the number of registered users associated with the access type.
  • the number of registered users for different access types may be determined based on the access type information.
  • Step 142 NEF sends Nnef_EventExposure_Subscribe or usubsubscribe Response response message to AF.
  • the NEF subscribes to the reporting events of the requesting slice to each NSACF of the requesting slice, and reports to the requesting application function AF after receiving the information reported by each NSACF.
  • the NEF may query the NSACF(s) corresponding to the access type information of the slice request through the NRF, or discover and select the NSACF(s) corresponding to the access type information of the slice request through local configuration.
  • Step 144 NEF sends Nnef_SliceEventExposure_Subscribe or Unsubscribe request message to NSACF.
  • the NEF initiates a subscription request to the NSACF that supports the Requested S-NSSAI request access type information, Send Nnef_SliceEventExposure_Subscribe/Unsubscribe request message, the message includes event ID, event filter, event report information, etc.
  • the NEF stores event report information requested by the AF.
  • the NEF can set the time report information as a periodic report in the subscription request to each NSACF. If the Requested S-NSSAI is performed by a single NSACF for UE slice admission control, the event report information set by the NEF itself is the same as the request received from the AF. At the same time, the NEF will set the event ID and event filter information according to the content in the request message received by the AF.
  • Step 145 NSACF sends Nnsacf_SliceEventExposure_Subscribe or usubsubscribe response message to NEF to confirm the subscription request.
  • Step 146 when the subscribed report condition is satisfied and the report event is triggered, the NSACF sends a trigger notification to the NEF, and executes the report of the information related to the subscription event.
  • Step 147 NSACF sends Nnsacf_SliceEvent Exposure_Notify message to NEF, the message carries event ID, event filter, event report information and other parameters.
  • Step 148 execute message aggregation.
  • NEF collects the reports of all NFACFs corresponding to the requested access type, and executes slice S-NSSAI in the requested event filter (such as 3GPP/non-3GPP access type) aggregation of the number.
  • slice S-NSSAI such as 3GPP/non-3GPP access type
  • the NEF performs the reporting of the number of slice S-NSSAIs in the requested event filter (such as 3GPP/non-3GPP access type).
  • NEF When the requested NSSAI request access type information corresponds to a single NSACF to perform UE slice admission control, NEF immediately returns a report notification to AF, reports its own statistical usage report, or performs periodic reporting to AF according to periodic subscription.
  • Step 149 NEF sends Nnef_SliceEventExposure_Notify notification message to AF, and the notification message includes event report information.
  • the subscription report is triggered.
  • the NEF sends a notification to the AF to report the subscription-related usage and information according to the subscription requirements, such as the number of UEs of the 3GPP access type of the slice, the number of UEs of the non-3GPP access type of the slice, or the 3GPP access type of the slice The number of UEs corresponding to internal satellite access, etc., or the proportion of the corresponding number of UEs to the maximum allowed number reported at the same time.
  • NEF executes the request for mapping between the AF application or service identifier and the slice identifier; in the first step, when the NEF receives the AF subscription request, it will The application or service identifier is mapped to a slice identifier and sent to the NSACF; when the NEF receives the subscription event notification from the NSACF, it maps the slice identifier to the application or service identifier and sends it to the AF.
  • an embodiment of the present disclosure provides a device for determining the number of registered users, wherein the device includes:
  • a determining module 151 configured to determine the number of registered users for different access types based on the access type information
  • the access type information indicates an access type for the terminal to access the network slice. It should be noted that those skilled in the art can understand that the methods provided in the embodiments of the present disclosure may be executed independently, or together with some methods in the embodiments of the present disclosure or some methods in related technologies.
  • an embodiment of the present disclosure provides a device for determining the number of registered users, wherein the device includes:
  • a receiving module 162 configured to receive a response message sent by the first network device in response to the slice user quantity update request message, wherein the response message carries that the number of registered users of the access type of the slice reaches a predetermined threshold information and/or number of registered users.
  • an embodiment of the present disclosure provides a device for determining the number of registered users, wherein the device includes:
  • the sending module 171 is configured to send a slice event subscription request indicating an access type to the first network device; wherein, the slice event subscription request is used to obtain an event report of the access type; The number of registered users associated with the type of access indicated in the request;
  • the receiving module 172 is configured to receive the event report sent by the first network device in response to the slice event subscription request.
  • An embodiment of the present disclosure provides a communication device, which includes:
  • memory for storing processor-executable instructions
  • the processor is configured to implement the method applied to any embodiment of the present disclosure when executing the executable instructions.
  • the processor may include various types of storage media, which are non-transitory computer storage media, and can continue to memorize and store information thereon after the communication device is powered off.
  • the processor can be connected to the memory through a bus or the like, and is used to read the executable program stored in the memory.
  • An embodiment of the present disclosure further provides a computer storage medium, wherein the computer storage medium stores a computer executable program, and when the executable program is executed by a processor, the method of any embodiment of the present disclosure is implemented.
  • an embodiment of the present disclosure provides a terminal structure.
  • this embodiment provides a terminal 800, which specifically can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc. .
  • the terminal 800 may include one or more of the following components: a processing component 802, a memory 804, a power supply component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communication component 816 .
  • the processing component 802 generally controls the overall operations of the terminal 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • the processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above method. Additionally, processing component 802 may include one or more modules that facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802 .
  • the memory 804 is configured to store various types of data to support operations at the device 800 . Examples of such data include instructions for any application or method operating on the terminal 800, contact data, phonebook data, messages, pictures, videos, etc.
  • the memory 804 can be implemented by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Magnetic or Optical Disk Magnetic Disk
  • the power supply component 806 provides power to various components of the terminal 800 .
  • Power components 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for terminal 800 .
  • the multimedia component 808 includes a screen providing an output interface between the terminal 800 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user.
  • the touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or a swipe action, but also detect duration and pressure associated with the touch or swipe operation.
  • the multimedia component 808 includes a front camera and/or a rear camera. When the device 800 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capability.
  • the audio component 810 is configured to output and/or input audio signals.
  • the audio component 810 includes a microphone (MIC), which is configured to receive an external audio signal when the terminal 800 is in an operation mode, such as a call mode, a recording mode and a voice recognition mode. Received audio signals may be further stored in memory 804 or sent via communication component 816 .
  • the audio component 810 also includes a speaker for outputting audio signals.
  • the I/O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: a home button, volume buttons, start button, and lock button.
  • Sensor component 814 includes one or more sensors for providing terminal 800 with various aspects of status assessment.
  • the sensor component 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and the keypad of the terminal 800, the sensor component 814 can also detect the terminal 800 or a change in the position of a component of the terminal 800, and the user The presence or absence of contact with the terminal 800, the terminal 800 orientation or acceleration/deceleration and the temperature change of the terminal 800.
  • Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact.
  • Sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.
  • the communication component 816 is configured to facilitate wired or wireless communication between the terminal 800 and other devices.
  • the terminal 800 can access a wireless network based on communication standards, such as Wi-Fi, 2G or 3G, or a combination thereof.
  • the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication.
  • NFC near field communication
  • the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID Radio Frequency Identification
  • IrDA Infrared Data Association
  • UWB Ultra Wideband
  • Bluetooth Bluetooth
  • terminal 800 may be programmed by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation for performing the methods described above.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor or other electronic component implementation for performing the methods described above.
  • non-transitory computer-readable storage medium including instructions, such as the memory 804 including instructions, which can be executed by the processor 820 of the terminal 800 to complete the above method.
  • the non-transitory computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
  • an embodiment of the present disclosure shows a structure of a base station.
  • the base station 900 may be provided as a network side device.
  • base station 900 includes processing component 922 , which further includes one or more processors, and a memory resource represented by memory 932 for storing instructions executable by processing component 922 , such as application programs.
  • the application program stored in memory 932 may include one or more modules each corresponding to a set of instructions.
  • the processing component 922 is configured to execute instructions, so as to perform any of the aforementioned methods applied to the base station.
  • Base station 900 may also include a power component 926 configured to perform power management of base station 900, a wired or wireless network interface 950 configured to connect base station 900 to a network, and an input-output (I/O) interface 958.
  • the base station 900 can operate based on an operating system stored in the memory 932, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or similar.

Landscapes

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

Abstract

本公开实施例提供了一种确定注册用户数量的方法，其中，所述方法由第一网络设备执行，所述方法包括：基于接入类型信息，确定针对不同接入类型的注册用户数量；其中，所述接入类型信息指示终端接入网络切片的接入类型。

Description

确定注册用户数量的方法、装置、通信设备及存储介质 技术领域
本公开涉及无线通信技术领域但不限于无线通信技术领域，尤其涉及一种确定注册用户数量的方法、装置、通信设备及存储介质。
背景技术
网络切片可以提供完整的网络功能，如无线电接入网络功能、核心网络功能和网际互连协议(IP，Internet Protocol)多媒体系统功能等。网络可以支持一个或多个网络切片。网络切片可以提供不同的承诺服务且专用于用户。
在相关技术中，网络切片中包含多种接入类型的注册用户。在网络切片内会执行全部接入类型的统计，这种统计方式并不能精准定位和满足运营业务的需求，尤其是在特定场景下的业务特性需求，也就无法针对网络状态相应地配置资源、触发和执行相关业务，甚至提升用户业务体验。
发明内容
本公开实施例公开了一种确定注册用户数量的方法、装置、通信设备及存储介质。
根据本公开实施例的第一方面，提供一种确定注册用户数量的方法，其中，所述方法由第一网络设备执行，所述方法包括：
基于接入类型信息，确定针对不同接入类型的注册用户数量；
其中，所述接入类型信息指示终端接入网络切片的接入类型。
在一个实施例中，所述接入类型信息，包括以下至少一项：
配置在第一网络设备上的接入类型信息；
从消费者网络功能获取的接入类型信息；
操作维护管理系统OAM配置的接入类型信息；
从访问和移动性管理功能AMF获取的接入类型信息。
在一个实施例中，所述接入类型信息指示以下至少一种：
接入类型Access Type；
无线接入类型RAT Radio Access Type；
接入辅助信息addAccessInfo。
在一个实施例中，所述接入类型包括以下至少一种：
第三代移动通信伙伴项目3GPP接入；
非3GPP接入；
3GPP和非3GPP接入。
在一个实施例中，所述无线接入类型包括以下至少一种：新空口接入NR、演进的通用移动通信系统陆面无线接入EUTRA、无线局域网接入WLAN、虚拟网接入VIRTUAL、窄带物联网接入NBIOT、有线网接入WIRELINE、有线电缆网接入WIRELINE_CABLE、有线宽带网接入WIRELINE_BBF、城市轨道交通车地综合通信系统接入LTE-M、新空口非许可频谱接入NR_U、演进的通用移动通信系统陆面非许可频谱无线接入EUTRA_U、可信任N3GA接入TRUSTED_N3GA、可信任无线局域网接入TRUSTED_WLAN、通用陆地无线接入UTRA、全球移动通信系统边缘无线接入网络接入GERA、新空口低轨道接入NR_LEO、新空口中高轨道接入NR_MEO、新空口静止地球轨道接入NR_GEO以及其他卫星接入NR_OTHER_SAT。
在一个实施例中，所述方法还包括：
响应于终端执行预定流程，更新针对不同所述接入类型的注册用户数量；
其中，所述预定流程包括以下之一：
终端的注册流程；
终端的配置更新流程；
终端的去注册流程。
在一个实施例中，所述响应于终端执行预定流程，更新针对不同所述接入类型的注册用户数量，包括：
响应于终端执行预定流程且接收到第二网络设备发送的切片用户数量更新请求消息，更新针对不同所述接入类型的注册用户数量；
其中，所述切片用户数量更新请求消息指示：增加或者减少所述注册用户数量。
在一个实施例中，所述方法还包括：
向所述第二网络设备发送针对所述切片用户数量更新请求消息的响应消息；
其中，所述响应消息携带所述接入类型的注册用户数量达到预定阈值的信息和/或与接入类型关联的注册用户数量。
在一个实施例中，所述方法还包括：
响应于接收到应用功能AF发送的指示接入类型的切片事件订阅请求，向所述AF发送所述接入类型的事件报告；其中，所述事件报告至少指示与接入类型关联的注册用户数量。
根据本公开实施例的第二方面，提供一种确定注册用户数量的方法，其中，所述方法由第二网络设备执行，所述方法包括：
向第一网络设备发送切片用户数量更新请求消息；
接收所述第一网络设备发送的响应消息，其中，所述响应消息携带切片的不同接入类型的注册用户数量达到预定阈值的信息和/或不同接入类型的注册用户数量。
在一个实施例中，所述接入类型包括以下至少一种：
第三代移动通信伙伴项目3GPP接入；
非3GPP接入；
3GPP和非3GPP接入。
在一个实施例中，所述无线接入类型包括以下至少一种：新空口接入NR、演进的通用移动通信系统陆面无线接入EUTRA、无线局域网接入WLAN、虚拟网接入VIRTUAL、窄带物联网接入NBIOT、有线网接入WIRELINE、有线电缆网接入WIRELINE_CABLE、有线宽带网接入WIRELINE_BBF、城市轨道交通车地综合通信系统接入LTE-M、新空口非许可频谱接入NR_U、演进的通用移动通信系统陆面非许可频谱无线接入EUTRA_U、可信任N3GA接入TRUSTED_N3GA、可信任无线局域网接入TRUSTED_WLAN、通用陆地无线接入UTRA、全球移动通信系统边缘无线接入网络接入GERA、新空口低轨道接入NR_LEO、新空口中高轨道接入NR_MEO、新空口静止地球轨道接入NR_GEO以及其他卫星接入NR_OTHER_SAT。
在一个实施例中，所述方法还包括：
接收终端发送的注册请求消息；
根据所述注册用户数量，确定是否拒绝终端的所述注册请求消息。
在一个实施例中，所述根据所述注册用户数量，确定是否拒绝终端的所述注册请求消息，包括：
响应于请求的部分网络切片的所述注册用户数量达到所述预定阈值，确定接受终端的所述注册请求消息；
或者，
响应于请求的全部网络切片的所述注册用户数量达到所述预定阈值且配置有备用网络切片，确定接受终端的所述注册请求消息；
或者，
响应于请求的全部网络切片的所述注册用户数量达到所述预定阈值且未配置备用网络切片，确定拒绝终端的所述注册请求消息。
根据本公开实施例的第三方面，提供一种确定注册用户数量的方法，其中，所述方法由第三网络设备执行，所述方法包括：
向第一网络设备发送指示接入类型的切片事件订阅请求；其中，所述切片事件订阅请求用于获取所述接入类型的事件报告；所述事件报告至少指示与切片事件订阅请求指示的接入类型关联的注册用户数量；
接收第一网络设备针对所述切片事件订阅请求发送的所述事件报告。
在一个实施例中，所述接入类型包括以下至少一种：
第三代移动通信伙伴项目3GPP接入；
非3GPP接入；
3GPP和非3GPP接入。
在一个实施例中，所述无线接入类型包括以下至少一种：新空口接入NR、演进的通用移动通信系统陆面无线接入EUTRA、无线局域网接入WLAN、虚拟网接入VIRTUAL、窄带物联网接入NBIOT、有线网接入WIRELINE、有线电缆网接入WIRELINE_CABLE、有线宽带网接入WIRELINE_BBF、城市轨道交通车地综合通信系统接入LTE-M、新空口非许可频谱接入NR_U、演进的通用移动通信系统 陆面非许可频谱无线接入EUTRA_U、可信任N3GA接入TRUSTED_N3GA、可信任无线局域网接入TRUSTED_WLAN、通用陆地无线接入UTRA、全球移动通信系统边缘无线接入网络接入GERA、新空口低轨道接入NR_LEO、新空口中高轨道接入NR_MEO、新空口静止地球轨道接入NR_GEO以及其他卫星接入NR_OTHER_SAT。
根据本公开实施例的第四方面，提供一种确定注册用户数量的装置，其中，所述装置包括：
确定模块，用于基于接入类型信息，确定针对不同接入类型的注册用户数量；
其中，所述接入类型信息指示与网络切片关联的接入类型。
根据本公开实施例的第五方面，提供一种确定注册用户数量的装置，其中，所述装置包括：
发送模块，用于向第一网络设备发送切片用户数量更新请求消息；
接收模块，用于接收所述第一网络设备针对所述切片用户数量更新请求消息发送的响应消息，其中，所述响应消息携带所述切片的所述接入类型的注册用户数量达到预定阈值的信息和/或注册用户数量。
根据本公开实施例的第六方面，提供一种确定注册用户数量的装置，其中，所述装置包括：
发送模块，用于向第一网络设备发送指示接入类型的切片事件订阅请求；其中，所述切片事件订阅请求用于获取接入类型的事件报告；所述事件报告至少指示与切片事件订阅请求指示的接入类型关联的注册用户数量；
接收模块，用于接收第一网络设备针对所述切片事件订阅请求发送的所述事件报告。
根据本公开实施例的第七方面，提供一种通信设备，所述通信设备，包括：
处理器；
用于存储所述处理器可执行指令的存储器；
其中，所述处理器被配置为：用于运行所述可执行指令时，实现本公开任意实施例所述的方法。
根据本公开实施例的第八方面，提供一种计算机存储介质，所述计算机存储介质存储有计算机可执行程序，所述可执行程序被处理器执行时实现本公开任意实施例所述的方法。
在本公开实施例中，基于接入类型信息，确定针对不同接入类型的注册用户数量；其中，所述接入类型信息指示终端接入网络切片的接入类型。这里，由于注册用户数量是基于终端接入网络切片的接入类型进行确定的，即可以确定不同接入类型的注册用户数量，相较于只能确定所有接入类型的总注册用户数量的方式，以单个接入类型为单位确定不同接入类型对应的注册用户数量能够更加精准地确定单个接入类型对应的注册用户数量，从而可以基于所述单个接入类型对应的注册用户数量配置资源、触发和执行相关业务，更好地满足用户的需求。
附图说明
图1是根据一示例性实施例示出的一种无线通信系统的结构示意图。
图2是根据一示例性实施例示出的一种确定注册用户数量的方法的流程示意图。
图3是根据一示例性实施例示出的一种确定注册用户数量的方法的流程示意图。
图4是根据一示例性实施例示出的一种确定注册用户数量的方法的流程示意图。
图5是根据一示例性实施例示出的一种确定注册用户数量的方法的流程示意图。
图6是根据一示例性实施例示出的一种确定注册用户数量的方法的流程示意图。
图7是根据一示例性实施例示出的一种确定注册用户数量的方法的流程示意图。
图8是根据一示例性实施例示出的一种确定注册用户数量的方法的流程示意图。
图9是根据一示例性实施例示出的一种确定注册用户数量的方法的流程示意图。
图10是根据一示例性实施例示出的一种确定注册用户数量的方法的流程示意图。
图11是根据一示例性实施例示出的一种确定注册用户数量的方法的流程示意图。
图12是根据一示例性实施例示出的一种确定注册用户数量的方法的流程示意图。
图13是根据一示例性实施例示出的一种确定注册用户数量的方法的流程示意图。
图14是根据一示例性实施例示出的一种确定注册用户数量的方法的流程示意图。
图15是根据一示例性实施例示出的一种确定注册用户数量的装置的结构示意图。
图16是根据一示例性实施例示出的一种确定注册用户数量的装置的结构示意图。
图17是根据一示例性实施例示出的一种确定注册用户数量的装置的结构示意图。
图18是根据一示例性实施例示出的一种终端的结构示意图。
图19是根据一示例性实施例示出的一种基站的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
出于简洁和便于理解的目的，本文在表征大小关系时，所使用的术语为“大于”或“小于”。但对于本领域技术人员来说，可以理解：术语“大于”也涵盖了“大于等于”的含义，“小于”也涵盖了“小于等于”的含义。
请参考图1，其示出了本公开实施例提供的一种无线通信系统的结构示意图。如图1所示，无线通信系统是基于移动通信技术的通信系统，该无线通信系统可以包括：若干个用户设备110以及若干个基站120。
其中，用户设备110可以是指向用户提供语音和/或数据连通性的设备。用户设备110可以经无线 接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，用户设备110可以是物联网用户设备，如传感器设备、移动电话和具有物联网用户设备的计算机，例如，可以是固定式、便携式、袖珍式、手持式、计算机内置的或者车载的装置。例如，站(Station，STA)、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点、远程用户设备(remote terminal)、接入用户设备(access terminal)、用户装置(user terminal)、用户代理(user agent)、用户设备(user device)、或用户设备(user equipment)。或者，用户设备110也可以是无人飞行器的设备。或者，用户设备110也可以是车载设备，比如，可以是具有无线通信功能的行车电脑，或者是外接行车电脑的无线用户设备。或者，用户设备110也可以是路边设备，比如，可以是具有无线通信功能的路灯、信号灯或者其它路边设备等。
基站120可以是无线通信系统中的网络侧设备。其中，该无线通信系统可以是5G系统，又称新空口系统或5G NR系统。或者，该无线通信系统也可以是5G系统的再下一代系统。其中，5G系统中的接入网可以称为NG-RAN(New Generation-Radio Access Network，新一代无线接入网)。
其中，基站120可以是4G系统中采用的演进型基站(eNB)。或者，基站120也可以是5G系统中采用集中分布式架构的基站(gNB)。当基站120采用集中分布式架构时，通常包括集中单元(central unit，CU)和至少两个分布单元(distributed unit，DU)。集中单元中设置有分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制协议(Radio Link Control，RLC)层、媒体访问控制(Media Access Control，MAC)层的协议栈；分布单元中设置有物理(Physical，PHY)层协议栈，本公开实施例对基站120的具体实现方式不加以限定。
基站120和用户设备110之间可以通过无线空口建立无线连接。该无线空口是基于第五代移动通信网络技术(5G)标准的无线空口，比如该无线空口是新空口；或者，该无线空口也可以是基于5G的更下一代移动通信网络技术标准的无线空口。
在一些实施例中，用户设备110之间还可以建立E2E(End to End，端到端)连接。比如车联网通信(vehicle to everything，V2X)中的V2V(vehicle to vehicle，车对车)通信、V2I(vehicle to Infrastructure，车对路边设备)通信和V2P(vehicle to pedestrian，车对人)通信等场景。
这里，上述用户设备可认为是下面实施例的终端设备。
在一些实施例中，上述无线通信系统还可以包含网络管理设备130。
若干个基站120分别与网络管理设备130相连。网络管理设备130可以是无线通信系统中的核心网设备，比如，接入和移动性管理功能(AMF，Access and Mobility Management Function)、会话管理功能(SMF，Session Management Function)、用户面功能(UPF，User Plane Function)、策略控制功能(PCF，Policy Control Function)、网络存储功能(NRF，Network Repository Function)等，对于网络管理设备130的实现形态，本公开实施例不做限定。
为了便于本领域内技术人员理解，本公开实施例列举了多个实施方式以对本公开实施例的技术方案进行清晰地说明。当然，本领域内技术人员可以理解，本公开实施例提供的多个实施例，可以被单独执行，也可以与本公开实施例中其他实施例的方法结合后一起被执行，还可以单独或结合后与其他相关技术中的一些方法一起被执行；本公开实施例并不对此作出限定。
为了更好地理解本公开任一个实施例所描述的技术方案，首先，对相关技术中网络切片的应用场景进行说明：
在一个实施例中，移动网络运营商部署的多个网络切片可以提供完全相同的功能。但是，针对不同的终端组，因为提供了不同的承诺服务，此类网络切片可能具有相同切片不同的单一网络切片选择辅助信息(S-NSSAI，Single Network Slice Selection Assistance Information)或相同服务类型不同的切片区分符。
在一个实施例中，终端的一组网络切片实例的选择通常是通过与网络切片选择功能(NSSF，Network Slice Selection Function)交互，由注册过程中的第一个联系的访问和移动性管理功能(AMF，Access and Mobility Management Function)触发，并且可能导致AMF的更改。每个公共陆地移动网(PLMN，Public Land Mobile Network)，协议数据单元(PDU，Protocol Data Unit)会话属于一个且只有一个特定的网络切片实例。尽管不同的网络切片实例可能具有使用相同数据网络名(DNN，Data Network Name)的特定切片的PDU会话，但不同的网络切片实例不共享PDU会话。在切换过程中，源AMF通过与网络注册功能(NRF，NF Repository Function)交互来选择目标AMF。
在一个实施例中，网络切片类型(NEST，Generic Network Slice Template)应用于网络切片，通常网络切片由多个网络切片实例支持。通用网络切片模板(GST，Network Slice Type)定义网络切片支持的属性。
在一个实施例中，网络切片接纳控制功能(NSACF，Network Slice Admission Control function)，用于监控支持NSAC功能的网络切片的注册终端终端数和PDU会话数。NSACF还配置了执行NSAC功能的S-NSSAI的接入类型信息。
在一个实施例中，每个NSACF配置网络切片允许接入的最大终端数量和允许激活的最大PDU会话数量。NSACF支持PLMN内的最大终端数和最大PDU会话数的监控和接纳控制。注册到当前切片的终端数量超出某个阈值(比如，切片最大终端数)，则NSAC会拒绝终端注册以控制服务的终端数不超出网络配置的切片最大终端数。当切片内激活的PDU会话数，超出某个阈值(例如，激活会话最大数)，则NSAC会拒绝PDU会话的激活，以控制当前的会话数不超出网络配置的最大会话数量。
在一个实施例中，运营商网络中可能部署多个NSACF。一个NSACF可以为一个服务区域的一个或多个服S-NSSAI切片服务。在一个服务区域内，一个S-NSSAI只由一个NSACF处理，可以是一个NSACF实例，也可以是一个NSACF集。一个PLMN可以有一个或多个服务区域。
在一个实施例中，应用功能(AF，Application Function)存在基于用户体验的保障或提升需求获取网络切片的状态信息的需求，比如，切片中当前的注册用户数、当前激活的PDU会话数、切片当前的注册用户数和/或激活PDU会话数占切片整体阈值的比例等信息。
相关技术中，不同接入方式的计费模式和费率不同，由此，不同接入方式的用户数的比例对于实际的网络切片状态信息的影响日渐显著。比如，对于不同时间或业务类型，不同接入方式的用户数差异显著。但是，网络基础设施和资源配置相对稳定，运营商或应用提供商如何进一步获取切片的注册用户数等详细信息和实时网络状况，进一步实现资源弹性配置和更好的业务体验，以及实现相关网络能力开放 的执行和优化，当前网络切片相关功能特性无法满足这类运营和业务需求。
因此，如何进一步获取切片注册用户数等相关参数的详细网络状态信息和实时网络状况，进一步实现资源弹性配置和更好的业务体验，以及实现相关网络能力开放的执行和优化，依然是无线网络中尚待解决的问题。
如图2所示，本实施例中提供一种确定注册用户数量的方法，其中，该方法由第一网络设备执行，所述方法包括：
步骤21、基于接入类型信息，确定针对不同接入类型的注册用户数量；
其中，接入类型信息指示终端接入网络切片的接入类型。
这里，本公开所涉及的终端可以是但不限于是手机、可穿戴设备、车载终端、路侧单元(RSU，Road Side Unit)、智能家居终端、工业用传感设备和/或医疗设备等。本公开中，注册用户数量也可以有“注册终端数量”的含义。本公开中，切片也可以有“网络切片或者网络切片实例”的含义。
本公开中涉及的第一网络设备可以是NSACF。需要说明的是，本公开中的第一网络设备并不限于NSACF，也可以是核心网中的其他通信节点，在此不做限定。这里，针对每个网络切片可以部署一个NSACF，也可以针对每个网络切片部署多个NSACF。如果针对每个网络切片部署有多个NSACF，则本公开所涉及的NSACF为该多个NSACF中的某个NSACF。类似地，示例性地，本公开中的第二网络设备可以是AMF，但本公开中的第二网络设备并不限于AMF，也可以是核心网中的其他通信节点。本公开中的第三网络设备可以是AF。
需要说明的是，本公开中确定针对不同接入类型的注册用户数量，可以包括：统计针对不同接入类型的注册用户数量。
这里，接入类型信息指示以下至少一种：
接入类型(Access Type)；
无线接入类型(RAT Radio Access Type)；
接入类型辅助信息。
应理解，接入类型指示信息可以包括接入类型、无线接入类型以及接入类型辅助信息中的至少一项，其中，接入类型辅助信息包括接入类型和无线接入类型。
在一个实施例中，接入类型包括以下至少之一：3GPP接入、非3GPP接入、3GPP和非3GPP接入。
在一个实施例中，无线接入类型包括以下至少之一：NR接入、EUTRA接入、WLAN接入、VIRTUAL接入、NBIOT接入、WIRELINE接入、WIRELINE_CABLE接入、WIRELINE_BBF接入、LTE-M接入、NR_U接入、EUTRA_U接入、TRUSTED_N3GA接入、TRUSTED_WLAN接入、UTRA接入、GERA接入、NR_LEO接入、NR_MEO接入、NR_GEO接入以及NR_OTHER_SAT接入。
在一些实施例中，接入类型信息可以是配置在NSACF上；或者，NSACF可以是从消费者网络功能获取接入类型信息；或者，从操作维护管理系统(OAM,Operation Administration and Maintenance)获取接入类型信息。需要说明的是，消费者网络功能可以包括以下之一：网络开放功能(NEF，Network Exposure Function)、策略决策功能(PCF，Policy Control Function)、多个NSACF部署场景时的主NSACF 以及操作维护管理系统OAM。
需要说明的是，不同接入类型的注册用户数量可以是多个接入类型的注册用户数量也可以是单个接入类型的注册用户数量。
在一个实施例中，在终端的注册流程中，基于接入类型信息，确定针对不同接入类型的注册用户数量；其中，接入类型信息指示终端接入网络切片的接入类型。如此，可以统计出不同接入类型的注册用户数量。
在一个实施例中，在终端的配置更新流程中，基于接入类型信息，确定针对不同接入类型的注册用户数量；其中，接入类型信息指示终端接入网络切片的接入类型。如此，可以统计出不同接入类型的注册用户数量。
在一个实施例中，在终端的去注册流程中，基于接入类型信息，确定针对不同接入类型的注册用户数量；其中，接入类型信息指示终端接入网络切片的接入类型。如此，可以统计出不同接入类型的注册用户数量。
在一些实施例中，这里的接入类型可以是终端当前接入网络切片的接入类型。或者，接入类型可以是网络切片需要执行NSAC统计的接入类型。
在一个实施例中，基于终端接入网络切片的接入类型，确定网络切片的每个接入类型的注册用户数量。如此，可以统计出不同接入类型的注册用户数量。
在一个实施例中，在确定针对不同接入类型的注册用户数量之前，可以更新针对不同接入类型的注册用户数量。如此，可以及时进行更新。
在一个实施例中，在终端的注册流程中，根据是否开启了早期有效性检查EAC模式，在传输注册接受消息之前或者之后执行针对不同接入类型的注册用户数量更新。这里，注册流程包括初始注册或者跨AMF切换导致的移动注册更新类型的注册过程。
示例性地，在EAC激活状态下，在传输注册接受消息前执行针对不同接入类型的注册用户数量更新；或者，在EAC未激活状态下，在传输注册接受消息之后执行针对不同接入类型的注册用户数量更新。
在一个实施例中，在终端的去注册流程中，在去注册流程结束后，执行针对不同接入类型的注册用户数量更新。
在一个实施例中，在终端的配置更新流程中，如果NSSAA切片特定的鉴权认证流程或者签约S-NSSAI变更流程触发了配置更新，则根据EAC模式在配置更新消息前执行针对不同接入类型的注册用户数量更新。示例性地，如果EAC模式被激活且更新标志指示增加数目，则在终端配置更新消息前执行针对不同接入类型的注册用户数量更新；或者，如果EAC模式被激活但更新标识指示减少数目，在终端配置更新消息后执行针对不同接入类型的注册用户数量更新；或者，如果EAC模式未被激活，在终端配置更新消息后执行针对不同接入类型的注册用户数量更新。
需要说明的是，更新注册用户数量可以是增加或者减少注册用户数量。
在一个实施例中，请参见图5，步骤52中，NSACF可以接收AMF发送的请求消息(例如，Nnsacf_NSAC_NumOfUEsUpdate_Request)，其中，该请求消息包括更新标识。这里，更新标识指示注 册用户的数量增加或者减少。示例性地，当用户注册到该切片时，更新标识指示注册用户的数量增加；或者，当用户从该切片中去注册或者注册无法继续时，更新标识指示注册用户的数量减少。
需要说明的是，请求消息还可以指示终端标识、接入类型、请求执行NSAC的相关切片S-NSSAIs和/或AMF标识等。这里，接入类型的信息，可以是由AMF本地生成的，也可以是从基站发送给AMF的请求消息中获取的。
在一个实施例中，针对切片，在AMF和NSACF首次交互执行更新时，AMF会在请求消息中携带早期有效性检查EAC需要通知到的相关节点NF信息，如此，通过此方式隐式地从NSACF订阅切片的EAC相关通知。
在一个实施例中，NSACF还配置有切片基于接入类型的允许的最大注册用户数量。当针对切片基于接入类型执行注册用户数量更新时，如果切片在该一个或者多个接入类型内达到了最大注册用户数，NSACF在返回给AMF的响应消息中携带数量达到最大用户数量的信息。需要说明的是，如果从AMF接收到EAC通知端点信息，NSACF存储与S-NSSAI关联的EAC通知端点信息，以便于后续使用存储的通知端点来更新EAC模式。
在一个实施例中，请再次参见图5，步骤54中，NSACF针对请求消息向AMF发送响应消息(例如，Nnsacf_NSAC_NumOfUEsUpdate_Response)，其中，响应消息中携带有终端接入切片的接入类型所注册用户数量达到设定阈值或者最大值的切片标识S-NSSAI(s)以及指示已经达到最大值的相关结果参数。
在一个实施例中，在终端注册流程中，在AMF接收到响应消息后，如果只有请求的部分切片达到最大注册用户数量，AMF会给注册终端发送一个注册接受消息。在注册接受消息中，在拒绝切片列表中携带因为更新被拒绝的切片标识，且相应的拒绝原因设定为切片该区域内的最大用户数量已到达。在一个实施例中，可以设置一个可发起重新请求的定时器。
在一个实施例中，当AMF发送给NSACF的请求消息中，所请求的全部切片S-NSSAI(s)都到了允许的最大值，且签约信息中如果有一个或多个签约切片标注为缺省切片，且同时不需要执行更新，则AMF可能会决策将这些缺省切片放入Allow NSSAI，作为授权允许切片。否则，AMF将会拒绝该用户UE的注册请求(比如，该接入类型的注册请求)。在注册拒绝消息中，AMF携带拒绝切片标识列表，每个切片带上相应的拒绝原因值，例如，切片该区域内的允许的最大注册用户数量已到达。在一个实施例中，设置一个可发起重新请求的定时器。
本公开实施例中，基于接入类型信息，确定针对不同接入类型的注册用户数量；其中，接入类型信息指示终端接入网络切片的接入类型。这里，由于注册用户数量是基于终端接入网络切片的接入类型进行确定的，即可以确定不同接入类型的注册用户数量，相较于只能确定所有接入类型的总注册用户数量的方式，以单个接入类型为单位确定不同接入类型对应的注册用户数量能够更加精准地确定单个接入类型对应的注册用户数量，从而可以基于单个接入类型对应的注册用户数量配置资源、触发和执行相关业务，更好地满足用户的需求。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
在一个实施例中，接入类型包括以下至少一种：
第三代移动通信伙伴项目3GPP接入；
非3GPP接入；
3GPP和非3GPP接入。
在一个实施例中，所述无线接入类型包括以下至少一种：新空口接入NR、演进的通用移动通信系统陆面无线接入EUTRA、无线局域网接入WLAN、虚拟网接入VIRTUAL、窄带物联网接入NBIOT、有线网接入WIRELINE、有线电缆网接入WIRELINE_CABLE、有线宽带网接入WIRELINE_BBF、城市轨道交通车地综合通信系统接入LTE-M、新空口非许可频谱接入NR_U、演进的通用移动通信系统陆面非许可频谱无线接入EUTRA_U、可信任N3GA接入TRUSTED_N3GA、可信任无线局域网接入TRUSTED_WLAN、通用陆地无线接入UTRA、全球移动通信系统边缘无线接入网络接入GERA、新空口低轨道接入NR_LEO、新空口中高轨道接入NR_MEO、新空口静止地球轨道接入NR_GEO以及其他卫星接入NR_OTHER_SAT。
如图4所示，本实施例中提供一种确定注册用户数量的方法，其中，该方法由第一网络设备执行，所述方法包括：
步骤41、响应于终端执行预定流程，更新不同所述接入类型的注册用户数量；
其中，所述预定流程包括以下之一：
终端的注册流程；
终端的配置更新流程；
终端的去注册流程。
也就是说，确定以及更新不同所述接入类型的注册用户数量可以在上述场景中触发。
在一个实施例中，在终端的注册流程中，根据是否开启了早期有效性检查EAC模式，在传输注册接受消息之前或者之后执行针对不同接入类型的注册用户数量更新。这里，注册流程包括初始注册或者跨AMF切换导致的移动注册更新类型的注册过程。示例性地，在EAC激活状态下，在传输注册接受消息前执行针对不同接入类型的注册用户数量更新；或者，在EAC未激活状态下，在传输注册接受消息之后执行针对不同接入类型的注册用户数量更新。
在一个实施例中，在终端的去注册流程中，在去注册流程结束后，执行针对不同接入类型的注册用户数量更新。
在一个实施例中，在终端的配置更新流程中，如果NSSAA切片特定的鉴权认证流程或者签约S-NSSAI变更流程触发了配置更新，则根据EAC模式在配置更新消息前执行针对不同接入类型的注册用户数量更新。示例性地，如果EAC模式被激活且更新标志指示增加数目，则在终端配置更新消息前执行针对不同接入类型的注册用户数量更新；或者，如果EAC模式被激活但更新标识指示减少数目，在终端配置更新消息后执行针对不同接入类型的注册用户数量更新；或者，如果EAC模式未被激活，在终端配置更新消息后执行针对不同接入类型的注册用户数量更新。
需要说明的是，更新注册用户数量可以是增加或者减少相应接入类型或无线接入类型的注册用户数量。
示例性地，请参见图5，在注册流程中，包括：
步骤51、终端在注册流程中，终端向网络发起到某个或某些网络切片的注册流程。这里，可以是终端向AMF发送注册请求消息；该注册请求消息可以携带切片标识和NSACF特性等参数。AMF基于切片标识和NSACF特性等参数，执行NSACF的发现和选择。触发注册UE对于网络切片基于接入类型的有效性检查和更新流程，这里，该有效性检查和更新流程包括：基于接入类型信息，确定针对不同接入类型的注册用户数量。
步骤52、AMF向NSACF发送Nnsacf_NSAC_NumOfUEsUpdate_Request。
步骤53、NSACF基于接入类型信息，确定针对不同接入类型的注册用户数量。这里，可以是检查和更新针对不同接入类型的注册用户数量。
步骤54、NSACF向AMF发送Nnsacf_NSAC_NumOfUEsUpdate_Response。这里，该Nnsacf_NSAC_NumOfUEsUpdate_Response包括NSACF确定的针对不同接入类型的注册用户数量。
步骤55、AMF向终端发送注册请求拒绝消息。示例性地，如果所有请求执行NSAC的切片都到达了最大值(在该基于接入类型的内到达了最大值，且在该切片内相应接入类型的其它NSACF也没新阈值可更新或补充)，且根据AMF配置和其它策略信息，比如没有其它可授权的缺省切片，也没有在执行NSSAA切片特定鉴权认证流程中的切片，则AMF将拒绝该UE通过该接入类型注册到相关网络切片，发送拒绝注册消息同时携带相关拒绝原因值，比如阈值到达等。否则，执行步骤56。
步骤56、AMF向终端发送注册请求接受消息。
示例性地，请参见图6，在去注册流程中，包括：
步骤61、终端已注册，终端或者网络触发去注册流程。
步骤62、终端向AMF发送去注册请求。
步骤63、执行去注册流程且去注册流程完成。
步骤64、AMF向终端发送去注册接受消息。需要说明的是，步骤62至步骤64为依据常规去注册流程，执行完成了去注册流程。AMF触发针对切片的基于接入类型注册用户数的有效性检查和更新流程。
步骤65、AMF向NSACF发送Nnsacf_NSAC_NumOfUEsUpdate_Request。
步骤66、NSACF基于接入类型信息，确定针对不同接入类型的注册用户数量。这里，可以是检查和更新针对不同接入类型的注册用户数量。
步骤67、NSACF向AMF发送Nnsacf_NSAC_NumOfUEsUpdate_Response。这里，该Nnsacf_NSAC_NumOfUEsUpdate_Response包括NSACF确定的针对不同接入类型的注册用户数量。
在一个实施例中，请参见图5中的步骤52，和图6中的步骤65，在执行预定流程时，NSACF可以接收AMF发送的请求消息(例如，Nnsacf_NSAC_NumOfUEsUpdate_Request)，其中，该请求消息包括更新标识。这里，更新标识指示注册用户的数量增加或者减少。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图7所示，本实施例中提供一种确定注册用户数量的方法，其中，该方法由第一网络设备执行，所述方法包括：
步骤71、响应于终端执行预定流程且接收到AMF发送的切片用户数量更新请求消息，更新不同接入类型的注册用户数量；其中，切片用户数量更新请求消息指示增加或者减少注册用户数量。
在一个实施例中，响应于终端执行预定流程且切片用户数量更新请求消息指示增加注册用户数量，增加不同接入类型的注册用户数量。
在一个实施例中，响应于终端执行预定流程且切片用户数量更新请求消息指示减少注册用户数量，减少不同接入类型的注册用户数量。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图8所示，本实施例中提供一种确定注册用户数量的方法，其中，该方法由第一网络设备执行，所述方法包括：
步骤81、向AMF发送针对切片用户数量更新请求消息的响应消息；
其中，响应消息携带所述接入类型的注册用户数量达到预定阈值的信息和/或注册用户数量。
在一个实施例中，第一网络设备接收AMF发送的切片用户数量更新请求消息；响应于终端执行预定流程且切片用户数量更新请求消息指示增加注册用户数量，增加不同接入类型的注册用户数量。向AMF发送携带增加后的不同接入类型的注册用户数量的响应消息。请参见图5中的步骤54，和图6中的步骤67，可以是发送Nnsacf_NSAC_NumOfUEsUpdate_Response响应消息。需要说明的是，如果增加后的不同接入类型的注册用户数量达到预定阈值，则响应消息还携带接入类型的注册用户数量达到预定阈值的信息。
在一个实施例中，响应于终端执行预定流程且切片用户数量更新请求消息指示减少注册用户数量，减少不同接入类型的注册用户数量。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图9所示，本实施例中提供一种确定注册用户数量的方法，其中，该方法由第一网络设备执行，所述方法包括：
步骤91、响应于接收到应用功能AF发送的指示接入类型的切片事件订阅请求，向AF发送接入类型的事件报告。
在一个实施例中，接收应用功能AF的切片事件订阅请求，其中，切片事件订阅请求携带接入类型的信息；将接入类型的信息指示的接入类型的事件报告发送给AF。
在一个实施例中，通过NEF接收AF的切片事件订阅请求；通过NEF发送事件报告给AF。
在一个实施例中，在通过NEF接收AF发送的切片事件订阅请求和通过NEF向AF发送事件报告时，如果接入类型的信息指示的接入类型关联多个NSACF时，NEF会向多个NSACF发送切片事件订阅请求；NEF在接收到事件信息后，会执行汇聚统计，将汇聚后的信息报告给AF。
在一个实施例中，NEF通过网络注册功能NRF执行NSASF的发现选择，或者NEF通过本地配置执行NSACF的发现选择。
在一个实施例中，NEF执行AF的应用或者业务标识与切片标识之间的映射；当NEF接收到AF的切片事件订阅请求时，将应用或者业务标识映射为切片标识，发送给NSACF；NEF在接收到NSACF的时间报告时，将切片标识映射为应用或者业务标识并发送给AF。示例性地，在响应消息中，将切片标识映射为应用或者业务标识发送给AF。
在一个实施例中，切片事件订阅请求包括请求订阅的事件，该事件包括以下至少一项：已注册的终端数量和已注册终端数占最大允许注册终端数量的比例。
在一个实施例中，切片事件订阅请求包括请求订阅事件筛选信息，其中，筛选信息指示需要进行报告的特征。例如，筛选信息指示接入类型信息。接入类型信息包括以下至少一项：接入类型、无线接入类型。筛选信息还可以指示以下至少一项：切片标识、切片标识和数据网络名称组合。
在一个实施例中，切片事件订阅请求还可以包括请求订阅的事件报告模式。该报告模式包括以下至少一项：触发上报的阈值、触发上报的周期时间间隔。这里，当达到阈值或者达到周期时间间隔的时刻则上报事件报告。
在一个实施例中，切片事件订阅请求包括立即报告标志，该立即报告标志在接收到请求后立即报告所请求的事件报告。
在一个实施例中，为了向NEF订阅或者取消网络切片类型相关的终端数量的上报通知，AF向NEF发送Nnef_EventExposure subscribe/unsubscribe Request消息，消息中包括事件ID、事件过滤器、事件报告信息。
在一个实施例中，事件ID参数，定义了订阅的事件ID，即已注册终端数量，或已注册终端数量占最大允许注册终端数的比例，或已注册终端数量和已注册终端数占最大允许注册终端数的比例。
在一个实施例中，事件过滤器参数，定义需要进行报告的范围。每个范围与接入类型对应。其中，接入类型信息，包括以下各项中至少一项：接入类型、无线接入类型、包括接入类型和无线接入类型在内的接入辅助信息。在一个实施例中，所述事件过滤器参数还包括以下各项中的一项：切片标识S-NSSAI，切片标识S-NSSAI和数据网络名称DNN组合。
在一个实施例中，事件报告信息参数，定义报告模式，包括一个阈值，或包含周期时间间隔的周期性报告。如果报告信息参数为一个触发上报的阈值，当该阈值到达则上报事件报告。如果报告信息参数为一个触发上报的周期时间间隔，当所述周期时间间隔到达则上报事件报告。订阅请求还可能会包括立即报告标志，指示收到请求后立即报告所请求的事件报告。
在一个实施例中，当请求切片中部署多个NSACF时，NEF接收到相应NSACF上报信息后，对上报消息执行汇聚统计，将汇聚后的信息报告给所述请求的应用功能AF。在一个实施例中，当存在多个 NSACF时，根据运营策略或NEF配置，可选择其中一个NSACF作为相应NSACF的主NSACF或代理NSACF，执行相关NSACF的状态信息的订阅和收集汇聚等。当该NSACF为主NSACF时，切片中其它NSACF为从属NSACF；当为代理NASCF时，所述NSACF和切片中的其它各NSACF不具有主从关系。
在一个实施例中，NEF向AF发送Nnef_EventExposure_Subscribe/usubsubscribe Response响应消息。NEF接收到应用功能AF的切片事件订阅请求后，向请求切片的各NSACF订阅请求切片的事件报告，在接收到各NSACF事件报告后，将事件报告发送给AF。需要说明的是，NEF可能会通过NRF查询到该切片请求接入类型信息相应的NSACF(s)，或者通过本地配置发现选择该切片请求接入类型信息相应的NSACF(s)。
在一个实施例中，如果NEF还没有向切片请求接入类型信息相应的NSACF(s)订阅相关Requested S-NSSAI的上报事件，NEF向支持Requested S-NSSAI请求接入类型信息相应的NSACF发起订阅请求，发送Nnef_SliceEventExposure_Subscribe/Unsubscribe request请求消息，消息包括事件ID，事件过滤器，事件报告信息等。NEF存储AF请求的事件报告信息。如果Requested S-NSSAI由多个NSACF执行UE切片接纳控制，则NEF可以在向各个NSACF的订阅请求中，设置时间报告信息为周期性报告。如果Requested S-NSSAI由单个NSACF执行UE切片接纳控制，则NEF自身设置的事件报告信息与从AF接收到的请求相同。NEF同时会根据AF接收到的请求消息中的内容，设置事件ID和事件过滤器信息。
在一个实施例中，NSACF向NEF发送Nnsacf_SliceEventExposure_Subscribe/usubsubscribe响应消息，进行订阅请求的确认。
在一个实施例中，当订阅的报告条件满足，报告事件被触发，NSACF向NEF发送触发通知，执行订阅事件相关信息的报告。
在一个实施例中，NSACF向NEF发送Nnsacf_SliceEvent Exposure_Notify消息，消息中携带事件ID，事件过滤器，事件报告信息等参数。
在一个实施例中，当requested NSSAI请求接入类型信息相应有多个NSACF执行UE切片接纳控制时，NEF收集该请求接入类型对应所有NFACF的报告，并执行切片S-NSSAI在请求的事件过滤器内(比如3GPP/non-3GPP接入类型)数量的聚合。当上报条件满足，触发上报时，NEF执行切片S-NSSAI在请求的事件过滤器内(比如3GPP/non-3GPP接入类型)数量的上报。
当requested NSSAI请求接入类型信息相应为单个NSACF执行UE切片接纳控制时，NEF立即向AF返回报告通知，上报自身统计的用量报告，或者根据周期性订阅向AF执行周期性上报。
在一个实施例中，当AF订阅的事件报告的条件触发/满足时，触发订阅上报。NEF向AF发送通知，按订阅要求，上报订阅的相关用量及信息，比如所述切片3GPP接入类型的UE数，所述切片non-3GPP接入类型的UE数，或者所述切片3GPP接入内卫星接入对应的UE数等，或者同时上报相应UE数占最大允许数量的比例等。
当网络不开放网络切片标识等信息给AF(比如非可信第三方AF)，NEF执行请求AF应用或业务标识和切片标识的映射；NEF收到AF订阅请求时，将应用或业务标识映射为切片标识，发送给NSACF；NEF收到NSACF的订阅事件通知时，将切片标识映射为应用或业务标识，发送给AF。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图10所示，本实施例中提供一种确定注册用户数量的方法，其中，该方法由第二网络设备执行，该方法包括：
步骤101、向第一网络设备发送切片用户数量更新请求消息；
步骤102、接收所述第一网络设备针对所述切片用户数量更新请求消息发送的响应消息，其中，所述响应消息携带所述切片的不同接入类型的注册用户数量达到预定阈值的信息和/或不同接入类型的注册用户数量。
这里，本公开所涉及的终端可以是但不限于是手机、可穿戴设备、车载终端、路侧单元(RSU，Road Side Unit)、智能家居终端、工业用传感设备和/或医疗设备等。本公开中，注册用户数量也可以有“注册终端数量”的含义。本公开中，切片也可以有“网络切片或者网络切片实例”的含义。
本公开中涉及的第一网络设备可以是NSACF。需要说明的是，本公开中的第一网络设备并不限于NSACF，也可以是核心网中的其他通信节点，在此不做限定。这里，针对每个网络切片可以部署一个NSACF，也可以针对每个网络切片部署多个NSACF。如果针对每个网络切片部署有多个NSACF，则本公开所涉及的NSACF为该多个NSACF中的某个NSACF。示例性地，本公开中的第二网络设备也可以是AMF，但本公开中的第二网络设备并不限于AMF，也可以是核心网中的其他通信节点。
需要说明的是，针对不同接入类型的注册用户数量可以是第一网络设备确定的或者统计的。
这里，接入类型包括接入类型(Access Type)和无线接入类型(RAT Radio Access Type)。在一个实施例中，无线接入类型包括以下至少之一：NR接入、EUTRA接入、WLAN接入、VIRTUAL接入、NBIOT接入、WIRELINE接入、WIRELINE_CABLE接入、WIRELINE_BBF接入、LTE-M接入、NR_U接入、EUTRA_U接入、TRUSTED_N3GA接入、TRUSTED_WLAN接入、UTRA接入、GERA接入、NR_LEO接入、NR_MEO接入、NR_GEO接入以及NR_OTHER_SAT接入。
在一个实施例中，在终端的注册流程中，向第一网络设备发送切片用户数量更新请求消息；接收所述第一网络设备针对所述切片用户数量更新请求消息发送的响应消息，其中，所述响应消息携带切片的不同接入类型的注册用户数量达到预定阈值的信息和/或不同接入类型的注册用户数量。
在一个实施例中，在终端的配置更新流程中，基于接入类型信息，确定针对不同接入类型的注册用户数量；其中，接入类型信息指示终端接入网络切片的接入类型。如此，可以统计出不同接入类型的注册用户数量。
在一个实施例中，在终端的去注册流程中，基于接入类型信息，确定针对不同接入类型的注册用户数量；其中，接入类型信息指示终端接入网络切片的接入类型。如此，可以统计出不同接入类型的注册用户数量。
在一个实施例中，请再次参见图5，步骤52中，AMF可以向NSACF发送请求消息(例如，Nnsacf_NSAC_NumOfUEsUpdate_Request)，其中，该请求消息包括更新标识。这里，更新标识指示注册用户的数量增加或者减少。示例性地，当用户注册到该切片时，更新标识指示注册用户的数量增加； 或者，当用户从该切片中去注册或者注册无法继续时，更新标识指示注册用户的数量减少。
需要说明的是，请求消息还可以包括指示终端标识、接入类型、请求执行NSAC的相关切片S-NSSAIs、和/或AMF标识等。这里，接入类型的信息，可以是由AMF本地生成的，也可以是从基站发送给AMF的请求消息中获取的。
在一个实施例中，针对切片，在AMF和NSACF首次交互执行更新时，AMF会在请求消息中携带早期有效性检查EAC需要通知到的相关节点NF信息，如此，通过此方式隐式地从NSACF订阅切片的EAC相关通知。
在一个实施例中，NSACF还配置有切片基于接入类型的允许的最大注册用户数量。当针对切片基于接入类型执行注册用户数量更新时，如果切片在该一个或者多个接入类型内达到了最大注册用户数，NSACF在返回给AMF的响应消息中携带数量达到最大用户数量的信息。需要说明的是，如果从AMF接收到EAC通知端点信息，NSACF存储与S-NSSAI关联的EAC通知端点信息，以便于后续使用存储的通知端点来更新EAC模式。
在一个实施例中，请再次参见图5，步骤54中，AMF接收NSACF针对请求消息发送的响应消息(例如，Nnsacf_NSAC_NumOfUEsUpdate_Response)，其中，响应消息中携带在切片的接入类型所注册用户数量达到设定阈值或者最大值的切片标识S-NSSAI(s)以及指示已经达到最大值的相关结果参数。
在一个实施例中，在终端注册流程中，在AMF接收到响应消息后，如果只有请求的部分切片达到最大注册用户数量，AMF会给注册终端发送一个注册接受消息。在注册接受消息中，在拒绝切片列表中携带因为更新被拒绝的切片标识，且相应的拒绝原因设定为切片该区域内的最大用户数量已到达。在一个实施例中，可以设置一个可发起重新请求的定时器。
在一个实施例中，当AMF发送给NSACF的请求消息中，所请求的全部切片S-NSSAI(s)都到了允许的最大值，且签约信息中如果有一个或多个签约切片标注为缺省切片，且同时不需要执行更新，则AMF可能会决策将这些缺省切片放入Allow NSSAI，作为授权允许切片。否则，AMF将会拒绝该用户UE的注册请求(比如，该接入类型的注册请求)。在注册拒绝消息中，AMF携带拒绝切片标识列表，每个切片带上相应的拒绝原因值，例如，切片该区域内的允许的最大注册用户数量已到达。在一个实施例中，设置一个可发起重新请求的定时器。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图11所示，本实施例中提供一种确定注册用户数量的方法，其中，该方法由第二网络设备执行，该方法包括：
步骤111、接收终端发送的注册请求消息；
步骤112、根据注册用户数量，确定是否拒绝终端的注册请求消息。
在一个实施例中，在终端注册流程中，在AMF接收到响应消息后，如果只有请求的部分切片达到最大注册用户数量，AMF会给注册终端发送一个注册接受消息。在注册接受消息中，在拒绝切片列表中携带因为更新被拒绝的切片标识，且相应的拒绝原因设定为切片该区域内的最大用户数量已到达。在 一个实施例中，可以设置一个可发起重新请求的定时器。
在一个实施例中，当AMF发送给NSACF的请求消息中，所请求的全部切片S-NSSAI(s)都到了允许的最大值，且签约信息中如果有一个或多个签约切片标注为缺省切片，且同时不需要执行更新，则AMF可能会决策将这些缺省切片放入Allow NSSAI，作为授权允许切片。否则，AMF将会拒绝该用户UE的注册请求(比如，该接入类型的注册请求)。在注册拒绝消息中，AMF携带拒绝切片标识列表，每个切片带上相应的拒绝原因值，例如，切片该区域内的允许的最大注册用户数量已到达。在一个实施例中，设置一个可发起重新请求的定时器。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图12所示，本实施例中提供一种确定注册用户数量的方法，其中，该方法由第二网络设备执行，该方法包括：
步骤121、响应于请求的部分网络切片的所述注册用户数量达到所述预定阈值，确定接受终端的所述注册请求消息；
或者，
响应于请求的全部网络切片的所述注册用户数量达到所述预定阈值且配置有备用网络切片，确定接受终端的所述注册请求消息；
或者，
响应于请求的全部网络切片的所述注册用户数量达到所述预定阈值且未配置备用网络切片，确定拒绝终端的所述注册请求消息。
这里，需要说明的是，当请求的部分网络切片的所述注册用户数量达到所述预定阈值，可以接收终端的注册请求消息，示例性地，可以是拒绝终端在注册用户数量达到所述预定阈值的网络切片上的注册且接受终端在注册用户数量未达到所述预定阈值的网络切片上的注册。例如，终端请求在4个切片上注册，4个切片分别为A切片、B切片、C切片和D切片,如果A切片、B切片和C切片的所述注册用户数量达到所述预定阈值，可以接受终端的所述注册请求消息，此时，可以接受终端在D切片上的注册，但会拒绝终端在A切片、B切片和C切片上的注册。
这里，预定阈值可以是最大的注册用户数或者会话数。示例性地，可以是实际数值，例如，绝对值。也可以是网络最大用户数或会话数的最大容量的比例对应的值，例如，相对值。
在一个实施例中，可以是根据要求的网络通信质量确定所述预定阈值。示例性地，当要求的网络通信质量更好更有保障，所述预定阈值可以设置为较小的值；或者，当要求的网络通信质量要求降低，所述预定阈值可以设定较大的值。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图13所示，本实施例中提供一种确定注册用户数量的方法，其中，该方法由第三网络设备执行， 该方法包括：
步骤131、向第一网络设备发送指示接入类型的切片事件订阅请求；其中，所述切片事件订阅请求用于获取所述接入类型的事件报告；所述事件报告至少指示与切片事件订阅请求指示的接入类型关联的注册用户数量；
步骤132、接收第一网络设备针对所述切片事件订阅请求发送的所述事件报告。
这里，本公开所涉及的终端可以是但不限于是手机、可穿戴设备、车载终端、路侧单元(RSU，Road Side Unit)、智能家居终端、工业用传感设备和/或医疗设备等。本公开中，注册用户数量也可以有“注册终端数量”的含义。本公开中，切片也可以有“网络切片或者网络切片实例”的含义。
本公开中涉及的第一网络设备可以是NSACF。需要说明的是，本公开中的第一网络设备并不限于NSACF，也可以是核心网中的其他通信节点，在此不做限定。这里，针对每个网络切片可以部署一个NSACF，也可以针对每个网络切片部署多个NSACF。如果针对每个网络切片部署有多个NSACF，则本公开所涉及的NSACF为该多个NSACF中的某个NSACF。示例性地，本公开中的第三网络设备可以是应用功能AF，但本公开中的第三网络设备并不限于AF，也可以是核心网中的其他通信节点。在一个实施例中，所述接入类型包括以下至少一种：
第三代移动通信伙伴项目3GPP接入；
非3GPP接入；
以及，3GPP和非3GPP接入。
在一个实施例中，所述无线接入类型包括以下至少一种：新空口接入NR、演进的通用移动通信系统陆面无线接入EUTRA、无线局域网接入WLAN、虚拟网接入VIRTUAL、窄带物联网接入NBIOT、有线网接入WIRELINE、有线电缆网接入WIRELINE_CABLE、有线宽带网接入WIRELINE_BBF、城市轨道交通车地综合通信系统接入LTE-M、新空口非许可频谱接入NR_U、演进的通用移动通信系统陆面非许可频谱无线接入EUTRA_U、可信任N3GA接入TRUSTED_N3GA、可信任无线局域网接入TRUSTED_WLAN、通用陆地无线接入UTRA、全球移动通信系统边缘无线接入网络接入GERA、新空口低轨道接入NR_LEO、新空口中高轨道接入NR_MEO、新空口静止地球轨道接入NR_GEO以及其他卫星接入NR_OTHER_SAT。
在一个实施例中，应用功能AF向NSACF发送切片事件订阅请求，其中，切片事件订阅请求携带接入类型的信息；接收NSACF发送的接入类型的信息指示的接入类型的事件报告。
在一个实施例中，通过NEF发送切片事件订阅请求；通过NEF接收事件报告。
在一个实施例中，在通过NEF发送切片事件订阅请求和通过NEF接收事件报告时，如果接入类型的信息指示的接入类型关联多个NSACF时，NEF会向多个NSACF发送切片事件订阅请求；NEF在接收到事件信息后，会执行汇聚统计，将汇聚后的信息报告给AF。
在一个实施例中，NEF通过网络注册功能NRF执行NSASF的发现选择，或者NEF通过本地配置执行NSACF的发现选择。
在一个实施例中，NEF执行AF的应用或者业务标识与切片标识之间的映射；当NEF接收到AF的切片事件订阅请求时，将应用或者业务标识映射为切片标识，发送给NSACF；NEF在接收到 NSACF的时间报告时，将切片标识映射为应用或者业务标识并发送给AF。
在一个实施例中，切片事件订阅请求包括请求订阅的事件，该事件包括以下至少一项：已注册的终端数量和已注册终端数占最大允许注册终端数量的比例。
在一个实施例中，切片事件订阅请求包括请求订阅事件筛选信息，其中，筛选信息指示需要进行报告的特征。例如，筛选信息指示接入类型信息。接入类型信息包括以下至少一项：接入类型、无线接入类型。筛选信息还可以指示以下至少一项：切片标识、切片标识和数据网络名称组合。
在一个实施例中，切片事件订阅请求还可以包括请求订阅的事件报告模式。该报告模式包括以下至少一项：触发上报的阈值、触发上报的周期时间间隔。这里，当达到阈值或者达到周期时间间隔的时刻则上报事件报告。
在一个实施例中，切片事件订阅请求包括立即报告标志，该立即报告标志在接收到请求后立即报告所请求的事件报告。
在一个实施例中，为了向NEF订阅或者取消网络切片类型相关的终端数量的上报通知，AF向NEF发送Nnef_EventExposure subscribe/unsubscribe Request消息，消息中包括事件ID、事件过滤器、事件报告信息。
在一个实施例中，事件ID参数，定义了订阅的事件ID，即已注册终端数量，或已注册终端数量占最大允许注册终端数的比例，或已注册终端数量和已注册终端数占最大允许注册终端数的比例。
在一个实施例中，事件过滤器参数，定义需要进行报告的范围。每个范围与接入类型对应。其中，接入类型信息，包括以下各项中至少一项：接入类型、无线接入类型、包括接入类型和无线接入类型在内的接入辅助信息。在一个实施例中，所述事件过滤器参数还包括以下各项中的一项：切片标识S-NSSAI，切片标识S-NSSAI和数据网络名称DNN组合。
在一个实施例中，事件报告信息参数，定义报告模式，包括一个阈值，或包含周期时间间隔的周期性报告。如果报告信息参数为一个触发上报的阈值，当该阈值到达则上报事件报告。如果报告信息参数为一个触发上报的周期时间间隔，当所述周期时间间隔到达则上报事件报告。订阅请求还可能会包括立即报告标志，指示收到请求后立即报告所请求的事件报告。
在一个实施例中，当请求切片中部署多个NSACF时，NEF接收到相应NSACF上报信息后，对上报消息执行汇聚统计，将汇聚后的信息报告给所述请求的应用功能AF。在一个实施例中，当存在多个NSACF时，根据运营策略或NEF配置，可选择其中一个NSACF作为相应NSACF的主NSACF或代理NSACF，执行相关NSACF的状态信息的订阅和收集汇聚等。当该NSACF为主NSACF时，切片中其它NSACF为从属NSACF；当为代理NASCF时，所述NSACF和切片中的其它各NSACF不具有主从关系。
在一个实施例中，NEF向AF发送Nnef_EventExposure_Subscribe/usubsubscribe Response响应消息。NEF接收到应用功能AF的切片事件订阅请求后，向请求切片的各NSACF订阅请求切片的事件报告，在接收到各NSACF事件报告后，将事件报告发送给AF。需要说明的是，NEF可能会通过NRF查询到该切片请求接入类型信息相应的NSACF(s)，或者通过本地配置发现选择该切片请求接入类型信息相应的NSACF(s)。
在一个实施例中，如果NEF还没有向切片请求接入类型信息相应的NSACF(s)订阅相关Requested S-NSSAI的上报事件，NEF向支持Requested S-NSSAI请求接入类型信息相应的NSACF发起订阅请求，发送Nnef_SliceEventExposure_Subscribe/Unsubscribe request请求消息，消息包括事件ID，事件过滤器，事件报告信息等。NEF存储AF请求的事件报告信息。如果Requested S-NSSAI由多个NSACF执行UE切片接纳控制，则NEF可以在向各个NSACF的订阅请求中，设置时间报告信息为周期性报告。如果Requested S-NSSAI由单个NSACF执行UE切片接纳控制，则NEF自身设置的事件报告信息与从AF接收到的请求相同。NEF同时会根据AF接收到的请求消息中的内容，设置事件ID和事件过滤器信息。
在一个实施例中，NSACF向NEF发送Nnsacf_SliceEventExposure_Subscribe/usubsubscribe响应消息，进行订阅请求的确认。
在一个实施例中，当订阅的报告条件满足，报告事件被触发，NSACF向NEF发送触发通知，执行订阅事件相关信息的报告。
在一个实施例中，NSACF向NEF发送Nnsacf_SliceEvent Exposure_Notify消息，消息中携带事件ID，事件过滤器，事件报告信息等参数。
在一个实施例中，当requested NSSAI请求接入类型信息相应有多个NSACF执行UE切片接纳控制时，NEF收集该请求接入类型对应所有NFACF的报告，并执行切片S-NSSAI在请求的事件过滤器内(比如3GPP/non-3GPP接入类型)数量的聚合。当上报条件满足，触发上报时，NEF执行切片S-NSSAI在请求的事件过滤器内(比如3GPP/non-3GPP接入类型)数量的上报。
当requested NSSAI请求接入类型信息相应为单个NSACF执行UE切片接纳控制时，NEF立即向AF返回报告通知，上报自身统计的用量报告，或者根据周期性订阅向AF执行周期性上报。
在一个实施例中，当AF订阅的事件报告的条件触发/满足时，触发订阅上报。NEF向AF发送通知，按订阅要求，上报订阅的相关用量及信息，比如所述切片3GPP接入类型的UE数，所述切片non-3GPP接入类型的UE数，或者所述切片3GPP接入内卫星接入对应的UE数等，或者同时上报相应UE数占最大允许数量的比例等。
当网络不开放网络切片标识等信息给AF(比如非可信第三方AF)，NEF执行请求AF应用或业务标识和切片标识的映射；NEF收到AF订阅请求时，将应用或业务标识映射为切片标识，发送给NSACF；NEF收到NSACF的订阅事件通知时，将切片标识映射为应用或业务标识，发送给AF。
示例性地，为了更好地理解本公开实施例，请参见图14，确定注册用户数量的方法的通知流程可以包括：
步骤141、AF向NEF发送Nnef_EventExposure subscribe或者unsubscribe Request消息。这里，可以是为了向NEF订阅或取消网络切片接入类型相关的终端数量的上报通知，AF向NEF发送Nnef_EventExposure subscribe/unsubscribe Request消息，消息中包括事件ID、事件过滤器、事件报告信息。这里，相关的终端数量的上报通知包括：接入类型关联的注册用户数量。这里，可以是基于接入类型信息，确定针对不同接入类型的注册用户数量。
步骤142、NEF向AF发送Nnef_EventExposure_Subscribe或者usubsubscribe Response响应消息。NEF接收到应用功能AF的切片事件订阅请求后，向所述请求切片的各NSACF订阅所述请求切片的上 报事件，收到各NSACF上报信息后，报告给所述请求的应用功能AF。
步骤143、NEF可能会通过NRF查询到该切片请求接入类型信息相应的NSACF(s)，或者通过本地配置发现选择该切片请求接入类型信息相应的NSACF(s)。
步骤144、NEF向NSACF发送Nnef_SliceEventExposure_Subscribe或者Unsubscribe request请求消息。示例性地，如果NEF还没有向切片请求接入类型信息相应的NSACF(s)订阅相关Requested S-NSSAI的上报事件，NEF向支持Requested S-NSSAI请求接入类型信息相应的NSACF发起订阅请求，发送Nnef_SliceEventExposure_Subscribe/Unsubscribe request请求消息，消息包括事件ID，事件过滤器，事件报告信息等。NEF存储AF请求的事件报告信息。如果Requested S-NSSAI由多个NSACF执行UE切片接纳控制，则NEF可以在向各个NSACF的订阅请求中，设置时间报告信息为周期性报告。如果Requested S-NSSAI由单个NSACF执行UE切片接纳控制，则NEF自身设置的事件报告信息与从AF接收到的请求相同。NEF同时会根据AF接收到的请求消息中的内容，设置事件ID和事件过滤器信息。
步骤145、NSACF向NEF发送Nnsacf_SliceEventExposure_Subscribe或者usubsubscribe响应消息，进行订阅请求的确认。
步骤146、当订阅的报告条件满足，报告事件被触发，NSACF向NEF发送触发通知，执行订阅事件相关信息的报告。
步骤147、NSACF向NEF发送Nnsacf_SliceEvent Exposure_Notify消息，消息中携带事件ID，事件过滤器，事件报告信息等参数。
步骤148、执行消息聚合。示例性地，当requested NSSAI请求接入类型信息相应有多个NSACF执行UE切片接纳控制时，NEF收集该请求接入类型对应所有NFACF的报告，并执行切片S-NSSAI在请求的事件过滤器内(比如3GPP/non-3GPP接入类型)数量的聚合。当上报条件满足，触发上报时，NEF执行切片S-NSSAI在请求的事件过滤器内(比如3GPP/non-3GPP接入类型)数量的上报。
当requested NSSAI请求接入类型信息相应为单个NSACF执行UE切片接纳控制时，NEF立即向AF返回报告通知，上报自身统计的用量报告，或者根据周期性订阅向AF执行周期性上报。
步骤149、NEF向AF发送Nnef_SliceEventExposure_Notify通知消息，通知消息包括事件报告信息。示例性地，当AF订阅的事件报告的条件触发/满足时，触发订阅上报。NEF向AF发送通知，按订阅要求，上报订阅的相关用量及信息，比如所述切片3GPP接入类型的UE数，所述切片non-3GPP接入类型的UE数，或者所述切片3GPP接入内卫星接入对应的UE数等，或者同时上报相应UE数占最大允许数量的比例等。
当网络不开放网络切片标识等信息给AF(比如非可信第三方AF)，NEF执行请求AF应用或业务标识和切片标识的映射；在第一步骤中，NEF收到AF订阅请求时，将应用或业务标识映射为切片标识，发送给NSACF；NEF收到NSACF的订阅事件通知时，将切片标识映射为应用或业务标识，发送给AF。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图15所示，本公开实施例中提供一种确定注册用户数量的装置，其中，所述装置包括：
确定模块151，用于基于接入类型信息，确定针对不同接入类型的注册用户数量；
其中，所述接入类型信息指示终端接入网络切片的接入类型。需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图16所示，本公开实施例中提供一种确定注册用户数量的装置，其中，所述装置包括：
发送模块161，用于向第一网络设备发送切片用户数量更新请求消息；
接收模块162，用于接收所述第一网络设备针对所述切片用户数量更新请求消息发送的响应消息，其中，所述响应消息携带所述切片的所述接入类型的注册用户数量达到预定阈值的信息和/或注册用户数量。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
如图17所示，本公开实施例中提供一种确定注册用户数量的装置，其中，所述装置包括：
发送模块171，用于向第一网络设备发送指示接入类型的切片事件订阅请求；其中，所述切片事件订阅请求用于获取接入类型的事件报告；所述事件报告至少指示与切片事件订阅请求指示的接入类型关联的注册用户数量；
接收模块172，用于接收第一网络设备针对所述切片事件订阅请求发送的所述事件报告。
需要说明的是，本领域内技术人员可以理解，本公开实施例提供的方法，可以被单独执行，也可以与本公开实施例中一些方法或相关技术中的一些方法一起被执行。
本公开实施例提供一种通信设备，通信设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，处理器被配置为：用于运行可执行指令时，实现应用于本公开任意实施例的方法。
其中，处理器可包括各种类型的存储介质，该存储介质为非临时性计算机存储介质，在通信设备掉电之后能够继续记忆存储其上的信息。
处理器可以通过总线等与存储器连接，用于读取存储器上存储的可执行程序。
本公开实施例还提供一种计算机存储介质，其中，计算机存储介质存储有计算机可执行程序，可执行程序被处理器执行时实现本公开任意实施例的方法。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
如图18所示，本公开一个实施例提供一种终端的结构。
参照图18所示终端800本实施例提供一种终端800，该终端具体可是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图18，终端800可以包括以下一个或多个组件：处理组件802，存储器804，电源组件806，多媒体组件808，音频组件810，输入/输出(I/O)的接口812，传感器组件814，以及通信组件816。
处理组件802通常控制终端800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件802可以包括一个或多个处理器820来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件802可以包括一个或多个模块，便于处理组件802和其他组件之间的交互。例如，处理组件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在设备800的操作。这些数据的示例包括用于在终端800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件806为终端800的各种组件提供电力。电源组件806可以包括电源管理系统，一个或多个电源，及其他与为终端800生成、管理和分配电力相关联的组件。
多媒体组件808包括在终端800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄像头。当设备800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当终端800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件802和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器，用于为终端800提供各个方面的状态评估。例如，传感器组件814可以检测到设备800的打开/关闭状态，组件的相对定位，例如组件为终端800的显示器和小键盘，传感器组件814还可以检测终端800或终端800一个组件的位置改变，用户与终端800接触的存在或不存在，终端800方位或加速/减速和终端800的温度变化。传感器组件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于终端800和其他设备之间有线或无线方式的通信。终端800可以接入基于通信标准的无线网络，如Wi-Fi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件816经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信组件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，终端800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器804，上述指令可由终端800的处理器820执行以完成上述方法。例如，非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
如图19所示，本公开一实施例示出一种基站的结构。例如，基站900可以被提供为一网络侧设备。参照图19，基站900包括处理组件922，其进一步包括一个或多个处理器，以及由存储器932所代表的存储器资源，用于存储可由处理组件922的执行的指令，例如应用程序。存储器932中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件922被配置为执行指令，以执行上述方法前述应用在所述基站的任意方法。
基站900还可以包括一个电源组件926被配置为执行基站900的电源管理，一个有线或无线网络接口950被配置为将基站900连接到网络，和一个输入输出(I/O)接口958。基站900可以操作基于存储在存储器932的操作系统，例如Windows Server TM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM或类似。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本公开旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由下面的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (22)

  1. 一种确定注册用户数量的方法，其中，所述方法由第一网络设备执行，所述方法包括：
    基于接入类型信息，确定针对不同接入类型的注册用户数量；
    其中，所述接入类型信息指示终端接入网络切片的接入类型。
  2. 根据权利要求1所述的方法，其中，所述接入类型信息，包括以下至少一项：
    配置在第一网络设备上的接入类型信息；
    从消费者网络功能获取的接入类型信息；
    操作维护管理系统OAM配置的接入类型信息；
    从访问和移动性管理功能AMF获取的接入类型信息。
  3. 根据权利要求1所述的方法，其中，所述接入类型信息指示以下至少一种：
    接入类型Access Type；
    无线接入类型RAT Radio Access Type；
    接入辅助信息addAccessInfo。
  4. 根据权利要求3所述的方法，其中，所述接入类型包括以下至少一种：
    第三代移动通信伙伴项目3GPP接入；
    非3GPP接入；
    3GPP和非3GPP接入。
  5. 根据权利要求3所述的方法，其中，所述无线接入类型包括以下至少一种：新空口接入NR、演进的通用移动通信系统陆面无线接入EUTRA、无线局域网接入WLAN、虚拟网接入VIRTUAL、窄带物联网接入NBIOT、有线网接入WIRELINE、有线电缆网接入WIRELINE_CABLE、有线宽带网接入WIRELINE_BBF、城市轨道交通车地综合通信系统接入LTE-M、新空口非许可频谱接入NR_U、演进的通用移动通信系统陆面非许可频谱无线接入EUTRA_U、可信任N3GA接入TRUSTED_N3GA、可信任无线局域网接入TRUSTED_WLAN、通用陆地无线接入UTRA、全球移动通信系统边缘无线接入网络接入GERA、新空口低轨道接入NR_LEO、新空口中高轨道接入NR_MEO、新空口静止地球轨道接入NR_GEO以及其他卫星接入NR_OTHER_SAT。
  6. 根据权利要求1所述的方法，其中，所述方法还包括：
    响应于终端执行预定流程，更新针对不同所述接入类型的注册用户数量；
    其中，所述预定流程包括以下之一：
    终端的注册流程；
    终端的配置更新流程；
    终端的去注册流程。
  7. 根据权利要求6所述的方法，其中，所述响应于终端执行预定流程，更新针对不同所述接入类型的注册用户数量，包括：
    响应于终端执行预定流程且接收到第二网络设备发送的切片用户数量更新请求消息，更新针对不同所述接入类型的注册用户数量；
    其中，所述切片用户数量更新请求消息指示：增加或者减少所述注册用户数量。
  8. 根据权利要求7所述的方法，其中，所述方法还包括：
    向所述第二网络设备发送针对所述切片用户数量更新请求消息的响应消息；
    其中，所述响应消息携带所述接入类型的注册用户数量达到预定阈值的信息和/或与接入类型关联的注册用户数量。
  9. 根据权利要求1所述的方法，其中，所述方法还包括：
    响应于接收到应用功能AF发送的指示接入类型的切片事件订阅请求，向所述AF发送所述接入类型的事件报告；其中，所述事件报告至少指示与接入类型关联的注册用户数量。
  10. 一种确定注册用户数量的方法，其中，所述方法由第二网络设备执行，所述方法包括：
    向第一网络设备发送切片用户数量更新请求消息；
    接收所述第一网络设备发送的响应消息，其中，所述响应消息携带切片的不同接入类型的注册用户数量达到预定阈值的信息和/或不同接入类型的注册用户数量。
  11. 根据权利要求10所述的方法，其中，所述接入类型包括以下至少一种：
    第三代移动通信伙伴项目3GPP接入；
    非3GPP接入；
    3GPP和非3GPP接入。
  12. 根据权利要求11所述的方法，其中，所述无线接入类型包括以下至少一种：新空口接入NR、演进的通用移动通信系统陆面无线接入EUTRA、无线局域网接入WLAN、虚拟网接入VIRTUAL、窄带物联网接入NBIOT、有线网接入WIRELINE、有线电缆网接入WIRELINE_CABLE、有线宽带网接入WIRELINE_BBF、城市轨道交通车地综合通信系统接入LTE-M、新空口非许可频谱接入NR_U、演进的通用移动通信系统陆面非许可频谱无线接入EUTRA_U、可信任N3GA接入TRUSTED_N3GA、可信任无线局域网接入TRUSTED_WLAN、通用陆地无线接入UTRA、全球移动通信系统边缘无线接入网络接入GERA、新空口低轨道接入NR_LEO、新空口中高轨道接入NR_MEO、新空口静止地球轨道接入NR_GEO以及其他卫星接入NR_OTHER_SAT。
  13. 根据权利要求10所述的方法，其中，所述方法还包括：
    接收终端发送的注册请求消息；
    根据所述注册用户数量，确定是否拒绝终端的所述注册请求消息。
  14. 根据权利要求13所述的方法，其中，所述根据所述注册用户数量，确定是否拒绝终端的所述注册请求消息，包括：
    响应于请求的部分网络切片的所述注册用户数量达到所述预定阈值，确定接受终端的所述注册请求消息；
    或者，
    响应于请求的全部网络切片的所述注册用户数量达到所述预定阈值且配置有备用网络切片，确定接受终端的所述注册请求消息；
    或者，
    响应于请求的全部网络切片的所述注册用户数量达到所述预定阈值且未配置备用网络切片，确定拒绝终端的所述注册请求消息。
  15. 一种确定注册用户数量的方法，其中，所述方法由第三网络设备执行，所述方法包括：
    向第一网络设备发送指示接入类型的切片事件订阅请求；其中，所述切片事件订阅请求用于获取所述接入类型的事件报告；所述事件报告至少指示与切片事件订阅请求指示的接入类型关联的注册用户数量；
    接收第一网络设备针对所述切片事件订阅请求发送的所述事件报告。
  16. 根据权利要求15所述的方法，其中，所述接入类型包括以下至少一种：
    第三代移动通信伙伴项目3GPP接入；
    非3GPP接入；
    3GPP和非3GPP接入。
  17. 根据权利要求16所述的方法，其中，所述无线接入类型包括以下至少一种：新空口接入NR、演进的通用移动通信系统陆面无线接入EUTRA、无线局域网接入WLAN、虚拟网接入VIRTUAL、窄带物联网接入NBIOT、有线网接入WIRELINE、有线电缆网接入WIRELINE_CABLE、有线宽带网接入WIRELINE_BBF、城市轨道交通车地综合通信系统接入LTE-M、新空口非许可频谱接入NR_U、演进的通用移动通信系统陆面非许可频谱无线接入EUTRA_U、可信任N3GA接入TRUSTED_N3GA、可信任无线局域网接入TRUSTED_WLAN、通用陆地无线接入UTRA、全球移动通信系统边缘无线接入网络接入GERA、新空口低轨道接入NR_LEO、新空口中高轨道接入NR_MEO、新空口静止地球轨道接入NR_GEO以及其他卫星接入NR_OTHER_SAT。
  18. 一种确定注册用户数量的装置，其中，所述装置包括：
    确定模块，用于基于接入类型信息，确定针对不同接入类型的注册用户数量；
    其中，所述接入类型信息指示与网络切片关联的接入类型。
  19. 一种确定注册用户数量的装置，其中，所述装置包括：
    发送模块，用于向第一网络设备发送切片用户数量更新请求消息；
    接收模块，用于接收所述第一网络设备针对所述切片用户数量更新请求消息发送的响应消息，其中，所述响应消息携带所述切片的所述接入类型的注册用户数量达到预定阈值的信息和/或注册用户数量。
  20. 一种确定注册用户数量的装置，其中，所述装置包括：
    发送模块，用于向第一网络设备发送指示接入类型的切片事件订阅请求；其中，所述切片事件订阅请求用于获取接入类型的事件报告；所述事件报告至少指示与切片事件订阅请求指示的接入类型关联的注册用户数量；
    接收模块，用于接收第一网络设备针对所述切片事件订阅请求发送的所述事件报告。
  21. 一种通信设备，其中，包括：
    存储器；
    处理器，所述处理器与所述存储器连接，被配置为通过执行存储在所述存储器上的计算机可执行指令，并能够实现权利要求1至9、10至14或者15至17任一项所述的方法。
  22. 一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被处理器执行后能够实现权利要求1至9、10至14或者15至17任一项所述的方法。
PCT/CN2022/072120 2022-01-14 2022-01-14 确定注册用户数量的方法、装置、通信设备及存储介质 Ceased WO2023133838A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN202280000182.5A CN116803111A (zh) 2022-01-14 2022-01-14 确定注册用户数量的方法、装置、通信设备及存储介质
US18/728,007 US20250113285A1 (en) 2022-01-14 2022-01-14 Method and apparatus for determining number of registered users, communication device and storage medium
PCT/CN2022/072120 WO2023133838A1 (zh) 2022-01-14 2022-01-14 确定注册用户数量的方法、装置、通信设备及存储介质
EP22919488.1A EP4465669A4 (en) 2022-01-14 2022-01-14 METHOD AND APPARATUS FOR DETERMINING THE NUMBER OF REGISTERED USERS, COMMUNICATION DEVICE AND STORAGE MEDIUM

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/072120 WO2023133838A1 (zh) 2022-01-14 2022-01-14 确定注册用户数量的方法、装置、通信设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023133838A1 true WO2023133838A1 (zh) 2023-07-20

Family

ID=87279897

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/072120 Ceased WO2023133838A1 (zh) 2022-01-14 2022-01-14 确定注册用户数量的方法、装置、通信设备及存储介质

Country Status (4)

Country Link
US (1) US20250113285A1 (zh)
EP (1) EP4465669A4 (zh)
CN (1) CN116803111A (zh)
WO (1) WO2023133838A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230085363A1 (en) * 2020-02-18 2023-03-16 Lg Electronics Inc. Communication related to network slice
TWI893537B (zh) * 2023-11-22 2025-08-11 中華電信股份有限公司 用戶申請５ｇ網路切片服務之供裝系統、方法及其電腦可讀媒介

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN120752969A (zh) * 2023-01-05 2025-10-03 三星电子株式会社 考虑网络切片配额的支持网络切片改变的方法和设备
US20250344132A1 (en) * 2024-05-02 2025-11-06 Verizon Patent And Licensing Inc. Systems and methods for dynamic per-slice capacity thresholds in a wireless network

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102572783A (zh) * 2007-05-11 2012-07-11 华为技术有限公司 一种注册处理方法、系统及装置
WO2019063107A1 (en) * 2017-09-28 2019-04-04 Telefonaktiebolaget Lm Ericsson (Publ) METHODS AND DEVICES FOR SUPPORTING USER EQUIPMENT AUTHORIZATION, UE, BASED ON ACCESS NETWORK TYPE AND ON THE BASIS OF RADIO ACCESS TECHNOLOGY, RAT
CN110402604A (zh) * 2017-03-16 2019-11-01 Lg 电子株式会社 在无线通信系统中通知移动性事件的方法及其设备
CN110679185A (zh) * 2017-03-20 2020-01-10 中兴通讯股份有限公司 网络切片服务功能
CN111201810A (zh) * 2018-01-05 2020-05-26 Oppo广东移动通信有限公司 无线通信方法和设备
CN112788704A (zh) * 2019-11-06 2021-05-11 华为技术有限公司 网络切片的使用控制方法、装置及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102572783A (zh) * 2007-05-11 2012-07-11 华为技术有限公司 一种注册处理方法、系统及装置
CN110402604A (zh) * 2017-03-16 2019-11-01 Lg 电子株式会社 在无线通信系统中通知移动性事件的方法及其设备
CN110679185A (zh) * 2017-03-20 2020-01-10 中兴通讯股份有限公司 网络切片服务功能
WO2019063107A1 (en) * 2017-09-28 2019-04-04 Telefonaktiebolaget Lm Ericsson (Publ) METHODS AND DEVICES FOR SUPPORTING USER EQUIPMENT AUTHORIZATION, UE, BASED ON ACCESS NETWORK TYPE AND ON THE BASIS OF RADIO ACCESS TECHNOLOGY, RAT
CN111201810A (zh) * 2018-01-05 2020-05-26 Oppo广东移动通信有限公司 无线通信方法和设备
CN112788704A (zh) * 2019-11-06 2021-05-11 华为技术有限公司 网络切片的使用控制方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4465669A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230085363A1 (en) * 2020-02-18 2023-03-16 Lg Electronics Inc. Communication related to network slice
US12363629B2 (en) * 2020-02-18 2025-07-15 Lg Electronics Inc. Communication related to network slice
TWI893537B (zh) * 2023-11-22 2025-08-11 中華電信股份有限公司 用戶申請５ｇ網路切片服務之供裝系統、方法及其電腦可讀媒介

Also Published As

Publication number Publication date
EP4465669A4 (en) 2025-04-16
US20250113285A1 (en) 2025-04-03
EP4465669A1 (en) 2024-11-20
CN116803111A (zh) 2023-09-22

Similar Documents

Publication Publication Date Title
WO2023133838A1 (zh) 确定注册用户数量的方法、装置、通信设备及存储介质
CN117044248B (zh) 基于接入类型的切片事件订阅上报方法、装置及存储介质
CN116406513A (zh) QoS监控结果的订阅方法、装置、通信设备及存储介质
US20240430752A1 (en) Data analysis methods and apparatuses of radio network, communication devices and storage mediums
CN113892282B (zh) 上报信息的方法、装置、通信设备及存储介质
CN116349267A (zh) 密钥分发方法、装置、通信设备及存储介质
WO2024000537A1 (zh) 网络访问方法、装置、通信设备和存储介质
CN116762384B (zh) 信息传输方法、装置、通信设备和存储介质
CN116762389B (zh) 信息传输方法、装置、通信设备和存储介质
US20260059293A1 (en) Information processing method and apparatus, and communication device and storage medium
WO2023245448A1 (zh) 一种信息传输方法、装置、通信设备及存储介质
WO2023245457A1 (zh) 一种信息传输方法、装置、通信设备及存储介质
WO2023240643A1 (zh) 信息处理方法、装置、通信设备及存储介质
WO2023240641A1 (zh) 信息处理方法、装置、通信设备及存储介质
WO2023000154A1 (zh) 跟踪区异常处理方法及装置、通信设备及存储介质
EP4615030A1 (en) Information processing method and apparatus, communication device and storage medium
EP4572412A1 (en) Information processing methods, system and apparatus, communication device, and storage medium
CN116998186A (zh) 信息处理方法、装置、通信设备及存储介质
WO2023184105A1 (zh) 获取终端位置的方法、装置、通信设备及存储介质
WO2024207521A1 (zh) 信息传输方法、装置、系统、通信设备及存储介质
WO2024031460A1 (zh) 一种接入行为确定方法、装置、通信设备及存储介质
WO2024036438A1 (zh) 网络选择方法及装置、通信设备及存储介质
CN116325554A (zh) 信息传输方法、装置、通信设备和存储介质
WO2022236642A1 (zh) 信息处理方法、装置、通信设备及存储介质

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202280000182.5

Country of ref document: CN

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

Ref document number: 22919488

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18728007

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 202447060987

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2022919488

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022919488

Country of ref document: EP

Effective date: 20240814

WWP Wipo information: published in national office

Ref document number: 18728007

Country of ref document: US