WO2020187052A1 - Procédé et appareil de sélection de tranches de réseaux - Google Patents

Procédé et appareil de sélection de tranches de réseaux Download PDF

Info

Publication number
WO2020187052A1
WO2020187052A1 PCT/CN2020/078084 CN2020078084W WO2020187052A1 WO 2020187052 A1 WO2020187052 A1 WO 2020187052A1 CN 2020078084 W CN2020078084 W CN 2020078084W WO 2020187052 A1 WO2020187052 A1 WO 2020187052A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network slice
terminal device
service data
slice
Prior art date
Application number
PCT/CN2020/078084
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 WO2020187052A1 publication Critical patent/WO2020187052A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/13—Cell handover without a predetermined boundary, e.g. virtual cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • This application relates to the field of communication technology, and in particular to a method and device for network slice selection.
  • Network slice is a logical network with specific network characteristics divided from the operator’s communication network. It is the fifth generation (5th generation) proposed by the 3rd generation partnership project (3GPP). , 5G) mobile communication technology is a key technology for network differentiation requirements.
  • a physical network can be abstracted into multiple network slices, and each network slice constitutes an end-to-end logical network, which is logically isolated from each other.
  • Each network slice can flexibly provide one or more network services according to the requirements of the demander, and has no influence on other network slices in the network.
  • the network performance requirements of different network slices are not the same.
  • the network slices of augmented reality (AR) or virtual reality (VR) services require large bandwidth and low latency services;
  • the network slicing of things (IOT) services requires support for massive terminal access, but the bandwidth is small and there is no requirement for delay.
  • the network can select the service network slice for the terminal device.
  • the network can select the service network slice for different service data streams of the same application.
  • embodiments of the present application provide a network slice selection method and device, which are used to select network slices for different service data streams of the same application.
  • an embodiment of the present application provides a network slice selection method, which includes:
  • the terminal device receives the first network slice selection strategy from the policy control network element in the first network, where the first network slice selection strategy is used to indicate the network in the first network corresponding to the multiple service data streams of the first application in the terminal device. Slicing, where the multiple service data streams of the first application include the first service data stream; further, the terminal device may determine the network in the first network corresponding to the first service data stream to be sent according to the first network slice selection strategy The slice is the first network slice.
  • the terminal device can determine according to the first network slice selection strategy
  • the multiple service data streams of the first application respectively correspond to the network slices in the first network, so that different service data streams of the same application can be transmitted through different network slices; the method in the embodiment of this application can ensure that A good user experience, on the other hand, facilitates operators to provide differentiated services by deploying different network slices.
  • the network performance of the first network slice meets the network performance requirement of the first service data flow.
  • the first network slice selection strategy includes an association between the identification of the first application, the network performance requirement of the first service data flow, and the identification of the first network slice.
  • the first network slice selection strategy includes multiple communication descriptors and routing descriptors corresponding to the multiple communication descriptors; the multiple communication descriptors include the first communication descriptor, and the first communication description The symbol corresponds to the first routing descriptor; the first communication descriptor includes the identification of the first application and the requirements of the first service data stream on network performance; the first routing descriptor includes the identification of the first network slice.
  • the terminal device determines the first network slice in the first network corresponding to the first service data stream according to the first network slice selection strategy, which may mean: the terminal device obtains the first network slice to which the first service data stream belongs.
  • the identification of the application and the requirement of the first service data stream for network performance If the identification of the application to which the first service data stream belongs and the requirement of the first service data stream for network performance match the first communication descriptor, the first communication descriptor can be determined.
  • the network slice corresponding to the service data flow is the first network slice.
  • the terminal device may send the first service data stream through the first network slice.
  • the first network slice has multiple network slice instances.
  • the terminal device sending the first service data stream through the first network slice may include: the terminal device sends the first network slice to the first network slice.
  • a network slice selection network element sends a first request, the first request includes the identification of the first network slice, and the first request is used to request to determine the first network slice instance among the multiple network slice instances, where the network of the first network slice instance The performance meets the requirements of the first service data stream for network performance, and the first network slice instance is used to transmit the first service data stream.
  • the method may further include: the terminal device receives the first mapping information sent by the second network slice selection network element in the second network, and the first The mapping information is used to indicate that one or more network slices in the first network respectively correspond to a network slice in the second network.
  • One or more network slices in the first network include the first network slice, and the first network slice corresponds to The network slice in the second network is the second network slice, and the network performance of the second network slice matches the network performance of the first network slice; further, the terminal device can use the first mapping information to correspond to the first network slice The second network slice sends the first service data stream.
  • the terminal device can obtain the first network slice after determining that the network slice corresponding to the first service data stream is the first network slice
  • the corresponding second network slice sends the first service data stream through the second network slice, so that when the service network of the terminal device is the second network, the network slice for transmitting the first data stream can be determined relatively quickly.
  • the second network slice has multiple network slice instances.
  • the terminal device sending the first service data stream through the second network slice may include: the terminal device sends the first service data stream to the second network slice. 2.
  • Network slice selection The network element sends a second request, the second request includes the identifier of the second network slice, and the second request is used to request to determine the second network slice instance among the multiple network slice instances, where the network of the second network slice instance The performance meets the requirements of the first service data stream for network performance, and the second network slice instance is used to transmit the first service data stream.
  • the network performance may include any one or any combination of the following: service level agreement SLA level, billing level, service quality QoS level.
  • an embodiment of the present application provides a network slice selection method, which includes:
  • the policy control network element in the first network generates a first network slice selection strategy for the terminal device, and sends the first network slice selection strategy to the terminal device; wherein, the first network slice selection strategy is used to instruct the first application in the terminal device
  • the multiple service data streams respectively correspond to network slices in the first network.
  • the terminal device can be based on the first network slice
  • the selection strategy determines the network slices in the first network corresponding to the multiple service data streams of the first application, so that different service data streams of the same application can be transmitted through different network slices.
  • the multiple service data streams of the first application include the first service data stream, and the network slice in the first network corresponding to the first service data stream is the first network slice; the network of the first network slice The performance meets the network performance requirements of the first service data stream.
  • the first network slice selection strategy includes an association between the identification of the first application, the network performance requirement of the first service data flow, and the identification of the first network slice.
  • the first network slice selection strategy includes multiple communication descriptors and routing descriptors corresponding to the multiple communication descriptors; the multiple communication descriptors include the first communication descriptor, and the first communication description The symbol corresponds to the first routing descriptor; the first communication descriptor includes the identification of the first application and the requirements of the first service data stream on network performance; the first routing descriptor includes the identification of the first network slice.
  • the policy control network element generates the first network slice selection strategy for the terminal device, which may include: the policy control network element obtains application information and network slice information of the terminal device, and the application information includes the identification of the first application, The network performance requirements of the multiple service data streams of the first application, the network slice information includes the identification of one or more network slices in the first network, and the network performance of one or more network slices in the first network; further, The policy control network element may generate the first network slice selection policy according to the application information and the network slice information.
  • the policy control network element may obtain the application information of the terminal device from the application function network element or the network capability opening function network element.
  • the policy control network element may obtain network slice information from the first network slice selection network element or the network data analysis function network element.
  • an embodiment of the present application provides a network slice selection method, which includes:
  • the terminal device receives a second network slice selection strategy from the policy control network element in the first network, where the second network slice selection strategy is used to instruct at least one network slice in the first network corresponding to the first application in the terminal device; further, the terminal The device may determine the first network slice from the at least one network slice for the first service data flow to be sent according to the second network slice selection strategy and the network performance of at least one network slice in the first network corresponding to the first application, where ,
  • the multiple service data streams of the first application include the first service data stream, and the network performance of the first network slice meets the network performance requirement of the first service data stream.
  • the terminal device selects the network slice for the service data stream of the first application, it introduces the requirement of the service data stream of the first application on the network performance and at least one network slice in the first network corresponding to the first application. Therefore, it is possible to select network slices for different service data streams according to the network performance requirements of different service data streams of the first application, so that different service data streams of the same application can be transmitted through different network slices. In this way, on the one hand, a good user experience can be guaranteed, and on the other hand, it is convenient for operators to provide differentiated services by deploying different network slices.
  • the terminal device may receive network slice information from the first network slice selection network element in the first network, and the network slice information includes the network performance of at least one network slice in the first network corresponding to the first application .
  • the terminal device may send the first service data stream through the first network slice.
  • the first network slice has multiple network slice instances; in this case, the terminal device sending the first service data stream through the first network slice may include: the terminal device sends the first network slice to the first network slice.
  • a network slice selection network element sends a first request, the first request includes the identification of the first network slice; the first request is used to request to determine the first network slice instance among the multiple network slice instances, where the network of the first network slice instance The performance meets the requirements of the first service data stream for network performance, and the first network slice instance is used to transmit the first service data stream.
  • the method may further include: the terminal device receives the first mapping information from the second network slice selection network element in the second network, and the first mapping The information is used to indicate that one or more network slices in the first network respectively correspond to the network slices in the second network.
  • One or more network slices in the first network include the first network slice, and the first network slice corresponds to The network slice in the second network is the second network slice, and the network performance of the second network slice matches the network performance of the first network slice; further, the terminal device can use the first network slice corresponding to the first network slice according to the first mapping information The second network slice sends the first service data stream.
  • the terminal device can obtain the first network slice after determining that the network slice corresponding to the first service data stream is the first network slice
  • the corresponding second network slice sends the first service data stream through the second network slice, so that when the service network of the terminal device is the second network, the network slice for transmitting the first data stream can be determined relatively quickly.
  • the second network slice has multiple network slice instances; in this case, the terminal device sending the first service data stream through the second network slice may include: the terminal device sends the first service data stream to the second network slice.
  • Network slice selection The network element sends a second request, the second request includes the identification of the second network slice; the second request is used to request to determine the second network slice instance among the multiple network slice instances, where the second network slice instance The network performance meets the network performance requirements of the first service data stream, and the second network slice instance is used to transmit the first service data stream.
  • an embodiment of the present application provides a network slice selection method, which includes:
  • the first network slice selection network element in the first network obtains network slice information, and sends the network slice information to the second network slice selection network element in the second network; wherein, the network slice information includes one or more of the network slice information in the first network.
  • the identification of each network slice, and the network performance of one or more network slices in the first network is the first network slice selection network element in the first network.
  • the network slice information sent by the first network slice selection network element includes the network performance of one or more network slices in the first network, it is convenient for the second network slice selection network element to be based on the network slices in the first network. Network performance to generate the first mapping information.
  • the first network slice selection network element may obtain network slice information from the network data analysis function network element in the first network.
  • the method may further include: the first network slice selection network element receives a first request from the terminal device, the first request includes the identifier of the first network slice, and further obtains according to the identifier of the first network slice A plurality of network slice instances of the first network slice; and, selecting the first network slice instance from the plurality of network slice instances, and feeding back the identifier of the first network slice instance to the first access management network element in the first network .
  • an embodiment of the present application provides a network slice selection method, which includes:
  • the second network slice selection network element in the second network receives network slice information from the first network slice selection network element in the first network, and the network slice information includes the identification of one or more network slices in the first network, and the first network slice selection network element
  • the network performance of one or more network slices in a network may be generated; further, the second network slice selection network element may generate first mapping information for the terminal device according to the network slice information; the first mapping information is used to indicate one of the first networks Or a plurality of network slices respectively correspond to a network slice in the second network, one or more network slices in the first network include the first network slice, and the network slice in the second network corresponding to the first network slice is the second network slice
  • the network performance of the second network slice matches the network performance of the first network slice.
  • the second network slice selection network element may send the first mapping information to the terminal device.
  • the method may further include: the second network slice selection network element receives a second request from the terminal device, the second request includes an identifier of the second network slice; further, according to the identifier of the second network slice, Acquire multiple network slice instances of the second network slice; and, select the second network slice instance from the multiple network slice instances, and feed back the identifier of the second network slice instance to the second access management network in the second network yuan.
  • an embodiment of the present application provides a network slice selection method, which includes:
  • the terminal device obtains a second network slice selection strategy, and the second network slice selection strategy is used to indicate at least one network slice in the first network corresponding to the first application in the terminal device; if the service network of the terminal device is the first network, the terminal The device selects the network element from the first network slice to receive the network performance of one or more network slices in the first network, and according to the network performance requirements of the first service data stream to be sent, and the application status of the first service data stream.
  • the identification, the network slice selection strategy, and the network performance of one or more network slices in the first network select the first network slice in the first network for the first service data flow.
  • the terminal device when the terminal device selects the network slice for the first service data stream, it introduces the network performance of one or more network slices in the first network and the network performance requirements of the service data stream, so that the service When the network is the first network, suitable network slices are selected for different service data streams of the first application.
  • an embodiment of the present application provides a network slice selection method, and the method includes:
  • the first network slice selection network element in the first network receives a first request from the terminal device, where the first request includes the identifier of the first network slice; further, according to the identifier of the first network slice, obtain multiple networks of the first network slice A slice instance; and, selecting a first network slice instance from a plurality of network slice instances, and feeding back the identifier of the first network slice instance to the first access management network element in the first network.
  • an embodiment of the present application provides a network slice selection method, which includes:
  • the terminal device obtains a second network slice selection strategy, which is used to indicate at least one network slice in the first network corresponding to the first application in the terminal device; if the service network of the terminal device is the second network, the terminal The device receives second mapping information and network performance of one or more network slices in the second network from the second network slice selection network element in the second network, and the second mapping information is used to indicate one or more network slices in the first network.
  • Each network slice corresponds to the network slice in the second network; further, the terminal device can be based on the network performance requirements of the first service data stream to be sent, the identification of the application to which the first service data stream belongs, the network slice selection strategy, The second mapping information and the network performance of one or more network slices in the second network select the second network slice in the second network for the first service data flow.
  • the terminal device when the terminal device selects the network slice for the first service data stream, it introduces the network performance of one or more network slices in the second network and the network performance requirements of the service data stream, so that the service When the network is the second network, suitable network slices are selected for different service data streams of the first application.
  • an embodiment of the present application provides a network slice selection method, which includes:
  • the second network slice in the second network selects the network element to generate second mapping information, and the second mapping information is used to indicate that one or more network slices in the first network respectively correspond to network slices in the second network; if the terminal device If the service network is the second network, the second network slice selection network element sends the second mapping information and the network performance of one or more network slices in the second network to the terminal device.
  • the method may further include: the second network slice selection network element receives a second request from the terminal device, the second request includes an identifier of the second network slice; further, according to the identifier of the second network slice, Acquire multiple network slice instances of the second network slice; and, select the second network slice instance from the multiple network slice instances, and feed back the identifier of the second network slice instance to the second access management network in the second network yuan.
  • an embodiment of the present application provides a network slice selection method, which includes:
  • the terminal device obtains a second network slice selection strategy, and the second network slice selection strategy is used to indicate at least one network slice in the first network corresponding to the first application in the terminal device; if the service network of the terminal device is the first network, the terminal The device can select the first network slice in the first network for the first service data stream according to the application to which the first service data stream to be sent belongs and the network slice selection strategy; further, if the terminal device determines that the first network slice exists An established PDU session, and the PDU session meets the network performance requirements of the first service data flow, the first service data flow can be transmitted through the PDU session.
  • the terminal device may send a third request to the first network slice selection network element in the first network, and the third request includes the first network slice.
  • the identification of a network slice, the network performance requirement of the first data stream; the third request is used to request to determine the third network slice instance among the multiple network slice instances of the first network slice, and the network performance of the third network slice instance meets The first data flow requires network performance, and the third network slice instance is used to transmit the first service data flow.
  • an embodiment of the present application provides a network slice selection method, which includes:
  • the first network slice selection network element in the first network receives a third request from the terminal device.
  • the third request includes the identification of the first network slice and the network performance requirement of the first data stream to be sent; further, according to the first network The identification of the slice, obtaining multiple network slice instances of the first network slice and the network performance of the multiple network slice instances; and, selecting the first network performance from the multiple network slice instances that meets the network performance requirements of the first service data stream Three network slice instances, and feed back the identifier of the third network slice instance to the first access management network element in the first network.
  • an embodiment of the present application provides a network slice selection method, which includes:
  • the terminal device obtains a network slice selection strategy and second mapping information.
  • the network slice selection strategy is used to indicate at least one network slice in the first network corresponding to the first application in the terminal device
  • the second mapping information is used to indicate the network slice in the first network.
  • One or more network slices respectively correspond to network slices in the second network; if the service network of the terminal device is the second network, the terminal device can select the strategy according to the application to which the first service data stream to be sent belongs, network slice selection strategy, The second mapping information selects the second network slice for the first service data flow; further, if the terminal device determines that there is an established PDU session in the second network slice, and the PDU session meets the network performance requirements of the first service data flow , The first service data stream can be transmitted through the PDU session.
  • the terminal device may send a fourth request to the second network slice selection network element in the second network, where the fourth request includes the first 2.
  • the identification of the network slice and the network performance requirement of the first data stream; the fourth request is used to request the determination of the fourth network slice instance among the multiple network slice instances of the second network slice, and the network performance of the fourth network slice instance meets The first data flow requires network performance, and the fourth network slice instance is used to transmit the first service data flow.
  • an embodiment of the present application provides a network slice selection method, which includes:
  • the second network slice selection network element in the second network receives a fourth request from the terminal device, where the fourth request includes the identification of the second network slice and the network performance requirement of the first data stream to be sent; and, according to the second network
  • the identifier of the slice is used to obtain multiple network slice instances of the second network slice and the network performance of the multiple network slice instances; further, the network performance of the multiple network slice instances is selected from the multiple network slice instances to meet the network performance requirements of the first service data stream.
  • an embodiment of the present application provides a device, which may be a terminal device or a policy control network element, a first network slice selection network element or a second network slice selection network element, or the device may also be deployed
  • the terminal device or the policy control network element or the first network slice selects the network element or the second network slice selects the semiconductor chip in the network element.
  • the device has the function of realizing various possible designs of any one of the first aspect to the thirteenth aspect. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • an embodiment of the present application provides a device that includes a processor and a memory, the processor is configured to execute instructions stored on the memory, and when the instructions are executed, the device executes the first aspect to The methods described in the various possible designs of any one of the thirteenth aspects.
  • an embodiment of the present application also provides a computer-readable storage medium.
  • the computer-readable storage medium includes instructions. When the instructions are executed, any one of the first to thirteenth aspects is implemented. Of the various possible designs described.
  • the embodiments of the present application also provide a computer program product including instructions, which when run on a computer, enable the computer to execute various possible designs in any one of the first to thirteenth aspects. The method described.
  • Figure 1 is a schematic diagram of a system architecture to which an embodiment of the application is applicable;
  • FIG. 2 is a schematic flowchart corresponding to a network slice selection method provided by an embodiment of this application;
  • FIG. 3 is a schematic flow diagram corresponding to another network slice selection method provided by an embodiment of this application.
  • FIG. 4 is a schematic flowchart corresponding to another network slice selection method provided by an embodiment of this application.
  • FIG. 5 is a schematic diagram of the process corresponding to the network slice selection method in the first embodiment of this application.
  • FIG. 6 is a schematic flowchart of a network slice selection method in Embodiment 2 of this application.
  • FIG. 7 is a schematic flowchart of a network slice selection method in Embodiment 3 of this application.
  • FIG. 8 is a schematic diagram of a flow corresponding to the network slice selection method in the fourth embodiment of the application.
  • FIG. 9 is a schematic flowchart of a network slice selection method in Embodiment 5 of this application.
  • FIG. 10 is a possible exemplary block diagram of a device involved in an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of a terminal device provided by an embodiment of this application.
  • FIG. 12 is a schematic structural diagram of a device provided by an embodiment of this application.
  • Fig. 1 exemplarily shows a schematic diagram of a system architecture to which an embodiment of the present application is applicable.
  • the system architecture includes terminal equipment, access network (AN) equipment, access management network elements, session management network elements, user plane network elements, policy control network elements, and network slice selection network elements , Application server and data network (DN) connecting the application server and the operator’s network.
  • network elements such as policy control network elements and network slice selection network elements are connected to the service bus.
  • the terminal device can send the application service data stream to the application server through the AN device, the user plane network element, and the DN, or the application server can also send the service data stream to the terminal device through the DN, the user plane network element, and the access network device.
  • the interface between the user plane network element and the DN may be called the N6 interface
  • the interface between the user plane network element and the session management network element may be called the N4 interface
  • the interface between the session management network element and the access management network element The interface can be called the N11 interface
  • the interface between the session management network element and the policy control network element can be called the N7 interface
  • the interface between the access management network element and the policy control network element can be called the N15 interface.
  • the names of these interfaces may not change or may be replaced with other names, which is not limited in this application.
  • Terminal equipment It is a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes , Balloons and satellites etc.).
  • the terminal device may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, an industrial control ( Wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grids, and transportation safety Wireless terminal, wireless terminal in smart city, wireless terminal in smart home, etc.
  • Terminal equipment may sometimes be called user equipment (UE), mobile station, remote station, etc.
  • the embodiments of the present application do not limit the specific technology, device form, and name used by the terminal equipment.
  • AN equipment used to be responsible for the wireless side access of the terminal equipment.
  • Possible deployment forms include: a centralized unit (CU) and a distributed unit (DU) separation scenario and a single site scenario.
  • CU supports radio resource control (radio resource control, RRC), packet data convergence protocol (packet data convergence protocol, PDCP), service data adaptation protocol (service data adaptation protocol, SDAP) and other protocols;
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • DU It mainly supports radio link control (RLC), media access control (MAC) and physical layer protocols.
  • a single site can include (new radio Node, gNB), evolved Node B (evolved Node B, eNB), radio network controller (RNC), and Node B (Node B, NB) , Base Station Controller (BSC), Base Transceiver Station (BTS), Femtocell Base Station, Base Band Unit (BBU), etc.
  • gNB new radio Node
  • eNB evolved Node B
  • RNC radio network controller
  • Node B Node B
  • BSC Base Station Controller
  • BTS Base Transceiver Station
  • Femtocell Base Station Base Band Unit
  • Access management network element Mainly used for terminal attachment, mobility management, and tracking area update procedures in the mobile network.
  • the access management network element terminates non-access stratum (NAS) messages, completes registration management, Connection management and reachability management, allocating track area list (track area list, TA list), mobility management, etc., and transparently route session management (session management, SM) messages to the session management network element.
  • NAS non-access stratum
  • the access management network element may be an access and mobility management function (AMF).
  • Session management network element Mainly used for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning an Internet Protocol (IP) address to the terminal, selecting a user plane network element that provides a message forwarding function, and so on.
  • IP Internet Protocol
  • the session management network element may be a session management function (session management function, SMF).
  • User plane network element Mainly responsible for processing user messages, such as forwarding, billing, and lawful monitoring.
  • the user plane network element may also be called a protocol data unit (protocol data unit, PDU) session anchor (PDU) session anchor (PSA).
  • PDU protocol data unit
  • PDU session anchor
  • PSA session anchor
  • the user plane network element may be a user plane function (UPF).
  • UPF user plane function
  • Policy control network element including user subscription data management function, policy control function, charging policy control function, quality of service (quality of service, QoS) control, etc.
  • the policy control network element may be a policy control function (PCF).
  • PCF policy control function
  • Network slicing selection network element Mainly used to select the appropriate network slicing for the terminal's business.
  • the network slice selection network element may be a network slice selection function (network slice selection function, NSSF) network element.
  • Data network Provides data transmission services for the terminal, which can be a public data network (PDN) network, such as the Internet.
  • PDN public data network
  • system architecture shown in FIG. 1 may also include network data analysis network elements, network capability opening function network elements, application function network elements, unified data management network elements, and unified data storage network elements connected to the service bus.
  • Network warehouse function network element may also include network data analysis network elements, network capability opening function network elements, application function network elements, unified data management network elements, and unified data storage network elements connected to the service bus.
  • network data analysis network elements can be based on various network functions (network function, NF), such as policy control network elements, session management network elements, user plane network elements, access management network elements, application function network elements (through network capabilities Open function network element) to collect data, and analyze and predict.
  • network function network function
  • the network data analysis network element may be a network data analysis function (NWDAF).
  • Network capability opening network element part of the network functions can be exposed to applications in a controlled manner.
  • the network capability opening network element may be a network exposure function (NEF).
  • Unified data management network element responsible for managing the contract information of the terminal.
  • the unified data management network element may be unified data management (UDM).
  • Unified data storage network element responsible for storing structured data information, including contract information, policy information, and network data or business data defined in a standard format.
  • the unified data storage network element may be a unified data repository (UDR).
  • Application function network element It can provide service data of various applications to the control plane network element of the communication network of the operator, or obtain network data information and control information from the control plane network element of the communication network.
  • the application function network element may be an application function (AF).
  • Network warehouse function network element In a 5G communication system, the network warehouse function network element may be a network repository function (NRF).
  • NRF network repository function
  • the network elements described in the embodiments of this application may be hardware, or may also be functionally divided software or a structure combining the two.
  • the network element described in the embodiment of the present application may also be referred to as a functional entity.
  • a policy control network element may also be referred to as a policy control functional entity.
  • the name of each network element is not limited in the embodiment of the present application, and those skilled in the art can replace the name of the foregoing network element with another name to perform the same function.
  • LTE long-term evolution
  • 5th generation fifth generation
  • 5G fifth generation
  • the device issues a URSP (user equipment route selection policy, user equipment routing selection policy), where the URSP includes a network slice selection policy (network slice selection policy, NSSP).
  • URSP user equipment route selection policy, user equipment routing selection policy
  • NSSP network slice selection policy
  • the NSSP may include multiple rules, and each of the multiple rules may include the identification of the application and the identification of the network slice.
  • the identifier of the network slice may be a single network slice selection assistance information (S-NSSAI), where the identifier of the network slice in HPLMN may be expressed as hS-NSSAI, visiting public land
  • S-NSSAI single network slice selection assistance information
  • hS-NSSAI the identifier of the network slice in HPLMN
  • VPLMN visitor public land mobile network
  • the meaning of the rule expressed in the second row of Table 1 is that if the identifier of an application is "App-A", when the application requests to establish a session connection, the terminal device carries S in the session establishment request -NSSAI can be "hS-NSSAI1".
  • the service network of the terminal device is HPLMN, the network will select the network slice identified as “hS-NSSAI 1" (such as network slice a1) to transmit the service data flow of the application.
  • the meaning of the rule stated in the third row of Table 1 is that if the identifier of an application is "App-B", when the application requests to establish a session connection, the S-NSSAI carried by the terminal device in the session establishment request can be "hS -NSSAI 2", when the service network of the terminal device is HPLMN, the network will select the network slice identified as “hS-NSSAI 2" (such as network slice a2) to transmit the service data flow of the application.
  • the NSSP can also include a default rule (see the fourth row in Table 1).
  • the meaning of the default rule is that if the identity of an application cannot match other rules, the application requests to establish a session connection ,
  • the S-NSSAI carried in the session establishment request by the terminal device can be the S-NSSAI specified by the default rule (ie "hS-NSSAI 3").
  • the service network of the terminal device is HPLMN, the network will select the identifier as "hS- The network slice of NSSAI 3" (such as network slice a3) transmits the service data flow of the application.
  • the S-NSSAI in the NSSP are all S-NSSAI allocated by the HPLMN.
  • S-NSSAI can be divided into two types: standard S-NSSAI and custom S-NSSAI.
  • standard S-NSSAI can be used on all operator networks, while custom S-NSSAI can only be used by the operator that allocates it. Used within the network, and a custom S-NSSAI only identifies a network slice in an operator's network.
  • the S-NSSAI contracted by the terminal device in HPLMN is a custom S-NSSAI, after the terminal device roams, it will not be able to use the hS-NSSAI in the VPLMN to determine the network slice that the terminal device is allowed to use in the VPLMN.
  • a possible solution is to configure network slice mapping information according to the roaming agreement signed by HPLMN and VPLMN, that is, HPLMN and VPLMN can map the S-NSSAI in the two networks when signing the roaming agreement It means that hS-NSSAI is mapped to vS-NSSAI, or it can also be said that a correspondence relationship is established between hS-NSSAI and vS-NSSAI. See Table 2 for an example of network slice mapping information.
  • HPLMN includes 3 network slices, namely network slice a1 (hS-NSSAI 1), network slice a2 (hS-NSSAI 2), and network slice a3 (hS-NSSAI 3);
  • VPLMN includes 3 There are two network slices, namely network slice b1 (vS-NSSAI 1), network slice b2 (vS-NSSAI 2), and network slice b3 (vS-NSSAI 3).
  • the terminal device determines that the identifier of the network slice corresponding to App-A is hS-NSSAI 1 according to Table 1, and the terminal device requests the session establishment
  • the S-NSSAI carried in it can be hS-NSSAI 1.
  • the terminal device determines according to Table 1 that the identifier of the network slice corresponding to App-A is hS-NSSAI 1, and determines hS according to Table 2.
  • -NSSAI 1 corresponds to vS-NSSAI 1
  • the S-NSSAI carried in the session establishment request of the terminal device can be "vS-NSSAI 1".
  • the identification of the application is usually the installation package identification of the application in the application market
  • the network slice a1 is selected for APP-A
  • all the service data streams of APP-A will pass through the network Slice a1 for transmission.
  • the application may have many service data streams during use, and these service data streams have very different requirements for network performance; taking WeChat as an example, it can send messages and video calls. You can make mobile payments and play games.
  • customers or operators may want different service data streams of the same application to be transmitted in different network slices.
  • the embodiments of the present application provide a network slice selection method and device, which are used to select network slices for different service data streams of the same application.
  • the network slice selection method provided by the embodiment of the present application may include two possible solutions, namely, solution one and solution two.
  • the network slice selection strategy is used to indicate the network slices in the first network corresponding to the multiple service data streams of the first application in the terminal device.
  • the terminal device can determine the first application according to the network slice selection strategy.
  • the terminal device can obtain the network performance of one or more network slices in the first network and/or the second network, and then can perform network performance according to the requirements of the first service data flow in the first application.
  • the first service data flow selects a network slice in the first network or the second network.
  • FIG. 2 is a schematic flowchart of a network slice selection method provided by an embodiment of the application, as shown in FIG. 2, including:
  • Step 201 The policy control network element in the first network generates a network slice selection policy (may be referred to as a first NSSP) for the terminal device.
  • the first NSSP is used to indicate that the multiple service data streams of the first application in the terminal device respectively correspond to A network slice in the first network, where the multiple service data streams of the first application include the first service data stream.
  • the first NSSP may include multiple communication descriptors and routing descriptors corresponding to the multiple communication descriptors; the multiple communication descriptors include a first communication descriptor, and the first communication descriptor corresponds to the first route.
  • the first NSSP includes a first communication descriptor and a first routing descriptor corresponding to the first communication descriptor, which can also be described as: the first NSSP includes the identification of the first application and the first service data stream Association between the demand for network performance and the identification of the first network slice.
  • a possible implementation manner for the policy control network element to generate the first NSSP for the terminal device is that the policy control network element obtains the application information and network slice information of the terminal device, and based on the application information and network information of the terminal device The slice information generates the first NSSP.
  • the application information of the terminal device may include the identifier of the first application, and the requirements of multiple service data streams of the first application on network performance. Further, the application information of the terminal device may also include other possible information, such as multiple service data stream templates, performance characteristics of multiple service data streams, etc., which are not specifically limited.
  • the policy control network element may obtain the application information of the terminal device from the application function network element or the network capability opening function network element.
  • the service provider of the first application may use the application function network element to provide application information to the network. If the application function network element is located in the first network, the application function network element may obtain the address of the policy control network element in advance, and then Send the application information of the terminal device to the policy control network element; if the application function network element does not belong to the first network, the application function network element can provide the network capability opening function network element with information about the terminal device using the first application (for example, it can It is the generic public subscription identifier (GPSI) of the terminal device.
  • GPSI generic public subscription identifier
  • the network capability opening function network element can determine the address of the policy control network element according to the information of the terminal device using the first application, and then apply the function network The element can send the application information of the terminal device to the policy control network element through the network capability opening function network element.
  • the network slice information may include identifications of one or more network slices in the first network, and network performance of one or more network slices in the first network.
  • the policy control network element may obtain network slice information from the first network slice selection network element or the network data analysis network element in the first network.
  • the policy control network element may send a request to the network slice selection network element, and accordingly, the network slice selection network element returns network slice information to the policy control network element according to the request.
  • the policy control network element can subscribe to the network data analysis network element for network slicing information, so that the network data analysis network element can slice the network in time The information is updated to the policy control network element; in another example, the policy control network element may also send a request to the network data analysis network element, and accordingly, the network data analysis network element returns network slice information to the policy control network element according to the request.
  • Step 202 The policy control network element sends the first NSSP to the terminal device.
  • the policy control network element may send the first NSSP to the terminal device through the access management network element and the AN device in the first network.
  • the policy control network element may send the first NSSP to the terminal device after detecting a preset event.
  • the preset event may be at least one of the following: the terminal device is registered to the first network or the second network, the contracted network slice of the terminal device in the first network changes, the terminal device moves to the second network, and the user plane device starts Or turn off application traffic detection. Understandably, the preset event may also be other possible events set by those skilled in the art, which is not limited in this application.
  • the policy control network element detects that the terminal device is registered to the first network, which may mean that the policy control network element receives a notification message from the unified data management network element that the terminal device is registered to the first network.
  • Step 203 The terminal device receives the first NSSP from the policy control network element in the first network.
  • the terminal device may receive the first NSSP sent by the policy control network element through the access management network element and the AN device in the first network.
  • Step 204 The terminal device determines, according to the first NSSP, the network slice in the first network corresponding to the first service data stream to be sent as the first network slice.
  • the terminal device obtains the identification of the application to which the first service data flow belongs and the network performance requirement of the first service data flow, and if the identification of the application to which the first service data flow belongs and the network performance of the first service data flow are determined If the requirement matches the first communication descriptor, it is determined that the network slice corresponding to the first service data stream is the first network slice.
  • step 205 is executed. If the service network is the second network, step 206 to step 209 are executed.
  • Step 205 The terminal device transmits the first service data stream through the first network slice.
  • the terminal device determines that there is a PDU session established using the identifier of the first network slice, it can directly transmit the first service data stream through the PDU session, and if it is determined that there is no PDU session established using the identifier of the first network slice , The identifier of the first network slice may be used to establish a PDU session, and after the PDU session is successfully established, the first service data stream is transmitted through the PDU session.
  • the terminal device uses the identifier of the first network slice to establish a PDU session, which may be: the terminal device selects the network from the first network slice in the first network.
  • the element sends a first request.
  • the first request includes the identification of the first network slice and the network performance requirement of the first service data flow. Accordingly, the first network slice selection network element may receive the first request from the terminal device according to the first request.
  • a network slice identification obtain multiple network slice instances of the first network slice and the network performance of the multiple network slice instances, select the first network performance from the multiple network slice instances to meet the network performance requirements of the first service data stream A network slice instance, and the identifier of the first network slice instance is fed back to the first access management network element in the first network, and the first access management network element may establish a PDU session based on the identifier of the first network slice instance.
  • Step 206 The first network slice selection network element in the first network obtains network slice information, and sends the network slice information to the second network slice selection network element in the second network.
  • the network slice information includes the network slice information in the first network. The identification of one or more network slices, and the network performance of one or more network slices in the first network.
  • the first network slice selection network element may obtain the network slice information from a network data analysis function network element in the first network.
  • the first network slice selection network element may send the acquired network slice information to the second network slice selection network element when the first network and the second network enter into a roaming agreement, or the first network slice selection network element
  • the network element may also send the network slice information to the second network slice selection network element after the first network and the second network enter into a roaming agreement, if it is determined that the identifier of the network slice in the first network has changed; implementation of this application The example does not limit this.
  • Step 207 The second network slice selection network element receives network slice information from the first network slice selection network element, generates first mapping information according to the network slice information, and sends the first mapping information to the terminal device.
  • the first mapping information is used to indicate that one or more network slices in the first network respectively correspond to network slices in the second network.
  • One or more network slices in the first network include the first network slice, and The network slice in the second network corresponding to one network slice is the second network slice, and the network performance of the second network slice matches the network performance of the first network slice.
  • Step 208 The terminal device receives the first mapping information from the second network slice selection network element.
  • Step 209 The terminal device transmits the first service data stream through the second network slice corresponding to the first network slice according to the first mapping information.
  • the terminal device determines that there is a PDU session established using the identifier of the second network slice, it can directly transmit the first service data stream through the PDU session, and if it is determined that there is no PDU session established using the identifier of the second network slice , The identifier of the second network slice may be used to establish a PDU session, and after the PDU session is successfully established, the first service data stream is transmitted through the PDU session.
  • the terminal device uses the identifier of the second network slice to establish a PDU session, which may be: the terminal device selects the network from the second network slice in the second network.
  • the element sends a second request.
  • the second request includes the identifier of the second network slice and the network performance requirement of the first service data flow.
  • the second network slice selection network element may receive the second request from the terminal device according to the first Second, the identification of the network slice, obtain multiple network slice instances of the second network slice and the network performance of the multiple network slice instances, and select the network performance from the multiple network slice instances to meet the network performance requirements of the first service data stream Two network slice instances, and feed back the identifier of the second network slice instance to the second access management network element in the second network, and the second access management network element may establish a PDU session based on the identifier of the second network slice instance.
  • the terminal device can determine according to the first NSSP Multiple service data streams of the first application correspond to network slices in the first network, so that different service data streams of the same application can be transmitted through different network slices; for example, taking WeChat as an example, when a message needs to be transmitted When the service data stream (the data volume of the service data stream is small and the delay requirement is low), the network slice corresponding to the service data stream can be used. When the service data stream of the video call needs to be transmitted (the data volume of the service data stream) Larger, higher latency requirements), you can use the network slice corresponding to the service data stream.
  • the method in the embodiment of the present application can ensure a good user experience on the one hand, and on the other hand, it is convenient for operators to provide differentiated services by deploying different network slices.
  • FIG. 3 is a schematic flowchart of a network slice selection method according to an embodiment of the application, as shown in FIG. 3, including:
  • Step 301 The policy control network element in the first network generates a network slice selection policy (may be referred to as a second NSSP) for the terminal device, and the second NSSP is used to indicate at least one of the first networks corresponding to the first application in the terminal device Network slicing.
  • a network slice selection policy may be referred to as a second NSSP
  • Step 302 The policy control network element sends the second NSSP to the terminal device.
  • the policy control network element may send the second NSSP to the terminal device through the access management network element and the AN device in the first network. If the service network of the terminal device is the second network, the policy control network element may send the second NSSP to the terminal device through the policy control network element in the second network, the access management network element in the second network, and the AN device.
  • Step 303 The terminal device receives the second NSSP from the policy control network element.
  • the terminal device may receive the second NSSP sent by the policy control network element through the access management network element and the AN device in the first network. If the service network of the terminal device is the second network, the terminal device can receive the policy control network element in the first network through the policy control network element in the second network, the access management network element in the second network, and the AN device The second NSSP.
  • Step 304 The terminal device determines a first network slice from at least one network slice for the first service data stream to be sent according to the second NSSP and the network performance of at least one network slice in the first network corresponding to the first application, where ,
  • the multiple service data streams of the first application include the first service data stream, that is, the first service data stream is one of the multiple service data streams of the first application, and the network performance of the first network slice meets the first Business data flow demands on network performance.
  • the terminal device can obtain the network performance of at least one network slice in the first network corresponding to the first application in multiple ways. For example, when the terminal device registers to the first network, it can obtain the network performance from the first network.
  • the first network slice selection network element receives network slice information, and the network slice information may include network performance of one or more network slices in the first network, where one or more network slices in the first network include the corresponding first application At least one network slice in the first network; further, after the terminal device receives the network performance of at least one network slice in the first network corresponding to the first application from the first network slice selection network element, it may be stored in In the preset storage space, in this way, when the service network of the terminal device is the second network, the terminal device can obtain the network performance of at least one network slice in the first network corresponding to the first application from the preset storage space.
  • step 305 is executed, and if the service network of the terminal device is For the second network, step 306 to step 309 are executed.
  • Step 305 The terminal device transmits the first service data stream through the first network slice.
  • Step 306 The first network slice selection network element in the first network obtains network slice information, and sends the network slice information to the second network slice selection network element in the second network.
  • the network slice information includes the network slice information in the first network. The identification of one or more network slices, and the network performance of one or more network slices in the first network.
  • Step 307 The second network slice selection network element receives network slice information from the first network slice selection network element, generates first mapping information according to the network slice information, and sends the first mapping information to the terminal device.
  • the first mapping information is used to indicate that one or more network slices in the first network respectively correspond to network slices in the second network.
  • One or more network slices in the first network include the first network slice, and The network slice in the second network corresponding to one network slice is the second network slice, and the network performance of the second network slice matches the network performance of the first network slice.
  • Step 308 The terminal device receives the first mapping information from the second network slice selection network element.
  • Step 309 The terminal device transmits the first service data stream through the second network slice corresponding to the first network slice according to the first mapping information.
  • the terminal device selects the network slice for the service data flow of the first application, it introduces the requirement of the service data flow of the first application on the network performance and the network performance requirements of the first application corresponding to the first application.
  • the network performance of at least one network slice can thereby select network slices for different service data streams according to the network performance requirements of different service data streams of the first application, so that different service data streams of the same application can be transmitted through different network slices. In this way, on the one hand, a good user experience can be guaranteed, and on the other hand, it is convenient for operators to provide differentiated services by deploying different network slices.
  • FIG. 4 is a schematic flowchart corresponding to another network slice selection method provided by an embodiment of this application.
  • the process described in FIG. 4 is mainly for a scenario where the service network of the terminal device is the second network. As shown in Figure 4, it includes:
  • Step 401 The policy control network element in the first network generates a second NSSP for the terminal device, where the second NSSP is used to indicate at least one network slice in the first network corresponding to the first application in the terminal device.
  • Step 402 The policy control network element sends the second NSSP to the terminal device.
  • the policy control network element may send the second NSSP to the terminal device through the access management network element and the AN device in the first network.
  • Step 403 The terminal device receives the second NSSP from the policy control network element.
  • the terminal device may receive the second NSSP sent by the policy control network element through the access management network element and the AN device in the first network.
  • Step 404 The terminal device receives the second mapping information from the second network slice selection network element in the second network.
  • the second mapping information may be the mapping information generated by the second network slice selection network based on the roaming protocol, as shown in Table 2.
  • the second mapping information may be used to indicate a network slice in the second network corresponding to at least one network slice in the first network.
  • Step 405 The terminal device determines, according to the second NSSP and the second mapping information, at least one network slice in the second network corresponding to the first service data flow to be sent; and the terminal device according to the second network slice corresponding to the first service data flow
  • the network performance of at least one network slice in the network is the first service data flow to determine the second network slice from at least one network slice in the second network, and the network performance of the second network slice meets the network performance of the first service data flow Demand.
  • the network performance of at least one network slice in the second network corresponding to the first service data stream may be received from the second network slice selection network element when the terminal device registers to the second network, for example, the second network
  • the slice selection network element may send the network performance of at least one network slice in the second network to the terminal device through the access management network element and the AN device in the second network.
  • Step 406 The terminal device transmits the first service data stream through the second network slice.
  • the terminal device selects the network slice for the service data flow of the first application, it introduces the requirement of the service data flow of the first application on the network performance and at least one network slice in the second network.
  • Network performance so that network slices can be selected for different service data streams according to the network performance requirements of different service data streams of the first application, so that different service data streams of the same application can be transmitted through different network slices.
  • a good user experience can be guaranteed, and on the other hand, it is convenient for operators to provide differentiated services by deploying different network slices.
  • the difference between the methods shown in FIG. 3 and FIG. 4 is that when the service network of the terminal device is the second network, in the method shown in FIG. 3, the first service data flow is determined The first network slice whose network performance meets the network performance requirements of the first service data flow, and then obtains the second network slice corresponding to the first network slice according to the first mapping information; because the two networks corresponding to each other in the first mapping information The network performance of the slices (for example, one network slice is the first network slice in the first network, and the other network slice is the second network slice in the second network) match, therefore, the second network obtained according to the first mapping information The network performance of the slice also meets the network performance requirements of the first service data stream, so that the first service data stream can be transmitted through the second network slice.
  • the two can be cross-referenced.
  • scheme one (such as the method shown in Figure 2) and scheme two (such as the method shown in Figure 3 and Figure 4) is: in the scheme one, the current NSSP is improved, and the current NSSP includes The content (see Table 1) is the association between the application identifier and the network slice identifier, and the content included in the NSSP in the first application further introduces the network performance requirements of the service data flow of the first application, so that the terminal equipment Able to select different network slices for different service data streams with different performance requirements.
  • the current NSSP is used.
  • the terminal device selects network slices based on the NSSP, it fully considers the network performance of the network slice and the requirements of the service data flow on the network performance, so that the terminal device can select different network slices for different service data flows. .
  • the descriptions of FIGS. 2, 3, and 4 can refer to each other.
  • Network performance may include at least one of the following: service level agreement (SLA) level, billing level, and quality of service (quality of service, QoS) level.
  • the requirements of the service data flow for network performance may also include at least one of the following: SLA level, billing level, and QoS level.
  • the network performance and service data flow requirements for network performance can be understood as a set of corresponding concepts. For example, network performance includes SLA levels, and the service data flow requirements for network performance also include SLA levels; network performance includes Charging level, the requirements of the service data flow on network performance also include the charging level.
  • the requirements of network performance and service data flow on network performance may also include other possible content, which is not limited in this application.
  • the SLA level is used to reflect the ability of the network slicing to guarantee the service data flow's requirements for network performance. For example, it can be several levels negotiated in advance by the application and the operator. Each level can represent that each service data flow of the application cannot satisfy the network. The degree of tolerance of the occurrence probability of SLA, or the proportion of time during which the SLA required by each service data flow of the application can be satisfied by the network. For example, a service data flow can tolerate that the network cannot meet the promised delay requirement within 0.1% of the time.
  • the charging level can be several charging levels negotiated in advance by the application (or user) and the operator, and each level corresponds to the number of network resources allocated by the operator or the allocation method (shared or exclusive, etc.).
  • the QoS level may be the level of performance characteristics of the network required by the service data flow, or the probability that the network slice meets the performance characteristics and QoS parameters required by the service data flow.
  • the network performance of the two network slices involved in the embodiments of the present application match, for example, the network performance of the first network slice in the first network matches the network performance of the second network slice in the second network, which may refer to The network performance of the first network slice is the same as the network performance of the second network slice, or the network performance of the second network slice is better than the network performance of the first network slice.
  • the network performance of the second network slice is better than the network performance of the first network slice, which may mean that the charging level of the second network slice is not higher than the charging level of the first network slice; If the network performance is at the SLA level, the network performance of the second network slice is better than the network performance of the first network slice, which may mean that the SLA level of the second network slice is higher than the SLA level of the first network slice; if the network performance is QoS level
  • the fact that the network performance of the second network slice is better than the network performance of the first network slice may mean that the QoS level of the second network slice is higher than the QoS level of the first network slice.
  • step numbers involved in the embodiments of the present application are only a possible example of the execution process, and do not constitute a restriction on the order of execution of each step. In the embodiments of the present application, there is no strict execution sequence among steps that have no time sequence dependency relationship with each other.
  • the policy control network element is PCF
  • the network slice selection network element is NSSF
  • the user plane network element is UPF
  • the session management network element is SMF
  • the access management network element is AMF
  • network data The analysis network element is NWDAF
  • network capability opening network element is NEF
  • unified data management network element is UDM
  • unified data storage network element is UDR
  • application function network element is AF
  • network warehouse function network element is NRF as examples.
  • the first network may be HPLMN
  • the policy control network element in the first network may be h-PCF
  • the first network slice selection network element in the first network may be h-NSSF, and other network elements may refer to Processing
  • the second network may be VPLMN
  • the second network slice selection network element in the second network may be v-NSSF, and other network elements may refer to processing.
  • FIG. 5 is a schematic diagram of the process corresponding to the network slice selection method in Embodiment 1 of this application, as shown in FIG. 5, including:
  • Step 501 The h-PCF obtains the application information of the terminal device from the AF.
  • the application information of the terminal device includes the identification of the first application and the requirements for network performance of multiple service data streams of the first application.
  • the first application may be any one of one or more applications used by the terminal device.
  • the applications used by the terminal device include APP-A, APP-B, and APP-C, and the first application may be APP- A. APP-B or APP-C.
  • the first application is APP-A as an example for description.
  • the first application may include service data stream 1, service data stream 2, and service data stream 3. Taking network performance as an example of SLA level, the requirement of service data stream 1 for network performance can be SLA level 1, and service The requirement of data stream 2 for network performance can be SLA level 2, and the requirement of service data stream 3 for network performance can be SLA level 3.
  • Step 502 The h-PCF obtains network slice information from the h-NSSF.
  • the network slice information includes the identification of one or more network slices in the HPLMN and the network performance of one or more network slices in the HPLMN.
  • the identification of one or more network slices in the HPLMN may include the subscription hS-NSSAI of the terminal device in the HPLMN.
  • the contract hS-NSSAI of the terminal equipment in HPLMN includes hS-NSSAI 1, hS-NSSAI 2, hS-NSSAI 3.
  • the network performance of the network slice identified by hS-NSSAI 1 (that is, network slice a1) is SLA level 1
  • the network performance of the network slice identified by hS-NSSAI 2 that is, network slice a2) is SLA level 2
  • hS-NSSAI 3 The network performance of the identified network slice (ie, network slice a3) is SLA level 3.
  • the h-PCF can generate the first NSSP according to the application information and network slice information of the terminal device.
  • the first NSSP may include multiple communication descriptors and routing descriptors corresponding to the multiple communication descriptors. See Table 3, which is an example of the content included in the first NSSP.
  • the first NSSP includes three communication descriptors and three routing descriptors corresponding to the three communication descriptors.
  • the first communication descriptor includes the identification of the first application (APP-A) and the requirement of service data stream 1 for network performance;
  • the first routing descriptor includes the identification of the network slice a1 (hS-NSSAI 1);
  • the network slice corresponding to APP-A's service data stream 1 is network slice a1.
  • the second communication descriptor includes the identification of the first application (APP-A) and the requirement of service data stream 2 for network performance; the second routing descriptor includes the identification of the network slice a2 (hS-NSSAI 2); that is, The network slice corresponding to APP-A's service data stream 2 is network slice a2.
  • the third communication descriptor includes the identification of the first application (that is, APP-A) and the requirement of service data stream 3 for network performance; the third routing descriptor includes the identification of the network slice a3 (that is, hS-NSSAI 3). In other words, the network slice corresponding to the service data stream 3 of APP-A is network slice a3.
  • the information shown in Table 3 can also be understood as that the first NSSP includes: APP-A, the network performance requirements of the first service data flow, and the association between hS-NSSAI 1; APP-A The requirements of the second service data stream on network performance and the association between hS-NSSAI 2; the requirements of APP-A and the third service data stream on network performance and the association between hS-NSSAI 3.
  • the network performance of the network slice corresponding to a certain service data flow in the first NSSP can meet the network performance requirement of the service data flow.
  • the network performance of network slice a1 meets the network performance requirements of service data stream 1
  • the network performance of network slice a2 meets the network performance requirements of service data stream 2
  • the network performance of network slice a3 meets the service data flow 3 Demand for network performance.
  • the time for h-PCF to generate the first NSSP is not limited, and it only needs to be generated before step 504.
  • Steps 503a to 503f are the process of registering the terminal device to HPLMN.
  • Step 503a The terminal device sends a registration request to the h-AMF through the AN device.
  • the registration request may carry the identification of the terminal device.
  • Step 503b h-AMF determines the UDM that manages the subscription data of the terminal device according to the identification of the terminal device, and obtains the subscription data of the terminal device from the UDM, where the subscription data of the terminal device includes the terminal device's contract hS-NSSAI in HPLMN , Namely hS-NSSAI 1, hS-NSSAI 2, hS-NSSAI 3.
  • Step 503c After verifying that the identity of the terminal device is legal, the h-AMF sends a network slice selection request to h-NSSF, where the network slice selection request includes the location information of the terminal device and the contract hS-NSSAI of the terminal device in the HPLMN.
  • Step 503d h-NSSF sends a network slice selection response to h-AMF, where the network slice selection response includes the terminal device's permission hS-NSSAI in the HPLMN.
  • the allowable hS-NSSAI of the terminal device in the HPLMN refers to the contract hS-NSSAI that the network can provide services for the terminal device in the current registration area after the terminal device is registered in the HPLMN.
  • the allowable hS-NSSAI of the terminal device in the HPLMN includes hS-NSSAI 1, hS-NSSAI 2, hS-NSSAI 3, that is, the contract hS-NSSAI that the network can provide services for the terminal device in the current registration area includes hS-NSSAI 1, hS-NSSAI 2, hS-NSSAI 3.
  • h-AMF accepts the registration request of the terminal device, and sends a registration response to the terminal device through the AN device, where the registration response includes the terminal device's permission hS-NSSAI in the HPLMN, namely hS-NSSAI 1, hS -NSSAI 2, hS-NSSAI 3.
  • the terminal device receives the response message of successful registration and stores the permission hS-NSSAI.
  • Step 503f After the terminal device is successfully registered, the h-AMF can register the context data of the terminal device with the UDM that manages the subscription data of the terminal device, where the context data of the terminal device is used for registration management and mobility management of the terminal device.
  • step 503g during the processing of the registration request, h-PCF can subscribe to UDM for the context data change event of the terminal device. In this way, after h-AMF registers the context data of the terminal device with UDM, UDM will send a notification to h-PCF news.
  • Step 504 After receiving the notification message, the h-PCF sends the first NSSP to the terminal device.
  • the h-PCF After the h-PCF receives the notification message, it can also determine whether the terminal device needs to configure or update the NSSP. If it is determined that the configuration or update is required, then the first NSSP is sent to the terminal device; if it is determined that the configuration or update is not required, Then the first NSSP may not be sent to the terminal device.
  • the h-PCF can determine whether it is necessary to configure or update the NSSP for the terminal device in various ways.
  • the notification message may include the NSSP stored by the terminal device (for ease of description, referred to as the original NSSP); after the h-PCF receives the notification message, if it is determined that the notification message includes the original NSSP, the original NSSP and The first NSSP is compared, when the original NSSP is different from the first NSSP (for example, the first NSSP includes the content shown in Table 3, and the original NSSP only includes the content shown in the first three rows in Table 3, excluding the fourth Line), h-PCF can determine that the NSSP needs to be updated for the terminal device; in this case, h-PCF can send the entire content of the first NSSP to the terminal device, or h-PCF can also send the first NSSP The NSSP is different from the content of the original NSSP (that is, part of the content of the first NSSP, such as
  • h-PCF can determine that the terminal device needs to be configured with NSSP. In this case, h-PCF can send all of the first NSSP to the terminal device content.
  • the terminal device receives and stores the first NSSP sent by the h-PCF.
  • Step 505 The terminal device determines that the service data stream 1 of the first application needs to be sent.
  • the first application (generally the client program of the first application) needs to send service data stream 1, it will call the data sending interface provided by the terminal device, and provide the identification (APP-A) and service of the first application. Data stream 1 and service data stream 1 demand network performance. In this way, the terminal device can obtain the identification of the first application (APP-A), the service data stream 1, and the network performance requirements of the service data stream 1.
  • Step 506 After the terminal device determines that the network slice corresponding to service data stream 1 is network slice a1 according to the identifier of the first application, the requirement for network performance of service data stream 1 and the first NSSP, if the identifier of network slice a1 (hS- NSSAI 1) allows hS-NSSAI, then step 507 can be performed. If the identifier of the network slice a1 (hS-NSSAI1) does not allow hS-NSSAI, then in a possible implementation, the terminal device can adjust the network performance requirements of the service data stream 1.
  • the specific adjustment basis can be determined by those skilled in the art Setting, not limited.
  • the terminal device adjusts the network performance requirement of service data stream 1 to SLA level 2, so that the network slice corresponding to service data stream 1 can be determined based on the adjusted requirements.
  • the terminal device can send a prompt message to the user, prompting the user to confirm whether the service data stream 1's network performance requirements can be adjusted to SLA level 2. If the user confirms, the terminal device can be adjusted based on The latter needs to determine the network slice corresponding to service data stream 1.
  • Step 507 The terminal device determines whether there is a PDU session established using hS-NSSAI1, if it exists, step 508 can be performed, and if it does not exist, the terminal device can use hS-NSSAI1 to establish a PDU session.
  • Step 508 The terminal device sends the service data stream 1 through the existing PDU session in the network slice a1.
  • the operator can deploy one or more network slice instances (NSI) for a network slice identified by S-NSSAI.
  • NSSAI network slice instances
  • the network performance of multiple network slicing instances may be the same or different.
  • the network performance of the multiple network slice instances is the same
  • the network performance of the network slice a1 is the network performance of any network slice instance in the multiple network slice instances.
  • the network performance of the multiple network slice instances can be the same. It can also be different, see the description below for details.
  • the terminal device uses hS-NSSAI 1 to establish a PDU session, which can be: if the network slice a1 has a network slice instance, the terminal device uses hS-NSSAI 1 to establish a PDU session.
  • the specific implementation process includes (not shown in Figure 5): Step a1, the terminal device sends a session establishment request to the h-AMF network element through the AN device, where the session establishment request carries hS-NSSAI1; step a2, the h-AMF network element sends the session establishment request to the network according to the hS-NSSAI1 carried in the session establishment request.
  • the network repository function (NRF) network element requests to determine the h-SMF network element; the address of the NRF can be provided by the hNSSF network element to the h-AMF network element in the registration process of the terminal device, or it can be the h-AMF network After receiving the session establishment request message, the element requests the hNSSF network element to select the network slice for the
  • network slice a1 has multiple network slice instances, for example, network slice a1 has network slice instance a11 and network slice instance a12, where the network performance of network slice instance a11 and network slice instance a12 is the same as that of network slice a1, both If the SLA level is 1, the specific implementation process of the terminal device using hS-NSSAI 1 to establish a PDU session may include step 509 to step 511.
  • Step 509 The terminal device sends a first request to h-NSSF, where the first request includes hS-NSSAI1.
  • the terminal device sends the first request to the h-NSSF network element, which may be: the terminal device sends a session establishment request to h-AMF through the AN device, and the session establishment request carries hS-NSSAI1; accordingly, h-AMF receives After the session establishment request, a network slice instance selection request is sent to h-NSSF, and the network slice instance selection request includes hS-NSSAI1.
  • the h-NSSF selects a network slice instance a11 for the service data stream 1 from a plurality of network slice instances included in the network slice a1 according to the first request.
  • the specific basis for selecting the network slice instance is not limited in the embodiment of the present application.
  • Step 511 The h-NSSF sends the identifier of the network slice instance a11 to the h-AMF.
  • the h-AMF may request the NRF to determine the h-SMF network element in the network slice instance a11 according to the identifier of the network slice instance a11, and then request the h-SMF network element to establish a PDU session.
  • the specific implementation process can refer to the above step a2 to step a6.
  • Step 513 The terminal device sends the service data stream 1 through the newly established PDU session in the network slice instance a11.
  • the service network of the terminal device in the first solution is a VPLMN.
  • Fig. 6 is a schematic diagram of the process corresponding to the network slice selection method in the second embodiment of this application, as shown in Fig. 6, including:
  • Step 601 and step 602 can refer to step 501 and step 502 in FIG. 5.
  • Step 603 h-NSSF sends network slice information to v-NSSF.
  • the network slice information includes the identification of one or more network slices in HPLMN, and the network performance of one or more network slices in HPLMN.
  • the identification of one or more network slices in the HPLMN may include the subscription hS-NSSAI of the terminal device in the HPLMN.
  • the contract hS-NSSAI of the terminal equipment in HPLMN includes hS-NSSAI 1, hS-NSSAI 2, hS-NSSAI 3.
  • the network performance of hS-NSSAI 1 is SLA level 1
  • the network performance of hS-NSSAI 2 is SLA level 2
  • the network performance of hS-NSSAI 3 is SLA level 3.
  • Step 604 The v-NSSF generates mapping information 1 according to the roaming agreement, the network performance of one or more network slices in the HPLMN, and the network performance of one or more network slices in the VPLMN.
  • mapping information 1 is used to indicate the network slices in the VPLMN corresponding to one or more network slices in the HPLMN. See Table 4, which is an example of the mapping information 1.
  • vS-NSSAI 1 is the identifier of network slice b1 in VPLMN
  • vS-NSSAI 2 is the identifier of network slice b2 in VPLMN
  • vS-NSSAI 3 is the identifier of network slice b3 in VPLMN.
  • Network slice a1 corresponds to network slice b1, or network slice a1 maps to network slice b1
  • network slice a2 corresponds to network slice b2, or network slice a2 maps to network slice b2
  • network slice a3 corresponds to network slice b3, or network slice a3 is mapped to network slice b3.
  • the network performance of the network slice in the HPLMN corresponding to a certain network slice in the VPLMN matches the network performance of the network slice.
  • the network performance of network slice b1 matches the network performance of network slice a1; the network performance of network slice b2 matches the network performance of network slice a2; the network performance of network slice b3 matches the network performance of network slice a3. match.
  • TOS value and/or flow identifier can also be used to indicate the network performance of the network slice, for example, TOS1 and/or flow identifier 1 indicate SLA level 1.
  • the v-NSSF can also generate the above mapping information 1 according to the roaming agreement, the TOS value of the network slice and/or the flow identifier.
  • mapping information 1 the TOS value and/or the TOS value of a certain network slice in the VPLMN
  • the flow identification matches the TOS value and/or flow identification of the network slice in the corresponding HPLMN (the same or corresponding according to the roaming agreement).
  • Steps 605a to 605f are procedures for the terminal device to register with the VPLMN.
  • Step 605a The terminal device sends a registration request to the v-AMF through the AN device.
  • the registration request may carry the identification of the terminal device.
  • the v-AMF determines the UDM that manages the subscription data of the terminal device according to the identification of the terminal device, and obtains the subscription data of the terminal device from the UDM, where the subscription data of the terminal device includes the terminal device's contract hS-NSSAI in HPLMN , Namely hS-NSSAI 1, hS-NSSAI 2, hS-NSSAI 3.
  • Step 605c After verifying that the identity of the terminal device is legal, the v-AMF sends a network slice selection request to the v-NSSF, where the network slice selection request includes the location information of the terminal device and the contract hS-NSSAI of the terminal device in the HPLMN.
  • v-NSSF sends a network slice selection response to v-AMF, where the network slice selection response includes the vS-NSSAI allowed by the terminal device in the VPLMN and mapping information 2, and the mapping information 2 is used to indicate the allowed vS-NSSAI and other information.
  • the corresponding hS-NSSAI The corresponding hS-NSSAI.
  • the vS-NSSAI allowed by the terminal device in the VPLMN refers to the vS-NSSAI that the network can provide services for the terminal device in the current registration area after the terminal device is registered in the VPLMN.
  • the vS-NSSAI allowed by the terminal device in the VPLMN includes vS-NSSAI1, vS-NSSAI2, that is, the vS-NSSAI that the network can provide services for the terminal device in the current registration area includes vS-NSSAI1, vS -NSSAI2, vS-NSSAI that cannot provide services to terminal devices includes vS-NSSAI3.
  • the mapping information 2 is used to indicate vS-NSSAI 1, vS-NSSAI 2 and their corresponding hS-NSSAI. See Table 5, which is an example of mapping information 2.
  • the mapping information 2 may be a part of the content of the mapping information 1, as shown in Table 5. In other possible embodiments, if the vS-NSSAI in the mapping information 1 is all allowed vS-NSSAI, the mapping information 2 may also be the same as the mapping information 1.
  • the v-AMF accepts the registration request of the terminal device, and sends a successful registration response to the terminal device through the AN device, where the registration response includes the terminal device's permission vS-NSSAI in the VPLMN (that is, vS-NSSAI 1, vS -NSSAI 2) and mapping information 2.
  • the terminal device receives the response message of successful registration, and stores the permission vS-NSSAI and the mapping information 2.
  • the v-AMF can register the context data of the terminal device with the UDM that manages the subscription data of the terminal device, where the context data of the terminal device is used for registration management and mobility management of the terminal device.
  • Step 605g after the v-AMF registers the context data of the terminal device with the UDM, the UDM may send a notification message to the h-PCF.
  • Step 606 After receiving the notification message, the h-PCF sends the first NSSP to the terminal device.
  • Step 607 The terminal device determines that the service data stream 1 of the first application needs to be sent.
  • step 608 the terminal device determines that the network slice in the HPLMN corresponding to service data stream 1 is network slice a1 according to the identification of the first application, the requirement of service data stream 1 for network performance and the first NSSP, and then determines according to the mapping information 2.
  • the network slice in the VPLMN corresponding to service data stream 1 is network slice b1. If the identifier of the network slice b1 (vS-NSSAI 1) allows vS-NSSAI, step 609 may be performed.
  • Step 609 The terminal device judges whether there is a PDU session established using vS-NSSAI1, if it exists, it can perform step 610, if it does not exist, the terminal device can use vS-NSSAI1 to establish a PDU session.
  • Step 610 The terminal device sends the service data stream 1 through the existing PDU session in the network slice b1.
  • the terminal device uses vS-NSSAI 1 to establish a PDU session, which can be: if the network slice b1 has a network slice instance, the terminal device uses vS-NSSAI 1 to establish a PDU session.
  • the specific implementation process includes (not shown in Figure 5): Step b1: The terminal device sends a session establishment request to the v-AMF network element through the AN device, where the session establishment request carries vS-NSSAI1; Step 2, the v-AMF network element sends the NRF according to the vS-NSSAI1 carried in the session establishment request Request to determine the v-SMF network element; the NRF address can be provided to v-AMF by vNSSF in the registration process of the terminal device, or the v-AMF network element requests the vNSSF network element for session establishment after receiving the session establishment request message The vS-NSSAI carried in the request message is obtained when the network slice is selected; step b3, the NRF network element selects the v
  • v-AMF forwards the session establishment request to the selected v-SMF network element; Step b5, after the v-SMF network element receives the session establishment request, it selects the appropriate v-UPF network element and controls the selected v-UPF The network element establishes a PDU session; step b6, the v-SMF network element sends a session establishment response message to the terminal device through the v-AMF and AN device, and at the same time informs the AN device of the session-related information through the v-AMF network element, which may include the session Information such as the tunnel address and QoS parameters of the user plane.
  • session Information such as the tunnel address and QoS parameters of the user plane.
  • network slice b1 has multiple network slice instances, for example, network slice b1 has network slice instance b11 and network slice instance b12, where the network performance of network slice instance b11 and network slice instance b12 is the same as that of network slice b11, both If it is SLA level 1, the specific implementation process of the terminal device using vS-NSSAI 1 to establish a PDU session may include step 611 to step 613.
  • Step 611 The terminal device sends a second request to v-NSSF, where the second request includes vS-NSSAI1.
  • the v-NSSF selects a network slice instance b11 for the service data flow 1 from a plurality of network slice instances included in the network slice a1 according to the second request.
  • the specific basis for selecting the network slice instance is not limited in the embodiment of the present application.
  • Step 613 The v-NSSF sends the identifier of the network slice instance b11 to the v-AMF.
  • the v-AMF may request the NRF to determine the v-SMF network element in the network slice instance b11 according to the identifier of the network slice instance b11, and then request the v-SMF network element to establish a PDU session.
  • the specific implementation process refer to the above step b2 to step b6.
  • Step 615 The terminal device sends the service data stream 1 through the PDU session established in the network slice instance b11.
  • FIG. 7 is a schematic diagram of the process corresponding to the network slice selection method in the third embodiment of this application, as shown in FIG. 7, including:
  • the h-PCF obtains the identifier of one or more applications in the terminal device, and the one or more applications include the first application.
  • h-PCF may obtain the identification of the first application in the terminal device from AF.
  • h-PCF may also obtain multiple service data flow templates of the first application and multiple service data of the first application from AF. Stream performance characteristics, etc.
  • Step 702 h-PCF obtains the identifiers of one or more network slices in HPLMN.
  • the identification of one or more network slices in the HPLMN may include the subscription hS-NSSAI of the terminal device in the HPLMN.
  • the hS-NSSAI contract of the terminal device in HPLMN includes hS-NSSAI1, hS-NSSAI2, and hS-NSSAI3.
  • the h-PCF may obtain the contract hS-NSSAI of the terminal device in the HPLMN from the h-NSSF.
  • the h-PCF can generate a second NSSP according to the identity of the first application and the hS-NSSAI of the terminal device in the HPLMN contract.
  • the second NSSP can be used to indicate at least one network slice in the HPLMN corresponding to the first application in the terminal device. . See Table 6, which is an example of the content included in the second NSSP.
  • the network slice in HPLMN corresponding to the first application includes network slice a1 (hS-NSSAI 1), network slice a2 (hS-NSSAI 2), and network slice a3 (hS-NSSAI 3). ).
  • the time for the h-PCF to generate the second NSSP is not limited.
  • Steps 703a to 703g are processes for the terminal device to register with HPLMN.
  • Step 703a The terminal device sends a registration request to the h-AMF through the AN device, and the registration request can carry the identification of the terminal device.
  • h-AMF determines the UDM that manages the subscription data of the terminal device according to the identification of the terminal device, and obtains the subscription data of the terminal device from the UDM, where the subscription data of the terminal device includes the terminal device's contract hS-NSSAI in HPLMN , Namely hS-NSSAI 1, hS-NSSAI 2, hS-NSSAI 3.
  • step 703c after verifying that the identity of the terminal device is legal, the h-AMF sends a network slice selection request to the h-NSSF, where the network slice selection request includes the location information of the terminal device and the contract hS-NSSAI of the terminal device in the HPLMN.
  • Step 703d h-NSSF sends a network slice selection response to h-AMF, where the network slice selection response includes the terminal device’s permission hS-NSSAI in the HPLMN and the terminal device’s contract in the HPLMN for the network slice identified by hS-NSSAI.
  • Performance ie, the network performance of network slice a1, network slice a2, and network slice a3.
  • the allowable hS-NSSAI of the terminal device in HPLMN includes hS-NSSAI 1, hS-NSSAI 2, hS-NSSAI 3; the network performance of the network slice identified by hS-NSSAI 1 (that is, network slice a1) is SLA level 1.
  • the network performance of the network slice identified by hS-NSSAI 2 ie network slice a2) is SLA level 2
  • the network performance of the network slice identified by hS-NSSAI 3 ie network slice a3) is SLA level 3.
  • Step 703e h-AMF accepts the registration request of the terminal device, and sends a registration response of successful registration to the terminal device through the AN device, where the registration response includes the terminal device's permission hS-NSSAI in the HPLMN (that is, hS-NSSAI 1, hS -NSSAI 2, hS-NSSAI 3) and the network performance of the network slice identified by the terminal device in the HPLMN contract hS-NSSAI.
  • the terminal device receives a successful registration response message, and stores the network performance of the network slice identified by the hS-NSSAI and the terminal device's subscription in the HPLMN.
  • the h-AMF can register the context data of the terminal device with the UDM that manages the subscription data of the terminal device, where the context data of the terminal device is used for registration management and mobility management of the terminal device.
  • step 703g during the processing of the registration request, h-PCF can subscribe to UDM for the context data change event of the terminal device. In this way, after h-AMF registers the context data of the terminal device with UDM, UDM will send a notification to h-PCF news.
  • Step 704 After receiving the notification message, the h-PCF sends the second NSSP to the terminal device. Correspondingly, the terminal device receives and stores the second NSSP sent by the h-PCF.
  • Step 705 The terminal device determines that the service data stream 1 of the first application needs to be sent.
  • the first application (generally the client program of the first application) needs to send service data stream 1, it will call the data sending interface provided by the terminal device, and provide the identification (APP-A) and service of the first application. Data stream 1 and service data stream 1 demand network performance. In this way, the terminal device can obtain the identification of the first application (APP-A), the service data stream 1, and the network performance requirements of the service data stream 1 (for example, SLA level 1).
  • Step 706 The terminal device determines according to the identity of the first application, the requirement of service data flow 1 for network performance, the second NSSP, the network performance of the network slice with the hS-NSSAI identity of the terminal device in HPLMN, and the allowable hS-NSSAI.
  • the network slice corresponding to service data stream 1 is network slice a1, where the network performance of network slice a1 meets the network performance requirements of service data stream 1.
  • the terminal device may determine, according to the identifier of the first application and the second NSSP, that the network slice corresponding to the first application includes network slice a1 and network slice a2. Since hS-NSSAI1 and hS-NSSAI2 are allowed for hS-NSSAI, The terminal device can determine the network slice a1 whose network performance meets the network performance requirements of the service flow from the network slice a1 and the network slice a2 according to the network performance requirements of the service data stream 1 and the respective network performances that allow hS-NSSAI.
  • step 707 to step 713 refer to the description of step 507 to step 513 in FIG. 5.
  • the h-NSSF can send the terminal device the network performance of the network slice identified by the hS-NSSAI sign in the HPLMN contract of the terminal device (see step
  • the network slice selection response of 703d includes the network performance of the network slice identified by the terminal device in the HPLMN contract hS-NSSAI
  • the registration response in step 703e includes the network performance of the network slice identified by the terminal device in the HPLMN contract hS-NSSAI
  • the h-NSSF may not send the terminal device the network performance of the network slice identified by the hS-NSSAI contract of the terminal device in the HPLMN, that is, the network slice selection response in step 703d is not Including the network performance of the network slice identified by the terminal device in the HPLMN contracted hS-NSSAI, and the registration response in step 703e does not include the network performance of the network slice identified by the terminal device in the HPLMN contracted hS-NSSAI; in this case, After step 705, step 706' to step 713' can be performed.
  • Step 706' the terminal device selects a network slice for service data flow 1 according to the identity of the first application, the second NSSP, and the allowed hS-NSSAI.
  • the terminal device may determine, according to the identifier of the first application and the second NSSP, that the network slice corresponding to the first application includes network slice a1, network slice a2, and network slice a3. Since hS-NSSAI1 and hS-NSSAI2 are allowed for hS -NSSAI, so the terminal device can select a network slice from network slice a1 and network slice a2, and perform step 707' according to the selected network slice.
  • Step 707' if the network slice selected in step 706' is network slice a1, the terminal device determines whether there is a PDU session established using hS-NSSAI 1, and if the existing and established PDU session meets the conditions, step 708 can be performed If the existing but established PDU session does not meet the condition, then return to step 706'. At this time, the network slice selected in step 706' may be network slice a2. If there is no PDU session established using hS-NSSAI 1, the terminal device can use hS-NSSAI 1 to establish a PDU session.
  • the terminal device may store the corresponding relationship between the established PDU session and the network performance requirement of the service data flow, as shown in Table 7.
  • Table 7 Examples of correspondence between PDU sessions and service data flow requirements for network performance
  • PDU session 1 is a PDU session established using hS-NSSAI 1.
  • the condition that the established PDU session satisfies the condition may mean that the established PDU session meets the network performance requirements of service data flow 1, that is, the service data flow corresponding to the established PDU session has an impact on network performance.
  • the requirements are the same as those of service data stream 1 for network performance. Since the service data flow corresponding to PDU session 1 in Table 7 requires SLA level 1 for network performance, it can be considered that PDU session 1 meets the conditions.
  • the corresponding relationship between the established PDU session and the network performance requirements of the service data flow may come from the record of the established session stored by the terminal device after the session is successfully established, and the record includes the established session identifier and the trigger establishment. For the corresponding relationship between the service data stream to be sent in the session and the network performance requirements, see step 712' for details.
  • Step 708' the terminal device sends the service data stream 1 through the existing PDU session in the network slice a1.
  • the terminal device uses hS-NSSAI 1 to establish a PDU session, which can be: if the network slice a1 has a network slice instance, the PDU session can be established through step a1 to step a5. If network slice a1 has multiple network slice instances, for example, network slice a1 has network slice instance a11 and network slice instance a12, where the network performance of network slice instance a11 and network slice instance a12 may be the same or different, the terminal device The specific implementation process of using hS-NSSAI 1 to establish a PDU session may include step 709' to step 711'.
  • step 709' the terminal device sends a third request to h-NSSF, where the third request includes hS-NSSAI1 and the requirement of service data flow 1 for network performance.
  • the terminal device sending the third request to the h-NSSF may be: the terminal device sends a session establishment request to the h-AMF through the AN device, and the session establishment request carries hS-NSSAI1 and service data flow 1 requirements for network performance; Correspondingly, after receiving the session establishment request, h-AMF sends a network slice instance selection request to h-NSSF.
  • the network slice instance selection request includes hS-NSSAI1 and service data stream 1 requirements for network performance.
  • Step 710' according to the third request, if h-NSSF determines that among the multiple network slice instances included in the network slice a1 identified by hS-NSSAI1, there are network slice instances whose network performance meets the requirements of service data flow 1 for network performance, then Select the network slice instance (for example, network slice instance a11) for the service data flow, and perform step 711'; if it is determined that there is no network performance in the multiple network slice instances included in the network slice a1 that meets the requirement of service data flow 1 for network performance For the required network slice instance, return to step 706'. At this time, the network slice selected in step 706' may be network slice a2.
  • Step 711' h-NSSF sends the identifier of the network slice instance a11 to h-AMF.
  • the h-AMF may request the NRF to determine the h-SMF network element in the network slice instance a11 according to the identifier of the network slice instance a11, and then request the h-SMF network element to establish a PDU session.
  • the specific implementation process can refer to the above step a2 to step a6.
  • the terminal device may store the corresponding relationship between the PDU session and the network performance requirement of the service data stream 1.
  • Step 713' the terminal device sends the service data stream 1 through the newly established PDU session in the network slice instance a11.
  • the fourth embodiment a possible implementation process of the network slice selection method will be described mainly for the scenario in which the service network of the terminal device in the second solution is a VPLMN.
  • FIG. 8 is a schematic flowchart of a network slice selection method in Embodiment 4 of this application. As shown in Figure 8, including:
  • step 801 and step 802 reference may be made to the description of step 701 and step 702 in FIG. 7.
  • Step 803 h-NSSF sends network slice information to v-NSSF.
  • the network slice information includes the identification of one or more network slices in HPLMN, and the network performance of one or more network slices in HPLMN.
  • the one or more network slices in the HPLMN include one or more network slices in the hS-NSSAI signed by the terminal device in the HPLMN.
  • the v-NSSF generates mapping information 1 according to the roaming agreement, the network performance of one or more network slices in HPLMN, and the network performance of one or more network slices in VPLMN.
  • the mapping information 1 can be shown in Table 4.
  • Steps 805a to 805f are the process of registering the terminal device to the VPLMN.
  • Step 805a The terminal device sends a registration request to the v-AMF through the AN device, and the registration request may carry the identification of the terminal device.
  • v-AMF determines the UDM that manages the subscription data of the terminal device according to the identification of the terminal device, and obtains the subscription data of the terminal device from the UDM, where the subscription data of the terminal device includes the terminal device's contract hS-NSSAI in HPLMN , Namely hS-NSSAI 1, hS-NSSAI 2, hS-NSSAI 3, hS-NSSAI 4, hS-NSSAI 5.
  • step 805c after verifying that the identity of the terminal device is legal, the v-AMF sends a network slice selection request to the v-NSSF, where the network slice selection request includes the location information of the terminal device and the contract hS-NSSAI of the terminal device in the HPLMN.
  • the v-NSSF sends a network slice selection response to v-AMF, where the network slice selection response includes the vS-NSSAI allowed by the terminal device in the VPLMN and mapping information 2.
  • the mapping information 2 is used to indicate that the corresponding vS-NSSAI is allowed hS-NSSAI. See Table 5 for mapping information 2.
  • the v-AMF accepts the registration request of the terminal device, and sends a successful registration response to the terminal device through the AN device, where the registration response includes the terminal device's permission vS-NSSAI in the VPLMN (ie vS-NSSAI 1, vS -NSSAI 2) and mapping information 2.
  • the terminal device receives the response message of successful registration, and stores the permission vS-NSSAI and the mapping information 2.
  • the v-AMF may register the context data of the terminal device with the UDM that manages the subscription data of the terminal device, where the context data of the terminal device is used for registration management and mobility management of the terminal device.
  • step 805g after the v-AMF registers the context data of the terminal device with the UDM, the UDM may send a notification message to the h-PCF.
  • Step 806 After receiving the notification message, the h-PCF sends the second NSSP to the terminal device.
  • Step 807 The terminal device determines that the service data stream 1 of the first application needs to be sent.
  • Step 808 the terminal device according to the identification of the first application, the requirement of service data flow 1 for network performance (for example, SLA level 1), the second NSSP, and the network performance of the network slice identified by the terminal device in the HPLMN contract hS-NSSAI 2. Mapping information 2. Allow vS-NSSAI to determine that the network slice corresponding to service data stream 1 is network slice b1, where the network performance of network slice b1 meets the network performance requirements of service data stream 1.
  • the network performance of the network slice identified by the terminal device in the HPLMN contract hS-NSSAI may be acquired and stored by the terminal device in the process of registering with the HPLMN.
  • the terminal device may determine, according to the identity of the first application and the second NSSP, that the network slice in the HPLMN corresponding to the first application includes network slice a1 and network slice a2; further, according to the requirements of service data flow 1 for network performance and The network performance of the network slice identified by the terminal device in the HPLMN contract hS-NSSAI (that is, the network performance of network slice a1, network slice a2), and the network slice a1 whose network performance meets the network performance requirements of service data stream 1 is determined; Furthermore, according to the mapping information 2, it is determined that the network slice corresponding to network slice a1 is network slice b1, and vS-NSSAI 1 is allowed vS-NSSAI.
  • hS-NSSAI that is, the network performance of network slice a1, network slice a2
  • vS-NSSAI 1 is allowed vS-NSSAI.
  • the network slice corresponding to service data flow 1 is network slice b1.
  • the network performance of the network slice a1 matches the network performance of the network slice b1
  • the network performance of the network slice b1 also meets the network performance requirements of the service data stream 1.
  • step 809 to step 815 refer to the description of step 609 to step 615.
  • the terminal device can obtain the network performance of the network slice identified by the pre-stored terminal device's contract hS-NSSAI in the HPLMN.
  • the terminal device may not obtain the network performance of the network slice identified by the hS-NSSAI contract of the terminal device in HPLMN (for example, the terminal device is not pre-stored, so it cannot be obtained), but in the terminal
  • v-NSSF can send to the terminal device the network performance that allows the network slice identified by vS-NSSAI, that is, the network slice selection response in step 905d can include the network that allows the network slice identified by vS-NSSAI Performance, the registration response in step 905e may include the network performance that allows the network slice identified by vS-NSSAI); in this case, the above step 808 may be step 808':
  • Step 808' the terminal device according to the identification of the first application, the requirement of the service data stream 1 for network performance (for example, SLA level 1), the second NSSP, the mapping information 2, the network performance of the network slice that allows vS-NSSAI identification, It is determined that the network slice corresponding to the service data stream 1 is the network slice b1, where the network performance of the network slice b1 meets the requirement of the service data stream 1 for network performance.
  • the terminal device may determine, according to the identifier of the first application and the second NSSP, that the network slice corresponding to the first application includes network slice a1 and network slice a2; further, according to the mapping information 2, the corresponding network slice a1 and network slice a2 are obtained.
  • VPLMN allows network slices identified by vS-NSSAI, namely network slice b1 and network slice b2; further, according to the network performance requirements of service data stream 1 and the network performance of network slice b1 and network slice b2, it can be determined Network slice b1 whose network performance meets the network performance requirements of service data stream 1.
  • the terminal device may not obtain the network performance of the network slice identified by the terminal device in the HPLMN contracted hS-NSSAI (for example, the terminal device is not pre-stored, so it cannot be obtained), v-NSSF It also does not send the network performance of the network slice that allows vS-NSSAI identification to the terminal device.
  • steps 808" to step 815" can be executed as follows:
  • Step 808 the terminal device selects a network slice for service data flow 1 according to the identification of the first application, the second NSSP, the mapping information 2, vS-NSSAI allowed.
  • the terminal device may determine, according to the identity of the first application and the second NSSP, that the network slice in the HPLMN corresponding to the first application includes network slice a1 and network slice a2; further, the network slice corresponding to network slice a1 is determined according to the mapping information 2.
  • the slice is network slice b1, and vS-NSSAI 1 is allowed vS-NSSAI, the network slice corresponding to network slice a2 is network slice b2, and vS-NSSAI 2 is allowed vS-NSSAI. Therefore, the terminal device can select a network slice for the service data stream 1 from the network slice b1 and the network slice b2, and perform step 809" according to the selected network slice.
  • Step 809" if the network slice selected in step 808" is network slice b1, the terminal device determines whether there is a PDU session established using vS-NSSAI 1, and if the existing and established PDU session meets the conditions, step 810 ", if the existing but established PDU session does not meet the conditions, return to step 808". At this time, the network slice selected in step 808" can be network slice b2. If there is no PDU session established using hS-NSSAI 1 , The terminal device can use vS-NSSAI 1 to establish a PDU session.
  • the terminal device may store the correspondence between the established PDU session and the service data flow's requirements for network performance.
  • the established PDU session meeting the condition may mean that the service data flow corresponding to the established PDU session has a negative impact on the network.
  • the performance requirements are the same as the network performance requirements of service data stream 1.
  • Step 810 the terminal device sends the service data stream 1 through the existing PDU session in the network slice b1.
  • the terminal device uses vS-NSSAI 1 to establish a PDU session, which can be: if the network slice b1 has a network slice instance, it can establish a PDU session by performing steps b1 to b5. If network slice b1 has multiple network slice instances, for example, network slice b1 has network slice instance b11 and network slice instance b12, where the network performance of network slice instance b11 and network slice instance b12 may be the same or different, then the terminal device The specific implementation process of using vS-NSSAI 1 to establish a PDU session may include step 811" to step 813".
  • Step 811 the terminal device sends a fourth request to v-NSSF, where the fourth request includes vS-NSSAI1 and the requirement of service data flow 1 for network performance.
  • the terminal device sending the fourth request to the v-NSSF may be: the terminal device sends a session establishment request to the v-AMF through the AN device, and the session establishment request carries vS-NSSAI1 and service data flow 1 requirements for network performance;
  • the terminal device sends a network slice instance selection request to v-NSSF.
  • the network slice instance selection request includes vS-NSSAI1 and service data stream 1 requirements for network performance.
  • Step 812 according to the fourth request, if v-NSSF determines that among the multiple network slice instances included in network slice b1, there is a network slice instance whose network performance meets the requirements of service data flow 1 for network performance, then select this for the service data flow Network slicing instance (for example, network slicing instance b11), and step 813"; if it is determined that there is no network slicing instance whose network performance meets the requirements of service data flow 1 for network performance among the multiple network slicing instances included in network slice b1, Then return to step 808". At this time, the network slice selected in step 808" may be network slice b2.
  • Step 813 v-NSSF sends the identifier of the network slice instance b11 to v-AMF.
  • Step 814 v-AMF can establish a PDU session according to the identifier of the network slice instance b11.
  • the specific implementation process can refer to the above steps b2 to b6.
  • the terminal device can store the PDU session and Correspondence between service data stream 1's requirements for network performance.
  • Step 815 the terminal device sends the service data stream 1 through the PDU session established in the network slice instance b11.
  • FIG. 9 is a schematic diagram of the process corresponding to the network slice selection method in Embodiment 5 of this application, as shown in FIG. 9, including:
  • step 901 and step 902 reference may be made to the description of step 701 and step 702 in FIG. 7.
  • Step 903 The h-NSSF sends the identification of one or more network slices in the HPLMN to the v-NSSF.
  • the identification of one or more network slices in the HPLMN may include the subscription hS-NSSAI of the terminal device in the HPLMN.
  • the contract hS-NSSAI of the terminal equipment in HPLMN includes hS-NSSAI 1, hS-NSSAI 2, hS-NSSAI 3.
  • the v-NSSF In step 904, the v-NSSF generates mapping information 3 according to the roaming protocol, and the mapping information 3 is used to indicate the network slices in the HPLMN corresponding to one or more network slices in the VPLMN. See Table 8 for an example of mapping information 3.
  • network slice b1 corresponds to network slice a1
  • network slice b2 corresponds to network slice a2
  • network slice b3 corresponds to network slice a3.
  • Steps 905a to 905f are procedures for the terminal device to register with the VPLMN.
  • Step 905a The terminal device sends a registration request to the v-AMF through the AN device, and the registration request can carry the identification of the terminal device.
  • Step 905b v-AMF determines the UDM that manages the subscription data of the terminal device according to the identification of the terminal device, and obtains the subscription data of the terminal device from the UDM, where the subscription data of the terminal device includes the terminal device's contract hS-NSSAI in HPLMN , Namely hS-NSSAI 1, hS-NSSAI 2, hS-NSSAI 3.
  • step 905c after verifying that the identity of the terminal device is legal, the v-AMF sends a network slice selection request to the v-NSSF, where the network slice selection request includes the location information of the terminal device and the contract hS-NSSAI of the terminal device in the HPLMN.
  • Step 905d v-NSSF sends a network slice selection response to v-AMF, where the network slice selection response includes the terminal device's permission vS-NSSAI (such as vS-NSSAI 1, vS-NSSAI 2) and vS-NSSAI permission in the VPLMN
  • vS-NSSAI such as vS-NSSAI 1, vS-NSSAI 2
  • vS-NSSAI permission in the VPLMN The identification of the identified network slice, the network performance of the network slice that allows vS-NSSAI identification, and the mapping information4.
  • the mapping information 4 is used to indicate the hS-NSSAI corresponding to the allowed vS-NSSAI. See Table 9 for mapping information 4.
  • the mapping information 4 may be a part of the content of the mapping information 3, as shown in Table 9. In other possible embodiments, if the vS-NSSAI in the mapping information 3 is all allowed vS-NSSAI, the mapping information 4 may also be the same as the mapping information 3.
  • the v-AMF accepts the registration request of the terminal device, and sends a registration response of successful registration to the terminal device through the AN device, where the registration response includes the terminal device's permission vS-NSSAI in the VPLMN (that is, vS-NSSAI 1, vS -NSSAI 2), allow network performance and mapping information of the network slice identified by vS-NSSAI4.
  • the terminal device receives the response message of successful registration, and stores the network performance and mapping information of the network slices that allow vS-NSSAI, allow vS-NSSAI, and allow vS-NSSAI identification.
  • the v-AMF may register the context data of the terminal device with the UDM that manages the subscription data of the terminal device, where the context data of the terminal device is used for registration management and mobility management of the terminal device.
  • step 905g after the v-AMF registers the context data of the terminal device with the UDM, the UDM may send a notification message to the h-PCF.
  • Step 906 After receiving the notification message, the h-PCF sends the second NSSP to the terminal device.
  • Step 907 The terminal device determines that the service data stream 1 of the first application needs to be sent.
  • Step 908 The terminal device determines the network performance of the network slice that allows vS-NSSAI identification according to the identification of the first application, the requirement of the service data stream 1 for network performance (for example, SLA level 1), the second NSSP, the mapping information 4.
  • the network slice corresponding to service data stream 1 is network slice b1, where the network performance of network slice b1 meets the requirements of service data stream 1 for network performance.
  • the terminal device may determine, according to the identifier of the first application and the second NSSP, that the network slice corresponding to the first application includes network slice a1, network slice a2, and network slice a3; further, according to the mapping information 4, obtain network slice a1, Network slices identified by vS-NSSAI are allowed in the VPLMN corresponding to network slice a2, namely network slice b1 and network slice b2 (hS-NSSAI 3 that identifies network slice a3 is not included in the mapping information 4, so there is no corresponding allowed vS- Network slice identified by NSSAI); further, according to the network performance requirements of service data stream 1 and the network performance of network slice b1 and network slice b2, a network whose network performance meets the network performance requirements of service data stream 1 can be determined Slice b1.
  • step 909 to step 915 reference may be made to the description of step 609 to step 615.
  • the v-NSSF can send to the terminal device the network performance of the network slice identified by vS-NSSAI (see the network slice selection in step 905d).
  • the response includes allowing the network performance of the network slice identified by vS-NSSAI, and the registration response in step 905e includes allowing the network performance of the network slice identified by vS-NSSAI).
  • the v-NSSF may not send the network performance of the network slice that allows the vS-NSSAI identification to the terminal device, that is, the network slice selection response in step 905d does not include the vS-NSSAI identification allowed
  • the registration response in step 905e includes the network performance of the network slice identified by vS-NSSAI; in this case, after the above step 907, you can perform steps 908" to step 915", step 908" For the specific content to step 915", refer to step 808" to step 815".
  • the first mapping information involved in the process described in FIG. 2 may be the mapping information 1 described in Embodiment 2, Embodiment 4, and Embodiment 5, or may also be Embodiment 2, Embodiment 4.
  • the second mapping information involved in the process described in FIG. 4 may be the mapping information 3 described in the fifth embodiment, or may also be the mapping information 4 described in the fifth embodiment.
  • each network element includes a hardware structure and/or software module (or unit) corresponding to each function.
  • the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the present invention.
  • FIG. 10 shows a possible exemplary block diagram of a device involved in an embodiment of the present application, and the device 1000 may exist in the form of software.
  • the device 1000 may include: a processing unit 1002 and a communication unit 1003.
  • the processing unit 1002 is used to control and manage the actions of the device 1000.
  • the communication unit 1003 is used to support communication between the apparatus 1000 and other devices or network elements.
  • the communication unit 1003 is also referred to as a transceiver unit, and may include a receiving unit and/or a sending unit, which are used to perform receiving and sending operations, respectively.
  • the device 1000 may further include a storage unit 1001 for storing program codes and data of the device 1000.
  • the processing unit 1002 may be a processor or a controller, which may implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of the embodiments of the present application.
  • the communication unit 1003 may be a communication interface, a transceiver, or a transceiver circuit, etc., where the communication interface is a general term. In a specific implementation, the communication interface may include multiple interfaces.
  • the storage unit 1001 may be a memory.
  • the apparatus 1000 may be the terminal device in any of the foregoing embodiments, or may also be a semiconductor chip provided in the terminal device.
  • the processing unit 1002 may support the apparatus 1000 to perform the actions of the terminal device in the foregoing method examples.
  • the processing unit 1002 mainly supports the apparatus 1000 to execute internal actions of the terminal device in the method example, and the communication unit 1003 may support the communication between the apparatus 1000 and other devices or network elements.
  • the processing unit 1002 is used to support the device 1000 to perform step 204 in FIG. 2, and the communication unit 1003 is used to support the device 1000 to perform step 203, step 205, step 208, and step 209 in FIG.
  • the processing unit 1002 uses 3, the communication unit 1003 is used to support the device 1000 to perform step 303, step 305, step 308, and step 309 in FIG. 3; for another example, the processing unit 1002 is used to support the device 1000 to execute the diagram In step 405 in 4, the communication unit 1003 is used to support the device 1000 to perform steps 403 and 406 in FIG. 4; for another example, the processing unit 1002 is used to support the device 1000 to perform steps 506 and 507 in FIG. 5, and the communication unit 1003 For supporting the device 1000 to perform step 503a, step 503e, step 508, step 509, and step 513 in FIG.
  • the processing unit 1002 is used for supporting the device 1000 to perform step 608 and step 609 in FIG. 6, and the communication unit 1003 For supporting the device 1000 to perform step 605a, step 605e, step 610, step 611, and step 615 in FIG. 6; for another example, the processing unit 1002 is used for supporting the device 1000 to perform step 706 and step 707 in FIG. 7, and the communication unit 1003 For supporting the device 1000 to perform step 703a, step 703e, step 708, step 709, and step 713 in FIG. 7; for another example, the processing unit 1002 is used for supporting the device 1000 to perform step 808 and step 809 in FIG.
  • step 805a For supporting the device 1000 to perform step 805a, step 805e, step 810, step 811, and step 815 in FIG. 8; for another example, the processing unit 1002 is used for supporting the device 1000 to perform step 908 and step 909 in FIG. 9, and the communication unit 1003
  • the device for supporting 1000 executes step 905a, step 905e, step 910, step 911, and step 915 in FIG. 9.
  • the communication unit 1003 is configured to receive a network slice selection strategy from a policy control network element in the first network, and the network slice selection strategy is used to indicate multiple service data streams of the first application in the terminal device Respectively corresponding to the network slices in the first network, where the multiple service data streams of the first application include the first service data stream; the processing unit 1002 is configured to determine the corresponding first service data stream to be sent according to the network slice selection strategy
  • the network slice in the first network is the first network slice.
  • the network performance of the first network slice meets the network performance requirement of the first service data flow.
  • the network slice selection strategy includes an association between the identification of the first application, the network performance requirement of the first service data flow, and the identification of the first network slice.
  • the network slice selection strategy includes multiple communication descriptors and routing descriptors corresponding to the multiple communication descriptors; the multiple communication descriptors include a first communication descriptor, and the first communication descriptor corresponds to The first routing descriptor; the first communication descriptor includes the identification of the first application and the requirements of the first service data stream for network performance; the first routing descriptor includes the identification of the first network slice.
  • the processing unit 1002 is specifically configured to: obtain the identification of the application to which the first service data flow belongs and the network performance requirement of the first service data flow; if the identification of the application to which the first service data flow belongs is determined If the network performance requirement of the first service data stream matches the first communication descriptor, it is determined that the network slice corresponding to the first service data stream is the first network slice.
  • the communication unit 1003 may also be configured to send the first service data stream through the first network slice.
  • the communication unit 1003 may also be configured to: receive the first mapping information sent by the second network slice selection network element in the second network, and the first The mapping information is used to indicate that one or more network slices in the first network respectively correspond to a network slice in the second network.
  • One or more network slices in the first network include the first network slice, and the first network slice corresponds to The network slice in the second network is the second network slice, and the network performance of the second network slice matches the network performance of the first network slice; according to the first mapping information, it is sent through the second network slice corresponding to the first network slice The first business data flow.
  • the communication unit 1003 is configured to receive a network slice selection strategy from a policy control network element in the first network, and the network slice selection strategy is used to indicate the first network corresponding to the first application in the terminal device.
  • the processing unit 1002 is configured to slice from at least one network slice for the first service data stream to be sent according to the network slice selection strategy and the network performance of at least one network slice in the first network corresponding to the first application.
  • the first network slice is determined in, where the multiple service data streams of the first application include the first service data stream, and the network performance of the first network slice meets the network performance requirement of the first service data stream.
  • the communication unit 1003 may also be configured to send the first service data stream through the first network slice.
  • the communication unit 1003 may also be used to: receive the first mapping information from the second network slice selection network element in the second network, and the first mapping The information is used to indicate that one or more network slices in the first network respectively correspond to the network slices in the second network.
  • One or more network slices in the first network include the first network slice, and the first network slice corresponds to The network slice in the second network is the second network slice, and the network performance of the second network slice matches the network performance of the first network slice; further, according to the first mapping information, the second network slice corresponding to the first network slice is used Send the first service data stream.
  • the apparatus 1000 may also be a network device (such as a policy control network element) in any of the foregoing embodiments, or may also be a semiconductor chip provided in the network device.
  • the processing unit 1002 may support the device 1000 to execute the actions of the policy control network element in the above method examples.
  • the processing unit 1002 mainly supports the device 1000 in executing the internal actions of the policy control network element in the method example, and the communication unit 1003 can support the communication between the device 1000 and other devices or network elements.
  • the processing unit 1002 is used to support the device 1000 to perform step 201 in FIG. 2, and the communication unit 1003 is used to support the device 1000 to perform step 202 in FIG.
  • the processing unit 1002 is used to support the device 1000 to perform step 201 in FIG.
  • the communication unit 1003 is used to support the device 1000 to perform step 302 in FIG. 3; for another example, the processing unit 1002 is used to support the device 1000 to perform step 401 in FIG. 4, and the communication unit 1003 is used to support the device 1000 to perform step 302 in FIG.
  • the processing unit 1002 is used to support the device 1000 to perform the first NSSP generation action in FIG. 5, and the communication unit 1003 is used to support the device 1000 to perform step 501, step 502, and step 504 in FIG. 5; and
  • the processing unit 1002 is used to support the device 1000 to perform the action of generating the first NSSP in FIG.
  • the communication unit 1003 is used to support the device 1000 to perform step 601, step 602, and step 606 in FIG. 6; for another example, the processing unit 1002 For supporting the device 1000 to perform the action of generating the second NSSP in FIG. 7, the communication unit 1003 is used for supporting the device 1000 to perform step 701, step 702, and step 704 in FIG. 7; for another example, the processing unit 1002 is used for supporting the device 1000 To perform the action of generating the second NSSP in FIG. 8, the communication unit 1003 is used to support the device 1000 to perform step 801, step 802, and step 806 in FIG. 8; for another example, the processing unit 1002 is used to support the device 1000 to perform step 806 in FIG. In the action of generating the second NSSP, the communication unit 1003 is used to support the device 1000 to perform step 901, step 902, and step 906 in FIG. 9.
  • the processing unit 1002 is configured to generate a network slice selection strategy for the terminal device, and the network slice selection strategy is used to indicate the first network corresponding to the multiple service data streams of the first application in the terminal device.
  • the communication unit 1003 is used to send a network slice selection strategy to the terminal device.
  • the multiple service data streams of the first application include the first service data stream, and the network slice in the first network corresponding to the first service data stream is the first network slice;
  • the network performance meets the network performance requirements of the first service data stream.
  • the communication unit 1003 is also used to obtain application information and network slicing information of the terminal device.
  • the application information includes the identification of the first application and the requirements for network performance of multiple service data streams of the first application.
  • the network slice information includes the identification of one or more network slices in the first network, and the network performance of one or more network slices in the first network; the processing unit is also used to generate network slice selections according to application information and network slice information Strategy.
  • FIG. 11 is a schematic structural diagram of a terminal device 1100 according to an embodiment of the application. For ease of description, FIG. 11 only shows the main components of the terminal device. As shown in FIG. 11, the terminal device 1100 includes a processor, a memory, a control circuit, an antenna, and an input and output device. The terminal device 1100 can be applied to the system architecture shown in FIG. 1 to perform the functions of the terminal device in the foregoing method embodiment.
  • the processor is mainly used to process the communication protocol and communication data, and to control the entire terminal device, execute the software program, and process the data of the software program, for example, to control the terminal device to perform the actions described in the above method embodiment.
  • the memory is mainly used to store software programs and data.
  • the control circuit is mainly used for the conversion of baseband signals and radio frequency signals and the processing of radio frequency signals.
  • the control circuit and the antenna together can also be called a transceiver, which is mainly used to send and receive radio frequency signals in the form of electromagnetic waves.
  • Input and output devices such as touch screens, display screens, and keyboards, are mainly used to receive data input by users and output data to users.
  • the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program.
  • the processor performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit.
  • the radio frequency circuit performs radio frequency processing on the baseband signal and then sends the radio frequency signal to the outside in the form of electromagnetic waves through the antenna.
  • the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.
  • FIG. 11 only shows a memory and a processor. In actual terminal devices, there may be multiple processors and memories.
  • the memory may also be referred to as a storage medium or a storage device, etc., which is not limited in the embodiment of the present application.
  • the processor may include a baseband processor and a central processing unit.
  • the baseband processor is mainly used to process communication protocols and communication data.
  • the central processing unit is mainly used to control the entire terminal device and execute Software program, processing the data of the software program.
  • the processor in FIG. 11 integrates the functions of the baseband processor and the central processing unit.
  • the baseband processor and the central processing unit may also be independent processors and are interconnected by technologies such as buses.
  • the terminal device may include multiple baseband processors to adapt to different network standards, the terminal device may include multiple central processors to enhance its processing capabilities, and various components of the terminal device may be connected through various buses.
  • the baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip.
  • the central processing unit can also be expressed as a central processing circuit or a central processing chip.
  • the function of processing the communication protocol and communication data can be built in the processor, or can be stored in the storage unit in the form of a software program, and the processor executes the software program to realize the baseband processing function.
  • the antenna and control circuit with the transceiver function can be regarded as the communication unit of the device 1000, and the processor with processing function Considered as the processing unit of the device 1000.
  • the terminal device 1100 includes a communication unit 1101 and a processing unit 1102.
  • the communication unit 1101 may also be called a transceiver, a transceiver, a transceiving device, and so on.
  • the device for implementing the receiving function in the communication unit 1101 can be regarded as the receiving unit, and the device for implementing the sending function in the communication unit 1101 can be regarded as the sending unit, that is, the communication unit 1101 includes a receiving unit and a sending unit.
  • the receiving unit may also be called a receiver, a receiver, a receiving circuit, etc.
  • the sending unit may be called a transmitter, a transmitter, or a transmitting circuit, etc.
  • the terminal device 1100 shown in FIG. 11 can implement various processes involving the terminal device in the method embodiments illustrated in FIG. 2 to FIG. 9.
  • the operation and/or function of each module in the terminal device 1100 are respectively for implementing the corresponding process in the foregoing method embodiment.
  • FIG. 12 is a schematic structural diagram of an apparatus provided by an embodiment of this application.
  • the apparatus 1200 may be the policy control network element described in the foregoing method embodiment.
  • the apparatus 1200 may be used to implement the content described in the foregoing method embodiment, and for details, refer to the description in the foregoing method embodiment.
  • the apparatus 1200 may include one or more processors 1201, and the processor 1201 may also be referred to as a processing unit, which may implement certain control functions.
  • the processor 1201 may be a general-purpose processor or a special-purpose processor, for example, a baseband processor.
  • the processor 1201 may also store instructions and/or data 1203, and the instructions and/or data 1203 may be executed by the processor, so that the apparatus 1200 executes the method described in the foregoing method embodiments. Methods.
  • the processor 1201 may include a transceiver unit for implementing receiving and sending functions.
  • the transceiver unit may be a transceiver circuit or an interface.
  • the circuits or interfaces used to implement the receiving and sending functions can be separate or integrated.
  • the apparatus 1200 may include a circuit, and the circuit may implement the sending or receiving function in the foregoing method embodiment.
  • the apparatus 1200 may include one or more memories 1202, on which instructions 1204 may be stored, and the instructions may be executed on the processor, so that the apparatus 1200 executes the description in the above embodiments Methods.
  • data may also be stored in the memory.
  • instructions and/or data may also be stored in the processor.
  • the processor and memory can be provided separately or integrated together.
  • the apparatus 1200 may further include a transceiver 1205 and/or an antenna 1206.
  • the processor 1201 may be called a processing unit, and controls the device.
  • the transceiver 1205 may be called a transceiver unit, a transceiver, a transceiver circuit or a transceiver, etc., and is used to implement the transceiver function of the device.
  • the apparatus 1200 may include a processor 1201 and a transceiver 1205.
  • the steps in the method provided in this embodiment can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the aforementioned processor may be a general-purpose central processing unit (central processing unit, CPU), general-purpose processor, digital signal processing (digital signal processing, DSP), application specific integrated circuits (ASIC), field programmable gate array Field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof; it can also be a combination that implements computing functions, such as a combination of one or more microprocessors, DSP and micro-processing The combination of the device, etc.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the memory or storage unit in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electronic Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • serial link DRAM SLDRAM
  • direct rambus RAM direct rambus RAM
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer programs or instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer program or instruction may be stored in a computer-readable storage medium, or transmitted through the computer-readable storage medium.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server integrating one or more available media.
  • the usable medium may be a magnetic medium, such as a floppy disk, a hard disk, and a magnetic tape; it may also be an optical medium, such as a DVD; it may also be a semiconductor medium, such as a solid state disk (SSD).
  • the various illustrative logic units and circuits described in the embodiments of this application can be implemented by general-purpose processors, digital signal processors, application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, Discrete gates or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions.
  • the general-purpose processor may be a microprocessor, and optionally, the general-purpose processor may also be any traditional processor, controller, microcontroller, or state machine.
  • the processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration achieve.
  • the steps of the method or algorithm described in the embodiments of the present application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • the software unit can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other storage medium in the art.
  • the storage medium may be connected to the processor, so that the processor can read information from the storage medium, and can store and write information to the storage medium.
  • the storage medium may also be integrated into the processor.
  • the processor and the storage medium can be arranged in an ASIC, and the ASIC can be arranged in a terminal device.
  • the processor and the storage medium may also be arranged in different components in the terminal device.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention se rapporte au domaine technique des communications. L'invention concerne un appareil et un procédé de sélection de tranches de réseaux. Le procédé comprend les étapes suivantes : un dispositif terminal reçoit une politique de sélection de tranches de réseaux à partir d'un élément de réseau de commande de politique dans un premier réseau, la politique de sélection de tranches de réseaux servant à indiquer des tranches de réseau dans le premier réseau correspondant respectivement à de multiples flux de données de service d'une première application dans le dispositif terminal, les multiples flux de données de service de la première application comprenant un premier flux de données de service ; puis le dispositif terminal peut déterminer, selon la politique de sélection de tranches de réseaux, qu'une tranche de réseau dans le premier réseau, correspondant à un premier flux de données de service à envoyer, constitue une première tranche de réseau. Grâce au procédé, un dispositif terminal peut déterminer, selon une politique de sélection de tranches de réseaux, des tranches de réseau dans un premier réseau correspondant respectivement à de multiples flux de données de service d'une première application, afin que différents flux de données de service de la même application puissent être transmis par l'intermédiaire de différentes tranches de réseau.
