Nothing Special   »   [go: up one dir, main page]

WO2022036568A1 - 无线通信方法、终端设备和网络设备 - Google Patents

无线通信方法、终端设备和网络设备 Download PDF

Info

Publication number
WO2022036568A1
WO2022036568A1 PCT/CN2020/109883 CN2020109883W WO2022036568A1 WO 2022036568 A1 WO2022036568 A1 WO 2022036568A1 CN 2020109883 W CN2020109883 W CN 2020109883W WO 2022036568 A1 WO2022036568 A1 WO 2022036568A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
slice
demand
information
cell
Prior art date
Application number
PCT/CN2020/109883
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 JP2023511870A priority Critical patent/JP2023545345A/ja
Priority to CN202310494085.2A priority patent/CN116437403A/zh
Priority to EP20949780.9A priority patent/EP4203551A4/en
Priority to KR1020237006634A priority patent/KR20230052904A/ko
Priority to CN202080102263.7A priority patent/CN115918152A/zh
Priority to PCT/CN2020/109883 priority patent/WO2022036568A1/zh
Publication of WO2022036568A1 publication Critical patent/WO2022036568A1/zh
Priority to US18/089,490 priority patent/US20230209416A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/13Cell handover without a predetermined boundary, e.g. virtual cells
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/18Selecting a network or a communication service
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0001Arrangements for dividing the transmission path
    • H04L5/0003Two-dimensional division
    • H04L5/0005Time-frequency
    • H04L5/0007Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/06Reselecting a communication resource in the serving access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/14Reselecting a network or an air interface
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters
    • H04W36/26Reselection being triggered by specific parameters by agreed or negotiated communication parameters
    • H04W36/28Reselection being triggered by specific parameters by agreed or negotiated communication parameters involving a plurality of connections, e.g. multi-call or multi-bearer connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/34Reselection control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/20Selecting an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W68/00User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005Transmission of information for alerting of incoming communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W68/00User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02Arrangements for increasing efficiency of notification or paging channel
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/15Setup of multiple wireless link connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0069Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/08Reselecting an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/50Connection management for emergency connections

