WO2024017023A1 - 允许的nssai的获取方法、终端及网络侧设备 - Google Patents

允许的nssai的获取方法、终端及网络侧设备 Download PDF

Info

Publication number
WO2024017023A1
WO2024017023A1 PCT/CN2023/104754 CN2023104754W WO2024017023A1 WO 2024017023 A1 WO2024017023 A1 WO 2024017023A1 CN 2023104754 W CN2023104754 W CN 2023104754W WO 2024017023 A1 WO2024017023 A1 WO 2024017023A1
Authority
WO
WIPO (PCT)
Prior art keywords
nssai
network element
network
terminal
session
Prior art date
Application number
PCT/CN2023/104754
Other languages
English (en)
French (fr)
Inventor
孙晓文
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2024017023A1 publication Critical patent/WO2024017023A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/20Traffic policing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/16Discovering, processing access restriction or access information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/18Selecting a network or a communication service
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/12Setup of transport tunnels
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/30Connection release
    • H04W76/32Release of transport tunnels

Definitions

  • This application belongs to the field of wireless communication technology, and specifically relates to a method for obtaining allowed Network Slice Selection Assistance Information (NSSAI), a terminal and a network-side device.
  • NSSAI Network Slice Selection Assistance Information
  • a terminal when a terminal accesses the network, it carries the requested NSSAI (Requested NSSAI). After receiving the request from the terminal, the network side returns the allowed NSSAI (Allowed NSSAI).
  • the network side statically configures access control information and session control information for the terminal.
  • the terminal initiates a registration request and a session request, it needs to determine the multi-dimensional restriction information and finally select the Requested NSSAI for registration as needed. That is to say, the terminal needs to identify the service attributes when it is powered on and register, and determine the single network slice selection auxiliary information (Single network slice selection auxiliary information, S-NSSAI) list contained in the Request NSSAI under different regional scopes and different business requirements ( list). Therefore, in related technologies, there is a strong reliance on the terminal to identify different network slice service types and requirements.
  • the terminal is required to identify on-demand registration slices and perform corresponding operations when registering, and the terminal processes the information obtained from the network side in the above operations, which is complex.
  • the requirements for the terminal are relatively high, which increases the complexity of the terminal.
  • Embodiments of the present application provide a permitted NSSAI acquisition method, terminal and network-side device, which can solve the problem in related technologies that relies heavily on the terminal to identify different network slicing service types and requirements for the terminal.
  • a method for obtaining allowed network slice selection assistance information including: a terminal sending a first registration request to a first network element, wherein the first registration request carries the NSSAI requested by the terminal. ; After successfully registering to the network, the terminal receives the first information sent by the first network element; wherein the first information includes allowed NSSAI and first identification information, wherein the allowed NSSAI does not include: On-demand registration NSSAI, the first identification information is used to indicate the allowed on-demand registration NSSAI.
  • a device for obtaining allowed network slice selection auxiliary information including: a first sending module, configured to send a first registration request to the first network element, wherein the first registration request carries NSSAI requested by the terminal; a first receiving module, configured to receive the first information sent by the first network element; wherein the first information includes allowed NSSAI and first identification information, wherein the allowed NSSAI does not include : On-demand registration NSSAI, the first identification information is used to indicate the allowed on-demand registration NSSAI.
  • a method for obtaining allowed network slice selection auxiliary information including: a first network element receiving a first registration request sent by a terminal, wherein the first registration request carries the information requested by the terminal. NSSAI; the first network element determines at least one allowed NSSAI corresponding to the terminal based on the first target information; the first network element sends first information to the terminal, wherein the first information includes allowed NSSAI and first identification information, wherein the allowed NSSAI includes NSSAI in the at least one allowed NSSAI except the NSSAI corresponding to the network slice registered on demand, and the first identification information is used to indicate that the at least one allowed NSSAI An on-demand registered NSSAI within an allowed NSSAI.
  • a device for obtaining allowed network slice selection assistance information including: a second receiving module configured to receive a first registration request sent by a terminal, wherein the first registration request carries the NSSAI requested by the terminal; a second determination module, configured to determine at least one allowed NSSAI corresponding to the terminal based on the first target information; a second sending module, configured to send the first information to the terminal, wherein the The first information includes allowed NSSAI and first identification information, wherein the allowed NSSAI includes NSSAI in the at least one allowed NSSAI except the NSSAI corresponding to the network slice registered on demand, and the first identification information is NSSAI indicating on-demand registration among the at least one allowed NSSAI.
  • a method for obtaining a control policy including: the first network element sending a first request to a second network element, wherein the first request is used for a network control policy corresponding to terminal behavior information, The first request carries the terminal behavior information; the first network element receives at least one network control policy sent by the second network element, wherein the network control policy includes S-NSSAI and registration Correspondence between timers.
  • a device for obtaining a control policy including: a third sending module configured to send a first request to a second network element, wherein the first request is used for a network control policy corresponding to terminal behavior information , the first request carries the terminal behavior information; a third receiving module is used to receive at least one network control policy sent by the second network element, wherein the network control policy includes S-NSSAI Correspondence with registration timer.
  • a method for sending a control policy including: a second network element receiving a first request sent by a first network element, wherein the first request is used for a network control policy corresponding to terminal behavior information of a terminal ; The second network element determines at least one network control strategy based on the second target information, wherein the network control strategy includes Correspondence between S-NSSAI and registration timer; the second network element sends the at least one network control policy to the first network element.
  • a device for sending a control policy including: a fourth receiving module configured to receive a first request sent by a first network element, wherein the first request is used for terminal behavior information of a corresponding terminal.
  • Network control strategy configured to determine at least one network control strategy according to the second target information, wherein the network control strategy includes the corresponding relationship between S-NSSAI and the registration timer; the fourth sending module, Used to send the at least one network control policy to the first network element.
  • a method for controlling a PDU session including: a third network element receiving a PDU session establishment request sent by a terminal, the PDU session establishment request being used to request the establishment of a second PDU session; the third network element Send a second request to the second network element, where the second request is used for a session control policy corresponding to the terminal behavior information of the terminal; the third network element receives at least one item sent by the second network element Session control policy, wherein the session control policy includes the corresponding relationship between S-NSSAI and session timer; after determining that the second PDU session is established, the third network element starts a session corresponding to the second S-NSSAI The first session timer, the second S-NSSAI is the S-NSSAI corresponding to the second PDU session; when the first session timer times out, the third network element releases the third Two PDU sessions, wherein the first session timer is suspended when the user plane function UPF connection corresponding to the second PDU session is active or a new UPF
  • a control device for a PDU session including: a fifth receiving module, configured to receive a PDU session establishment request sent by a terminal, where the PDU session establishment request is used to request the establishment of a second PDU session; a fifth sending module A module configured to send a second request to a second network element, where the second request is used for a session control policy corresponding to terminal behavior information of the terminal; the fifth receiving module is further configured to receive the third At least one session control policy sent by the two network elements, wherein the session control policy includes the corresponding relationship between S-NSSAI and session timer; the second control module is used to: after determining that the second PDU session is established , start the first session timer corresponding to the second S-NSSAI, and the second S-NSSAI is the S-NSSAI corresponding to the second PDU session; when the first session timer times out, Release the second PDU session, wherein when the user plane function UPF connection corresponding to the second PDU session is in an active
  • a terminal in an eleventh aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions When the program or instructions are executed by the processor, the following is implemented: mentioned in the first aspect steps of the method.
  • a terminal including a processor and a communication interface, wherein the processor is used to implement the steps of the method described in the first aspect, and the communication interface is used to communicate with an external device.
  • a network side device in a thirteenth aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are used by the processor.
  • the steps of the method described in the third aspect, or the steps of the method described in the fifth aspect, or the steps of the method described in the seventh aspect, or the method described in the ninth aspect are realized. A step of.
  • a network side device including a processor and a communication interface, wherein the processor is used to implement the steps of the method described in the third aspect, or to implement the method described in the fifth aspect.
  • the communication interface is used to communicate with an external device.
  • a system for obtaining allowed network slice selection auxiliary information including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the method described in the first aspect.
  • the network side device Can be used to perform the steps of the method described in the third aspect, or implement the steps of the method described in the fifth aspect, or implement the steps of the method described in the seventh aspect, or implement the method described in the ninth aspect A step of.
  • a readable storage medium is provided. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method are implemented. The steps of the method described in the third aspect, or the steps of implementing the method described in the fifth aspect, or the steps of the method described in the seventh aspect, or the steps of the method described in the ninth aspect.
  • a chip in a seventeenth aspect, includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the method described in the first aspect. The steps of the method, or the steps of realizing the method as described in the third aspect, or the steps of realizing the method as described in the fifth aspect, or the steps of realizing the method as described in the seventh aspect, or the steps of realizing the method as described in the ninth aspect steps of the method described.
  • a computer program/program product is provided, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement as described in the first aspect
  • the terminal when the terminal initiates registration, it only needs to carry the NSSAI requested by the terminal.
  • the network side identifies the NSSAI allowed by the terminal and the NSSAI registered on demand among the NSSAI allowed by the terminal, thereby returning the allowed NSSAI and
  • the first identification information indicates the allowed NSSAI for on-demand registration, so that the terminal can learn the NSSAI for on-demand registration without requiring the terminal to identify different network slicing service types and requirements, thereby reducing requirements on the terminal.
  • Figure 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable
  • Figure 2a shows a schematic flowchart of a method for obtaining allowed network slice selection auxiliary information provided by an embodiment of the present application
  • Figure 2b shows another schematic flowchart of a method for obtaining allowed network slice selection auxiliary information provided by an embodiment of the present application
  • Figure 3 shows a schematic flowchart of a method for obtaining a control policy provided by an embodiment of the application
  • Figure 4 shows a schematic flowchart of a method for sending a control policy provided by an embodiment of the present application
  • Figure 5 shows a schematic flow chart of the PDU session control method provided by the embodiment of the present application.
  • Figure 6 shows another schematic flow chart of the PDU session control method provided by the embodiment of the present application.
  • Figure 7 shows a schematic flow chart of a policy update method in an embodiment of the present application
  • Figure 8 shows a schematic flow chart of another policy update method in the embodiment of the present application.
  • Figure 9 shows a schematic structural diagram of a device for obtaining allowed network slice selection auxiliary information provided by an embodiment of the present application.
  • Figure 10 shows another structural schematic diagram of an apparatus for obtaining allowed network slice selection assistance information provided by an embodiment of the present application
  • Figure 11 shows a schematic structural diagram of a device for obtaining a control strategy provided by an embodiment of the present application
  • Figure 12 shows a schematic structural diagram of a control strategy sending device provided by an embodiment of the present application
  • Figure 13 shows a schematic structural diagram of a PDU session control device provided by an embodiment of the present application.
  • Figure 14 shows a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 15 shows a schematic diagram of the hardware structure of a terminal provided by an embodiment of the present application.
  • Figure 16 shows a schematic diagram of the hardware structure of a network-side device provided by an embodiment of the present application.
  • first, second, etc. in the description and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first" and “second” are distinguished objects It is usually one type, and the number of objects is not limited.
  • the first object can be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the related objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced, LTE-A Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR New Radio
  • FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable.
  • the wireless communication system includes a terminal 11 and a network side device 12.
  • the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, or a super mobile personal computer.
  • Tablet Personal Computer Tablet Personal Computer
  • laptop computer laptop computer
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • UMPC ultra-mobile personal computer
  • UMPC mobile Internet device
  • MID mobile Internet Device
  • AR augmented reality
  • VR virtual reality
  • robots wearable devices
  • WUE Vehicle User Equipment
  • PUE Pedestrian User Equipment
  • smart home home equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.
  • game consoles personal computers (personal computer, PC), teller machine or self-service machine and other terminal-side devices.
  • Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets) bracelets, smart anklets, etc.), smart wristbands, smart clothing, etc.
  • the network side device 12 may include an access network device and/or a core network device, where the access network device 12 may also be called a radio access network device, a radio access network (Radio Access Network, RAN), or a radio access network. function or radio access network unit.
  • RAN Radio Access Network
  • the access network device 12 may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point or Wireless Fidelity (Wireless Fidelity, WiFi) node, etc.
  • the base station can be called Node B, Evolved Node B (eNB), access point, base transceiver station (Base Transceiver) Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B-node, home evolved B-node, transmitting receiving point (Transmitting Receiving Point, TRP) or some other appropriate terminology in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms.
  • Core network equipment may include but is not limited to at least one of the following: core network nodes, core network functions, mobility management entities (Mobility Management Entity, MME), access mobility management functions (Access and Mobility Management Function, AMF), session management functions (Session Management Function, SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Service Discovery function (Edge Application Server Discovery Function, EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), centralized network configuration ( Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (Local NEF, or L-NEF), Binding Support Function (Binding Support Function, BSF), application function (Application Function, AF), etc.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • PCF Policy Control Function
  • PCF may include access management PCF (Access Management PCF, AM-PCF) and session management PCF (Session Management PCF, SM-PCF).
  • access management PCF Access Management PCF
  • AM-PCF Access Management PCF
  • session management PCF Session Management PCF
  • SM-PCF Session Management PCF
  • Figure 2a shows a schematic flowchart of a method for obtaining allowed network slice selection assistance information in an embodiment of the present application.
  • the method 200a can be executed by a terminal.
  • the method may be performed by software or hardware installed on the terminal.
  • the method may include the following steps.
  • the terminal sends a first registration request to the first network element, where the first registration request carries the NSSAI requested by the terminal.
  • the first registration request can be used to register the network slice corresponding to the normal service, but not to register the network slice registered on demand. That is to say, in the embodiment of this application, the terminal does not need to distinguish the signature during initial registration.
  • the terminal does not need to distinguish the signature during initial registration.
  • the first registration request may be a request for the terminal to access the network.
  • the first registration request may be an attachment request (Attach Request) or a registration request (Registration Request) to register to the network.
  • the first network element may include an AMF.
  • the first registration request may also carry first indication information indicating that the terminal behavior is supported. For example, if the terminal itself has requirements for power saving, customized access, etc., the terminal may indicate the terminal requirements through the first indication information.
  • the requested NSSAI carried in the first registration request is requested by the terminal according to the normal business process, without the terminal needing to identify which services perform on-demand registration and session processes.
  • the requested NSSAI carried in the first registration request may be the NSSAI configured in the current Public Land Mobile Network (Public Land Mobile Network, PLMN).
  • PLMN Public Land Mobile Network
  • S212 The terminal receives the first information sent by the first network element.
  • the first information includes allowed NSSAI and first identification information, wherein the allowed NSSAI does not include: NSSAI for on-demand registration, and the first identification information is used to indicate the allowed NSSAI for on-demand registration.
  • the allowed NSSAI (Allowed NSSAI) is used to indicate the S-NSSAIs values that the UE could use in the Serving PLMN in the current Registration Area.
  • the first network element When the first registration request is an attach request or a registration request to register to the network, the first network element, after receiving the first registration request from the terminal, can execute the normal registration process and the Authentication Server Function (AUSF) Interact with UDM, etc. to complete the registration process.
  • the first network element can determine the value of the NSSAI allowed by the terminal. For network slices registered on demand, this NSSAI will not be added to the returned allowed NSSAI, and there will be no rejected NSSAI in the returned allowed NSSAI. (Rejected NSSAI).
  • the first network element can also return a first identification to indicate the allowed on-demand registration NSSAI. Therefore, the first identification can also be called on-demand allowed (On-demand Allowed) NSSAI. logo.
  • the terminal when the terminal initiates registration, it only needs to carry the NSSAI requested by the terminal.
  • the network side identifies the NSSAI allowed by the terminal and the NSSAI registered on demand among the NSSAI allowed by the terminal, thereby returning the allowed NSSAI and
  • the first identification information the returned allowed NSSAI does not include the NSSAI for on-demand registration, but indicates the allowed NSSAI for on-demand registration through the first identification information, so that the terminal can learn the NSSAI for on-demand registration, There is no need for the terminal to identify different network slicing service types and requirements, which reduces the load on the terminal and reduces the requirements on the terminal.
  • the method may further include the following steps:
  • Step 1 Based on the user equipment routing option policy (UE Route Selection Policy, URSP) rules, the terminal obtains the single network slice selection auxiliary information (Single Network) corresponding to the protocol data unit (Protocol Data Unit, PDU) session that transmits the service to be transmitted. Slice Selection Assistance Information, S-NSSAI).
  • UE Route Selection Policy UE Route Selection Policy
  • URSP User Equipment Routing Policy
  • URSP User Plane Selection Policy
  • S-NSSAI Slice Selection Assistance Information
  • the terminal matches the traffic of an application based on URSP rules, it obtains the matching traffic descriptor.
  • the traffic descriptor describes a set of attributes of the PDU session (that is, the attributes of the PDU session that transmits the service to be transmitted). This set of attributes It generally includes information such as S-NSSAI, data network name (DNN), and access type.
  • the S-NSSAI corresponding to the PDU session in step 1 is the S-NSSAI in the attributes of the PDU session determined based on the URSP rules.
  • Step 2 Determine that the S-NSSAI corresponding to the PDU session matches an allowed on-demand registration NSSAI indicated by the first identification information.
  • the terminal discovers that the S-NSSAI corresponding to the PDU session is an allowed on-demand registration NSSAI.
  • Step 3 The terminal sends a second registration request, where the second registration request is used to request registration to the network slice corresponding to the S-NSSAI.
  • the terminal sends a second registration request to request registration to the network slice corresponding to the S-NSSAI.
  • Step 4 After receiving the registration success response, the terminal sends a PDU session establishment request, where the PDU session establishment request is used to request the establishment of the PDU session.
  • some network slices may require the terminal to not need to register when there is no session request.
  • registration and PDU session requests are only initiated when there is a session requirement.
  • the terminal can only register to the NSSAI when it needs to establish a PDU session corresponding to the NSSAI registered on demand. This can reduce the unnecessary registration process of the terminal and meet the needs of power saving or differentiated operation and maintenance.
  • Figure 2b shows another schematic flowchart of a method for obtaining allowed network slice selection auxiliary information provided by an embodiment of the present application. As shown in Figure 2b, the method 200b mainly includes the following steps.
  • the first network element receives the first registration request sent by the terminal, where the first registration request carries the NSSAI requested by the terminal.
  • the first registration request is the same as the first registration request in method 200.
  • the first registration request is the same as the first registration request in method 200.
  • the first network element may include an AMF.
  • the first network element determines at least one allowed NSSAI corresponding to the terminal based on the first target information.
  • the first target information includes but is not limited to at least one of the following:
  • Operator side policy for example, the operator side specifies the terminal types applicable to each network slice, etc., and can determine the allowed NSSAI corresponding to the terminal.
  • User subscription information of the terminal For example, some special network slices may require the terminal to subscribe to certain special services before they can be used. Therefore, based on the user subscription information of the terminal, the allowed NSSAI corresponding to the user subscription information of the terminal can be obtained.
  • the first network element sends first information to the terminal, where the first information includes allowed NSSAI and first identification information, where the allowed NSSAI includes the at least one allowed NSSAI except NSSAI other than the NSSAI registered on demand, the first identification information is used to indicate the NSSAI registered on demand among the at least one allowed NSSAI.
  • the first network element determines at least one allowed NSSAI corresponding to the terminal, returns the NSSAI other than the NSSAI registered on demand to the terminal, and indicates the at least one allowed NSSAI through the first identification information.
  • the on-demand registration of NSSAI in NSSAI allows the terminal to register only the network slices corresponding to normal services without distinguishing the business needs of different network slices during initial registration. For on-demand registration network slices (only when there are (Initiate registration and session requests when the session is required) Do not register temporarily, and ensure that the network slice registered on demand will not be rejected. Subsequent registration and session requests can be flexibly initiated according to business needs.
  • FIG 3 shows a schematic flowchart of a control policy acquisition method provided by an embodiment of the present application. As shown in Figure 3, the method 300 mainly includes the following steps.
  • the first network element sends a first request to the second network element, where the first request is used for the network control policy corresponding to the terminal behavior information of the terminal, and the first registration request carries the terminal behavioral information.
  • the second network element may include PCF, or if the PCF includes AM-PCF and SM-PCF, the second network element may include AM-PCF.
  • the terminal behavior information may include one or more of the terminal's power saving requirements, customized access requirements, etc.
  • the first network element may send the first request to the second network element when the terminal initially registers, for example, after the terminal successfully registers to the network slice for the first time.
  • the first network element may send the first registration request after receiving the first registration request in methods 200a and 200b and after the terminal successfully registers with the network.
  • the first network element receives at least one network control policy sent by the second network element, where the network control policy includes the corresponding relationship between S-NSSAI and registration timer.
  • the first network element can obtain the network control policy from the second network element, so that the first network element can control the registration duration according to the network control policy to save resources.
  • the method may further include the following steps:
  • Step 1 The first network element executes a registration process for the terminal to register in the first network slice corresponding to the first S-NSSAI.
  • the first S-NSSAI may be an NSSAI corresponding to a normal business process, for example, an allowed (allowed) NSSAI included in the first information in methods 200a and 200b, or may be an on-demand registration (on- demand), for example, the NSSAI identified by the first identification information contained in the first information in methods 200a and 200b.
  • the first network element may register the terminal with the first network slice corresponding to the first S-NSSAI after receiving a registration request initiated by the terminal to register with the first network slice corresponding to the first S-NSSAI.
  • Registration process in the first network slice For example, after successfully registering with the network, the terminal obtains the first S-NSSAI corresponding to the PDU session that transmits the service to be transmitted based on the URSP rules, and determines that the first NSSAI is the NSSAI registered on demand based on the first identification information. , then a second registration request is sent. The second registration request is used to request registration to the first network slice corresponding to the first S-NSSAI.
  • the first network element After receiving the second registration request, the first network element executes the terminal Registration process in the first network slice corresponding to the first S-NSSAI.
  • the first network element may perform registration of the terminal with the first S-NSSAI after receiving a registration request from the terminal to the first network slice other than the on-demand registration network slice. The corresponding registration process in the first network slice.
  • Step 1 may be performed after S312 or before S310.
  • the terminal registering to the first network slice corresponding to the first S-NSSAI may be the first time the terminal registers to the network slice.
  • the step may be to perform S310 after the terminal successfully registers with the first network slice.
  • Step 2 When the terminal successfully registers with the first network slice, the first network element starts the first registration corresponding to the first S-NSSAI according to the at least one network control policy. timer.
  • Step 3 If the PDU session establishment request of the first PDU session corresponding to the first S-NSSAI is not received before the first registration timer expires, the first network element executes the terminal operation.
  • the deregistration process of the first network slice Through the deregistration process, the terminal's registration in the first network slice can be deregistered, and the terminal is in an unregistered state in the first network slice again.
  • the first network element performs monitoring of the registration duration according to the at least one network control policy. After the terminal registers to the network slice corresponding to the first S-NSSAI, if no targeting is initiated within a certain period of time, The establishment process of the first PDU session corresponding to the S-NSSAI triggers the deregistration process of the terminal in the network slice corresponding to the first S-NSSAI, and deregisters the terminal in the network slice corresponding to the first S-NSSAI to save resources. .
  • the network control policy may also include a corresponding relationship between the S-NSSAI and the session timer.
  • the PCF can decide the corresponding relationship between S-NSSAI and the registration timer (Reg_Timer) and the corresponding relationship between the S-NSSAI and the session timer (PDU_Timer). That is, the PCF can Determine access control policies and session control policies.
  • the method may further include the following steps:
  • Step 1 The first network element receives a PDU session establishment request initiated by the terminal, where the PDU session establishment request is used to request the establishment of a second PDU session corresponding to the second S-NSSAI.
  • the first network element receives a PDU session establishment request initiated by the terminal.
  • the PDU session establishment request is used to request the establishment of a second session corresponding to the second S-NSSAI. PDU session.
  • Step 2 After determining that the second PDU session is successfully established, the first network element starts the first session timer corresponding to the second S-NSSAI.
  • Step 3 When the first session timer times out, the first network element releases the second PDU session, wherein the UPF connection corresponding to the second PDU session is active or established with the In the case of a new UPF connection corresponding to the second PDU session, the first session timer is suspended; in the case of a UPF connection corresponding to the second PDU session being released, the first session timer counts.
  • the first network element can control the session duration, and when the first session timer corresponding to the second S-NSSAI times out, release the second PDU session to save PDU session resources.
  • the method may further include the following steps:
  • Step 1 The first network element receives a session release message sent by the third network element, where the session release message Used to indicate the release of the second PDU session.
  • the third network element may be SMF.
  • the AM-PCF sends the network control policy to the first network element, and the SMF sends a PDU session establishment request to the SM after receiving the PDU session establishment request requesting to establish the second PDU session.
  • -PCF sends a policy acquisition request to obtain the session control policy from SM-PCF.
  • SMF determines to release the second PDU session according to the session control policy, and then initiates the release process of the second PDU session and sends the request to the second PDU session.
  • a network element sends the session release message.
  • Step 2 The first network element releases the second PDU session.
  • the first network element releases the second PDU session based on the session release message.
  • the method may further include: the first network element starting a second registration timer corresponding to the second S-NSSAI, and If the PDU session establishment request corresponding to the second S-NSSAI is not received before the second registration timer expires, the first network element executes the terminal operation corresponding to the second S-NSSAI.
  • the first network element starts the second registration timer corresponding to the second S-NSSAI, and monitors the registration time for the terminal to register to the second S-NSSAI. If the PDU session establishment request corresponding to the second S-NSSAI is not received before the second registration timer times out, the deregistration process of the terminal in the second network slice may be triggered to save resources.
  • the method may further include the following steps:
  • Step 1 The first network element receives the updated at least one network control policy sent by the second network element;
  • Step 2 The first network element saves and uses the updated at least one network control policy.
  • the second network element can update the network control strategy and send the updated network control strategy to the first network element for use, thereby avoiding network control decisions caused by changes in the network environment and other factors.
  • differentiated business strategies can be implemented.
  • FIG 4 shows a schematic flowchart of a control policy sending method provided by an embodiment of the present application. As shown in Figure 4, the method 400 mainly includes the following steps.
  • the second network element receives the first request sent by the first network element, where the first request is used for the network control policy corresponding to the terminal behavior information of the terminal.
  • the first network element may send the first request as described in method 300.
  • the second network element may be a PCF.
  • the PCF may include AM-PCF and SM-PCF.
  • the second network element determines at least one network control policy based on the second target information, where the network control policy includes a corresponding relationship between the S-NSSAI and the registration timer.
  • the second target information includes at least one of the following:
  • the terminal can sign a contract in advance.
  • the terminal can be deregistered after the terminal does not perform transmission of the service for a certain period of time.
  • the terminal may not transmit the service for a long time in certain locations. Therefore, when the terminal is located in these locations, the terminal may After a certain period of time without performing the transmission of this service, the terminal will be deregistered.
  • the external application of AF may include the corresponding application server and application information external to AF.
  • the game provider will inform the operator of the access strategy when signing a contract with the operator network.
  • the user can be deregistered after the user does not use the game for more than a certain period of time.
  • the load condition of network slicing For example, when the load of a network slice exceeds a certain threshold, in order to allow other terminals to obtain the services provided by the network slice, the terminal can be deregistered after the user has not performed service transmission corresponding to the network slice for a long time.
  • S414 The second network element sends the at least one network control policy to the first network element.
  • the network control policy further includes a correspondence between S-NSSAI and session timers.
  • S-NSSAI Session timers.
  • the second network element can provide S-NSSAI to the first network element at the same time after receiving the first request. Corresponding registration timer and session timer.
  • the method may further include the following steps:
  • Step 1 The second network element determines to update the at least one network control policy
  • Step 2 The second network element obtains at least one updated network control policy
  • Step 3 The second network element sends the updated at least one network control policy to the first network element.
  • the network control policy includes an identification list of on-demand network slices (one or more S-NSSAI) and a corresponding control duration Reg_Timer.
  • the second network element may determine to update the at least one network control policy under at least one of the following conditions:
  • the second network element receives the trigger information of the external AF, and the trigger information is used to indicate updating the There is one less network control strategy; for example, the game company can negotiate with the operator to update the network control strategy, for example, update the corresponding relationship between the registration timer and S-NSSAI, that is, update the control duration corresponding to one or more S-NSSAI.
  • the second network element receives a notification from the UDR, and the notification indicates that the subscription information of the terminal has changed. For example, for a certain type of service, the terminal may update its subscription information.
  • the second network element obtains analysis information from NWDAF.
  • the second network element can obtain the analysis information obtained by NWDAF by evaluating and calculating the current and historical network operating status, and based on the analysis information, determine that the network control policy needs to be updated.
  • the second network element can update the network control strategy, so that different network control strategies can be formulated according to different situations.
  • the method may further include the following steps:
  • Step 1 The second network element receives a second request sent by a third network element, where the second request is used for a session control policy corresponding to the terminal behavior information.
  • the third network element may be SMF.
  • the PCF includes AM-PCF and SM-PCF
  • AM-PCF sends a network control policy to the first network element
  • SMF sends a PDU session establishment request to the first network element after receiving a PDU session establishment request requesting to establish a second PDU session.
  • SM-PCF sends a second request to request the session control policy corresponding to the terminal behavior information.
  • Step 2 The second network element determines at least one session control policy based on the second target information, where the session control policy includes the corresponding relationship between S-NSSAI and session timer.
  • the second network element may determine the at least one session control policy based on at least one of the user subscription information of the terminal, the location information of the terminal, the external application of the AF, and the load condition of the network slice.
  • Step 3 The second network element sends the at least one session control policy to the third network element.
  • the second network element sends at least one session control policy to the third network element, and the third network element controls the session duration of the terminal based on the at least one session control policy,
  • the method may further include at least one of the following:
  • Step 1 The second network element determines to update the at least one session control policy
  • Step 2 The second network element obtains at least one updated session control policy
  • Step 3 The second network element sends the updated at least one session control policy to the third network element.
  • the session control policy includes an identification list of on-demand network slicing (one or more S-NSSAI) and the corresponding The session control duration PDU_Timer.
  • the second network element may determine to update the at least one session control policy under at least one of the following conditions:
  • the second network element receives trigger information from the external AF, where the trigger information is used to indicate updating the at least one session control policy;
  • the second network element receives a notification from the unified data warehousing UDR, and the notification indicates that the subscription information of the terminal has changed;
  • the second network element obtains analysis information from the network data analysis function NWDAF.
  • the second network element can update the session control policy, so that different session control policies can be formulated according to different situations.
  • Figure 5 shows a schematic flowchart of a PDU session control method provided by an embodiment of the present application. As shown in Figure 5, the method 500 mainly includes the following steps.
  • the third network element receives a PDU session establishment request sent by the terminal, where the PDU session establishment request is used to request the establishment of a second PDU session.
  • the terminal can initiate a PDU session establishment request.
  • the PDU session establishment request can carry terminal behavior information, such as the terminal's power saving requirements, the terminal's customized access requirements, etc.
  • the third network element for example, SMF receives the PDU session establishment request sent by the terminal.
  • the third network element sends a second request to the second network element, where the second request is used for a session control policy corresponding to the terminal behavior information of the terminal.
  • the third network element may send the second request to the second network element in the policy process.
  • the third network element receives at least one session control policy sent by the second network element, where the session control policy includes the corresponding relationship between S-NSSAI and session timer.
  • the second network element may obtain and send the at least one session control policy in the manner described in the above method 400.
  • the relevant description in the method 400 please refer to the relevant description in the method 400, which will not be described again here.
  • S516 After determining that the second PDU session is established, the third network element starts the first session timer corresponding to the second S-NSSAI, and the second S-NSSAI is corresponding to the second PDU session. S-NSSAI.
  • the third network element can control the duration of the PDU session based on the session control policy to save resources.
  • the method further includes: the third network element sends a session release message to the first network element, wherein: The session release message is used to indicate releasing the second PDU session.
  • the third network element releases the second PDU session
  • the first network element is notified, so that the first network element can learn that the second PDU session is released and start the second S corresponding to the second PDU session.
  • - NSSAI registration timer If the terminal does not receive a request from the terminal to initiate a PDU session corresponding to the second S-NSSAI before the registration timer of the second S-NSSAI expires, the terminal is triggered to respond to the second S-NSSAI. The deregistration process of the network slice.
  • Figure 6 shows another schematic flow chart of the PDU session control method provided by the embodiment of the present application. As shown in Figure 6, the method mainly includes the following steps:
  • Step 601 The UE initiates a registration request.
  • the network can be required to provide UE Behavior policy request information to the AMF.
  • the Request NSSAI initiated by the UE here is requested according to the normal business process, and there is no need to identify which services require on-demand registration and session processes.
  • the UE does not carry UE behavior information, then whether to distribute the corresponding policy is completely determined by the network, for example, based on PLMN, subscription, network load, service characteristics, etc.
  • Step 602 AMF performs the normal registration process and the interactive registration process with AUSF and UDM. If you need to perform network slice reselection, you need to interact with NSSF and so on.
  • AMF determines the value of Allowed NSSAI based on operator policy, terminal current location information, user subscription, current network slice load, etc. For network slices registered on demand, this NSSAI is not added to the returned Allowed NSSAI, but It also does not exist in Rejected NSSAI, and a new On-demand Allowed NSSAI flag is added and eventually passed to the terminal.
  • the terminal When the terminal subsequently has a business request for PDU session connection, it matches the URSP.
  • the S-NSSAI corresponding to the matching PDU session is consistent with the On-demand Allowed NSSAI, the terminal first initiates registration and then initiates a PDU Session request.
  • the normal process is executed. In this case, the UE does not need to perform excessive operations to perform corresponding registration request differentiation, reducing the load of the UE.
  • the modification of the network policy is more flexible and can focus on multiple aspects. Factors such as load, tracking area (TA) information, external strategies, etc.
  • Steps 603-605 AMF initiates Npcf_AMPlicyControl_Create Request to PCF/AM-PCF, please Find the response strategy supported by the corresponding UE Behavior.
  • PCF customizes one or more network control strategies based on the terminal's contract, AF external application, terminal's current location, current network load, etc., and returns the registration management timer (Reg_Timer) and the corresponding S-NSSAI is used by AMF to perform access control on the responding S-NSSAI.
  • Step 606 the rest of the registration process is completed.
  • Step 607 After receiving the Reg_Timer, the AMF monitors the current registration status of the corresponding S-NSSAI. If AMF continues to fail to receive the terminal's PDU Session Establishment Request request for S-NSSAI, after the Reg_timer expires, AMF triggers the deregistration operation of this terminal.
  • the AMF can accept two different types of timers at the same time during the first terminal registration.
  • the PCF does not distinguish between AM-PCF and SM-PCF, and only one type is deployed in the network. Type PCF, and then perform the corresponding operation.
  • PDU_Timer can be sent to AMF at the same time as registration, and AMF can also trigger PDU Session Release. In this case, steps 608-613 can be skipped.
  • Step 608 The terminal initiates a PDU Session Establishment Request and carries the UE Behavior support request.
  • Step 609 Complete session SMF selection and PDU Session authentication and authentication
  • Steps 610-612 in the policy process, the SMF selects the PCF and initiates an Npcf_SMPlicyControl_Create Request to the selected PCF, requesting the response policy supported by the corresponding UE Behavior.
  • the PCF selects the PCF based on the terminal's contract, AF external application, terminal's current location, and network.
  • One or more customized session control policies based on current load and other conditions, including PDU_timer and corresponding S-NSSAI, are returned to SMF for SMF to perform access control on the responding S-NSSAI.
  • Step 613 the rest of the PDU session establishment process.
  • Step 614 SMF starts the received PDU_Timer and monitors the current PDU session status.
  • Step 615 If the current UPF connection is active or there is a new UPF connection, the PDU_timer does not work, the UPF connection is released, and the PDU_Timer starts timing. If the PDU_Timer expires, SMF triggers the related operations of PDU Session Release (PDU Session Release).
  • Step 616 SMF sends a PDU connection release message to AMF, triggering AMF to start the corresponding Reg_Timer. If the Reg_Timer expires and there is no new PDU session request, AMF triggers the terminal deregistration process.
  • Figure 7 shows a schematic flow chart of a policy update method in the embodiment of the present application. As shown in Figure 7, the method mainly includes the following steps:
  • Step 701 After AM-PCF formulates and sends the control strategy (for example, the above-mentioned network control strategy), it decides to update the control strategy.
  • the updated information may be triggered by one or more of the following situations (including but not limited to).
  • Step 702 AM-PCF formulates a policy.
  • Step 703 AM-PCF sends the corresponding RPRM policy to AMF under Npcf_AMPolicyControl_UpdateNotify.
  • the control policy includes the on-demand network slice identification list (one or more S-NSSAI) and the corresponding control duration Reg_Timer.
  • Step 704 AMF deploys and saves the received policy.
  • FIG. 8 shows a schematic flow chart of another policy update method in the embodiment of the present application. As shown in Figure 8, the method mainly includes the following steps:
  • Step 801 After SM-PCF formulates and sends a control policy (for example, the above-mentioned session control policy), SM-PCF decides to update the policy.
  • the updated information may consist of one or more of the following (including but not limited to) Situation trigger a) Triggered by external AF b) UDR notification c) Analysis information obtained from NWDAF.
  • Step 802 SM-PCF formulates a strategy.
  • Step 803 PCF sends the corresponding policy to SMF under Npcf_SMPolicyControl_UpdateNotify.
  • the policy includes the on-demand network slice identification list (one or more S-NSSAI) and the corresponding control duration PDU_Timer.
  • Step 804 SMF deploys and saves the received policy.
  • the embodiments of the present application provide the above method, and the execution subject may be a virtual device.
  • a virtual device is used as an example to perform the above method to describe each device provided by the embodiment of the present application.
  • Figure 9 shows a schematic structural diagram of a device for obtaining allowed network slice selection assistance information provided by an embodiment of the present application.
  • the device mainly includes: a first sending module 901 and a first receiving module 902.
  • the first sending module 901 is configured to send a first registration request to the first network element, where the first registration request carries the NSSAI requested by the terminal;
  • the first receiving module 902 is configured to Receive the first information sent by the first network element; wherein the first information includes allowed NSSAI and first identification information, wherein the allowed NSSAI does not include: NSSAI registered on demand, the first identification information Information used to indicate the NSSAI allowed for on-demand registration.
  • the device may further include: a first obtaining module 903 and a first determining module 904; wherein the first obtaining module 903 is used to obtain, based on URSP rules, Transmit the S-NSSAI corresponding to the PDU session of the service to be transmitted; the first determination module 904 is used to determine the S-NSSAI corresponding to the PDU session and an allowed on-demand registration NSSAI indicated by the first identification information matching; the first sending module 901 is also used to send a second registration request, wherein the second registration request is used to request registration to the The network slice corresponding to the S-NSSAI identification; the first receiving module is also used to receive a registration success response; the first sending module 901 is also used to send a PDU session establishment request, wherein the PDU session establishment Request is used to request to establish the PDU session.
  • a first obtaining module 903 is used to obtain, based on URSP rules, Transmit the S-NSSAI corresponding to the PDU session of the service to be transmitted
  • the first registration request also carries first indication information indicating that the terminal behavior is supported.
  • the device for obtaining the allowed network slice selection assistance information in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or may be a component in the electronic device, such as an integrated circuit or chip.
  • the electronic device may be a terminal or other devices other than the terminal.
  • terminals may include but are not limited to the types of terminals 11 listed above, and other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., which are not specifically limited in the embodiment of this application.
  • the device for obtaining the allowed network slice selection auxiliary information provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 2a and achieve the same technical effect. To avoid duplication, it will not be described again here.
  • Figure 10 shows another structural schematic diagram of an apparatus for obtaining allowed network slice selection auxiliary information provided by an embodiment of the present application.
  • the apparatus 1000 mainly includes a second receiving module 1001, a second determining module 1002 and The second sending module 1003.
  • the second receiving module 1001 is used to receive the first registration request sent by the terminal, wherein the first registration request carries the NSSAI requested by the terminal; the second determining module 1002 is used to Based on the first target information, determine at least one allowed NSSAI corresponding to the terminal; the second sending module 1003 is used to send the first information to the terminal, wherein the first information includes the allowed NSSAI and a first identification Information, wherein the allowed NSSAI includes the NSSAI in the at least one allowed NSSAI except the NSSAI corresponding to the network slice registered on demand, and the first identification information is used to indicate the at least one allowed NSSAI. NSSAI registered on demand.
  • the first target information includes at least one of the following:
  • the location information of the terminal is the location information of the terminal.
  • the load of the network slice is the load of the network slice.
  • the device for obtaining the allowed network slice selection auxiliary information provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 2b and achieve the same technical effect. To avoid duplication, it will not be described again here.
  • FIG 11 shows a schematic structural diagram of a device for obtaining a control strategy provided by an embodiment of the present application.
  • the device 1100 mainly includes: a third sending module 1101 and a third receiving module 1102.
  • the third sending module 1101 is configured to send a first request to the second network element, where the first request is used for the network control policy corresponding to the terminal behavior information of the terminal, and the first request carries the terminal behavior information;
  • the third receiving module 1102 is configured to receive at least one network control policy sent by the second network element, wherein the network control policy includes S-NSSAI and registration timer Correspondence.
  • the device may also include: a first control module 1103, used for:
  • the network control policy also includes the corresponding relationship between S-NSSAI and session timer; the third receiving module 1102 is also used to receive a PDU session establishment request initiated by the terminal, wherein , the PDU session establishment request is used to request the establishment of a second PDU session corresponding to the second S-NSSAI; the first control module 1103 is also used to start the connection with the second PDU session after determining that the second PDU session is successfully established.
  • the first session timer corresponding to the second S-NSSAI when the first session timer times out, release the second PDU session, wherein the UPF connection corresponding to the second PDU session is active state or establish a new UPF connection corresponding to the second PDU session, the first session timer is suspended, and when the UPF connection corresponding to the second PDU session is released, the first session The timer counts.
  • the third receiving module 1102 is further configured to receive a session release message sent by the third network element after receiving at least one network control policy returned by the second network element, wherein, The session release message is used to indicate releasing the second PDU session; the first control module 1103 is also used to release the second PDU session.
  • the first control module 1103 is also configured to start a second registration timer corresponding to the second S-NSSAI after releasing the second PDU session. If the PDU session establishment request corresponding to the second S-NSSAI is not received before the timer expires, execute the deregistration process of the terminal in the second network slice corresponding to the second S-NSSAI, wherein, The second S-NSSAI corresponds to the second PDU session.
  • the third receiving module 1102 is also configured to receive the The updated at least one network control policy.
  • control strategy acquisition device provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 3 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • Figure 12 shows a schematic structural diagram of a control strategy sending device provided by an embodiment of the present application.
  • the device 1200 mainly includes: a fourth receiving module 1201, a third determining module 1202 and a fourth sending module 1203 .
  • the fourth receiving module 1201 is used to receive the first request sent by the first network element, where the first request is used for the network control policy corresponding to the terminal behavior information of the terminal; the third determining module 1202, configured to determine at least one network control strategy based on the second target information, wherein the network control strategy includes a corresponding relationship between S-NSSAI and the registration timer; a fourth sending module 1203, configured to send the A network element sends the at least one network control policy.
  • the fourth receiving module 1201 is also configured to receive a second request sent by a third network element, where the second request is used for a session control policy corresponding to the terminal behavior information;
  • the third determination module 1202 is further configured to determine at least one session control policy according to the second target information, wherein the session control policy includes a corresponding relationship between a single NSSAI and a session timer;
  • the fourth The sending module 1203 is also configured to send the at least one session control policy to the third network element.
  • the third determining module 1202 is also used to determine to update the at least one session control policy, and obtain the updated at least one session control policy; the fourth sending module 1203, It is also used to send the updated at least one session control policy to the third network element.
  • the third determining module 1202 determines to update the at least one session control policy under at least one of the following circumstances:
  • the third determining module 1202 is also used to determine to update the at least one network control policy, and obtain the updated at least one network control policy; the fourth sending module 1203, It is also used to send the updated at least one session control policy to the first network element.
  • the third determining module 1202 determines to update the at least one network control policy under at least one of the following circumstances:
  • control strategy sending device provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 4 and achieve the same technical effect. To avoid duplication, details will not be described here.
  • Figure 13 shows a schematic structural diagram of a PDU session control device provided by an embodiment of the present application.
  • the device 1300 mainly includes: a fifth receiving module 1301, a fifth sending module 1302 and a second control module 1303 .
  • the fifth receiving module 1301 is used to receive a PDU session establishment request sent by the terminal, and the PDU session establishment request is used to request the establishment of a second PDU session; the fifth sending module 1302 is used to send a request to the second PDU session.
  • the network element sends a second request, where the second request is used for a session control policy corresponding to the terminal behavior information of the terminal; the fifth receiving module 1301 is also used to receive at least A session control policy, wherein the session control policy includes the corresponding relationship between S-NSSAI and session timer; the second control module 1303 is configured to: after determining that the second PDU session is established, start the communication with the second PDU session.
  • the first session timer corresponding to S-NSSAI, the second S-NSSAI is the S-NSSAI corresponding to the second PDU session; when the first session timer times out, release the second PDU session, wherein the first session timer is suspended when the user plane function UPF connection corresponding to the second PDU session is active or a new UPF connection corresponding to the second PDU session is established, When the UPF connection corresponding to the second PDU session is released, the first session timer counts.
  • the fifth sending module 1302 is further configured to send a session release message to the first network element, where the session release message is used to indicate releasing the second PDU session.
  • the PDU session control device provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 5 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • this embodiment of the present application also provides a communication device 1400, which includes a processor 1401 and a memory 1402.
  • the memory 1402 stores programs or instructions that can be run on the processor 1401, such as , when the communication device 1400 is a terminal, when the program or instruction is executed by the processor 1401, each step of the above-mentioned allowed network slice selection assistance information acquisition method 200a embodiment can be achieved, and the same technical effect can be achieved.
  • the communication device 1400 is a network-side device, when the program or instruction is executed by the processor 1401, the steps of the method 200b for obtaining the allowed network slice selection auxiliary information are implemented, or the method 300 for obtaining the control policy is implemented.
  • An embodiment of the present application also provides a terminal, including a processor and a communication interface.
  • the processor is used to implement the above allowed
  • the communication interface is used to communicate with external devices.
  • This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment.
  • Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
  • FIG. 15 is a schematic diagram of the hardware structure of a terminal that implements an embodiment of the present application.
  • the terminal 1500 includes but is not limited to: a radio frequency unit 1501, a network module 1502, an audio output unit 1503, an input unit 1504, a sensor 1505, a display unit 1506, a user input unit 1507, an interface unit 1508, a memory 1509, a processor 1510, etc. At least some parts.
  • the terminal 1500 may also include a power supply (such as a battery) that supplies power to various components.
  • the power supply may be logically connected to the processor 1510 through a power management system, thereby managing charging, discharging, and power consumption through the power management system. Management and other functions.
  • the terminal structure shown in FIG. 15 does not constitute a limitation on the terminal.
  • the terminal may include more or fewer components than shown in the figure, or some components may be combined or arranged differently, which will not be described again here.
  • the input unit 1504 may include a graphics processor (Graphics Processing Unit, GPU) 15041 and a microphone 15042.
  • the graphics processor 15041 is responsible for the image capture device (GPU) in the video capture mode or the image capture mode. Process the image data of still pictures or videos obtained by cameras (such as cameras).
  • the display unit 1506 may include a display panel 15061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 1507 includes a touch panel 15071 and at least one of other input devices 15072 .
  • Touch panel 15071 also known as touch screen.
  • the touch panel 15071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 15072 may include but are not limited to physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described again here.
  • the radio frequency unit 1501 can transmit it to the processor 1510 for processing; in addition, the radio frequency unit 1501 can send uplink data to the network side device.
  • the radio frequency unit 1501 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low noise amplifier, duplexer, etc.
  • Memory 1509 may be used to store software programs or instructions as well as various data.
  • the memory 1509 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, Image playback function, etc.) etc.
  • memory 1509 may include volatile memory or nonvolatile memory, or memory 1509 may include both volatile and nonvolatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) and Direct Rambus RAM (DRRAM).
  • RAM Random Access Memory
  • Static RAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM Double Data Rate SDRAM
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM enhanced synchronous dynamic random access memory
  • Synchlink DRAM, SLDRAM synchronous link dynamic random access memory
  • DRRAM Direct Rambus RAM
  • the processor 1510 may include one or more processing units; optionally, the processor 1510 integrates an application processor and a modem processor, where the application processor mainly handles operations related to the operating system, user interface, application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the above modem processor may not be integrated into the processor 1510.
  • the radio frequency unit 150 is configured to send a first registration request to the first network element, where the first registration request carries the NSSAI requested by the terminal; receive the first information sent by the first network element; wherein, The first information includes allowed NSSAI and first identification information, wherein the allowed NSSAI does not include: NSSAI for on-demand registration, and the first identification information is used to indicate the allowed NSSAI for on-demand registration.
  • Embodiments of the present application also provide a network-side device, including a processor and a communication interface.
  • the processor is used to implement each step of the above-mentioned method 200b for obtaining the allowed network slice selection auxiliary information, or to implement the above-mentioned method 300 for obtaining the control strategy.
  • Each step of the embodiment, or each step of the above-mentioned control policy sending method 400 embodiment, or each step of the above-mentioned PDU session control method 500 embodiment is implemented, and the communication interface is used to communicate with external devices.
  • This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment.
  • Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.
  • the embodiment of the present application also provides a network side device.
  • the network side device 1600 includes: a processor 1601, a network interface 1602, and a memory 1603.
  • the network interface 1602 is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 1600 in this embodiment of the present invention also includes: instructions or programs stored in the memory 1603 and executable on the processor 1601.
  • the processor 1601 calls the instructions or programs in the memory 1603 to execute the instructions shown in Figures 10 to 13. It shows the execution method of each module and achieves the same technical effect. To avoid duplication, it will not be repeated here.
  • Embodiments of the present application also provide a readable storage medium on which a program or instructions are stored.
  • the above-mentioned method 200a for obtaining auxiliary information for network slice selection is implemented.
  • Each process in the example, or each process in the above-mentioned PDU session control method 500 embodiment can achieve the same technical effect. To avoid duplication, it will not be described again here.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes computer readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disk, etc.
  • An embodiment of the present application further provides a chip.
  • the chip includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions.
  • the above-mentioned allowed network slice selection auxiliary information Each process of the acquisition method 200a embodiment, or implement each process of the above allowed network slice selection auxiliary information acquisition method 200b embodiment, or implement each process of the above control strategy acquisition method 300 embodiment, or implement the above control strategy.
  • the various processes of the embodiment of the sending method 400, or the various processes of the embodiment of the above-mentioned PDU session control method 500, can achieve the same technical effect. To avoid duplication, they will not be described again here.
  • chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.
  • Embodiments of the present application further provide a computer program/program product, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the above allowed network slice selection.
  • the various processes of the method 200a for obtaining auxiliary information, or the various processes of the method 200b for obtaining auxiliary information for allowing network slice selection, or the various processes of the method 300 for obtaining the control policy, or the above Each process of the control policy sending method 400 embodiment, or each process of the above PDU session control method 500 embodiment, can achieve the same technical effect, and will not be described again here to avoid duplication.
  • the embodiment of the present application also provides a system for obtaining allowed network slice selection auxiliary information, including: a terminal and a network side device.
  • the terminal can be used to perform the above-mentioned method 200a for obtaining allowed network slice selection auxiliary information.
  • the network side device may be used to perform the various processes of the above-mentioned embodiment of the method 200b for obtaining the allowed network slice selection assistance information, or perform the various processes of the above-mentioned embodiment of the method 300 for obtaining the control policy, or Execute each process of the above-mentioned control policy sending method 400 embodiment, or execute each process of the above-mentioned PDU session control method 500 embodiment.
  • the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation.
  • the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology.
  • the computer software product is stored in a storage medium (such as ROM/RAM, disk , CD), including several instructions to cause a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of this application.