PCT/CN2020/078084 2019-03-19 2020-03-05 Procédé et appareil de sélection de tranches de réseaux WO2020187052A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910210064.7A CN111726839B (zh) 2019-03-19 2019-03-19 一种网络切片选择方法及装置
CN201910210064.7 2019-03-19

Publications (1)

Publication Number Publication Date
WO2020187052A1 true WO2020187052A1 (fr) 2020-09-24

Family

ID=72519662

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/078084 WO2020187052A1 (fr) 2019-03-19 2020-03-05 Procédé et appareil de sélection de tranches de réseaux

Country Status (2)

Country Link
CN (1) CN111726839B (fr)
WO (1) WO2020187052A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113572864A (zh) * 2021-07-21 2021-10-29 腾讯科技（深圳）有限公司 一种数据处理方法、网元设备以及可读存储介质
CN114258010A (zh) * 2020-09-25 2022-03-29 中国移动通信有限公司研究院 信息处理方法、装置、设备及可读存储介质
CN114301831A (zh) * 2021-12-10 2022-04-08 中国联合网络通信集团有限公司 一种业务传输方法、装置及存储介质

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113949634A (zh) 2020-07-16 2022-01-18 华为技术有限公司 一种报文传输的方法、装置及系统
CN112333770B (zh) * 2020-11-06 2023-10-13 中国联合网络通信集团有限公司 网络切片的选择方法及装置、切片映射系统、网络设备
CN112566120B (zh) * 2020-12-02 2023-10-27 中国联合网络通信集团有限公司 切片管理方法、装置、系统及业务订购服务器
CN114666232A (zh) * 2020-12-04 2022-06-24 中兴通讯股份有限公司 数据传输方法、用户设备及存储介质
CN112737980B (zh) * 2020-12-15 2022-07-29 云南电网有限责任公司 基于时间的网络切片资源动态划分方法及装置
CN114765582B (zh) * 2020-12-30 2023-11-17 华为技术有限公司 数据传输方法、设备及系统
CN113271592B (zh) * 2021-04-01 2024-01-12 维沃移动通信有限公司 数据传输方法、装置和电子设备
CN113068226A (zh) * 2021-04-06 2021-07-02 中国联合网络通信集团有限公司 流量控制方法、流量控制规则同步方法、终端、服务器
CN115442300A (zh) * 2021-06-04 2022-12-06 华为技术有限公司 报文转发方法、装置及通信网络
CN115580919A (zh) * 2021-06-21 2023-01-06 华为技术有限公司 一种网络切片选择方法及相关装置
CN113179518B (zh) * 2021-06-30 2021-10-26 中移(上海)信息通信科技有限公司 一种数据传输方法、数据传输装置、数据传输设备及终端
WO2023102947A1 (fr) * 2021-12-10 2023-06-15 Nokia Shanghai Bell Co., Ltd. Remappage de tranche de réseau
CN114258154B (zh) * 2021-12-30 2023-05-12 中国联合网络通信集团有限公司 会话方法、终端及会话功能实体设备
CN114553701B (zh) * 2022-02-18 2024-05-24 中国电信股份有限公司 切片标识管理方法、装置、设备及介质
CN114666863A (zh) * 2022-03-25 2022-06-24 Oppo广东移动通信有限公司 数据路由方法及装置
CN117279058A (zh) * 2022-06-20 2023-12-22 华为技术有限公司 通信方法、装置和系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107040481A (zh) * 2016-02-04 2017-08-11 中兴通讯股份有限公司 一种网络切片选择方法、策略生成方法及网络节点
WO2018205150A1 (fr) * 2017-05-09 2018-11-15 华为技术有限公司 Procédé et appareil de mise à jour de politique de sélection de tronçon de réseau
CN109257771A (zh) * 2018-11-16 2019-01-22 腾讯科技（深圳）有限公司 业务数据的传输方法、装置及设备
CN110324284A (zh) * 2018-03-30 2019-10-11 华为技术有限公司 接入ims的方法和通信装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109391648B (zh) * 2017-08-04 2020-12-22 华为技术有限公司 一种应用与网络切片的关联方法、装置和通信系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107040481A (zh) * 2016-02-04 2017-08-11 中兴通讯股份有限公司 一种网络切片选择方法、策略生成方法及网络节点
WO2018205150A1 (fr) * 2017-05-09 2018-11-15 华为技术有限公司 Procédé et appareil de mise à jour de politique de sélection de tronçon de réseau
CN110324284A (zh) * 2018-03-30 2019-10-11 华为技术有限公司 接入ims的方法和通信装置
CN109257771A (zh) * 2018-11-16 2019-01-22 腾讯科技（深圳）有限公司 业务数据的传输方法、装置及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Enhanced IMS to 5GC Integration (Release 16)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.794, no. V1.0.0, 14 March 2019 (2019-03-14), pages 1 - 83, XP051722778 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114258010A (zh) * 2020-09-25 2022-03-29 中国移动通信有限公司研究院 信息处理方法、装置、设备及可读存储介质
CN113572864A (zh) * 2021-07-21 2021-10-29 腾讯科技（深圳）有限公司 一种数据处理方法、网元设备以及可读存储介质
CN113572864B (zh) * 2021-07-21 2023-06-20 腾讯科技（深圳）有限公司 一种数据处理方法、网元设备以及可读存储介质
CN114301831A (zh) * 2021-12-10 2022-04-08 中国联合网络通信集团有限公司 一种业务传输方法、装置及存储介质
CN114301831B (zh) * 2021-12-10 2023-07-07 中国联合网络通信集团有限公司 一种业务传输方法、装置及存储介质