Definitions

  • the embodiments of the present application relate to the field of communication, and more particularly, to a wireless communication method, a terminal device, and a network device.
  • the vertical industry's demand for wireless communication is obvious to all.
  • the Radio Access Network needs to understand how to support the access network.
  • vertical business enhancements One way is to provide lower latency, more targeted, more flexible and more scalable services for multiple services with different requirements through slicing or network slicing.
  • the terminal device is currently configured with slices
  • the terminal device obtains the information that requires slices, how to process the terminal device is a technical problem to be solved urgently in the present application.
  • Embodiments of the present application provide a wireless communication method, terminal device, and network device.
  • a processing method of the terminal device when the terminal device obtains the information of the required slicing under the condition that the terminal device is currently configured with slices is given.
  • a wireless communication method includes: a terminal device obtains indication information, the indication information is used to indicate the information of the required slice; the terminal device performs cell reselection according to the information of the required slice or determines whether the The serving cell triggers the connection establishment procedure.
  • a wireless communication method includes: a terminal device acquires indication information, where the indication information is used to indicate information about a required slice; and the terminal device sends the indication information to a network device.
  • a wireless communication method comprising: a network device receiving indication information, where the indication information is used to indicate information of required slices; the network device determines and/or sends at least one of the following according to the information of required slices: a terminal The first indication of whether the serving cell of the device supports the required slice; the DC configuration corresponding to the required slice; the CA configuration corresponding to the required slice; the second indication that the terminal device needs to perform cell handover; the third indication that the terminal device needs to perform cell redirection.
  • a terminal device for executing the method in the above-mentioned first aspect or each of its implementations.
  • the terminal device includes a functional module for executing the method in the above-mentioned first aspect or each implementation manner thereof.
  • a terminal device for executing the method in the second aspect or each of its implementations.
  • the terminal device includes a functional module for executing the method in the second aspect or each implementation manner thereof.
  • a network device for executing the method in the third aspect or each of its implementations.
  • the network device includes functional modules for executing the methods in the third aspect or each of its implementations.
  • a terminal device including a processor and a memory.
  • the memory is used for storing a computer program
  • the processor is used for calling and running the computer program stored in the memory to execute the method in the above-mentioned first aspect or each implementation manner thereof.
  • a terminal 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 each of its implementations.
  • 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 third aspect or each of its implementations.
  • an apparatus for implementing the method in any one of the above-mentioned first aspect to the third aspect or each implementation manner thereof.
  • the apparatus includes: a processor for calling and running a computer program from a memory, so that a device installed with the apparatus executes any one of the above-mentioned first to third aspects or each of its implementations method.
  • a computer-readable storage medium for storing a computer program, and the computer program causes a computer to execute the method in any one of the above-mentioned first aspect to the third aspect or each implementation manner thereof.
  • a computer program product comprising computer program instructions, the computer program instructions cause a computer to execute the method in any one of the above-mentioned first to third aspects or the implementations thereof.
  • a thirteenth aspect provides a computer program that, when run on a computer, causes the computer to perform the method of any one of the above-mentioned first to third aspects or the respective implementations thereof.
  • a processing method of the terminal device when the terminal device obtains the information of the required slicing under the situation that the terminal device is currently configured with slices is given.
  • the terminal device can perform cell reselection or determine whether to trigger the connection establishment process in the serving cell of the terminal device according to the information of the required slice, so as to ensure service transmission or cell camping corresponding to the required slice.
  • the network device may determine and/or send at least one of the following according to the information of the demand slice indicated by the indication information: the first indication of whether the serving cell of the terminal device supports the demand slice; the DC configuration corresponding to the demand slice; The activation or deactivation instruction of the DC; the CA configuration corresponding to the required slice; the activation or deactivation instruction of the CA corresponding to the required slice; the second instruction that the terminal equipment needs to perform cell handover; the third instruction that the terminal equipment needs to perform cell redirection. Therefore, the service transmission corresponding to the demand slice can be guaranteed.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • FIG. 2 is a flowchart of a wireless communication method provided by an embodiment of the present application.
  • FIG. 3 is an interaction flowchart of a wireless communication method provided by another embodiment of the present application.
  • FIG. 4 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application
  • FIG. 5 shows a schematic block diagram of a terminal device 500 according to an embodiment of the present application
  • FIG. 6 shows a schematic block diagram of a network device 600 according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a communication device 700 provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a device according to an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • New Radio Interface New Radio, NR
  • evolution system of NR system LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR) on unlicensed spectrum -U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), next-generation communication systems or other communication systems, etc.
  • UMTS Universal Mobile Telecommunication System
  • WLAN Wireless Local Area Networks
  • WiFi Wireless Fidelity
  • the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.
  • Carrier Aggregation, CA Carrier Aggregation, CA
  • DC Dual Connectivity
  • SA standalone
  • This embodiment of the present application does not limit the applied spectrum.
  • the embodiments of the present application may be applied to licensed spectrum, and may also be applied to unlicensed spectrum.
  • 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 referred to as a communication terminal, a terminal).
  • the network device 110 may provide communication coverage for a particular geographic area, and may communicate with terminal devices located within the coverage area.
  • FIG. 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. This application The embodiment does not limit this.
  • the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • a device having a communication function in the network/system may be referred to as a communication device.
  • the communication device may include a network device 110 and a terminal device 120 with a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here.
  • the communication device may also include other devices in the communication system 100, such as other network entities such as a network controller, a mobility management entity, etc., which are not limited in this embodiment of the present application.
  • terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • UE User Equipment
  • access terminal subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • the terminal device can be a station (STAION, ST) in the WLAN, can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, and next-generation communication systems, such as terminal devices in NR networks or Terminal equipment in the future evolved Public Land Mobile Network (Public Land Mobile Network, PLMN) network, etc.
  • STAION, ST in the WLAN
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • a network device can be a device used to communicate with a mobile device.
  • the network device can be an access point (Access Point, AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, or a WCDMA
  • the base station (NodeB, NB) can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or an access point, or a vehicle-mounted device, a wearable device, and a network device or base station in an NR network ( gNB) or network equipment in the future evolved PLMN network, etc.
  • gNB NR network
  • a network device provides services for a cell
  • a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell
  • the cell may be a network device (for example, a frequency domain resource).
  • the cell corresponding to the base station), the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell), where the small cell can include: Metro cell, Micro cell, Pico cell cell), Femto cell, etc.
  • These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-speed data transmission services.
  • a cell reselection strategy based on frequency priority is defined.
  • Cell reselection refers to a process in which a terminal device selects a best cell to provide a service signal by monitoring the signal quality of neighboring cells and the current serving cell in a disconnected state.
  • the terminal equipment will access the cell to camp.
  • the terminal device calculates Srxlev (that is, the S criterion) according to the reference signal received power (Reference Signal Received Power, RSRP) measurement result, and compares it with Sintrasearch (that is, the same-frequency measurement start threshold) It is compared with Snonintrasearch (that is, the inter-frequency/inter-system measurement start threshold) as the judgment condition for whether to start the adjacent cell measurement.
  • Srxlev that is, the S criterion
  • RSRP Reference Signal Received Power
  • the R criterion is used for cell reselection, that is, the cell is sorted according to the signal quality of the cells, and the cell with the best signal quality is selected as the candidate reselection target cell.
  • the cell with high frequency priority as long as the signal quality of the cell meets a certain threshold, the cell with high frequency priority will be reselected.
  • the cell with low frequency priority only when the signal quality of the serving cell is lower than a certain threshold Will re-select the past.
  • Paging Initiated by a network device to a terminal device in an idle or inactive or connected state. Paging is divided into a core network (Core Network, CN) initial paging message and a RAN initial paging message.
  • Core Network Core Network
  • CN initial paging initiate paging within the scope of the registered tracking area (Tracking Area, TA) list (list). Notify the terminal device to receive the paging message.
  • Track Area TA
  • list Notify the terminal device to receive the paging message.
  • RAN Initial Paging Initiates a paging message within the RAN range. Notify the terminal device to receive the paging message.
  • Network equipment triggers paging: initiates paging within the cell range; notifies the system of message updates and notifies terminal equipment to receive information such as Earthquake and Tsunami Warning System (ETWS).
  • EWS Earthquake and Tsunami Warning System
  • the system message change indication and the Public Warning System (Public Warning System, PWS) notification indication are carried in the Downlink Control Information (Downlink Control Information, DCI).
  • DCI Downlink Control Information
  • the paging message is carried on the Paging Control Channel (Paging Control Channel), the Paging Channel (Paging Channel, PCH), and the Physical Downlink Shared Channel (Physical Downlink Shared Channel, PDSCH); through the Physical Downlink Control Channel (Physical Downlink Control Channel) Channel, PDCCH) to schedule transmission.
  • the paging-Radio Network Temporary Identifier (paging-Radio Network Temporary Identifier, P-RNTI) has a fixed value of FFFE, which is used to scramble the DCI of the paging message.
  • P-RNTI paging-Radio Network Temporary Identifier
  • P-RNTI has a fixed value of FFFE, which is used to scramble the DCI of the paging message.
  • the idle state in this application is also described as RRC idle state (RRC_IDLE), the inactive state is also described as RRC inactive state (RRC_INACTIVE), and the connected state is also described as RRC connected state (RRC_CONNECTED).
  • the paging message contains:
  • the identity of the paged terminal equipment is the Serving-Temporary Mobile Subscriber Identity (S-TMSI) during the initial paging of the CN, and the system information Temporary Mobile Subscriber Identity (System Information Temporary Mobile Subscriber Identity, S-TMSI) during the initial paging of the RAN. Information-Temporary Mobile Subscriber Identity, SI-RNTI). International Mobile Subscriber Identity (IMSI)/Subscription Permanent Identifier (SUPI)/Subscription Concealed Identifier (SUCI) are not supported for paging terminal equipment. Among them, up to 32 terminal devices can be paged at the same time.
  • SI-RNTI Information-Temporary Mobile Subscriber Identity
  • Access type that triggers paging: 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) or non-3GPP.
  • 3rd Generation Partnership Project 3rd Generation Partnership Project
  • non-3GPP the technical indication of the access network used to indicate that the packet data unit (Packet Data Unit, PDU) session (session) belongs to needs to be submitted to the upper layer.
  • PDU Packet Data Unit
  • the terminal device receives the paging message at its own paging occasion in the RRC_IDLE and RRC_INACTIVE states.
  • the terminal device does not need to monitor the PDCCH all the time, but only at the paging occasion, so as to achieve the purpose of saving power on the terminal device side.
  • the calculation of paging timing is based on DRX, and the size of DRX determines the balance between power saving of terminal equipment and access delay. There are three DRX used by terminal equipment to calculate paging occasions:
  • Cell default DRX cycle (Cell default DRX cycle): It is the cell-level DRX broadcast by the cell system.
  • Terminal equipment-specific DRX (UE specific DRX): It is the DRX determined by the terminal equipment, and is sent to the CN side through a Non-Access Stratrum (NAS) message, and is sent to the network equipment by the CN side in paging.
  • NAS Non-Access Stratrum
  • RAN DRX When the network side decides to let the terminal device enter the inactive state, it is configured to the terminal device through the RRC Release (Release) message.
  • the terminal device and the network side adopt the minimum principle to select DRX for calculating the paging occasion.
  • RRC_IDLE UE the smallest DRX among Cell default DRX cycle and UE specific DRX is used.
  • RRC_INACTIVE UE the smallest DRX among Cell default DRX cycle, UE specific DRX and RAN DRX is used.
  • FIG. 2 is a flowchart of a wireless communication method provided by an embodiment of the present application, and the method includes the following steps:
  • Step S210 The terminal device acquires indication information, where the indication information is used to indicate the information of the required slice.
  • Step S220 The terminal device performs cell reselection according to the information of the required slice or determines whether to trigger the connection establishment process in the serving cell of the terminal device.
  • this embodiment is applicable to a scenario where the terminal device is in a disconnected state, but is not limited thereto.
  • the network device may broadcast the information of the slices supported by the network device through a system message.
  • the information of the slice supported by the network device includes, but is not limited to, at least one of the following: the identifier of the slice supported by the network device, the priority of the slice, the frequency point information corresponding to the slice, and the cell information corresponding to the slice.
  • the slice supported by the network device may be a slice supported by a cell covered by the network device, or may not be a slice supported by other cells except the cell covered by the network device.
  • the above-mentioned network device may configure a slice for the terminal device according to the information of the slice supported by the network device, where the configured slice may be any slice supported by the network device.
  • the terminal device may select a cell corresponding to the above-configured slice to camp on.
  • the above-mentioned information of required slices is also described as information of required slices, or information of required slices of the above-mentioned terminal equipment, or information of required slices of the above-mentioned terminal equipment. This application does not limit this.
  • the information of the required slice includes, but is not limited to, at least one of the following: the identifier of the required slice, the priority of the required slice, the frequency point information corresponding to the required slice, and the cell information corresponding to the required slice.
  • the identifier of the required slice may be single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI) or network slice selection assistance information (Network Slice Selection Assistance Information, NSSAI), which is not made in this application. limit.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • NSSAI Network Slice Selection Assistance Information
  • the frequency point information corresponding to the required slice is also described as the frequency point information of the cell corresponding to the required slice.
  • the frequency point information includes but is not limited to the following information: frequency point identification and/or frequency point priority.
  • the cell information corresponding to the required slice includes, but is not limited to, the following information: the identity of the cell corresponding to the required slice, the priority of the cell, the frequency information of the cell, and the bandwidth information of the cell.
  • the terminal device can obtain the indication information in the following manner, but is not limited to this:
  • the indication information is generated by the non-access stratum (Non-Access Stratrum, NAS) of the terminal device and sent to the access stratum (Access Stratrum, AS) of the terminal device.
  • NAS Non-Access Stratrum
  • AS access stratum
  • the indication information is sent by the core network device to the terminal device through a NAS message.
  • the indication information is sent by the network device to the terminal device, for example, the indication information is carried in the paging message.
  • the core network device may send a paging message to the network device when the called data is pushed, and further, the network device may send the paging message to the terminal device.
  • the core network device is an access and mobility management entity (Access and Mobility Management Function, AMF), but is not limited thereto.
  • AMF Access and Mobility Management Function
  • the indication information is sent in a service request (Service request) process, a PDU session establishment request (PDU session establishment request) process, a paging process or a PDU session modification request (PDU session modification request) process.
  • the indication information is sent when the service arrives.
  • the service may be a paging service or other data service, etc., which is not limited in this application.
  • the NAS of the terminal device may send the indication information to the AS under any circumstances, or may send the indication information when certain conditions are met.
  • the core network device may send the indication information to the terminal device under any circumstances, or may send the indication under certain conditions. information.
  • the access network device may send the indication information to the terminal device under any circumstances, or may send the indication information when certain conditions are met.
  • the above condition may be that the priority of the required slice is higher than the priority of the currently configured, serviced or established slice of the terminal device. Or, under the above conditions, the priority of the required slice is not lower than the priority of the currently configured, serviced or established slice of the terminal device.
  • the indication information may be carried in the cause value.
  • the above-mentioned cause value is any one of the following, but not limited thereto: RRC establishment cause (Establishment Cause), RRC reestablishment cause (Reestablishment Cause), and cell reselection cause (Resume Cause).
  • the information of the demand slice may also be pre-configured by the network device to the terminal device, which is not limited in this application.
  • the terminal device may select a cell corresponding to the above-configured slice to camp on. After the terminal device obtains the information of the required slice, if the terminal device is not performing the cell reselection process, it can directly perform the cell reselection. If the terminal device is performing the cell reselection process, the terminal device interrupts the current cell reselection process, and further, the terminal device performs cell reselection according to the information of the required slice.
  • the terminal device For the case where the indication information is sent to the AS by the NAS of the terminal device, and the NAS of the terminal device passes the indication information only to update the information of the required slices, not to trigger service transmission or PDU session establishment, the terminal device The cell reselection can be performed according to the information of the required slice.
  • the terminal device performs cell reselection according to the information of the required slices. , the connection establishment process can be triggered in the reselected cell.
  • the indication information is sent by the core network device to the terminal device through the NAS or sent by the core network device to the terminal device
  • the terminal device after the terminal device performs cell reselection according to the information of the required slice, it can also be reselected.
  • the cell triggers the connection establishment procedure.
  • the connection establishment process may also be triggered in the reselected cell.
  • connection establishment process includes but is not limited to: an RRC connection establishment process and a PDU session establishment process.
  • the terminal device determines that the connection establishment process is triggered in the serving cell of the terminal device. If the terminal device determines, according to the information of the demand slice, that the cell corresponding to the demand slice is not the serving cell, the terminal device determines that it is not in the serving cell of the terminal device to trigger the connection establishment process. If the terminal equipment determines that the cell corresponding to the demand slice is not the serving cell according to the information of the demand slice, the terminal equipment determines that the connection establishment process is triggered in the serving cell of the terminal equipment, but only supports emergency service transmission.
  • the terminal device may directly perform cell reselection according to the information of the required slice or determine whether to trigger the connection establishment process in the serving cell of the terminal device.
  • the terminal device determines that the following conditions are met, and performs cell reselection or determines whether to trigger the connection establishment process in the serving cell of the terminal device.
  • the above conditions include but are not limited to: the serving cell of the terminal device or the frequency of the serving cell cannot support the current service of the terminal device and the service corresponding to the demand slice at the same time, and/or, the priority of the service corresponding to the demand slice is high. Based on the priority of the current service and/or the priority of the required slice is not lower than the priority of the currently configured, serviced or established slice of the terminal device.
  • the processing method of the terminal device when the terminal device in the disconnected state is currently configured with slicing, when the terminal device obtains the information of the required slicing, the processing method of the terminal device is given, that is, the terminal device can slice according to the requirements. information to perform cell reselection or determine whether to trigger the connection establishment procedure in the serving cell of the terminal device. Further, in this application, the terminal device can perform cell reselection or determine whether to trigger the connection establishment process in the serving cell of the terminal device according to the information of the required slice, so as to ensure service transmission or cell camping corresponding to the required slice.
  • FIG. 3 is an interactive flowchart of a wireless communication method provided by another embodiment of the present application, and the method includes the following steps:
  • Step S310 The terminal device acquires indication information, where the indication information is used to indicate the information of the required slice.
  • Step S320 The terminal device sends indication information to the network device.
  • Step S330 The network device determines and/or sends at least one of the following according to the information of the demand slice: the first indication of whether the serving cell of the terminal device supports the demand slice; the dual connectivity (Dual Connectivity, DC) configuration corresponding to the demand slice; the demand slice The activation or deactivation instruction of the corresponding DC; the carrier aggregation (Carrier Aggregation, CA) configuration corresponding to the required slice; the activation or deactivation instruction of the CA corresponding to the required slice; the second instruction that the terminal equipment needs to perform cell handover; the terminal equipment needs A third instruction to perform cell redirection.
  • this embodiment is applicable to a scenario where the terminal device is in a connected state and is triggered by a new uplink (Uplink, UL) service requirement, or, in a scenario where a new UL service arrives, there is a new downlink (downlink, DL) service requirement. Trigger, or, a scenario where a DL new service arrives, but not limited to this.
  • a new PDU session can be established to support demand slicing.
  • the network device can also configure the data radio bearer (Data Radio Bearer, DRB) for the terminal device through the RRC reconfiguration message.
  • DRB data Radio Bearer
  • the network device may broadcast the information of the slices supported by the network device through a system message.
  • the information of the slices supported by the network device the information of the slices configured by the network device for the terminal device, and the information of the required slices, reference may be made to the embodiment corresponding to FIG. 2 , which will not be repeated in this application.
  • the terminal device may select a cell corresponding to a slice configured by the network device to camp on. Further, the terminal equipment can establish a connection in the cell and perform service transmission.
  • the terminal device may acquire the indication information in the following manner, but is not limited to this: the indication information is generated by the NAS of the terminal device and sent to the AS of the terminal device. Or, the indication information is sent by the core network device to the terminal device through a NAS message.
  • the core network device may be an AMF or other core network device, which is not limited in this application.
  • the indication information is sent in a service request (Service request) process, a PDU session establishment request (PDU session establishment request) process, a paging process or a PDU session modification request (PDU session modification request) process.
  • the indication information is sent when the service arrives.
  • the service may be a paging service or other data service, etc., which is not limited in this application.
  • the NAS of the terminal device may send the indication information to the AS under any circumstances, or may send the indication information when certain conditions are met.
  • the core network device may send the indication information to the terminal device under any circumstances, or may send the indication information under certain conditions. Instructions.
  • the above condition may be that the priority of the required slice is higher than the priority of the currently configured, serviced or established slice of the terminal device. Or, under the above conditions, the priority of the required slice is not lower than the priority of the currently configured, serviced or established slice of the terminal device.
  • the indication information may be carried in the cause value.
  • the above-mentioned cause value is any one of the following, but not limited thereto: RRC establishment cause (Establishment Cause), RRC reestablishment cause (Reestablishment Cause), and cell reselection cause (Resume Cause).
  • the terminal device may send the indication information to the network device through a dedicated message.
  • the dedicated message is any one of the following: an RRC message, a media access control control element (Media Access Control Control Element, MAC CE), and uplink control information (Uplink Control Information, UCI).
  • RRC message a media access control control element
  • MAC CE Media Access Control Control Element
  • UCI Uplink Control Information
  • the terminal device may send the above-mentioned indication information to the network device under any circumstances, and may also send the indication information when certain conditions are met.
  • this condition includes but is not limited to: the serving cell of the terminal device or the frequency of the serving cell cannot support the current service of the terminal device and the service corresponding to the demand slice at the same time, and/or the priority of the service corresponding to the demand slice is high. Based on the priority of the current service, and/or the priority of the required slice is not lower than the priority of the currently configured, serviced or established slice of the terminal device.
  • the information of the demand slice may also be pre-configured by the network device to the terminal device, which is not limited in this application.
  • the network device can obtain the above-mentioned indication information from the application server, wherein the application server can directly send the indication information to the network device. , or, the application server sends it to the terminal device, and the application layer of the terminal device sends the indication information to the network device. In a word, this application does not limit how the network device obtains the indication information.
  • the indication information further includes first information.
  • the first information is used to request at least one of the following: perform cell handover; establish CA; establish DC; and perform cell redirection.
  • the above-mentioned indication information may also not include the first information, that is, the terminal device does not need to send the above-mentioned at least one request to the network device.
  • the network device may determine and/or send a first indication of whether the serving cell of the terminal device supports the required slicing according to the information of the serving cell of the terminal device and the information of the required slicing.
  • the network device may determine and/or send the above-mentioned first indication.
  • the terminal equipment performs service transmission of demand slices in the serving cell.
  • the network device may determine whether demand slicing needs to be supported according to the information of the demand slicing. For example, at least one of CA, DC, cell handover, and cell redirection is used to support the above-mentioned demand slicing, so as to realize the service transmission of the demanded slicing.
  • the network device may determine whether to support demand slicing in the following manner, but is not limited to this:
  • the network device determines whether it needs to support the demand slicing according to the priority of the demand slice and the priority of the slice currently configured by the terminal device. or,
  • the network device determines whether the demand slicing needs to be supported according to the priority of the frequency point of the demand slice and the priority of the frequency point of the slice currently configured by the terminal device.
  • the network device determines that the demand slice needs to be supported. If the priority of the demand slice is lower than or equal to the priority of the currently configured slice, the network device determines that the demand slice does not need to be supported. Alternatively, if the priority of the demand slice is equal to or higher than the priority of the currently configured slice, the network device determines that the demand slice needs to be supported. If the priority of the demand slice is lower than the priority of the currently configured slice, the network device determines that the demand slice does not need to be supported.
  • the network device determines that the required slice needs to be supported. If the priority of the frequency point of the required slice is lower than or equal to the priority of the frequency point of the currently configured slice, the network device determines that the required slice does not need to be supported. Alternatively, if the priority of the frequency point of the required slice is equal to or higher than the priority of the frequency point of the currently configured slice, the network device determines that the required slice needs to be supported. If the priority of the frequency point of the required slice is lower than the priority of the frequency point of the currently configured slice, the network device determines that the required slice does not need to be supported.
  • the serving slice and the requirement slice cannot be supported at the same time, determine the slice that needs to support the requirement, or the slice that does not need to support the requirement.
  • the network device may determine the DC configuration corresponding to the demand slice and the activation or deactivation indication of the DC corresponding to the demand slice according to the information of the demand slice and the information of the slice supported by the serving cell. , CA configuration, at least one of activation or deactivation indication of the CA corresponding to the required slice, cell handover, and cell handover.
  • the information of the slice supported by the serving cell is also described as the information of the slice supported by the network device.
  • information about slices supported by the network device reference may be made to the previous embodiment, which will not be repeated in this application.
  • the network device can determine the DC configuration corresponding to the required slice, the activation or deactivation indication of the DC corresponding to the required slice, the CA configuration, and the activation of the CA corresponding to the required slice according to the information of the required slice and the information of the slice supported by the serving cell. Or at least one of deactivation indication, cell handover and cell handover, for example description:
  • Example 1 When the frequency point supported by the serving cell of the terminal equipment is A, and the frequency point supported by the required slice is B, the network equipment can use the DC or CA technology for the serving cell and other cells, so that the frequency point corresponding to the terminal equipment can be For B, in this way, the service transmission that requires slices can be realized.
  • Example 2 When the frequency supported by the serving cell of the terminal device is A, and the frequency supported by the required slice is B, if the network device determines that the frequency supported by another cell is B, it will instruct the terminal device to switch to this frequency. cell, so that the frequency point corresponding to the terminal equipment can be B, so that the service transmission that requires slicing can be realized.
  • the terminal device may send capability indication information to the network device.
  • the capability indication information is used to indicate at least one of the following:
  • the list in item 5 is a list of bandwidth combinations supported by the terminal device.
  • the list in item 6 is a list of frequency point combinations corresponding to slices supported by the terminal device.
  • the list in item 7 is a list of bandwidth combinations corresponding to slices supported by the terminal device.
  • the list in item 8 is a list of carrier combinations corresponding to slices supported by the terminal device.
  • the network device may determine and/or send the following information according to the required slice information, the slice information supported by the serving cell, and the capability indication information of the terminal device: At least one item: the DC configuration corresponding to the required slice; the activation or deactivation instruction of the DC corresponding to the required slice; the CA configuration corresponding to the required slice; the activation or deactivation instruction of the CA corresponding to the required slice; Second indication; the terminal equipment needs to perform a third indication of cell redirection.
  • the terminal equipment does not support CA and DC technology, but supports cell switching technology, if the network equipment determines If the frequency point supported by another cell is B, the terminal equipment is instructed to switch to this cell, so that the frequency point corresponding to the terminal equipment can be B, so that the service transmission that requires slices can be realized.
  • the network device sends the DC configuration and/or CA configuration corresponding to the demand slice to the terminal device, and/or, the activation or deactivation instruction of the DC and/or CA corresponding to the demand slice; then the terminal device is configured according to the DC and/or CA configuration, and/or, activation or deactivation of the DC and/or CA corresponding to the demand slice instructs to perform service transmission of the demand slice.
  • the terminal device performs service transmission requiring slicing on one of the at least one cell.
  • the terminal equipment simultaneously transmits the service of the required slice and the transmission of the current service on one cell of the at least one cell. For example, both the service transmission of the required slice and the transmission of the current service are performed in cell 1.
  • the terminal device respectively performs the transmission of the required slice service and the transmission of the current service on at least two cells of the at least one cell. For example, the service transmission of the required slice is performed in cell 1, and the transmission of the current service is performed in cell 2.
  • the terminal device can perform at least one of the following: activate the cell; perform timing advance (TA) synchronization; and indicate to the network device that the cell needs to be activated.
  • TA timing advance
  • the terminal device performs cell handover and/or performs service transmission of the required slice according to the second indication.
  • the terminal device performs cell redirection and/or service transmission of the demand slice according to the third indication.
  • the network device may determine and/or send at least one of the following in any case: the first indication of whether the serving cell of the terminal device supports the demand slice; the DC configuration corresponding to the demand slice; the CA configuration corresponding to the demand slice; The activation or deactivation instruction of the CA corresponding to the slice; the activation or deactivation instruction of the DC corresponding to the slice is required; the second instruction that the terminal equipment needs to perform cell handover; the third instruction that the terminal equipment needs to perform cell redirection.
  • the network device determines and/or sends at least one of the following: a first indication of whether the serving cell of the terminal device supports the demand slice; the DC configuration corresponding to the demand slice; the CA configuration corresponding to the demand slice; the demand slice The activation or deactivation instruction of the corresponding CA; the activation or deactivation instruction of the DC corresponding to the required slice; the second instruction that the terminal equipment needs to perform cell handover; the third instruction that the terminal equipment needs to perform cell redirection.
  • the above condition may be that the serving cell of the terminal device or the frequency of the serving cell cannot support the current service of the terminal device and the service corresponding to the demand slice at the same time, and/or, the priority of the service corresponding to the demand slice is higher than the current service. and/or the priority of the required slice is not lower than the priority of the currently configured, serviced or established slice of the terminal device. .
  • the network device determines and/or sends at least one of the following: a first indication of whether the serving cell of the terminal device supports the demand slice; the DC configuration corresponding to the demand slice; the CA configuration corresponding to the demand slice; The activation or deactivation instruction of the CA corresponding to the slice is required; the activation or deactivation instruction of the DC corresponding to the slice is required; the second instruction that the terminal equipment needs to perform cell handover; the third instruction that the terminal equipment needs to perform cell redirection. It can be performed independently, that is, performed by decoupling.
  • the network device does not need to first determine whether the serving cell of the terminal device supports the demand slice, and then determine the DC configuration, CA configuration, cell handover or cell redirection corresponding to the demand slice. For another example, the network device does not need to first determine whether to provide the DC and/or CA configuration to the terminal device, and then determine whether to perform cell redirection or cell handover when it determines not to provide the DC and/or CA configuration.
  • the processing method of the terminal device when the terminal device in the connected state is currently configured with slicing, when the terminal device obtains the information that requires slicing, the processing method of the terminal device is given, that is, the terminal device can send the network device to the network device. Instructions.
  • the network device may determine and/or send at least one of the following according to the information of the demand slice indicated by the indication information: whether the serving cell of the terminal device supports the first indication of the demand slice; the DC configuration corresponding to the demand slice; the corresponding demand slice CA configuration; the activation or deactivation instruction of the CA corresponding to the required slice; the activation or deactivation instruction of the DC corresponding to the required slice; the second instruction that the terminal equipment needs to perform cell handover; the third instruction that the terminal equipment needs to perform cell redirection . Therefore, the service transmission corresponding to the demand slice can be guaranteed.
  • FIG. 4 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application.
  • the terminal device 400 includes: a processing unit 410, configured to obtain indication information, where the indication information is used to indicate the information of the required slice. Perform cell reselection or determine whether to trigger the connection establishment process in the serving cell of the terminal device according to the information of the required slice.
  • the indication information is generated by the NAS of the terminal device and sent to the AS of the terminal device; or,
  • the indication information is sent by the core network device to the terminal device through a NAS message; or,
  • the indication information is sent by the network device to the terminal device.
  • the indication information is carried in the paging message.
  • the indication information is sent when the priority of the required slice is higher than the priority of the slice currently configured, serviced or established by the terminal device.
  • the indication information is sent in a service request process, a PDU session establishment request process, a paging process, or a PDU session adjustment request process.
  • the indication information is sent when the service arrives.
  • the indication information is carried in the cause value.
  • the cause value is any one of the following: RRC establishment cause, RRC re-establishment cause, and cell reselection cause.
  • the terminal device is in a disconnected state.
  • the processing unit 410 is further configured to: if the terminal device is performing the cell reselection procedure, interrupt the cell reselection procedure.
  • processing unit 410 is further configured to: trigger the connection establishment process in the reselected cell.
  • the processing unit 410 is specifically configured to perform at least one of the following: if it is determined according to the information of the demand slice that the cell corresponding to the demand slice is the serving cell, determine that the connection establishment process is triggered in the serving cell of the terminal device. If it is determined according to the information of the demand slice that the cell corresponding to the demand slice is not the serving cell, it is determined that the serving cell of the terminal equipment is not in the serving cell to trigger the connection establishment process. If the terminal equipment determines that the cell corresponding to the demand slice is not the serving cell according to the information of the demand slice, it is determined that the connection establishment process is triggered in the serving cell of the terminal equipment, and only emergency service transmission is performed.
  • the processing unit 410 is specifically configured to: if the serving cell of the terminal device or the frequency of the serving cell cannot simultaneously support the current service of the terminal device and the service corresponding to the required slice, and/or the priority of the service corresponding to the required slice If the priority is higher than that of the current service, the cell reselection is performed according to the information of the demand slice or it is determined whether to trigger the connection establishment process in the serving cell of the terminal device.
  • the information of the required slice includes at least one of the following: an identifier of the required slice, the priority of the required slice, frequency point information corresponding to the required slice, and cell information corresponding to the required slice.
  • the frequency point information includes: frequency point identification and/or frequency point priority.
  • the above-mentioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip.
  • the terminal device 400 may correspond to the terminal device in the method embodiment corresponding to FIG. 2 , and the above-mentioned and other operations and/or functions of the various units in the terminal device 400 are respectively for realizing the above-mentioned FIG. 2
  • the corresponding process of the terminal device in the corresponding method embodiment will not be repeated here.
  • FIG. 5 shows a schematic block diagram of a terminal device 500 according to an embodiment of the present application.
  • the terminal device 500 includes:
  • the processing unit 510 is configured to obtain indication information, where the indication information is used to indicate the information of the required slice.
  • the communication unit 520 is configured to send indication information to the network device.
  • the indication information is generated by the NAS of the terminal device and sent to the AS of the terminal device.
  • the indication information is sent by the core network device to the terminal device through a NAS message.
  • the indication information is sent when the priority of the required slice is higher than the priority of the slice currently configured, serviced or established by the terminal device.
  • the indication information is sent in a service request process, a PDU session establishment request process, a paging process, or a PDU session adjustment request process.
  • the indication information is sent when the service arrives.
  • the indication information is carried in the cause value.
  • the cause value is any one of the following: RRC establishment cause, RRC re-establishment cause, and cell reselection cause.
  • the indication information is carried in a dedicated message.
  • the dedicated message is any one of the following: RRC message, MAC CE, UCI.
  • the indication information further includes first information.
  • the first information is used to request at least one of the following: perform cell handover. Establish carrier aggregation CA. A dual-connected DC is established. Perform cell redirection.
  • the communication unit 520 is further configured to: send capability indication information to the network device.
  • the capability indication information is used to indicate at least one of the following:
  • a combination or list of bandwidths supported by the end device is
  • the communication unit 520 is further configured to receive at least one of the following:
  • the first indication of whether the serving cell of the terminal device supports the required slicing is the first indication of whether the serving cell of the terminal device supports the required slicing.
  • the terminal device needs a second indication of cell handover.
  • the terminal device needs to perform a third indication of cell redirection.
  • the processing unit 510 is further configured to: if the first indication indicates that the serving cell of the terminal equipment supports the demand slicing, perform service transmission of the demand slicing in the serving cell.
  • the processing unit 510 is further configured to: perform the requirement slice operation according to at least one of the DC configuration, the DC activation or deactivation instruction corresponding to the requirement slice, the CA configuration, and the CA activation or deactivation instruction corresponding to the requirement slice. business transmission.
  • the processing unit 510 is specifically configured to: if at least one is determined according to at least one of the DC configuration, the DC activation or deactivation instruction corresponding to the demand slice, the CA configuration, and the CA activation or deactivation instruction corresponding to the demand slice If one cell supports required slicing, the service transmission of required slicing is performed on one cell of at least one cell.
  • the processing unit 510 is specifically configured to: if at least one is determined according to at least one of the DC configuration, the DC activation or deactivation instruction corresponding to the demand slice, the CA configuration, and the CA activation or deactivation instruction corresponding to the demand slice If one cell supports the required slice and the current service of the terminal equipment, the service transmission of the required slice and the transmission of the current service are simultaneously performed on one cell of at least one cell; or,
  • the activation or deactivation instruction of the DC corresponding to the demand slice, the CA configuration, and the activation or deactivation instruction of the CA corresponding to the demand slice supports the demand slice and the current service of the terminal equipment, Then, the service transmission of the required slice and the transmission of the current service are respectively performed on at least two cells of the at least one cell.
  • processing unit 510 is further configured to: perform cell handover and/or perform service transmission requiring slices according to the second instruction.
  • processing unit 510 is further configured to: perform cell redirection and/or perform service transmission requiring slices according to the third instruction.
  • the communication unit 520 is specifically configured to: if the serving cell of the terminal device or the frequency of the serving cell cannot simultaneously support the current service of the terminal device and the service corresponding to the required slice, and/or the priority of the service corresponding to the required slice If the priority is higher than the current service, the indication information is sent to the network device.
  • the terminal device is in a connected state.
  • the information of the required slice includes at least one of the following: an identifier of the required slice, the priority of the required slice, frequency point information corresponding to the required slice, and cell information corresponding to the required slice.
  • the frequency point information includes: frequency point identification and/or frequency point priority.
  • the above-mentioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip.
  • the terminal device 500 may correspond to the terminal device in the method embodiment corresponding to FIG. 3 , and the above-mentioned and other operations and/or functions of the various units in the terminal device 500 are for realizing the above-mentioned FIG. 3 , respectively.
  • the corresponding process of the terminal device in the corresponding method embodiment will not be repeated here.
  • FIG. 6 shows a schematic block diagram of a network device 600 according to an embodiment of the present application.
  • the network device 600 includes: a communication unit 610 and a processing unit 620 .
  • the communication unit 610 is configured to receive indication information, where the indication information is used to indicate the information of the required slice.
  • the processing unit 620 is configured to determine at least one of the following items according to the information of the demand slice, and/or the communication unit 610 is configured to send at least one of the following items:
  • the first indication of whether the serving cell of the terminal device supports the required slicing is the first indication of whether the serving cell of the terminal device supports the required slicing.
  • the terminal device needs a second indication of cell handover.
  • the terminal device needs to perform a third indication of cell redirection.
  • the indication information comes from a terminal device.
  • the indication information is generated by the NAS of the terminal device and sent to the AS of the terminal device.
  • the indication information is sent by the core network device to the terminal device through a NAS message.
  • the indication information is sent when the priority of the required slice is higher than the priority of the currently configured, serviced or established slice of the terminal device.
  • the indication information is sent in a service request process, a PDU session establishment request process, a paging process, or a PDU session adjustment request process.
  • the indication information is sent when the service arrives.
  • the indication information is carried in the cause value.
  • the cause value is any one of the following: RRC establishment cause, RRC re-establishment cause, and cell reselection cause.
  • the indication information is carried in a dedicated message.
  • the dedicated message is any one of the following: RRC message, MAC CE, UCI.
  • the indication information comes from an application server.
  • the displayed information further includes first information.
  • the first information is used to request at least one of the following: perform cell handover. Create a CA. Build DC. Perform cell redirection.
  • the communication unit 610 is further configured to: send capability indication information to the terminal device.
  • the capability indication information is used to indicate at least one of the following:
  • a combination or list of bandwidths supported by the end device is
  • the information of the required slice includes at least one of the following: an identifier of the required slice, the priority of the required slice, frequency point information corresponding to the required slice, and cell information corresponding to the required slice.
  • the frequency point information includes: frequency point identification and/or frequency point priority.
  • the processing unit 620 is specifically configured to: determine whether the demand slice needs to be supported according to the priority of the demand slice and the priority of the slice currently configured by the terminal device.
  • the processing unit 620 is further configured to: if the priority of the required slice is higher than the priority of the currently configured slice, determine that the required slice needs to be supported. If the priority of the demand slice is lower than or equal to the priority of the currently configured slice, it is determined that the demand slice does not need to be supported.
  • the processing unit 620 is specifically configured to: determine the DC configuration corresponding to the required slice, the activation or deactivation indication of the DC corresponding to the required slice, the CA configuration, the required slice, according to the information of the required slice and the information of the slice supported by the serving cell. At least one of activation or deactivation indication of the corresponding CA, cell handover and cell redirection.
  • the processing unit 620 is specifically configured to: if the serving cell of the terminal device or the frequency of the serving cell cannot simultaneously support the current service of the terminal device and the service corresponding to the required slice, and/or the priority of the service corresponding to the required slice If the priority is higher than the current service, at least one item is determined according to the indication information.
  • the communication unit 610 is specifically configured to: if the serving cell of the terminal device or the frequency of the serving cell cannot simultaneously support the current service of the terminal device and the service corresponding to the required slice, and/or, the priority of the service corresponding to the required slice If the priority is higher than the current service, at least one item is sent according to the indication information.
  • the terminal device is in a connected state.
  • the above-mentioned communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system-on-chip.
  • the network device 600 may correspond to the network device in the method embodiment corresponding to FIG. 2 , and the above-mentioned and other operations and/or functions of each unit in the network device 600 are for realizing the above-mentioned FIG. 2 , respectively.
  • the corresponding process of the network device in the corresponding method embodiment is not repeated here for brevity.
  • FIG. 7 is a schematic structural diagram of a communication device 700 provided by an embodiment of the present application.
  • the communication device 700 shown in FIG. 7 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
  • the communication device 700 may further include a memory 720 .
  • the processor 710 may call and run a computer program from the memory 720 to implement the methods in the embodiments of the present application.
  • the memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .
  • the communication device 700 may further include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate with other devices, specifically, may send information or data to other devices, or receive other devices Information or data sent by a device.
  • the processor 710 may control the transceiver 730 to communicate with other devices, specifically, may send information or data to other devices, or receive other devices Information or data sent by a device.
  • the transceiver 730 may include a transmitter and a receiver.
  • the transceiver 730 may further include antennas, and the number of the antennas may be one or more.
  • the communication device 700 may specifically be the network device in this embodiment of the present application, and the communication device 700 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, details are not repeated here. .
  • the communication device 700 may specifically be the terminal device of the embodiment of the present application, and the communication device 700 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which is not repeated here for brevity. .
  • FIG. 8 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
  • the apparatus 800 shown in FIG. 8 includes a processor 810, and the processor 810 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
  • the apparatus 800 may further include a memory 820 .
  • the processor 810 may call and run a computer program from the memory 820 to implement the methods in the embodiments of the present application.
  • the memory 820 may be a separate device independent of the processor 810 , or may be integrated in the processor 810 .
  • the apparatus 800 may further include an input interface 830 .
  • the processor 810 may control the input interface 830 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.
  • the apparatus 800 may further include an output interface 840 .
  • the processor 810 may control the output interface 840 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
  • the apparatus can be applied to the network equipment in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application, which are not repeated here for brevity.
  • the apparatus may be applied to the terminal equipment in the embodiments of the present application, and the apparatus may implement the corresponding processes implemented by the terminal equipment in each method of the embodiments of the present application, which will not be repeated here for brevity.
  • the device mentioned in the embodiment of the present application may also be a chip.
  • it can be a system-on-chip, a system-on-a-chip, a system-on-a-chip, or a system-on-a-chip.
  • FIG. 9 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in FIG. 9 , the communication system 900 includes a terminal device 910 and a network device 920 .
  • the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method
  • the network device 920 can be used to implement the corresponding functions implemented by the network device or the base station in the above method. Repeat.
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment 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 may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be Random Access Memory (RAM), which acts as an external cache.
  • RAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory Synchlink DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a 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, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
  • Embodiments of the present application further provide a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium can be applied to the network device or the base station in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device or the base station in each method of the embodiments of the present application, in order to It is concise and will not be repeated here.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and are not repeated here for brevity.
  • Embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device or the base station in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device or the base station in the various methods of the embodiments of the present application, for the sake of brevity. , and will not be repeated here.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, For brevity, details are not repeated here.
  • the embodiments of the present application also provide a computer program.
  • the computer program can be applied to the network device or the base station in the embodiments of the present application, and when the computer program runs on the computer, the computer can execute the corresponding methods implemented by the network device or the base station in each method of the embodiments of the present application.
  • the process for the sake of brevity, will not be repeated here.
  • the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application, and when the computer program is run on the computer, the mobile terminal/terminal device implements the various methods of the computer program in the embodiments of the present application.
  • the corresponding process for the sake of brevity, will not be repeated here.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of 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 components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

