WO2019001204A1 - Procédé et appareil de sélection de tranche - Google Patents

Procédé et appareil de sélection de tranche Download PDF

Info

Publication number
WO2019001204A1
WO2019001204A1 PCT/CN2018/088889 CN2018088889W WO2019001204A1 WO 2019001204 A1 WO2019001204 A1 WO 2019001204A1 CN 2018088889 W CN2018088889 W CN 2018088889W WO 2019001204 A1 WO2019001204 A1 WO 2019001204A1
Authority
WO
WIPO (PCT)
Prior art keywords
nssai
terminal device
access
mobility management
management function
Prior art date
Application number
PCT/CN2018/088889
Other languages
English (en)
Chinese (zh)
Inventor
朱方园
余芳
李岩
倪慧
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019001204A1 publication Critical patent/WO2019001204A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular, to a slice selection method and apparatus.
  • the network segmentation technology provides a network environment that is isolated from each other in different application scenarios by means of a virtual independent logical network on the same network infrastructure, so that different application scenarios can customize network functions and features according to their respective requirements, thereby ensuring the requirements of different services. .
  • the terminal device may access one or more network slices.
  • the terminal device can provide the network slice selection assistance information (NSSAI) to the network for selecting a suitable terminal device for the network.
  • NSSAI network slice selection assistance information
  • AMF Access and mobility management function
  • S-NSSAI Single Network Slice Selection Assistance information
  • the terminal device needs to provide auxiliary information to indicate which S-NSSAI corresponds to the terminal.
  • the core network selects an AMF entity that serves the terminal device based on the auxiliary information. For example, as shown in FIG.
  • the network may select the second AMF entity AMF-2 as the AMF entity initially serving the terminal device.
  • the present application describes a slice selection method and apparatus.
  • an embodiment of the present application provides a slice selection method, the method comprising: a first access and mobility management function entity (eg, a first AMF entity) receiving a registration request message from a terminal device, where the registration request message includes The NSSAI corresponding to the slice requested by the terminal device.
  • the NSSAI corresponding to the slice requesting access includes at least a first S-NSSAI, wherein the first S-NSSAI is an S-NSSAI that is not supported by the first access and mobility management function entity.
  • the first access and mobility management function entity acquires the attribute information of the first S-NSSAI, and uses the slice corresponding to the second S-NSSAI to provide the service corresponding to the first S-NSSAI to the terminal device according to the attribute information.
  • the first access and mobility management function entity acquires an NSSP, and the NSSP includes an association between the application and the second S-NSSAI.
  • the first access and mobility management function entity sends a registration accept message to the terminal device, where the registration accept message includes the NSSAI and the NSSP corresponding to the slice that the terminal device allows access, and the NSSAI corresponding to the slice that is allowed to access includes the second S-NSSAI.
  • the first AMF entity obtains the attribute information.
  • the first S-NSSAI corresponding to the second S-NSSAI is used according to the attribute information to provide the first S-NSSAI corresponding to the terminal device.
  • the service corresponding to the first S-NSSAI that is not supported is not discarded, but is provided by the slice corresponding to the second S-NSSAI.
  • the NSSP rule in the NSSP acquired by the first access and mobility management function entity is associated with the second S-NSSAI.
  • the terminal device can be aware that the service corresponding to the first S-NSSAI is provided by the slice corresponding to the second S-NSSAI. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • obtaining attribute information of the first S-NSSAI may be implemented by: the first access and mobility management function entity from a user data management device (eg, a UDM device) or a policy control function device (
  • the PCF device acquires attribute information of the first S-NSSAI.
  • the first access and mobility management function entity acquires the slice subscription policy information from the user data management device or the policy control function device, and obtains the attribute information of the first S-NSSAI from the slice subscription policy information.
  • the acquiring the NSSP may be implemented by: the first access and mobility management function entity sending the foregoing indication information to the policy control function device, requesting the policy control function device to update the NSSP related to the first S-NSSAI .
  • the first access and mobility management function entity receives the NSSP from the policy control function device.
  • the method further includes: the first access and mobility management function entity adds indication information in the context of the terminal device, the indication information is used to indicate that the first access and mobility management function entity uses The slice corresponding to the second S-NSSAI provides the service corresponding to the first S-NSSAI for the terminal device. Therefore, through the delivery of the context, the other access and mobility management function entities can obtain the foregoing indication information, thereby determining whether the access and mobility management function entity is suitable for the terminal device, thereby improving the user's service experience.
  • the method further includes: the first access and mobility management function entity receives a request message from the second access and mobility management function entity (eg, the second AMF entity) to request the terminal device Context; the first access and mobility management function entity sends the context of the terminal device to the second access and mobility management function entity, the context including the indication information. Therefore, according to the solution of the present application, after the terminal device moves, the second AMF entity requests the context of the terminal device from the first AMF entity before the mobile, so that the second AMF entity is not the most suitable AMF entity, if the terminal device is currently accessed.
  • the second AMF entity requests the context of the terminal device from the first AMF entity before the mobile, so that the second AMF entity is not the most suitable AMF entity, if the terminal device is currently accessed.
  • the third AMF entity there are other access and mobility management function entities (eg, the third AMF entity) that can support the first S-NSSAI, and then redirect the terminal device to the third AMF entity supporting the first S-NSSAI.
  • the terminal device is served by a "most suitable" third AMF entity.
  • the service corresponding to the first S-NSSAI can still be implemented in the second PLMN after the terminal device moves. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the present application further discloses a slice selection method, including: a second access and mobility management function entity receives a registration request message, where the registration request message includes an NSSAI corresponding to a slice that the terminal device allows access, and a terminal device.
  • the temporary identifier, the NSSAI corresponding to the slice allowed to access includes the second S-NSSAI.
  • the second access and mobility management function entity acquires the context of the terminal device from the first access and mobility management function entity according to the temporary identifier, and the context includes indication information.
  • the indication information is used to indicate that the first access and mobility management function entity uses the slice corresponding to the second S-NSSAI to provide the terminal device with the service corresponding to the first S-NSSAI.
  • the second access and mobility management function entity does not support the first S-NSSAI, but there are other access and mobility management function entities in the PLMN network currently accessed by the terminal device that can support the first S-NSSAI, then the second The access and mobility management function entity redirects the terminal device to a third access and mobility management functional entity (eg, a third AMF entity) that supports the first S-NSSAI.
  • a third access and mobility management functional entity eg, a third AMF entity
  • the second AMF entity requests the context of the terminal device from the first AMF entity before the mobile, so as to know that the second AMF entity is not the most suitable AMF entity, if the terminal device currently accesses the PLMN.
  • the first AMF entity in the first PLMN does not support the first S-NSSAI
  • the service corresponding to the first S-NSSAI can still be implemented in the second PLMN after the terminal device moves. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the method further includes: the second access and mobility management function entity sends a context of the terminal device to the third access and mobility management function entity, the context including the indication information. Therefore, the third access and mobility management function entity receiving the indication information can send the indication information to the PCF device and request the PCF device to update the NSSP related to the second S-NSSAI. Thus, the updated NSSP is restored to the "real" content. Subsequently, the terminal device can obtain the complete service according to the updated NSSP association application and the S-NSSAI. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the present application further discloses a slice selection method, including: a third access and mobility management function entity acquires a context of a terminal device, where the context includes indication information.
  • the indication information is used to indicate that the first access and mobility management function entity uses the slice corresponding to the second S-NSSAI to provide the terminal device with the service corresponding to the first S-NSSAI.
  • the third access and mobility management function entity sends indication information to the policy control function device, requesting the policy control function device to update the NSSP related to the second S-NSSAI.
  • the updated NSSP includes an association between the application and the first S-NSSAI.
  • the third access and mobility management function entity receives the updated NSSP from the policy control function device.
  • the "most suitable" third AMF entity provides services for the terminal device.
  • the third AMF entity acquires the context containing the indication information, and sends the indication information to the PCF device and requests the PCF device to update the NSSP related to the second S-NSSAI.
  • the updated NSSP is restored to the "real" content.
  • the terminal device can obtain the complete service according to the updated NSSP association application and the S-NSSAI. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the present application also discloses a slice selection method, including: the policy control function device receives indication information from a first access and mobility management function entity.
  • the indication information is used to indicate that the first access and mobility management function entity uses the slice corresponding to the second S-NSSAI to provide the terminal device with the service corresponding to the first S-NSSAI.
  • the policy control function device updates the NSSP related to the first S-NSSAI according to the indication information, and sends the updated first NSSP to the first access and mobility management function entity.
  • the updated first NSSP includes an association between the application and the second S-NSSAI.
  • the PCF device when the first AMF entity does not support the first S-NSSAI and the slice corresponding to the second S-NSSAI is used to provide the service corresponding to the first S-NSSAI to the terminal device, the PCF device will involve the first S- The NSSP of the NSSAI is updated such that the updated NSSP includes an association between the application and the second S-NSSAI. Therefore, the service corresponding to the first S-NSSAI that is not supported is not discarded, but is provided by the slice corresponding to the second S-NSSAI.
  • the terminal device can sense that the service corresponding to the first S-NSSAI is replaced by the slice corresponding to the second S-NSSAI. The services corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the method further includes: the policy control function device receiving the indication information from the third access and mobility management function entity; the policy control function device updating, according to the indication information, the second S- The NSSAI NSSP, the updated second NSSP includes an association between the application and the first S-NSSAI; the policy control function device sends the updated second NSSP to the third access and mobility management function entity. Therefore, when the terminal device moves, the terminal device is served by the "most appropriate" third AMF entity.
  • the third AMF entity sends the indication information to the PCF device and requests the PCF device to update the NSSP related to the second S-NSSAI.
  • the updated NSSP is restored to the "real" content.
  • the terminal device can obtain the complete service according to the updated NSSP association application and the S-NSSAI. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the present application further discloses a slice selection method, including: determining, by the terminal device, whether the current location of the terminal device is within a service area of the first slice corresponding to the first S-NSSAI according to the NSSP.
  • the NSSP includes an association between the first S-NSSAI and a service area of the first slice.
  • the terminal device sends a registration request message.
  • the registration request message carries the first S-NSSAI.
  • the first S-NSSAI is used to select the first slice.
  • the terminal device before the terminal device initiates the registration request, it is determined whether the current location of the terminal device is within the service area of the slice corresponding to the first S-NSSAI in the requested NSSAI.
  • the first S-NSSAI is included in the NSSAI of the registration request message only when the current location of the terminal device is within the service area. Therefore, the core network is prevented from rejecting the registration request of the terminal device because the S-NSSAI requested by the terminal device cannot be supported, thereby saving signaling interaction between the terminal device and the core network.
  • the step of determining includes: the terminal device periodically determining whether the base station corresponding to the current location of the terminal device is within the service area of the first slice. Therefore, if the location of the terminal device in the first time is not in the service area of the slice corresponding to the first S-NSSAI in the requested NSSAI, the terminal device determines, in the subsequent second time, the location of the terminal device in the requested NSSAI. Within the service area of the slice corresponding to the S-NSSAI, a new registration request can still be initiated to obtain the corresponding service.
  • the embodiment of the present application provides an access and mobility management function entity, where the session management function entity has the first access and mobility management function entity, the second access and mobility management in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the access and mobility management functional entity includes a processor and a transceiver configured to process the first access and mobility management functional entity, the second access and the mobile
  • the sex management function entity or the third access and mobility management function entity performs the corresponding functions in the above methods.
  • the transceiver is configured to implement a first access and mobility management function entity, a second access and mobility management function entity or a third access and mobility management function entity and other access and mobility management function entities/policies Control communication between the functional device/user data management device/access network device.
  • the access and mobility management functional entity may also include a memory for coupling with the processor that holds program instructions and data necessary for the session management function entity.
  • an embodiment of the present application provides a policy control function device, where the policy control function device has a function of implementing a policy control function device behavior in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the policy control function device includes a processor and a transceiver configured to process a policy control function device to perform a corresponding function in the above method.
  • the transceiver is configured to implement communication between a policy control function device and an access and mobility management function entity.
  • the policy control function device can also include a memory for coupling with the processor that holds program instructions and data necessary for the session management function entity.
  • an embodiment of the present application provides a terminal device, where the terminal device has a function of implementing behavior of a terminal device in the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the terminal device includes a processor and a transceiver, the processor being configured to process the terminal device to perform a corresponding function in the above method.
  • the transceiver is configured to implement communication between the terminal device and the access and mobility management function entity/access network device.
  • the terminal device may also include a memory for coupling with the processor that holds program instructions and data necessary for the session management function entity.
  • embodiments of the present application provide a computer readable storage medium having instructions stored therein that, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • embodiments of the present application provide a computer program product comprising instructions that, when run on a computer, cause the computer to perform the methods described in the various aspects above.
  • the present application provides a chip system, including a processor, for supporting the foregoing access and mobility management function entity, a policy control function device, or a terminal device to implement the functions involved in the foregoing aspects, for example, , generating or processing the information involved in the above method.
  • the chip system further includes a memory for holding program instructions and data necessary for the data transmitting device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • FIG. 1 is a schematic diagram of a part of an S-NSSAI in which an AMF entity can only support a terminal device request in the prior art
  • FIG. 2 is a schematic diagram of a network slice-based communication system according to an embodiment of the present invention.
  • FIG. 3 is a signaling interaction diagram of a slice selection method according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of reselecting an AMF entity after a terminal device moves according to an embodiment of the present invention
  • FIG. 5 is a signaling interaction diagram of a slice selection method according to an embodiment of the present invention.
  • 6 to 9 are schematic flowcharts of a slice selection method according to an embodiment of the present invention.
  • FIG. 10 is a schematic flowchart diagram of a slice selection method according to another embodiment of the present invention.
  • FIG. 11A and 11B are schematic structural diagrams of an AMF entity according to an embodiment of the present invention.
  • 12A and 12B are schematic diagrams showing the structure of a PCF entity according to an embodiment of the present invention.
  • FIGS. 13A and 13B are schematic diagrams showing the structure of a terminal device according to an embodiment of the present invention.
  • the embodiment of the present application proposes a solution based on the communication system shown in FIG. 2, which can be applied to implement network slice selection in a next generation mobile network (such as 5G network) architecture.
  • a next generation mobile network such as 5G network
  • the control plane function and the forwarding plane function of the mobile gateway are decoupled, and the separated control plane functions and the third generation partnership project (3GPP) traditional control network element MME And merge into a unified control plane entity.
  • the user plane UPF entity can implement user plane functions (SGW-U and PGW-U) of a serving gateway (SGW) and a packet data network gateway (PGW).
  • the unified control plane entity can be decomposed into an access and mobility management function (AMF) entity and a session management function (SMF) entity.
  • AMF access and mobility management function
  • SMF session management function
  • the AMF entity may be responsible for the attachment, mobility management, and tracking area update process of the terminal device.
  • the SMF entity may be responsible for session management of the terminal device, selection of user plane devices, reselection of user plane devices, internet protocol (IP) address allocation, quality of service (QoS) control, and session establishment, Modify and release, etc.
  • IP internet protocol
  • QoS quality of service
  • the embodiments of the present application can also be applied to other communication technologies for the future.
  • the system architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.
  • the embodiment of the present application provides a network slice-based communication system.
  • the communication system includes at least a terminal device 202, an access network device 204, and a plurality of network slices, such as network slice 1 and network slice 2.
  • network slice such as network slice 1 and network slice 2.
  • the description is referred to as “slice” of “network slice”.
  • each slice may also be referred to as “slice instance” or “network slice instance”, which is not in the present application. This limit.
  • the terminal device 202 can access one or multiple slices simultaneously.
  • slice 1 and slice 2 may share a partial control plane, which may also be referred to as a shared control network function (CCNF).
  • the control plane that Slice 1 and Slice 2 can share includes AMF entity 206.
  • the session management function is slice-specific, and this part of the control function needs to be instantiated within the slice.
  • the user plane functionality also needs to be instantiated within the slice.
  • the session management function and the user plane function are slice-specific and are used to implement slice-specific services.
  • slice 1 includes SMF entity 208a and user plane entity 210a
  • slice 2 includes SMF entity 208b and user plane entity 210b.
  • the terminal device 202 involved in the embodiments of the present application may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem.
  • the terminal device may also be referred to as a user equipment (UE), a mobile station (MS), a terminal, and may also include a subscriber unit, a cellular phone, a smart phone.
  • UE user equipment
  • MS mobile station
  • subscriber unit a cellular phone
  • smart phone smart phone
  • wireless data card personal digital assistant (PDA) computer, tablet computer, wireless modem (modem), handheld device, laptop computer, cordless phone (cordless) Phone) or wireless local loop (WLL) station, machine type communication (MTC) terminal, and the like.
  • PDA personal digital assistant
  • modem modem
  • handheld device laptop computer
  • cordless phone cordless phone
  • WLL wireless local loop
  • MTC machine type communication
  • the access network device involved in the embodiment of the present application is a device deployed in a wired or wireless access network to provide wireless communication functions for the terminal device 102.
  • the access network device may include various forms of base stations, such as a macro base station, a micro base station (also referred to as a small station), a relay station, an access point, and the like.
  • base stations such as a macro base station, a micro base station (also referred to as a small station), a relay station, an access point, and the like.
  • the name of a device having a base station function may be different, for example, in an LTE system, an evolved Node B (evolved NodeB, eNB or eNodeB), in the third In a 3rd generation (3G) system, it is called a Node B or the like.
  • gNB gNodeB
  • the AMF entity involved in the embodiment of the present application may be responsible for attachment, mobility management, tracking area update process, and the like of the terminal device.
  • AMF entities may also be referred to as AMF devices or AMF network elements. In the example of Figure 2, only one AMF entity is shown. However, the invention does not limit the number of AMF entities. Different AMF entities can be connected to different slices or to the same slice.
  • slice 1 and slice 2 respectively include an SMF entity: SMF entities 208a and 208b.
  • the SMF entity involved in the embodiment of the present application may be responsible for session management of the terminal device, selection of the user plane entity, reselection of the user plane entity, IP address allocation, QoS control, and establishment, modification, and release of the session.
  • the SMF entity may also be referred to as an SMF device or an SMF network element.
  • slice 1 and slice 2 respectively include one UPF entity: UPF entity 210a and UPF entity 210b.
  • the UPF entity 210a and the UPF entity 210b may be connected to the same or different data networks (DNs) for implementing data transmission of the service.
  • the UPF entity may also be referred to as a UPF device or a UPF network element.
  • the communication system further includes a user data management (UDM) device 212.
  • the UDM device 212 is configured to store subscription data of the user, for example, mobility management related subscription data and session management related subscription data.
  • a UDM device may also be referred to as a UDM entity or a UDM network element.
  • the communication system further includes a policy control function (PCF) device 214.
  • the PCF device 214 includes policy control and flow charging based control functions.
  • the PCF device 214 can implement a user subscription data management function, a policy control function, a charging policy control function, QoS control, and the like.
  • a PCF device may also be referred to as a PCF entity or a PCF network element.
  • establishing a user plane connection to a data network by slicing includes two steps: first, selecting an AMF entity supporting NSSAI through a registration process; and second, establishing one or more by slicing A packet data unit (PDU) session to the data network.
  • PDU packet data unit
  • the terminal device 202 can access one or multiple slices at the same time. Each slice can provide different services. In addition, operators can also lay out multiple slices to provide the same service for different groups of users.
  • the type of slice can be identified by S-NSSAI.
  • NSSAI is a collection of S-NSSAI. Each S-NSSAI is used by the secondary network to select a particular network slice instance. It is also possible to select the same network slice instance through different S-NSSAI.
  • the terminal device 202 Under each PLMN, the terminal device 202 locally stores an NSSAI corresponding to the slice configured to be accessed (referred to as a configured NSSAI, configured NSSAI in the following description). In the process of initial registration initiated by the network, the terminal device 202 may use the S-NSSAI in the configured NSSAI as the NSSAI corresponding to the slice requesting access (referred to as the requested NSSAI, requested NSSAI in the following description). Slice selection. The access network device selects an appropriate AMF entity according to the requested NSSAI and sends an initial registration request message to the AMF entity.
  • the terminal device 202 obtains, from the core network, an NSSAI corresponding to the slice that is allowed to be accessed under the PLMN (referred to as an allowed NSSAI, allowed NSSAI in the following description) and stores it.
  • an allowed NSSAI corresponding to the slice that is allowed to be accessed under the PLMN
  • Each S-NSSAI in the allowed NSSAI is valid under the registration area of the AMF to which the terminal device 202 has been registered.
  • the subsequent terminal device 202 initiates a service request, the above-mentioned allowed NSSAI may be provided to the network for slice selection.
  • the terminal device 202 may be locally stored through a network-triggered mobility management (MM) process.
  • MM network-triggered mobility management
  • step 301 the terminal device 202 sends a registration request message to the access network device 204.
  • the registration request message carries the requested NSSAI.
  • the access network device 204 After receiving the registration request message, the access network device 204 selects the AMF entity for the terminal device 202 according to the requested NSSAI. If no AMF entity in the current PLMN can satisfy all S-NSSAIs in the requested NSSAI, the access network device 204 selects the first AMF entity according to the local policy information.
  • the requested NSSAI includes S-NSSAI 2, 3, 4. There is no AMF entity in the current PLMN that can support S-NSSAI 2, 3, 4 at the same time.
  • the first AMF entity within the current PLMN supports S-NSSAI 3, 4 in the requested NSSAI, but does not support S-NSSAI 2 in the requested NSSAI.
  • the access network device selects the first AMF entity according to the local policy information.
  • the access network device 204 sends a registration request message containing the requested NSSAI to the first AMF entity.
  • Step 302 After receiving the registration request message, the first AMF entity acquires the attribute information of the first S-NSSAI.
  • the first S-NSSAI is an S-NSSAI (for example, the above S-NSSAI 2) that is not supported by the first AMF entity in the requested NSSAI.
  • the first AMF entity does not support the first S-NSSAI, indicating that the first AMF entity is not connected to the slice corresponding to the first S-NSSAI.
  • the attribute information of the first S-NSSAI is used to indicate whether the service corresponding to the first S-NSSAI is allowed to be provided to the terminal device 202 by using the slice corresponding to the other S-NSSAI if the current SMN does not support the first S-NSSAI.
  • "other S-NSSAI" here may be the default S-NSSAI (default S-NSSAI).
  • the first S-NSSAI may be replaced by other S-NSSAIs in the requested NSSAI.
  • the first AMF entity sends a request message to the UDM device 212 or the PCF device 214, where the request message carries a permanent identifier of the terminal device 202, and the request message message is used to request the slice subscription policy information of the terminal device 202.
  • the first AMF entity receives a response message containing slice subscription policy information.
  • the slice subscription policy information includes attribute information of each S-NSSAI and each S-NSSAI in the NSSAI signed by the terminal device 202.
  • the NSSAI signed by the terminal device 202 includes the S-NSSAI 2, 3, and 4, and the slice subscription policy information acquired by the first AMF entity is as shown in Table 1:
  • the first column indicates each S-NSSAI in the NSSAI contracted by the terminal device 202
  • the second column indicates the attribute information of each S-NSSAI.
  • the attribute information of S-NSSAI2 is S-NSSAI 3, indicating that the service corresponding to S-NSSAI2 can be provided by the slice corresponding to S-NSSAI 3 instead of the slice corresponding to S-NSSAI 2.
  • the attribute information of S-NSSAI 3 is null, indicating that the service corresponding to S-NSSAI3 has no other S-NSSAI corresponding slice.
  • the first AMF entity may obtain the attribute information of the first S-NSSAI from the slice subscription policy information.
  • Step 303 The first AMF entity provides the terminal device 202 with the service corresponding to the first S-NSSAI by using the slice corresponding to the second S-NSSAI according to the attribute information.
  • the first AMF entity learns, according to the attribute information, that the second S-NSSAI can provide the service corresponding to the first S-NSSAI in place of the first S-NSSAI.
  • the service corresponding to the above S-NSSAI 2 may be provided by a slice corresponding to the S-NSSAI 3.
  • the second S-NSSAI is determined according to the above attribute information, and can replace the S-NSSAI of the service corresponding to the first S-NSSAI in place of the first S-NSSAI.
  • the second S-NSSAI is S-NSSAI 3.
  • the second S-NSSAI is the S-NSSAI in the requested NSSAI.
  • the first AMF entity Since the first AMF entity supports the S-NSSAI 3, 4, and the service corresponding to the S-NSSAI 2 can be provided by the slice corresponding to the S-NSSAI 3, the first AMF entity supporting the S-NSSAI 3, 4 can be equal to
  • the terminal device 202 is provided with services corresponding to the slice S-NSSAI 2, 3, 4. Therefore, the first AMF entity may use the slice corresponding to the second S-NSSAI to provide the terminal device 202 with the service corresponding to the first S-NSSAI to serve the terminal device 202.
  • Step 304 The first AMF entity adds an indication (indication) in the context of the terminal device 202, where the indication information is used to indicate that the first AMF entity uses the slice corresponding to the second S-NSSAI to provide the first S-NSSAI to the terminal device 202.
  • the indication information is used to indicate that the first AMF entity uses the slice corresponding to the S-NSSAI 3 to provide the terminal device 202 with the service corresponding to the S-NSSAI 2.
  • the first AMF entity may also add the received slice subscription policy information to the context of the terminal device 202.
  • Step 305 the first AMF entity sends a request message to the PCF device 214.
  • the request message carries the indication information.
  • the request message is a network slicing selection policy (NSSP) update request message.
  • NSSP network slicing selection policy
  • Step 306 After receiving the request message, the PCF device 214 updates the NSSP according to the indication information, and sends a response message carrying the updated NSSP to the first AMF entity.
  • the NSSP of the terminal device 202 stored in the PCF device 214 is as shown in Table 2:
  • the NSSP includes one or more NSSP rules, and each NSSP rule associates an application with an S-NSSAI.
  • the NSSP rule 1 is associated with the application A and the S-NSSAI 2
  • the NSSP rule 2 is associated with the application B and the S-NSSAI 2.
  • the application A and the application B need to select the slice according to the NSSP rule 1 and the rule 2, respectively, and the slice types corresponding to the application A and the application B correspond to the S-NSSAI 2.
  • NSSP rule 3 is associated with application C and S-NSSAI 3
  • NSSP rule 4 is associated with application D and S-NSSAI 4.
  • the PCF device 214 After receiving the request message carrying the indication information, the PCF device 214 updates the NSSP of the terminal device 202. For example, PCF device 214 updates the NSSP rules relating to the first S-NSSAI to be associated with the second S-NSSAI (eg, S-NSSAI 3).
  • the updated NSSP is referred to as the first NSSP and includes the association of the application with the second S-NSSAI.
  • the first NSSP is shown in Table 3:
  • the PCF device 214 adds a flag to the modified NSSP rule, where the flag is used to indicate that the first S-NSSAI corresponding to the NSSP rule is modified by the core network to be the second S- NSSAI, thus modifying the NSSP rules associated with the second S-NSSAI, and the unmodified itself is distinguished from the NSSP rules associated with the second S-NSSAI.
  • a second S-NSSAI ie, S-NSSAI 3
  • S-NSSAI 3 corresponding to NSSP rule 1 and NSSP rule 2 respectively adds a flag to distinguish NSSP rules 1, 2 and NSSP rules 3
  • NSSP Rule 1 and NSSP Rule 2 are rules that associate the application with the second S-NSSAI after being modified by the core network.
  • the NSSP rule 3 is not modified by the core network, and is itself a rule that associates the application with the second S-NSSAI.
  • the PCF device 214 sends a response message to the first AMF entity.
  • the response message carries the first NSSP.
  • Step 307 The first AMF entity sends a registration accept message to the terminal device 202 through the access network device 204.
  • the registration acceptance message includes the first NSSP and the allowed NSSAI.
  • the allowed NSSAI includes the above second S-NSSAI.
  • S-NSSAI 3 is the second S-NSSAI
  • the allowed NSSAI includes S-NSSAI 3, 4.
  • the registration accept message also includes a temporary identity assigned by the first AMF entity to the terminal device 202.
  • the temporary identifier includes a 5G-globally unique temporay identifier (5G-GUTI).
  • the temporary identifier allocated by the first AMF entity to the terminal device 202 includes a first field (for example, identification information of the first AMF) for identifying the first AMF entity, and a terminal device for uniquely identifying the first AMF entity.
  • the second field of 202 is a temporary identity assigned by the first AMF entity to the terminal device 202.
  • step 308 the terminal device 202 stores the first NSSP. In addition, the terminal device 202 also stores the allowed NSSAI.
  • the terminal device 202 initiates a session establishment process by selecting a corresponding S-NSSAI for the application according to the first NSSP association application and the S-NSSAI.
  • an application of the terminal device 202 initiates a data transmission, and the terminal device 202 selects an S-NSSAI for the application according to the first NSSP.
  • the terminal device 202 selects the S-NSSAI 3 according to the NSSP rule 1 in the first NSSP, and sends a session establishment request message carrying the S-NSSAI 3 to the core network, and the session establishment process is continued by the core network. .
  • the first AMF entity acquires attribute information from the UDM device 212 or the PCF device 214, and according to the attribute information, when the first AMF entity does not support the first S-NSSAI, the second S-NSSAI is used.
  • the corresponding slice provides the terminal device 202 with the service corresponding to the first S-NSSAI. Therefore, the service corresponding to the first S-NSSAI that is not supported is not discarded, but is provided by the slice corresponding to the second S-NSSAI.
  • the PCF device 214 accordingly updates the NSSP rules relating to the first S-NSSAI to be associated with the second S-NSSAI.
  • the terminal device 202 may be aware that the service corresponding to the first S-NSSAI is provided by the slice corresponding to the second S-NSSAI. Thereby, the service corresponding to the NSSAI requested by the terminal device 202 can be satisfied, and the service experience of the user is improved.
  • the AMF entity needs to be reselected.
  • the first AMF entity is located in the first PLMN, and the second ALM entity includes a second AMF entity and a third AMF entity.
  • the second AMF entity supports S-NSSAI 3, 4
  • the third AMF entity supports S-NSSAI 2, 3, 4. Since the allowed NSSAI stored in the terminal device 202 includes the S-NSSAI 3, 4, when the terminal device 202 initiates the periodic registration update request procedure again after the mobile, the NSSAI requested by the terminal device 202 is the allowed NSSAI. Therefore, both the second AMF entity and the third AMF entity can satisfy the request of the terminal device 202. According to the solution of the present application, the terminal device 202 can be redirected to the "best fit" third AMF entity by the "second-appropriate" second AMF entity to obtain the service, thereby improving the user's service experience.
  • the terminal device 202 Before step 501, the terminal device 202 is located in the first PLMN, and the terminal device 202 registers with the first AMF entity through the registration process. For example, the terminal device 202 registers with the first AMF entity through steps 301 to 308 in FIG. 3 described above. I will not repeat them here.
  • Step 501 when the terminal device 202 moves from the first PLMN to the second PLMN, the terminal device 202 sends a registration request message to the access network device 204' in the second PLMN.
  • the registration request message carries the requested NSSAI.
  • the requested NSSAI is the allowed NSSAI held by the terminal device 202.
  • the allowed NSSAI carried by the UE in step 501 is referred to as a first allowed NSSAI, and the first allowed NSSAI includes the second S-NSSAI described above.
  • the first allowed NSSAI includes S-NSSAI 3, 4.
  • the registration request message further includes a temporary identifier allocated by the first AMF entity to the terminal device 202.
  • the temporary identity can also be referred to as the old temporary identity.
  • Step 502 After receiving the registration request message, the access network device 204' selects the AMF entity for the terminal device 202 according to the requested NSSAI.
  • the access network device 204' within the second PLMN cannot identify the first AMF entity based on the old temporary identification of the terminal device 202. Accordingly, the access network device 204' re-selects the AMF entity for the terminal device 202 based on the requested NSSAI.
  • the requested NSSAI includes S-NSSAI 3, 4.
  • the second AMF entity within the second PLMN supports the S-NSSAI 3, 4 in the requested NSSAI, and the third AMF entity within the second PLMN additionally supports S-NSSAI 2.
  • the access network device selects the second AMF entity according to the local policy information.
  • the access network device 204' sends a registration request message to the second AMF entity.
  • the registration request message includes the NSSAI of the above request and the old temporary identity of the terminal device 202.
  • Step 504 After receiving the registration request message, the second AMF entity acquires the context of the terminal device 202 from the first AMF entity according to the old temporary identifier of the terminal device 202.
  • the second AMF entity obtains the identification information of the first AMF entity according to the first field in the old temporary identifier of the terminal device 202, thereby requesting the first AMF entity to acquire the context of the terminal device 202. Since the first AMF entity has previously added in the context of the terminal device 202 to instruct the first AMF entity to use the slice corresponding to the second S-NSSAI to provide the first device S for the terminal device 202 (eg, by step 304 in FIG. 3) The indication information of the service corresponding to the NSSAI, and the context of the terminal device 202 acquired by the second AMF entity from the first AMF entity includes the indication information.
  • the second AMF entity further includes the slice subscription policy information of the terminal device 202 in the context of acquiring the terminal device 202 from the first AMF entity.
  • Step 505 If the second AMF entity does not support the first S-NSSAI, the second AMF entity redirects the terminal device 202 to the third AMF entity supporting the first S-NSSAI in the second PLMN.
  • the second AMF entity learns, according to the indication information in the context, that the service corresponding to the first S-NSSAI is provided by the second S-NSSAI corresponding to the terminal device 202.
  • the second AMF entity may learn that the NSSAI of the "actual" request by the terminal device 202 includes at least the first S-NSSAI. Therefore, the second AMF entity is not the "most suitable" AMF entity serving the terminal device 202.
  • the second AMF entity redirects the terminal device 202 to the third of the second PLMN that supports the first S-NSSAI.
  • AMF entity learns that the terminal device 202 has subscribed to the first S-NSSAI according to the slice subscription policy information included in the context acquired in step 504, and the AMF entity (eg, the third AMF entity) may exist in the current PLMN.
  • the slice service corresponding to the first S-NSSAI is provided to the UE.
  • the second AMF entity learns that the NSSAI of the "actual" request by the terminal device 202 includes at least the first S-NSSAI and the second S-NSSAI.
  • the second AMF entity is not the "best fit" AMF entity serving the terminal device 202, thereby redirecting the terminal device 202 to a third AMF entity supporting the first S-NSSAI and the second S-NSSAI within the second PLMN .
  • the second AMF entity learns that the terminal device 202 has subscribed to the first S-NSSAI and the second S-NSSAI according to the slice subscription policy information included in the context acquired in step 504. Then, the current PLMN has an AMF entity (for example, The third AMF entity may provide the UE with a slice service corresponding to the first S-NSSAI and the second S-NSSAI.
  • the second AMF entity may select the third AMF entity by the following three implementation manners.
  • the present invention does not limit the method for selecting the third AMF entity by the second AMF entity.
  • the second AMF entity is configured with identifier information of other AMF entities in the current second PLMN and corresponding capability information (supported S-NSSAI), and the second AMF entity according to other AMF capabilities The information determines that the third AMF entity can support the first S-NSSAI and obtain the identification information of the third AMF entity.
  • the second AMF entity sends a request message to the network slicing selection function (NSSF) network element, where the request message carries the S-NSSAI that the target AMF entity needs to support (for example, First S-NSSAI).
  • the NSSF determines that the third AMF entity can support the first S-NSSAI, and sends a response message to the second AMF entity, where the response message carries the identifier information of the third AMF entity.
  • the second AMF entity sends a request message to the Network Repository Function (NRF) network element, where the request message carries the S-NSSAI that the target AMF entity needs to support (for example, An S-NSSAI).
  • NRF Network Repository Function
  • the NRF determines that the third AMF entity can support the first S-NSSAI, and sends a response message to the second AMF entity, where the response message carries the identifier information of the third AMF entity.
  • the NSSAI of the request received by the second AMF entity through step 503 includes S-NSSAI 3, 4.
  • the second AMF entity obtains the indication information by step 504: the first AMF entity uses the slice corresponding to the S-NSSAI 3 to provide the terminal device 202 with the service corresponding to the S-NSSAI 2.
  • the second AMF entity learns that the NSSAI of the "actual" request by the terminal device 202 includes S-NSSAI 2, 3, 4. Since the second AMF entity only supports S-NSSAI 3,4 but does not support S-NSSAI 2, the second AMF entity is not the "most suitable" AMF entity serving the terminal device 202. Since the second PLMN has a third AMF entity supporting both S-NSSAI 2, 3, 4, the second AMF entity redirects the terminal device 202 to a third AMF entity supporting S-NSSAI 2, 3, 4.
  • the second AMF entity may forward the registration request message sent by the terminal device 202 to the third AMF entity by using the access network device 204', that is, the second AMF entity first sends the terminal device 202.
  • the registration request message and the identification information of the third AMF entity are sent to the access network device 204', and the access network device 204' forwards the registration request message sent by the terminal device 202 to the third AMF entity according to the identification information of the third AMF entity.
  • the second AMF entity directly forwards the registration request message sent by the terminal device 202 to the third AMF entity according to the identifier information of the third AMF entity.
  • the registration request message sent by the terminal device 202 forwarded by the second AMF entity is the same as the parameter carried in step 501.
  • the registration request message sent by the terminal device 202 forwarded by the second AMF entity is the same as the parameter carried in step 501.
  • step 501 sees that the registration request message sent by the terminal device 202 forwarded by the second AMF entity is the same as the parameter carried in step 501.
  • the terminal device 202 is served by the third AMF entity.
  • Step 506 the third AMF entity sends a request message to the PCF device 214.
  • the request message carries the indication information for requesting the PCF device 214 to update the NSSP related to the second S-NSSAI. For example, the request message selects a policy update request message for the network slice.
  • the third AMF entity first obtains the foregoing indication information by:
  • a first possible implementation manner in the foregoing redirection process, the second AMF entity passes the context including the indication information to the third AMF entity.
  • the third AMF entity obtains the old temporary identifier of the terminal device 202. Thereafter, the third AMF entity acquires the context of the terminal device 202 containing the indication information from the first AMF entity according to the old temporary identifier of the terminal device 202.
  • Step 507 After receiving the request message, the PCF device 214 updates the NSSP according to the indication information, and sends a response message carrying the updated NSSP to the first AMF entity.
  • the NSSP of the terminal device 202 stored in the PCF device 214 is as shown in Table 3 above.
  • the PCF device 214 updates the NSSP rules related to the second S-NSSAI to be associated with the first S-NSSAI (eg, S-NSSAI 2).
  • the PCF device 214 when the PCF device 214 generates the first NSSP of the terminal device 202, a flag is added to the modified NSSP rule to indicate that the first S-NSSAI corresponding to the NSSP rule is modified by the core network to be the second S-NSSAI.
  • the NSSP rules modified to be associated with the second S-NSSAI are distinguished from the NSSP rules associated with the second S-NSSAI. Then, after receiving the request message carrying the indication information in step 507, the PCF device 214 learns to update the second S-NSSAI included in the previously modified NSSP rule to the first S-NSSAI.
  • the PCF device 214 can determine that the NSSP rule 1 and the NSSP rule 2 are previously modified NSSP rules according to the flag bits in Table 3, and then the second S-NSSAI included in the NSSP rule 1 and the NSSP rule 2 (ie, S -NSSAI 3) Updated to the first S-NSSAI (ie, S-NSSAI 2).
  • S-NSSAI 3 also contains the second S-NSSAI (ie, S-NSSAI 3), since the NSSP Rule 3 does not contain the flag bit, there is no need to modify the second S-NSSAI.
  • the updated NSSP is a second NSSP, including an association between the application and the first S-NSSAI.
  • the second NSSP is as shown in Table 2 above.
  • the PCF device 214 sends a response message to the third AMF entity.
  • the response message carries a second NSSP.
  • Step 508 The third AMF entity sends a registration accept message to the terminal device 202 through the access network device 204.
  • the registration accept message includes a second NSSP and a second allowed NSSAI.
  • the third AMF entity determines the second permission according to the NSSAI (ie, the first allowed NSSAI) of the request carried by the terminal device 202 in the registration request message, the subscription information of the terminal device 202, and the slice type supported by the third AMF entity.
  • NSSAI ie, the first allowed NSSAI
  • the second allowed NSSAI includes the first S-NSSAI described above.
  • the second allowed NSSAI further includes a second S-NSSAI.
  • S-NSSAI 2 is the first S-NSSAI
  • S-NSSAI 3 is the second S-NSSAI.
  • the second allowed NSSAI includes S-NSSAI 2, 3, 4.
  • the registration accept message also includes a temporary identifier assigned by the third AMF entity to the terminal device 202.
  • the temporary identification includes 5G-GUTI.
  • the 5G-GUTI at this time is a new temporary identifier.
  • the new temporary identifier of the terminal device 202 includes a first field for identifying a third AMF entity (eg, identification information of the third AMF), and a second identifier for uniquely identifying the terminal device 202 within the third AMF entity. Field.
  • step 509 the terminal device 202 stores the second NSSP. In addition, the terminal device 202 also updates the second allowed NSSAI.
  • the terminal device 202 initiates a session establishment process by selecting a corresponding S-NSSAI for the application according to the second NSSP association application and the S-NSSAI. For example, for the data transmission initiated by the application A, the terminal device 202 selects the S-NSSAI 2 according to the NSSP rule 1 in the second NSSP, and sends a session establishment request message carrying the S-NSSAI 2 to the core network, and the session establishment process is continued by the core network. .
  • the second AMF entity selected by the access network device 204 requests the context of the terminal device 202 from the first AMF entity before the mobile, thereby knowing that the second AMF entity is not
  • the most suitable AMF entity redirects the terminal device 202 to a third AMF entity supporting the first S-NSSAI and the second S-NSSAI, and the "most suitable" third AMF entity provides service to the terminal device 202.
  • the service corresponding to the first S-NSSAI can still be implemented in the second PLMN after the terminal device 202 moves.
  • the third AMF entity acquires the context containing the indication information, and sends the indication information to the PCF device and requests the PCF device to update the NSSP related to the second S-NSSAI.
  • the updated NSSP is restored to the "real" content.
  • the terminal device 202 can associate the application with the S-NSSAI according to the updated NSSP, thereby obtaining a complete service. Thereby, the service corresponding to the NSSAI requested by the terminal device 202 can be satisfied, and the service experience of the user is improved.
  • FIG. 6 illustrates a slice selection method in accordance with an embodiment of the present invention.
  • the method can be performed by a first access and mobility management function entity (e.g., the first AMF entity described above).
  • Figure 6 will be described in conjunction with Figures 3 through 5.
  • the method includes:
  • Step 602 The first access and mobility management function entity receives a registration request message from a terminal device (for example, the foregoing terminal device 202), where the registration request message includes an NSSAI corresponding to the slice that the terminal device requests to access.
  • the NSSAI corresponding to the slice requesting access includes at least a first S-NSSAI (for example, the above S-NSSAI 2), wherein the first S-NSSAI is an S-NSSAI that is not supported by the first access and mobility management function entity.
  • step 602 can refer to the description of step 301 in FIG.
  • Step 604 The first access and mobility management function entity acquires the attribute information of the first S-NSSAI, and provides the terminal device with the slice corresponding to the second S-NSSAI (for example, the foregoing S-NSSAI 3) according to the attribute information.
  • step 604 can refer to the description of steps 302 and 303 in FIG.
  • Step 606 The first access and mobility management function entity acquires an NSSP (for example, the first NSSP described above), and the NSSP includes an association between the application and the second S-NSSAI.
  • an NSSP for example, the first NSSP described above
  • step 606 can refer to the description of step 306 in FIG.
  • Step 608 The first access and mobility management function entity sends a registration accept message to the terminal device, where the registration accept message includes the NSSAI and the NSSP corresponding to the slice that the terminal device allows to access, and the NSSAI corresponding to the slice that is allowed to access includes the second S. -NSSAI.
  • step 606 can refer to the description of step 307 in FIG.
  • the first AMF entity obtains the attribute information.
  • the first S-NSSAI is used to provide the first device to the terminal device according to the attribute information. S-NSSAI corresponding business. Therefore, the service corresponding to the first S-NSSAI that is not supported is not discarded, but is provided by the slice corresponding to the second S-NSSAI.
  • the NSSP rule in the NSSP acquired by the first access and mobility management function entity is associated with the second S-NSSAI.
  • the terminal device can be aware that the service corresponding to the first S-NSSAI is provided by the slice corresponding to the second S-NSSAI. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the method further includes: the first access and mobility management function entity adds indication information in the context of the terminal device, where the indication information is used to indicate that the first access and mobility management function entity uses the second S-NSSAI
  • the corresponding slice provides the terminal device with the service corresponding to the first S-NSSAI (for example, refer to the description of step 304 in FIG. 3). Therefore, through the delivery of the context, the other access and mobility management function entities can obtain the foregoing indication information, thereby determining whether the access and mobility management function entity is suitable for the terminal device, thereby improving the user's service experience.
  • step 604 includes: the first access and mobility management function entity acquires the first S-NSSAI from the user data management device (for example, the UDM device 212) or the policy control function device (for example, the PCF device 214). Attribute information (for example, reference may be made to the description of steps 302a, 302b in FIG. 3).
  • the step 606 includes: the first access and mobility management function entity sends the foregoing indication information to the policy control function device (for example, the PCF device 214), requesting the policy control function device to update the NSSP related to the first S-NSSAI.
  • the indication information is used to indicate that the first access and mobility management function entity uses the slice corresponding to the second S-NSSAI to provide the service corresponding to the first S-NSSAI for the terminal device; the first access and mobility management function entity
  • the policy control function device receives the NSSP (for example, reference may be made to the description of step 305 in FIG. 3).
  • the method further includes: the first access and mobility management function entity receives a request message from the second access and mobility management function entity (for example, the foregoing second AMF entity) to request a context of the terminal device;
  • the first access and mobility management function entity sends the context of the terminal device to the second access and mobility management function entity, the context including the indication information (for example, reference may be made to the description of step 504 in FIG. 5). Therefore, according to the solution of the present application, after the terminal device moves, the second AMF entity requests the context of the terminal device from the first AMF entity before the mobile, so that the second AMF entity is not the most suitable AMF entity, and the terminal device is heavy.
  • the "most suitable" third AMF entity provides services to the terminal device.
  • the service corresponding to the first S-NSSAI can still be implemented in the second PLMN after the terminal device moves. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • FIG. 7 illustrates a slice selection method in accordance with an embodiment of the present invention.
  • the method can be performed by a second access and mobility management function entity (e.g., the second AMF entity described above).
  • Figure 7 will be described in conjunction with Figure 5.
  • the method includes:
  • Step 702 The second access and mobility management function entity receives a registration request message, where the registration request message includes an NSSAI corresponding to the slice that the terminal device is allowed to access and a temporary identifier of the terminal device (for example, the foregoing temporary temporary identifier), and the access request message is allowed.
  • the NSSAI corresponding to the incoming slice includes a second S-NSSAI (eg, S-NSSAI 3 described above).
  • step 702 can refer to the description of step 503 in FIG.
  • Step 704 The second access and mobility management function entity acquires a context of the terminal device from the first access and mobility management function entity (for example, the foregoing first AMF entity) according to the temporary identifier, where the context includes indication information.
  • the indication information is used to indicate that the first access and mobility management function entity uses the slice corresponding to the second S-NSSAI to provide the terminal device with the service corresponding to the first S-NSSAI (for example, the foregoing S-NSSAI 2).
  • step 704 can refer to the description of step 504 in FIG.
  • Step 706 If the second access and mobility management function entity does not support the first S-NSSAI, the second access and mobility management function entity redirects the terminal device to the third access and the first S-NSSAI.
  • a mobility management functional entity eg, the third AMF entity described above.
  • step 706 can refer to the description of step 505 in FIG.
  • the second AMF entity requests the context of the terminal device from the first AMF entity before the mobile, so as to know that the second AMF entity is not the most suitable AMF entity, if the terminal device currently accesses the PLMN If there are other access and mobility management function entities (such as the third AMF entity) that can support the first S-NSSAI in the network, the terminal device is redirected to the third AMF entity supporting the first S-NSSAI, A suitable "third AMF entity" provides services to the terminal device.
  • the first AMF entity in the first PLMN does not support the first S-NSSAI
  • the service corresponding to the first S-NSSAI can still be implemented in the second PLMN after the terminal device moves. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the method further includes: the second access and mobility management function entity sends the context of the terminal device to the third access and mobility management function entity, where the context includes the indication information (for example, refer to FIG. 5 Description of step 506). Therefore, the third access and mobility management function entity receiving the indication information can send the indication information to the PCF device and request the PCF device to update the NSSP related to the second S-NSSAI. Thus, the updated NSSP is restored to the "real" content. Subsequently, the terminal device can obtain the complete service according to the updated NSSP association application and the S-NSSAI. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the third access and mobility management function entity sends the context of the terminal device to the third access and mobility management function entity, where the context includes the indication information (for example, refer to FIG. 5 Description of step 506). Therefore, the third access and mobility management function entity receiving the indication information can send the indication information to the PCF device and request the PC
  • FIG. 8 illustrates a slice selection method in accordance with an embodiment of the present invention.
  • the method can be performed by a third access and mobility management function entity (e.g., the third AMF entity described above).
  • Figure 8 will be described in conjunction with Figure 5.
  • the method includes:
  • Step 802 The third access and mobility management function entity acquires a context of the terminal device, where the context includes indication information.
  • the indication information is used to indicate that the first access and mobility management function entity (for example, the first AMF entity described above) provides the first terminal device with the slice corresponding to the second S-NSSAI (for example, the S-NSSAI 3) The service corresponding to S-NSSAI (for example, the above S-NSSAI 2).
  • step 802 can refer to the description of step 506 in FIG.
  • Step 804 The third access and mobility management function entity sends indication information to the policy control function device (for example, the PCF device 214), and requests the policy control function device to update the NSSP related to the second S-NSSAI.
  • the updated NSSP (eg, the second NSSP described above) includes an association between the application and the first S-NSSAI.
  • step 804 can refer to the description of steps 506 and 507 in FIG.
  • Step 806 The third access and mobility management function entity receives the updated NSSP from the policy control function device.
  • step 806 can refer to the description of step 507 in FIG.
  • the terminal device is served by the "most suitable" third AMF entity.
  • the third AMF entity acquires the context containing the indication information, and sends the indication information to the PCF device and requests the PCF device to update the NSSP related to the second S-NSSAI.
  • the updated NSSP is restored to the "real" content.
  • the terminal device can obtain the complete service according to the updated NSSP association application and the S-NSSAI. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • FIG. 9 illustrates a slice selection method in accordance with an embodiment of the present invention.
  • the method can be performed by a policy control function device (e.g., PCF device 214 described above).
  • Figure 9 will be described in conjunction with Figures 3 through 5.
  • the method includes:
  • Step 902 The policy control function device receives the indication information from the first access and mobility management function entity (for example, the first AMF entity).
  • the indication information is used to indicate that the first access and mobility management function entity uses the slice corresponding to the second S-NSSAI (for example, the S-NSSAI 3) to provide the first S-NSSAI to the terminal device (for example, the foregoing S-NSSAI 2) ) Corresponding business.
  • step 902 can refer to the description of step 305 in FIG.
  • Step 904 The policy control function device updates the NSSP related to the first S-NSSAI according to the indication information, and sends the updated first NSSP to the first access and mobility management function entity.
  • the updated first NSSP (eg, the first NSSP described above) includes an association between the application and the second S-NSSAI.
  • step 904 can refer to the description of step 306 in FIG.
  • the PCF device when the first AMF entity does not support the first S-NSSAI and uses the slice corresponding to the second S-NSSAI to provide the first S-NSSAI corresponding service for the terminal device, the PCF device will involve the first S- The NSSP of the NSSAI is updated such that the updated NSSP includes an association between the application and the second S-NSSAI. Therefore, the service corresponding to the first S-NSSAI that is not supported is not discarded, but is provided by the slice corresponding to the second S-NSSAI.
  • the terminal device can sense that the service corresponding to the first S-NSSAI is replaced by the slice corresponding to the second S-NSSAI. The services corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the method further includes: the policy control function device receives the indication information from a third access and mobility management function entity (for example, the third AMF entity, where the policy control function device updates the involved device according to the indication information.
  • the second NSSP of the second S-NSSAI, the updated second NSSP (for example, the second NSSP described above) includes an association between the application and the first S-NSSAI; and the policy control function device to the third access and mobility management function The entity sends the updated second NSSP.
  • the terminal device when the terminal device moves, the terminal device is served by the "most appropriate" third AMF entity.
  • the third AMF entity sends the indication information to the PCF device and requests the PCF device to update the NSSP related to the second S-NSSAI.
  • the updated NSSP is restored to the "real" content.
  • the terminal device can obtain the complete service according to the updated NSSP association application and the S-NSSAI. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the present application also provides another slice selection method.
  • the method can be performed by a terminal device (e.g., terminal device 202 described above). As shown in FIG. 10, the method includes:
  • Step 1001 The terminal device determines, according to the NSSP, whether the current location of the terminal device is within the service area of the first slice corresponding to the first S-NSSAI.
  • the NSSP includes an association between the first S-NSSAI and a service area of the first slice.
  • the NSSP stored in the terminal device adds one dimension to the NSSP in the prior art: a serving area of the slice corresponding to the S-NSSAI.
  • the NSSP includes one or more NSSP rules, and each NSSP rule associates the application, the S-NSSAI, and the service area of the slice corresponding to the S-NSSAI.
  • the service area may be a certain location area. For example, a location area may be identified by a tracking area list (TA list).
  • the service area may also be an area covered by the entire network (for example, all PLMNs, all PLMNs). The whole network coverage means that no matter where the terminal device is located, it is located within the service area of the slice corresponding to the S-NSSAI.
  • the NSSP stored in the terminal device is as shown in Table 4:
  • NSSP Rule 1 Application A S-NSSAI-2 Service area 2 NSSP Rule 2 Application B S-NSSAI-2 Service area 2 NSSP Rule 3 Application C S-NSSAI-3 Service area 2, 3 NSSP Rule 4 Application D S-NSSAI-4 Service area 2, 3
  • the first S-NSSAI is the S-NSSAI included in the NSSAI that the terminal device wants to request.
  • the terminal device Before transmitting the registration request message, the terminal device first determines, according to the NSSP, whether the current location of the terminal device is within the service area of the first slice corresponding to the first S-NSSAI.
  • the NSSAI that the terminal device wants to request includes S-NSSAI 2, 3, 4, and the current location of the terminal device is within the service area 3.
  • the terminal device knows that the terminal device is within the service area of the S-NSSAI 3, 4, but not within the service area of the S-NSSAI 2, according to the NSSP of Table 4. Therefore, the terminal device 202 requests only the service corresponding to the S-NSSAI 3, 4 from the network, and does not request the service corresponding to the S-NSSAI 2 from the network.
  • the terminal device may further determine, according to the NSSP, whether a slice corresponding to the S-NSSAI is deployed in the PLMN where the terminal device is currently located. If the slice corresponding to the S-NSSAI is deployed in the current PLMN, it is determined whether the current location of the terminal device is located in the service area of the slice. For example, the NSSAI that the terminal device wants to request also includes S-NSSAI 5. As can be seen from Table 4, since the slice corresponding to the S-NSSAI 5 is not deployed in the PLMN, the terminal device does not request the service corresponding to the S-NSSAI 5 from the network.
  • the current location of the terminal device is located in the service area of the first slice, it indicates that the first slice corresponding to the first S-NSSAI is deployed in the PLMN where the terminal device is currently located.
  • Step 1002 When the current location of the terminal device is in the service area of the first slice, the terminal device sends a registration request message.
  • the registration request message carries the first S-NSSAI.
  • the first S-NSSAI is used to select the first slice.
  • the terminal device is within the service area of the S-NSSAI 3, 4, but not within the service area of the S-NSSAI 2. Therefore, the NSSAI in the registration request message includes S-NSSAI 3, 4, excluding S-NSSAI 2. That is, the first S-NSSAI is S-NSSAI 3 or 4.
  • the access network device in the service area 3 selects the AMF entity i supporting S-NSSAI3, 4 in the area. Thereafter, the other steps in the registration process are continued until the registration process ends, and the present invention is not described herein.
  • the slice selection method of the embodiment of the present application before the terminal device initiates the registration request, it is determined whether the current location of the terminal device is within the service area of the slice corresponding to the first S-NSSAI in the requested NSSAI.
  • the first S-NSSAI is included in the NSSAI of the registration request message only when the current location of the terminal device is within the service area. Therefore, the core network is prevented from rejecting the registration request of the terminal device because the S-NSSAI requested by the terminal device cannot be supported, thereby saving signaling interaction between the terminal device and the core network.
  • the terminal device may initiate a periodic registration request. Before transmitting the registration request message, the terminal device still determines, by step 1003, whether the current location of the terminal device is within the service area of the slice corresponding to each S-NSSAI.
  • the terminal device Before transmitting the registration request message, the terminal device learns that the terminal device is within the service area of the S-NSSAI 2, 3, 4 according to the NSSP of Table 4. Therefore, in step 1004, the terminal device 202 sends a registration request message to the network requesting the service corresponding to the S-NSSAI 2, 3, 4. After receiving the registration request message, the access network device in the service area 3 cannot connect to the AMF entity i that was previously serving the terminal device, and then selects the S-NSSAI in the area according to the requested S-NSSAI 2, 3, and 4. 2, 3, 4 AMF entities ii. Thereafter, the other steps in the registration process are continued until the registration process ends, and the present invention is not described herein.
  • the terminal device determines, according to the NSSP, whether the current location of the terminal device is in the service area of the first slice corresponding to the first S-NSSAI, and the terminal device periodically determines the current status of the terminal device. Whether the base station corresponding to the location is within the service area of the first slice. Therefore, if the location of the terminal device in the first time is not in the service area of the slice corresponding to the first S-NSSAI in the requested NSSAI, the terminal device determines, in the subsequent second time, the location of the terminal device in the requested NSSAI. Within the service area of the slice corresponding to the S-NSSAI, a new registration request can still be initiated to obtain the corresponding service.
  • each network element such as the above-mentioned session management function entity, etc.
  • each network element includes hardware structures and/or software modules corresponding to the execution of the respective functions.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the access and mobility management function entity may include a receiving module 1101, a processing module 1102, and a transmitting module 1103, as shown in FIG. 11A.
  • the access and mobility management function entity can be used to perform the operations of the first access and mobility management function entity (e.g., the first AMF entity) of Figures 3, 5, and 6 above.
  • the first access and mobility management function entity e.g., the first AMF entity
  • the receiving module 1101 is configured to receive a registration request message from the terminal device, where the registration request message includes an NSSAI corresponding to the slice that the terminal device requests to access, and the NSSAI corresponding to the slice that is requested to access includes at least the first single S-NSSAI.
  • the first S-NSSAI is an S-NSSAI that is not supported by the first access and mobility management function entity, and is used to obtain attribute information of the first S-NSSAI.
  • the processing module 1102 is configured to use the slice corresponding to the second S-NSSAI to provide the terminal device with the service corresponding to the first S-NSSAI according to the attribute information.
  • the receiving module 1101 is further configured to acquire a network slice selection policy NSSP, where the NSSP includes an association between the application and the second S-NSSAI.
  • the sending module 1103 is configured to send a registration accept message to the terminal device, where the registration accept message includes an NSSAI corresponding to a slice that the terminal device is allowed to access, and the NSSP, where the NSSAI corresponding to the slice that is allowed to access includes the Said second S-NSSAI.
  • the service corresponding to the first S-NSSAI that is not supported is not discarded, but is provided by the slice corresponding to the second S-NSSAI.
  • the services corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the processing module 1102 is further configured to add indication information in a context of the terminal device, where the indication information is used to indicate that the first access and mobility management function entity uses the second S-NSSAI corresponding
  • the slice provides the terminal device with the service corresponding to the first S-NSSAI.
  • the receiving module 1101 is configured to acquire the attribute information of the first S-NSSAI from the user data management device or the policy control function device.
  • the sending module 1103 is further configured to send the indication information to the policy control function device, requesting the policy control function device to update the NSSP related to the first S-NSSAI, where the indication information is used to indicate the An access and mobility management function entity uses the slice corresponding to the second S-NSSAI to provide the terminal device with the service corresponding to the first S-NSSAI; and the receiving module 1101 is configured to receive from the policy control function device.
  • the NSSP is further configured to send the indication information to the policy control function device, requesting the policy control function device to update the NSSP related to the first S-NSSAI, where the indication information is used to indicate the An access and mobility management function entity uses the slice corresponding to the second S-NSSAI to provide the terminal device with the service corresponding to the first S-NSSAI; and the receiving module 1101 is configured to receive from the policy control function device.
  • the NSSP is further configured to send the indication information to the policy control function device, requesting the policy control function device to update the NSSP related to the
  • the receiving module 1101 is further configured to receive a request message from the second access and mobility management function entity to request a context of the terminal device; the sending module 1103 is further configured to use the second access and mobility The management function entity sends a context of the terminal device, the context including the indication information.
  • the receiving module 1101, the processing module 1102, and the sending module 1103 in the first access and mobility management function entity may further implement other operations or functions of the first AMF entity in the foregoing method, and details are not described herein.
  • the access and mobility management function entity can be used to perform the operations of the second access and mobility management function entity (e.g., the second AMF entity) of Figures 5 and 7 above.
  • the second access and mobility management function entity e.g., the second AMF entity
  • the receiving module 1101 is configured to receive a registration request message, where the registration request message includes a network slice selection assistance information NSSAI corresponding to a slice that the terminal device is allowed to access, and a temporary identifier of the terminal device, and the NSSAI corresponding to the slice that is allowed to be accessed Include a second single network slice selection assistance information S-NSSAI; configured to acquire, according to the temporary identifier, a context of the terminal device from a first access and mobility management function entity, where the context includes indication information, the indication The information is used to indicate that the first access and mobility management function entity uses the slice corresponding to the second S-NSSAI to provide the terminal device with the service corresponding to the first S-NSSAI. If the second access and mobility management function entity does not support the first S-NSSAI, the processing module 1102 is configured to redirect the terminal device to a third access and support the first S-NSSAI. Mobility management functional entity.
  • the second AMF entity requests the context of the terminal device from the first AMF entity before the mobile, so as to know that the second AMF entity is not the most suitable AMF entity, if other terminals exist in the PLMN network currently accessed by the terminal device.
  • the access and mobility management function entity (eg, the third AMF entity) of the first S-NSSAI may be supported, and the terminal device is redirected to the third AMF entity supporting the first S-NSSAI, by "the most suitable"
  • the third AMF entity provides services for the terminal device.
  • the service corresponding to the first S-NSSAI can still be implemented in the second PLMN after the terminal device moves. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the sending module 1103 is configured to send, to the third access and mobility management function entity, a context of the terminal device, where the context includes the indication information.
  • the receiving module 1101, the processing module 1102, and the sending module 1103 in the second access and mobility management function entity may further implement other operations or functions of the second AMF entity in the foregoing method, and details are not described herein.
  • the access and mobility management function entity can be used to perform the operations of the third access and mobility management function entity (e.g., the third AMF entity) of Figures 5 and 8 above.
  • the third access and mobility management function entity e.g., the third AMF entity
  • the receiving module 1101 is configured to acquire a context of the terminal device, where the context includes indication information, where the indication information is used to indicate that the first access and mobility management function entity uses the slice corresponding to the second single network slice selection auxiliary information S-NSSAI. Providing, for the terminal device, a service corresponding to the first S-NSSAI.
  • the sending module 1103 is configured to send the indication information to the policy control function device, requesting the policy control function device to update a network slice selection policy NSSP related to the second S-NSSAI, where the updated NSSP includes an application and the first The association between S-NSSAI.
  • the receiving module 1101 is further configured to receive the updated NSSP from the policy control function device.
  • the terminal device when the terminal device moves, the terminal device is served by the "most appropriate" third AMF entity.
  • the third AMF entity acquires the context containing the indication information, and sends the indication information to the PCF device and requests the PCF device to update the NSSP related to the second S-NSSAI.
  • the updated NSSP is restored to the "real" content.
  • the terminal device can obtain the complete service according to the updated NSSP association application and the S-NSSAI. Therefore, the service corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the receiving module 1101, the processing module 1102, and the sending module 1103 in the third access and mobility management function entity may further implement other operations or functions of the third AMF entity in the foregoing method, and details are not described herein.
  • FIG. 11B is a schematic diagram showing another possible structure of the access and mobility management function entity involved in the above embodiment.
  • the access and mobility management functional entity includes a transceiver 1104 and a processor 1105, as shown in Figure 11B.
  • the processor 1105 is configured to process the access and mobility management function entity to perform the corresponding function of the first AMF entity, the second AMF entity, or the third AMF entity in the above method.
  • the transceiver 1104 is configured to implement communication between the first AMF entity, the second AMF entity, or the third AMF entity and other access and mobility management function entities/policy control function devices/user data management devices/access network devices .
  • the access and mobility management functional entity may also include a memory 1106 for coupling with a processor that holds program instructions and data necessary for the access and mobility management function entities.
  • the policy control function device may include a receiving module 1201, a processing module 1202, and a transmitting module 1203, as shown in FIG. 12A.
  • the policy control function device can be used to perform the operations of the policy control function device (eg, PCF device 214) in FIGS. 3, 5, and 9 above.
  • PCF device 21 e.g, PCF device 214
  • the receiving module 1201 is configured to receive indication information from the first access and mobility management function entity, where the indication information is used to indicate that the first access and mobility management function entity uses the second single network slice selection auxiliary information S-
  • the slice corresponding to the NSSAI provides the terminal device with the service corresponding to the first S-NSSAI.
  • the processing module 1202 is configured to update, according to the indication information, a network slice selection policy NSSP related to the first S-NSSAI, where the updated first NSSP includes an association between the application and the second S-NSSAI.
  • the sending module 1203 is configured to send the updated first NSSP to the first access and mobility management function entity.
  • the PCF device will involve the NSSP of the first S-NSSAI.
  • the update is made such that the updated NSSP includes an association between the application and the second S-NSSAI. Therefore, the service corresponding to the first S-NSSAI that is not supported is not discarded, but is provided by the slice corresponding to the second S-NSSAI.
  • the terminal device can sense that the service corresponding to the first S-NSSAI is replaced by the slice corresponding to the second S-NSSAI. The services corresponding to the NSSAI requested by the terminal device can be satisfied, and the service experience of the user is improved.
  • the receiving module 1201 is further configured to receive the indication information from the third access and mobility management function entity; the processing module 1202 is further configured to: update the NSSP related to the second S-NSSAI according to the indication information.
  • the updated second NSSP includes an association between the application and the first S-NSSAI; the sending module 1203 is further configured to send the updated second NSSP to the third access and mobility management function entity. .
  • the receiving module 1201, the processing module 1202, and the sending module 1203 in the policy control function device may also implement other operations or functions of the PCF device 214 in the foregoing method, and details are not described herein again.
  • FIG. 12B is a schematic diagram showing another possible structure of the policy control function device involved in the above embodiment.
  • the policy control function device includes a transceiver 1204 and a processor 1205 as shown in FIG. 12B.
  • the processor 1205 is configured to process the policy control function device to perform the corresponding functions of the PCF device 214 in the above method.
  • the transceiver 1204 is configured to implement communication between the PCF device 214 and the first AMF entity or the third AMF entity.
  • the policy control function device can also include a memory 1206 for coupling with the processor that holds the program instructions and data necessary for the policy control function device.
  • the terminal device may include a processing module 1302 and a transmitting module 1303, as shown in FIG. 13A.
  • the terminal device can be used to perform the operations of the terminal device (e.g., terminal device 202) in FIG. 10 described above.
  • the terminal device e.g., terminal device 202
  • the processing module 1302 is configured to determine, according to the network slice selection policy NSSP, whether the current location of the terminal device is in a service area of the first slice corresponding to the first single network slice selection auxiliary information S-NSSAI, where the NSSP includes An association between the first S-NSSAI and a service area of the first slice.
  • the sending module 1303 is configured to send a registration request message, where the registration request message carries the first S-NSSAI, the first S- NSSAI is used to select the first slice.
  • the terminal device initiates the registration request, it is determined whether the current location of the terminal device is within the service area of the slice corresponding to the first S-NSSAI in the requested NSSAI.
  • the first S-NSSAI is included in the NSSAI of the registration request message only when the current location of the terminal device is within the service area. Therefore, the core network is prevented from rejecting the registration request of the terminal device because the S-NSSAI requested by the terminal device cannot be supported, thereby saving signaling interaction between the terminal device and the core network.
  • the processing module 1302 is configured to periodically determine whether the base station corresponding to the current location of the terminal device is in a service area of the first slice.
  • the terminal device may further include a receiving module 1301.
  • the receiving module 1301, the processing module 1302, and the sending module 1303 in the terminal device may also implement other operations or functions of the terminal device 202 in the foregoing method, and details are not described herein again.
  • FIG. 13B is a schematic diagram showing another possible structure of the terminal device involved in the above embodiment.
  • the terminal device includes a transceiver 1304 and a processor 1305 as shown in FIG. 13B.
  • the processor 1305 is configured to process the terminal device 202 to perform the corresponding functions of the terminal device 202 in the above method.
  • the transceiver 1304 is configured to implement communication between the terminal device 202 and the access and mobility management function entity/access network device.
  • the terminal device may also include a memory 1306 for coupling with a processor that stores program instructions and data necessary for the terminal device.
  • FIGS 11B, 12B, and 13B only show a simplified design of the above apparatus.
  • each of the above devices may include any number of transmitters, receivers, processors, controllers, memories, communication units, etc., and all devices that can implement the present application are within the scope of the present application.
  • the controller/processor for performing the above-described session management function entity of the present application may be a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and a field programmable gate array. (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware or may be implemented by a processor executing software instructions.
  • the software instructions may be comprised of corresponding software modules that may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage well known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in a session management functional entity.
  • the processor and the storage medium can also exist as discrete components in the session management function entity.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Landscapes

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

Abstract

La présente invention se rapporte au domaine de la communication sans fil et concerne un procédé de sélection de tranche. Le procédé comprend : la réception, par une première entité de fonction de gestion d'accès et de mobilité, en provenance d'un dispositif terminal, d'un message de demande d'enregistrement comprenant des NSSAI demandées, les NSSAI demandées comprenant au moins des premières S-NSSAI non prises en charge par la première entité de fonction de gestion d'accès et de mobilité ; l'obtention d'informations d'attribut des premières S-NSSAI, et l'utilisation, en fonction des informations d'attribut, d'une tranche correspondant à des secondes S-NSSAI pour fournir un service correspondant aux premières S-NSSAI pour le dispositif terminal ; l'obtention d'un NSSP comprenant une association entre une application et les secondes S-NSSAI ; et l'envoi d'un message d'acceptation d'enregistrement au dispositif terminal, le message d'acceptation d'enregistrement comprenant des NSSAI autorisées et un NSSP du dispositif terminal, les NSSAI autorisées comprenant les secondes S-NSSAI. Grâce à la solution du mode de réalisation de l'invention, un service correspondant à des premières S-NSSAI non prises en charge n'est pas abandonné, et est au contraire fourni par une tranche correspondant à des secondes S-NSSAI. L'invention fournit tous les services correspondant à des NSSAI demandées par un dispositif terminal, ce qui permet d'améliorer l'expérience de service d'un utilisateur.
PCT/CN2018/088889 2017-06-29 2018-05-29 Procédé et appareil de sélection de tranche WO2019001204A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710530394.5 2017-06-29
CN201710530394.5A CN109219111B (zh) 2017-06-29 2017-06-29 切片选择方法和装置

Publications (1)

Publication Number Publication Date
WO2019001204A1 true WO2019001204A1 (fr) 2019-01-03

Family

ID=64740335

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/088889 WO2019001204A1 (fr) 2017-06-29 2018-05-29 Procédé et appareil de sélection de tranche

Country Status (2)

Country Link
CN (1) CN109219111B (fr)
WO (1) WO2019001204A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021149958A1 (fr) 2020-01-22 2021-07-29 Samsung Electronics Co., Ltd. Procédé de configuration de session et de transfert intercellulaire, et dispositif associé

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200091308A (ko) * 2019-01-22 2020-07-30 삼성전자주식회사 무선 통신 시스템에서 네트워크 슬라이스의 인터워킹을 제공하기 위한 장치 및 방법
CN110225563B (zh) * 2019-01-31 2020-11-10 华为技术有限公司 网络注册的方法及设备
CN111586668B (zh) * 2019-02-15 2022-04-12 华为技术有限公司 发送终端策略的方法、装置和系统
CN111586667B (zh) * 2019-02-15 2022-01-14 华为技术有限公司 通信方法及终端设备、核心网设备
WO2020164425A1 (fr) 2019-02-15 2020-08-20 华为技术有限公司 Procédé, dispositif et système de transmission de politique de terminal
CN111586690B (zh) * 2019-02-18 2023-11-07 华为技术有限公司 一种通信方法及装置
CN111586772B (zh) * 2019-02-18 2021-06-22 华为技术有限公司 一种通信方法及装置
CN111654862B (zh) * 2019-03-04 2021-12-03 华为技术有限公司 终端设备的注册方法及装置
CN111770558A (zh) * 2019-04-02 2020-10-13 中国移动通信有限公司研究院 一种切片接入方法、终端及网络设备
CN111866989A (zh) * 2019-04-28 2020-10-30 华为技术有限公司 通信方法、装置及系统
CN112118120B (zh) * 2019-06-20 2023-04-07 中国电信股份有限公司 切片签约方法、系统和计算机可读存储介质
CN112152926B (zh) * 2019-06-28 2022-03-04 华为技术有限公司 一种管理应用的网络切片的方法及装置
EP4055918A4 (fr) * 2019-11-08 2022-11-09 ZTE Corporation Procédés et dispositifs pour protéger la confidentialité d'informations d'identité de tranche
CN112825571A (zh) * 2019-11-21 2021-05-21 中兴通讯股份有限公司 网络功能管理、注册、请求方法、装置、网元及介质
WO2021159523A1 (fr) * 2020-02-14 2021-08-19 华为技术有限公司 Procédé, appareil et système de communication
CN113271217B (zh) * 2020-02-17 2022-09-16 华为技术有限公司 通信方法、装置及系统
CN114143303A (zh) * 2020-09-03 2022-03-04 中国移动通信有限公司研究院 一种终端通信方法、终端及计算机可读存储介质
CN114513799A (zh) * 2020-11-17 2022-05-17 中国移动通信有限公司研究院 一种策略通知方法、设备及存储介质
CN112492694B (zh) * 2020-12-15 2023-11-28 中国联合网络通信集团有限公司 双卡终端的切片管理方法、管理单元、终端设备及介质
CN113472853B (zh) * 2021-06-03 2023-04-18 中国联合网络通信集团有限公司 应用程序网络分片选择方法、应用服务器及udr
CN113411781B (zh) * 2021-06-25 2022-08-05 Oppo广东移动通信有限公司 网络切片服务的请求方法、装置、终端及存储介质
WO2023272737A1 (fr) * 2021-07-02 2023-01-05 Oppo广东移动通信有限公司 Procédé d'accès, dispositif terminal, élément réseau de gestion unifiée des données et premier élément réseau
CN115604696A (zh) * 2021-07-07 2023-01-13 华为技术有限公司（Cn） 执行在线签约的方法和装置

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
HUAWEI; HISILICON: "On Multiple Network Slice instances", SA WG2 MEETING #122, no. S2-174334, San Jose Del Cabo, Mexico, XP051309412 *
MOTOROLA MOBILITY; LENOVO: "Application Function influence on slice selection", SA WG2 MEETING #122, no. S2-174262, 20 June 2017 (2017-06-20), San Jose Del Cabo, Mexico, XP051309342 *
NOKIA; ALCATEL-LUCENT SHANGHAI BELL: "Slice assistance Information over RRC", 3GPP TSG-RAN WG2 NR ADHOC#2, no. R2-1706984, 17 June 2017 (2017-06-17), Qingdao, China, XP051307238 *
QUALCOMM INCORPORATED: "TS 23.501 - Proposal for co-existence of network slices stemming from offline discussion", SA WG2 MEETING #122, no. S2-174442, 20 June 2017 (2017-06-20), San Jose Del Cabo, Mexico, pages 1,2,8,9, XP051309502 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021149958A1 (fr) 2020-01-22 2021-07-29 Samsung Electronics Co., Ltd. Procédé de configuration de session et de transfert intercellulaire, et dispositif associé
EP4079084A4 (fr) * 2020-01-22 2023-06-21 Samsung Electronics Co., Ltd. Procédé de configuration de session et de transfert intercellulaire, et dispositif associé

Also Published As

Publication number Publication date
CN109219111A (zh) 2019-01-15
CN109219111B (zh) 2020-09-04

Similar Documents

Publication Publication Date Title
WO2019001204A1 (fr) Procédé et appareil de sélection de tranche
USRE49729E1 (en) Session information management method and apparatus
US11026080B2 (en) Policy control function determining method, apparatus, and system
WO2019114684A1 (fr) Acquisition de politique d'utilisateur
JP6855575B2 (ja) ネットワーク間変更方法および装置、ならびに関連デバイス
WO2018006784A1 (fr) Procédé, appareil, et système de sélection de tranche de réseau
KR102313165B1 (ko) 데이터 송신 방법, 디바이스 및 시스템
WO2019174505A1 (fr) Procédé et appareil de communication basés sur une tranche de réseau
WO2019157942A1 (fr) Procédé de communication, et appareil de communication
JP2020504566A (ja) 移動通信システムでアクセス及び移動性管理機能を選択するための方法及び装置
KR20210127827A (ko) 데이터 전송 방법, 장치, 및 시스템
JP2020516165A (ja) セッション管理機能選択のための方法および装置
JP7485793B2 (ja) スライスアクセス方法、装置、及びシステム
WO2023280121A1 (fr) Procédé et appareil d'obtention de service de périphérie
US11140592B2 (en) Method and apparatus for selecting radio access network device
US20160353498A1 (en) Communication control method, position management device, base station device, terminal device, and communication system
CN110651504A (zh) 通信终端、网络装置、通信方法及非暂时性计算机可读介质
US20230224770A1 (en) Communication method and apparatus
JP2021513825A (ja) Ｓｓｃモードを決定するための方法および装置
WO2019196680A1 (fr) Procédé de communication, et appareil de communication
WO2019184721A1 (fr) Procédé et dispositif de réacheminement
WO2019174582A1 (fr) Procédé et dispositif de transmission de message
WO2020052463A1 (fr) Procédé de communication et élément de réseau
KR102268412B1 (ko) 핸드오버 방법, 디바이스 및 시스템
WO2021052109A1 (fr) Procédé et appareil de communication

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18823766

Country of ref document: EP

Kind code of ref document: A1