Landscapes

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

Abstract

本申请公开了一种允许的NSSAI的获取方法、终端及网络侧设备,属于无线通信领域,本申请实施例的允许的网络切片选择辅助信息的获取方法,包括:终端向第一网元发送第一注册请求,其中,所述第一注册请求中携带有所述终端请求的NSSAI;在注册到网络成功后,所述终端接收所述第一网元发送的第一信息;其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中不包括:按需注册的NSSAI,所述第一标识信息用于指示允许的按需注册的NSSAI。

Description

允许的NSSAI的获取方法、终端及网络侧设备
交叉引用
本申请要求在2022年07月21日提交中国专利局、申请号为202210860357.1、发明名称为“允许的NSSAI的获取方法、终端及网络侧设备”的中国专利申请的优先权,该申请的全部内容通过引用结合在本申请中。
技术领域
本申请属于无线通信技术领域,具体涉及一种允许的网络切片选择辅助信息(Network Slice Selection Assistance Information,NSSAI)的获取方法、终端及网络侧设备。
背景技术
在相关技术中,终端在接入网络时,携带请求的NSSAI(Requested NSSAI),网络侧接收到终端的请求后,返回允许的NASSAI(Allowed NSSAI)。
在相关技术中,网络侧为终端静态配置接入控制信息以及会话控制信息,终端在发起注册请求及会话请求时,需要判断多维度的限制信息并最终按需选择Requested NSSAI进行注册。也就是说,终端在开机注册时需要识别业务属性,在不同的区域范围、不同的业务要求下判定Request NSSAI包含的单一网络切片选择辅助信息(单一网络切片选择辅助信息,S-NSSAI)列表(list)。因此,在相关技术中,强依赖于终端识别不同的网络切片业务类型和需求,要求终端在注册时即识别按需注册切片并执行对应操作,且终端处理上述操作从网络侧获取的信息复杂,对终端要求较高,增加了终端的复杂度。
发明内容
本申请实施例提供一种允许的NSSAI的获取方法、终端及网络侧设备,能够解决相关技术中强依赖于终端识别不同的网络切片业务类型和需求对终端要求较高的问题。
第一方面,提供了一种允许的网络切片选择辅助信息的获取方法,包括:终端向第一网元发送第一注册请求,其中,所述第一注册请求中携带有所述终端请求的NSSAI;在注册到网络成功后,所述终端接收所述第一网元发送的第一信息;其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中不包括:按需注册的NSSAI,所述第一标识信息用于指示允许的按需注册的NSSAI。
第二方面,提供了一种允许的网络切片选择辅助信息的获取装置,包括:第一发送模块,用于向第一网元发送第一注册请求,其中,所述第一注册请求中携带有终端请求的NSSAI;第一接收模块,用于接收所述第一网元发送的第一信息;其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中不包括:按需注册的NSSAI,所述第一标识信息用于指示允许的按需注册的NSSAI。
第三方面,提供了一种允许的网络切片选择辅助信息的获取方法,包括:第一网元接收终端发送的第一注册请求,其中,所述第一注册请求中携带有所述终端请求的NSSAI;所述第一网元基于第一目标信息,确定所述终端对应的至少一个允许的NSSAI;所述第一网元向所述终端发送第一信息,其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中包括所述至少一个允许的NSSAI中除按需注册的网络切片对应的NSSAI之外的NSSAI,所述第一标识信息用于指示所述至少一个允许的NSSAI中的按需注册的NSSAI。
第四方面,提供了一种允许的网络切片选择辅助信息的获取装置,包括:第二接收模块,用于接收终端发送的第一注册请求,其中,所述第一注册请求中携带有所述终端请求的NSSAI;第二确定模块,用于基于第一目标信息,确定所述终端对应的至少一个允许的NSSAI;第二发送模块,用于向所述终端发送第一信息,其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中包括所述至少一个允许的NSSAI中除按需注册的网络切片对应的NSSAI之外的NSSAI,所述第一标识信息用于指示所述至少一个允许的NSSAI中的按需注册的NSSAI。
第五方面,提供了一种控制策略的获取方法,包括:所述第一网元向第二网元发送第一请求,其中,所述第一请求用于对应终端行为信息的网络控制策略,所述第一请求中携带有所述终端行为信息;所述第一网元接收所述第二网元发送的至少一项网络控制策略,其中,所述网络控制策略中包括S-NSSAI与注册定时器的对应关系。
第六方面,提供了一种控制策略的获取装置,包括:第三发送模块,用于向第二网元发送第一请求,其中,所述第一请求用于对应终端行为信息的网络控制策略,所述第一请求中携带有所述终端行为信息;第三接收模块,用于接收所述第二网元发送的至少一项网络控制策略,其中,所述网络控制策略中包括S-NSSAI与注册定时器的对应关系。
第七方面,提供了一种控制策略的发送方法,包括:第二网元接收第一网元发送的第一请求,其中,所述第一请求用于对应终端的终端行为信息的网络控制策略;所述第二网元根据第二目标信息,确定至少一项网络控制策略,其中,所述网络控制策略中包括 S-NSSAI与注册定时器的对应关系;所述第二网元向所述第一网元发送所述至少一项网络控制策略。
第八方面,提供了一种控制策略的发送装置,包括:第四接收模块,用于接收第一网元发送的第一请求,其中,所述第一请求用于对应终端的终端行为信息的网络控制策略;第三确定模块,用于根据第二目标信息,确定至少一项网络控制策略,其中,所述网络控制策略中包括S-NSSAI与注册定时器的对应关系;第四发送模块,用于向所述第一网元发送所述至少一项网络控制策略。
第九方面,提供了一种PDU会话的控制方法,包括:第三网元接收终端发送的PDU会话建立请求,所述PDU会话建立请求用于请求建立第二PDU会话;所述第三网元向第二网元发送第二请求,其中,所述第二请求用于对应所述终端的终端行为信息的会话控制策略;所述第三网元接收所述第二网元发送的至少一项会话控制策略,其中,所述会话控制策略中包括S-NSSAI与会话定时器的对应关系;在确定所述第二PDU会话建立之后,所述第三网元启动与第二S-NSSAI对应的第一会话定时器,所述第二S-NSSAI为与所述第二PDU会话对应的S-NSSAI;在所述第一会话定时器超时的情况下,所述第三网元释放所述第二PDU会话,其中,在所述第二PDU会话对应的用户面功能UPF连接为激活态或建立与所述第二PDU会话对应的新的UPF连接的情况下,所述第一会话定时器暂停,在所述第二PDU会话对应的UPF连接释放的情况下,所述第一会话定时器进行计时。
第十方面,提供了一种PDU会话的控制装置,包括:第五接收模块,用于接收终端发送的PDU会话建立请求,所述PDU会话建立请求用于请求建立第二PDU会话;第五发送模块,用于向第二网元发送第二请求,其中,所述第二请求用于对应所述终端的终端行为信息的会话控制策略;所述第五接收模块,还用于接收所述第二网元发送的至少一项会话控制策略,其中,所述会话控制策略中包括S-NSSAI与会话定时器的对应关系;第二控制模块,用于:在确定所述第二PDU会话建立之后,启动与第二S-NSSAI对应的第一会话定时器,所述第二S-NSSAI为与所述第二PDU会话对应的S-NSSAI;在所述第一会话定时器超时的情况下,释放所述第二PDU会话,其中,在所述第二PDU会话对应的用户面功能UPF连接为激活态或建立与所述第二PDU会话对应的新的UPF连接的情况下,所述第一会话定时器暂停,在所述第二PDU会话对应的UPF连接释放的情况下,所述第一会话定时器进行计时。
第十一方面,提供了一种终端,该终端包括处理器和存储器,所述存储器存储可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第一方面所述 的方法的步骤。
第十二方面,提供了一种终端,包括处理器及通信接口,其中,所述处理器用于实现如第一方面所述的方法的步骤,所述通信接口用于与外部设备进行通信。
第十三方面,提供了一种网络侧设备,该网络侧设备包括处理器和存储器,所述存储器存储可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第三方面所述的方法的步骤,或者实现如第五方面所述的方法的步骤,或者实现如第七方面所述的方法的步骤,或者实现如第九方面所述的方法的步骤。
第十四方面,提供了一种网络侧设备,包括处理器及通信接口,其中,所述处理器用于实现如第三方面所述的方法的步骤,或者实现如第五方面所述的方法的步骤,或者实现如第七方面所述的方法的步骤,或者实现如第九方面所述的方法的步骤,所述通信接口用于与外部设备进行通信。
第十五方面,提供了一种允许的网络切片选择辅助信息的获取系统,包括:终端及网络侧设备,所述终端可用于执行如第一方面所述的方法的步骤,所述网络侧设备可用于执行如第三方面所述的方法的步骤,或者实现如第五方面所述的方法的步骤,或者实现如第七方面所述的方法的步骤,或者实现如第九方面所述的方法的步骤。
第十六方面,提供了一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤,或者实现如第三方面所述的方法的步骤,或者实现如第五方面所述的方法的步骤,或者实现如第七方面所述的方法的步骤,或者实现如第九方面所述的方法的步骤。
第十七方面,提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现如第一方面所述的方法的步骤,或实现如第三方面所述的方法的步骤,或者实现如第五方面所述的方法的步骤,或者实现如第七方面所述的方法的步骤,或者实现如第九方面所述的方法的步骤。
第十八方面,提供了一种计算机程序/程序产品,所述计算机程序/程序产品被存储在存储介质中,所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面所述的方法的步骤,或实现如第三方面所述的方法的步骤,或者实现如第五方面所述的方法的步骤,或者实现如第七方面所述的方法的步骤,或者实现如第九方面所述的方法的步骤。
在本申请实施例中,终端在发起注册时,只需携带终端请求的NSSAI,由网络侧识别终端允许的NSSAI以及终端允许的NSSAI中的按需注册的NSSAI,从而向终端返回允许的NSSAI和第一标识信息,返回的允许NSSAI中不包括按需注册的NSSAI,而是通过 第一标识信息指示允许的按需注册的NSSAI,从而使得终端可以获知按需注册的NSSAI,无需终端识别不同的网络切片业务类型和需求,降低了对终端的要求。
附图说明
图1示出本申请实施例可应用的一种无线通信系统的框图;
图2a示出本申请实施例提供的允许的网络切片选择辅助信息的获取方法的一种流程示意图;
图2b示出本申请实施例提供的允许的网络切片选择辅助信息的获取方法的另一种流程示意图;
图3示出申请实施例提供的控制策略的获取方法的一种流程示意图;
图4示出本申请实施例提供的控制策略的发送方法的一种流程示意图;
图5示出本申请实施例提供的PDU会话的控制方法的一种流程示意图;
图6示出本申请实施例提供的PDU会话的控制方法的另一种流程示意图;
图7示出本申请实施例中的一种策略更新方法的流程示意图;
图8示出本申请实施例中的另一种策略更新方法的流程示意图;
图9示出本申请实施例提供的允许的网络切片选择辅助信息的获取装置的一种结构示意图;
图10示出本申请实施例提供的允许的网络切片选择辅助信息的获取装置的另一种结构示意图;
图11示出本申请实施例提供的控制策略的获取装置的一种结构示意图;
图12示出本申请实施例提供的控制策略的发送装置的一种结构示意图;
图13示出本申请实施例提供的PDU会话的控制装置的一种结构示意图;
图14示出本申请实施例提供的一种通信设备的结构示意图;
图15示出本申请实施例提供的一种终端的硬件结构示意图;
图16示出本申请实施例提供的一种网络侧设备的硬件结构示意图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员所获得的所有其他实施例,都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象,而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换,以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施,且“第一”、“第二”所区别的对象通常为一类,并不限定对象的个数,例如第一对象可以是一个,也可以是多个。此外,说明书以及权利要求中“和/或”表示所连接对象的至少其中之一,字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是,本申请实施例所描述的技术不限于长期演进型(Long Term Evolution,LTE)/LTE的演进(LTE-Advanced,LTE-A)系统,还可用于其他无线通信系统,诸如码分多址(Code Division Multiple Access,CDMA)、时分多址(Time Division Multiple Access,TDMA)、频分多址(Frequency Division Multiple Access,FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access,OFDMA)、单载波频分多址(Single-carrier Frequency Division Multiple Access,SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用,所描述的技术既可用于以上提及的系统和无线电技术,也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(NewRadio,NR)系统,并且在以下大部分描述中使用NR术语,但是这些技术也可应用于NR系统应用以外的应用,如第6代(6thGeneration,6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中,终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant,PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer,UMPC)、移动上网装置(Mobile Internet Device,MID)、增强现实(augmented reality,AR)/虚拟现实(virtual reality,VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(Vehicle User Equipment,VUE)、行人终端(Pedestrian User Equipment,PUE)、智能家居(具有无线通信功能的家居设备,如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(personal computer,PC)、柜员机或者自助机等终端侧设备,可穿戴式设备包括:智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。需要说明的是,在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备和/或核心网设备,其中,接入网设备12也可以称为无线接入网设备、无线接入网(Radio Access Network,RAN)、无线接入网功能或无线接入网单元。接入网设备12可以包括基站、无线局域网 (Wireless Local Area Network,WLAN)接入点或无线保真(Wireless Fidelity,WiFi)节点等,基站可被称为节点B、演进节点B(eNB)、接入点、基收发机站(Base Transceiver Station,BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set,BSS)、扩展服务集(Extended Service Set,ESS)、家用B节点、家用演进型B节点、发送接收点(Transmitting Receiving Point,TRP)或所述领域中其他某个合适的术语,只要达到相同的技术效果,所述基站不限于特定技术词汇,需要说明的是,在本申请实施例中仅以NR系统中的基站为例进行介绍,并不限定基站的具体类型。核心网设备可以包含但不限于如下至少一项:核心网节点、核心网功能、移动管理实体(Mobility Management Entity,MME)、接入移动管理功能(Access and Mobility Management Function,AMF)、会话管理功能(Session Management Function,SMF)、用户平面功能(User Plane Function,UPF)、策略控制功能(Policy Control Function,PCF)、策略与计费规则功能单元(Policy and Charging Rules Function,PCRF)、边缘应用服务发现功能(Edge Application Server Discovery Function,EASDF)、统一数据管理(Unified Data Management,UDM),统一数据仓储(Unified Data Repository,UDR)、归属用户服务器(Home Subscriber Server,HSS)、集中式网络配置(Centralized network configuration,CNC)、网络存储功能(Network Repository Function,NRF),网络开放功能(Network Exposure Function,NEF)、本地NEF(Local NEF,或L-NEF)、绑定支持功能(Binding Support Function,BSF)、应用功能(Application Function,AF)等。其中,PCF可以包括接入管理PCF(Access Management PCF,AM-PCF)和会话管理PCF(Session Management PCF,SM-PCF)。需要说明的是,在本申请实施例中仅以NR系统中的核心网设备为例进行介绍,并不限定核心网设备的具体类型。
下面结合附图,通过一些实施例及其应用场景对本申请实施例提供的允许的网络切片选择辅助信息的获取方案进行详细地说明。
图2a示出本申请实施例中的允许的网络切片选择辅助信息的获取方法的一种流程示意图,该方法200a可以由终端执行。换言之,所述方法可以由安装在终端上的软件或硬件来执行。如图2a所示,该方法可以包括以下步骤。
S210,终端向第一网元发送第一注册请求,其中,所述第一注册请求中携带有所述终端请求的NSSAI。
在本申请实施例中,第一注册请求可以用于注册正常业务对应的网络切片,而暂不注册按需注册的网络切片。也就是说,在本申请实施例中,终端不需要在初始注册时区分签 约不同网络切片的业务需求即可实现仅注册正常业务对应的网络切片,而对于按需注册的网络切片(仅在有会话修的时候再发起注册和会话请求)暂不注册,且保证按需注册的网络切片不被拒绝,后续可以灵活的根据业务需求发起相应注册和会话请求。
在本申请实施例中,第一注册请求可以为终端请求接入网络的请求,例如,第一注册请求可以为附着请求(Attach Request)或注册到网络的注册请求(Registration Request)。
在本申请实施例中,第一网元可以包括AMF。
在一个可能的实现方式中,所述第一注册请求中还可以携带有指示支持终端行为的第一指示信息。例如,终端自身有省电、定制化接入的需求等,终端可以通过第一指示信息,指示终端的需求。
在S210中,第一注册请求中携带的请求的NSSAI是终端按照正常业务流程请求的,而无需终端识别哪些业务执行按需注册和会话的流程。例如,第一注册请求中携带的请求的NSSAI可以是当前公共陆地移动网络(Public Land Mobile Network,PLMN)内所配置的(Configured)NSSAI。
S212,所述终端接收所述第一网元发送的第一信息。
其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中不包括:按需注册的NSSAI,所述第一标识信息用于指示允许的按需注册的NSSAI。
其中,允许的NSSAI(Allowed NSSAI)用于指示UE可以在当前注册区域的服务PLMN中使用的S-NSSAIs值(Indicating the S-NSSAIs values the UE could use in the Serving PLMN in the current Registration Area)。
在第一注册请求为附着请求或注册到网络的注册请求时,第一网元在接收到终端的第一注册请求之后,可以执行正常注册流程,与鉴权服务功能(Authentication Server Function,AUSF)和UDM等进行交互,完成注册流程。并且,第一网元可以决定终端允许的(Allowed)NSSAI的值,对于按需注册的网络切片,在返回的允许的NSSAI中不加入此NSSAI,且返回的允许的NSSAI中也不存在拒绝的(Rejected NSSAI),另外,第一网元还可以返回第一标识,用于指示允许的按需注册的NSSAI,因此,该第一标识也可以称为按需允许的(On-demand Allowed)NSSAI标识。
在本申请实施例中,终端在发起注册时,只需携带终端请求的NSSAI,由网络侧识别终端允许的NSSAI以及终端允许的NSSAI中的按需注册的NSSAI,从而向终端返回允许的NSSAI和第一标识信息,返回的允许NSSAI中不包括按需注册的NSSAI,而是通过第一标识信息指示允许的按需注册的NSSAI,从而使得终端可以获知按需注册的NSSAI, 无需终端识别不同的网络切片业务类型和需求,降低了终端的负荷并且降低了对终端的要求。
在一个可能的实现方式中,在所述终端接收所述网络侧设备发送的第一信息之后,所述方法还可以包括以下步骤:
步骤1,所述终端基于用户设备路由选项策略(UE Route Selection Policy,URSP)规则,获取传输待传输业务的协议数据单元(Protocol Data Unit,PDU)会话对应的单一网络切片选择辅助信息(Single Network Slice Selection Assistance Information,S-NSSAI)。
例如,终端基于URSP规则匹配某个应用的流量后,获取匹配的流量描述符,该流量描述符中描述了PDU会话的一组属性(即传输待传输业务的PDU会话的属性),该组属性中一般包括S-NSSAI、数据网络名称(DNN)以及接入类型等信息。步骤1中的PDU会话对应的S-NSSAI即为基于URSP规则确定的PDU会话的属性中的S-NSSAI。
步骤2,确定所述PDU会话对应的S-NSSAI与所述第一标识信息指示的一个允许的按需注册的NSSAI匹配。
在该步骤中,终端发现所述PDU会话对应的S-NSSAI为允许的按需注册的NSSAI。
步骤3,所述终端发送第二注册请求,其中,所述第二注册请求用于请求注册到所述S-NSSAI对应的网络切片。
由于PDU会话对应的S-NSSAI为按需注册的NSSAI,因此,在建立PDU会话之前,终端发送第二注册请求,请求注册到该S-NSSAI对应的网络切片。
步骤4,在接收到注册成功响应之后,所述终端发送PDU会话建立请求,其中,所述PDU会话建立请求用于请求建立所述PDU会话。
针对多样化业务的需求,当终端同时签约并可以获取多个网络切片服务时,出于省电或差异化运维的需求,某些网络切片有可能要求终端在没有会话请求时也不需要注册在网络切片中,仅在有会话需求的时候再发起注册和PDU会话请求,通过上述可能的实现方式中,终端可以在需要建立按需注册的NSSAI对应的PDU会话时,才注册到该NSSAI,从而可以减少终端不必要的注册过程,满足省电或差异化运维的需求。
图2b示出本申请实施例提供的允许的网络切片选择辅助信息的获取方法的另一种流程示意图,如图2b所示,该方法200b主要包括以下步骤。
S220,第一网元接收终端发送的第一注册请求,其中,所述第一注册请求中携带有所述终端请求的NSSAI。
其中,第一注册请求与方法200中的第一注册请求相同,具体可以参见方法200中的 描述。
在本申请实施例中,第一网元可以包括AMF。
S222,所述第一网元基于第一目标信息,确定所述终端对应的至少一个允许的NSSAI。
在一个可能的实现方式中,所述第一目标信息包括但不限于以下至少之一:
(1)运营端策略;例如,运营端指定各个网络切片适用的终端类型等,可以确定终端对应的允许的NSSAI。
(2)所述终端的位置信息。不同的网络切片可能适用于不同的位置范围,因此,可以根据终端的位置信息,确定终端在当前位置对应的允许的NSSAI。
(3)所述终端的用户签约信息。例如,某些特殊的网络切片可以需要终端签约了某些特殊的业务才能使用,因此,根据终端的用户签约信息,可以获取与终端的用户签约信息对应的允许的NSSAI。
(4)网络切片的负载情况。为了均衡各个网络切片的负载,对于某些负载较高的网络切片,可以将其从终端的允许的NSSAI中排除。
通过上述可能的实现方式,
S224,所述第一网元向所述终端发送第一信息,其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中包括所述至少一个允许的NSSAI中除按需注册的NSSAI之外的NSSAI,所述第一标识信息用于指示所述至少一个允许的NSSAI中的按需注册的NSSAI。
在本申请实施例中,由第一网元决策终端对应的至少一个允许的NSSAI,并向终端返回除按需注册的NSSAI之外的NSSAI,并通过第一标识信息指示所述至少一个允许的NSSAI中的按需注册的NSSAI,从而使得终端不需要在初始注册时区分签约不同网络切片的业务需求即可实现仅注册正常业务对应的网络切片,而对于按需注册的网络切片(仅在有会话需求的时候再发起注册和会话请求)暂不注册,且保证按需注册的网络切片不被拒绝,后续可以灵活的根据业务需求发起相应注册和会话请求。
图3示出本申请实施例提供的控制策略获取方法的一种流程示意图,如图3所示,该方法300主要包括以下步骤。
S310,所述第一网元向第二网元发送第一请求,其中,所述第一请求用于对应终端的终端行为信息的网络控制策略,所述第一注册请求中携带有所述终端行为信息。
在本申请实施例中,第二网元可以包括PCF,或者,如果PCF包括AM-PCF和SM-PCF,则第二网元可以包括AM-PCF。
其中,所述终端行为信息可以包括终端的省电需求、定制化接入需求等中的一项或多项。
其中,第一网元可以在终端初始注册时,例如,在终端第一注册到网络切片成功后,向第二网元发送所述第一请求。例如,第一网元可以在接收到方法200a和200b中的第一注册请求后,在终端注册到网络成功后,发送所述第一请求。
S312,所述第一网元接收所述第二网元发送的至少一项网络控制策略,其中,所述网络控制策略中包括S-NSSAI与注册定时器的对应关系。
通过该可能的实现方式,第一网元可以从第二网元获取网络控制策略,从而使得第一网元可以根据网络控制策略对注册时长进行控制,以节约资源。
在一个可能的实现方式中,所述方法还可以包括以下步骤:
步骤1,所述第一网元执行所述终端注册到第一S-NSSAI对应的第一网络切片中的注册流程。
可选地,第一S-NSSAI可以为正常业务流程对应的NSSAI,例如,方法200a和方法200b中的第一信息中包含的允许的(Allowed)NSSAI,也可以为按需注册的(on-demand)的网络切片对应的NSSAI,例如,方法200a和方法200b中的第一信息包含的第一标识信息所标识的NSSAI。
在步骤1中,第一网元可以是在接收到所述终端发起的注册到第一S-NSSAI对应的第一网络切片的注册请求后,执行所述终端注册到第一S-NSSAI对应的第一网络切片中的注册流程。例如,终端在注册到网络成功后,基于URSP规则,获取传输待传输业务的PDU会话对应的第一S-NSSAI,根据所述第一标识信息,确定所述第一NSSAI为按需注册的NSSAI,则发送第二注册请求,所述第二注册请求用于请求注册到所述第一S-NSSAI对应的第一网络切片,第一网元在接收到第二注册请求后,执行所述终端注册到第一S-NSSAI对应的第一网络切片中的注册流程。当然,并不限于此,第一网元与可以在接收到终端请求注册到除按需注册的网络切片之外的第一网络切片的注册请求后,执行所述终端注册到第一S-NSSAI对应的第一网络切片中的注册流程。
其中,步骤1可以在S312之后执行,也可以是在S310之前执行,例如,所述终端注册到第一S-NSSAI对应的第一网络切片可能是终端第一次注册到网络切片,第一网元可以是在终端注册到第一网络切片成功后,执行S310。
步骤2,在所述终端注册到所述第一网络切片成功的情况下,所述第一网元根据所述至少一项网络控制策略,启动与所述第一S-NSSAI对应的第一注册定时器。
步骤3,在所述第一注册定时器超时前未接收到与所述第一S-NSSAI对应的第一PDU会话的PDU会话建立请求的情况下,所述第一网元执行所述终端在所述第一网络切片的解注册流程。通过所述解注册流程,可以解除所述终端在第一网络切片的注册,终端在第一网络切片再次处于未注册状态。
通过上述可能的实现方式中,第一网元根据所述至少一项网络控制策略,执行注册时长的监控,在终端注册到第一S-NSSAI对应的网络切片后,如果一定时间内未发起针对该S-NSSAI对应的第一PDU会话的建立流程,则触发终端在第一S-NSSAI对应的网络切片的解注册流程,解除终端在第一S-NSSAI对应的网络切片的注册,以节省资源。
在一个可能的实现方式中,所述网络控制策略中还可以包括S-NSSAI与会话定时器的对应关系。例如,在网络侧只部署一种类型的PCF的情况下,PCF可以决策S-NSSAI与注册定时器(Reg_Timer)的对应关系以及S-NSSAI与会话定时器(PDU_Timer)的对应关系,即PCF可以决策接入控制策略和会话控制策略。
在一个可能的实现方式中,在所述第一网元接收所述第二网元发送的至少一项网络控制策略之后,所述方法还可以包括以下步骤:
步骤1,所述第一网元接收所述终端发起的PDU会话建立请求,其中,所述PDU会话建立请求用于请求建立与对应第二S-NSSAI的第二PDU会话。
例如,在第二S-NSSAI对应的注册定时器到期前,第一网元接收到终端发起的PDU会话建立请求,该PDU会话建立请求用于请求建立与对应第二S-NSSAI的第二PDU会话。
步骤2,在确定所述第二PDU会话建立成功后,所述第一网元启动与所述第二S-NSSAI对应的第一会话定时器。
步骤3,在所述第一会话定时器超时的情况下,所述第一网元释放所述第二PDU会话,其中,在所述第二PDU会话对应的UPF连接为激活态或建立与所述第二PDU会话对应的新的UPF连接的情况下,所述第一会话定时器暂停,在所述第二PDU会话对应的UPF连接释放的情况下,所述第一会话定时器进行计时。
通过上述可能的实现方式,第一网元可以对会话时长进行控制,在第二S-NSSAI对应的第一会话定时器超时的情况下,释放第二PDU会话,节约PDU会话资源。
在一个可能的实现方式中,在所述第一网元接收所述第二网元发送的至少一项网络控制策略之后,所述方法还可以包括以下步骤:
步骤1,所述第一网元接收第三网元发送的会话释放消息,其中,所述会话释放消息 用于指示释放第二PDU会话。
其中,第三网元可以为SMF。
例如,在PCF包括AM-PCF和SM-PCF的情况下,AM-PCF向所述第一网元发送网络控制策略,SMF在接收到请求建立第二PDU会话的PDU会话建立请求后,向SM-PCF发送策略获取请求,从SM-PCF获取会话控制策略,在第二PDU会话建立请求后,SMF根据会话控制策略,确定释放第二PDU会话,则发起第二PDU会话的释放流程,向第一网元发送所述会话释放消息。
步骤2,所述第一网元释放所述第二PDU会话。所述第一网元基于所述会话释放消息,释放第二PDU会话。
在一个或多个可能的实现方式中,在释放所述第二PDU会话之后,所述方法还可以包括:所述第一网元启动与第二S-NSSAI对应的第二注册定时器,在所述第二注册定时器超时前未接收到与所述第二S-NSSAI对应的PDU会话建立请求的情况下,所述第一网元执行所述终端在所述第二S-NSSAI对应的第二网络切片的解注册流程,其中,所述第二S-NSSAI与所述第二PDU会话对应。在该可能的实现方式中,在释放了第二PDU会话之后,第一网元启动第二S-NSSAI对应的第二注册定时器,对终端注册到第二S-NSSAI的注册时长进行监控,如果在第二注册定时器超时前未接收到与所述第二S-NSSAI对应的PDU会话建立请求,则可以触发终端在第二网络切片的解注册流程,以节约资源。
在一个或多个可能的实现方式中,在所述第一网元接收所述第二网元发送的至少一项网络控制策略之后,所述方法还可以包括以下步骤:
步骤1,所述第一网元接收所述第二网元发送的更新后的所述至少一项网络控制策略;
步骤2,所述第一网元保存并使用更新后的所述至少一项网络控制策略。
通过上述可能的实现方式,第二网元可以对网络控制策略进行更新,并将更新后的网络控制策略发送第一网元使用,从而可以避免由于网络环境等因素变化而导致之前决策的网络控制策略不适用的情况,从而可以实现差异化业务策略的实现。
图4示出本申请实施例提供的控制策略的发送方法的一种流程示意图,如图4所示,该方法400主要包括以下步骤。
S410,第二网元接收第一网元发送的第一请求,其中,所述第一请求用于对应终端的终端行为信息的网络控制策略。
其中,第一网元可以按照方法300中所述发送所述第一请求。
在本申请实施例中,第二网元可以为PCF,例如,PCF可以包括AM-PCF和SM-PCF。
S412,所述第二网元根据第二目标信息,确定至少一项网络控制策略,其中,所述网络控制策略中包括S-NSSAI与注册定时器的对应关系。
在本申请实施例的一个可能实现方式中,所述第二目标信息包括以下至少一项:
(1)所述终端的用户签约信息;例如,用户可以预先签约,对于某类业务,在终端不执行该业务的传输超过多长时间后,可以将终端解注册。
(2)所述终端的位置信息;例如,对于终端注册的某些业务类型的网络切片,终端可能在某些位置不会长时间传输该业务,因此,可以在终端位于这些位置时,在终端不执行该业务的传输超过多长时间后,将终端解注册。
(3)AF的外部应用;其中,所述AF的外部应用可以包括AF外部对应的应用服务器及应用信息。例如,游戏服务器,游戏提供商在于运营商网络签约时会告知运营商接入策略,例如,为了满足游戏服务器的使用率,用户在不用游戏的时长超过多久后可以将用户解注册。
(4)网络切片的负载情况。例如,在网络切片的负载超过某一阈值时,为了使得其它终端可以获取到网络切片提供的业务,可以在用户多长时间未执行与该网络切片对应的业务传输后,将终端解注册。
S414,所述第二网元向所述第一网元发送所述至少一项网络控制策略。
在一个可能的实现方式中,所述网络控制策略中还包括S-NSSAI与会话定时器的对应关系。例如,在PCF不区分AM-PCF和SM-PCF,网络中只部署一种类型的PCF的情况下,第二网元可以在接收到第一请求后,同时向第一网元提供S-NSSAI对应的注册定时器和会话定时器。
在一个可能的实现方式中,在所述第二网元向所述第一网元发送所述至少一项网络控制策略之后,所述方法还可以包括以下步骤:
步骤1,所述第二网元确定更新所述至少一项网络控制策略;
步骤2,所述第二网元获取更新后的至少一项网络控制策略;
步骤3,所述第二网元将更新后的所述至少一项网络控制策略发送给所述第一网元。其中,所述网络控制策略包含按需网络切片的标识list(1个或多个S-NSSAI)以及对应的控制时长Reg_Timer。
其中,可选地,所述第二网元可以在以下至少一项的情况下确定更新所述至少一项网络控制策略:
(1)所述第二网元接收到外部AF的触发信息,所述触发信息用于指示更新所述至 少一项网络控制策略;例如,游戏商可以与运营商协商更新网络控制策略,例如,更新注册定时器和S-NSSAI的对应关系,即更新其中一个或多个S-NSSAI对应的控制时长。
(2)所述第二网元接收到UDR的通知,所述通知指示所述终端的签约信息发生改变。例如,对于某类业务,终端可能更新其签约信息。
(3)所述第二网元从NWDAF获取分析信息。其中,第二网元可以获取NWDAF通过评估计算当前以及历史网络运行状态得到的分析信息,基于该分析信息,确定需要更新网络控制策略。
通过上述可能的实现方式,第二网元可以对网络控制策略进行更新,从而可以根据不同的情况制定不同的网络控制策略。
在另一个可能的实现方式中,在所述第二网元向所述第一网元发送所述至少一项网络控制策略之后,所述方法还可以包括以下步骤:
步骤1,所述第二网元接收第三网元发送的第二请求,其中,所述第二请求用于对应所述终端行为信息的会话控制策略。
其中,第三网元可以为SMF。例如,在PCF包括AM-PCF和SM-PCF的情况下,AM-PCF向所述第一网元发送网络控制策略,而SMF在接收到请求建立第二PDU会话的PDU会话建立请求后,向SM-PCF发送第二请求,请求对应终端行为信息的会话控制策略。
步骤2,所述第二网元根据所述第二目标信息,确定至少一项会话控制策略,其中,所述会话控制策略中包括S-NSSAI与会话定时器的对应关系。
例如,第二网元可以基于所述终端的用户签约信息、所述终端的位置信息、AF的外部应用、以及网络切片的负载情况中的至少一项确定所述至少一项会话控制策略。
步骤3,所述第二网元向所述第三网元发送所述至少一项会话控制策略。
第二网元将至少一项会话控制策略发送给第三网元,由第三网元基于所述至少一项会话控制策略对终端的会话时长进行控制,
在一个可能的实现方式中,在所述第二网元向所述第三网元发送所述至少一项会话控制策略之后,所述方法还可以包括以下至少一项:
步骤1,所述第二网元确定更新所述至少一项会话控制策略;
步骤2,所述第二网元获取更新后的至少一项会话控制策略;
步骤3,所述第二网元将更新后的所述至少一项会话控制策略发送给所述第三网元。其中,所述会话控制策略包含按需网络切片的标识list(1个或多个S-NSSAI)以及对应 的会话控制时长PDU_Timer。
可选地,所述第二网元可以在以下至少一项的情况下确定更新所述至少一项会话控制策略:
(1)所述第二网元接收到外部AF的触发信息,所述触发信息用于指示更新所述至少一项会话控制策略;
(2)所述第二网元接收到统一数据仓储UDR的通知,所述通知指示所述终端的签约信息发生改变;
(3)所述第二网元从网络数据分析功能NWDAF获取分析信息。
通过上述可能的实现方式,第二网元可以对会话控制策略进行更新,从而可以根据不同的情况制定不同的会话控制策略。
图5示出本申请实施例提供的PDU会话的控制方法的一种流程示意图,如图5所示,该方法500主要包括以下步骤。
S510,第三网元接收终端发送的PDU会话建立请求,所述PDU会话建立请求用于请求建立第二PDU会话。
例如,终端可以发起PDU会话建立请求,该PDU会话建立请求中可以携带终端行为信息,例如,终端的省电需求、终端的定制化接入需求等,在完成会话SMF选择后,第三网元(例如,SMF)接收到终端发送的PDU会话建立请求。
S512,所述第三网元向第二网元发送第二请求,其中,所述第二请求用于对应所述终端的终端行为信息的会话控制策略。
例如,第三网元可以在策略流程中,向第二网元发送所述第二请求。
S514,所述第三网元接收所述第二网元发送的至少一项会话控制策略,其中,所述会话控制策略中包括S-NSSAI与会话定时器的对应关系。
其中,第二网元可以按照上述方法400中所述的方式获取并发送所述至少一项会话控制策略,具体可以参见方法400中的相关描述,在此不再赘述。
S516,在确定所述第二PDU会话建立之后,所述第三网元启动与第二S-NSSAI对应的第一会话定时器,所述第二S-NSSAI为与所述第二PDU会话对应的S-NSSAI。
S518,在所述第一会话定时器超时的情况下,所述第三网元释放所述第二PDU会话,其中,在所述第二PDU会话对应的UPF连接为激活态或建立与所述第二PDU会话对应的新的UPF连接的情况下,所述第一会话定时器暂停,在所述第二PDU会话对应的UPF连接释放的情况下,所述第一会话定时器进行计时。
通过本申请实施例提供的上述方法,第三网元可以基于会话控制策略,对PDU会话的时长进行控制,以节约资源。
在一个可能的实现方式中,在所述第三网元释放所述第二PDU会话之后,所述方法还包括:所述第三网元向第一网元发送会话释放消息,其中,所述会话释放消息用于指示释放第二PDU会话。通过该可能的实现方式,在第三网元释放第二PDU会话后,通知第一网元,从而使得第一网元可以获知第二PDU会话被释放,启动第二PDU会话对应的第二S-NSSAI的注册定时器,如果终端在第二S-NSSAI的注册定时器超时前,未接收到终端发起对应第二S-NSSAI的PDU会话的建立请求,则触发终端在第二S-NSSAI对应的网络切片的解注册流程。
图6示出本申请实施例提供的PDU会话的控制方法的另一种流程示意图,如图6所示,该方法主要包括以下步骤:
步骤601,UE发起注册请求。
可选地,如果UE自身有例如省电、定制化接入的需求,可以要求网络提供UE行为(UE Behavior)策略的请求信息给AMF。
其中,此处UE发起的Request NSSAI是按照正常业务流程请求,并不需要识别哪些业务需要做按需注册和会话流程。
其中,如果UE不携带UE行为信息,则是否分发对应的策略完全由网络进行判断,例如根据PLMN、签约、网络负载、业务特性等。
步骤602:AMF执行正常注册流程、与AUSF和UDM的交互注册流程。若需要执行网络切片重选,需要与NSSF等交互。在此处,AMF根据运营商策略、终端当前位置信息、用户签约、当前网络切片负载等情况决策Allowed NSSAI的值,对于按需注册的网络切片,在返回的Allowed NSSAI中不加入此NSSAI,但同样其不存在于Rejected NSSAI中,另外新增一个On-demand Allowed NSSAI标识最终传递给终端。
终端后续有业务请求PDU会话连接的需求时,与URSP匹配,当匹配的PDU会话对应的S-NSSAI与On-demand Allowed NSSAI一致时,终端先发起注册然后发起PDU Session request。对于正常的Allowed NSSAI执行正常流程,这种情况下的首先UE不用增强过多的操作来执行对应的注册请求区分,降低UE的负载,另外对于网络策略的修改更加灵活,可以多方面集中考虑多种因素例如负荷(load)、跟踪区域(Tracking Area,TA)信息、外部策略等。
步骤603-605:AMF向PCF/AM-PCF发起Npcf_AMPlicyControl_Create Request,请 求对应UE Behavior支持的响应策略,PCF根据终端的签约、AF外部应用、终端当前位置、网络当前负载等情况的一项或多项定制网络控制策略,返回的注册管理timer(Reg_Timer)及对应的S-NSSAI,供AMF对响应的S-NSSAI执行接入控制。
步骤606,其余注册流程完成。
步骤607,AMF收到Reg_Timer后,监控当前对应S-NSSAI的注册情况。若AMF持续未收到终端对S-NSSAI的PDU Session Establishment Request请求,Reg_timer到期后,AMF触发此终端的解注册操作。
其中,当Reg_Timer没有过期,可选地,可以在首次终端注册时同时由AMF同时接受两种不同类型的timer,这种情况时PCF不区分AM-PCF和SM-PCF,网络中只部署一种类型的PCF,然后执行对应的操作,PDU_Timer可以在注册的同时发给AMF,AMF也可以触发PDU Session Release,这种情况下,可以跳过步骤608-613。
步骤608,终端发起PDU会话建立请求(PDU Session Establishment Request),并携带UE Behavior的支持请求。
步骤609,完成会话SMF选择和PDU Session认证和鉴权
步骤610-612,在策略(Policy)流程中,SMF选择PCF,并向选择的PCF发起Npcf_SMPlicyControl_Create Request,请求对应UE Behavior支持的响应策略,PCF根据终端的签约、AF外部应用、终端当前位置、网络当前负载等情况的一项或多项等定制会话控制策略,包括PDU_timer及对应的S-NSSAI,并返回至SMF,供SMF对响应的S-NSSAI执行接入控制。
步骤613,其余的PDU会话建立流程。
步骤614,SMF启动接收到的PDU_Timer,监控当前的PDU会话状态。
步骤615,当前UPF连接是激活的或有新的upf连接,则PDU_timer不工作,UPF连接释放,PDU_Timer开始计时。若PDU_Timer到期,则由SMF触发PDU会话释放(PDU Session Release)的相关操作。
步骤616,SMF发送PDU连接释放的消息给AMF,触发AMF启动对应的Reg_Timer,如果Reg_Timer到期且没有新的PDU会话请求,则AMF触发终端解注册的流程。
图7示出本申请实施例中的一种策略更新方法的流程示意图,如图7所示,该方法主要包括以下步骤:
步骤701:AM-PCF在制定并发送控制策略(例如,上述的网络控制策略)之后,决策进行控制策略更新,更新的信息有可能由以下的(包含但不限于)一种或者几种情况触 发a)由外部AF触发b)UDR通知c)从NWDAF中获取到的分析信息。
步骤702,AM-PCF制定策略。
步骤703,AM-PCF在Npcf_AMPolicyControl_UpdateNotify下发给AMF对应的RPRM策略,在此方案中,控制策略包含按需网络切片的标识list(1个或多个S-NSSAI)以及对应的控制时长Reg_Timer。
步骤704:AMF部署和保存收到的策略。
图8示出本申请实施例中的另一种策略更新方法的流程示意图,如图8所示,该方法主要包括以下步骤:
步骤801:SM-PCF在制定并发送控制策略(例如,上述的会话控制策略)之后,SM-PCF决策进行策略更新,更新的信息有可能由以下的(包含但不限于)一种或者几种情况触发a)由外部AF触发b)UDR通知c)从NWDAF中获取到的分析信息。
步骤802:SM-PCF制定策略。
步骤803:PCF在Npcf_SMPolicyControl_UpdateNotify下发给SMF对应的策略,在此方案中,策略包含按需网络切片的标识list(1个或多个S-NSSAI)以及对应的控制时长PDU_Timer。
步骤804:SMF部署和保存收到的策略。
本申请实施例提供上述方法,执行主体可以为虚拟装置。本申请实施例中以虚拟装置执行上述方法为例,说明本申请实施例提供的各个装置。
图9示出本申请实施例提供的允许的网络切片选择辅助信息的获取装置的一种结构示意图,如图9所示,该装置主要包括:第一发送模块901和第一接收模块902。
在本申请实施例中,第一发送模块901,用于向第一网元发送第一注册请求,其中,所述第一注册请求中携带有终端请求的NSSAI;第一接收模块902,用于接收所述第一网元发送的第一信息;其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中不包括:按需注册的NSSAI,所述第一标识信息用于指示允许的按需注册的NSSAI。
在一个可能的实现方式中,如图9所示,所述装置还可以包括:第一获取模块903和第一确定模块904;其中,所述第一获取模块903,用于基于URSP规则,获取传输待传输业务的PDU会话对应的S-NSSAI;所述第一确定模块904,用于确定所述PDU会话对应的S-NSSAI与所述第一标识信息指示的一个允许的按需注册的NSSAI匹配;所述第一发送模块901,还用于发送第二注册请求,其中,所述第二注册请求用于请求注册到所 述S-NSSAI标识对应的网络切片;所述第一接收模块,还用于接收到注册成功响应;所述第一发送模块901,还用于发送PDU会话建立请求,其中,所述PDU会话建立请求用于请求建立所述PDU会话。
在一个可能的实现方式中,所述第一注册请求中还携带有指示支持终端行为的第一指示信息。
本申请实施例中的允许的网络切片选择辅助信息的获取装置可以是电子设备,例如具有操作系统的电子设备,也可以是电子设备中的部件,例如集成电路或芯片。该电子设备可以是终端,也可以为除终端之外的其他设备。示例性的,终端可以包括但不限于上述所列举的终端11的类型,其他设备可以为服务器、网络附属存储器(Network Attached Storage,NAS)等,本申请实施例不作具体限定。
本申请实施例提供的允许的网络切片选择辅助信息的获取装置能够实现图2a的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
图10示出本申请实施例提供的允许的网络切片选择辅助信息的获取装置的另一种结构示意图,如图10所示,该装置1000主要包括第二接收模块1001、第二确定模块1002和第二发送模块1003。
在本申请实施例中,第二接收模块1001,用于接收终端发送的第一注册请求,其中,所述第一注册请求中携带有所述终端请求的NSSAI;第二确定模块1002,用于基于第一目标信息,确定所述终端对应的至少一个允许的NSSAI;第二发送模块1003,用于向所述终端发送第一信息,其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中包括所述至少一个允许的NSSAI中除按需注册的网络切片对应的NSSAI之外的NSSAI,所述第一标识信息用于指示所述至少一个允许的NSSAI中的按需注册的NSSAI。
在一个可能的实现方式中,所述第一目标信息包括以下至少之一:
运营端策略;
所述终端的位置信息;
所述终端的用户签约信息;
网络切片的负载情况。
本申请实施例提供的允许的网络切片选择辅助信息的获取装置能够实现图2b的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
图11示出本申请实施例提供的控制策略的获取装置的一种结构示意图,如图11所示, 该装置1100主要包括:第三发送模块1101和第三接收模块1102。
在本申请实施例中,第三发送模块1101,用于向第二网元发送第一请求,其中,所述第一请求用于对应终端的终端行为信息的网络控制策略,所述第一请求中携带有所述终端行为信息;第三接收模块1102,用于接收所述第二网元发送的至少一项网络控制策略,其中,所述网络控制策略中包括S-NSSAI与注册定时器的对应关系。
在一个可能的实现方式中,如图11所示,该装置还可以包括:第一控制模块1103,用于:
执行所述终端注册到第一NSSAI对应的第一网络切片中的注册流程;
在所述终端注册到所述第一网络切片成功的情况下,根据所述至少一项网络控制策略,启动与所述第一S-NSSAI对应的第一注册定时器;
在所述第一注册定时器超时前未接收到与所述第一S-NSSAI对应的第一PDU会话的PDU会话建立请求的情况下,执行所述终端在所述第一网络切片的解注册流程。
在一个可能的实现方式中,所述网络控制策略中还包括S-NSSAI与会话定时器的对应关系;所述第三接收模块1102,还用于接收所述终端发起的PDU会话建立请求,其中,所述PDU会话建立请求用于请求建立与对应第二S-NSSAI的第二PDU会话;所述第一控制模块1103,还用于在确定所述第二PDU会话建立成功后,启动与所述第二S-NSSAI对应的第一会话定时器;在所述第一会话定时器超时的情况下,释放所述第二PDU会话,其中,在所述第二PDU会话对应的UPF连接为激活态或建立与所述第二PDU会话对应的新的UPF连接的情况下,所述第一会话定时器暂停,在所述第二PDU会话对应的UPF连接释放的情况下,所述第一会话定时器进行计时。
在一个可能的实现方式中,所述第三接收模块1102,还用于在接收所述第二网元返回的至少一项网络控制策略之后,接收第三网元发送的会话释放消息,其中,所述会话释放消息用于指示释放第二PDU会话;所述第一控制模块1103,还用于释放所述第二PDU会话。
在一个可能的实现方式中,所述第一控制模块1103,还用于在释放所述第二PDU会话之后,启动与第二S-NSSAI对应的第二注册定时器,在所述第二注册定时器超时前未接收到与所述第二S-NSSAI对应的PDU会话建立请求的情况下,执行所述终端在所述第二S-NSSAI对应的第二网络切片的解注册流程,其中,所述第二S-NSSAI与所述第二PDU会话对应。
在一个可能的实现方式中,所述第三接收模块1102,还用于接收所述第二网元发送 的更新后的所述至少一项网络控制策略。
本申请实施例提供的控制策略的获取装置能够实现图3的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
图12示出本申请实施例提供的控制策略的发送装置的一种结构示意图,如图12所示,该装置1200主要包括:第四接收模块1201、第三确定模块1202和第四发送模块1203。
在本申请实施例中,第四接收模块1201,用于接收第一网元发送的第一请求,其中,所述第一请求用于对应终端的终端行为信息的网络控制策略;第三确定模块1202,用于根据第二目标信息,确定至少一项网络控制策略,其中,所述网络控制策略中包括S-NSSAI与注册定时器的对应关系;第四发送模块1203,用于向所述第一网元发送所述至少一项网络控制策略。
在一个可能的实现方式中,所述第四接收模块1201,还用于接收第三网元发送的第二请求,其中,所述第二请求用于对应所述终端行为信息的会话控制策略;所述第三确定模块1202,还用于根据所述第二目标信息,确定至少一项会话控制策略,其中,所述会话控制策略中包括单NSSAI与会话定时器的对应关系;所述第四发送模块1203,还用于向所述第三网元发送所述至少一项会话控制策略。
在一个可能的实现方式中,所述第三确定模块1202,还用于确定更新所述至少一项会话控制策略,并获取更新后的至少一项会话控制策略;所述第四发送模块1203,还用于将更新后的所述至少一项会话控制策略发送给所述第三网元。
在一个可能的实现方式中,所述第三确定模块1202在以下至少一项的情况下确定更新所述至少一项会话控制策略:
接收到外部AF的触发信息,所述触发信息用于指示更新所述至少一项会话控制策略;
接收到UDR的通知,所述通知指示所述终端的签约信息发生改变;
从网络数据分析功能NWDAF获取分析信息。
在一个可能的实现方式中,所述第三确定模块1202,还用于确定更新所述至少一项网络控制策略,并获取更新后的至少一项网络控制策略;所述第四发送模块1203,还用于将更新后的所述至少一项会话控制策略发送给所述第一网元。
在一个可能的实现方式中,所述第三确定模块1202在以下至少一项的情况下确定更新所述至少一项网络控制策略:
接收到外部AF的触发信息,所述触发信息用于指示更新所述至少一项网络控制策略;
接收到UDR的通知,所述通知指示所述终端的签约信息发生改变;
从NWDAF获取分析信息。
本申请实施例提供的控制策略的发送装置能够实现图4的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
图13示出本申请实施例提供的PDU会话的控制装置的一种结构示意图,如图13所示,该装置1300主要包括:第五接收模块1301、第五发送模块1302和第二控制模块1303。
在本申请实施例中,第五接收模块1301,用于接收终端发送的PDU会话建立请求,所述PDU会话建立请求用于请求建立第二PDU会话;第五发送模块1302,用于向第二网元发送第二请求,其中,所述第二请求用于对应所述终端的终端行为信息的会话控制策略;所述第五接收模块1301,还用于接收所述第二网元发送的至少一项会话控制策略,其中,所述会话控制策略中包括S-NSSAI与会话定时器的对应关系;第二控制模块1303,用于:在确定所述第二PDU会话建立之后,启动与第二S-NSSAI对应的第一会话定时器,所述第二S-NSSAI为与所述第二PDU会话对应的S-NSSAI;在所述第一会话定时器超时的情况下,释放所述第二PDU会话,其中,在所述第二PDU会话对应的用户面功能UPF连接为激活态或建立与所述第二PDU会话对应的新的UPF连接的情况下,所述第一会话定时器暂停,在所述第二PDU会话对应的UPF连接释放的情况下,所述第一会话定时器进行计时。
在一个可能的实现方式中,所述第五发送模块1302,还用于向第一网元发送会话释放消息,其中,所述会话释放消息用于指示释放第二PDU会话。
本申请实施例提供的PDU会话的控制装置能够实现图5的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
可选的,如图14所示,本申请实施例还提供一种通信设备1400,包括处理器1401和存储器1402,存储器1402上存储有可在所述处理器1401上运行的程序或指令,例如,该通信设备1400为终端时,该程序或指令被处理器1401执行时实现上述允许的网络切片选择辅助信息的获取方法200a实施例的各个步骤,且能达到相同的技术效果。该通信设备1400为网络侧设备时,该程序或指令被处理器1401执行时实现上述允许的网络切片选择辅助信息的获取方法200b实施例的各个步骤,或者实现上述控制策略的获取方法300实施例的各个步骤,或者实现上述控制策略的发送方法400实施例的各个步骤,或者实现上述PDU会话的控制方法500实施例的各个步骤,且能达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例还提供一种终端,包括处理器和通信接口,处理器用于实现上述允许的 网络切片选择辅助信息的获取方法200b实施例的各个步骤,通信接口用于与外部设备通信。该终端实施例与上述终端侧方法实施例对应,上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中,且能达到相同的技术效果。具体地,图15为实现本申请实施例的一种终端的硬件结构示意图。
该终端1500包括但不限于:射频单元1501、网络模块1502、音频输出单元1503、输入单元1504、传感器1505、显示单元1506、用户输入单元1507、接口单元1508、存储器1509以及处理器1510等中的至少部分部件。
本领域技术人员可以理解,终端1500还可以包括给各个部件供电的电源(比如电池),电源可以通过电源管理系统与处理器1510逻辑相连,从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图15中示出的终端结构并不构成对终端的限定,终端可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置,在此不再赘述。
应理解的是,本申请实施例中,输入单元1504可以包括图形处理器(Graphics Processing Unit,GPU)15041和麦克风15042,图形处理器15041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1506可包括显示面板15061,可以采用液晶显示器、有机发光二极管等形式来配置显示面板15061。用户输入单元1507包括触控面板15071以及其他输入设备15072中的至少一种。触控面板15071,也称为触摸屏。触控面板15071可包括触摸检测装置和触摸控制器两个部分。其他输入设备15072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆,在此不再赘述。
本申请实施例中,射频单元1501接收来自网络侧设备的下行数据后,可以传输给处理器1510进行处理;另外,射频单元1501可以向网络侧设备发送上行数据。通常,射频单元1501包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器1509可用于存储软件程序或指令以及各种数据。存储器1509可主要包括存储程序或指令的第一存储区和存储数据的第二存储区,其中,第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外,存储器1509可以包括易失性存储器或非易失性存储器,或者,存储器1509可以包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(Read-Only Memory,ROM)、可编程只读存储器(Programmable ROM,PROM)、可擦除可编程只读存储器(Erasable PROM,EPROM)、电可擦除可编程只读存储器(Electrically EPROM,EEPROM) 或闪存。易失性存储器可以是随机存取存储器(Random Access Memory,RAM),静态随机存取存储器(Static RAM,SRAM)、动态随机存取存储器(Dynamic RAM,DRAM)、同步动态随机存取存储器(Synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM,DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM,DRRAM)。本申请实施例中的存储器1509包括但不限于这些和任意其它适合类型的存储器。
处理器1510可包括一个或多个处理单元;可选的,处理器1510集成应用处理器和调制解调处理器,其中,应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作,调制解调处理器主要处理无线通信信号,如基带处理器。可以理解的是,上述调制解调处理器也可以不集成到处理器1510中。
其中,射频单元150,用于向第一网元发送第一注册请求,其中,所述第一注册请求中携带有终端请求的NSSAI;接收所述第一网元发送的第一信息;其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中不包括:按需注册的NSSAI,所述第一标识信息用于指示允许的按需注册的NSSAI。
本申请实施例还提供一种网络侧设备,包括处理器和通信接口,处理器用于实现上述允许的网络切片选择辅助信息的获取方法200b实施例的各个步骤,或者实现上述控制策略的获取方法300实施例的各个步骤,或者实现上述控制策略的发送方法400实施例的各个步骤,或者实现上述PDU会话的控制方法500实施例的各个步骤,通信接口用于与外部设备进行通信。该网络侧设备实施例与上述网络侧设备方法实施例对应,上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中,且能达到相同的技术效果。
具体地,本申请实施例还提供了一种网络侧设备。如图16所示,该网络侧设备1600包括:处理器1601、网络接口1602和存储器1603。其中,网络接口1602例如为通用公共无线接口(common public radio interface,CPRI)。
具体地,本发明实施例的网络侧设备1600还包括:存储在存储器1603上并可在处理器1601上运行的指令或程序,处理器1601调用存储器1603中的指令或程序执行图10至13所示各模块执行的方法,并达到相同的技术效果,为避免重复,故不在此赘述。
本申请实施例还提供一种可读存储介质,所述可读存储介质上存储有程序或指令,该程序或指令被处理器执行时实现上述允许的网络切片选择辅助信息的获取方法200a实施 例的各个过程,或者实现上述允许的网络切片选择辅助信息的获取方法200b实施例的各个过程,或者实现上述控制策略的获取方法300实施例的各个过程,或者实现上述控制策略的发送方法400实施例的各个过程,或者实现上述PDU会话的控制方法500实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
其中,所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质,包括计算机可读存储介质,如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。
本申请实施例另提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,上述允许的网络切片选择辅助信息的获取方法200a实施例的各个过程,或者实现上述允许的网络切片选择辅助信息的获取方法200b实施例的各个过程,或者实现上述控制策略的获取方法300实施例的各个过程,或者实现上述控制策略的发送方法400实施例的各个过程,或者实现上述PDU会话的控制方法500实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
应理解,本申请实施例提到的芯片还可以称为系统级芯片,系统芯片,芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品,所述计算机程序/程序产品被存储在存储介质中,所述计算机程序/程序产品被至少一个处理器执行以实现上述允许的网络切片选择辅助信息的获取方法200a实施例的各个过程,或者实现上述允许的网络切片选择辅助信息的获取方法200b实施例的各个过程,或者实现上述控制策略的获取方法300实施例的各个过程,或者实现上述控制策略的发送方法400实施例的各个过程,或者实现上述PDU会话的控制方法500实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例还提供了一种允许的网络切片选择辅助信息的获取系统,包括:终端及网络侧设备,所述终端可用于执行如上所述的允许的网络切片选择辅助信息的获取方法200a实施例的各个过程,所述网络侧设备可用于执行如上所述的允许的网络切片选择辅助信息的获取方法200b实施例的各个过程,或者执行上述控制策略的获取方法300实施例的各个过程,或者执行上述控制策略的发送方法400实施例的各个过程,或者执行上述PDU会话的控制方法500实施例的各个过。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素, 而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外,需要指出的是,本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能,还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能,例如,可以按不同于所描述的次序来执行所描述的方法,并且还可以添加、省去、或组合各种步骤。另外,参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端(可以是手机,计算机,服务器,空调器,或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述,但是本申请并不局限于上述的具体实施方式,上述的具体实施方式仅仅是示意性的,而不是限制性的,本领域的普通技术人员在本申请的启示下,在不脱离本申请宗旨和权利要求所保护的范围情况下,还可做出很多形式,均属于本申请的保护之内。

Claims (40)

  1. 一种允许的网络切片选择辅助信息的获取方法,包括:
    终端向第一网元发送第一注册请求,其中,所述第一注册请求中携带有所述终端请求的网络切片选择辅助信息NSSAI;
    所述终端接收所述第一网元发送的第一信息;
    其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中不包括:按需注册的NSSAI,所述第一标识信息用于指示允许的按需注册的NSSAI。
  2. 根据权利要求1所述的方法,其中,在所述终端接收所述网络侧设备发送的第一信息之后,所述方法还包括:
    所述终端基于用户设备路由选项策略URSP规则,获取传输待传输业务的协议数据单元PDU会话对应的单一网络切片选择辅助信息S-NSSAI;
    确定所述PDU会话对应的S-NSSAI与所述第一标识信息指示的一个允许的按需注册的NSSAI匹配;
    所述终端发送第二注册请求,其中,所述第二注册请求用于请求注册到所述S-NSSAI对应的网络切片;
    在接收到注册成功响应之后,所述终端发送PDU会话建立请求,其中,所述PDU会话建立请求用于请求建立所述PDU会话。
  3. 根据权利要求1或2所述的方法,其中,所述第一注册请求中还携带有指示支持终端行为的第一指示信息。
  4. 一种允许的网络切片选择辅助信息的获取方法,包括:
    第一网元接收终端发送的第一注册请求,其中,所述第一注册请求中携带有所述终端请求的NSSAI;
    所述第一网元基于第一目标信息,确定所述终端对应的至少一个允许的NSSAI;
    所述第一网元向所述终端发送第一信息,其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中包括所述至少一个允许的NSSAI中除按需注册的NSSAI之外的NSSAI,所述第一标识信息用于指示所述至少一个允许的NSSAI中的按需注册的NSSAI。
  5. 根据权利要求4所述的方法,其中,所述第一目标信息包括以下至少之一:
    运营端策略;
    所述终端的位置信息;
    所述终端的用户签约信息;
    网络切片的负载情况。
  6. 一种控制策略的获取方法,包括:
    第一网元向第二网元发送第一请求,其中,所述第一请求用于对应终端的终端行为信息的网络控制策略,所述第一请求中携带有所述终端行为信息;
    所述第一网元接收所述第二网元发送的至少一项网络控制策略,其中,所述网络控制策略中包括S-NSSAI与注册定时器的对应关系。
  7. 根据权利要求6所述的方法,其中,所述方法还包括:
    所述第一网元执行所述终端注册到第一S-NSSAI对应的第一网络切片中的注册流程;
    在所述终端注册到所述第一网络切片成功的情况下,所述第一网元根据所述至少一项网络控制策略,启动与所述第一S-NSSAI对应的第一注册定时器;
    在所述第一注册定时器超时前未接收到与所述第一S-NSSAI对应的第一PDU会话的PDU会话建立请求的情况下,所述第一网元执行所述终端在所述第一网络切片的解注册流程。
  8. 根据权利要求6所述的方法,其中,所述网络控制策略中还包括S-NSSAI与会话定时器的对应关系。
  9. 根据权利要求8所述的方法,其中,在所述第一网元接收所述第二网元发送的至少一项网络控制策略之后,所述方法还包括:
    所述第一网元接收所述终端发起的PDU会话建立请求,其中,所述PDU会话建立请求用于请求建立与对应第二S-NSSAI的第二PDU会话;
    在确定所述第二PDU会话建立成功后,所述第一网元启动与所述第二S-NSSAI对应的第一会话定时器;
    在所述第一会话定时器超时的情况下,所述第一网元释放所述第二PDU会话,其中,在所述第二PDU会话对应的用户面功能UPF连接为激活态或建立与所述第二PDU会话对应的新的UPF连接的情况下,所述第一会话定时器暂停,在所述第二PDU会话对应的UPF连接释放的情况下,所述第一会话定时器进行计时。
  10. 根据权利要求6所述的方法,其中,在所述第一网元接收所述第二网元发送的至少一项网络控制策略之后,所述方法还包括:
    所述第一网元接收第三网元发送的会话释放消息,其中,所述会话释放消息用于指示 释放第二PDU会话;
    所述第一网元释放所述第二PDU会话。
  11. 根据权利要求9或10所述的方法,其中,在释放所述第二PDU会话之后,所述方法还包括:
    所述第一网元启动与第二S-NSSAI对应的第二注册定时器,在所述第二注册定时器超时前未接收到与所述第二S-NSSAI对应的PDU会话建立请求的情况下,所述第一网元执行所述终端在所述第二S-NSSAI对应的第二网络切片的解注册流程,其中,所述第二S-NSSAI与所述第二PDU会话对应。
  12. 根据权利要求6至11任一项所述的方法,其中,在所述第一网元接收所述第二网元发送的至少一项网络控制策略之后,所述方法还包括:
    所述第一网元接收所述第二网元发送的更新后的所述至少一项网络控制策略;
    所述第一网元保存并使用更新后的所述至少一项网络控制策略。
  13. 一种控制策略的发送方法,包括:
    第二网元接收第一网元发送的第一请求,其中,所述第一请求用于对应终端的终端行为信息的网络控制策略;
    所述第二网元根据第二目标信息,确定至少一项网络控制策略,其中,所述网络控制策略中包括S-NSSAI与注册定时器的对应关系;
    所述第二网元向所述第一网元发送所述至少一项网络控制策略。
  14. 根据权利要求13所述的方法,其中,所述第二目标信息包括以下至少一项:
    所述终端的用户签约信息;
    所述终端的位置信息;
    应用功能AF的外部应用;
    网络切片的负载情况。
  15. 根据权利要求13所述的方法,其中,所述网络控制策略中还包括S-NSSAI与会话定时器的对应关系。
  16. 根据权利要求13所述的方法,其中,在所述第二网元向所述第一网元发送所述至少一项网络控制策略之后,所述方法还包括:
    所述第二网元接收第三网元发送的第二请求,其中,所述第二请求用于对应所述终端行为信息的会话控制策略;
    所述第二网元根据所述第二目标信息,确定至少一项会话控制策略,其中,所述会话 控制策略中包括S-NSSAI与会话定时器的对应关系;
    所述第二网元向所述第三网元发送所述至少一项会话控制策略。
  17. 根据权利要求16所述的方法,其中,在所述第二网元向所述第三网元发送所述至少一项会话控制策略之后,所述方法还包括:
    所述第二网元确定更新所述至少一项会话控制策略;
    所述第二网元获取更新后的至少一项会话控制策略;
    所述第二网元将更新后的所述至少一项会话控制策略发送给所述第三网元。
  18. 根据权利要求17所述的方法,其中,所述第二网元在以下至少一项的情况下确定更新所述至少一项会话控制策略:
    所述第二网元接收到外部AF的触发信息,所述触发信息用于指示更新所述至少一项会话控制策略;
    所述第二网元接收到统一数据仓储UDR的通知,所述通知指示所述终端的签约信息发生改变;
    所述第二网元从网络数据分析功能NWDAF获取分析信息。
  19. 根据权利要求13至17中任一项所述的方法,其中,在所述第二网元向所述第一网元发送所述至少一项网络控制策略之后,所述方法还包括:
    所述第二网元确定更新所述至少一项网络控制策略;
    所述第二网元获取更新后的至少一项网络控制策略;
    所述第二网元将更新后的所述至少一项网络控制策略发送给所述第一网元。
  20. 根据权利要求19所述的方法,其中,所述第二网元在以下至少一项的情况下确定更新所述至少一项网络控制策略:
    所述第二网元接收到外部AF的触发信息,所述触发信息用于指示更新所述至少一项网络控制策略;
    所述第二网元接收到UDR的通知,所述通知指示所述终端的签约信息发生改变;
    所述第二网元从NWDAF获取分析信息。
  21. 一种PDU会话的控制方法,包括:
    第三网元接收终端发送的PDU会话建立请求,所述PDU会话建立请求用于请求建立第二PDU会话;
    所述第三网元向第二网元发送第二请求,其中,所述第二请求用于对应所述终端的终端行为信息的会话控制策略;
    所述第三网元接收所述第二网元发送的至少一项会话控制策略,其中,所述会话控制策略中包括S-NSSAI与会话定时器的对应关系;
    在确定所述第二PDU会话建立之后,所述第三网元启动与第二S-NSSAI对应的第一会话定时器,所述第二S-NSSAI为与所述第二PDU会话对应的S-NSSAI;
    在所述第一会话定时器超时的情况下,所述第三网元释放所述第二PDU会话,其中,在所述第二PDU会话对应的用户面功能UPF连接为激活态或建立与所述第二PDU会话对应的新的UPF连接的情况下,所述第一会话定时器暂停,在所述第二PDU会话对应的UPF连接释放的情况下,所述第一会话定时器进行计时。
  22. 根据权利要求21所述的方法,其中,在所述第三网元释放所述第二PDU会话之后,所述方法还包括:
    所述第三网元向第一网元发送会话释放消息,其中,所述会话释放消息用于指示释放第二PDU会话。
  23. 一种允许的网络切片选择辅助信息的获取装置,包括:
    第一发送模块,用于向第一网元发送第一注册请求,其中,所述第一注册请求中携带有终端请求的NSSAI;
    第一接收模块,用于接收所述第一网元发送的第一信息;
    其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中不包括:按需注册的NSSAI,所述第一标识信息用于指示允许的按需注册的NSSAI。
  24. 根据权利要求23所述的装置,其中,所述装置还包括:第一获取模块和第一确定模块;其中,
    所述第一获取模块,用于基于URSP规则,获取传输待传输业务的PDU会话对应的S-NSSAI;
    所述第一确定模块,用于确定所述PDU会话对应的S-NSSAI与所述第一标识信息指示的一个允许的按需注册的NSSAI匹配;
    所述第一发送模块,还用于发送第二注册请求,其中,所述第二注册请求用于请求注册到所述S-NSSAI标识对应的网络切片;
    所述第一接收模块,还用于接收到注册成功响应;
    所述第一发送模块,还用于发送PDU会话建立请求,其中,所述PDU会话建立请求用于请求建立所述PDU会话。
  25. 一种允许的网络切片选择辅助信息的获取装置,包括:
    第二接收模块,用于接收终端发送的第一注册请求,其中,所述第一注册请求中携带有所述终端请求的NSSAI;
    第二确定模块,用于基于第一目标信息,确定所述终端对应的至少一个允许的NSSAI;
    第二发送模块,用于向所述终端发送第一信息,其中,所述第一信息包括允许的NSSAI和第一标识信息,其中,允许的NSSAI中包括所述至少一个允许的NSSAI中除按需注册的网络切片对应的NSSAI之外的NSSAI,所述第一标识信息用于指示所述至少一个允许的NSSAI中的按需注册的NSSAI。
  26. 一种控制策略获取的装置,包括:
    第三发送模块,用于向第二网元发送第一请求,其中,所述第一请求用于对应终端的终端行为信息的网络控制策略,所述第一请求中携带有所述终端行为信息;
    第三接收模块,用于接收所述第二网元发送的至少一项网络控制策略,其中,所述网络控制策略中包括S-NSSAI与注册定时器的对应关系。
  27. 根据权利要求26所述的装置,其中,还包括:
    第一控制模块,用于:
    执行所述终端注册到第一S-NSSAI对应的第一网络切片中的注册流程;
    在所述终端注册到所述第一网络切片成功的情况下,根据所述至少一项网络控制策略,启动与所述第一S-NSSAI对应的第一注册定时器;
    在所述第一注册定时器超时前未接收到与所述第一S-NSSAI对应的第一PDU会话的PDU会话建立请求的情况下,执行所述终端在所述第一网络切片的解注册流程。
  28. 根据权利要求27所述的装置,其中,所述网络控制策略中还包括S-NSSAI与会话定时器的对应关系;
    所述第三接收模块,还用于接收所述终端发起的PDU会话建立请求,其中,所述PDU会话建立请求用于请求建立与对应第二S-NSSAI的第二PDU会话;
    所述第一控制模块,还用于在确定所述第二PDU会话建立成功后,启动与所述第二S-NSSAI对应的第一会话定时器;在所述第一会话定时器超时的情况下,释放所述第二PDU会话,其中,在所述第二PDU会话对应的UPF连接为激活态或建立与所述第二PDU会话对应的新的UPF连接的情况下,所述第一会话定时器暂停,在所述第二PDU会话对应的UPF连接释放的情况下,所述第一会话定时器进行计时。
  29. 根据权利要求27所述的装置,其中,
    所述第三接收模块,还用于在接收所述第二网元返回的至少一项网络控制策略之后, 接收第三网元发送的会话释放消息,其中,所述会话释放消息用于指示释放第二PDU会话;
    所述第一控制模块,还用于释放所述第二PDU会话。
  30. 根据权利要求28或29所述的装置,其中,
    所述第一控制模块,还用于在释放所述第二PDU会话之后,启动与第二S-NSSAI对应的第二注册定时器,在所述第二注册定时器超时前未接收到与所述第二S-NSSAI对应的PDU会话建立请求的情况下,执行所述终端在所述第二S-NSSAI对应的第二网络切片的解注册流程,其中,所述第二S-NSSAI与所述第二PDU会话对应。
  31. 根据权利要求26至30中任一项所述的装置,其中,所述第三接收模块,还用于接收所述第二网元发送的更新后的所述至少一项网络控制策略。
  32. 一种控制策略的发送装置,包括:
    第四接收模块,用于接收第一网元发送的第一请求,其中,所述第一请求用于对应终端的终端行为信息的网络控制策略;
    第三确定模块,用于根据第二目标信息,确定至少一项网络控制策略,其中,所述网络控制策略中包括S-NSSAI与注册定时器的对应关系;
    第四发送模块,用于向所述第一网元发送所述至少一项网络控制策略。
  33. 根据权利要求32所述的装置,其中,
    所述第四接收模块,还用于接收第三网元发送的第二请求,其中,所述第二请求用于对应所述终端行为信息的会话控制策略;
    所述第三确定模块,还用于根据所述第二目标信息,确定至少一项会话控制策略,其中,所述会话控制策略中包括单NSSAI与会话定时器的对应关系;
    所述第四发送模块,还用于向所述第三网元发送所述至少一项会话控制策略。
  34. 根据权利要求33所述的装置,其中,
    所述第三确定模块,还用于确定更新所述至少一项会话控制策略,并获取更新后的至少一项会话控制策略;
    所述第四发送模块,还用于将更新后的所述至少一项会话控制策略发送给所述第三网元。
  35. 根据权利要求32至34中任一项所述的装置,其中,
    所述第三确定模块,还用于确定更新所述至少一项网络控制策略,并获取更新后的至少一项网络控制策略;
    所述第四发送模块,还用于将更新后的所述至少一项会话控制策略发送给所述第一网元。
  36. 一种PDU会话的控制装置,包括:
    第五接收模块,用于接收终端发送的PDU会话建立请求,所述PDU会话建立请求用于请求建立第二PDU会话;
    第五发送模块,用于向第二网元发送第二请求,其中,所述第二请求用于对应所述终端的终端行为信息的会话控制策略;
    所述第五接收模块,还用于接收所述第二网元发送的至少一项会话控制策略,其中,所述会话控制策略中包括S-NSSAI与会话定时器的对应关系;
    第二控制模块,用于:
    在确定所述第二PDU会话建立之后,启动与第二S-NSSAI对应的第一会话定时器,所述第二S-NSSAI为与所述第二PDU会话对应的S-NSSAI;
    在所述第一会话定时器超时的情况下,释放所述第二PDU会话,其中,在所述第二PDU会话对应的用户面功能UPF连接为激活态或建立与所述第二PDU会话对应的新的UPF连接的情况下,所述第一会话定时器暂停,在所述第二PDU会话对应的UPF连接释放的情况下,所述第一会话定时器进行计时。
  37. 根据权利要求36所述的装置,其中,所述第五发送模块,还用于向第一网元发送会话释放消息,其中,所述会话释放消息用于指示释放第二PDU会话。
  38. 一种终端,包括处理器和存储器,所述存储器存储可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求1至3任一项所述的允许的网络切片选择辅助信息的获取方法的步骤。
  39. 一种网络侧设备,包括处理器和存储器,所述存储器存储可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求4至5任一项所述的允许的网络切片选择辅助信息的获取方法的步骤,或者实现如权利要求6至12任一项所述的控制策略获取方法的步骤,或者实现如权利要求13至20任一项所述的控制策略的发送方法的步骤,或者实现如权利要求21至22任一项所述的PDU会话的控制方法的步骤。
  40. 一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如权利要求1至5任一项所述的允许的网络切片选择辅助信息的获取方法的步骤,或者实现如权利要求6至12任一项所述的控制策略的获取方法的步骤,或者实现如权利要求13至20任一项所述的控制策略的发送方法的步骤,或者实现如权利要求 21至22任一项所述的PDU会话的控制方法的步骤。
PCT/CN2023/104754 2022-07-21 2023-06-30 允许的nssai的获取方法、终端及网络侧设备 WO2024017023A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210860357.1A CN117479268A (zh) 2022-07-21 2022-07-21 允许的nssai的获取方法、终端及网络侧设备
CN202210860357.1 2022-07-21

Publications (1)

Publication Number Publication Date
WO2024017023A1 true WO2024017023A1 (zh) 2024-01-25

Family

ID=89617032

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/104754 WO2024017023A1 (zh) 2022-07-21 2023-06-30 允许的nssai的获取方法、终端及网络侧设备

Country Status (2)

Country Link
CN (1) CN117479268A (zh)
WO (1) WO2024017023A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021021423A1 (en) * 2019-07-31 2021-02-04 Qualcomm Incorporated Network slice availability check and indication
WO2021091285A1 (en) * 2019-11-06 2021-05-14 Samsung Electronics Co., Ltd. Method and apparatus for controlling network slice in wireless communication system
WO2022098942A1 (en) * 2020-11-05 2022-05-12 Convida Wireless, Llc Network controlled ue behavior for slice access

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021021423A1 (en) * 2019-07-31 2021-02-04 Qualcomm Incorporated Network slice availability check and indication
WO2021091285A1 (en) * 2019-11-06 2021-05-14 Samsung Electronics Co., Ltd. Method and apparatus for controlling network slice in wireless communication system
WO2022098942A1 (en) * 2020-11-05 2022-05-12 Convida Wireless, Llc Network controlled ue behavior for slice access

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "Pre-SA2#152E discussion on FS_eNS_Ph3", 3GPP PRE-SA2#152E FS_ENS_PH3 R00, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 9, XP009553314, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_152E_Electronic_2022-08/INBOX/DRAFTS/FS_eNS_Ph3> *
APPLE: "KI#6, New Sol: On-demand slices", SA WG2 MEETING #151E, S2-2204794, 21 May 2022 (2022-05-21), XP052160280 *
MYUNGJUNE YOUN, LG ELECTRONICS, NEC, [APPLE, NOKIA, NOKIA SHANGHAI BELL,] ERICSSON, [LENOVO,] SAMSUNG, HUAWEI, HISILICON, SK TELEC: "Improved network control of the UE beahviour for a network slice", 3GPP TSG-SA WG2 MEETING #155, S2-2303203, 27 February 2023 (2023-02-27), XP052249387 *

Also Published As

Publication number Publication date
CN117479268A (zh) 2024-01-30

Similar Documents

Publication Publication Date Title
WO2023169523A1 (zh) 数据采集方法、装置、终端及网络侧设备
WO2023143422A1 (zh) 灾难漫游的控制方法、装置、终端及网络侧设备
WO2023093609A1 (zh) 物联网设备的会话建立方法及装置
WO2024017023A1 (zh) 允许的nssai的获取方法、终端及网络侧设备
CN115209492A (zh) 通信处理方法、装置及相关设备
WO2023185929A1 (zh) 资源控制方法、装置、终端及网络侧设备
WO2024037512A1 (zh) 网络接入方法、装置、终端及通信设备
WO2023179553A1 (zh) 终端不可用时期的协商方法、终端及网络侧设备
WO2024032537A1 (zh) 通信方法、设备及可读存储介质
WO2023213242A1 (zh) Ue策略信息的配置方法、装置、第一网络功能及终端
WO2024022267A1 (zh) 算力任务迁移方法及通信设备
WO2024032543A1 (zh) 信息获取方法、终端及接入网设备
WO2024022440A1 (zh) 小区切换方法、装置及相关设备
WO2024022398A1 (zh) 托管网络的选网信息的获取方法、终端及网络侧设备
WO2023185845A1 (zh) 通信方法、装置及相关设备
WO2024037632A1 (zh) 通信方法、终端及网络侧设备
WO2023198068A1 (zh) 移动性管理方法、装置、终端、网络侧设备及介质
WO2024120470A1 (zh) 模型训练方法、终端及网络侧设备
WO2023185728A1 (zh) 业务处理方法、装置、终端、网络侧设备及可读存储介质
WO2023131286A1 (zh) 资源控制方法、装置、终端、网络侧设备及可读存储介质
WO2023246584A1 (zh) 算力处理方法、装置及通信设备
WO2024012373A1 (zh) Ai模型信息传输方法、装置及设备
WO2023143423A1 (zh) 信息获取与存储、上报方法、装置、终端及网络功能
WO2023246756A1 (zh) 算力服务方法、装置、终端及核心网设备
WO2023185877A1 (zh) 路由处理方法、终端及网络侧设备

Legal Events

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

Ref document number: 23842088

Country of ref document: EP

Kind code of ref document: A1