Also Published As

Publication number Publication date
CN111726839B (zh) 2022-03-29
CN111726839A (zh) 2020-09-29

Similar Documents

Publication Publication Date Title
WO2020187052A1 (fr) Procédé et appareil de sélection de tranches de réseaux
JP7183416B2 (ja) 時間依存ネットワーキング通信方法及び装置
US11812496B2 (en) User group session management method and apparatus
WO2019126931A1 (fr) Contrôle de qualité de service (qos) dans l'informatique de périphérie mobile (mec)
US20220217611A1 (en) Service Configuration Method, Communication Apparatus, and Communication System
WO2020007202A1 (fr) Procédé, dispositif et système de transmission de données
US20210282053A1 (en) Transfer policy determining method, and apparatus
US20220338106A1 (en) Slice control method and apparatus
WO2022105897A1 (fr) Procédé d'établissement de chemin de service, appareil de communication et support d'enregistrement
US11824783B2 (en) Maximum data burst volume (MDBV) determining method, apparatus, and system
WO2018233451A1 (fr) Procédé, appareil et système de communication
US20220263879A1 (en) Multicast session establishment method and network device
WO2021227600A1 (fr) Procédé de commande de tranche de réseau et appareil de communication
WO2023179238A1 (fr) Procédé de synchronisation, appareil de communication et système de communication
WO2022267652A1 (fr) Procédé de communication, appareil de communication et système de communication
US10091645B1 (en) Handling mobile device administration in anchorless mobile networks
WO2021134347A1 (fr) Procédé, appareil et système d'attribution de ressources
CN114514764A (zh) 设备、方法和计算机程序
WO2023050781A1 (fr) Procédé de communication et appareil de communication
WO2024109221A1 (fr) Procédé et appareil de mise en correspondance de tranches de réseau
WO2023213177A1 (fr) Procédé et appareil de communication
US20240080716A1 (en) Wireless communication method, communication apparatus, and communication system
WO2023082858A1 (fr) Procédé de détermination de politique de gestion de mobilité, appareil de communication et système de communication
WO2023061207A1 (fr) Procédé de communication, appareil de communication et système de communication
WO2023231465A1 (fr) Procédé de synchronisation temporelle, appareil de communication et système 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: 20773049

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

Country of ref document: EP

Kind code of ref document: A1