Wireless communication method, terminal device and network device
By configuring and indicating the index list of S-NSSAI, the problem of how the base station lets the terminal device know the network slice it supports is solved, achieving the effect of resource conservation and privacy protection.
Patent Information
- Application Number
- CN202310334941.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-01-29
- Publication Date
- 2025-03-21
- Estimated Expiration
- 2041-01-29
AI Technical Summary
In 5G systems, how base stations let terminal devices know the network slicing they support is an urgent problem, especially when different cells may support different network slicing.
By configuring the index list of S-NSSAI of the index information of part or all of the S-NSSAIs of the serving network and indicating it to the terminal device, the terminal device can obtain the network slice supported by the base station.
This method avoids the slicing information supported by the base station directly broadcasts the service network, saves broadcast resources, and solves the problem of privacy exposure, while ensuring that the terminal device can correctly select the supported network slices.
Smart Images

Figure CN116367269B_ABST
Abstract
Description
[0001] This application is a divisional application of an application with a filing date of January 29, 2021, application number 2021800441483, and invention name “Method, terminal device and network device for wireless communication”. Technical Field
[0002] The embodiments of the present application relate to the field of communications, and more specifically, to a wireless communication method, terminal equipment, and network equipment. Background Art
[0003] In the 5G system, network slicing is deployed. Considering that different cells may support different network slices, in order for the terminal device to select a cell that supports the slice it wants to use, the base station needs to let the terminal device know the network slices supported by the base station. However, how the base station lets the terminal device know the network slices it supports is an urgent problem to be solved. Summary of the invention
[0004] An embodiment of the present application provides a wireless communication method, a terminal device, and a network device. The network device can configure an S-NSSAI index list including index information of part or all of the S-NSSAI of a service network, and indicate the S-NSSAI index list to the terminal device, so that the terminal device knows the network slices supported by the base station.
[0005] In a first aspect, a wireless communication method is provided, the method comprising:
[0006] The terminal device receives the first information; wherein,
[0007] The first information includes an S-NSSAI index list, where the S-NSSAI index list includes index information of part or all of the S-NSSAI of the serving network.
[0008] In a second aspect, a wireless communication method is provided, the method comprising:
[0009] The network device sends first information to the terminal device; wherein,
[0010] The first information includes an S-NSSAI index list, where the S-NSSAI index list includes index information of part or all of the S-NSSAI of the serving network.
[0011] In a third aspect, a terminal device is provided for executing the method in the first aspect.
[0012] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect.
[0013] In a fourth aspect, a network device is provided for executing the method in the second aspect.
[0014] Specifically, the network device includes a functional module for executing the method in the above second aspect.
[0015] In a fifth aspect, a terminal device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect.
[0016] In a sixth aspect, a network device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect.
[0017] In a seventh aspect, a device is provided for implementing the method in any one of the first to second aspects above.
[0018] Specifically, the apparatus includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the apparatus executes the method in any one of the first to second aspects described above.
[0019] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method in any one of the first to second aspects above.
[0020] In a ninth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to second aspects above.
[0021] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects above.
[0022] Through the above technical solution, the network device can configure an S-NSSAI index list including index information of part or all of the S-NSSAI of the service network, and indicate the S-NSSAI index list to the terminal device, so that the terminal device knows the network slices supported by the base station. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] Figure 1 It is a schematic diagram of a communication system architecture applied in an embodiment of the present application.
[0024] Figure 2 It is a schematic flowchart of a wireless communication method provided according to an embodiment of the present application.
[0025] Figure 3 It is a schematic flowchart of configuring an index list of S-NSSAI provided according to an embodiment of the present application.
[0026] Figure 4 It is a schematic flowchart of another configuration of an S-NSSAI index list provided according to an embodiment of the present application.
[0027] Figure 5 It is a schematic block diagram of a terminal device provided according to an embodiment of the present application.
[0028] Figure 6 It is a schematic block diagram of a network device provided according to an embodiment of the present application.
[0029] Figure 7 It is a schematic block diagram of a communication device provided according to an embodiment of the present application.
[0030] Figure 8 It is a schematic block diagram of a device provided according to an embodiment of the present application.
[0031] Fig. 9 It is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION
[0032] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. For the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0033] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.
[0034] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.
[0035] In some embodiments, the communication system in the embodiments of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.
[0036] In some embodiments, the communication system in the embodiments of the present application can be applied to unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiments of the present application can also be applied to licensed spectrum, where the licensed spectrum can also be considered as an unshared spectrum.
[0037] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
[0038] The terminal device can be a station (STATION, ST) in a WLAN, a cellular phone, a wireless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.
[0039] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).
[0040] In the embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.
[0041] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.
[0042] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device or base station (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.
[0043] As an example and not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. In some embodiments, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments, the network device may also be a base station set up in a location such as land or water.
[0044] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
[0045] Figure 1 A schematic diagram of a communication system 100 used in the present application is shown as an example. Figure 1As shown, the communication system 100 mainly includes a terminal device (User Equipment, UE) 101, an access network (Access Network, AN) device 102, an access and mobility management function (Access and Mobility Management Function, AMF) entity 103, a session management function (Session Management Function, SMF) entity 104, a user plane function (User Plane Function, UPF) entity 105, a policy control function (Policy Control function, PCF) entity 106, a unified data management (Unified Data Management, UDM) entity 107, a data network (Data Network, DN) 108, an application function (Application Function, AF) entity 109, an authentication server function (Authentication Server Function, AUSF) entity 110, and a network slice selection function (Network Slice Selection Function, NSSF) entity 111.
[0046] Specifically, in the communication system 100, the UE 101 is connected to the AN device 102 through the Uu interface for access layer connection to exchange access layer messages and wireless data transmission, and the UE 101 is connected to the AMF entity 103 through the N1 interface for non-access layer (Non-Access Stratum, NAS) to exchange NAS messages; the AN device 102 is connected to the AMF entity 103 through the N2 interface, and the AN device 102 is connected to the UPF entity 105 through the N3 interface; multiple UPF entities 105 are connected through the N9 interface, and the UPF entity 105 is connected to the DN through the N6 interface. 108 is connected, and at the same time, the UPF entity 105 is connected to the SMF entity 104 through the N4 interface; the SMF entity 104 is connected to the PCF entity 106 through the N7 interface, the SMF entity 104 is connected to the UDM entity 107 through the N10 interface, the SMF entity 104 controls the UPF entity 105 through the N4 interface, and at the same time, the SMF entity 104 is connected to the AMF entity 103 through the N11 interface; multiple AMF entities 103 are connected through the N14 interface, the AMF entity 103 is connected to the UDM entity 107 through the N8 interface, the AMF entity 103 is connected to the AUSF entity 110 through the N12 interface, the AMF entity 103 is connected to the NSSF entity 111 through the N22 interface, and at the same time, the AMF entity 103 is connected to the PCF entity 106 through the N15 interface; the PCF entity 106 is connected to the AF entity 109 through the N5 interface; the AUSF entity 110 is connected to the UDM entity 107 through the N13 interface.
[0047] In the communication system 100, the UDM entity 107 is a subscription database in the core network, which stores the subscription data of users in the 5G network. The AMF entity 103 is a mobility management function in the core network, and the SMF entity 104 is a session management function in the core network. In addition to the mobility management of the UE 101, the AMF entity 103 is also responsible for forwarding session management related messages between the UE 101 and the SMF entity 104. The PCF entity 106 is a policy management function in the core network, which is responsible for formulating policies related to the mobility management, session management, and billing of the UE 101. The UPF entity 105 is a user plane function in the core network, which transmits data with the external data network through the N6 interface and with the AN device 102 through the N3 interface. After the UE 101 accesses the 5G network through the Uu port, a protocol data unit (PDU) session data connection is established from the UE 101 to the UPF entity 105 under the control of the SMF entity 104, so as to transmit data. The AMF entity 103 and the SMF entity 104 obtain user subscription data from the UDM entity 107 through the N8 and N10 interfaces respectively, and obtain policy data from the PCF entity 106 through the N15 and N7 interfaces.
[0048] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0049] The terms used in the implementation mode of this application are only used to explain the specific embodiments of this application, and are not intended to limit this application. The terms "first", "second", "third" and "fourth" in the specification and claims of this application and the drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.
[0050] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.
[0051] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.
[0052] In the embodiments of the present application, "pre-definition" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.
[0053] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.
[0054] In order to facilitate a better understanding of the embodiments of the present application, the network slices related to the present application are explained.
[0055] Network slices can be identified using Single-Network Slice Selection Assistance Information (S-NSSAI). The collection of S-NSSAI is called Network Slice Selection Assistance Information (NSSAI).
[0056] When a terminal device needs to use a network slice, it must first request the use of the slice from the network. After the network agrees, it will establish a protocol data unit (PDU) session in the slice to transmit data.
[0057] The terminal device puts the requested S-NSSAI in the requested NSSAI according to the service, and the requested NSSAI is included in the registration request and sent to the AMF entity. The AMF entity determines the allowed NSSAI according to the scope of the terminal device contract and network slice deployment, and puts it in the registration accept to send to the terminal device, and also puts it in the N2 message to send to the base station radio access network (RAN).
[0058] After receiving the Allowed NSSAI, the terminal device needs to establish a PDU session in the slice in the Allowed NSSAI. Data can be sent and received only after the PDU session is established.
[0059] During network deployment, the coverage of each slice may be different. When the AMF entity determines the Allowed NSSAI, it needs to ensure that all slices in the Allowed NSSAI can cover the registration area (Tracking Area, TA) list assigned to the terminal device by the AMF entity. The AMF entity obtains the S-NSSAI and corresponding TA supported by the base station from the base station through the Next Generation Evolutional NodeB (NG-eNB) setup request (NG-eNB setup request) or RAN configuration update (RAN configuration update) signaling.
[0060] In Release 17, considering that different cells may support different network slices, in order for the terminal device to select a cell that supports the slice it wants to use, the base station needs to let the terminal device know the network slices supported by the base station.
[0061] If the base station directly puts the slice information, such as S-NSSAI (32 bits), in the broadcast information, because the base station may support multiple slices, it needs to broadcast multiple S-NSSAIs, which will make the broadcast information too large and occupy too many broadcast resources.
[0062] In addition, because S-NSSAI may be defined by the operator, there is a problem of privacy exposure if it is placed directly in the broadcast information.
[0063] Based on the above problems, the present application proposes a solution for configuring an index list of S-NSSAI. The network device can configure an index list of S-NSSAI including index information of part or all of the S-NSSAI of the service network, and indicate the index list of S-NSSAI to the terminal device, so that the terminal device can know the network slices supported by the base station.
[0064] The technical solution of the present application is described in detail below through specific embodiments.
[0065] Figure 2 is a schematic flow chart of a wireless communication method 200 according to an embodiment of the present application, such as Figure 2 As shown, the method 200 may include at least part of the following contents:
[0066] S210, the network device sends first information to the terminal device; wherein,
[0067] The first information includes an S-NSSAI index list, where the S-NSSAI index list includes index information of part or all of the S-NSSAIs of the serving network;
[0068] S220: The terminal device receives the first information.
[0069] In an embodiment of the present application, the terminal device can determine part or all of the S-NSSAI supported by the service network based on the index list of S-NSSAI, thereby avoiding the network device directly broadcasting part or all of the S-NSSAI supported by the service network, which occupies too many broadcast resources and causes privacy exposure issues.
[0070] It should be noted that the S-NSSAI index list is a form of expression of the index information of part or all of the S-NSSAI of the service network. The index information of part or all of the S-NSSAI of the service network can also be expressed through an S-NSSAI index set or similar concepts, which is not limited in the embodiments of the present application.
[0071] In some embodiments, the service network is a Public Land Mobile Network (PLMN) or a Stand-alone Non-public Networks (SNPN).
[0072] In some embodiments, the terminal device may perform at least one of the following according to the index list of the S-NSSAI:
[0073] Cell selection, cell reselection, and search before cell switching.
[0074] For example, after the terminal device obtains the index list of S-NSSAI, the terminal device saves the index list of S-NSSAI, and sends the index list of S-NSSAI or the S-NSSAI or S-NSSAI index corresponding to the service to the access stratum (AS) (such as the radio resource control (RRC) layer) of the terminal device. The AS layer of the terminal device uses the index to select a cell that can support these indexes as the resident cell of the terminal device.
[0075] In some embodiments, the first information is included in a non-access stratum (NAS) message, or the first information is included in an RRC message.
[0076] For example, in the case where the first information is included in a NAS message, the network device is an AMF entity.
[0077] For example, when the first information is included in the RRC message, the network device is a serving base station.
[0078] As Example 1, the first information is included in a NAS message. For example, the network device is an AMF entity, that is, the AMF entity sends the first information to the terminal device.
[0079] In Example 1, for example, the service network is a visited network. For example, the service network is a visited PLMN (visited-PLMN, V-PLMN), or the service network is a visited SNPN (visited-SNPN, V-SNPN).
[0080] In Example 1, for example, the S-NSSAI index list includes index information of all S-NSSAIs of the serving network.
[0081] For example, the index information of some S-NSSAIs among the index information of all S-NSSAIs includes the index information of the S-NSSAI to which the terminal device has subscribed.
[0082] In one implementation of Example 1, the index list of the S-NSSAI may be generated by an AMF entity. For example, the AMF entity generates the index list of the S-NSSAI according to the index corresponding to the S-NSSAI of the service network.
[0083] Specifically, taking the service network as PLMN as an example, SNPN is similar. If the AMF entity is locally configured with the index corresponding to the slice, an index list of the subscribed S-NSSAI is generated. If the AMF entity is the AMF of the V-PLMN, the V-PLMN S-NSSAI corresponding to the subscribed slice is found, and an index list of the V-PLMN S-NSSAI is generated. In other words, the index corresponding to the S-NSSAI of the current PLMN is unique in the entire PLMN.
[0084] In another implementation of Example 1, the index list of the S-NSSAI may be generated by the NSSF entity. For example, the AMF entity receives the index list of the S-NSSAI sent by the NSSF entity.
[0085] Specifically, taking the service network as PLMN as an example, SNPN is similar. The AMF entity sends the contracted slice and contracted slice change indication of the terminal device to the NSSF entity, and may indicate that the NSSF entity needs to provide an index list of S-NSSAI. The NSSF entity generates an index list of subscribed S-NSSAI based on the contracted slice and contracted slice change indication of the terminal device. If the NSSF entity is the NSSF entity of the V-PLMN, the V-PLMN S-NSSAI corresponding to the contracted slice is found, and an index list of V-PLMN S-NSSAI is generated. The index is unique in the entire PLMN. The NSSF entity can also determine the allowed NSSAI. If a contracted slice change indication is received, a configured NSSAI (also called subscribed S-NSSAIs) is generated at the same time. The index list of S-NSSAI can be part of the configured NSSAI, or a separate parameter. The NSSF entity sends the index list of S-NSSAI, allowed NSSAI, and configured NSSAI to the AMF entity.
[0086] In an implementation manner of Example 1, the first information is registration acceptance information (Registration accept) for registration request information (Registration request) sent by the terminal device, and the registration request information corresponds to one of initial registration, mobility registration, and emergency registration.
[0087] In another implementation of Example 1, the first information is a configuration update command.
[0088] In some implementations of Example 1, the first information further includes at least one of the following:
[0089] Allowed NSSAI, configured NSSAI, and network slicing indication information (Network slicing indication) used to indicate whether the contracted slice has changed.
[0090] In Example 1, for example, when the network slice indication information indicates that the contracted slice has changed, the terminal device deletes the index information of the S-NSSAI of other networks except the service network. In other words, the network slice indication information is used by the terminal device to delete the index information of the S-NSSAI of other networks except the service network.
[0091] For example, when the network slice indication information indicates that the contracted slice has changed, the terminal device deletes the index information of the S-NSSAI of other PLMNs except the serving PLMN.
[0092] As Example 2, the first information is included in an RRC message. For example, the network device is a serving base station, that is, the serving base station sends the first information to the terminal device.
[0093] In some implementations of Example 2, the S-NSSAI index list includes index information of a portion of the S-NSSAI of the service network, wherein the portion of the S-NSSAI includes the S-NSSAI supported by the cell and the S-NSSAI supported by the neighboring cells of the cell.
[0094] In some implementations of Example 2, when the service network and the first network share a service base station, the index list of the S-NSSAI includes index information of part of the S-NSSAI of the service network and index information of part of the S-NSSAI of the first network, wherein the part of the S-NSSAI includes the S-NSSAI supported by the cell and the S-NSSAI supported by the neighboring cells of the cell. That is, in this case, the index list of the S-NSSAI also includes the identifier or index of the service network and the identifier or index of the first network.
[0095] In Example 2, for example, the serving base station receives an index list of the S-NSSAI sent by the AMF entity.
[0096] Specifically, if there is no local configuration on the base station side, the AMF entity configures the index list of S-NSSAI, which includes the S-NSSAI index information supported by the cell (current cell or serving cell) and the S-NSSAI index information supported by the neighboring cells of the cell. The index is unique in the entire PLMN.
[0097] In Example 2, for example, the RRC message is an RRC connection establishment message, or the RRC message is an RRC connection reconfiguration message, or a new RRC message.
[0098] In some embodiments, the serving base station may broadcast the index corresponding to the S-NSSAI it supports, thereby saving broadcast resources while protecting privacy.
[0099] Therefore, in an embodiment of the present application, the network device can configure an S-NSSAI index list including index information of part or all of the S-NSSAI of the service network, and indicate the S-NSSAI index list to the terminal device, so that the terminal device knows the network slices supported by the base station.
[0100] As embodiment 1, the AMF entity configures the index list of S-NSSAI through the NAS layer, and the terminal device can Figure 3 The process shown obtains the index list of S-NSSAI. Figure 3 The process shown may specifically include S11 to S16.
[0101] S11, if the terminal device has not registered with the network, the terminal device sends a registration request to the AMF entity, which corresponds to one of the initial registration, mobility registration, and emergency registration;
[0102] S12: If the AMF entity does not have the network slice subscribed by the terminal device, it obtains it from the UDM entity; or, when the network slice subscribed by the terminal device changes, the UDM entity sends the updated subscribed slice to the AMF entity; if the AMF entity is the AMF of the V-PLMN, the UDM entity also sends a subscribed slice change indication to the V-AMF (i.e., the AMF of the V-PLMN);
[0103] S13, the (V-)AMF entity sends the slices subscribed by the terminal device and the indication of the change of the subscribed slice to the NSSF entity. If the AMF entity is V-AMF, the V-AMF entity sends the slices subscribed by the terminal device and the indication of the change of the subscribed slice to the V-NSSF entity (i.e., the NSSF of the V-PLMN), and may indicate that the NSSF entity needs to provide an index list of S-NSSAI;
[0104] In some embodiments, if the AMF entity is locally configured with an index corresponding to a slice, an index list of the subscribed S-NSSAI is generated; if the AMF entity is the AMF of the V-PLMN, the V-PLMN S-NSSAI corresponding to the subscribed slice is found, and an index list of the V-PLMN S-NSSAI is generated; that is, the index corresponding to the S-NSSAI of the current PLMN is unique in the entire PLMN;
[0105] S14, the (V-)NSSF entity generates an index list of subscribed S-NSSAI according to the subscribed slice and the subscribed slice change indication of the terminal device. If the NSSF entity is the NSSF of the V-PLMN (i.e., V-NSSF), it finds the V-PLMN S-NSSAI corresponding to the subscribed slice and generates an index list of the V-PLMN S-NSSAI, which is unique in the entire PLMN; the (V-)NSSF entity can also determine the allowed NSSAI. If a subscription slice change indication is received, a configured NSSAI (also referred to as subscribed S-NSSAIs) is generated at the same time; the index list of S-NSSAI can be part of the configured NSSAI, or a separate parameter; in addition, the (V-)NSSF sends the index list of S-NSSAI, allowed NSSAI, and configured NSSAI to the (V-)AMF;
[0106] S15a, if the above S11 is executed, the (V-)AMF replies a Registration accept to the terminal device, which includes an index list of S-NSSAI, allowed NSSAI, configured NSSAI, and a Network slicing indication for indicating whether the contracted slice has changed;
[0107] S15b: If the above S11 is not executed, the UDM entity updates the contracted slice to the (V-)AMF, then the AMF entity sends a configuration update command to the terminal device, which includes the index list of S-NSSAI, allowed NSSAI, and configured NSSAI;
[0108] S16, the terminal device saves the index list of S-NSSAI, which is associated with the current PLMN, and sends the list or the slices and their indexes corresponding to the service as needed to the AS layer, such as the RRC layer; the AS layer uses the index to find cells that can support these indexes as its resident cells. If the terminal device also receives the Network slicing indication indicating that the contracted slice has changed, the terminal device deletes the indexes corresponding to other PLMNs.
[0109] As embodiment 2, the serving base station configures the index list of S-NSSAI through the RRC layer, and the terminal device can Figure 4The process shown obtains the index list of S-NSSAI. Figure 4 The process shown may specifically include S21 to S23.
[0110] S21, if the serving base station has no local configuration, the AMF entity configures the S-NSSAI index list, and sends the S-NSSAI index list to the serving base station through the N2 message. The S-NSSAI index list includes the S-NSSAI index information supported by the cell (current cell or serving cell) and the S-NSSAI index information supported by the neighboring cells of the cell. The index is unique in the entire PLMN;
[0111] S22, the serving base station sends the index list of the S-NSSAI to the terminal device through an RRC message; wherein the RRC message may be an RRC connection establishment message, an RRC connection reconfiguration message or a new RRC message;
[0112] S23, the terminal device saves the index list of the S-NSSAI. The terminal device uses the indexes in the index list of the S-NSSAI to search for cells that support these indexes as its resident cells.
[0113] It should be noted that the above-mentioned Embodiment 1 and Embodiment 2 are described by taking the service network as PLMN as an example. Of course, the service network as SNPN is also applicable, and will not be described in detail here.
[0114] Combination of the above Figures 2 to 4 , describes in detail the method embodiment of the present application, and the following is combined with Figures 5 to 9 , the device embodiments of the present application are described in detail. It should be understood that the device embodiments and the method embodiments correspond to each other, and similar descriptions can refer to the method embodiments.
[0115] Figure 5 FIG. 3 shows a schematic block diagram of a terminal device 300 according to an embodiment of the present application. Figure 5 As shown, the terminal device 300 includes:
[0116] The communication unit 310 is used to receive the first information; wherein,
[0117] The first information includes an index list of single network slice auxiliary information S-NSSAI, and the index list of S-NSSAI includes index information of part or all of the S-NSSAI of the service network.
[0118] In some embodiments, the first information is included in a non-access stratum (NAS) message.
[0119] In some embodiments, the S-NSSAI index list includes index information of all S-NSSAIs of the serving network.
[0120] In some embodiments, the index information of some S-NSSAIs among the index information of all S-NSSAIs includes the index information of the S-NSSAIs subscribed by the terminal device.
[0121] In some embodiments, the first information is registration acceptance information for registration request information sent by the terminal device, and the registration request information corresponds to one of initial registration, mobility registration, and emergency registration.
[0122] In some embodiments, the first information is a configuration update command.
[0123] In some embodiments, the serving network is a visited network.
[0124] In some embodiments, the first information further includes at least one of the following:
[0125] Allowed network slice auxiliary information NSSAI, configured NSSAI, and network slice indication information used to indicate whether the contracted slice has changed.
[0126] In some embodiments, the terminal device 300 further includes: a processing unit 320,
[0127] When the network slice indication information indicates that the contracted slice has changed, the processing unit 320 is used to delete the index information of the S-NSSAI of other networks except the service network.
[0128] In some embodiments, the communication unit 310 is specifically used to:
[0129] Receive the first information sent by the AMF entity.
[0130] In some embodiments, the first information is included in a radio resource control (RRC) message.
[0131] In some embodiments, the index list of the S-NSSAI includes index information of a portion of the S-NSSAI of the service network, wherein the portion of the S-NSSAI includes the S-NSSAI supported by the cell and the S-NSSAI supported by the neighboring cells of the cell.
[0132] In some embodiments, when the service network shares a service base station with the first network, the index list of the S-NSSAI includes index information of part of the S-NSSAI of the service network and index information of part of the S-NSSAI of the first network, wherein the part of the S-NSSAI includes the S-NSSAI supported by the cell and the S-NSSAI supported by the neighboring cells of the cell.
[0133] In some embodiments, the RRC message is an RRC connection establishment message, or the RRC message is an RRC connection reconfiguration message.
[0134] In some embodiments, the communication unit 310 is specifically used to:
[0135] The first information sent by the serving base station is received.
[0136] In some embodiments, the terminal device 300 further includes: a processing unit 320,
[0137] The processing unit 320 is configured to perform at least one of the following according to the index list of the S-NSSAI:
[0138] Cell selection, cell reselection, and search before cell switching.
[0139] In some embodiments, the serving network is a public land mobile network PLMN or a standalone non-public network SNPN.
[0140] In some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.
[0141] It should be understood that the terminal device 300 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the terminal device 300 are respectively to implement Figure 2 For the sake of brevity, the corresponding process of the terminal device in the method 200 is not repeated here.
[0142] Figure 6 FIG. 4 shows a schematic block diagram of a network device 400 according to an embodiment of the present application. Figure 6 As shown, the network device 400 includes:
[0143] The communication unit 410 is used to send first information to the terminal device; wherein,
[0144] The first information includes an index list of single network slice auxiliary information S-NSSAI, and the index list of S-NSSAI includes index information of part or all of the S-NSSAI of the service network.
[0145] In some embodiments, the first information is included in a non-access stratum (NAS) message.
[0146] In some embodiments, the S-NSSAI index list includes index information of all S-NSSAIs of the serving network.
[0147] In some embodiments, the index information of some S-NSSAIs among the index information of all S-NSSAIs includes the index information of the S-NSSAIs subscribed by the terminal device.
[0148] In some embodiments, the network device 400 further includes: a processing unit 420,
[0149] The processing unit 420 is configured to generate an index list of the S-NSSAI according to an index corresponding to the S-NSSAI of the service network.
[0150] In some embodiments, the communication unit 410 is also used to receive an index list of the S-NSSAI sent by a network slice selection function NSSF entity.
[0151] In some embodiments, the first information is registration acceptance information for registration request information sent by the terminal device, and the registration request information corresponds to one of initial registration, mobility registration, and emergency registration.
[0152] In some embodiments, the first information is a configuration update command.
[0153] In some embodiments, the serving network is a visited network.
[0154] In some embodiments, the first information further includes at least one of the following:
[0155] Allowed network slice auxiliary information NSSAI, configured NSSAI, and network slice indication information used to indicate whether the contracted slice has changed.
[0156] In some embodiments, when the network slice indication information indicates that the contracted slice has changed, the network slice indication information is used by the terminal device to delete the index information of the S-NSSAI of other networks except the service network.
[0157] In some embodiments, the network device is an access and mobility management function AMF entity.
[0158] In some embodiments, the first information is included in a radio resource control (RRC) message.
[0159] In some embodiments, the index list of the S-NSSAI includes index information of a portion of the S-NSSAI of the service network, wherein the portion of the S-NSSAI includes the S-NSSAI supported by the cell and the S-NSSAI supported by the neighboring cells of the cell.
[0160] In some embodiments, when the service network shares a service base station with the first network, the index list of the S-NSSAI includes index information of part of the S-NSSAI of the service network and index information of part of the S-NSSAI of the first network, wherein the part of the S-NSSAI includes the S-NSSAI supported by the cell and the S-NSSAI supported by the neighboring cells of the cell.
[0161] In some embodiments, the communication unit 410 is also used to receive an index list of the S-NSSAI sent by the AMF entity.
[0162] In some embodiments, the RRC message is an RRC connection establishment message, or the RRC message is an RRC connection reconfiguration message.
[0163] In some embodiments, the network device is a serving base station.
[0164] In some embodiments, the index list of the S-NSSAI is used by the terminal device to perform at least one of the following:
[0165] Cell selection, cell reselection, and search before cell switching.
[0166] In some embodiments, the serving network is a public land mobile network PLMN or a standalone non-public network SNPN.
[0167] In some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.
[0168] It should be understood that the network device 400 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the network device 400 are respectively to implement Figure 2 For the sake of brevity, the corresponding processes of the network device in the method 200 are not repeated here.
[0169] Figure 7 It is a schematic structural diagram of a communication device 500 provided in an embodiment of the present application. Figure 7 The communication device 500 shown includes a processor 510, and the processor 510 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
[0170] In some embodiments, Figure 7 As shown, the communication device 500 may further include a memory 520. The processor 510 may call and run a computer program from the memory 520 to implement the method in the embodiment of the present application.
[0171] The memory 520 may be a separate device independent of the processor 510 , or may be integrated into the processor 510 .
[0172] In some embodiments, Figure 7 As shown, the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.
[0173] The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include an antenna, and the number of the antennas may be one or more.
[0174] In some embodiments, the communication device 500 may specifically be a network device of an embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.
[0175] In some embodiments, the communication device 500 may specifically be a terminal device of an embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.
[0176] Figure 8 It is a schematic structural diagram of the device of an embodiment of the present application. Figure 8 The device 600 shown includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.
[0177] In some embodiments, Figure 8 As shown, the apparatus 600 may further include a memory 620. The processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.
[0178] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .
[0179] In some embodiments, the apparatus 600 may further include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
[0180] In some embodiments, the apparatus 600 may further include an output interface 640. The processor 610 may control the output interface 640 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
[0181] In some embodiments, the device can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0182] In some embodiments, the apparatus can be applied to the terminal device in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the terminal device in the various methods in the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0183] In some embodiments, the device mentioned in the embodiments of the present application may also be a chip, for example, a system-on-chip, a system-on-chip, a chip system, or a system-on-chip chip.
[0184] Fig. 9 is a schematic block diagram of a communication system 700 provided in an embodiment of the present application. Fig. 9 As shown, the communication system 700 includes a terminal device 710 and a network device 720 .
[0185] Among them, the terminal device 710 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 720 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.
[0186] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0187] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0188] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
[0189] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.
[0190] In some embodiments, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0191] In some embodiments, the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0192] An embodiment of the present application also provides a computer program product, including computer program instructions.
[0193] In some embodiments, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0194] In some embodiments, the computer program product can be applied to the terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0195] The embodiment of the present application also provides a computer program.
[0196] In some embodiments, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0197] In some embodiments, the computer program can be applied to the terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0198] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0199] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0200] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0201] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0202] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0203] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. In view of such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0204] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A wireless communication method, characterized in that: include: The terminal device receives the first information sent by the access and mobility management function AMF entity; wherein, The first information includes an index list of single network slice auxiliary information S-NSSAI, and the index list of S-NSSAI includes index information of part or all of the S-NSSAI of the serving network, The service network is a visited network. The first information also includes: Allowed network slice auxiliary information NSSAI and configured NSSAI; wherein, the first information is included in a non-access layer NAS message, and the first information is registration acceptance information for the registration request information sent by the terminal device, and the registration request information corresponds to one of initial registration, mobility registration, and emergency registration.
2. The method according to claim 1, characterized in that The first information also includes: Network slice indication information used to indicate whether the contracted slice has changed.
3. The method according to claim 1, characterized in that The S-NSSAI index list includes index information of part of the S-NSSAI of the service network, wherein the part of the S-NSSAI includes the S-NSSAI supported by the cell and the S-NSSAI supported by the neighboring cells of the cell.
4. The method according to claim 1, characterized in that The method further comprises: The terminal device performs at least one of the following according to the index list of the S-NSSAI: Cell selection, cell reselection, and search before cell switching.
5. The method according to claim 1, characterized in that The method also includes: the terminal device sends the acquired S-NSSAI index list to the access layer AS of the terminal device, and the access layer AS of the terminal device uses the index to select a cell that can support the index as the resident cell of the terminal device.
6. A wireless communication method, characterized in that: include: The network device sends first information to the terminal device; wherein the network device is an access and mobility management function AMF entity, wherein, The first information includes an index list of single network slice auxiliary information S-NSSAI, and the index list of S-NSSAI includes index information of part or all of the S-NSSAI of the serving network, The service network is a visited network; The first information also includes: Allowed network slice auxiliary information NSSAI and configured NSSAI; wherein, the first information is included in a non-access layer NAS message, and the first information is registration acceptance information for the registration request information sent by the terminal device, and the registration request information corresponds to one of initial registration, mobility registration, and emergency registration.
7. The method according to claim 6, characterized in that The first information also includes: Network slice indication information used to indicate whether the contracted slice has changed.
8. The method according to claim 6, characterized in that The S-NSSAI index list includes index information of part of the S-NSSAI of the service network, wherein the part of the S-NSSAI includes the S-NSSAI supported by the cell and the S-NSSAI supported by the neighboring cells of the cell.
9. The method according to claim 6, characterized in that The S-NSSAI index list is used by the terminal device to perform at least one of the following: Cell selection, cell reselection, and search before cell switching.
10. A terminal device, characterized in that: include: A communication unit, configured to receive first information sent by an access and mobility management function AMF entity; wherein, The first information includes an index list of single network slice auxiliary information S-NSSAI, and the index list of S-NSSAI includes index information of part or all of the S-NSSAI of the serving network, The service network is a visited network; The first information also includes: Allowed network slice auxiliary information NSSAI and configured NSSAI; wherein, the first information is included in a non-access layer NAS message, and the first information is registration acceptance information for the registration request information sent by the terminal device, and the registration request information corresponds to one of initial registration, mobility registration, and emergency registration.
11. The terminal device according to claim 10, characterized in that: The communication unit is further used to send the acquired S-NSSAI index list to the access layer AS of the terminal device; The access layer AS of the terminal device uses the index to select a cell that can support the index as the resident cell of the terminal device.
12. A network device, characterized in that: include: A communication unit, configured to send first information to a terminal device; wherein the network device is an access and mobility management function AMF entity, wherein: The first information includes an index list of single network slice auxiliary information S-NSSAI, and the index list of S-NSSAI includes index information of part or all of the S-NSSAI of the serving network, The service network is a visited network; The first information also includes: Allowed network slice auxiliary information NSSAI and configured NSSAI; wherein, the first information is included in a non-access layer NAS message, and the first information is registration acceptance information for the registration request information sent by the terminal device, and the registration request information corresponds to one of initial registration, mobility registration, and emergency registration.
13. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 1 to 5.
14. A network device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 6 to 9.
15. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 5.
16. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 6 to 9.
Citation Information
Patent Citations
Use method and device of network slicing
CN109565451A