WO2021223191A1 - 信息发送、接收方法、终端及网络设备 - Google Patents

信息发送、接收方法、终端及网络设备 Download PDF

Info

Publication number
WO2021223191A1
WO2021223191A1 PCT/CN2020/089070 CN2020089070W WO2021223191A1 WO 2021223191 A1 WO2021223191 A1 WO 2021223191A1 CN 2020089070 W CN2020089070 W CN 2020089070W WO 2021223191 A1 WO2021223191 A1 WO 2021223191A1
Authority
WO
WIPO (PCT)
Prior art keywords
slice
terminal
network device
information
supported
Prior art date
Application number
PCT/CN2020/089070
Other languages
English (en)
French (fr)
Inventor
付喆
田文强
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to EP20934788.9A priority Critical patent/EP4135412A4/en
Priority to PCT/CN2020/089070 priority patent/WO2021223191A1/zh
Priority to CN202211560108.7A priority patent/CN115776699A/zh
Priority to CN202080094827.7A priority patent/CN115004788A/zh
Publication of WO2021223191A1 publication Critical patent/WO2021223191A1/zh
Priority to US17/980,127 priority patent/US20230058891A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • This application relates to the field of communications, and specifically, to a method for sending and receiving information, a terminal, and a network device.
  • the strong demand for wireless communications in vertical industries is obvious to all.
  • the access network supports the business of vertical industries to be enhanced. Based on network slicing, it provides services with lower latency, more target, greater flexibility and higher scalability for multiple services with different requirements.
  • the behaviors related to the network slicing supported by the RAN are not involved.
  • the embodiments of the present application provide a method for sending and receiving information, a terminal, and a network device to solve the technical problem of the lack of a standard for RAN to support network slicing in related technologies, so as to achieve the effect of providing a standard for RAN to support network slicing.
  • an information sending method including:
  • the terminal sends the slice information of the terminal to the network device.
  • an information receiving method including:
  • the network device receives the slice information of the terminal sent by the terminal.
  • a terminal including:
  • the first sending module is configured to send the slice information of the terminal to the network device.
  • a network device including:
  • the fourth receiving module is configured to receive the slice information of the terminal sent by the terminal.
  • a terminal including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned first aspect or each of its implementation modes.
  • a network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or its implementation manners.
  • a chip for implementing any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.
  • the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes any one of the above-mentioned first aspect to the second aspect or any of the implementations thereof method.
  • a storage medium for storing a computer program that enables a computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.
  • a computer program product including computer program instructions that cause a computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.
  • a computer program which when running on a computer, causes the computer to execute any one of the above-mentioned first aspect to the second aspect or the method in each implementation manner thereof.
  • the terminal sends the slicing information of the terminal to the network device, and the slicing information of the terminal is the slicing information of the slicing required by the terminal. Therefore, in the RAN, the requirement of the terminal for network slicing is taken into consideration.
  • the standard for RAN to support network slicing is solved, and the technical problem of the lack of a standard for RAN to support network slicing in related technologies is solved, and the effect of adapting to the development of technical standards can be achieved.
  • Fig. 1 is a schematic diagram of a communication system applied by an embodiment of the present application.
  • Fig. 2 is a schematic flowchart of an information sending method provided by an embodiment of the present application.
  • Figure 3 is a schematic diagram of a two-step random access process provided by an embodiment of the present application.
  • Fig. 4 is a schematic flowchart of an information receiving method provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of Embodiment 1 provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of Embodiment 2 provided by an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a terminal provided by an embodiment of the present application.
  • Fig. 8 is a schematic block diagram of a network device provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a chip of an embodiment of the present application.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System of Mobile Communication
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the communication system 100 applied in the embodiment of the present application is shown in FIG. 1.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or called a communication terminal or terminal).
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located in the coverage area.
  • the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (Evolutional Node B, eNB or eNodeB), or the wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in the future evolution of the Public Land Mobile Network (PLMN), etc.
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • LTE Long Term Evolutional Node B
  • eNB evolved base station
  • CRAN Cloud Radio Access Network
  • the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches
  • the communication system 100 also includes at least one terminal device 120 located within the coverage area of the network device 110.
  • the "terminal equipment” used here includes but is not limited to connection via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, and direct cable connection ; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and/or another terminal device that is set to receive/send communication signals; and/or Internet of Things (IoT) equipment.
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Line
  • WLAN wireless local area networks
  • IoT Internet of Things
  • a terminal device set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a “wireless terminal” or a “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio telephone transceivers Electronic device.
  • PCS Personal Communications System
  • GPS Global Positioning System
  • Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, or User device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in the future evolution of PLMN, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • D2D communication may be performed between the terminal devices 120.
  • the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.
  • NR New Radio
  • Figure 1 exemplarily shows one network device and two terminal devices.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. The embodiment does not limit this.
  • the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices.
  • the communication device may include a network device 110 with communication functions and a terminal device 120.
  • the network device 110 and the terminal device 120 may be the specific devices mentioned above, which will not be repeated here;
  • the device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • FIG. 2 is a schematic flowchart of an information sending method provided by an embodiment of the present application. As shown in FIG. 2, the method includes:
  • the terminal sends the slicing information of the terminal to the network device. It should be noted that the slicing information of the terminal here may be information of the slicing required by the terminal.
  • the terminal sends the slicing information of the terminal to the network device.
  • the slicing information of the terminal is the slicing information required by the terminal, which provides the standard for RAN to support network slicing, and solves the lack of standards for RAN to support network slicing in related technologies.
  • the technical problems in the future can achieve the effect of adapting to the development of technical standards.
  • the terminal in this method may be a smart terminal, for example, may be some smart terminals such as smart phones, smart cars, drones, and robots. It can also be some wearable devices, such as smart watches, smart bracelets, smart glasses, etc.
  • the terminal when the terminal sends the slicing information of the terminal to the network device, the terminal can send the slicing information of the terminal to the network device in a variety of ways.
  • the terminal can control RRC messages through radio resources or access RACH randomly.
  • the uplink message in the process carries slicing information and sends the slicing information to the network device.
  • the foregoing RRC message may be an uplink dedicated RRC message (UL dedicated RRC message).
  • the slicing information of the terminal is sent by the terminal to the network device.
  • the uplink message sent by the terminal to the network device can be used to carry the slicing information of the terminal, for example, it can be a random access RACH.
  • Uplink message in the process To facilitate the description of the uplink message in the random access RACH process, in this embodiment, the random access RACH process is first described.
  • the trigger/establishment cause value is carried in Msg 3.
  • the random access process is mainly triggered by the following events:
  • NR two kinds of random access methods are mainly supported, the random access method based on contention and the random access method based on non-competition.
  • Step1 The terminal selects the preamble and physical random access channel (Physical Random Access Channel, referred to as PRACH) resources (time-frequency resources and code domain resources):
  • PRACH Physical Random Access Channel
  • the terminal sends the selected preamble on the selected PRACH time-frequency resource. Based on the preamble, the base station can estimate the uplink time period (Timing) and the size of the grant resource required for the terminal to transmit message 3 (probably know, not precise) .
  • Step2 The network sends RAR to the terminal:
  • the terminal After sending message 1 (Msg1), the terminal opens a RAR window, and monitors the physical downlink control channel (Physical Downlink Control Channel, referred to as PDCCH) in the window.
  • PDCCH Physical Downlink Control Channel
  • the PDCCH uses random access radio network temporary identifier (Random Access Radio Network Temporary Identifier, referred to as RA-RNTI) for scrambling.
  • RA-RNTI Random Access Radio Network Temporary Identifier
  • the terminal After successfully monitoring the PDCCH scrambled by the RA-RNTI, the terminal can obtain the physical downlink shared channel (Physical Downlink Shared Channel, referred to as PDSCH) scheduled by the PDCCH, which includes RAR (random access response).
  • PDSCH Physical Downlink Shared Channel
  • the subheader of the RAR contains BI, which is used to indicate the back-off time of retransmission of message 1;
  • RAPID in RAR the preamble index (preamble index) received by the network in response;
  • the RAR payload (payload) contains a tag (TAG), which is used to adjust the uplink timing;
  • TAG tag
  • UL grant (uplink grant): an uplink resource indication for scheduling Msg3;
  • Temporary C-RNTI Temporary Cell Radio Network Temporary Identity
  • PDCCH Initial Access
  • Step3 The terminal transmits the RRC message on the scheduling resource
  • Msg3 The message of Msg3 is mainly used to inform the network of what event triggered the RACH process. For example, if it is an initial access random process, Msg3 will carry the terminal identification and establishment cause; if it is RRC re-establishment, it will carry the connected terminal identification and the re-establishment cause;
  • Msg4 is used for conflict resolution.
  • FIG. 3 is a schematic diagram of a two-step random access process provided by an embodiment of this application. As shown in Figure 3, the basic method is that Msg A transmits Msg1+Msg3 of the four-step RACH, and Msg B transmits Msg2+Msg4 of the four-step RACH. .
  • the trigger/establishment cause value will also be carried in Msg A.
  • the uplink message may include at least one of the following: message 1 in the four-step RACH process, message 3 in the four-step RACH process, and message A in the two-step RACH process. That is, the slicing information of the terminal is carried by at least one of the above three kinds of uplink messages, and the slicing information of the terminal is sent to the network device.
  • the slice information is carried by the reason value in the RRC message or the uplink message, where the reason value in the RRC message is used to characterize the reason why the standard triggers the RRC message, and the reason value in the uplink message is used to characterize the triggering of the RACH process. s reason.
  • the content of the cause value in the RRC message includes slice information, or the content of the cause value in the uplink message includes slice information.
  • the slice information of the terminal may include multiple types, as long as it can be used by the network device to determine the network slice required by the terminal. For example, it may include at least one of the following: the terminal's slice identifier, the category to which the terminal's slice belongs, the priority of the terminal's slice, the priority of the category to which the terminal's slice belongs, the location information of the terminal, and the preferred public land mobile network PLMN identification.
  • the slice identifier of the terminal is used to identify the slice of the terminal, that is, the slice used to identify the requirement of the terminal.
  • the form of the slice identification can be various, for example, simple digital identification, letter identification, text identification, etc. can be used, and some complex characters can also be used.
  • the category to which the terminal's slice belongs can be classified based on different applications, or can be classified based on different specific networks.
  • the priority of the slice of the terminal may be the level of the slice that is preferentially used. For example, it may be that the higher the level, the more preferentially used it is.
  • the priority of the category to which the slice of the terminal belongs may be the level of the slice category that is preferentially used. For example, it may be that the higher the level, the more preferentially used it is.
  • the method further includes: the terminal receives instruction information sent by the network device, the instruction information is used to indicate whether the terminal is allowed to perform different operations based on the slicing information, or, Indicates whether the terminal is allowed to report slice information.
  • the method further includes: the terminal receives the slicing indication information sent by the network device; and the terminal determines the slicing information according to the slicing indication information.
  • the slice indication information may be related information used by the network device to indicate to the terminal the slices that the network device can support.
  • the slice indication information may include multiple types, for example, may include at least one of the following: a slice identifier supported by the network device, a slice category supported by the network device, and a mapping between a slice identifier and a slice category supported by the network device Relationship, the priority of the slice ID supported by the network device, the priority of the slice category supported by the network device, the indication that the network device allows the reporting of slice information, the public land mobile network PLMN ID supported by the network device, and the slice ID and PLMN supported by the network device
  • the content corresponding to the slice information of the terminal in the slice indication information may have the same meaning as the slice information of the terminal.
  • the slice ID supported by the network device, the slice category supported by the network device, the priority of the slice ID supported by the network device, the priority of the slice category supported by the network device, and the public land mobile network PLMN ID supported by the network device, the above objects can be It may be one or multiple, for example, it may be a list including multiple.
  • the terminal when the terminal receives the slicing indication information sent by the network device, multiple methods can be adopted.
  • the terminal receives the slicing indication information sent by the network device in at least one of the following ways: the terminal receives the slicing indication information sent by the network device. , Receiving the slicing indication information; the terminal receives the slicing indication information by receiving the predetermined signaling sent by the network device.
  • the broadcasting range can be set, so that the broadcasting range of the network device can cover the terminal.
  • the predetermined signaling may be multiple, for example, it may be dedicated RRC signaling, such as RRC release signaling.
  • the slice information is determined to be different according to different contents of the slice information.
  • the slice information may include at least one of the following:
  • the terminal determines the category to which the slice of the terminal belongs according to the mapping relationship between the slice identifier supported by the network device in the slice indication information and the slice category; that is, as long as the slice of the terminal belongs to the slice category indicated in the slice indication information, it can According to the mapping relationship between the slice identifier and the slice category, the category to which the slice of the terminal belongs is determined.
  • the terminal When the terminal determines that the slice of the terminal does not belong to the slice category indicated in the slice indication information, the terminal assigns the slice of the terminal to a default category or a predetermined category; wherein the default category and the predetermined category may be set in advance.
  • the terminal When the terminal determines that the slice of the terminal does not belong to the slice indicated in the slice indication information, the terminal assigns the slice of the terminal to the default category or a predetermined category; that is, regardless of whether the slice of the terminal does not belong to the slice category indicated in the slice indication information, Whether the slice of the terminal does not belong to the slice indicated in the slice indication information, the slice of the terminal can be assigned to one category.
  • the terminal determines that the slice of the terminal does not belong to the slice indicated in the slice indication information
  • the terminal assigns the slice of the terminal to a default slice or a non-slice. That is, when the slice of the terminal does not belong to the slice indicated in the slice indication information, the slice of the terminal can also belong to a slice or a non-slice.
  • the terminal determines the category to which the slice of the terminal belongs according to the mapping relationship between all slice identifiers of the network device and the slice category in the slice indication information. That is, the network device sends the related information of all the slices of the network device to the terminal, and the terminal determines the category to which the slice of the terminal belongs according to the mapping relationship between all the slice identifiers and the slice category. In contrast to the foregoing network device only sending the information related to the supported slices, the network device provided here sends all slice-related information also belongs to one way.
  • the slice identifier of the terminal or the slice identifier supported by the network device may include multiple types, for example, each may include at least one of the following: network slice selection auxiliary information, single network slice selection auxiliary information, network slice identification .
  • the slice of the terminal may include at least one of the following: a requested slice (requested slice), an allowed slice (allowed slice), a configured slice (configured slice), and a default slice. (default), the signed slice.
  • the terminal may further include at least one of the following:
  • the terminal receives the control result sent by the network device, where the control result includes: the result of the RACH process determined according to the slice information, or the response to the RACH process triggered by the terminal;
  • the terminal receives the selection result sent by the network device, where the selection result includes at least one of the following: the access and mobility management entity AMF selected according to the slice information to provide services for the terminal, and the selection result selected according to the slice information to provide the terminal.
  • the session management function entity SMF of the service, the user plane function entity UPF selected according to the slice information to provide services for the terminal indicates whether the required core network entity is selected.
  • the result of the RACH process may include: the success of the RACH process and the failure of the RACH process.
  • the response to the RACH process triggered by the terminal may include at least one of the following: the network device responds to the UE (making the UE RACH successful), the network device sends a RACH response message for the UE (making the UE RACH successful), and the network device sends a short RACH backoff (making the UE RACH successful).
  • the RACH succeeds as soon as possible), the network device does not respond to the UE, the network device does not send Msg 4 or Msg B for the UE, and the network device sends a long RACH backoff.
  • FIG. 4 is a schematic flowchart of the information receiving method provided by the embodiment of the present application. As shown in FIG. 4, the method includes:
  • the network device receives the slicing information of the terminal sent by the terminal.
  • the network device receives the slicing information of the terminal sent by the terminal.
  • the slicing information of the terminal is the slicing information of the slicing required by the terminal. Therefore, the RAN takes into account the needs of the terminal for network slicing, and provides information about the RAN supporting network slicing.
  • the standard solves the technical problem of the lack of standards for RAN to support network slicing in related technologies, and can achieve the effect of adapting to the development of technical standards.
  • the network device in this method may be a device in an access network, for example, various types of base stations.
  • the access network may be a radio access network RAN or the like.
  • the network device when the network device receives the slicing information sent by the terminal, the network device can receive the slicing information of the terminal sent by the terminal in a variety of ways.
  • the network device can control RRC messages or random access RACH procedures through radio resources.
  • the uplink message in, carries slice information, and receives slice information sent by the terminal.
  • the foregoing RRC message may be an uplink dedicated RRC message (UL dedicated RRC message).
  • the slicing information of the terminal is sent by the terminal to the network device.
  • the uplink message sent by the terminal to the network device can be used to carry the slicing information of the terminal, for example, it can be a random access RACH.
  • Uplink message in the process may include at least one of the following: message 1 in the four-step RACH process, message 3 in the four-step RACH process, and message A in the two-step RACH process. Therefore, the network device can receive the slice information of the terminal through at least one of the foregoing three types of messages.
  • the slice information is carried by the reason value in the RRC message or the uplink message, where the reason value in the RRC message is used to characterize the reason why the standard triggers the RRC message, and the reason value in the uplink message is used to characterize the triggering of the RACH process. s reason.
  • the content of the cause value in the RRC message includes slice information, or the content of the cause value in the uplink message includes slice information.
  • the slice information of the terminal may include multiple types, as long as it can be used by the network device to determine the network slice required by the terminal. For example, it may include at least one of the following: the terminal's slice identifier, the category to which the terminal's slice belongs, the priority of the terminal's slice, the priority of the category to which the terminal's slice belongs, the location information of the terminal, and the preferred public land mobile network PLMN identification.
  • the slice identifier of the terminal is used to identify the slice of the terminal, that is, the slice used to identify the needs of the terminal.
  • the form of the slice identification can be various, for example, simple digital identification, letter identification, text identification, etc. can be used, and some complex characters can also be used.
  • the category to which the terminal's slice belongs can be classified based on different applications, or can be classified based on different specific networks.
  • the priority of the slice of the terminal may be the level of the slice that is preferentially used. For example, it may be that the higher the level, the more preferentially used it is.
  • the priority of the category to which the slice of the terminal belongs may be the level of the slice category that is preferentially used. For example, it may be that the higher the level, the more preferentially used it is.
  • the method before the network device receives the slicing information of the terminal sent by the terminal, the method further includes: the network device sends slicing indication information to the terminal.
  • the slice indication information may be related information for the network device to indicate to the terminal the slices that the network device can support.
  • the method further includes: the network device sends the known slicing information to the terminal.
  • the slice information may be related information used by the network device to indicate to the terminal the slice known by the network device, such as priority, such as the relationship between the slice and the category, and so on.
  • the slice indication information may also include multiple types. For example, it may include at least one of the following: a slice identifier supported by the network device, a slice category supported by the network device, and a difference between the slice identifier supported by the network device and the slice category.
  • mapping relationship the priority of the slice ID supported by the network device, the priority of the slice category supported by the network device, the indication that the network device allows the reporting of slice information, the public land mobile network PLMN ID supported by the network device, and the slice ID supported by the network device
  • the mapping relationship between PLMN identities, the mapping relationship between the slice category supported by the network device and the PLMN identity, the threshold of the number of terminals defined by the slices supported by the network device, the threshold of the number of terminals defined by the slices supported by the PLMN, and the slices supported by the session The defined threshold for the number of terminals, the threshold for the number of sessions defined by the slices supported by the network device, and the threshold for the number of sessions defined by the slices supported by the PLMN.
  • the content corresponding to the slice information of the terminal in the slice indication information may have the same meaning as the slice information of the terminal.
  • the slice ID supported by the network device, the slice category supported by the network device, the priority of the slice ID supported by the network device, the priority of the slice category supported by the network device, and the public land mobile network PLMN ID supported by the network device, the above objects can be It may be one or multiple, for example, it may be a list including multiple.
  • the network device when the network device sends the slicing instruction information to the terminal, multiple methods may also be adopted.
  • the network device sends the slicing instruction information to the terminal in at least one of the following ways: the network device broadcasts the slicing instruction information to the terminal. Send slicing indication information; the network device sends slicing indication information to the terminal by sending predetermined signaling to the terminal.
  • the broadcast range can be set by the above-mentioned broadcast method, so that the broadcast range of the network device can cover the terminal.
  • the predetermined signaling may be multiple, for example, it may be dedicated RRC signaling, such as RRC release signaling.
  • the slice identifier of the terminal or the slice identifier supported by the network device may include multiple types, for example, each may include at least one of the following: network slice selection auxiliary information, single network slice selection auxiliary information, network slice identification .
  • the network device may also determine whether the terminal can provide the slicing required by the terminal according to the slicing information, and obtain the determination result. That is, the network device determines whether it can provide the terminal with the slicing required by the terminal, or whether it can provide the terminal with the slicing of the terminal, so as to subsequently provide services to the terminal.
  • the network device can also send the judgment result of whether the terminal can provide the terminal required slices to the terminal, that is, the network device sends the judgment result to the terminal.
  • the terminal is made aware of whether the network device can provide the terminal with a slice of the terminal demand, so that the terminal can correspondingly perform a behavior adapted to the network device.
  • the network device when the network device sends the judgment result to the terminal, different processing can be performed according to the difference of the judgment result. For example, when the judgment result is that it can provide the terminal slice for the terminal, the network device sends the judgment result to the terminal. Contains a response message that can provide the terminal with a slice of the terminal. That is, when the network device determines that it can provide the terminal's slice information for the terminal, it will send it to the terminal device, otherwise it will not send it.
  • the network device can determine whether it can provide the terminal with the slicing required by the terminal according to the slicing information in the following manner: when the network device determines that the terminal meets the slicing condition according to the slicing information, the network device determines that it can provide the terminal with the required slicing. slice.
  • the slicing condition is different according to the slice information.
  • it may include at least one of the following: the slice supported by the network device matches the slice required by the terminal, and the slice category supported by the network device belongs to the slice required by the terminal.
  • the location of the terminal is within the range of the slice service provided by the network device, the priority of the slice supported by the network device meets the priority of the slice required by the terminal, the slice with a predetermined priority supported by the network device matches the slice required by the terminal, The slices supported by the device match the slices with the predetermined priority required by the terminal, the slices with the predetermined priority supported by the network device match the slices with the predetermined priority required by the terminal, and the category of the slice with the predetermined priority supported by the network device matches the requirement of the terminal.
  • the category to which the slice belongs matches, the category to which the slice supported by the network device belongs matches the category to which the slice of the predetermined priority required by the terminal belongs, and the category to which the slice of the predetermined priority supported by the network device belongs to the predetermined priority slice of the terminal requirement.
  • the slice category supported by the network device meets the terminal requirements of the slice category, which is lower than the threshold of the number of terminals defined by the slice supported by the network device, lower than the threshold of the number of terminals defined by the slices supported by PLMN, and lower than the threshold of the number of terminals supported by the session
  • the threshold for the number of terminals defined by the slice is lower than the threshold for the number of sessions defined by the slices supported by the network device, and lower than the threshold for the number of sessions defined by the slices supported by the PLMN; the slice required by the terminal matches the predetermined slice supported by the network device, and the terminal needs The predetermined slice matches the slice supported by the network device.
  • the threshold for the number of sessions defined by the supported slices is lower than the threshold for the number of sessions defined by the slices supported by the PLMN.
  • lower than the threshold for the number of terminals defined by the slices supported by the network device may be the service provided by the slices supported by the network device The maximum number of terminals or PDU (Protocol Data Unit) sessions or DRB (Data Radio Bearer).
  • terminal number threshold Take the terminal number threshold as an example. For slices supported by network devices, up to 3 terminals can be served , Where 3 is the threshold for the number of terminals. It should be noted that 3 is only an example, and can also be other numbers according to the specific conditions of the slice.
  • the network device chooses the slice that the terminal needs more closely matches the one supported by the network device. For example, the network device indicates to support the slice with the slice ID 1-5, the terminal 1 needs the slice with the slice ID 1-3, and the terminal 2 needs the slice.
  • the slice ID is slices 1-4, and the network device selects terminal 2.
  • the network device instructs to support slices with slice identifiers 1-5, and the priority of slice identifiers from 1 to 5 is getting lower and lower, terminal 1 requires slice identifiers as 1-3, and terminal 2 requires slice identifiers as 2-5. Select terminal 1 for network equipment.
  • the network device determines whether it can provide the required slice for the terminal.
  • slice identification are also applicable to the judgment of the slice category, also to the judgment of the priority of the slice identification, and also to the judgment of the priority of the slice category. For example.
  • the slice required by the terminal matches the predetermined slice supported by the network device.
  • the predetermined slice supported by the network device there may be multiple slices required by the terminal. If the identifier of the predetermined slice is 1, 3, 5, 8, it can be considered that the slice required by the terminal matches the predetermined slice supported by the network device; but if the identifier of the predetermined slice supported by the network device is 1, 3, 7, 9, then you can It is considered that the slicing required by the terminal does not match the predetermined slicing supported by the network device.
  • the slicing required by the terminal needs to be able to provide services for a predetermined number of terminals, and if the predetermined slicing supported by the network device can also provide services for the predetermined number of terminals, the slicing required by the terminal is considered to be the same as the reservation supported by the network device.
  • the slice matches, otherwise it is considered that the slice required by the terminal does not match the predetermined slice supported by the network device.
  • the slicing required by the terminal needs to be able to provide services for more than 3 terminals, and if the predetermined slicing supported by the network equipment can also provide services for more than 3 terminals, the slicing required by the terminal is considered to be the predetermined slicing supported by the network equipment.
  • Match but if the predetermined slice supported by the network device cannot provide services for more than 3 terminals, it is considered that the slice required by the terminal does not match the predetermined slice supported by the network device.
  • the network device judges whether it can provide the terminal required slices for the terminal according to the slice information, and obtains the judgment result, which includes at least one of the following:
  • the network device performs RACH process control on the terminal according to whether it can provide the terminal required slices for the terminal, and obtains the control result.
  • the control result includes: the result of the RACH process determined according to the slice information, or the response to the RACH process triggered by the terminal ;
  • the network device feeds back the control result to the terminal according to whether it can provide the terminal required slices for the terminal, where the control result includes: the result of the RACH process determined according to the slice information, or the response to the RACH process triggered by the terminal;
  • the network device responds to the RRC request message triggered by the terminal according to whether it can provide the slicing required by the terminal for the terminal;
  • the network device selects at least one of the following services for the terminal according to whether it can provide a slice of the terminal demand for the terminal: the access and mobility management entity AMF, the session management function entity SMF, and the user plane function entity UPF.
  • the result of the RACH process may include: successful execution of the RACH process and failure of the execution of the RACH process.
  • the response to the RACH process triggered by the terminal may include at least one of the following: the network device responds to the UE (making the UE RACH successful), the network device sends a RACH response message for the UE (making the UE RACH successful), and the network device sends a short RACH backoff (making the UE RACH successful).
  • the RACH succeeds as soon as possible), the network device does not respond to the UE, the network device does not send Msg 4 or Msg B for the UE, and the network device sends a long RACH backoff.
  • the slice of the terminal may include at least one of the following: a requested slice (requested slice), an allowed slice (allowed slice), a configured slice (configured slice), and a default slice. (default slice), the contracted slice.
  • the terminal takes the terminal as a UE as an example to describe the preferred implementation manners provided in this application.
  • a slice-based random access method is provided, for example, through the UE (the UE is used as Example explanation)
  • the slice information is carried in the RACH process, so that the UE can quickly access and avoid the delay of UE access and service service.
  • the slice-based random access method may include: the UE carries slice information during the RACH process, where the slice information is used by the network device to perform access control (for example, determine the result of performing the RACH process), and/or select Suitable network function entities, for example, suitable network function entities include at least one of the following: Access and Mobility Management Function (AMF), Session Management Function (SMF) ), user plane function entity (User Plane Function, referred to as UPF), etc.
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • the slice information of the UE includes at least one of the following: the slice identifier of the UE, the category to which the slice of the UE belongs, the priority of the slice of the UE, the priority of the category to which the slice of the UE belongs, the location information of the UE, and the preferred public land mobile Network PLMN identity.
  • the network device sends slice indication information to the UE by broadcasting or through a dedicated radio resource control RRC message, where the slice indication information includes at least one of the following: slice type supported by the network device , The slice ID supported by the network device, the mapping relationship between the slice ID supported by the network device and the slice category, the priority of the slice category supported by the network device, the priority of the slice ID supported by the network device, and the indication that the network device allows the reporting of slice information,
  • the public land mobile network PLMN identity supported by the network device the mapping relationship between the slice identity supported by the network device and the PLMN identity, the mapping relationship between the slice category supported by the network device and the PLMN identity, and the terminal defined by the slice supported by the network device Number threshold, the threshold of the number of terminals defined by the slices supported by the PLMN, the threshold of the number of terminals defined by the slices supported by the session, the threshold of the number of sessions defined by the slices supported by the network device, and the threshold of
  • the UE may determine the slicing information based on the slicing required by the UE and the slicing indication information sent by the network device.
  • NSSAI Network Slice Selection Assistance Information
  • S-NSSAI Single Network Slice Selection Assistance Information
  • NSID Network Slicing Identity
  • the UE carries slice information through the RACH process. For example, it can be carried in the Msg 3 or Msg A message in the RACH process.
  • the first cause value carried in the RACH process can be used to indicate slice information.
  • the slice information is used for the network device to perform access control (such as determining the RACH response mode or result).
  • the slice information may include at least one of the following: the slice identifier of the UE, the category to which the slice of the UE belongs, the priority of the slice of the UE, the priority of the category to which the slice of the UE belongs, and UE location information.
  • FIG. 5 is a schematic diagram of Embodiment 1 provided by an embodiment of the present application. As shown in FIG. 5, this embodiment includes:
  • S1 The network device broadcasts slice related information through the serving cell.
  • the broadcast slice related information may include at least one of the following: slice identifier (specifically, slice identifier may include: NSSAI, S-NSSAI, NSID); slice category (including category identifier); the mapping relationship between slice identifier and slice category; The priority of the slice category; the priority of the slice ID.
  • slice identifier may include: NSSAI, S-NSSAI, NSID
  • slice category including category identifier
  • the mapping relationship between slice identifier and slice category The priority of the slice category; the priority of the slice ID.
  • the slice related information may include slices supported by the serving cell, or slices not supported by the serving cell.
  • the slice supported by the serving cell is the slice supported by the network, that is, the slice supported by the network equipment included in the network.
  • the slice related information may also be through dedicated RRC signaling, such as an RRC release indication.
  • the UE Non-Access Stratum sends indication information to the Access Stratum (AS for short) of the UE, where the indication information is UE-related slice information.
  • the indication information is embodied as the first cause value.
  • the content of the cause value is slice information.
  • the slice information may include at least one of the following: the slice identifier of the UE, the category to which the slice of the UE belongs, the priority of the slice of the UE, the priority of the category to which the slice of the UE belongs, and UE location information.
  • the UE AS triggers the RACH process, and the UE-related slice information is carried in the RACH process.
  • the RACH process is 2-step RACH, 4-step RACH.
  • the slice information is carried in Msg 3 or Msg A.
  • the first cause value in the RACH is used to carry the slice information.
  • the slice information for example, the cause value is carried in an establishment request (establishment request) message, or a reestablishment request (reestablishment request) message, or a resume request (Resume request) message.
  • the cause value is a new cause value introduced in establishmentCause, or reestablishmentCause, or ResumeCause to reflect slice information.
  • the cause value content is the slice information.
  • the slice information may include at least one of the following: the slice identifier of the UE, the category to which the slice of the UE belongs, the priority of the slice of the UE, the priority of the category to which the slice of the UE belongs, UE location information, and a slice request indication.
  • the slice information may be one or multiple, for example, a list.
  • the slice of the UE in the slice information may include one of the following: a requested slice, an allowed slice, a configured slice, and a contracted slice, that is, the slice information may be embodied as a slice identifier.
  • the UE determines the slice category to which the slice of the UE belongs, it may be determined according to the relationship between the slice and the category indicated by the cell. If the slice of the UE does not belong to the slice in the category indicated by the cell, the UE may belong to the default category or the predetermined category.
  • the UE may belong to the default category or a predetermined category, or directly report the slice identifier.
  • the UE may attribute the slice to the default slice or non-slice.
  • the network may also provide all slice information and/or all slice information and the relationship between the category, and the slice may not be a slice supported by the current network.
  • the network device receives the first cause value carried in the RACH, determines the slice information, and then performs access control (such as whether to respond to the RACH process of the UE, whether to send Msg 4 or Msg B for the UE, and whether to send long/ Short RACH backoff value, etc.).
  • access control such as whether to respond to the RACH process of the UE, whether to send Msg 4 or Msg B for the UE, and whether to send long/ Short RACH backoff value, etc.
  • the network device determines the slices that can be provided according to the location of the UE. That is, the network device determines the slice of the location according to the location of the UE, and determines whether it can provide the slice service for the UE. Alternatively, the network device determines the slice at the location according to the location and slice priority of the UE, or the location and slicing requirements of the UE, and determines whether the UE can provide a priority slice service for the UE. If there is a corresponding slice service at this location, the network device responds to the UE, or sends a RACH response message for the UE, or sends a short RACH backoff. Otherwise, the network device does not respond to the UE, or does not send Msg 4 or Msg B for the UE, or sends a long RACH backoff.
  • the network device determines that the corresponding slice required by the UE can be provided for the UE based on this information, and the network device responds to the UE (making the UE RACH successful) , Or send a RACH response message for the UE (make the UE RACH successful), or send a short RACH backoff (make the RACH succeed as soon as possible). Otherwise, the network does not respond to the UE, or does not send Msg 4 or Msg B for the UE, or sends a long RACH backoff.
  • the network device determines that it can provide the corresponding slice service for the UE according to the information, and the network device responds to the UE (making the UE RACH successful), or sends RACH response message for the UE (to make the UE RACH successful), or to send a short RACH backoff (to make the RACH succeed as soon as possible). Otherwise, the network device does not respond to the UE, or does not send Msg4 or Msg B for the UE, or sends a long RACH backoff.
  • the network device determines whether the service can be provided based on the priority slice according to the information. For example, whether the network device can support the slices corresponding to the priority, if it can support the slices corresponding to the priority, whether the network device can still provide these slice services for the UE according to other factors (the maximum number of UEs supported in the slice, etc.). If so, the network device responds to the UE (making the UE RACH successful), or sends a RACH response message for the UE (making the UE RACH successful), or sends a short RACH backoff (making the RACH successful as soon as possible). Otherwise, the network device does not respond to the UE, or does not send Msg 4 or Msg B for the UE, or sends a long RACH backoff.
  • the network equipment is based on the location of the UE and the type of the UE (for example, whether the UE is a slicing-capable UE). If the UE is not a slicing-capable UE, and the network to which the network equipment belongs is a slice-provided network, then The network device may not respond to the UE.
  • the UE determines the RACH result according to the message sent by the network device, and performs subsequent operations.
  • the network device performs access control (such as whether to respond to the RACH process of the UE, whether to send Msg 4 or MsgB for the UE, whether to send long/short RACH backoff values, etc. ), distinguish the UE (whether it is supported, priority, etc.) to ensure the priority access of the required UE.
  • access control such as whether to respond to the RACH process of the UE, whether to send Msg 4 or MsgB for the UE, whether to send long/short RACH backoff values, etc.
  • the UE carries slice information through the RACH process. For example, it can be carried in the Msg 3 or Msg A message in the RACH process.
  • the first cause value carried in the RACH process can be used to indicate the slice information.
  • the slice information is used by the network device to select appropriate network function entities, such as AMF, SMF and UPF, so as to provide services for the UE.
  • the network entity is AMF as an example for description.
  • Other network function entities, such as SMF and UPF can also be selected accordingly to provide services for the UE, and the detailed description will not be separately elaborated.
  • the slice information may include at least one of the following: the slice identifier of the UE, the category to which the slice of the UE belongs, the priority of the slice of the UE, the priority of the category to which the slice of the UE belongs, UE location information, and so on.
  • FIG. 6 is a schematic diagram of Embodiment 2 provided by an embodiment of the present application. As shown in FIG. 6, this embodiment includes:
  • S1 The network device broadcasts slice related information through the serving cell. in:
  • the slice related information may include at least one of the following: slice identifier (specifically, the slice identifier may include: NSSAI, S-NSSAI, NSID); slice category (including category identifier); the mapping relationship between the slice identifier and the slice category; the slice category The priority; the priority of the slice ID.
  • the slice related information may include slices supported by the serving cell, or slices not supported by the serving cell.
  • the slice supported by the serving cell is the slice supported by the network, that is, the slice supported by the network equipment included in the network.
  • the slice related information may also be through dedicated RRC signaling, such as an RRC release indication.
  • the UE NAS sends indication information to the UE AS, where the indication information is slice information related to the UE. in:
  • the indication information is embodied as the first cause value.
  • the content of the cause value is slice information.
  • the slice information may include at least one of the following: the slice identifier of the UE, the category to which the slice of the UE belongs, the priority of the slice of the UE, the priority of the category to which the slice of the UE belongs, and UE location information.
  • the UE AS triggers the RACH process, and the UE-related slice information is carried in the RACH process.
  • the RACH process is 2-step RACH, 4-step RACH.
  • the slice information is carried in Msg 3 or Msg A.
  • the first cause value in the RACH is used to carry the slice information.
  • the slice information for example, the cause value is carried in an establishment request message, or a reestablishment request message, or a resume request message.
  • the cause value is a new cause value introduced in establishmentCause, or reestablishmentCause, or ResumeCause to reflect slice information.
  • the content of the cause value is slice information.
  • the slice information may include at least one of the following: the slice identifier of the UE, the category to which the slice of the UE belongs, the priority of the slice of the UE, the priority of the category to which the slice of the UE belongs, UE location information, and a slice request indication.
  • the slice information can be one or multiple, for example, a list.
  • the UE slice in the UE slice information may include one of the following: requested slice, allowed slice, and configured slice. That is, the slice information can be embodied as a slice identifier.
  • the UE determines the slice category to which the slice of the UE belongs, it may be determined according to the relationship between the slice and the category indicated by the cell. If the slice of the UE does not belong to the slice in the category indicated by the cell, the UE may belong to the default category or the predetermined category.
  • the UE may belong to the default category or a predetermined category, or directly report the slice identifier.
  • the network device receives the first cause value carried in the RACH, determines slice information, and then selects a suitable AMF for the UE to provide a service for the UE.
  • the following is an example.
  • the network device determines the slices that can be provided according to the location of the UE. If there is a corresponding slice service at the location, the AMF corresponding to the slice is selected to provide service for the UE. Otherwise, the network chooses the default or predetermined AMF.
  • the network device will select the network function entity that does not provide slicing first if the UE is a non-slicing UE based on the location of the UE and the UE type (such as whether the UE is a UE with slicing capability). (As default, AMF is reserved), otherwise, the AMF that provides slices is selected.
  • the network device determines the slices that can be provided according to the UE location, slice (or category) and slice (or category) priority, and Choose a suitable AMF, and preferentially select a slice service with a higher priority for the UE. Otherwise, the network device chooses the default or predetermined AMF
  • the network device determines that the sliced AMF can be provided for the UE based on this information, otherwise the network device selects the default or predetermined AMF.
  • the network device determines the AMF that can provide the corresponding slice service for the UE based on this information, otherwise the network device selects the default or specific AMF
  • the network device determines whether the service can be provided based on the slice corresponding to the priority according to the information. For example, whether the network device can support the slices corresponding to the priority, if it can support the slices corresponding to the priority, whether the network device can still provide these slice services for the UE according to other factors (the maximum number of UEs supported in the slice, etc.). If yes, the network device selects an AMF that can provide priority slicing services for the UE; otherwise, the network device selects the default or specific AMF.
  • this embodiment 2 compared with the above embodiment 1, another network behavior is given, that is, based on the slice information in the RACH process, by distinguishing the UE (support or not, priority, etc.), the network device selects the appropriate AMF, So as to ensure the service of UEs with different needs.
  • the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • FIG. 7 is a schematic block diagram of a terminal provided by an embodiment of the present application. As shown in FIG. 7, the terminal 700 includes: a first sending module 702, and the first sending module 702 will be described below.
  • the first sending module 702 is configured to send the slice information of the terminal to the network device.
  • the first sending module is configured to carry slicing information through a radio resource control RRC message or an uplink message in a random access RACH process, and send the slicing information to the network device.
  • the uplink message includes at least one of the following: message 1 in the four-step RACH process, message 3 in the four-step RACH process, and message A in the two-step RACH process.
  • the slice information is carried by the reason value in the RRC message or the uplink message, where the reason value in the RRC message is used to characterize the reason why the standard triggers the RRC message, and the reason value in the uplink message is used to characterize the reason for triggering the RACH process. reason.
  • the content of the cause value in the RRC message includes slice information, or the content of the cause value in the uplink message includes slice information.
  • the slice information of the terminal includes at least one of the following: the slice identifier of the terminal, the category to which the slice of the terminal belongs, the priority of the slice of the terminal, the priority of the category to which the slice of the terminal belongs, the location information of the terminal, and the priority The selected public land mobile network PLMN identity.
  • the terminal further includes: a first receiving module, configured to receive slicing indication information sent by the network device before sending the slicing information required by the terminal to the network device;
  • the instruction information determines the slice information.
  • the slice indication information includes at least one of the following: a slice identifier supported by the network device, a slice category supported by the network device, a mapping relationship between a slice identifier supported by the network device and a slice category, and a slice identifier supported by the network device Priority, the priority of the slice category supported by the network device, the indication that the network device allows the reporting of slice information, the public land mobile network PLMN identity supported by the network device, the mapping relationship between the slice identity supported by the network device and the PLMN identity, the network device The mapping relationship between the supported slice category and the PLMN identifier, the threshold of the number of terminals defined by the slices supported by the network device, the threshold of the number of terminals defined by the slices supported by the PLMN, the threshold of the number of terminals defined by the slices supported by the session, the network device supports Threshold for the number of sessions defined by the slices of PLMN.
  • the first receiving module is configured to receive the slicing indication information sent by the network device in at least one of the following ways: receiving the slicing indication information by receiving the broadcast of the network device; and sending the predetermined signaling by the receiving network device Way, receiving slice indication information.
  • the first determining module is configured to determine the slice information according to the slice indication information including at least one of the following: according to the mapping relationship between the slice identifier supported by the network device and the slice category in the slice indication information, determine the slice to which the terminal belongs When it is determined that the slice of the terminal does not belong to the slice category indicated in the slice indication information, the slice of the terminal is assigned to the default category or a predetermined category; it is determined that the slice of the terminal does not belong to the slice indicated in the slice indication information Below, the terminal’s slice is attributed to the default or predetermined category; if it is determined that the terminal slice does not belong to the slice indicated in the slice indication information, the terminal’s slice is attributed to the default slice or non-slice; the terminal according to the network in the slice indication information
  • the mapping relationship between all the slice identifiers of the device and the slice category determines the category to which the slice of the terminal belongs.
  • the slice identifier of the terminal or the slice identifier supported by the network device includes at least one of the following: network slice selection auxiliary information, single network slice selection auxiliary information, and network slice identification.
  • the slice of the terminal includes at least one of the following: a requested slice, an allowed slice, a configured slice, and a default slice.
  • the terminal further includes at least one of the following: a second receiving module configured to receive a control result sent by a network device, where the control result includes: a result of the RACH process determined according to the slice information, or a trigger to the terminal The response of the RACH process; the third receiving module is used to receive the selection result sent by the network device, where the selection result includes at least one of the following: the access and mobility management entity AMF selected according to the slice information to provide services for the terminal , The session management function entity SMF selected according to the slice information to provide services for the terminal, the user plane function entity UPF selected according to the slice information to provide services for the terminal, and an indication of whether the required core network entity is selected.
  • the control result includes: a result of the RACH process determined according to the slice information, or a trigger to the terminal The response of the RACH process
  • the third receiving module is used to receive the selection result sent by the network device, where the selection result includes at least one of the following: the access and mobility management entity AMF selected according to the slice information to provide services
  • the result of the RACH process includes: successful execution of the RACH process and failure of the execution of the RACH process.
  • FIG. 8 is a schematic block diagram of a network device provided by an embodiment of the present application. As shown in FIG. 8, the network device 800 includes a fourth receiving module 802. The fourth receiving module 802 will be described below.
  • the fourth receiving module 802 is configured to receive the slice information of the terminal sent by the terminal.
  • the fourth receiving module is configured to use a radio resource control RRC message or an uplink message in a random access RACH process to carry slicing information, and receive slicing information sent by the terminal.
  • the uplink message includes at least one of the following: message 1 in the four-step RACH process, message 3 in the four-step RACH process, and message A in the two-step RACH process.
  • the slice information is carried by the reason value in the RRC message or the uplink message, where the reason value in the RRC message is used to characterize the reason why the standard triggers the RRC message, and the reason value in the uplink message is used to characterize the reason for triggering the RACH process. reason.
  • the content of the cause value in the RRC message includes slice information, or the content of the cause value in the uplink message includes slice information.
  • the slice information of the terminal includes at least one of the following: the slice identifier of the terminal, the category to which the slice of the terminal belongs, the priority of the slice of the terminal, the priority of the category to which the slice of the terminal belongs, the location information of the terminal, and the priority The selected public land mobile network PLMN identity.
  • the network device further includes: a second sending module, configured to send slicing indication information to the terminal before receiving the slicing information of the terminal sent by the terminal.
  • a second sending module configured to send slicing indication information to the terminal before receiving the slicing information of the terminal sent by the terminal.
  • the slice indication information includes at least one of the following: a slice identifier supported by the network device, a slice category supported by the network device, a mapping relationship between a slice identifier supported by the network device and a slice category, and a slice identifier supported by the network device Priority, the priority of the slice category supported by the network device, the indication that the network device allows the reporting of slice information, the public land mobile network PLMN identity supported by the network device, the mapping relationship between the slice identity supported by the network device and the PLMN identity, the network device The mapping relationship between the supported slice category and the PLMN identifier, the threshold of the number of terminals defined by the slices supported by the network device, the threshold of the number of terminals defined by the slices supported by the PLMN, the threshold of the number of terminals defined by the slices supported by the session, the network device supports The threshold of the number of sessions defined by the slices of PLMN, and the threshold of the number of sessions defined by the slices supported by the PLMN.
  • the second sending module is configured to send slicing indication information to the terminal in at least one of the following ways: sending slicing indication information to the terminal by broadcasting; sending predetermined signaling to the terminal Send slicing instructions.
  • the slice identifier of the terminal or the slice identifier supported by the network device includes at least one of the following: network slice selection auxiliary information, single network slice selection auxiliary information, and network slice identification.
  • the network device further includes: a judging module, which is used to judge whether the terminal can be provided with the slice required by the terminal according to the slice information, and obtain the judgment result.
  • a judging module which is used to judge whether the terminal can be provided with the slice required by the terminal according to the slice information, and obtain the judgment result.
  • the network device further includes: a third sending module, configured to send the judgment result to the terminal.
  • the third sending module is configured to send a response message including the slice that can provide the terminal to the terminal when the judgment result of the judgment module is that the slice of the terminal can be provided for the terminal.
  • the judging module is further configured to determine, according to the slice information, that the terminal meets the slicing condition, the network device determines that it can provide the terminal with the slice required by the terminal.
  • the slicing condition includes at least one of the following: the slice supported by the network device matches the slice required by the terminal, the slice category supported by the network device matches the category to which the slice required by the terminal belongs, and the location of the terminal provides slice services on the network device. Within the range, the priority of the slice supported by the network device meets the priority of the slice required by the terminal, the slice with a predetermined priority supported by the network device matches the slice with the terminal demand, and the slice supported by the network device matches the predetermined priority of the terminal demand.
  • the slice of the predetermined priority supported by the network device matches the slice of the predetermined priority required by the terminal
  • the category of the slice of the predetermined priority supported by the network device matches the category of the slice required by the terminal
  • the slice supported by the network device belongs The category matches the category of the slice of the predetermined priority required by the terminal.
  • the category of the slice of the predetermined priority supported by the network device matches the category of the slice of the predetermined priority of the terminal needs.
  • the slice category supported by the network device meets the needs of the terminal.
  • the category to which the slice belongs is lower than the threshold of the number of terminals defined by the slices supported by the network device, lower than the threshold of the number of terminals defined by the slices supported by the PLMN, lower than the threshold of the number of terminals defined by the slices supported by the session, and lower than the threshold of the number of terminals defined by the slices supported by the session
  • the threshold of the number of sessions defined by the supported slices is lower than the threshold of the number of sessions defined by the slices supported by the PLMN; the slices required by the terminal match the predetermined slices supported by the network device, and the predetermined slice required by the terminal matches the slice supported by the network device.
  • the judging module is also used to judge whether the terminal can be provided with slices required by the terminal according to the slice information, and to obtain the judgment result, including at least one of the following: execute the terminal according to whether the slices can be provided for the terminal with the terminal requirements.
  • the RACH process is controlled to obtain the control result, where the control result includes: the result of the RACH process determined according to the slice information, or the response to the RACH process triggered by the terminal; and the response to the terminal triggered according to whether the slice required by the terminal can be provided for the terminal RRC request message:
  • the terminal can provide a slice of terminal requirements, select at least one of the following services for the terminal: access and mobility management entity AMF, session management function entity SMF, and user plane function entity UPF.
  • the result of the RACH process includes: successful execution of the RACH process and failure of the execution of the RACH process.
  • the slice of the terminal includes at least one of the following: a requested slice, an allowed slice, a configured slice, and a default slice.
  • FIG. 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 900 shown in FIG. 9 includes a processor 910, and the processor 910 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the communication device 900 may further include a memory 920.
  • the processor 910 may call and run a computer program from the memory 920 to implement the method in the embodiment of the present application.
  • the memory 920 may be a separate device independent of the processor 910, or may be integrated in the processor 910.
  • the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 930 may include a transmitter and a receiver.
  • the transceiver 930 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 900 may specifically be a terminal in an embodiment of the present application, and the communication device 900 may implement corresponding procedures implemented by the terminal in each method in the embodiments of the present application. For brevity, details are not described herein again.
  • the communication device 900 may specifically be a network device of an embodiment of the application, and the communication device 900 may implement the corresponding process implemented by the network device in each method of the embodiment of the application. For the sake of brevity, details are not repeated here. .
  • FIG. 10 is a schematic structural diagram of a chip of an embodiment of the present application.
  • the chip 1000 shown in FIG. 10 includes a processor 1010, and the processor 1010 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 1000 may further include a memory 1020.
  • the processor 1010 can call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.
  • the memory 1020 may be a separate device independent of the processor 1010, or may be integrated in the processor 1010.
  • the chip 1000 may further include an input interface 1030.
  • the processor 1010 can control the input interface 1030 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 1000 may further include an output interface 1040.
  • the processor 1010 can control the output interface 1040 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the terminal in the embodiment of the present application, and the chip can implement the corresponding process implemented by the terminal in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the terminal in each method of the embodiment of the present application.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip, etc.
  • the processor of 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 above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • 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 decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • 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.
  • the memory 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 (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • DDR SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • Synchronous Link Dynamic Random Access Memory Synchronous Link Dynamic Random Access Memory
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment 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 connection Dynamic random access memory (Synch Link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.
  • the embodiments of the present application also provide a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium can be applied to the terminal in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the terminal in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the terminal in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the terminal in each method of the embodiment of the present application.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the terminal in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the terminal in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the terminal in each method of the embodiment of the present application.
  • details are not repeated here. .
  • the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the terminal in the embodiment of the present application.
  • the computer program runs on the computer, the computer executes the corresponding process implemented by the terminal in each method of the embodiment of the present application. For the sake of brevity, This will not be repeated here.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program runs on the computer, it causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • I won’t repeat it here.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is realized in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes. .

Landscapes

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

Abstract

本申请实施例公开了一种信息发送、接收方法、终端及网络设备。其中，该方法包括：终端将终端的切片信息发送给网络设备。通过本申请实施例，解决了相关技术中缺乏关于RAN支持网络切片的标准的技术问题，进而可以达到适应技术标准发展的效果。

Description

信息发送、接收方法、终端及网络设备 技术领域
本申请涉及通信领域，具体而言，涉及一种信息发送、接收方法、终端及网络设备。
背景技术
垂直行业对无线通信的强劲需求是有目共睹的，为了满足垂直行业的业务对延迟、移动性、可靠性、位置精度等方面的需求，无线接入网(Radio Access Network，简称为RAN)需要对如何在接入网支持垂直行业的业务进行增强。基于网络切片(slicing)，对不同需求的多个业务提供更低时延，更有目标性，更大灵活性和更高可扩展性的服务。但在相关技术中，并不涉及RAN支持的网络切片相关的行为。
因此，在相关技术中，缺乏关于RAN支持网络切片的标准。
针对上述的问题，目前尚未提出有效的解决方案。
发明内容
本申请实施例提供一种信息发送、接收方法、终端及网络设备，以解决相关技术中缺乏关于RAN支持网络切片的标准的技术问题，进而可以达到提供关于RAN支持网络切片的标准的效果。
第一方面，提供了一种信息发送方法，包括：
终端将所述终端的切片信息发送给网络设备。
第二方面，提供了一种信息接收方法，包括：
网络设备接收终端发送的所述终端的切片信息。
第三方面，提供了一种终端，包括：
第一发送模块，用于将所述终端的切片信息发送给网络设备。
第四方面，提供了一种网络设备，包括：
第四接收模块，用于接收终端发送的所述终端的切片信息。
第五方面，提供了一种终端，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面或其各实现方式中的方法。
第六方面，提供了一种网络设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第二方面或其各实现方式中的方法。
第七方面，提供了一种芯片，用于实现上述第一方面至第二方面中的任一方面或其各实现方式中的方法。具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行如上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第八方面，提供了一种存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第九方面，提供了一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第十方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
通过上述技术方案，由所述终端将所述终端的切片信息发送给网络设备，终端的切片信息即是终端需求的切片的切片信息，因此，在RAN中考虑了终端需要网络切片的需求，提供了关于RAN支持网络切片的标准，解决了相关技术中缺乏关于RAN支持网络切片的标准的技术问题，进而可以达到适应技术标准发展的效果。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是本申请实施例应用的通信系统的示意图。
图2是本申请实施例提供的信息发送方法的示意性流程图。
图3是本申请实施例提供的两步随机接入过程的示意图。
图4是本申请实施例提供的信息接收方法的示意性流程图。
图5是本申请实施例提供的实施方式1的示意图。
图6是本申请实施例提供的实施方式2的示意图。
图7是本申请实施例提供的终端的示意性框图。
图8是本申请实施例提供的网络设备的示意性框图。
图9是本申请实施例提供的一种通信设备的示意性结构图。
图10是本申请实施例的芯片的示意性结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统或5G系统等。
示例性的，本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110，网络设备110可以是与终端设备120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。可选地，该网络设备110可以是GSM系统或CDMA系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以 为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
该通信系统100还包括位于网络设备110覆盖范围内的至少一个终端设备120。作为在此使用的“终端设备”包括但不限于经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network，WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一终端设备的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线接口通信的终端设备可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话；可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System，PCS)终端；可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System，GPS)接收器的PDA；以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端设备可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
可选地，终端设备120之间可以进行设备到设备(Device to Device，D2D)通信。
可选地，5G系统或5G网络还可以称为新无线(New Radio，NR)系统或NR网络。
图1示例性地示出了一个网络设备和两个终端设备，可选地，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
可选地，该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端设备120，网络设备110和终端设备120可以为上文的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
基于上述说明，本申请实施例提出了一种信息发送方法。图2是本申请实施例提供的信息发送方法的示意性流程图，如图2所示，该方法包括：
S202，终端将终端的切片信息发送给网络设备，其中，需要说明的是，此处终端的切片信息可以是终端需求的切片的信息。
通过上述步骤，由终端将终端的切片信息发送给网络设备，终端的切片信息即是终端需求的切片信息，提供了RAN支持网络切片的标准，解决了相关技术中缺乏关于RAN支持网络切片的标准的技术问题，进而可以达到适应技术标准发展的效果。
需要说明的是，该方法中的终端可以是智能终端，例如，可以是一些智能手机、智能汽车、无人机、 机器人等智能终端。还可以是一些可穿戴设备，例如，智能手表，智能手环，智能眼镜等。
作为一种实施例，终端将终端的切片信息发送给网络设备时，终端可以通过多种方式，将终端的切片信息发送给网络设备，例如，终端可以通过无线资源控制RRC消息或随机接入RACH过程中的上行消息，携带切片信息，将切片信息发送给网络设备。其中，上述RRC消息可以是上行专用RRC消息(UL dedicated RRC消息)。
作为一种实施例，原则上，终端的切片信息是由终端发送给网络设备的，只要是终端向网络设备发送的上行消息均可以用于携带终端的切片信息，例如，可以是随机接入RACH过程中的上行消息。为便于对随机接入RACH过程中的上行消息进行说明，在本实施例中，先对随机接入RACH过程进行说明。
在NR中，RACH过程包括两种，一种是legacy)随机接入(4-step RACH)，另一种是，两步随机接入过程(2-step RACH)，下面分别说明。
legacy随机接入(4-step RACH)：
在RACH过程中，在Msg 3中携带触发/建立的原因值。
随机接入过程主要有如下事件触发：
- Initial access from RRC_IDLE；
- RRC Connection Re-establishment procedure；
- Handover；
- DL or UL data arrival during RRC_CONNECTED when UL synchronisation status is"non-synchronised"；
- UL data arrival during RRC_CONNECTED when there are no PUCCH resources for SR available；
- SR failure；
- Request by RRC upon synchronous reconfiguration；
- Transition from RRC_INACTIVE；
- To establish time alignment at SCell addition；
- Request for Other SI(see subclause 7.3)；
- Beam failure recovery.
在NR中，主要支持两种随机接入方式，基于竞争的随机接入方式和基于非竞争的随机接入方式。
步骤如下：
Step1：终端选择前导码(preamble)和物理随机接入信道(Physical Random Access Channel，简称为PRACH)资源(时频资源和码域资源)：
终端在选择的PRACH时频资源上发送选择的前导码，基站基于前导码可以估计上行时段(Timing)，和终端传输消息3所需要的授权(grant)资源的大小(大概知道，不能精确知道)。
Step2：网络发送RAR给终端：
终端发送消息1(Msg1)之后,开启一个RAR window，在该window内监测物理下行控制信道(Physical Downlink Control Channel，简称为PDCCH)。该PDCCH采用随机接入无线网络临时标识(Random Access Radio Network Temporary Identifier，简称为RA-RNTI)加扰。
成功监测到RA-RNTI加扰的PDCCH之后，终端能够获得该PDCCH调度的物理下行共享信道(Physical Downlink Shared Channel，简称为PDSCH)，其中包含RAR(随机接入响应)。
RAR的子头(subheader)中包含BI，用于指示重传消息1的回退时间；
RAR中的RAPID：网络响应收到的前导码索引(preamble index)；
RAR的有效载荷(payload)中包含了标签(TAG)，用于调整上行时序；
UL grant(上行授权)：用于调度Msg3的上行资源指示；
Temporary C-RNTI(临时的小区无线网络临时标识)：用于加扰消息4的PDCCH(初始接入)；
Step3：终端在调度资源上传输RRC消息
Msg3的消息主要用于通知网络该RACH过程是由什么事件触发。比如，如果是初始接入随机过程，则在Msg3中会携带终端标识和建立原因(establishment cause)；如果是RRC重建，则会携带连接态终端标识和重建原因(re-establishment cause)；
同时，Msg3携带的终端标识的竞争冲突可以在第四步中得到解决；
Step4：竞争冲突解决
Msg4用于冲突解决。
两步随机接入过程(2-step RACH)：
两步RACH可以提高时延，同时也能降低信令开销。图3是本申请实施例提供的两步随机接入过程的示意图，如图3所示，基本的方式是，Msg A传输四步RACH的Msg1+Msg3，Msg B传输四步RACH的Msg2+Msg4。
同样的，在2-step RACH过程中，也会在Msg A中携带触发/建立的原因值。
基于上述说明，作为一种实施例，上行消息可以包括以下至少之一：四步RACH过程中的消息1，四步RACH过程中的消息3，两步RACH过程中的消息A。即通过上述三种上行消息中的至少之一携带终端的切片信息，将终端的切片信息发送给网络设备。
作为一种实施例，通过RRC消息或上行消息中的原因值携带切片信息，其中，RRC消息中的原因值用于表征标准触发RRC消息的原因，上行消息中的原因值用于表征触发RACH过程的原因。其中，RRC消息中的原因值的内容包括切片信息，或，上行消息中的原因值的内容包括切片信息。
作为一种实施例，终端的切片信息可以包括多种，只要能够用于网络设备确定终端需求的网络切片即可。例如，可以包括以下至少之一：终端的切片标识，终端的切片所属的类别，终端的切片的优先级，终端的切片所属的类别的优先级，终端的位置信息，优先选择的公共陆地移动网PLMN标识。
其中，终端的切片标识用于标识终端的切片，即用于标识终端需求的切片。切片标识的形式可以多种，例如，可以采用简单的数字标识，字母标识，文字标识等，还可以采用一些复杂字符等。终端的切片所属的类别可以是基于应用的不同所进行的分类，也可以依据具体网络不同所进行的分类等。终端的切片的优先级，可以是优先使用的切片的等级，例如，可以是等级越高，越能够优先使用。终端的切片所属的类别的优先级，可以是优先使用的切片类别的等级，例如，可以是等级越高，越能够优先使用。
作为一种实施例，在终端将终端的切片信息发送给网络设备之前，还包括：终端接收网络设备发送的指示信息，该指示信息用于指示是否允许终端基于切片信息执行不同的操作，或者，指示是否允许终端上报切片信息。
作为一种实施例，在终端将终端的切片信息发送给网络设备之前，还包括：终端接收网络设备发送的切片指示信息；终端根据切片指示信息确定切片信息。
需要说明的是，切片指示信息可以是用于网络设备向终端指示网络设备能够支持的切片的相关信息。
作为一种实施例，切片指示信息可以包括多种，例如，可以包括以下至少之一：网络设备支持的切片标识，网络设备支持的切片类别，网络设备支持的切片标识与切片类别之间的映射关系，网络设备支持的切片标识的优先级，网络设备支持的切片类别的优先级，网络设备允许切片信息上报的指示，网络设备支持的公共陆地移动网PLMN标识，网络设备支持的切片标识与PLMN标识之间的映射关系，网络设备支持的切片类别与PLMN标识之间的映射关系，网络设备支持的切片所限定的终端数目阈值，PLMN支持的切片所限定的终端数目阈值，会话支持的切片所限定的终端数目阈值，网络设备支持的切片所限定的会话数目阈值，PLMN支持的切片所限定的会话数目阈值。
其中，切片指示信息中与终端的切片信息对应的内容，可以有与终端的切片信息相同的含义。另外，网络设备支持的切片标识，网络设备支持的切片类别，网络设备支持的切片标识的优先级，网络设备支持的切片类别的优先级，网络设备支持的公共陆地移动网PLMN标识，上述对象可以是一个，也可以是多个，例如，可以是包括多个的列表。
作为一种实施例，终端接收网络设备发送的切片指示信息时，可以采用多种方式，例如，终端通过以下方式至少之一，接收网络设备发送的切片指示信息：终端通过接收网络设备广播的方式，接收切片指示信息；终端通过接收网络设备发送预定信令的方式，接收切片指示信息。需要说明的是，通过上述广播的方式可以通过设置广播的范围，使得网络设备广播的范围能够覆盖到该终端。上述通过预定信令的方式时，预定信令可以是多种，例如，可以是专用RRC信令，比如，RRCrelease信令。
作为一种实施例，终端根据切片指示信息确定切片信息时，依据切片信息的不同内容，确定切片信息也不同，例如，可以包括以下至少之一：
终端根据切片指示信息中网络设备支持的切片标识与切片类别之间的映射关系，确定终端的切片所属的类别；即只要终端的切片属于切片指示信息中所指示的切片类别的情况下，就可以依据切片标识与切片类别之间的映射关系，确定终端的切片所属的类别。
终端确定终端的切片不属于切片指示信息中所指示的切片类别的情况下，终端将终端的切片归属于默认类别或者预定类别；其中，默认类别和预定类别可以是提前设置的。
终端确定终端的切片不属于切片指示信息中所指示的切片的情况下，终端将终端的切片归属于默认类别或者预定类别；即不管是终端的切片不属于切片指示信息中所指示的切片类别，还是终端的切片不属于切片指示信息中所指示的切片，均能够将终端的切片进行归属到一个类别。
终端确定终端的切片不属于切片指示信息中所指示的切片的情况下，终端将终端的切片归属于默认切片或者非切片。即在终端的切片不属于切片指示信息中所指示的切片时，将终端的切片也能够归属于一个切片或者非切片。
终端根据切片指示信息中网络设备的所有切片标识与切片类别之间的映射关系，确定终端的切片所属的类别。即网络设备将网络设备的所有切片的相关信息发送给终端，终端根据所有切片标识与切片类别之间的映射关系，确定终端的切片所属的类别。相对于上述网络设备仅发送支持的切片相关的信息，此处提供的网络设备发送所有的切片相关的信息也属于一种方式。
作为一种实施例，终端的切片标识或者网络设备支持的切片标识均可以包括多种，例如，均可以包括以下至少之一：网络切片选择辅助信息，单网络切片选择辅助信息，网络切片的标识。
作为一种实施例，终端的切片(即终端需求的切片)可以包括以下至少之一：请求的切片(requested切片)，允许的切片(allowed切片)，配置的切片(configured切片)，默认的切片(default)，签约的切片。
作为一种实施例，在终端将终端的切片信息发送给网络设备后，还可以包括以下至少之一：
终端接收网络设备发送的控制结果，其中，控制结果包括：依据切片信息确定的RACH过程的结果，或对终端触发的RACH过程的响应；
终端接收网络设备发送的选择结果，其中，选择结果包括以下至少之一：依据切片信息选择的用于为终端提供服务的接入和移动性管理实体AMF，依据切片信息选择的用于为终端提供服务的会话管理功能实体SMF，依据切片信息选择的用于为终端提供服务的用户面功能实体UPF，是否选择到需求的核心网实体的指示。
其中，RACH过程的结果可以包括：RACH过程成功和RACH过程失败。对终端触发的RACH过程的响应可以包括以下至少之一：网络设备响应UE(使得UE RACH成功)，网络设备发送针对UE的RACH响应消息(使得UE RACH成功)，网络设备发送短RACH backoff(使得RACH尽快成功)，网络设备不响应UE，网络设备不发送针对UE的Msg 4或Msg B，网络设备发送长RACH backoff。
本申请实施例还提出了一种信息接收方法，图4是本申请实施例提供的信息接收方法的示意性流程图，如图4所示，该方法包括：
S402，网络设备接收终端发送的终端的切片信息。
通过上述步骤，网络设备接收终端发送的终端的切片信息，终端的切片信息即是终端需求的切片的切片信息，因此，在RAN中考虑了终端需要网络切片的需求，提供了关于RAN支持网络切片的标准，解决了相关技术中缺乏关于RAN支持网络切片的标准的技术问题，进而可以达到适应技术标准发展的效果。
需要说明的是，该方法中的网络设备可以是接入网中的设备，例如，各种类型的基站。接入网可以是无线接入网RAN等。
作为一种实施例，网络设备接收终端发送的切片信息时，网络设备可以通过多种方式，接收终端发送的终端的切片信息，例如，网络设备可以通过无线资源控制RRC消息或随机接入RACH过程中的上行消息，携带切片信息，接收终端发送的切片信息。其中，上述RRC消息可以是上行专用RRC消息(UL dedicated RRC消息)。
作为一种实施例，原则上，终端的切片信息是由终端发送给网络设备的，只要是终端向网络设备发送的上行消息均可以用于携带终端的切片信息，例如，可以是随机接入RACH过程中的上行消息。基于上述对RACH过程的说明，该RACH过程中的上行消息可以包括以下至少之一：四步RACH过程中的消息消息1，四步RACH过程中的3，两步RACH过程中的消息A。因此，网络设备通过上述三种消息至少之一均可以接收到终端的切片信息。
作为一种实施例，通过RRC消息或上行消息中的原因值携带切片信息，其中，RRC消息中的原因值用于表征标准触发RRC消息的原因，上行消息中的原因值用于表征触发RACH过程的原因。其中，RRC消息中的原因值的内容包括切片信息，或，上行消息中的原因值的内容包括切片信息。
作为一种实施例，终端的切片信息可以包括多种，只要能够用于网络设备确定终端需求的网络切片即可。例如，可以包括以下至少之一：终端的切片标识，终端的切片所属的类别，终端的切片的优先级，终端的切片所属的类别的优先级，终端的位置信息，优先选择的公共陆地移动网PLMN标识。
同样，对应于上述终端侧，终端的切片标识用于标识终端的切片，即用于标识终端需求的切片。切片标识的形式可以多种，例如，可以采用简单的数字标识，字母标识，文字标识等，还可以采用一些复杂字符等。终端的切片所属的类别可以是基于应用的不同所进行的分类，也可以依据具体网络不同所进行的分类等。终端的切片的优先级，可以是优先使用的切片的等级，例如，可以是等级越高，越能够优先使用。终端的切片所属的类别的优先级，可以是优先使用的切片类别的等级，例如，可以是等级越高，越能够优先使用。
作为一种实施例，在网络设备接收终端发送的终端的切片信息之前，还包括：网络设备向终端发送切片指示信息。其中，切片指示信息可以是用于网络设备向终端指示网络设备能够支持的切片的相关信息。
作为一种实施例，在网络设备接收终端发送的终端的切片信息之前，还包括：网络设备向终端发送所知的切片信息。其中，切片信息可以是用于网络设备向终端指示网络设备所知的切片的相关信息，如优先级，如切片与类别的关系等。
作为一种实施例，切片指示信息也可以包括多种，例如，可以包括以下至少之一：网络设备支持的切片标识，网络设备支持的切片类别，网络设备支持的切片标识与切片类别之间的映射关系，网络设备支持的切片标识的优先级，网络设备支持的切片类别的优先级，网络设备允许切片信息上报的指示，网络设备支持的公共陆地移动网PLMN标识，网络设备支持的切片标识与PLMN标识之间的映射关系，网络设备支持的切片类别与PLMN标识之间的映射关系，网络设备支持的切片所限定的终端数目阈值，PLMN支持的切片所限定的终端数目阈值，会话支持的切片所限定的终端数目阈值，网络设备支持的切片所限定的会话数目阈值，PLMN支持的切片所限定的会话数目阈值。
与终端侧对应地，切片指示信息中与终端的切片信息对应的内容，可以有与终端的切片信息相同的含义。另外，网络设备支持的切片标识，网络设备支持的切片类别，网络设备支持的切片标识的优先级，网络设备支持的切片类别的优先级，网络设备支持的公共陆地移动网PLMN标识，上述对象可以是一个，也可以是多个，例如，可以是包括多个的列表。
作为一种实施例，网络设备向终端发送切片指示信息时，也可以采用多种方式，例如，网络设备通过以下方式至少之一，向终端发送切片指示信息：网络设备通过广播的方式，向终端发送切片指示信息；网络设备通过向终端发送预定信令的方式，向终端发送切片指示信息。对应地，通过上述广播的方式可以通过设置广播的范围，使得网络设备广播的范围能够覆盖到该终端。上述通过预定信令的方式时，预定信令可以是多种，例如，可以是专用RRC信令，比如，RRCrelease信令。
作为一种实施例，终端的切片标识或者网络设备支持的切片标识均可以包括多种，例如，均可以包括以下至少之一：网络切片选择辅助信息，单网络切片选择辅助信息，网络切片的标识。
作为一种实施例，在网络设备接收终端发送的终端的切片信息之后，网络设备还可以根据切片信息判断是否能够为终端提供终端需求的切片，得到判断结果。即网络设备确定是否能够为终端提供终端需求的切片，或者是确定是否能够为终端提供终端的切片，以便后续对终端提供服务。
作为一种实施例，在网络设备确定是否能够为终端提供终端需求的切片之后，还可以将是否能够为终端提供终端需求的切片的判断结果发送给终端，即网络设备向终端发送判断结果。通过将判断结果发送给终端，使得终端知晓网络设备是否能够为终端提供终端需求的切片，以便终端对应地执行与网络设备适应的行为。
作为一种实施例，在网络设备向终端发送判断结果时，可以依据判断结果的不同而执行不同的处理，例如，在判断结果为能够为终端提供终端的切片的情况下，网络设备向终端发送包含能够为终端提供终端的切片的响应消息。即在网络设备确定能够为终端提供终端的切片信息的情况下，才向终端设备发送，否则不进行发送。
作为一种实施例，网络设备根据切片信息判断是否能够为终端提供终端需求的切片可以采用以下方式：网络设备根据切片信息确定终端满足切片条件的情况下，网络设备确定能够为终端提供终端需求的切片。
作为一种实施例，切片条件依据切片信息的不同也不同，例如，可以包括以下至少之一：网络设备支持的切片与终端需求的切片匹配，网络设备支持的切片类别与终端需求的切片所属的类别匹配，终端的位置在网络设备提供切片服务的范围内，网络设备支持的切片的优先级满足终端需求的切片的优先级，网络设备支持的预定优先级的切片与终端需求的切片匹配，网络设备支持的切片与终端需求的预定优先 级的切片匹配，网络设备支持的预定优先级的切片与终端需求的预定优先级切片匹配，网络设备支持的预定优先级的切片所属的类别与终端需求的切片所属的类别匹配，网络设备支持的切片所属的类别与终端需求的预定优先级的切片所属的类别匹配，网络设备支持的预定优先级的切片所属的类别与终端需求的预定优先级切片所属的类别匹配，网络设备支持的切片类别满足终端需求的切片所属的类别，低于网络设备支持的切片所限定的终端数目阈值，低于PLMN支持的切片所限定的终端数目阈值，低于会话支持的切片所限定的终端数目阈值，低于网络设备支持的切片所限定的会话数目阈值，低于PLMN支持的切片所限定的会话数目阈值；终端需求的切片与网络设备支持的预定切片匹配，终端需求的预定切片与网络设备支持的切片匹配。
其中，对于切片条件：低于网络设备支持的切片所限定的终端数目阈值，低于PLMN支持的切片所限定的终端数目阈值，低于会话支持的切片所限定的终端数目阈值，低于网络设备支持的切片所限定的会话数目阈值，低于PLMN支持的切片所限定的会话数目阈值，其中，低于网络设备支持的切片所限定的终端数目阈值，可以是网络设备支持的切片所能够提供服务的终端或PDU(协议数据单元Protocol Data Unit)会话或DRB(数据无线承载Data Radio Bearer)的最大数目，以终端数目阈值为例，对于网络设备支持的切片而言，最多为3个终端提供服务，这里的3即是终端数目阈值。需要说明的是，3仅仅是一个举例，也可以是依据切片的具体情况的其它数目。
对于切片条件：网络设备选择终端需求的切片与网络设备支持的更匹配的，例如，网络设备指示支持切片标识为1-5的切片，终端1需求切片标识为1-3的切片，终端2需求切片标识为1-4的切片，网络设备选终端2。又例如，网络设备指示支持切片标识为1-5的切片，切片标识为1到5的优先级越来越低，终端1需求切片标识为1-3，终端2需求切片标识为2-5，网络设备选终端1。
基于上述切片条件，针对上述小于网络设备支持的切片所限定的终端数目阈值的情况，在小于网络设备支持的切片所限定的终端数目阈值，并且大于网络设备支持的切片所限定的终端数目的另一阈值的情况下，网络设备确定是否能够为终端提供需求的切片。
需要说明的是，上述对切片标识所进行的举例也同样适用于切片类别的判断，也适用于切片标识优先级的判断，还适用于切片类别的优先级的判断等，在此不进行一一举例。
另外，对于切片条件：终端需求的切片与网络设备支持的预定切片匹配，例如，终端需求的切片可以是多个，比如，终端需求的切片的标识是1，3，5，而网络设备支持的预定切片的标识是1，3，5，8，则可以认为终端需求的切片与网络设备支持的预定切片匹配；但如果网络设备支持的预定切片的标识是1，3，7，9，则可以认为终端需求的切片与网络设备支持的预定切片是不匹配的。还有一种情况，终端需求的切片是需要能够为预定数目的终端提供服务，而网络设备支持的预定切片如果也能为预定数目的终端提供服务，则认为终端需求的切片与网络设备支持的预定切片匹配，否则认为终端需求的切片与网络设备支持的预定切片不匹配。例如，终端需求的切片是需要能够为3个以上的终端提供服务，而网络设备支持的预定切片如果也能为3个以上的终端提供服务，则认为终端需求的切片与网络设备支持的预定切片匹配，但如果网络设备支持的预定切片如果不能为3个以上的终端提供服务，则认为终端需求的切片与网络设备支持的预定切片不匹配。
作为一种实施例，网络设备根据切片信息判断是否能够为终端提供终端需求的切片，得到判断结果，包括以下至少之一：
网络设备依据是否能够为终端提供的终端需求的切片，对终端执行RACH过程控制，得到控制结果，其中，控制结果包括：依据切片信息确定的RACH过程的结果，或对终端触发的RACH过程的响应；
网络设备依据是否能够为终端提供的终端需求的切片，向终端执反馈控制结果，其中，控制结果包括：依据切片信息确定的RACH过程的结果，或对终端触发的RACH过程的响应；
网络设备依据是否能够为终端提供的终端需求的切片，响应终端触发的RRC请求消息；
网络设备依据是否能够为终端提供的终端需求的切片，选择为终端提供服务的以下至少之一：接入和移动性管理实体AMF，会话管理功能实体SMF，用户面功能实体UPF。
其中，RACH过程的结果可以包括：执行RACH过程成功和执行RACH过程失败。对终端触发的RACH过程的响应可以包括以下至少之一：网络设备响应UE(使得UE RACH成功)，网络设备发送针对UE的RACH响应消息(使得UE RACH成功)，网络设备发送短RACH backoff(使得RACH尽快成功)，网络设备不响应UE，网络设备不发送针对UE的Msg 4或Msg B，网络设备发送长RACH backoff。
作为一种实施例，终端的切片(即终端需求的切片)可以包括以下至少之一：请求的切片(requested切片)，允许的切片(allowed切片)，配置的切片(configured切片)，默认的切片(default切片)，签约的切片。
结合上述实施例及优选实施例，下面以终端为UE为例，对本申请所提供的优选实施方式进行说明。
在相关技术中，未考虑如何使得UE快速接入所需要的网络切片的小区，在本发明优选实施方式中，提供了一种基于切片的随机接入方法，例如，通过UE(以下以UE为例说明)在RACH过程中携带切片信息，使得UE能够快速接入，避免UE接入和业务服务的时延。
该基于切片的随机接入方法，可以包括：UE在RACH过程中携带切片信息，其中，该切片信息用于网络设备执行接入控制(例如，确定执行RACH过程的结果)，和/或，选择合适的网络功能实体，例如，合适的网络功能实体包括以下至少之一：接入和移动性管理实体(Access and Mobility Management Function，简称为AMF)，会话管理功能实体(Session Management Function，简称为SMF)，用户面功能实体(User Plane Function，简称为UPF)等。
UE的切片信息包括以下至少之一：UE的切片标识，UE的切片所属的类别，UE的切片的优先级，UE的切片所属的类别的优先级，UE的位置信息，优先选择的公共陆地移动网PLMN标识。
可选地，在UE将切片信息发送给网络设备之前，网络设备通过广播或通过专用无线资源控制RRC消息向UE发送切片指示信息，该切片指示信息包括以下至少之一：网络设备支持的切片类别，网络设备支持的切片标识，网络设备支持的切片标识和切片类别的映射关系，网络设备支持的切片类别的优先级，网络设备支持的切片标识的优先级，网络设备允许切片信息上报的指示，网络设备支持的公共陆地移动网PLMN标识，网络设备支持的切片标识与PLMN标识之间的映射关系，网络设备支持的切片类别与PLMN标识之间的映射关系，网络设备支持的切片所限定的终端数目阈值，PLMN支持的切片所限定的终端数目阈值，会话支持的切片所限定的终端数目阈值，网络设备支持的切片所限定的会话数目阈值，PLMN支持的切片所限定的会话数目阈值。
另外，在UE向网络设备发送终端的切片信息之前，UE可以基于UE需求的切片和网络设备发送的切片指示信息，确定切片信息。
需要说明的是，上述不管是切片信息中的切片标识还是切片指示信息中的切片标识，均可以包括以下至少之一：网络切片选择辅助信息(NSSAI,Network Slice Selection Assistance Information，单网络切片选择辅助信息(S-NSSAI,Single Network Slice Selection Assistance Information，网络切片的标识(Network Slicing Identity,NSID)。
下面以具体的RACH过程为例对实施方式进行说明。
实施方式1
UE通过RACH过程携带切片信息。例如，可以利用RACH过程中的Msg 3或Msg A消息携带。比如，可以利用RACH过程中携带的第一cause原因值指示切片信息。该切片信息，用于网络设备执行接入控制(如确定RACH响应方式或结果)。该切片信息可以包括以下至少之一：UE的切片标识，UE的切片所属的类别，UE的切片的优先级，UE的切片所属类别的优先级，UE位置信息。图5是本申请实施例提供的实施方式1的示意图，如图5所示，该实施方式包括：
S1，网络设备通过服务小区广播切片相关信息。
广播的切片相关信息，可以包括以下至少之一：切片标识(具体的，切片标识可以包括：NSSAI，S-NSSAI，NSID)；切片类别(包括类别标识)；切片标识和切片类别的映射关系；切片类别的优先级；切片标识的优先级。
切片相关信息，可以包括服务小区支持的切片，也可以包括服务小区不支持的切片。其中，服务小区支持的切片即是网络支持的切片，也即是网络所包括的网络设备支持的切片。
切片相关信息，也可以是通过专用(dedicated)RRC信令，如RRCrelease指示。
S2，UE非接入层(Non-Access Stratrum，简称为NAS)向UE接入层(Access Stratum，简称为AS)发送指示信息，该指示信息为UE相关的切片信息。其中：
指示信息体现为第一cause原因值。
原因值的内容为切片信息。
切片信息可以包括以下至少之一：UE的切片标识，UE的切片所属的类别，UE的切片的优先级，UE的切片所属类别的优先级，UE位置信息。
S3，UE AS触发RACH过程，在RACH过程中携带UE相关的切片信息。其中：
RACH过程为2-step RACH，4-step RACH。
在Msg 3或Msg A中携带该切片信息。
利用RACH中的第一cause原因值，携带该切片信息。
该切片信息，例如，cause原因值携带在建立请求(establishment request)消息，或重建请求(reestablishment request)消息，或恢复请求(Resume request)消息中。
cause原因值为在establishmentCause，或reestablishmentCause，或ResumeCause引入的新的原因值，用于体现切片信息。
cause原因值内容为该切片信息。
该切片信息可以包括以下至少之一：UE的切片标识，UE的切片所属的类别，UE的切片的优先级，UE的切片所属类别的优先级，UE位置信息，切片请求指示。切片信息，可以是一个，也可以是多个，例如，一个列表(list)。
切片信息中UE的切片可以包括以下之一：requested切片，allowed切片，configured切片，签约切片，即切片信息可以体现为切片标识。
另外：
UE确定UE的切片所属的切片类别时，可以根据小区指示的切片和类别的关系确定。若是UE的切片不属于小区指示的类别中的切片时，UE可以将该切片归属于默认类别，或预定类别。
UE确定UE的切片不属于小区指示的切片时，UE可以将该切片归属于默认类别，或预定类别，也可以直接上报该切片标识。
UE确定UE的切片不属于小区指示的切片时，UE可以将该切片归属于默认切片或非切片。
此外，网络也可以给所有切片信息和/或所有切片信息和类别的关系，该切片不一定是当前网络支持的切片。
S4，网络设备接收RACH中携带的第一cause原因值，确定切片信息，进而执行接入控制(如是否响应该UE的RACH过程，是否发送针对该UE的Msg 4或Msg B，是否发送长/短RACH backoff值等)。下面举例说明。
若cause值为UE位置，网络设备根据UE的位置，确定可以提供的切片。即网络设备根据UE的位置，确定该位置的切片，确定能否为UE提供切片服务。或者，网络设备根据UE的位置和切片优先级，或，UE的位置和切片需求，确定该位置的切片，确定能否为UE提供的优先的切片服务。若该位置有对应的切片服务，网络设备响应UE，或发送针对UE的RACH响应消息，或发送短RACH backoff。否则，网络设备不响应UE，或不发送针对UE的Msg 4或Msg B，或发送长RACH backoff。
若cause原因值为UE位置和切片请求指示(或UE的其它切片信息等)，网络设备根据这些信息，确定可以为UE提供对应的，UE需求的切片，网络设备响应UE(使得UE RACH成功)，或发送针对UE的RACH响应消息(使得UE RACH成功)，或发送短RACH backoff(使得RACH尽快成功)。否则，网络不响应UE，或不发送针对UE的Msg 4或Msg B，或发送长RACH backoff。
若cause原因值为UE的切片标识，或，UE的切片所属的类别，网络设备根据该信息，确定为能为该UE提供对应切片的服务，网络设备响应UE(使得UE RACH成功)，或发送针对UE的RACH响应消息(使得UE RACH成功)，或发送短RACH backoff(使得RACH尽快成功)。否则，网络设备不响应UE，或不发送针对UE的Msg4或Msg B，或发送长RACH backoff。
若cause原因值为UE的切片标识的优先级，或，UE的切片所属的类别的优先级，网络设备根据该信息，确定是否能基于优先的切片提供服务。例如，网络设备是否能够支持优先级对应的切片，如果能够支持这些优先级对应的切片，根据其他因素(该切片下最大支持的UE数目等)网络设备是否还能为UE提供这些切片服务。若是，网络设备响应UE(使得UE RACH成功)，或发送针对UE的RACH响应消息(使得UE RACH成功)，或发送短RACH backoff(使得RACH尽快成功)。否则，网络设备不响应UE，或不发送针对UE的Msg 4或Msg B，或发送长RACH backoff。
若cause原因值为UE位置，网络设备根据UE的位置和UE类型(如UE是否为由切片能力的UE)，若UE非有切片能力的UE，网络设备所属的网络是切片提供的网络，则网络设备可以不响应UE。
S5，UE根据网络设备发送的消息，确定RACH结果，执行后续操作。
通过上述实施方式1，基于RACH过程中的切片信息，网络设备执行接入控制(如是否响应该UE的RACH过程，是否发送针对该UE的Msg 4或MsgB，是否发送长/短RACH backoff值等)，区分UE(是否支持，优先级等等)，保证需求UE的优先接入。
实施方式2
UE通过RACH过程携带切片信息。例如，可以利用RACH过程中的Msg 3或Msg A消息携带。比如，可以利用RACH过程中携带的第一cause原因值指示该切片信息。该切片信息，用于网络设备选择合适的网络功能实体，例如，AMF，SMF UPF，从而为UE提供服务。下面以网络实体为AMF为例进行说明，其它的网络功能实体，例如，SMF,UPF也可以相应地被选择，从而为UE提供服务，不分别具体展开说明。该切片信息可以包括以下至少之一：UE的切片标识，UE的切片所属的类别，UE的切片的优先级，UE的切片所属类别的优先级，UE位置信息等。图6是本申请实施例提供的实施方式2的示意图，如图6所示，该实施方式包括：
S1，网络设备通过服务小区广播切片相关信息。其中：
该切片相关信息可以包括以下至少之一：切片标识(具体的，切片标识可以包括：NSSAI，S-NSSAI，NSID)；切片类别(包括类别标识)；切片标识和切片类别的映射关系；切片类别的优先级；切片标识的优先级。
切片相关信息，可以包括服务小区支持的切片，也可以包括服务小区不支持的切片。其中，服务小区支持的切片即是网络支持的切片，也即是网络所包括的网络设备支持的切片。
切片相关信息，也可以是通过专用(dedicated)RRC信令，如RRCrelease指示。
S2，UE NAS向UE AS发送指示信息，该指示信息为UE相关的切片信息。其中：
指示信息体现为第一cause原因值。
原因值的内容为切片信息。
切片信息可以包括以下至少之一：UE的切片标识，UE的切片所属的类别，UE的切片的优先级，UE的切片所属类别的优先级，UE位置信息。
S3，UE AS触发RACH过程，在RACH过程中携带UE相关的切片信息。其中：
RACH过程为2-step RACH，4-step RACH.。
在Msg 3或Msg A中携带该切片信息。
利用RACH中的第一cause原因值，携带该切片信息。
该切片信息，例如，cause原因值携带在establishment request消息，或reestablishment request消息，或Resume request消息中。
cause原因值为在establishmentCause，或reestablishmentCause，或ResumeCause引入的新的原因值，用于体现切片信息。
cause原因值内容为切片信息。
该切片信息可以包括以下至少之一：UE的切片标识，UE的切片所属的类别，UE的切片的优先级，UE的切片所属类别的优先级，UE位置信息，切片请求指示。切片信息，可以是一个，也可以是多个，例如，一个list。
UE切片信息中UE的切片可以包括以下之一：requested切片，allowed切片，configured切片。即切片信息可以体现为切片标识。
另外：
UE确定UE的切片所属的切片类别时，可以根据小区指示的切片和类别的关系确定。若是UE的切片不属于小区指示的类别中的切片时，UE可以将该切片归属于默认类别，或预定类别。
UE确定UE的切片不属于小区指示的切片时，UE可以将该切片归属于默认类别，或预定类别，也可以直接上报该切片标识。
S4，网络设备接收RACH中携带的第一cause原因值，确定切片信息，进而为UE选择合适的AMF，为UE提供服务。下面举例说明。
若cause值为UE位置，网络设备根据UE的位置，确定可以提供的切片。若该位置有对应的切片服务，选择该切片对应的AMF为UE提供服务。否则网络选择默认或预定AMF。
若cause值为UE位置，网络设备根据UE的位置和UE类型(如UE是否为有切片能力的UE)，若UE为非有切片能力的UE，网络设备优先选择不提供切片的网络功能实体(如默认，预定AMF)，否则，选择提供切片的AMF。
若cause值为UE位置，切片(或类别)，和切片(或类别)优先级，网络设备根据UE的位置，切片(或类别)和切片(或类别)优先级，确定可以提供的切片，以及选择合适的AMF，为UE优先选 择优先级高的切片的服务。否则网络设备选择默认或预定AMF
若cause值为UE位置和切片请求指示，网络设备根据这些信息，确定可以为UE提供切片的AMF，否则网络设备选择默认或预定AMF。
若cause值为UE的切片标识，或，UE的切片所属的类别，网络设备根据该信息，确定能为该UE提供对应切片服务的AMF，否则网络设备选择默认或特定AMF
若cause值为UE的切片标识的优先级，或，UE的切片所属的类别优先级，网络设备根据该信息，确定是否能基于优先级对应的切片提供服务。例如，网络设备是否能够支持优先级对应的切片，如果能够支持这些优先级对应的切片，根据其他因素(该切片下最大支持的UE数目等)网络设备是否还能为UE提供这些切片服务。若是，网络设备选择能为UE提供优先切片服务的AMF，否则网络设备选择默认或特定AMF。
通过本实施方式2，对比上述实施方式1，给出了另一种网络行为，即基于RACH过程中的切片信息，通过区分UE(是否支持，优先级等等)，网络设备选择合适的AMF，从而保证不同需求UE的服务。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
上文中结合图1至图6，详细描述了根据本申请实施例的信息发送、接收方法，下面将结合图7至图9，描述根据本申请实施例的终端和网络设备。
图7是本申请实施例提供的终端的示意性框图，如图7所示，该终端700包括：第一发送模块702，下面对该第一发送模块702进行说明。
第一发送模块702，用于将终端的切片信息发送给网络设备。
作为一个实施例，第一发送模块，用于通过无线资源控制RRC消息或随机接入RACH过程中的上行消息，携带切片信息，将切片信息发送给网络设备。
作为一个实施例，上行消息包括以下至少之一：四步RACH过程中的消息1，四步RACH过程中的消息3，两步RACH过程中的消息A。
作为一个实施例，通过RRC消息或上行消息中的原因值携带切片信息，其中，RRC消息中的原因值用于表征标准触发RRC消息的原因，上行消息中的原因值用于表征触发RACH过程的原因。
作为一个实施例，RRC消息中的原因值的内容包括切片信息，或，上行消息中的原因值的内容包括切片信息。
作为一个实施例，终端的切片信息包括以下至少之一：终端的切片标识，终端的切片所属的类别，终端的切片的优先级，终端的切片所属的类别的优先级，终端的位置信息，优先选择的公共陆地移动网PLMN标识。
作为一个实施例，该终端还包括：第一接收模块，用于在将终端需求的切片的切片信息发送给网络设备之前，接收网络设备发送的切片指示信息；第一确定模块，用于根据切片指示信息确定切片信息。
作为一个实施例，切片指示信息包括以下至少之一：网络设备支持的切片标识，网络设备支持的切片类别，网络设备支持的切片标识与切片类别之间的映射关系，网络设备支持的切片标识的优先级，网络设备支持的切片类别的优先级，网络设备允许切片信息上报的指示，网络设备支持的公共陆地移动网PLMN标识，网络设备支持的切片标识与PLMN标识之间的映射关系，网络设备支持的切片类别与PLMN标识之间的映射关系，网络设备支持的切片所限定的终端数目阈值，PLMN支持的切片所限定的终端数目阈值，会话支持的切片所限定的终端数目阈值，网络设备支持的切片所限定的会话数目阈值， PLMN支持的切片所限定的会话数目阈值。
作为一个实施例，第一接收模块，用于通过以下方式至少之一，接收网络设备发送的切片指示信息：通过接收网络设备广播的方式，接收切片指示信息；通过接收网络设备发送预定信令的方式，接收切片指示信息。
作为一个实施例，第一确定模块，用于根据切片指示信息确定切片信息包括以下至少之一：根据切片指示信息中网络设备支持的切片标识与切片类别之间的映射关系，确定终端的切片所属的类别；确定终端的切片不属于切片指示信息中所指示的切片类别的情况下，将终端的切片归属于默认类别或者预定类别；确定终端的切片不属于切片指示信息中所指示的切片的情况下，将终端的切片归属于默认类别或者预定类别；确定终端切片不属于切片指示信息中所指示的切片的情况下，将终端的切片归属于默认切片或者非切片；终端根据切片指示信息中网络设备的所有切片标识与切片类别之间的映射关系，确定终端的切片所属的类别。
作为一个实施例，终端的切片标识或者网络设备支持的切片标识包括以下至少之一：网络切片选择辅助信息，单网络切片选择辅助信息，网络切片的标识。
作为一个实施例，终端的切片包括以下至少之一：请求的切片，允许的切片，配置的切片和默认的切片。
作为一个实施例，该终端还包括以下至少之一：第二接收模块，用于接收网络设备发送的控制结果，其中，控制结果包括：依据切片信息确定的RACH过程的结果，或对终端触发的RACH过程的响应；第三接收模块，用于接收网络设备发送的选择结果，其中，选择结果包括以下至少之一：依据切片信息选择的用于为终端提供服务的接入和移动性管理实体AMF，依据切片信息选择的用于为终端提供服务的会话管理功能实体SMF，依据切片信息选择的用于为终端提供服务的用户面功能实体UPF，是否选择到需求的核心网实体的指示。
作为一个实施例，RACH过程的结果包括：执行RACH过程成功和执行RACH过程失败。
应理解，根据本申请实施例的装置中的各个单元的上述和其它操作和/或功能分别为了实现图1至图6中的各个方法中终端的相应流程，为了简洁，在此不再赘述。
图8是本申请实施例提供的网络设备的示意性框图，如图8所示，该网络设备800，包括：第四接收模块802，下面对该第四接收模块802进行说明。
第四接收模块802，用于接收终端发送的终端的切片信息。
作为一个实施例，第四接收模块，用于通过无线资源控制RRC消息或随机接入RACH过程中的上行消息，携带切片信息，接收终端发送的切片信息。
作为一个实施例，上行消息包括以下至少之一：四步RACH过程中的消息消息1，四步RACH过程中的3，两步RACH过程中的消息A。
作为一个实施例，通过RRC消息或上行消息中的原因值携带切片信息，其中，RRC消息中的原因值用于表征标准触发RRC消息的原因，上行消息中的原因值用于表征触发RACH过程的原因。
作为一个实施例，RRC消息中的原因值的内容包括切片信息，或，上行消息中的原因值的内容包括切片信息。
作为一个实施例，终端的切片信息包括以下至少之一：终端的切片标识，终端的切片所属的类别，终端的切片的优先级，终端的切片所属的类别的优先级，终端的位置信息，优先选择的公共陆地移动网PLMN标识。
作为一个实施例，该网络设备还包括：第二发送模块，用于在接收终端发送的终端的切片信息之前， 向终端发送切片指示信息。
作为一个实施例，切片指示信息包括以下至少之一：网络设备支持的切片标识，网络设备支持的切片类别，网络设备支持的切片标识与切片类别之间的映射关系，网络设备支持的切片标识的优先级，网络设备支持的切片类别的优先级，网络设备允许切片信息上报的指示，网络设备支持的公共陆地移动网PLMN标识，网络设备支持的切片标识与PLMN标识之间的映射关系，网络设备支持的切片类别与PLMN标识之间的映射关系，网络设备支持的切片所限定的终端数目阈值，PLMN支持的切片所限定的终端数目阈值，会话支持的切片所限定的终端数目阈值，网络设备支持的切片所限定的会话数目阈值，PLMN支持的切片所限定的会话数目阈值。
作为一个实施例，第二发送模块，用于通过以下方式至少之一，向终端发送切片指示信息：通过广播的方式，向终端发送切片指示信息；通过向终端发送预定信令的方式，向终端发送切片指示信息。
作为一个实施例，终端的切片标识或网络设备支持的切片标识包括以下至少之一：网络切片选择辅助信息，单网络切片选择辅助信息，网络切片的标识。
作为一个实施例，网络设备还包括：判断模块，用于根据切片信息判断是否能够为终端提供终端需求的切片，得到判断结果。
作为一个实施例，网络设备还包括：第三发送模块，用于向终端发送判断结果。
作为一个实施例，第三发送模块，用于在判断模块的判断结果为能够为终端提供终端的切片的情况下，向终端发送包含能够为终端提供终端的切片的响应消息。
作为一个实施例，判断模块，还用于根据切片信息确定终端满足切片条件的情况下，网络设备确定能够为终端提供终端需求的切片。
作为一个实施例，切片条件包括以下至少之一：网络设备支持的切片与终端需求的切片匹配，网络设备支持的切片类别与终端需求的切片所属的类别匹配，终端的位置在网络设备提供切片服务的范围内，网络设备支持的切片的优先级满足终端需求的切片的优先级，网络设备支持的预定优先级的切片与终端需求的切片匹配，网络设备支持的切片与终端需求的预定优先级的切片匹配，网络设备支持的预定优先级的切片与终端需求的预定优先级切片匹配，网络设备支持的预定优先级的切片所属的类别与终端需求的切片所属的类别匹配，网络设备支持的切片所属的类别与终端需求的预定优先级的切片所属的类别匹配，网络设备支持的预定优先级的切片所属的类别与终端需求的预定优先级切片所属的类别匹配，网络设备支持的切片类别满足终端需求的切片所属的类别，低于网络设备支持的切片所限定的终端数目阈值，低于PLMN支持的切片所限定的终端数目阈值，低于会话支持的切片所限定的终端数目阈值，低于网络设备支持的切片所限定的会话数目阈值，低于PLMN支持的切片所限定的会话数目阈值；终端需求的切片与网络设备支持的预定切片匹配，终端需求的预定切片与网络设备支持的切片匹配。
作为一个实施例，判断模块，还用于根据切片信息判断是否能够为终端提供终端需求的切片，得到判断结果，包括以下至少之一：依据是否能够为终端提供的终端需求的切片，对终端执行RACH过程控制，得到控制结果，其中，控制结果包括：依据切片信息确定的RACH过程的结果，或对终端触发的RACH过程的响应；依据是否能够为终端提供的终端需求的切片，响应终端触发的RRC请求消息；依据是否能够为终端提供的终端需求的切片，选择为终端提供服务的以下至少之一：接入和移动性管理实体AMF，会话管理功能实体SMF，用户面功能实体UPF。
作为一个实施例，RACH过程的结果包括：执行RACH过程成功和执行RACH过程失败。
作为一个实施例，终端的切片包括以下至少之一：请求的切片，允许的切片，配置的切片和默认的切片。
应理解，根据本申请实施例的装置中的各个单元的上述和其它操作和/或功能分别为了实现图1至图6中的各个方法中网络设备的相应流程，为了简洁，在此不再赘述。
图9是本申请实施例提供的一种通信设备的示意性结构图。图9所示的通信设备900包括处理器910，处理器910可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图9所示，通信设备900还可以包括存储器920。其中，处理器910可以从存储器920中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器920可以是独立于处理器910的一个单独的器件，也可以集成在处理器910中。
可选地，如图9所示，通信设备900还可以包括收发器930，处理器910可以控制该收发器930与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器930可以包括发射机和接收机。收发器930还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备900具体可为本申请实施例的终端，并且该通信设备900可以实现本申请实施例的各个方法中由终端实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备900具体可为本申请实施例的网络设备，并且该通信设备900可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
图10是本申请实施例的芯片的示意性结构图。图10所示的芯片1000包括处理器1010，处理器1010可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图10所示，芯片1000还可以包括存储器1020。其中，处理器1010可以从存储器1020中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1020可以是独立于处理器1010的一个单独的器件，也可以集成在处理器1010中。
可选地，该芯片1000还可以包括输入接口1030。其中，处理器1010可以控制该输入接口1030与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片1000还可以包括输出接口1040。其中，处理器1010可以控制该输出接口1040与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的终端，并且该芯片可以实现本申请实施例的各个方法中由终端实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非 易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch Link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的终端，并且该计算机程序使得计算机执行本申请实施例的各个方法中由终端实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的终端，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由终端实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的终端，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由终端实现的相应流程，为了简洁，在此不再赘述。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分， 实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需求选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (70)

  1. 一种信息发送方法，其特征在于，包括：
    终端将所述终端的切片信息发送给网络设备。
  2. 根据权利要求1所述的方法，其特征在于，所述终端将所述终端的切片信息发送给所述网络设备包括：
    所述终端通过无线资源控制RRC消息或随机接入RACH过程中的上行消息，携带所述切片信息，将所述切片信息发送给所述网络设备。
  3. 根据权利要求2所述的方法，其特征在于，所述上行消息包括以下至少之一：
    四步RACH过程中的消息1，四步RACH过程中的消息3，两步RACH过程中的消息A。
  4. 根据权利要求2所述的方法，其特征在于，通过所述RRC消息或所述上行消息中的原因值携带所述切片信息，其中，所述RRC消息中的原因值用于表征标准触发所述RRC消息的原因，所述上行消息中的原因值用于表征触发所述RACH过程的原因。
  5. 根据权利要求4所述的方法，其特征在于，所述RRC消息中的所述原因值的内容包括所述切片信息，或，所述上行消息中的原因值的内容包括所述切片信息。
  6. 根据权利要求1所述的方法，其特征在于，所述终端的切片信息包括以下至少之一：
    终端的切片标识，终端的切片所属的类别，终端的切片的优先级，终端的切片所属的类别的优先级，终端的位置信息，优先选择的公共陆地移动网PLMN标识。
  7. 根据权利要求1所述的方法，其特征在于，在所述终端将所述终端的切片信息发送给所述网络设备之前，还包括：
    所述终端接收所述网络设备发送的切片指示信息；
    所述终端根据所述切片指示信息确定所述切片信息。
  8. 根据权利要求7所述的方法，其特征在于，所述切片指示信息包括以下至少之一：
    网络设备支持的切片标识，网络设备支持的切片类别，网络设备支持的切片标识与切片类别之间的映射关系，网络设备支持的切片标识的优先级，网络设备支持的切片类别的优先级，网络设备允许所述切片信息上报的指示，网络设备支持的公共陆地移动网PLMN标识，网络设备支持的切片标识与PLMN标识之间的映射关系，网络设备支持的切片类别与PLMN标识之间的映射关系，网络设备支持的切片所限定的终端数目阈值，PLMN支持的切片所限定的终端数目阈值，会话支持的切片所限定的终端数目阈值，网络设备支持的切片所限定的会话数目阈值，PLMN支持的切片所限定的会话数目阈值。
  9. 根据权利要求7所述的方法，其特征在于，所述终端通过以下方式至少之一，接收所述网络设备发送的所述切片指示信息：
    所述终端通过接收所述网络设备广播的方式，接收所述切片指示信息；
    所述终端通过接收所述网络设备发送预定信令的方式，接收所述切片指示信息。
  10. 根据权利要求7所述的方法，其特征在于，所述终端根据所述切片指示信息确定所述切片信息包括以下至少之一：
    所述终端根据所述切片指示信息中网络设备支持的切片标识与切片类别之间的映射关系，确定终端的切片所属的类别；
    所述终端确定终端的切片不属于所述切片指示信息中所指示的切片类别的情况下，所述终端将所述终端的切片归属于默认类别或者预定类别；
    所述终端确定终端的切片不属于所述切片指示信息中所指示的切片的情况下，所述终端将所述终端的切片归属于默认类别或者预定类别；
    所述终端确定终端的切片不属于所述切片指示信息中所指示的切片的情况下，所述终端将所述终端的切片归属于默认切片或者非切片；
    所述终端根据所述切片指示信息中网络设备的所有切片标识与切片类别之间的映射关系，确定终端的切片所属的类别。
  11. 根据权利要求6或8所述的方法，其特征在于，终端的切片标识或者网络设备支持的切片标识包括以下至少之一：
    网络切片选择辅助信息，单网络切片选择辅助信息，网络切片的标识。
  12. 根据权利要求1至10中任一项所述的方法，其特征在于，所述终端的切片包括以下至少之一：请求的切片，允许的切片，配置的切片和默认的切片。
  13. 根据权利要求1至10中任一项所述的方法，其特征在于，所述方法还包括以下至少之一：
    所述终端接收所述网络设备发送的控制结果，其中，所述控制结果包括：依据所述切片信息确定的RACH过程的结果，或对所述终端触发的RACH过程的响应；
    所述终端接收所述网络设备发送的选择结果，其中，所述选择结果包括以下至少之一：依据所述切片信息选择的用于为所述终端提供服务的接入和移动性管理实体AMF，依据所述切片信息选择的用于为所述终端提供服务的会话管理功能实体SMF，依据所述切片信息选择的用于为所述终端提供服务的用户面功能实体UPF，是否选择到需求的核心网实体的指示。
  14. 根据权利要求13所述的方法，其特征在于，RACH过程的结果包括：执行RACH过程成功和执行RACH过程失败。
  15. 一种信息接收方法，其特征在于，包括：
    网络设备接收终端发送的所述终端的切片信息。
  16. 根据权利要求15所述的方法，其特征在于，所述网络设备接收所述终端发送的所述切片信息包括：
    所述网络设备通过无线资源控制RRC消息或随机接入RACH过程中的上行消息，携带所述切片信息，接收所述终端发送的所述切片信息。
  17. 根据权利要求16所述的方法，其特征在于，所述上行消息包括以下至少之一：
    四步RACH过程中的消息消息1，四步RACH过程中的3，两步RACH过程中的消息A。
  18. 根据权利要求16所述的方法，其特征在于，通过所述RRC消息或所述上行消息中的原因值携带所述切片信息，其中，所述RRC消息中的原因值用于表征标准触发所述RRC消息的原因，所述上行消息中的原因值用于表征触发所述RACH过程的原因。
  19. 根据权利要求18所述的方法，其特征在于，所述RRC消息中的所述原因值的内容包括所述切片信息，或，所述上行消息中的原因值的内容包括所述切片信息。
  20. 根据权利要求15所述的方法，其特征在于，所述终端的切片信息包括以下至少之一：
    终端的切片标识，终端的切片所属的类别，终端的切片的优先级，终端的切片所属的类别的 优先级，终端的位置信息，优先选择的公共陆地移动网PLMN标识。
  21. 根据权利要求15所述的方法，其特征在于，在所述网络设备接收所述终端发送的所述终端的切片信息之前，还包括：
    所述网络设备向所述终端发送切片指示信息。
  22. 根据权利要求21所述的方法，其特征在于，所述切片指示信息包括以下至少之一：
    网络设备支持的切片标识，网络设备支持的切片类别，网络设备支持的切片标识与切片类别之间的映射关系，网络设备支持的切片标识的优先级，网络设备支持的切片类别的优先级，网络设备允许所述切片信息上报的指示，网络设备支持的公共陆地移动网PLMN标识，网络设备支持的切片标识与PLMN标识之间的映射关系，网络设备支持的切片类别与PLMN标识之间的映射关系，网络设备支持的切片所限定的终端数目阈值，PLMN支持的切片所限定的终端数目阈值，会话支持的切片所限定的终端数目阈值，网络设备支持的切片所限定的会话数目阈值，PLMN支持的切片所限定的会话数目阈值。
  23. 根据权利要求21所述的方法，其特征在于，所述网络设备通过以下方式至少之一，向所述终端发送所述切片指示信息：
    所述网络设备通过广播的方式，向所述终端发送所述切片指示信息；
    所述网络设备通过向所述终端发送预定信令的方式，向所述终端发送所述切片指示信息。
  24. 根据权利要求20或22所述的方法，其特征在于，所述终端的切片标识或所述网络设备支持的切片标识包括以下至少之一：
    网络切片选择辅助信息，单网络切片选择辅助信息，网络切片的标识。
  25. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    所述网络设备根据所述切片信息判断是否能够为所述终端提供所述终端需求的切片，得到判断结果。
  26. 根据权利要求25所述的方法，其特征在于，所述方法还包括：
    所述网络设备向所述终端发送所述判断结果。
  27. 根据权利要求26所述的方法，其特征在于，所述网络设备向所述终端发送所述判断结果包括：
    在所述判断结果为能够为所述终端提供所述终端的切片的情况下，所述网络设备向所述终端发送包含能够为所述终端提供所述终端的切片的响应消息。
  28. 根据权利要求25所述的方法，其特征在于，所述网络设备根据所述切片信息判断是否能够为所述终端提供所述终端需求的切片包括：
    所述网络设备根据所述切片信息确定所述终端满足切片条件的情况下，所述网络设备确定能够为所述终端提供所述终端需求的切片。
  29. 根据权利要求28所述的方法，其特征在于，所述切片条件包括以下至少之一：
    所述网络设备支持的切片与所述终端需求的切片匹配，所述网络设备支持的切片类别与所述终端需求的切片所属的类别匹配，所述终端的位置在所述网络设备提供切片服务的范围内，所述网络设备支持的切片的优先级满足所述终端需求的切片的优先级，所述网络设备支持的预定优先级的切片与所述终端需求的切片匹配，所述网络设备支持的切片与所述终端需求的预定优先级的切片匹配，所述网络设备支持的预定优先级的切片与所述终端需求的预定优先级切片匹配，所述 网络设备支持的预定优先级的切片所属的类别与所述终端需求的切片所属的类别匹配，所述网络设备支持的切片所属的类别与所述终端需求的预定优先级的切片所属的类别匹配，所述网络设备支持的预定优先级的切片所属的类别与所述终端需求的预定优先级切片所属的类别匹配，所述网络设备支持的切片类别满足所述终端需求的切片所属的类别，低于网络设备支持的切片所限定的终端数目阈值，低于PLMN支持的切片所限定的终端数目阈值，低于会话支持的切片所限定的终端数目阈值，低于网络设备支持的切片所限定的会话数目阈值，低于PLMN支持的切片所限定的会话数目阈值；所述终端需求的切片与所述网络设备支持的预定切片匹配，所述终端需求的预定切片与所述网络设备支持的切片匹配。
  30. 根据权利要求25所述的方法，其特征在于，所述网络设备根据所述切片信息判断是否能够为所述终端提供所述终端需求的切片，得到所述判断结果之后，还包括以下至少之一：
    所述网络设备依据是否能够为所述终端提供的所述终端需求的切片，对所述终端执行RACH过程控制，得到控制结果，其中，所述控制结果包括：依据所述切片信息确定的RACH过程的结果，或对所述终端触发的RACH过程的响应；
    所述网络设备依据是否能够为所述终端提供的所述终端需求的切片，对终端发送RAHC过程结果，或对所述终端触发的RACH过程的响应；
    所述网络设备依据是否能够为所述终端提供的所述终端需求的切片，响应所述终端触发的RRC请求消息；
    所述网络设备依据是否能够为所述终端提供的所述终端需求的切片，选择为所述终端提供服务的以下至少之一：接入和移动性管理实体AMF，会话管理功能实体SMF，用户面功能实体UPF。
  31. 根据权利要求30所述的方法，其特征在于，RACH过程的结果包括：执行RACH过程成功和执行RACH过程失败。
  32. 根据权利要求15至23，25至31中任一项所述的方法，其特征在于，所述终端的切片包括以下至少之一：请求的切片，允许的切片，配置的切片和默认的切片。
  33. 一种终端，其特征在于，包括：
    第一发送模块，用于将所述终端的切片信息发送给网络设备。
  34. 根据权利要求33所述的终端，其特征在于，包括：
    所述第一发送模块，用于通过无线资源控制RRC消息或随机接入RACH过程中的上行消息，携带所述切片信息，将所述切片信息发送给所述网络设备。
  35. 根据权利要求34所述的终端，其特征在于，所述上行消息包括以下至少之一：
    四步RACH过程中的消息1，四步RACH过程中的消息3，两步RACH过程中的消息A。
  36. 根据权利要求34所述的终端，其特征在于，通过所述RRC消息或所述上行消息中的原因值携带所述切片信息，其中，所述RRC消息中的原因值用于表征标准触发所述RRC消息的原因，所述上行消息中的原因值用于表征触发所述RACH过程的原因。
  37. 根据权利要求36所述的终端，其特征在于，所述RRC消息中的所述原因值的内容包括所述切片信息，或，所述上行消息中的原因值的内容包括所述切片信息。
  38. 根据权利要求33所述的终端，其特征在于，所述终端的切片信息包括以下至少之一：
    终端的切片标识，终端的切片所属的类别，终端的切片的优先级，终端的切片所属的类别的优先级，终端的位置信息，优先选择的公共陆地移动网PLMN标识。
  39. 根据权利要求33所述的终端，其特征在于，还包括：
    第一接收模块，用于在将所述终端需求的切片的切片信息发送给所述网络设备之前，接收所述网络设备发送的切片指示信息；
    第一确定模块，用于根据所述切片指示信息确定所述切片信息。
  40. 根据权利要求39所述的终端，其特征在于，所述切片指示信息包括以下至少之一：
    网络设备支持的切片标识，网络设备支持的切片类别，网络设备支持的切片标识与切片类别之间的映射关系，网络设备支持的切片标识的优先级，网络设备支持的切片类别的优先级，网络设备允许所述切片信息上报的指示，网络设备支持的公共陆地移动网PLMN标识，网络设备支持的切片标识与PLMN标识之间的映射关系，网络设备支持的切片类别与PLMN标识之间的映射关系，网络设备支持的切片所限定的终端数目阈值，PLMN支持的切片所限定的终端数目阈值，会话支持的切片所限定的终端数目阈值，网络设备支持的切片所限定的会话数目阈值，PLMN支持的切片所限定的会话数目阈值。
  41. 根据权利要求39所述的终端，其特征在于，所述第一接收模块，用于通过以下方式至少之一，接收所述网络设备发送的所述切片指示信息：
    通过接收所述网络设备广播的方式，接收所述切片指示信息；
    通过接收所述网络设备发送预定信令的方式，接收所述切片指示信息。
  42. 根据权利要求39所述的终端，其特征在于，所述第一确定模块，用于根据所述切片指示信息确定所述切片信息包括以下至少之一：
    根据所述切片指示信息中网络设备支持的切片标识与切片类别之间的映射关系，确定终端的切片所属的类别；
    确定所述终端的切片不属于所述切片指示信息中所指示的切片类别的情况下，将所述终端的切片归属于默认类别或者预定类别；
    确定终端的切片不属于所述切片指示信息中所指示的切片的情况下，将所述终端的切片归属于默认类别或者预定类别；
    确定终端的切片不属于所述切片指示信息中所指示的切片的情况下，将所述终端的切片归属于默认切片或者非切片；
    所述终端根据所述切片指示信息中网络设备的所有切片标识与切片类别之间的映射关系，确定终端的切片所属的类别。
  43. 根据权利要求38或40所述的终端，其特征在于，终端的切片标识或者网络设备支持的切片标识包括以下至少之一：
    网络切片选择辅助信息，单网络切片选择辅助信息，网络切片的标识。
  44. 根据权利要求33至42中任一项所述的终端，其特征在于，所述终端的切片包括以下至少之一：请求的切片，允许的切片，配置的切片和默认的切片。
  45. 根据权利要求33至42中任一项所述的终端，其特征在于，还包括以下至少之一：
    第二接收模块，用于接收所述网络设备发送的控制结果，其中，所述控制结果包括：依据所述切片信息确定的RACH过程的结果，或对所述终端触发的RACH过程的响应；
    第三接收模块，用于接收所述网络设备发送的选择结果，其中，所述选择结果包括以下至少 之一：依据所述切片信息选择的用于为所述终端提供服务的接入和移动性管理实体AMF，依据所述切片信息选择的用于为所述终端提供服务的会话管理功能实体SMF，依据所述切片信息选择的用于为所述终端提供服务的用户面功能实体UPF，是否选择到需求的核心网实体的指示。
  46. 根据权利要求45所述的终端，其特征在于，RACH过程的结果包括：执行RACH过程成功和执行RACH过程失败。
  47. 一种网络设备，其特征在于，包括：
    第四接收模块，用于接收终端发送的所述终端的切片信息。
  48. 根据权利要求47所述的网络设备，其特征在于，
    所述第四接收模块，用于通过无线资源控制RRC消息或随机接入RACH过程中的上行消息，携带所述切片信息，接收所述终端发送的所述切片信息。
  49. 根据权利要求48所述的网络设备，其特征在于，所述上行消息包括以下至少之一：
    四步RACH过程中的消息消息1，四步RACH过程中的3，两步RACH过程中的消息A。
  50. 根据权利要求48所述的网络设备，其特征在于，通过所述RRC消息或所述上行消息中的原因值携带所述切片信息，其中，所述RRC消息中的原因值用于表征标准触发所述RRC消息的原因，所述上行消息中的原因值用于表征触发所述RACH过程的原因。
  51. 根据权利要求50所述的网络设备，其特征在于，所述RRC消息中的所述原因值的内容包括所述切片信息，或，所述上行消息中的原因值的内容包括所述切片信息。
  52. 根据权利要求47所述的网络设备，其特征在于，所述终端的切片信息包括以下至少之一：
    终端的切片标识，终端的切片所属的类别，终端的切片的优先级，终端的切片所属的类别的优先级，终端的位置信息，优先选择的公共陆地移动网PLMN标识。
  53. 根据权利要求47所述的网络设备，其特征在于，还包括：
    第二发送模块，用于在接收所述终端发送的所述终端的切片信息之前，向所述终端发送切片指示信息。
  54. 根据权利要求53所述的网络设备，其特征在于，所述切片指示信息包括以下至少之一：
    网络设备支持的切片标识，网络设备支持的切片类别，网络设备支持的切片标识与切片类别之间的映射关系，网络设备支持的切片标识的优先级，网络设备支持的切片类别的优先级，网络设备允许所述切片信息上报的指示，网络设备支持的公共陆地移动网PLMN标识，网络设备支持的切片标识与PLMN标识之间的映射关系，网络设备支持的切片类别与PLMN标识之间的映射关系，网络设备支持的切片所限定的终端数目阈值，PLMN支持的切片所限定的终端数目阈值，会话支持的切片所限定的终端数目阈值，网络设备支持的切片所限定的会话数目阈值，PLMN支持的切片所限定的会话数目阈值。
  55. 根据权利要求53所述的网络设备，其特征在于，所述第二发送模块，用于通过以下方式至少之一，向所述终端发送所述切片指示信息：
    通过广播的方式，向所述终端发送所述切片指示信息；
    通过向所述终端发送预定信令的方式，向所述终端发送所述切片指示信息。
  56. 根据权利要求52或54所述的网络设备，其特征在于，所述终端的切片标识或所述网络设备支持的切片标识包括以下至少之一：
    网络切片选择辅助信息，单网络切片选择辅助信息，网络切片的标识。
  57. 根据权利要求47所述的网络设备，其特征在于，所述网络设备还包括：
    判断模块，用于根据所述切片信息判断是否能够为所述终端提供所述终端需求的切片，得到判断结果。
  58. 根据权利要求57所述的网络设备，其特征在于，所述网络设备还包括：
    第三发送模块，用于向所述终端发送所述判断结果。
  59. 根据权利要求58所述的网络设备，其特征在于，
    所述第三发送模块，用于在所述判断模块的判断结果为能够为所述终端提供所述终端的切片的情况下，向所述终端发送包含能够为所述终端提供所述终端的切片的响应消息。
  60. 根据权利要求57所述的网络设备，其特征在于，所述判断模块，还用于根据所述切片信息确定所述终端满足切片条件的情况下，所述网络设备确定能够为所述终端提供所述终端需求的切片。
  61. 根据权利要求60所述的网络设备，其特征在于，所述切片条件包括以下至少之一：
    所述网络设备支持的切片与所述终端需求的切片匹配，所述网络设备支持的切片类别与所述终端需求的切片所属的类别匹配，所述终端的位置在所述网络设备提供切片服务的范围内，所述网络设备支持的切片的优先级满足所述终端需求的切片的优先级，所述网络设备支持的预定优先级的切片与所述终端需求的切片匹配，所述网络设备支持的切片与所述终端需求的预定优先级的切片匹配，所述网络设备支持的预定优先级的切片与所述终端需求的预定优先级切片匹配，所述网络设备支持的预定优先级的切片所属的类别与所述终端需求的切片所属的类别匹配，所述网络设备支持的切片所属的类别与所述终端需求的预定优先级的切片所属的类别匹配，所述网络设备支持的预定优先级的切片所属的类别与所述终端需求的预定优先级切片所属的类别匹配，所述网络设备支持的切片类别满足所述终端需求的切片所属的类别，低于网络设备支持的切片所限定的终端数目阈值，低于PLMN支持的切片所限定的终端数目阈值，低于会话支持的切片所限定的终端数目阈值，低于网络设备支持的切片所限定的会话数目阈值，低于PLMN支持的切片所限定的会话数目阈值；所述终端需求的切片与所述网络设备支持的预定切片匹配，所述终端需求的预定切片与所述网络设备支持的切片匹配。
  62. 根据权利要求57所述的网络设备，其特征在于，所述判断模块，还用于根据所述切片信息判断是否能够为所述终端提供所述终端需求的切片，得到所述判断结果，包括以下至少之一：
    依据是否能够为所述终端提供的所述终端需求的切片，对所述终端执行RACH过程控制，得到控制结果，其中，所述控制结果包括：依据所述切片信息确定的RACH过程的结果，或对所述终端触发的RACH过程的响应；
    依据是否能够为所述终端提供的所述终端需求的切片，对终端发送RAHC过程结果，或对所述终端触发的RACH过程的响应；
    依据是否能够为所述终端提供的所述终端需求的切片，响应所述终端触发的RRC请求消息；
    依据是否能够为所述终端提供的所述终端需求的切片，选择为所述终端提供服务的以下至少之一：接入和移动性管理实体AMF，会话管理功能实体SMF，用户面功能实体UPF。
  63. 根据权利要求62所述的网络设备，其特征在于，RACH过程的结果包括：执行RACH过程成功和执行RACH过程失败。
  64. 根据权利要求47至55，57至63中任一项所述的网络设备，其特征在于，所述终端的切片包括以 下至少之一：请求的切片，允许的切片，配置的切片和默认的切片。
  65. 一种终端，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至14中任一项所述的信息发送方法。
  66. 一种网络设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求15至32中任一项所述的信息接收方法。
  67. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至14中任一项所述的信息发送方法，或者执行如权利要求15至32中任一项所述的信息接收方法。
  68. 一种存储介质，其特征在于，所述存储介质存储有至少一个计算机执行指令，其中，在所述至少一个计算机执行指令运行时控制处理器执行如权利要求1至14中任一项所述的信息发送方法，或者执行如权利要求15至32中任一项所述的信息接收方法。
  69. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至14中任一项所述的信息发送方法，或者执行如权利要求15至32中任一项所述的信息接收方法。
  70. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1至14中任一项所述的信息发送方法，或者执行如权利要求15至32中任一项所述的信息接收方法。
PCT/CN2020/089070 2020-05-07 2020-05-07 信息发送、接收方法、终端及网络设备 WO2021223191A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP20934788.9A EP4135412A4 (en) 2020-05-07 2020-05-07 INFORMATION TRANSMITTING METHOD, INFORMATION RECEIVING METHOD, TERMINAL AND NETWORK DEVICE
PCT/CN2020/089070 WO2021223191A1 (zh) 2020-05-07 2020-05-07 信息发送、接收方法、终端及网络设备
CN202211560108.7A CN115776699A (zh) 2020-05-07 2020-05-07 信息发送、接收方法、终端及网络设备
CN202080094827.7A CN115004788A (zh) 2020-05-07 2020-05-07 信息发送、接收方法、终端及网络设备
US17/980,127 US20230058891A1 (en) 2020-05-07 2022-11-03 Information sending method, information receiving method, terminal and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/089070 WO2021223191A1 (zh) 2020-05-07 2020-05-07 信息发送、接收方法、终端及网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/980,127 Continuation US20230058891A1 (en) 2020-05-07 2022-11-03 Information sending method, information receiving method, terminal and network device

Publications (1)

Publication Number Publication Date
WO2021223191A1 true WO2021223191A1 (zh) 2021-11-11

Family

ID=78467782

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/089070 WO2021223191A1 (zh) 2020-05-07 2020-05-07 信息发送、接收方法、终端及网络设备

Country Status (4)

Country Link
US (1) US20230058891A1 (zh)
EP (1) EP4135412A4 (zh)
CN (2) CN115776699A (zh)
WO (1) WO2021223191A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11805463B2 (en) * 2021-07-23 2023-10-31 T-Mobile Innovations Llc User equipment (UE) handover in wireless communication networks

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572517A (zh) * 2015-10-09 2017-04-19 中国移动通信集团公司 网络切片的处理方法、接入网络的选择方法及装置
CN106572516A (zh) * 2016-09-28 2017-04-19 华为技术有限公司 一种网络切片选择方法、终端设备及网络设备
CN109792657A (zh) * 2017-10-26 2019-05-21 Oppo广东移动通信有限公司 无线通信方法和设备
WO2019140629A1 (zh) * 2018-01-19 2019-07-25 Oppo广东移动通信有限公司 一种接入控制的方法、设备及计算机存储介质
EP3537760A1 (en) * 2016-11-03 2019-09-11 KT Corporation Method for processing data on basis of network slice, and apparatus therefor
CN110741684A (zh) * 2019-09-05 2020-01-31 北京小米移动软件有限公司 信息发送方法及装置、网络选择方法及装置和基站

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107734708B (zh) * 2016-08-12 2023-07-28 华为技术有限公司 无线网络的接入控制方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572517A (zh) * 2015-10-09 2017-04-19 中国移动通信集团公司 网络切片的处理方法、接入网络的选择方法及装置
CN106572516A (zh) * 2016-09-28 2017-04-19 华为技术有限公司 一种网络切片选择方法、终端设备及网络设备
EP3537760A1 (en) * 2016-11-03 2019-09-11 KT Corporation Method for processing data on basis of network slice, and apparatus therefor
CN109792657A (zh) * 2017-10-26 2019-05-21 Oppo广东移动通信有限公司 无线通信方法和设备
WO2019140629A1 (zh) * 2018-01-19 2019-07-25 Oppo广东移动通信有限公司 一种接入控制的方法、设备及计算机存储介质
CN110741684A (zh) * 2019-09-05 2020-01-31 北京小米移动软件有限公司 信息发送方法及装置、网络选择方法及装置和基站

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN115004788A (zh) 2022-09-02
EP4135412A1 (en) 2023-02-15
CN115776699A (zh) 2023-03-10
US20230058891A1 (en) 2023-02-23
EP4135412A4 (en) 2023-05-10

Similar Documents

Publication Publication Date Title
CN110856276A (zh) 非连接态ue的数据传输、接收方法及装置、终端、基站
US20220007426A1 (en) Random access method and device
CN111565473A (zh) 一种随机接入方法和装置
US11825519B2 (en) Random access method, terminal device, network device, and storage medium
WO2020186466A1 (zh) 无线通信的方法、终端设备和网络设备
EP3879883A1 (en) Random access process selection method and apparatus, chip, and computer program
US20210153247A1 (en) Random access method and terminal device
CN111757543B (zh) 一种数据传输方法及装置、终端
WO2020191599A1 (zh) 通信方法、终端设备和网络设备
US20220039152A1 (en) Method for transmitting information in random access process, terminal device and network device
US20230058891A1 (en) Information sending method, information receiving method, terminal and network device
US20230129426A1 (en) Wireless communication method and terminal device
CN112567873B (zh) 一种信息传输的方法、设备及计算机存储介质
WO2020223878A1 (zh) 随机接入的方法、终端设备和网络设备
WO2020206643A1 (zh) 一种随机接入方法、设备及存储介质
US20230209614A1 (en) Random access method and device, terminal, and storage medium
US20220353908A1 (en) Control method for slice network, terminal, and network device
US20220167434A1 (en) Random access problem reporting method, terminal device and storage medium
US20210136813A1 (en) Random Access Method and Apparatus
WO2020206597A1 (zh) 功率分配的方法和终端设备
WO2020186468A1 (zh) 随机接入的方法和设备
WO2020198988A1 (zh) 一种随机接入方法、电子设备及存储介质
CN114788382A (zh) 用于传输数据的方法及设备
CN115299165A (zh) 一种数据传输方法、终端设备、网络设备

Legal Events

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

Ref document number: 20934788

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020934788

Country of ref document: EP

Effective date: 20221111

NENP Non-entry into the national phase

Ref country code: DE