本申请实施例提供了一种无线通信方法、终端设备和网络设备。该方法包括:终端设备获取指示信息,指示信息用于指示需求切片的信息;终端设备根据需求切片的信息进行小区重选或者确定是否在终端设备的服务小区触发连接建立过程。从而给出了在终端设备当前配置了切片的情况下,当终端设备获取到需求切片的信息时,终端设备的处理方法。

Description

无线通信方法、终端设备和网络设备 技术领域
本申请实施例涉及通信领域,并且更具体地,涉及无线通信方法、终端设备和网络设备。
背景技术
垂直行业对无线通信的需求是有目共睹的,为了满足垂直行业对延迟、移动性、可靠性、位置精度等方面的需求,无线接入网络(Radio Access Network,RAN)需要对如何在接入网支持垂直业务进行增强。其中,一种方式是通过切片或者网络切片(slicing)对不同需求的多个业务提供更低时延,更有目标性,更大的灵活性和更高的可扩展性服务。
在终端设备当前配置了切片的情况下,当终端设备获取到需求切片的信息时,终端设备如何进行处理,是本申请亟待解决的技术问题。
发明内容
本申请实施例提供了一种无线通信方法、终端设备和网络设备。从而给出了在终端设备当前配置了切片的情况下,当终端设备获取到需求切片的信息时,终端设备的处理方法。
第一方面,提供了一种无线通信方法,该方法包括:终端设备获取指示信息,指示信息用于指示需求切片的信息;终端设备根据需求切片的信息进行小区重选或者确定是否在终端设备的服务小区触发连接建立过程。
第二方面,提供了一种无线通信方法,该方法包括:终端设备获取指示信息,指示信息用于指示需求切片的信息;终端设备向网络设备发送指示信息。
第三方面,提供了一种无线通信方法,该方法包括:网络设备接收指示信息,指示信息用于指示需求切片的信息;网络设备根据需求切片的信息确定和/或发送以下至少一项:终端设备的服务小区是否支持需求切片的第一指示;需求切片对应的DC配置;需求切片对应的CA配置;终端设备需要进行小区切换的第二指示;终端设备需要进行小区重定向的第三指示。
第四方面,提供了一种终端设备,用于执行上述第一方面或其各实现方式中的方法。
具体地,该终端设备包括用于执行上述第一方面或其各实现方式中的方法的功能模块。
第五方面,提供了一种终端设备,用于执行上述第二方面或其各实现方式中的方法。
具体地,该终端设备包括用于执行上述第二方面或其各实现方式中的方法的功能模块。
第六方面,提供了一种网络设备,用于执行上述第三方面或其各实现方式中的方法。
具体地,该网络设备包括用于执行上述第三方面或其各实现方式中的方法的功能模块。
第七方面,提供了一种终端设备,包括处理器和存储器。该存储器用于存储计算机程序,该处理器用于调用并运行该存储器中存储的计算机程序,执行上述第一方面或其各实现方式中的方法。
第八方面,提供了一种终端设备,包括处理器和存储器。该存储器用于存储计算机程序,该处理器用于调用并运行该存储器中存储的计算机程序,执行上述第二方面或其各实现方式中的方法。
第九方面,提供了一种网络设备,包括处理器和存储器。该存储器用于存储计算机程序,该处理器用于调用并运行该存储器中存储的计算机程序,执行上述第三方面或其各实现方式中的方法。
第十方面,提供了一种装置,用于实现上述第一方面至第三方面中的任一方面或其各实现方式中的方法。
具体地,该装置包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有该装置的设备执行如上述第一方面至第三方面中的任一方面或其各实现方式中的方法。
第十一方面,提供了一种计算机可读存储介质,用于存储计算机程序,该计算机程序使得计算机执行上述第一方面至第三方面中的任一方面或其各实现方式中的方法。
第十二方面,提供了一种计算机程序产品,包括计算机程序指令,计算机程序指令使得计算机执行上述第一方面至第三方面中的任一方面或其各实现方式中的方法。
第十三方面,提供了一种计算机程序,当其在计算机上运行时,使得计算机执行上述第一方面至第三方面中的任一方面或其各实现方式中的方法。
通过上述第一方面至第三方面的任一方面的技术方案,给出了在终端设备当前配置了切片的情况下,当终端设备获取到需求切片的信息时,终端设备的处理方法。终端设备可以根据需求切片的信息进行小区重选或者确定是否在终端设备的服务小区触发连接建立过程,从而可以保证需求切片对应的业务传输或者小区驻留。或者,网络设备可以根据指示信息所指示的需求切片的信息确定和/或发送以下至少一项:终端设备的服务小区是否支持需求切片的第一指示;需求切片对应的DC配置;需求切片对应的DC的激活或去激活指示;需求切片对应的CA配置;需求切片对应的CA的激活或去激 活指示;终端设备需要进行小区切换的第二指示;终端设备需要进行小区重定向的第三指示。从而可以保证需求切片对应的业务传输。
附图说明
图1为本申请实施例提供的一种通信系统架构的示意性图;
图2为本申请一实施例提供的无线通信方法流程图;
图3为本申请另一实施例提供的无线通信方法交互流程图;
图4示出了根据本申请实施例的终端设备400的示意性框图;
图5示出了根据本申请实施例的终端设备500的示意性框图;
图6示出了根据本申请实施例的网络设备600的示意性框图;
图7是本申请实施例提供的一种通信设备700示意性结构图;
图8是本申请实施例的装置的示意性结构图;
图9是本申请实施例提供的一种通信系统900的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。针对本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
本申请实施例可以应用于各种通信系统,例如:全球移动通讯(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)系统、先进的长期演进(Advanced long term evolution,LTE-A)系统、新空口(New Radio,NR)、NR系统的演进系统、免授权频谱上的LTE(LTE-based access to unlicensed spectrum,LTE-U)系统、免授权频谱上的NR(NR-based access to unlicensed spectrum,NR-U)系统、通用移动通信系统(Universal Mobile Telecommunication System,UMTS)、无线局域网(Wireless Local Area Networks,WLAN)、无线保真(Wireless Fidelity,WiFi)、下一代通信系统或其他通信系统等。
通常来说,传统的通信系统支持的连接数有限,也易于实现,然而,随着通信技术的发展,移动通信系统将不仅支持传统的通信,还将支持例如,设备到设备(Device to Device,D2D)通信,机器到机器(Machine to Machine,M2M)通信,机器类型通信(Machine Type Communication,MTC),以及车辆间(Vehicle to Vehicle,V2V)通信等,本申请实施例也可以应用于这些通信系统。
可选地,本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation,CA)场景,也可以应用于双连接(Dual Connectivity,DC)场景,还可以应用于独立(Standalone,SA)布网场景。
本申请实施例对应用的频谱并不限定。例如,本申请实施例可以应用于授权频谱,也可以应用于免授权频谱。
示例性的,本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110,网络设备110可以是与终端设备120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖,并且可以与位于该覆盖区域内的终端设备进行通信。
图1示例性地示出了一个网络设备和两个终端设备,可选地,该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备,本申请实施例对此不做限定。
可选地,该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体,本申请实施例对此不作限定。
应理解,本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例,通信设备可包括具有通信功能的网络设备110和终端设备120,网络设备110和终端设备120可以为上文所述的具体设备,此处不再赘述;通信设备还可包括通信系统100中的其他设备,例如网络控制器、移动管理实体等其他网络实体,本申请实施例中对此不做限定。
应理解,本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
本申请实施例结合终端设备和网络设备描述了各个实施例,其中:终端设备也可以称为用户设备(User Equipment,UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。终端设备可以是WLAN中的站 点(STAION,ST),可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol,SIP)电话、无线本地环路(Wireless Local Loop,WLL)站、个人数字处理(Personal Digital Assistant,PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及下一代通信系统,例如,NR网络中的终端设备或者未来演进的公共陆地移动网络(Public Land Mobile Network,PLMN)网络中的终端设备等。
作为示例而非限定,在本申请实施例中,该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备,是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称,如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上,或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备,更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能,例如:智能手表或智能眼镜等,以及只专注于某一类应用功能,需要和其它设备如智能手机配合使用,如各类进行体征监测的智能手环、智能首饰等。
网络设备可以是用于与移动设备通信的设备,网络设备可以是WLAN中的接入点(Access Point,AP),GSM或CDMA中的基站(Base Transceiver Station,BTS),也可以是WCDMA中的基站(NodeB,NB),还可以是LTE中的演进型基站(Evolutional Node B,eNB或eNodeB),或者中继站或接入点,或者车载设备、可穿戴设备以及NR网络中的网络设备或者基站(gNB)或者未来演进的PLMN网络中的网络设备等。
在本申请实施例中,网络设备为小区提供服务,终端设备通过该小区使用的传输资源(例如,频域资源,或者说,频谱资源)与网络设备进行通信,该小区可以是网络设备(例如基站)对应的小区,小区可以属于宏基站,也可以属于小小区(Small cell)对应的基站,这里的小小区可以包括:城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等,这些小小区具有覆盖范围小、发射功率低的特点,适用于提供高速率的数据传输服务。
在介绍本申请技术方案之前,下面先介绍小区重选和寻呼:
(1)小区重选:
终端设备在非连接态(即空闲态或者非激活态)下执行小区选择和重选过程中,为了满足空闲态下的负荷均衡,定义了基于频率优先级的小区重选策略。
小区重选(cell reselection)指终端设备在非连接态下通过监测邻区和当前服务小区的信号质量,以选择一个最好的小区提供服务信号的过程。当邻区的信号质量及电平满足S准则满足一定重选判决准则时,终端设备将接入该小区驻留。
终端设备成功驻留到驻留小区后,将持续对该小区进行测量。终端设备在无线资源控制(Radio Resource Control,RRC)层根据参考信号接收功率(Reference Signal Received Power,RSRP)测量结果计算Srxlev(即S准则),并将其与Sintrasearch(即同频测量启动门限)和Snonintrasearch(即异频/异系统测量启动门限)比较,作为是否启动邻区测量的判决条件。
在同频或者频率同优先级的异频的小区重选中,采用R准则进行小区重选,即按照小区的信号质量进行排序,选择信号质量最好的小区为候选的重选目标小区。对于高频率优先级的小区,只要小区信号质量满足一定门限,就重选到频率优先级高的小区中去,对于低频率优先级的小区,只有当服务小区的信号质量低于一定门限时才会重选过去。
(2)寻呼(Paging):
由网络设备向空闲态或非激活态或连接态的终端设备发起。寻呼分为核心网(Core Network,CN)初始的寻呼消息和RAN初始的寻呼消息。
CN初始寻呼:在注册的跟踪区域(Tracking Area,TA)列表(list)范围内发起寻呼。通知终端设备接收寻呼消息。
RAN初始寻呼:在RAN范围内发起寻呼消息。通知终端设备接收寻呼消息。
网络设备触发寻呼:在小区范围内发起寻呼;通知系统消息更新以及通知终端设备接收地震和海啸预警系统(Earthquake and Tsunami Warning System,ETWS)等信息。此时在下行控制信息(Downlink Control Information,DCI)中携带该系统消息变更指示和公共预警系统(Public Warning System,PWS)通知指示。
其中,寻呼消息承载于寻呼控制信道(Paging Control Channel)、寻呼信道(Paging Channel,PCH)、物理下行共享信道(Physical Downlink Shared Channel,PDSCH)上;通过物理下行控制信道(Physical Downlink Control Channel,PDCCH)调度传输。寻呼-无线网络临时标识(paging-Radio Network Temporary Identifier,P-RNTI)取值固定为FFFE,用于加扰寻呼消息的DCI。当有寻呼时,网络设备会在计算好的寻呼时机,在PDCCH上下发PDCCH授权(grant)。如果终端设备在寻呼时 机上监听到P-RNTI,则会到指定的时频资源上接收寻呼消息。
需要说明的是,本申请中的空闲态也被描述为RRC空闲态(RRC_IDLE),非激活态也被描述为RRC非激活态(RRC_INACTIVE),连接态也被描述为RRC连接态(RRC_CONNECTED)。
寻呼消息包含:
被寻呼终端设备的标识:CN初始寻呼时该标识为服务临时移动用户标识(Serving-Temporary Mobile Subscriber Identity,S-TMSI),RAN初始寻呼时该标识为系统信息临时移动用户标识(System Information-Temporary Mobile Subscriber Identity,SI-RNTI)。不支持国际移动用户识别码(International Mobile Subscriber Identity,IMSI)/订阅永久标识符(Subscription Permanent Identifier,SUPI)/订阅隐藏标识符(Subscription Concealed Identifier,SUCI)用于寻呼终端设备。其中,最多可以同时寻呼32个终端设备。
触发寻呼的接入类型(Access type):第三代合作伙伴计划(3rd Generation Partnership Project,3GPP)或者非3GPP。其中,用于指示分组数据单元(Packet Data Unit,PDU)会话(session)所属于的接入网技术指示需要递交给高层。
处于不同的RRC状态,对于寻呼消息的接收有不同的需求。
Figure PCTCN2020109883-appb-000001
终端设备在RRC_IDLE和RRC_INACTIVE状态下在自己的寻呼时机接收寻呼消息。终端设备不用始终监听PDCCH,只有在寻呼时机时监听即可,达到终端设备侧省电的目的。寻呼时机的计算基于DRX,DRX的大小决定了终端设备省电和接入时延之间均衡。用于终端设备计算寻呼时机的DRX有三个:
小区默认DRX周期(Cell default DRX cycle):其是小区系统广播的小区级别的DRX。
终端设备专用DRX(UE specific DRX):其是由终端设备决定的DRX,通过非接入层(Non-Access Stratrum,NAS)消息发给CN侧,在寻呼是CN侧发送给网络设备的。
RAN DRX:当网络侧决定让终端设备进入非激活态时,通过RRC释放(Release)消息配置给终端设备。
终端设备和网络侧采用最小原则选择DRX用于计算寻呼时机。对于RRC_IDLE UE,使用Cell default DRX cycle和UE specific DRX中最小的DRX。对于RRC_INACTIVE UE,使用Cell default DRX cycle,UE specific DRX和RAN DRX中最小的DRX。
下面针对本申请技术方案,进行详细阐述:
图2为本申请一实施例提供的无线通信方法流程图,该方法包括如下步骤:
步骤S210:终端设备获取指示信息,指示信息用于指示需求切片的信息。
步骤S220:终端设备根据需求切片的信息进行小区重选或者确定是否在终端设备的服务小区触发连接建立过程。
可选地,本实施例适用于终端设备处于非连接态的场景,但不限于此。其中,在终端设备处于非连接态时,网络设备可以通过系统消息广播网络设备支持的切片的信息。
可选地,网络设备支持的切片的信息包括,但不限于以下至少一项:网络设备支持的切片的标识,该切片的优先级,该切片对应的频点信息,该切片对应的小区信息。
可选地,网络设备支持的切片可以是网络设备所覆盖的小区支持的切片,也可以不是除该网络设 备所覆盖的小区之外的其他小区支持的切片。
可选地,上述网络设备可以根据其支持的切片的信息为终端设备配置切片,其中配置的切片可以是网络设备支持的任一切片。
应理解的是,上述配置的切片也被描述为当前配置的切片、当前服务的切片、当前建立的切片或者当前允许的切片。
可选地,终端设备可以选择该上述配置的切片对应的小区驻留。
应理解的是,上述需求切片的信息也被描述为需求的切片的信息,或者,上述终端设备的需求切片的信息,或者,上述终端设备的需求的切片的信息。本申请对此不作限制。
可选地,需求切片的信息包括,但不限于以下至少一项:需求切片的标识,需求切片的优先级,需求切片对应的频点信息,需求切片对应的小区信息。
可选地,需求切片的标识可以是单一网络切片选择辅助信息(Single Network Slice Selection Assistance Information,S-NSSAI)或者是网络切片选择辅助信息(Network Slice Selection Assistance Information,NSSAI),本申请对此不作限制。
应理解的是,切片与小区一一对应。因此,需求切片对应的频点信息也被描述为该需求切片对应的小区的频点信息。
可选地,频点信息包括但不限于如下信息:频点标识和/或频点优先级。
可选地,需求切片对应的小区信息包括,但不限于如下信息:需求切片对应的小区的标识、该小区的优先级、该小区的频点信息、该小区的带宽信息。
可选地,当终端设备处于非连接态时,终端设备可以通过如下方式获取指示信息,但不限于此:
1、指示信息是由终端设备的非接入层(Non-Access Stratrum,NAS)生成,并发送给终端设备的接入层(Access Stratrum,AS)的。
2、指示信息是由核心网设备通过NAS消息发送给终端设备的。
3、指示信息是由网络设备发送给所述终端设备的,例如指示信息携带在寻呼消息中。
可选地,核心网设备可在被叫,数据推送时,向网络设备发送寻呼消息,进一步地,该网络设备可以向终端设备发送该寻呼消息。
可选地,该核心网设备是接入和移动性管理实体(Access and Mobility Management Function,AMF),但不限于此。
可选地,指示信息是在服务请求(Service request)过程、PDU会话建立请求(PDU session establishment request)过程、寻呼过程或者PDU会话调整请求(PDU session modification request)过程中发送的。或者,指示信息是在业务到达时发送的。
可选地,该业务可以是寻呼业务或者是其他数据业务等,本申请对此不作限制。
可选地,针对指示信息是由终端设备的NAS发送给AS的情况,终端设备的NAS可以在任何情况下给AS发送该指示信息,也可以在满足一定条件的情况下,发送该指示信息。
可选地,针对指示信息是由核心网设备通过NAS发送给终端设备的情况,核心网设备可以在任何情况下给终端设备发送该指示信息,也可以在满足一定条件的情况下,发送该指示信息。
可选地,针对指示信息是由网络设备发送给终端设备的情况,接入网设备可以在任何情况下给终端设备发送该指示信息,也可以在满足一定条件的情况下,发送该指示信息。
可选地,上述条件可以是需求切片的优先级高于终端设备当前配置、服务或者建立的切片的优先级。或者,上述条件时需求切片的优先级不低于终端设备当前配置、服务或者建立的切片的优先级。
可选地,指示信息可以携带在原因值中。
可选地,上述原因值为以下任一项,但不限于此:RRC建立原因(Establishment Cause)、RRC重建原因(Reestablishment Cause)、小区重选原因(Resume Cause)。
需要说明的是,需求切片的信息除了可以通过指示信息获取之外,该需求切片的信息也可以是网络设备预配置给终端设备的,本申请对此不作限制。
可选地,如上所述,终端设备可以选择该上述配置的切片对应的小区驻留。当终端设备获取到需求切片的信息之后,若终端设备没有正在执行小区重选过程,则可以直接进行小区重选。若终端设备正在执行小区重选过程,则终端设备中断当前小区重选过程,进一步地,终端设备根据需求切片的信息进行小区重选。
可选地,针对指示信息是由终端设备的NAS发送给AS的情况,而终端设备的NAS通过指示信息仅是为了更新需求切片的信息,而不是为了触发业务传输或者PDU会话建立时,终端设备根据需求切片的信息进行小区重选即可。
可选地,针对指示信息是由终端设备的NAS发送给AS的情况,而终端设备的NAS通过指示信 息是为了触发业务传输或者PDU会话建立时,终端设备根据需求切片的信息进行小区重选之后,可以在重选后的小区触发连接建立过程。
可选地,针对指示信息是由核心网设备通过NAS发送给终端设备或者是由核心网设备发送给终端设备的情况,终端设备根据需求切片的信息进行小区重选之后,也可以在重选后的小区触发连接建立过程。
可选地,针对指示信息是是由网络设备发送给终端设备的情况,终端设备根据需求切片的信息进行小区重选之后,也可以在重选后的小区触发连接建立过程。
可选地,上述连接建立过程包括但不限于:RRC连接建立过程、PDU会话建立过程。
可选地,若终端设备根据需求切片的信息确定需求切片对应的小区是服务小区,则终端设备确定在终端设备的服务小区触发连接建立过程。若终端设备根据需求切片的信息确定需求切片对应的小区不是服务小区,则终端设备确定不在终端设备的服务小区触发连接建立过程。若终端设备根据需求切片的信息确定需求切片对应的小区不是服务小区,则终端设备确定在终端设备的服务小区触发连接建立过程,但仅支持紧急业务传输。
可选地,当终端设备获取到需求切片的信息之后,可以直接根据需求切片的信息进行小区重选或者确定是否在终端设备的服务小区触发连接建立过程。或者,当终端设备获取到需求切片的信息之后,终端设备确定满足如下条件时,才进行小区重选或者确定是否在终端设备的服务小区触发连接建立过程。
可选地,上述条件包括但不限于:终端设备的服务小区或者服务小区的频点不能同时支持终端设备的当前业务和需求切片对应的业务,和/或,需求切片对应的业务的优先级高于当前业务的优先级和/或,需求切片的优先级不低于终端设备当前配置、服务或者建立的切片的优先级。
综上,在本申请中,给出了在非连接态的终端设备当前配置了切片的情况下,当终端设备获取到需求切片的信息时,终端设备的处理方法,即终端设备可以根据需求切片的信息进行小区重选或者确定是否在终端设备的服务小区触发连接建立过程。进一步地,在本申请中,终端设备可以根据需求切片的信息进行小区重选或者确定是否在终端设备的服务小区触发连接建立过程,从而可以保证需求切片对应的业务传输或者小区驻留。
图3为本申请另一实施例提供的无线通信方法交互流程图,该方法包括如下步骤:
步骤S310:终端设备获取指示信息,指示信息用于指示需求切片的信息。
步骤S320:终端设备向网络设备发送指示信息。
步骤S330:网络设备根据需求切片的信息确定和/或发送以下至少一项:终端设备的服务小区是否支持需求切片的第一指示;需求切片对应的双连接(Dual Connectivity,DC)配置;需求切片对应的DC的激活或去激活指示;需求切片对应的载波聚合(Carrier Aggregation,CA)配置;需求切片对应的CA的激活或去激活指示;终端设备需要进行小区切换的第二指示;终端设备需要进行小区重定向的第三指示。
可选地,本实施例适用于终端设备处于连接态,有上行链路(Uplink,UL)新业务需求触发,或者,UL新业务到达的场景,有下行链路(downlink,DL)新业务需求触发,或者,DL新业务到达的场景,但不限于此。在这种场景下,可以建立新的PDU会话,以支持需求切片。网络设备也可以通过RRC重配置消息,为终端设备配置数据无线承载(Data Radio Bearer,DRB)。
其中,网络设备可以通过系统消息广播网络设备支持的切片的信息。
关于网络设备支持的切片的信息、网络设备为终端设备配置的切片的信息以及需求切片的信息的阐述,可以参考图2对应的实施例,本申请对此不再赘述。
可选地,终端设备可以选择网络设备为其配置的切片对应的小区驻留。进一步地,终端设备可以在该小区建立连接,并进行业务传输。
可选地,终端设备可以通过如下方式获取指示信息,但不限于此:指示信息是由终端设备的NAS生成,并发送给终端设备的AS的。或者,指示信息是由核心网设备通过NAS消息发送给终端设备的。
可选地,该核心网设备可以是AMF,也可以是其他核心网设备,本申请对此不作限制。
可选地,指示信息是在服务请求(Service request)过程、PDU会话建立请求(PDU session establishment request)过程、寻呼过程或者PDU会话调整请求(PDU session modification request)过程中发送的。或者,指示信息是在业务到达时发送的。
可选地,该业务可以是寻呼业务或者是其他数据业务等,本申请对此不作限制。
可选地,针对指示信息是由终端设备的NAS发送给AS的情况,终端设备的NAS可以在任何情况下给AS发送该指示信息,也可以在满足一定条件的情况下,发送该指示信息。
可选地,针对指示信息是由核心网设备通过NAS消息发送给终端设备的情况,核心网设备可以在任何情况下给终端设备发送该指示信息,也可以在满足一定条件的情况下,发送该指示信息。
可选地,上述条件可以是需求切片的优先级高于终端设备当前配置、服务或者建立的切片的优先级。或者,上述条件时需求切片的优先级不低于终端设备当前配置、服务或者建立的切片的优先级。
可选地,指示信息可以携带在原因值中。
可选地,上述原因值为以下任一项,但不限于此:RRC建立原因(Establishment Cause)、RRC重建原因(Reestablishment Cause)、小区重选原因(Resume Cause)。
可选地,终端设备可以通过专用消息向网络设备发送指示信息。
可选地,专用消息为以下任一项:RRC消息、媒体接入控制控制单元(Media Access Control Control Element,MAC CE)、上行控制信息(Uplink Control Information,UCI)。
可选地,终端设备可以在任何情况下向网络设备发送上述指示信息,也可以在满足一定条件的情况下,发送该指示信息。
可选地,该条件包括但不限于:终端设备的服务小区或者服务小区的频点不能同时支持终端设备的当前业务和需求切片对应的业务,和/或,需求切片对应的业务的优先级高于当前业务的优先级,和/或,需求切片的优先级不低于终端设备当前配置、服务或者建立的切片的优先级。
需要说明的是,需求切片的信息除了可以通过指示信息获取之外,该需求切片的信息也可以是网络设备预配置给终端设备的,本申请对此不作限制。
需要说明的是,网络设备获取指示信息的方式,除了采用上述从终端设备处获取指示信息之外,还可以从应用服务器处获取上述指示信息,其中,应用服务器可以直接将指示信息发送给网络设备,或者,应用服务器发送给终端设备,终端设备的应用层将该指示信息发送给网络设备。总之,本申请对网络设备如何获取指示信息不作限制。
可选地,指示信息还包括第一信息。其中,第一信息用于请求以下至少一项:进行小区切换;建立CA;建立DC;进行小区重定向。
需要说明的是,上述指示信息也可以不包括第一信息,即无需终端设备向网络设备发送上述至少一项请求。
可选地,网络设备可以根据终端设备的服务小区的信息和需求切片的信息确定和/或发送终端设备的服务小区是否支持需求切片的第一指示。
示例性地,当终端设备的服务小区支持的频点为A,而需求切片支持的频点为B时,A和B不同,表示终端设备的服务小区不支持需求切片。这种情况下,网络设备可以确定和/或发送上述第一指示。
可选地,若第一指示指示终端设备的服务小区支持需求切片,则终端设备在服务小区进行需求切片的业务传输。相反,若网络设备确定终端设备的服务小区不支持需求切片,则网络设备可以根据需求切片的信息确定是否需要支持需求切片。例如:采用CA、DC、小区切换、小区重定向中的至少一项技术,来支持上述需求切片,以实现需求切片的业务传输。
可选地,网络设备可以通过如下方式确定是否需要支持需求切片,但不限于此:
1、网络设备根据需求切片的优先级和终端设备当前配置的切片的优先级,确定是否需要支持需求切片。或者,
2、网络设备根据需求切片的频点的优先级和终端设备当前配置的切片的频点的优先级,确定是否需要支持需求切片。
3、如存在正在服务的切片,且正在服务的切片和需求切片不能同时支持,确定是否需要支持需求的切片。
针对第1点进行说明:
可选地,若需求切片的优先级高于当前配置的切片的优先级,则网络设备确定需要支持需求切片。若需求切片的优先级低于或等于当前配置的切片的优先级,则网络设备确定不需要支持需求切片。或者,若需求切片的优先级等于或高于当前配置的切片的优先级,则网络设备确定需要支持需求切片。若需求切片的优先级低于当前配置的切片的优先级,则网络设备确定不需要支持需求切片。
针对第2点进行说明:
可选地,若需求切片的频点的优先级高于当前配置的切片的频点的优先级,则网络设备确定需要支持需求切片。若需求切片的频点的优先级低于或等于当前配置的切片的频点的优先级,则网络设备确定不需要支持需求切片。或者,若需求切片的频点的优先级等于或高于当前配置的切片的频点的优先级,则网络设备确定需要支持需求切片。若需求切片的频点的优先级低于当前配置的切片的频点的优先级,则网络设备确定不需要支持需求切片。
针对第3点进行说明:
如存在正在服务的切片,且正在服务的切片和需求切片不能同时支持,确定需要支持需求的切片,或者不需要支持需求的切片。
可选地,在网络设备确定需要支持需求切片时,网络设备可以根据需求切片的信息和服务小区支持的切片的信息,确定需求切片对应的DC配置、需求切片对应的DC的激活或去激活指示、CA配置、需求切片对应的CA的激活或去激活指示、进行小区切换和进行小区切换中的至少一项。
需要说明的是,服务小区支持的切片的信息也被描述为网络设备支持的切片的信息。关于网络设备支持的切片的信息,可参考上一实施例,本申请对此不再赘述。
下面对网络设备可以根据需求切片的信息和服务小区支持的切片的信息,确定需求切片对应的DC配置、需求切片对应的DC的激活或去激活指示、CA配置、需求切片对应的CA的激活或去激活指示、进行小区切换和进行小区切换中的至少一项,进行示例性说明:
示例一:当终端设备的服务小区支持的频点为A,而需求切片支持的频点为B时,网络设备可以对服务小区和其他小区采用DC或者CA技术,使得终端设备对应的频点可以为B,这样可以实现需求切片的业务传输。
示例二:当终端设备的服务小区支持的频点为A,而需求切片支持的频点为B时,此时若网络设备确定其他一小区支持的频点为B,则指示终端设备切换至该小区,使得终端设备对应的频点可以为B,这样可以实现需求切片的业务传输。
可选地,终端设备可以向网络设备发送能力指示信息。其中,能力指示信息用于指示用于指示以下至少一项:
1、终端设备是否支持CA。
2、终端设备是否支持DC。
3、终端设备支持的频点。
4、终端设备支持的带宽。
5、终端设备支持的带宽组合或列表。
6、支持的切片对应的频点组合或列表。
7、支持的切片对应的带宽组合或列表。
8、支持的切片对应的载波组合或列表。
其中,第5项中的列表是终端设备支持的带宽组合的列表。第6项中的列表是终端设备支持的切片对应的频点组合的列表。第7项中的列表是终端设备支持的切片对应的带宽组合的列表。第8项中的列表是终端设备支持的切片对应的载波组合的列表。
可选地,若终端设备向网络设备发送了能力指示信息,那么在步骤S330中,网络设备可以根据需求切片的信息、服务小区支持的切片信息和终端设备的能力指示信息确定和/或发送以下至少一项:需求切片对应的DC配置;需求切片对应的DC的激活或去激活指示;需求切片对应的CA配置;需求切片对应的CA的激活或去激活指示;终端设备需要进行小区切换的第二指示;终端设备需要进行小区重定向的第三指示。
示例性地,当终端设备的服务小区支持的频点为A,而需求切片支持的频点为B时,但是终端设备不支持CA和DC技术,而支持小区切换技术,这时若网络设备确定其他一小区支持的频点为B,则指示终端设备切换至该小区,使得终端设备对应的频点可以为B,这样可以实现需求切片的业务传输。
可选地,若网络设备向终端设备发送了需求切片对应的DC配置和/或CA配置,和/或,需求切片对应的DC和/或CA的激活或去激活指示;则终端设备根据DC配置和/或CA配置,和/或,需求切片对应的DC和/或CA的激活或去激活指示进行需求切片的业务传输。
可选地,针对需求切片的业务传输而言:若DC配置和/或CA配置中的,和/或,需求切片对应的DC和/或CA的激活或去激活指示确定的小区中的至少一个小区支持需求切片,则终端设备在至少一个小区上的一个小区上进行需求切片的业务传输。
可选地,针对需求切片的业务传输和当前业务的传输而言:若DC配置和/或CA配置中的,和/或,需求切片对应的DC和/或CA的激活或去激活指示确定的小区中的至少一个小区支持需求切片和终端设备当前业务,则终端设备在至少一个小区的一个小区上同时进行需求切片的业务传输和当前业务的传输。例如:需求切片的业务传输和当前业务的传输均在小区1执行。或者,若DC配置和/或CA配置中的至少一个小区支持需求切片和终端设备当前业务,则终端设备在至少一个小区的至少两个小区上分别进行需求切片的业务传输和当前业务的传输。例如:需求切片的业务传输在小区1执行,当前业务的传输在小区2执行。
需要说明的是,当需求切片对应的小区处于去激活态时,终端设备可以执行以下至少一项:激活该小区;进行定时(Timing Advance,TA)同步;向网络设备指示需要激活该小区。
可选地,若网络设备向终端设备发送了需求切片对应的第二指示,则终端设备根据第二指示进行小区切换和/或进行需求切片的业务传输。
可选地,若网络设备向终端设备发送了需求切片对应的第三指示,则终端设备根据第三指示进行小区重定向和/或进行需求切片的业务传输。
可选地,网络设备可以在任何情况下确定和/或发送以下至少一项:终端设备的服务小区是否支持需求切片的第一指示;需求切片对应的DC配置;需求切片对应的CA配置;需求切片对应的CA的激活或去激活指示;需求切片对应的DC的激活或去激活指示;终端设备需要进行小区切换的第二指示;终端设备需要进行小区重定向的第三指示。或者,网络设备在满足一定条件下,确定和/或发送以下至少一项:终端设备的服务小区是否支持需求切片的第一指示;需求切片对应的DC配置;需求切片对应的CA配置;需求切片对应的CA的激活或去激活指示;需求切片对应的DC的激活或去激活指示;终端设备需要进行小区切换的第二指示;终端设备需要进行小区重定向的第三指示。
可选地,上述条件可以是终端设备的服务小区或者服务小区的频点不能同时支持终端设备的当前业务和需求切片对应的业务,和/或,需求切片对应的业务的优先级高于当前业务的优先级,和/或,需求切片的优先级不低于终端设备当前配置、服务或者建立的切片的优先级。。
需要说明的是,在本申请中,网络设备确定和/或发送以下至少一项:终端设备的服务小区是否支持需求切片的第一指示;需求切片对应的DC配置;需求切片对应的CA配置;需求切片对应的CA的激活或去激活指示;需求切片对应的DC的激活或去激活指示;终端设备需要进行小区切换的第二指示;终端设备需要进行小区重定向的第三指示。可以是独立执行的,即解耦合执行的,例如:网络设备不需要首先判断终端设备的服务小区是否支持需求切片,再确定需求切片对应的DC配置、CA配置、小区切换或者小区重定向。再例如:网络设备不需要先确定是否向终端设备提供DC和/或CA配置,当确定不提供DC和/或CA配置时,再确定是否进行小区重定向或者小区切换。
综上,在本申请中,给出了在连接态的终端设备当前配置了切片的情况下,当终端设备获取到需求切片的信息时,终端设备的处理方法,即终端设备可以向网络设备发送指示信息。进一步地,网络设备可以根据指示信息所指示的需求切片的信息确定和/或发送以下至少一项:终端设备的服务小区是否支持需求切片的第一指示;需求切片对应的DC配置;需求切片对应的CA配置;需求切片对应的CA的激活或去激活指示;需求切片对应的DC的激活或去激活指示;终端设备需要进行小区切换的第二指示;终端设备需要进行小区重定向的第三指示。从而可以保证需求切片对应的业务传输。
上文结合图2至图3,详细描述了本申请的方法实施例,下文结合图4至图9,详细描述本申请的装置实施例,应理解,装置实施例与方法实施例相互对应,类似的描述可以参照方法实施例。
图4示出了根据本申请实施例的终端设备400的示意性框图。如图4所示,该终端设备400,包括:处理单元410,用于:获取指示信息,指示信息用于指示需求切片的信息。根据需求切片的信息进行小区重选或者确定是否在终端设备的服务小区触发连接建立过程。
可选地,指示信息是由终端设备的NAS生成,并发送给终端设备的AS的;或者,
指示信息是由核心网设备通过NAS消息发送给终端设备的;或者,
指示信息是由网络设备发送给终端设备的。
可选地,指示信息携带在寻呼消息中。
可选地,指示信息是在需求切片的优先级高于终端设备当前配置、服务或者建立的切片的优先级时发送的。
可选地,指示信息是在服务请求过程、PDU会话建立请求过程、寻呼过程或者PDU会话调整请求过程中发送的。或者,指示信息是在业务到达时发送的。
可选地,指示信息携带在原因值中。
可选地,原因值为以下任一项:RRC建立原因、RRC重建原因、小区重选原因。
可选地,终端设备处于非连接态。
可选地,处理单元410还用于:若终端设备正在执行小区重选过程,则中断小区重选过程。
可选地,处理单元410还用于:在重选后的小区触发连接建立过程。
可选地,处理单元410具体用于执行以下至少一项:若根据需求切片的信息确定需求切片对应的小区是服务小区,则确定在终端设备的服务小区触发连接建立过程。若根据需求切片的信息确定需求切片对应的小区不是服务小区,则确定不在终端设备的服务小区触发连接建立过程。若终端设备根据需求切片的信息确定需求切片对应的小区不是服务小区,则确定在终端设备的服务小区触发连接建立过程,并仅进行紧急业务传输。
可选地,处理单元410具体用于:若终端设备的服务小区或者服务小区的频点不能同时支持终端设备的当前业务和需求切片对应的业务,和/或,需求切片对应的业务的优先级高于当前业务的优先级,则根据需求切片的信息进行小区重选或者确定是否在终端设备的服务小区触发连接建立过程。
可选地,需求切片的信息包括以下至少一项:需求切片的标识,需求切片的优先级,需求切片对应的频点信息,需求切片对应的小区信息。
可选地,频点信息包括:频点标识和/或频点优先级。
可选地,在一些实施例中,上述通信单元可以是通信接口或收发器,或者是通信芯片或者片上系统的输入输出接口。
应理解,根据本申请实施例的终端设备400可对应于图2对应的方法实施例中的终端设备,并且终端设备400中的各个单元的上述和其它操作和/或功能分别为了实现上述图2对应的方法实施例中终端设备的相应流程,为了简洁,在此不再赘述。
图5示出了根据本申请实施例的终端设备500的示意性框图。如图5所示,该终端设备500,包括:
处理单元510,用于获取指示信息,指示信息用于指示需求切片的信息。
通信单元520,用于向网络设备发送指示信息。
可选地,指示信息是由终端设备的NAS生成,并发送给终端设备的AS的。或者,指示信息是由核心网设备通过NAS消息发送给终端设备的。
可选地,指示信息是在需求切片的优先级高于终端设备当前配置、服务或者建立的切片的优先级时发送的。
可选地,指示信息是在服务请求过程、PDU会话建立请求过程、寻呼过程或者PDU会话调整请求过程中发送的。或者,指示信息是在业务到达时发送的。
可选地,指示信息携带在原因值中。
可选地,原因值为以下任一项:RRC建立原因、RRC重建原因、小区重选原因。
可选地,指示信息携带在专用消息中。
可选地,专用消息为以下任一项:RRC消息、MAC CE、UCI。
可选地,指示信息还包括第一信息。其中,第一信息用于请求以下至少一项:进行小区切换。建立载波聚合CA。建立双连接DC。进行小区重定向。
可选地,通信单元520还用于:向网络设备发送能力指示信息。其中,能力指示信息用于指示用于指示以下至少一项:
终端设备是否支持CA。
终端设备是否支持DC。
终端设备支持的频点。
终端设备支持的带宽。
终端设备支持的带宽组合或列表。
支持的切片对应的频点组合或列表。
支持的切片对应的带宽组合或列表。
支持的切片对应的载波组合或列表。
可选地,通信单元520还用于接收以下至少一项:
终端设备的服务小区是否支持需求切片的第一指示。
需求切片对应的DC配置。
需求切片对应的DC的激活或去激活指示。
需求切片对应的CA配置。
需求切片对应的CA的激活或去激活指示。
终端设备需要进行小区切换的第二指示。
终端设备需要进行小区重定向的第三指示。
可选地,处理单元510还用于:若第一指示指示终端设备的服务小区支持需求切片,则在服务小区进行需求切片的业务传输。
可选地,处理单元510还用于:根据DC配置、需求切片对应的DC的激活或去激活指示、CA配置和需求切片对应的CA的激活或去激活指示中的至少一项进行需求切片的业务传输。
可选地,处理单元510具体用于:若根据DC配置、需求切片对应的DC的激活或去激活指示、CA配置和需求切片对应的CA的激活或去激活指示中的至少一项确定的至少一个小区支持需求切片,则在至少一个小区上的一个小区上进行需求切片的业务传输。
可选地,处理单元510具体用于:若根据DC配置、需求切片对应的DC的激活或去激活指示、CA配置和需求切片对应的CA的激活或去激活指示中的至少一项确定的至少一个小区支持需求切片和终端设备当前业务,则在至少一个小区的一个小区上同时进行需求切片的业务传输和当前业务的传输;或者,
若根据DC配置、需求切片对应的DC的激活或去激活指示、CA配置和需求切片对应的CA的激活或去激活指示中的至少一项确定的至少一个小区支持需求切片和终端设备当前业务,则在至少一个小区的至少两个小区上分别进行需求切片的业务传输和当前业务的传输。
可选地,处理单元510还用于:根据第二指示进行小区切换和/或进行需求切片的业务传输。
可选地,处理单元510还用于:根据第三指示进行小区重定向和/或进行需求切片的业务传输。
可选地,通信单元520具体用于:若终端设备的服务小区或者服务小区的频点不能同时支持终端设备的当前业务和需求切片对应的业务,和/或,需求切片对应的业务的优先级高于当前业务的优先级,则向网络设备发送指示信息。
可选地,终端设备处于连接态。
可选地,需求切片的信息包括以下至少一项:需求切片的标识,需求切片的优先级,需求切片对应的频点信息,需求切片对应的小区信息。
可选地,频点信息包括:频点标识和/或频点优先级。
可选地,在一些实施例中,上述通信单元可以是通信接口或收发器,或者是通信芯片或者片上系统的输入输出接口。
应理解,根据本申请实施例的终端设备500可对应于图3对应的方法实施例中的终端设备,并且终端设备500中的各个单元的上述和其它操作和/或功能分别为了实现上述图3对应的方法实施例中终端设备的相应流程,为了简洁,在此不再赘述。
图6示出了根据本申请实施例的网络设备600的示意性框图。如图6所示,该网络设备600包括:通信单元610和处理单元620。通信单元610用于接收指示信息,指示信息用于指示需求切片的信息。处理单元620用于根据需求切片的信息确定以下至少一项,和/或,通信单元610用于发送以下至少一项:
终端设备的服务小区是否支持需求切片的第一指示。
需求切片对应的DC配置。
需求切片对应的DC的激活或去激活指示。
需求切片对应的CA配置。
需求切片对应的CA的激活或去激活指示。
终端设备需要进行小区切换的第二指示。
终端设备需要进行小区重定向的第三指示。
可选地,指示信息来自于终端设备。
可选地,指示信息是由终端设备的NAS生成,并发送给终端设备的AS的。或者,指示信息是由核心网设备通过NAS消息发送给终端设备的。
可选地,指示信息是在需求切片的优先级高于终端设备当前配置、服务或者建立的切片的优先级时发送的。
可选地,指示信息是在服务请求过程、PDU会话建立请求过程、寻呼过程或者PDU会话调整请求过程中发送的。或者,指示信息是在业务到达时发送的。
可选地,指示信息携带在原因值中。
可选地,原因值为以下任一项:RRC建立原因、RRC重建原因、小区重选原因。
可选地,指示信息携带在专用消息中。
可选地,专用消息为以下任一项:RRC消息、MAC CE、UCI。
可选地,指示信息来自于应用服务器。
可选地,示信息还包括第一信息。其中,第一信息用于请求以下至少一项:进行小区切换。建立CA。建立DC。进行小区重定向。
可选地,通信单元610还用于:向终端设备发送能力指示信息。其中,能力指示信息用于指示用于指示以下至少一项:
终端设备是否支持CA。
终端设备是否支持DC。
终端设备支持的频点。
终端设备支持的带宽。
终端设备支持的带宽组合或列表。
支持的切片对应的频点组合或列表。
支持的切片对应的带宽组合或列表。
支持的切片对应的载波组合或列表。
可选地,需求切片的信息包括以下至少一项:需求切片的标识,需求切片的优先级,需求切片对应的频点信息,需求切片对应的小区信息。
可选地,频点信息包括:频点标识和/或频点优先级。
可选地,处理单元620具体用于:根据需求切片的优先级和终端设备当前配置的切片的优先级,确定是否需要支持需求切片。
可选地,处理单元620还用于:若需求切片的优先级高于当前配置的切片的优先级,则确定需要支持需求切片。若需求切片的优先级低于或等于当前配置的切片的优先级,则确定不需要支持需求切片。
可选地,处理单元620具体用于:根据需求切片的信息和服务小区支持的切片的信息,确定需求切片对应的DC配置、需求切片对应的DC的激活或去激活指示、CA配置、需求切片对应的CA的激活或去激活指示、进行小区切换和进行小区重定向中的至少一项。
可选地,处理单元620具体用于:若终端设备的服务小区或者服务小区的频点不能同时支持终端设备的当前业务和需求切片对应的业务,和/或,需求切片对应的业务的优先级高于当前业务的优先级,则根据指示信息确定至少一项。和/或,通信单元610具体用于:若终端设备的服务小区或者服务小区的频点不能同时支持终端设备的当前业务和需求切片对应的业务,和/或,需求切片对应的业务的优先级高于当前业务的优先级,则根据指示信息发送至少一项。
可选地,终端设备处于连接态。
可选地,在一些实施例中,上述通信单元可以是通信接口或收发器,或者是通信芯片或者片上系统的输入输出接口。
应理解,根据本申请实施例的网络设备600可对应于图2对应的方法实施例中的网络设备,并且网络设备600中的各个单元的上述和其它操作和/或功能分别为了实现上述图2对应的方法实施例中网络设备的相应流程,为了简洁,在此不再赘述。
图7是本申请实施例提供的一种通信设备700示意性结构图。图7所示的通信设备700包括处理器710,处理器710可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
可选地,如图7所示,通信设备700还可以包括存储器720。其中,处理器710可以从存储器720中调用并运行计算机程序,以实现本申请实施例中的方法。
其中,存储器720可以是独立于处理器710的一个单独的器件,也可以集成在处理器710中。
可选地,如图7所示,通信设备700还可以包括收发器730,处理器710可以控制该收发器730与其他设备进行通信,具体地,可以向其他设备发送信息或数据,或接收其他设备发送的信息或数据。
其中,收发器730可以包括发射机和接收机。收发器730还可以进一步包括天线,天线的数量可以为一个或多个。
可选地,该通信设备700具体可为本申请实施例的网络设备,并且该通信设备700可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该通信设备700具体可为本申请实施例的终端设备,并且该通信设备700可以实现本申请实施例的各个方法中由终端设备实现的相应流程,为了简洁,在此不再赘述。
图8是本申请实施例的装置的示意性结构图。图8所示的装置800包括处理器810,处理器810可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
可选地,如图8所示,装置800还可以包括存储器820。其中,处理器810可以从存储器820中调用并运行计算机程序,以实现本申请实施例中的方法。
其中,存储器820可以是独立于处理器810的一个单独的器件,也可以集成在处理器810中。
可选地,该装置800还可以包括输入接口830。其中,处理器810可以控制该输入接口830与其他设备或芯片进行通信,具体地,可以获取其他设备或芯片发送的信息或数据。
可选地,该装置800还可以包括输出接口840。其中,处理器810可以控制该输出接口840与其他设备或芯片进行通信,具体地,可以向其他设备或芯片输出信息或数据。
可选地,该装置可应用于本申请实施例中的网络设备,并且该装置可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该装置可应用于本申请实施例中的终端设备,并且该装置可以实现本申请实施例的各个方法中由终端设备实现的相应流程,为了简洁,在此不再赘述。
可选地,本申请实施例提到的装置也可以是芯片。例如可以是系统级芯片,系统芯片,芯片系统或片上系统芯片等。
图9是本申请实施例提供的一种通信系统900的示意性框图。如图9所示,该通信系统900包括终端设备910和网络设备920。
其中,该终端设备910可以用于实现上述方法中由终端设备实现的相应的功能,以及该网络设备920可以用于实现上述方法中由网络设备或者基站实现的相应的功能为了简洁,在此不再赘述。
应理解,本申请实施例的处理器可能是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(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 (123)

  1. 一种无线通信方法,其特征在于,包括:
    终端设备获取指示信息,所述指示信息用于指示需求切片的信息;
    所述终端设备根据所述需求切片的信息进行小区重选或者确定是否在所述终端设备的服务小区触发连接建立过程。
  2. 根据权利要求1所述的方法,其特征在于,
    所述指示信息是由所述终端设备的非接入层NAS生成,并发送给所述终端设备的接入层AS的;或者,
    所述指示信息是由核心网设备通过NAS消息发送给所述终端设备的;或者,
    所述指示信息是由网络设备发送给所述终端设备的。
  3. 根据权利要求2所述的方法,其特征在于,所述指示信息携带在寻呼消息中。
  4. 根据权利要求2或3所述的方法,其特征在于,所述指示信息是在所述需求切片的优先级高于所述终端设备当前配置、服务或者建立的切片的优先级时发送的。
  5. 根据权利要求1-4任一项所述的方法,其特征在于,
    所述指示信息是在服务请求过程、分组数据单元PDU会话建立请求过程、寻呼过程或者PDU会话调整请求过程中发送的;或者,
    所述指示信息是在业务到达时发送的。
  6. 根据权利要求1-5任一项所述的方法,其特征在于,所述指示信息携带在原因值中。
  7. 根据权利要求6所述的方法,其特征在于,所述原因值为以下任一项:无线资源控制RRC建立原因、RRC重建原因、小区重选原因。
  8. 根据权利要求1-7任一项所述的方法,其特征在于,所述终端设备处于非连接态。
  9. 根据权利要求1-8任一项所述的方法,其特征在于,所述终端设备根据所述需求切片的信息进行小区重选之前,还包括:
    若所述终端设备正在执行小区重选过程,则所述终端设备中断所述小区重选过程。
  10. 根据权利要求1-9任一项所述的方法,其特征在于,所述终端设备根据所述需求切片的信息进行小区重选之后,还包括:
    所述终端设备在重选后的小区触发连接建立过程。
  11. 根据权利要求1-10任一项所述的方法,其特征在于,所述终端设备根据所述需求切片的信息确定是否在所述终端设备的服务小区触发连接建立过程,包括以下至少之一:
    若所述终端设备根据所述需求切片的信息确定所述需求切片对应的小区是所述服务小区,则所述终端设备确定在所述终端设备的服务小区触发连接建立过程;
    若所述终端设备根据所述需求切片的信息确定所述需求切片对应的小区不是所述服务小区,则所述终端设备确定不在所述终端设备的服务小区触发连接建立过程;
    若所述终端设备根据所述需求切片的信息确定所述需求切片对应的小区不是所述服务小区,则所述终端设备确定在所述终端设备的服务小区触发连接建立过程,并仅进行紧急业务传输。
  12. 根据权利要求1-11任一项所述的方法,其特征在于,所述终端设备根据所述需求切片的信息进行小区重选或者确定是否在所述终端设备的服务小区触发连接建立过程,包括:
    若所述终端设备的服务小区或者所述服务小区的频点不能同时支持所述终端设备的当前业务和所述需求切片对应的业务,和/或,所述需求切片对应的业务的优先级高于所述当前业务的优先级,则所述终端设备根据所述需求切片的信息进行小区重选或者确定是否在所述终端设备的服务小区触发连接建立过程。
  13. 根据权利要求1-12任一项所述的方法,其特征在于,所述需求切片的信息包括以下至少一项:所述需求切片的标识,所述需求切片的优先级,所述需求切片对应的频点信息,所述需求切片对应的小区信息。
  14. 根据权利要求13所述的方法,其特征在于,所述频点信息包括:频点标识和/或频点优先级。
  15. 一种无线通信方法,其特征在于,包括:
    终端设备获取指示信息,所述指示信息用于指示需求切片的信息;
    所述终端设备向网络设备发送所述指示信息。
  16. 根据权利要求15所述的方法,其特征在于,
    所述指示信息是由所述终端设备的NAS生成,并发送给所述终端设备的AS的;或者,所述指示信息是由核心网设备通过NAS消息发送给所述终端设备的。
  17. 根据权利要求16所述的方法,其特征在于,所述指示信息是在所述需求切片的优先级高于 所述终端设备当前配置、服务或者建立的切片的优先级时发送的。
  18. 根据权利要求15-17任一项所述的方法,其特征在于,
    所述指示信息是在服务请求过程、PDU会话建立请求过程、寻呼过程或者PDU会话调整请求过程中发送的;或者,
    所述指示信息是在业务到达时发送的。
  19. 根据权利要求15-18任一项所述的方法,其特征在于,所述指示信息携带在原因值中。
  20. 根据权利要求19所述的方法,其特征在于,所述原因值为以下任一项:RRC建立原因、RRC重建原因、小区重选原因。
  21. 根据权利要求15所述的方法,其特征在于,所述指示信息携带在专用消息中。
  22. 根据权利要求21所述的方法,其特征在于,所述专用消息为以下任一项:RRC消息、媒体接入控制控制单元MAC CE、上行控制信息UCI。
  23. 根据权利要求15-22任一项所述的方法,其特征在于,所述指示信息还包括第一信息;其中,所述第一信息用于请求以下至少一项:
    进行小区切换;
    建立载波聚合CA;
    建立双连接DC;
    进行小区重定向。
  24. 根据权利要求15-23任一项所述的方法,其特征在于,还包括:
    所述终端设备向网络设备发送能力指示信息;
    其中,所述能力指示信息用于指示用于指示以下至少一项:
    所述终端设备是否支持CA;
    所述终端设备是否支持DC;
    所述终端设备支持的频点;
    所述终端设备支持的带宽;
    所述终端设备支持的带宽组合或列表;
    支持的切片对应的频点组合或列表;
    支持的切片对应的带宽组合或列表;
    支持的切片对应的载波组合或列表。
  25. 根据权利要求15-24任一项所述的方法,其特征在于,还包括:所述终端设备接收以下至少一项:
    所述终端设备的服务小区是否支持所述需求切片的第一指示;
    所述需求切片对应的DC配置;
    所述需求切片对应的DC的激活或去激活指示;
    所述需求切片对应的CA配置;
    所述需求切片对应的CA的激活或去激活指示;
    所述终端设备需要进行小区切换的第二指示;
    所述终端设备需要进行小区重定向的第三指示。
  26. 根据权利要求25所述的方法,其特征在于,还包括:
    若所述第一指示指示所述终端设备的服务小区支持所述需求切片,则所述终端设备在所述服务小区进行所述需求切片的业务传输。
  27. 根据权利要求25所述的方法,其特征在于,还包括:
    所述终端设备根据所述DC配置、所述需求切片对应的DC的激活或去激活指示、所述CA配置和所述需求切片对应的CA的激活或去激活指示中的至少一项进行所述需求切片的业务传输。
  28. 根据权利要求27所述的方法,其特征在于,所述终端设备根据所述DC配置、所述需求切片对应的DC的激活或去激活指示、所述CA配置和所述需求切片对应的CA的激活或去激活指示中的至少一项进行所述需求切片的业务传输,包括:
    若根据所述DC配置、所述需求切片对应的DC的激活或去激活指示、所述CA配置和所述需求切片对应的CA的激活或去激活指示中的至少一项确定的至少一个小区支持所述需求切片,则所述终端设备在所述至少一个小区上的一个小区上进行所述需求切片的业务传输。
  29. 根据权利要求27所述的方法,其特征在于,所述终端设备根据所述DC配置、所述需求切片对应的DC的激活或去激活指示、所述CA配置和所述需求切片对应的CA的激活或去激活指示中的至少一项进行所述需求切片的业务传输,包括:
    若根据所述DC配置、所述需求切片对应的DC的激活或去激活指示、所述CA配置和所述需求切片对应的CA的激活或去激活指示中的至少一项确定的至少一个小区支持所述需求切片和所述终端设备当前业务,则所述终端设备在所述至少一个小区的一个小区上同时进行所述需求切片的业务传输和所述当前业务的传输;或者,
    若根据所述DC配置、所述需求切片对应的DC的激活或去激活指示、所述CA配置和所述需求切片对应的CA的激活或去激活指示中的至少一项确定的至少一个小区支持所述需求切片和所述终端设备当前业务,则所述终端设备在所述至少一个小区的至少两个小区上分别进行所述需求切片的业务传输和所述当前业务的传输。
  30. 根据权利要求25所述的方法,其特征在于,还包括:
    所述终端设备根据所述第二指示进行小区切换和/或进行所述需求切片的业务传输。
  31. 根据权利要求25所述的方法,其特征在于,还包括:
    所述终端设备根据所述第三指示进行小区重定向和/或进行所述需求切片的业务传输。
  32. 根据权利要求15-31任一项所述的方法,其特征在于,所述终端设备向网络设备发送所述指示信息,包括:
    若所述终端设备的服务小区或者所述服务小区的频点不能同时支持所述终端设备的当前业务和所述需求切片对应的业务,和/或,所述需求切片对应的业务的优先级高于所述当前业务的优先级,则所述终端设备向网络设备发送所述指示信息。
  33. 根据权利要求15-32任一项所述的方法,其特征在于,所述终端设备处于连接态。
  34. 根据权利要求15-33任一项所述的方法,其特征在于,所述需求切片的信息包括以下至少一项:所述需求切片的标识,所述需求切片的优先级,所述需求切片对应的频点信息,所述需求切片对应的小区信息。
  35. 根据权利要求34所述的方法,其特征在于,所述频点信息包括:频点标识和/或频点优先级。
  36. 一种无线通信方法,其特征在于,包括:
    网络设备接收指示信息,所述指示信息用于指示需求切片的信息;
    所述网络设备根据所述需求切片的信息确定和/或发送以下至少一项:
    所述终端设备的服务小区是否支持所述需求切片的第一指示;
    所述需求切片对应的DC配置;
    所述需求切片对应的DC的激活或去激活指示;
    所述需求切片对应的CA配置;
    所述需求切片对应的CA的激活或去激活指示;
    所述终端设备需要进行小区切换的第二指示;
    所述终端设备需要进行小区重定向的第三指示。
  37. 根据权利要求36所述的方法,其特征在于,所述指示信息来自于终端设备。
  38. 根据权利要求37所述的方法,其特征在于,所述指示信息是由所述终端设备的NAS生成,并发送给所述终端设备的AS的;或者,所述指示信息是由核心网设备通过NAS消息发送给所述终端设备的。
  39. 根据权利要求38所述的方法,其特征在于,所述指示信息是在所述需求切片的优先级高于所述终端设备当前配置、服务或者建立的切片的优先级时发送的。
  40. 根据权利要求36-39任一项所述的方法,其特征在于,
    所述指示信息是在服务请求过程、PDU会话建立请求过程、寻呼过程或者PDU会话调整请求过程中发送的;或者,
    所述指示信息是在业务到达时发送的。
  41. 根据权利要求36-40任一项所述的方法,其特征在于,所述指示信息携带在原因值中。
  42. 根据权利要求41所述的方法,其特征在于,所述原因值为以下任一项:RRC建立原因、RRC重建原因、小区重选原因。
  43. 根据权利要求36或37所述的方法,其特征在于,所述指示信息携带在专用消息中。
  44. 根据权利要求43所述的方法,其特征在于,所述专用消息为以下任一项:RRC消息、MAC CE、UCI。
  45. 根据权利要求36所述的方法,其特征在于,所述指示信息来自于应用服务器。
  46. 根据权利要求36-45任一项所述的方法,其特征在于,所述指示信息还包括第一信息;其中,所述第一信息用于请求以下至少一项:
    进行小区切换;
    建立CA;
    建立DC;
    进行小区重定向。
  47. 根据权利要求36-46任一项所述的方法,其特征在于,还包括:
    所述网络设备向所述终端设备发送能力指示信息;
    其中,所述能力指示信息用于指示用于指示以下至少一项:
    所述终端设备是否支持CA;
    所述终端设备是否支持DC;
    所述终端设备支持的频点;
    所述终端设备支持的带宽;
    所述终端设备支持的带宽组合或列表;
    支持的切片对应的频点组合或列表;
    支持的切片对应的带宽组合或列表;
    支持的切片对应的载波组合或列表。
  48. 根据权利要求36-47任一项所述的方法,其特征在于,所述需求切片的信息包括以下至少一项:所述需求切片的标识,所述需求切片的优先级,所述需求切片对应的频点信息,所述需求切片对应的小区信息。
  49. 根据权利要求48所述的方法,其特征在于,所述频点信息包括:频点标识和/或频点优先级。
  50. 根据权利要求48或49所述的方法,其特征在于,还包括:
    所述网络设备根据所述所述需求切片的优先级和所述终端设备当前配置的切片的优先级,确定是否需要支持所述需求切片。
  51. 根据权利要求50所述的方法,其特征在于,所述网络设备根据所述所述需求切片的优先级和当前配置的切片的优先级,确定是否需要支持所述需求切片,包括:
    若所述需求切片的优先级高于所述当前配置的切片的优先级,则所述网络设备确定需要支持所述需求切片;
    若所述需求切片的优先级低于或等于所述当前配置的切片的优先级,则所述网络设备确定不需要支持所述需求切片。
  52. 根据权利要求36-51任一项所述的方法,其特征在于,所述网络设备根据所述需求切片的信息确定所述需求切片对应的DC配置、所述需求切片对应的DC的激活或去激活指示、CA配置、所述需求切片对应的CA的激活或去激活指示、进行小区切换和进行小区重定向中的至少一项,包括:
    所述网络设备根据所述需求切片的信息和所述服务小区支持的切片的信息,确定所述需求切片对应的DC配置、所述需求切片对应的DC的激活或去激活指示、CA配置、所述需求切片对应的CA的激活或去激活指示、进行小区切换和进行小区重定向中的至少一项。
  53. 根据权利要求36-52任一项所述的方法,其特征在于,所述网络设备根据所述指示信息确定和/或发送所述至少一项,包括:
    若所述终端设备的服务小区或者所述服务小区的频点不能同时支持所述终端设备的当前业务和所述需求切片对应的业务,和/或,所述需求切片对应的业务的优先级高于所述当前业务的优先级,则所述网络设备根据所述指示信息确定和/或发送所述至少一项。
  54. 根据权利要求36-53任一项所述的方法,其特征在于,所述终端设备处于连接态。
  55. 一种终端设备,其特征在于,包括:处理单元,用于:
    获取指示信息,所述指示信息用于指示需求切片的信息;
    根据所述需求切片的信息进行小区重选或者确定是否在所述终端设备的服务小区触发连接建立过程。
  56. 根据权利要求55所述的终端设备,其特征在于,
    所述指示信息是由所述终端设备的NAS生成,并发送给所述终端设备的AS的;或者,
    所述指示信息是由核心网设备通过NAS消息发送给所述终端设备的;或者,
    所述指示信息是由网络设备发送给所述终端设备的。
  57. 根据权利要求56所述的终端设备,其特征在于,所述指示信息携带在寻呼消息中。
  58. 根据权利要求56或57所述的终端设备,其特征在于,所述指示信息是在所述需求切片的优先级高于所述终端设备当前配置、服务或者建立的切片的优先级时发送的。
  59. 根据权利要求55-58任一项所述的终端设备,其特征在于,
    所述指示信息是在服务请求过程、PDU会话建立请求过程、寻呼过程或者PDU会话调整请求过 程中发送的;或者,
    所述指示信息是在业务到达时发送的。
  60. 根据权利要求55-59任一项所述的终端设备,其特征在于,所述指示信息携带在原因值中。
  61. 根据权利要求60所述的终端设备,其特征在于,所述原因值为以下任一项:RRC建立原因、RRC重建原因、小区重选原因。
  62. 根据权利要求55-61任一项所述的终端设备,其特征在于,所述终端设备处于非连接态。
  63. 根据权利要求55-62任一项所述的终端设备,其特征在于,所述处理单元还用于:
    若所述终端设备正在执行小区重选过程,则中断所述小区重选过程。
  64. 根据权利要求55-63任一项所述的终端设备,其特征在于,所述处理单元还用于:在重选后的小区触发连接建立过程。
  65. 根据权利要求55-64任一项所述的终端设备,其特征在于,所述处理单元具体用于执行以下至少一项:
    若根据所述需求切片的信息确定所述需求切片对应的小区是所述服务小区,则确定在所述终端设备的服务小区触发连接建立过程;
    若根据所述需求切片的信息确定所述需求切片对应的小区不是所述服务小区,则确定不在所述终端设备的服务小区触发连接建立过程;
    若所述终端设备根据所述需求切片的信息确定所述需求切片对应的小区不是所述服务小区,则确定在所述终端设备的服务小区触发连接建立过程,并仅进行紧急业务传输。
  66. 根据权利要求55-65任一项所述的终端设备,其特征在于,所述处理单元具体用于:
    若所述终端设备的服务小区或者所述服务小区的频点不能同时支持所述终端设备的当前业务和所述需求切片对应的业务,和/或,所述需求切片对应的业务的优先级高于所述当前业务的优先级,则根据所述需求切片的信息进行小区重选或者确定是否在所述终端设备的服务小区触发连接建立过程。
  67. 根据权利要求55-66任一项所述的终端设备,其特征在于,所述需求切片的信息包括以下至少一项:所述需求切片的标识,所述需求切片的优先级,所述需求切片对应的频点信息,所述需求切片对应的小区信息。
  68. 根据权利要求67所述的终端设备,其特征在于,所述频点信息包括:频点标识和/或频点优先级。
  69. 一种终端设备,其特征在于,包括:
    处理单元,用于获取指示信息,所述指示信息用于指示需求切片的信息;
    通信单元,用于向网络设备发送所述指示信息。
  70. 根据权利要求69所述的终端设备,其特征在于,
    所述指示信息是由所述终端设备的NAS生成,并发送给所述终端设备的AS的;或者,所述指示信息是由核心网设备通过NAS消息发送给所述终端设备的。
  71. 根据权利要求70所述的终端设备,其特征在于,所述指示信息是在所述需求切片的优先级高于所述终端设备当前配置、服务或者建立的切片的优先级时发送的。
  72. 根据权利要求69-71任一项所述的终端设备,其特征在于,
    所述指示信息是在服务请求过程、PDU会话建立请求过程、寻呼过程或者PDU会话调整请求过程中发送的;或者,
    所述指示信息是在业务到达时发送的。
  73. 根据权利要求69-72任一项所述的终端设备,其特征在于,所述指示信息携带在原因值中。
  74. 根据权利要求73所述的终端设备,其特征在于,所述原因值为以下任一项:RRC建立原因、RRC重建原因、小区重选原因。
  75. 根据权利要求69所述的终端设备,其特征在于,所述指示信息携带在专用消息中。
  76. 根据权利要求75所述的终端设备,其特征在于,所述专用消息为以下任一项:RRC消息、MAC CE、UCI。
  77. 根据权利要求69-76任一项所述的终端设备,其特征在于,所述指示信息还包括第一信息;其中,所述第一信息用于请求以下至少一项:
    进行小区切换;
    建立载波聚合CA;
    建立双连接DC;
    进行小区重定向。
  78. 根据权利要求69-77任一项所述的终端设备,其特征在于,所述通信单元还用于:向网络设备发送能力指示信息;
    其中,所述能力指示信息用于指示用于指示以下至少一项:
    所述终端设备是否支持CA;
    所述终端设备是否支持DC;
    所述终端设备支持的频点;
    所述终端设备支持的带宽;
    所述终端设备支持的带宽组合或列表;
    支持的切片对应的频点组合或列表;
    支持的切片对应的带宽组合或列表;
    支持的切片对应的载波组合或列表。
  79. 根据权利要求69-78任一项所述的终端设备,其特征在于,所述通信单元还用于接收以下至少一项:
    所述终端设备的服务小区是否支持所述需求切片的第一指示;
    所述需求切片对应的DC配置;
    所述需求切片对应的DC的激活或去激活指示;
    所述需求切片对应的CA配置;
    所述需求切片对应的CA的激活或去激活指示;
    所述终端设备需要进行小区切换的第二指示;
    所述终端设备需要进行小区重定向的第三指示。
  80. 根据权利要求79所述的终端设备,其特征在于,所述处理单元还用于:
    若所述第一指示指示所述终端设备的服务小区支持所述需求切片,则在所述服务小区进行所述需求切片的业务传输。
  81. 根据权利要求79所述的终端设备,其特征在于,所述处理单元还用于:
    根据所述DC配置、所述需求切片对应的DC的激活或去激活指示、所述CA配置和所述需求切片对应的CA的激活或去激活指示中的至少一项进行所述需求切片的业务传输。
  82. 根据权利要求81所述的终端设备,其特征在于,所述处理单元具体用于:
    若根据所述DC配置、所述需求切片对应的DC的激活或去激活指示、所述CA配置和所述需求切片对应的CA的激活或去激活指示中的至少一项确定的至少一个小区支持所述需求切片,则在所述至少一个小区上的一个小区上进行所述需求切片的业务传输。
  83. 根据权利要求81所述的终端设备,其特征在于,所述处理单元具体用于:
    若根据所述DC配置、所述需求切片对应的DC的激活或去激活指示、所述CA配置和所述需求切片对应的CA的激活或去激活指示中的至少一项确定的至少一个小区支持所述需求切片和所述终端设备当前业务,则在所述至少一个小区的一个小区上同时进行所述需求切片的业务传输和所述当前业务的传输;或者,
    若根据所述DC配置、所述需求切片对应的DC的激活或去激活指示、所述CA配置和所述需求切片对应的CA的激活或去激活指示中的至少一项确定的至少一个小区支持所述需求切片和所述终端设备当前业务,则在所述至少一个小区的至少两个小区上分别进行所述需求切片的业务传输和所述当前业务的传输。
  84. 根据权利要求79所述的终端设备,其特征在于,所述处理单元还用于:
    根据所述第二指示进行小区切换和/或进行所述需求切片的业务传输。
  85. 根据权利要求79所述的终端设备,其特征在于,所述处理单元还用于:
    根据所述第三指示进行小区重定向和/或进行所述需求切片的业务传输。
  86. 根据权利要求69-85任一项所述的终端设备,其特征在于,所述通信单元具体用于:
    若所述终端设备的服务小区或者所述服务小区的频点不能同时支持所述终端设备的当前业务和所述需求切片对应的业务,和/或,所述需求切片对应的业务的优先级高于所述当前业务的优先级,则向网络设备发送所述指示信息。
  87. 根据权利要求69-86任一项所述的终端设备,其特征在于,所述终端设备处于连接态。
  88. 根据权利要求69-87任一项所述的终端设备,其特征在于,所述需求切片的信息包括以下至少一项:所述需求切片的标识,所述需求切片的优先级,所述需求切片对应的频点信息,所述需求切片对应的小区信息。
  89. 根据权利要求88所述的终端设备,其特征在于,所述频点信息包括:频点标识和/或频点优 先级。
  90. 一种网络设备,其特征在于,包括:通信单元和处理单元;
    所述通信单元用于接收指示信息,所述指示信息用于指示需求切片的信息;
    所述处理单元用于根据所述需求切片的信息确定以下至少一项,和/或,所述通信单元用于发送以下至少一项:
    所述终端设备的服务小区是否支持所述需求切片的第一指示;
    所述需求切片对应的DC配置;
    所述需求切片对应的DC的激活或去激活指示;
    所述需求切片对应的CA配置;
    所述需求切片对应的CA的激活或去激活指示;
    所述终端设备需要进行小区切换的第二指示;
    所述终端设备需要进行小区重定向的第三指示。
  91. 根据权利要求90所述的网络设备,其特征在于,所述指示信息来自于终端设备。
  92. 根据权利要求91所述的网络设备,其特征在于,所述指示信息是由所述终端设备的NAS生成,并发送给所述终端设备的AS的;或者,所述指示信息是由核心网设备通过NAS消息发送给所述终端设备的。
  93. 根据权利要求92所述的网络设备,其特征在于,所述指示信息是在所述需求切片的优先级高于所述终端设备当前配置、服务或者建立的切片的优先级时发送的。
  94. 根据权利要求90-93任一项所述的网络设备,其特征在于,
    所述指示信息是在服务请求过程、PDU会话建立请求过程、寻呼过程或者PDU会话调整请求过程中发送的;或者,
    所述指示信息是在业务到达时发送的。
  95. 根据权利要求90-94任一项所述的网络设备,其特征在于,所述指示信息携带在原因值中。
  96. 根据权利要求95所述的网络设备,其特征在于,所述原因值为以下任一项:RRC建立原因、RRC重建原因、小区重选原因。
  97. 根据权利要求90或91所述的网络设备,其特征在于,所述指示信息携带在专用消息中。
  98. 根据权利要求97所述的网络设备,其特征在于,所述专用消息为以下任一项:RRC消息、MAC CE、UCI。
  99. 根据权利要求90所述的网络设备,其特征在于,所述指示信息来自于应用服务器。
  100. 根据权利要求90-99任一项所述的网络设备,其特征在于,所述指示信息还包括第一信息;其中,所述第一信息用于请求以下至少一项:
    进行小区切换;
    建立CA;
    建立DC;
    进行小区重定向。
  101. 根据权利要求90-100任一项所述的网络设备,其特征在于,所述通信单元还用于:向所述终端设备发送能力指示信息;
    其中,所述能力指示信息用于指示用于指示以下至少一项:
    所述终端设备是否支持CA;
    所述终端设备是否支持DC;
    所述终端设备支持的频点;
    所述终端设备支持的带宽;
    所述终端设备支持的带宽组合或列表;
    支持的切片对应的频点组合或列表;
    支持的切片对应的带宽组合或列表;
    支持的切片对应的载波组合或列表。
  102. 根据权利要求90-101任一项所述的网络设备,其特征在于,所述需求切片的信息包括以下至少一项:所述需求切片的标识,所述需求切片的优先级,所述需求切片对应的频点信息,所述需求切片对应的小区信息。
  103. 根据权利要求102所述的网络设备,其特征在于,所述频点信息包括:频点标识和/或频点优先级。
  104. 根据权利要求102或103所述的网络设备,其特征在于,所述处理单元具体用于:根据所 述所述需求切片的优先级和所述终端设备当前配置的切片的优先级,确定是否需要支持所述需求切片。
  105. 根据权利要求104所述的网络设备,其特征在于,所述处理单元还用于:
    若所述需求切片的优先级高于所述当前配置的切片的优先级,则确定需要支持所述需求切片;
    若所述需求切片的优先级低于或等于所述当前配置的切片的优先级,则确定不需要支持所述需求切片。
  106. 根据权利要求90-105任一项所述的网络设备,其特征在于,所述处理单元具体用于:
    根据所述需求切片的信息和所述服务小区支持的切片的信息,确定所述需求切片对应的DC配置、所述需求切片对应的DC的激活或去激活指示、CA配置、所述需求切片对应的CA的激活或去激活指示、进行小区切换和进行小区重定向中的至少一项。
  107. 根据权利要求90-106任一项所述的网络设备,其特征在于,所述处理单元具体用于:
    若所述终端设备的服务小区或者所述服务小区的频点不能同时支持所述终端设备的当前业务和所述需求切片对应的业务,和/或,所述需求切片对应的业务的优先级高于所述当前业务的优先级,则根据所述指示信息确定所述至少一项;
    和/或,所述通信单元具体用于:
    若所述终端设备的服务小区或者所述服务小区的频点不能同时支持所述终端设备的当前业务和所述需求切片对应的业务,和/或,所述需求切片对应的业务的优先级高于所述当前业务的优先级,则根据所述指示信息发送所述至少一项。
  108. 根据权利要求90-107任一项所述的网络设备,其特征在于,所述终端设备处于连接态。
  109. 一种终端设备,其特征在于,包括:处理器和存储器,该存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,执行如权利要求1至14中任一项所述的方法。
  110. 一种终端设备,其特征在于,包括:处理器和存储器,该存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,执行如权利要求15至35中任一项所述的方法。
  111. 一种网络设备,其特征在于,包括:处理器和存储器,该存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,执行如权利要求36至54中任一项所述的方法。
  112. 一种芯片,其特征在于,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求1至14中任一项所述的方法。
  113. 一种芯片,其特征在于,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求15至35中任一项所述的方法。
  114. 一种芯片,其特征在于,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求36至54中任一项所述的方法。
  115. 一种计算机可读存储介质,其特征在于,用于存储计算机程序,所述计算机程序使得计算机执行如权利要求1至14中任一项所述的方法。
  116. 一种计算机可读存储介质,其特征在于,用于存储计算机程序,所述计算机程序使得计算机执行如权利要求15至35中任一项所述的方法。
  117. 一种计算机可读存储介质,其特征在于,用于存储计算机程序,所述计算机程序使得计算机执行如权利要求36至54中任一项所述的方法。
  118. 一种计算机程序产品,其特征在于,包括计算机程序指令,该计算机程序指令使得计算机执行如权利要求1至14中任一项所述的方法。
  119. 一种计算机程序产品,其特征在于,包括计算机程序指令,该计算机程序指令使得计算机执行如权利要求15至35中任一项所述的方法。
  120. 一种计算机程序产品,其特征在于,包括计算机程序指令,该计算机程序指令使得计算机执行如权利要求36至54中任一项所述的方法。
  121. 一种计算机程序,其特征在于,所述计算机程序使得计算机执行如权利要求1至14中任一项所述的方法。
  122. 一种计算机程序,其特征在于,所述计算机程序使得计算机执行如权利要求15至35中任一项所述的方法。
  123. 一种计算机程序,其特征在于,所述计算机程序使得计算机执行如权利要求36至54中任一项所述的方法。
PCT/CN2020/109883 2020-08-18 2020-08-18 无线通信方法、终端设备和网络设备 WO2022036568A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
JP2023511870A JP2023545345A (ja) 2020-08-18 2020-08-18 無線通信方法、端末デバイス及びネットワークデバイス
CN202310494085.2A CN116437403A (zh) 2020-08-18 2020-08-18 无线通信方法、终端设备和网络设备
EP20949780.9A EP4203551A4 (en) 2020-08-18 2020-08-18 WIRELESS COMMUNICATION METHOD, TERMINAL DEVICE AND NETWORK DEVICE
KR1020237006634A KR20230052904A (ko) 2020-08-18 2020-08-18 무선 통신 방법, 단말 디바이스 및 네트워크 디바이스
CN202080102263.7A CN115918152A (zh) 2020-08-18 2020-08-18 无线通信方法、终端设备和网络设备
PCT/CN2020/109883 WO2022036568A1 (zh) 2020-08-18 2020-08-18 无线通信方法、终端设备和网络设备
US18/089,490 US20230209416A1 (en) 2020-08-18 2022-12-27 Wireless communication method, terminal device, and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/109883 WO2022036568A1 (zh) 2020-08-18 2020-08-18 无线通信方法、终端设备和网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/089,490 Continuation US20230209416A1 (en) 2020-08-18 2022-12-27 Wireless communication method, terminal device, and network device

Publications (1)

Publication Number Publication Date
WO2022036568A1 true WO2022036568A1 (zh) 2022-02-24

Family

ID=80322394

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/109883 WO2022036568A1 (zh) 2020-08-18 2020-08-18 无线通信方法、终端设备和网络设备

Country Status (6)

Country Link
US (1) US20230209416A1 (zh)
EP (1) EP4203551A4 (zh)
JP (1) JP2023545345A (zh)
KR (1) KR20230052904A (zh)
CN (2) CN116437403A (zh)
WO (1) WO2022036568A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023174321A1 (zh) * 2022-03-16 2023-09-21 维沃移动通信有限公司 语音业务的实现方法、装置及终端
WO2024019565A1 (ko) * 2022-07-22 2024-01-25 삼성전자 주식회사 무선 통신 시스템에서 페이징 메시지를 이용한 슬라이스 기반 셀 재선택 방법 및 장치

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107223350A (zh) * 2017-04-26 2017-09-29 北京小米移动软件有限公司 小区选择或重选方法、装置及系统
CN110248353A (zh) * 2018-03-07 2019-09-17 电信科学技术研究院有限公司 一种网络切片处理方法及设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7150831B2 (ja) * 2017-09-28 2022-10-11 テレフオンアクチーボラゲット エルエム エリクソン(パブル) スライス可用性に基づく周波数又は無線アクセス技術(rat)選択

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107223350A (zh) * 2017-04-26 2017-09-29 北京小米移动软件有限公司 小区选择或重选方法、装置及系统
CN110248353A (zh) * 2018-03-07 2019-09-17 电信科学技术研究院有限公司 一种网络切片处理方法及设备

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Slicing based cell (re)selection", 3GPP DRAFT; R2-2006951, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. E-Meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911810 *
QUALCOMM INCORPORATED: "Discussion on RAN slicing enhancement", 3GPP DRAFT; R2-2006767, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911674 *
SAMSUNG, AT&T, SPRINT, INTERDIGITAL, CHINA MOBILE, SK TELECOM, CONVIDA WIRELESS, ZTE, APPLE, KDDI: "Key Issue on 5GC assisted cell selection to access network slice", 3GPP DRAFT; S2-2001467, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Incheon, Korea; 20200113 - 20200117, 17 January 2020 (2020-01-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051844207 *
See also references of EP4203551A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023174321A1 (zh) * 2022-03-16 2023-09-21 维沃移动通信有限公司 语音业务的实现方法、装置及终端
WO2024019565A1 (ko) * 2022-07-22 2024-01-25 삼성전자 주식회사 무선 통신 시스템에서 페이징 메시지를 이용한 슬라이스 기반 셀 재선택 방법 및 장치

Also Published As

Publication number Publication date
EP4203551A4 (en) 2023-10-11
US20230209416A1 (en) 2023-06-29
JP2023545345A (ja) 2023-10-30
KR20230052904A (ko) 2023-04-20
CN116437403A (zh) 2023-07-14
CN115918152A (zh) 2023-04-04
EP4203551A1 (en) 2023-06-28

Similar Documents

Publication Publication Date Title
US11259346B2 (en) UE-to-network relay initiation and configuration
KR102666360B1 (ko) 무선 통신 방법, 단말 장치 및 네트워크 장치
US10595355B2 (en) Method and apparatus for establishing a connection in a wireless communication system
WO2020167205A1 (en) Early measurement reporting with rrc resume request message and indication of request for early measurements in association with paging
RU2771170C2 (ru) Способ и устройство представления отчета об информации о местоположении
US11356838B2 (en) Tracking area update in RRC_INACTIVE
WO2020187148A1 (zh) 寻呼监听方法、装置、系统及存储介质
CN115669070A (zh) 基于条件的辅节点或主辅小区变更方法及设备
US20160021649A1 (en) Bearer management for prose direct discovery
JPWO2019030938A1 (ja) 無線基地局及び無線通信方法
WO2019210521A1 (zh) 更新系统信息的方法、终端设备和网络设备
US20230209416A1 (en) Wireless communication method, terminal device, and network device
WO2020230019A1 (en) Idle/inactive measurement handling during radio resource control state transitions
WO2020164025A1 (zh) 状态转移的方法和设备
WO2022011618A1 (zh) 信息处理方法、终端设备和网络设备
US20230389110A1 (en) Terminal device, core network node, network device and method therein for facilitating paging procedure
JP2018507595A (ja) 無線装置、ネットワークノード、および、それらにおける方法
CN115150908A (zh) 一种寻呼方法及装置
WO2017111788A1 (en) Devices and methods of lwa power consumption reduction and rlf prevention
WO2022000311A1 (zh) 无线通信的方法、终端设备和网络设备
CN114830713B (zh) 控制辅小区组状态的方法和终端设备
WO2023202487A1 (zh) 一种寻呼方法、装置、芯片及模组设备
US20230262656A1 (en) Communications Method and Apparatus
WO2023124823A1 (zh) 一种通信方法及装置
WO2022147796A1 (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: 20949780

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023511870

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20237006634

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 202327018261

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020949780

Country of ref document: EP

Effective date: 20230320