WO2022188156A1 - 通信方法和通信装置 - Google Patents

通信方法和通信装置 Download PDF

Info

Publication number
WO2022188156A1
WO2022188156A1 PCT/CN2021/080479 CN2021080479W WO2022188156A1 WO 2022188156 A1 WO2022188156 A1 WO 2022188156A1 CN 2021080479 W CN2021080479 W CN 2021080479W WO 2022188156 A1 WO2022188156 A1 WO 2022188156A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
redcap
network element
terminal device
access
Prior art date
Application number
PCT/CN2021/080479
Other languages
English (en)
French (fr)
Inventor
潘奇
黄正磊
陈磊
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2021/080479 priority Critical patent/WO2022188156A1/zh
Priority to CN202180081172.4A priority patent/CN116569571A/zh
Priority to EP21929630.8A priority patent/EP4294059A4/en
Publication of WO2022188156A1 publication Critical patent/WO2022188156A1/zh
Priority to US18/461,905 priority patent/US20230413039A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of communication, and more particularly, to a communication method and a communication device.
  • 5G wireless technologies are primarily used to address a variety of use cases, which are categorized as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and large-scale Machine type communication (massive machine type communication, mMTC). Nonetheless, there are a few other use cases between these primary use cases, such as industrial sensor networks, video surveillance, and wearables.
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable and low-latency communication
  • mMTC massive machine type communication
  • mMTC massive machine type communication
  • REDCAP reduced capability
  • REDCAP terminals have lower cost and complexity, smaller form factor and longer battery life. For a REDCAP terminal, how to ensure that the terminal can only use corresponding use cases or services is a key issue currently faced.
  • the present application provides a communication method and a communication device, which are beneficial to ensure that a corresponding terminal device can only use its corresponding service.
  • a communication method comprising: a first network element acquiring first REDCAP information from a terminal device and second REDCAP information subscribed to by the terminal device, and according to the first REDCAP information and the second REDCAP information information to determine whether to allow the terminal device to use the service corresponding to the first REDCAP information.
  • the first network element is an access network device or a core network device.
  • the first network element can verify whether the REDCAP information (ie, the first REDCAP information) reported by the terminal device can be used through the REDCAP information (ie, the second REDCAP information) subscribed by the terminal device, thereby It is beneficial to ensure that the terminal device can only use its corresponding service.
  • the first REDCAP information is used to indicate the REDCAP access technology
  • the second information is used to indicate whether the terminal device subscribes to the REDCAP access technology
  • whether to allow the terminal device to use the service corresponding to the first REDCAP information refers to whether to allow the terminal device to establish a connection with the network through the REDCAP access technology.
  • the first network element can determine whether the terminal device can establish a connection with the network through the REDCAP access technology, thereby ensuring that the terminal device can only establish a connection with the network using the access technology it subscribes to.
  • the first REDCAP information is used to indicate the REDCAP access technology and the first service type, and the access technology used by the first service type is the REDCAP access technology
  • the second REDCAP information is used to indicate the REDCAP access technology and at least one service type, and the access technology used by the at least one service type is the REDCAP access technology.
  • whether to allow the terminal device to use the service corresponding to the first REDCAP information refers to whether to allow the terminal device to use the service of the first service type through the REDCAP access technology.
  • the first network element can determine whether the terminal device can use the service of the first service type through the REDCAP access technology, thereby ensuring that the terminal device can only be used for the service of the first service type under the REDCAP access technology .
  • the first REDCAP information is used to indicate a first type of REDCAP access technology
  • the second REDCAP information is used to indicate at least one type of REDCAP access technology
  • Different types of REDCAP access technologies correspond to different service types.
  • the first type of REDCAP access technology corresponds to the first service type.
  • whether to allow the terminal device to use the service corresponding to the first REDCAP information refers to whether to allow the terminal device to use the first type of REDCAP access technology, or whether to allow the terminal device to use the first type of REDCAP access technology. access technology to use the service of the first service type, or whether to allow the terminal device to use the service of the first service type.
  • the first network element can determine whether the terminal device can use the first type of REDCAP access technology, thereby ensuring that the terminal device can only use the first type of REDCAP access technology.
  • the first network element sends first indication information to the terminal device, where the first indication information is used to indicate that the terminal device is not allowed to use the information corresponding to the first REDCAP information service, or used to indicate that the terminal device cannot use the service corresponding to the first REDCAP information.
  • the first indication information includes a reason value, where the reason value is used to indicate the reason why the terminal device is rejected.
  • the first network element when the first network element is an access network device, the first network element obtains the first REDCAP information from the terminal device, including: the first network element The first network element receives the radio resource control (radio resource control, RRC) message from the terminal device, and the RRC message includes the first REDCAP information; or, the first network element receives the radio capability information from the terminal device, and according to the radio capability information to determine the first REDCAP information; or, the first network element receives a first message from an access and mobility management network element, where the first message includes the first REDCAP information; or, the first network element receives a message from the access and mobility management network element.
  • the wireless capability information of the terminal device of the entry and mobility management network element is determined, and the first REDCAP information is determined according to the wireless capability information.
  • the first network element can obtain the first REDCAP information.
  • the RRC message is an RRC connection establishment request message.
  • the first network element is an access network device in the second network during the handover process of the terminal device from the first network to the second network.
  • the first network may be a fourth generation (4th generation, 4G) or a long term evolution (long term evolution, LTE) network
  • the second network may be a fifth generation (5th generation, 5G) or a new radio (new radio) , NR) network.
  • acquiring the first REDCAP information from the terminal device by the first network element includes: the first network element receiving information from an access network device in the first network. wireless capability information of the terminal device; the first network element determines the first REDCAP information according to the wireless capability information.
  • the method further includes: the first network element receives the REDCAP indication information sent by the access and mobility management network element in the second network , the REDCAP indication information is used to instruct the first network element to determine the first REDCAP information according to the wireless capability information.
  • the first network element may determine the first REDCAP information according to the wireless capability information according to the indication of the access and mobility management network element in the second network.
  • the first network element acquiring the second REDCAP information subscribed by the terminal device includes: The management network element sends request information, the request information is used to request the access and mobility management network element to obtain the second REDCAP information from the unified data management network element; the first network element receives the second REDCAP information from the access and mobility management network element REDCAP information.
  • the access and mobility management network element is an access and mobility management network element in the second network.
  • the first network element is an access and mobility management network element.
  • acquiring the first REDCAP information by the first network element includes: the first network element receiving a non-access stratum (NAS) from the terminal device ) message, the NAS message includes the first REDCAP information; or, the first network element receives the first REDCAP information from the access network device.
  • NAS non-access stratum
  • the method before the first network element receives the first REDCAP information from the access network device, the method further includes: the first network element reports to the access network device Send the wireless capability information of the terminal device, where the wireless capability information is used by the access network device to determine the first REDCAP information.
  • the first network element is an access and mobility management network element in the second network during the handover process of the terminal device from the first network to the second network.
  • acquiring the first REDCAP information by the first network element includes: the first network element receiving the first REDCAP from the access network device in the second network information, the first REDCAP information is determined by the access network device in the second network according to the wireless capability information of the terminal device from the access network device in the first network.
  • the method before the first network element receives the first REDCAP information from the access network device in the second network, the method further includes: the first network element Send REDCAP indication information to the access network device in the second network, where the REDCAP indication information is used to instruct the access network device in the second network to determine the first REDCAP information according to the wireless capability information.
  • the first network element is a session management network element.
  • acquiring the first REDCAP information by the first network element includes: the first network element receiving the first REDCAP information from the access and mobility management network element.
  • obtaining the second REDCAP information by the first network element includes: the first network element sends request information to the unified data management network element according to the first REDCAP information, the The request information is used to request the second REDCAP information; the first network element receives the second REDCAP information from the unified data management network element.
  • the second REDCAP information is further used to indicate service feature information corresponding to the at least one service type.
  • the method further includes: the first network element sends third indication information to the terminal device, where the third indication information is used to indicate one of the following or Multiple: the terminal device saves the timing advance (TA) value used in the current RRC connection establishment process, and uses it when the next RRC connection is established; or, the terminal device reduces the frequency of neighbor cell measurement ; or, the terminal device saves the transmit power used in the current RRC connection establishment process, and uses it in the next RRC connection establishment.
  • TA timing advance
  • the first network element may send third indication information, and use the third indication information to Methods such as random access, radio resource management, or power control of the terminal device are optimized.
  • the method further includes: the first network element sends broadcast information, where the broadcast information includes the REDCAP access technology indication information and optimization indication information, and the optimization information indicates the Whether to instruct the terminal device whose access technology is the first radio access technology to enable the optimization function according to the optimization instruction information, the optimization function includes one or more of the following: saving the current RRC connection establishment process using TA value of the timing advance, and use it when the next RRC connection is established; or, reduce the frequency of neighbor cell measurement; use.
  • the first network element may send broadcast information, and the broadcast information can be used to communicate to the terminal device.
  • Methods such as random access, radio resource management or power control are optimized.
  • a communication method including: a terminal device sending first REDCAP information; the terminal device receiving indication information sent from a first network element according to the first REDCAP information, where the indication information is used to indicate whether to allow the terminal The device uses the service corresponding to the first REDCAP information.
  • the first network element can verify whether the first REDCAP information can be used through the subscribed REDCAP information of the terminal device, thereby helping to ensure that the terminal device can only use its corresponding service.
  • the method further includes: the terminal device sends, according to the indication information, adjusted REDCAP information, where the adjusted REDCAP information is different from the first REDCAP information.
  • sending the first REDCAP information by the terminal device includes: the terminal device sending wireless capability information, where the wireless capability information is used to determine the first REDCAP information.
  • the first network element is an access network device.
  • the method further includes: the terminal device receiving third indication information from the first network element, where the third indication information is used to indicate one of the following Item or items: the terminal device saves the timing advance TA value used in the current RRC connection establishment process, and uses it when the next RRC connection is established; or, the terminal device reduces the frequency of neighbor cell measurement; or, The terminal device saves the transmit power used in the current RRC connection establishment process, and uses it in the next RRC connection establishment.
  • the method further includes: the terminal device receives broadcast information from the first network element, where the broadcast information includes the REDCAP access technology indication information and optimization indication information , the optimization information indicates whether the terminal device whose access technology is the REDCAP access technology enables the optimization function according to the optimization instruction information, and the optimization function includes one or more of the following: save the current RRC connection establishment The timing advance TA value used in the process, and used in the next RRC connection establishment; or, reduce the frequency of neighbor cell measurement; or, save the transmit power used in the current RRC connection establishment process, and use it in the next Used when an RRC connection is established.
  • a communication system including: a first network element and a second network element; the second network element sends first REDCAP information of a terminal device to the first network element; the first network element according to the The first REDCAP information obtains the second REDCAP information subscribed by the terminal device; the first network element determines whether to allow the terminal device to use the corresponding first REDCAP information according to the first REDCAP information and the second REDCAP information Business.
  • the first network element can verify whether the first REDCAP information can be used through the subscribed REDCAP information of the terminal device, thereby helping to ensure that the terminal device can only use its corresponding service.
  • the second network element is an access and mobility management network element, and the first network element is an access network device; or, the second network element is access network equipment, and the first network element is an access and mobility management network element; or, the second network element is an access and mobility management network element, and the first network element is a session management network element; or, The second network element is an access network device in the first network during the handover process of the terminal device from the first network to the second network, and the first network element is an access network device in the second network.
  • the system further includes a unified data management network element; and the first network element acquires the second REDCAP subscribed by the terminal device according to the first REDCAP information
  • the information includes: the first network element obtains the second REDCAP information from the unified data management network element according to the first REDCAP information.
  • a communication apparatus comprising various modules or units for performing the method in any one of the first to second aspects or any possible implementation manners of the first to second aspects.
  • an apparatus including a processor.
  • the processor is coupled to the memory and is operable to execute instructions in the memory to cause the apparatus to perform the method of the first aspect to the second aspect or any one of the possible implementations of the first aspect to the second aspect.
  • the apparatus further includes a memory.
  • the apparatus further includes an interface circuit, and the processor is coupled to the interface circuit.
  • a processor including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor performs the method of the first aspect to the second aspect or any one of the possible implementations of the first aspect to the second aspect .
  • the above-mentioned processor may be a chip
  • the input circuit may be an input pin
  • the output circuit may be an output pin
  • the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver
  • the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter
  • the circuit can be the same circuit that acts as an input circuit and an output circuit at different times.
  • the embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.
  • a processing apparatus including a processor and a memory.
  • the processor is configured to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter, so as to execute any one of the first to second aspects or any possible implementation manner of the first to second aspects method in .
  • the processor is one or more, and the memory is one or more.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be separately set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting manner of the memory and the processor.
  • ROM read only memory
  • the processing device in the above seventh aspect may be a chip, and the processor may be implemented by hardware or software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented by software, the processor may be a logic circuit or an integrated circuit.
  • the processor can be a general-purpose processor, which is realized by reading software codes stored in a memory, and the memory can be integrated in the processor or located outside the processor and exist independently.
  • a computer program product comprising: a computer program (also referred to as code, or instructions), when the computer program is executed, the computer executes the first aspect, the second aspect, and the ninth aspect. or the method in any possible implementation manner of the first aspect to the second aspect.
  • a computer program also referred to as code, or instructions
  • a computer-readable medium stores a computer program (also referred to as code, or instruction) when it runs on a computer, causing the computer to execute the above-mentioned first to second aspects A method of implementation in any one of the possible implementations of the aspect or the first aspect to the second aspect.
  • FIG. 1 is a schematic diagram of a communication system provided by the present application.
  • FIG. 2 is a schematic diagram of another communication system provided by the application.
  • FIG. 3 is a schematic flowchart of a communication method provided by the present application.
  • FIG. 5 is a schematic flowchart of a communication method provided by the present application.
  • FIG. 6 is a schematic flowchart of another communication method provided by the present application.
  • FIG. 7 is a schematic flowchart of a communication method provided by the present application.
  • FIG. 9 is a schematic block diagram of a communication device provided by the present application.
  • FIG. 10 is a schematic block diagram of an access network device provided by the present application.
  • FIG. 11 is a schematic block diagram of a terminal device provided by the present application.
  • FIG. 12 is a schematic block diagram of a communication apparatus provided by the present application.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • 5th generation, 5G new radio
  • new radio new radio, NR
  • FIG. 1 shows an architectural diagram of a system 100 that can be applied to the present application.
  • the system 100 may include one or more of the following devices: a terminal device 101, an access network device 102, a user plane network element 103, a data network 104, an access and mobility management network element 105, The session management network element 106 , the policy control network element 107 , the application network element 108 , the unified data management network element 109 and the network opening network element 110 .
  • Terminal device 101 may be user equipment (user equipment, UE), user, 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.
  • UE user equipment
  • it can be a mobile phone (mobile phone), a tablet computer (pad), a computer with a wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, an industrial control (industrial control) wireless terminals in ), wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety , wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the terminal device 101 may also be a device or a circuit structure provided in the above-mentioned various devices, for example, a chip or a chip system.
  • the terminal device in this application may refer to a REDCAP terminal device, or a low-capability terminal device, a reduced-capability terminal device, a REDCAP UE, a Reduced Capacity UE, a narrow-band NR (narrow-band NR, NB-NR) UE, and the like.
  • the terminal device in this application has one or more of the following features:
  • the bandwidth capability can be represented by the baseband maximum bandwidth processing capability.
  • the bandwidth supported by the terminal device in this application is not greater than 40MHz.
  • the terminal device in this application may support 2-receive and 1-transmit (2 receive antennas and 1 transmit antenna), or 1-receive and 1-transmit (1 receive antenna and 1 transmit antenna).
  • Uplink maximum transmit power For example, the maximum uplink transmit power of the terminal device in this application may be 4 decibel milliwatts (dBm) A value in 20dBm.
  • dBm decibel milliwatts
  • the terminal device in this application may be a terminal device in NR release 17 (release-17, Rel-1) or a version after NRRel-17.
  • the terminal device in the present application does not support carrier aggregation, or supports carrier aggregation, but the maximum number of carrier aggregation supported at the same time is smaller than that of legacy or normal or high-capability terminal devices (also referred to as legacy (legacy) ) The maximum number of carrier aggregations supported by the terminal equipment or the normal terminal equipment at the same time.
  • the terminal device in this application supports half-duplex frequency division duplexing (FDD).
  • FDD frequency division duplexing
  • the minimum delay between the terminal device receiving the downlink data and sending the feedback on the downlink data in this application is longer than the time between the traditional capability or normal capability or high capability terminal device receiving the downlink data and sending the feedback on the downlink data and/or, the minimum delay between the terminal device in this application sending the uplink data and receiving the feedback to the uplink data is greater than the traditional capability or normal capability or high capability terminal device sending uplink data and receiving pair The minimum delay between the feedback of the upstream data.
  • the baseband processing capability of the terminal device in the present application is lower than the baseband processing capability of the conventional capability or normal capability or high capability terminal device.
  • the baseband processing capability may include at least one of the following: the maximum number of multiple input multiple output (MIMO) layers supported by the terminal device when performing data transmission, the hybrid automatic repeat request (hybrid automatic repeat request) supported by the terminal device , HARQ) number of processes, the maximum transmission block size (TBS) supported by the terminal device.
  • MIMO multiple input multiple output
  • HARQ hybrid automatic repeat request
  • TBS transmission block size
  • the peak transmission rate refers to the maximum data transmission rate that a terminal device can achieve in a unit time (eg, per second).
  • the peak uplink rate supported by the terminal device in the present application may be lower than the peak uplink rate supported by the conventional capability, normal capability or high capability terminal device, and/or the downlink peak rate supported by the terminal device in the present application may be lower than the conventional capability or the downlink peak rate supported by normal or high-capability terminal devices.
  • the buffer can be understood as the total size of the layer 2 (Layer2, L2) buffer, or the buffer can also be understood as the total number of soft channel bits that can be used by the HARQ process.
  • Access network equipment 102 capable of managing wireless resources, providing access services for terminal devices, and then completing the forwarding of control signals and user data between the terminal devices and the core network.
  • the access network equipment may be a transmission reception point (transmission reception point, TRP), an evolved base station (evolved NodeB, eNB or eNodeB) in the LTE system, a home base station (for example, home evolved NodeB, or home Node B, HNB), Wireless controllers, relay stations, access points, in-vehicle devices, wearable devices, and 5G mobile communication systems in baseband unit (BBU) and cloud radio access network (CRAN) scenarios Next generation NodeB (gNB), access network equipment, access point (AP), etc. in the future evolution of the public land mobile network (PLMN) network.
  • TRP transmission reception point
  • eNB evolved NodeB
  • eNodeB evolved NodeB
  • HNB home NodeB
  • Wireless controllers Wireless controllers
  • relay stations relay stations
  • access points access points
  • in-vehicle devices wearable devices
  • 5G mobile communication systems in baseband unit (BBU) and cloud radio access network (CRAN) scenarios
  • BBU baseband
  • User plane network element 103 mainly responsible for data packet routing and forwarding.
  • Data network 104 may be operator services, Internet access or third-party services, such as IP Multi-media Service (IMS), Internet, and the like.
  • a data network can include an application server (AS), which is a software framework that provides an environment in which applications run, providing security, data, transaction support, load balancing, and large-scale distributed system management for applications.
  • AS application server
  • the terminal device obtains the application message by communicating with the AS.
  • Access and mobility management network element 105 mainly responsible for mobility management in the mobile network, such as user location update, user registration in the network, user handover, and the like.
  • Session management network element 106 mainly responsible for session management in the mobile network, such as session establishment, modification, and release. Specific functions include assigning IP addresses to users and selecting user plane NEs that provide packet forwarding functions.
  • Policy control network element 107 responsible for providing policies to access and mobility management network elements and session management network elements, such as quality of service (quality of service, QoS) policies, slice selection policies, and the like.
  • quality of service quality of service, QoS
  • slice selection policies and the like.
  • Application network element 108 responsible for providing services to the 3GPP network, interacting with the policy control network element to perform policy control, and the like.
  • Unified data management network element 109 used to store user data, such as subscription information and authentication/authorization information.
  • Network opening network element 110 Provides a framework, authentication, and interface related to network capability opening, and transfers information between the 5G system network function and other network functions.
  • devices or network elements may be devices with corresponding functions, and may be software/hardware modules (eg, chips) and the like inside the device. It should also be understood that any device or network element involved in this application may be implemented in the form of software or a combination of software and hardware.
  • the system 100 shown in FIG. 1 may be the 5G system shown in FIG. 2 . It should be understood that the system 100 may also be a 4G system or other systems, which are not limited in this application.
  • FIG. 2 is a schematic diagram of a 5G system architecture.
  • the network elements with the same reference numerals in FIG. 1 are the names of the corresponding network elements in FIG. 1 in the current 5G system.
  • the 5G system architecture may include one or more of the following network elements: UE 101, (radio) access network ((radio) access network, (R) AN) 102, user plane function (user plane function, UPF) 103, data network (DN) 104, access and mobility management function (AMF) 105, session management function (session management function, SMF) 106, policy control function (policy control function, PCF) 107, application function (application function, AF) 108, unified data management (unified data management, UDM) 109 and network exposure function (network exposure function) 110.
  • UE 101 radio access network
  • R radio access network
  • UPF user plane function
  • DN data network
  • AMF access and mobility management function
  • SMF session management function
  • policy control function policy control function
  • PCF policy
  • each network element shown in FIG. 2 is only a name, and the name does not limit the function of the network element itself.
  • the foregoing network elements may also have other names, which are not specifically limited in this embodiment of the present application.
  • some or all of the above-mentioned network elements may use the terminology in 5G, or may have other names.
  • the interface between network elements shown in FIG. 2 is only an example. In 5G networks and other future networks, the interface between network elements may not be the interface shown in the figure, and this application does not make any limited.
  • a communication system to which the present application may be applied may include more or less network elements or devices.
  • the device or network element in FIG. 2 may be hardware, software divided by functions, or a combination of the above two.
  • the devices or network elements in FIG. 2 may communicate with each other through other devices or network elements.
  • 5G wireless technology is primarily used to address various use cases, which are categorized as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine-type communications (mMTC). Nonetheless, there are a few other use cases between these primary use cases, such as industrial sensor networks, video surveillance, and wearables.
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable and low-latency communications
  • mMTC massive machine-type communications
  • REDCAP reduced capability
  • REDCAP terminals have lower cost and complexity, smaller form factor and longer battery life. For a REDCAP terminal, how to ensure that the terminal can only use corresponding use cases or services is a key issue currently faced.
  • the present application provides a communication method, in which the access network device or the core network device can determine whether the terminal device can use the service corresponding to the REDCAP information (ie, the first REDCAP information) reported by the terminal device, thereby facilitating the guarantee A terminal device can only use its corresponding service.
  • the access network device or the core network device can determine whether the terminal device can use the service corresponding to the REDCAP information (ie, the first REDCAP information) reported by the terminal device, thereby facilitating the guarantee A terminal device can only use its corresponding service.
  • FIG. 3 is a schematic flowchart of a communication method provided by the present application.
  • the method 300 may include steps S310 to S330, and each step will be described below.
  • the first network element acquires the REDACP information from the terminal device, that is, the first REDACP information.
  • the first REDACP information may be actively sent by other network elements to the first network element, or may be sent by other network elements to the first network element after receiving the request of the first network element, or may be The first network element is determined by itself.
  • Methods 400 to 800 will be exemplified below.
  • the first network element acquires the subscribed REDCAP information of the terminal device, that is, the second REDCAP information.
  • the first network element may acquire the subscription information of the terminal device from the unified data management network element, where the subscription information of the terminal device includes the second REDCAP information.
  • the first network element may acquire the second REDCAP information in the subscription information of the terminal device from the unified data management network element.
  • the second REDCAP information may be information that has been stored in the unified data management network element when the terminal device subscribes, or may be sent by the application network element to the unified data management network element through a capability open interface.
  • the first network element determines, according to the first REDCAP information and the second REDCAP information, whether to allow the terminal device to use the service corresponding to the first REDCAP information.
  • the first REDCAP information is used to indicate the REDCAP access technology.
  • the second REDCAP information is used to indicate the access technology subscribed by the terminal device, or the second REDCAP information is used to indicate whether the terminal device has subscribed to the REDCAP access technology.
  • the terminal device If the access technology subscribed by the terminal device includes the REDCAP access technology, or the terminal device subscribes to the REDCAP access technology, the terminal device is allowed to use the service corresponding to the first REDCAP information, that is, the terminal device is allowed to use REDCAP
  • the access technology establishes the connection with the network. If the access technology subscribed by the terminal device does not include the REDCAP access technology, or the terminal device does not subscribe to the REDCAP access technology, the terminal device is not allowed to use the service corresponding to the first REDCAP information, that is, the terminal is not allowed The device establishes a connection to the network using the REDCAP access technology.
  • REDCAP access refers to the "reduced" version of NR technology that 5G NR uses to adapt to massive IoT terminal network access, namely Reduced Capability NR. It meets the network connection requirements of IoT terminal devices in three scenarios of video surveillance, industrial sensor networks and wearable devices, or similar requirements in other scenarios. That is to say, in the first implementation manner and the following second implementation manner, it can be considered that REDCAP terminals corresponding to different scenarios or different use cases can establish connections with the network through the REDCAP access technology.
  • a REDCAP terminal corresponding to a video surveillance scene can all be connected to the network through the REDCAP access technology.
  • a REDCAP terminal corresponding to an industrial sensor network can all be connected to the network through the REDCAP access technology.
  • the terminal device is a wearable device, and if the wearable device subscribes to the REDCAP access technology, the wearable device may be allowed to establish a connection with the network through the REDCAP access technology. If the access technology contracted by the wearable device is narrow band internet of things (NB-IoT), the wearable device is not allowed to establish a connection with the network through the REDCAP access technology.
  • NB-IoT narrow band internet of things
  • the first REDCAP information is used to indicate the REDCAP access technology and the first service type, and the access technology used by the first service type is the REDCAP access technology.
  • the second REDCAP information is used to indicate the REDCAP access technology and at least one service type, and the access technology used by the at least one service type is the REDCAP access technology.
  • the terminal device is allowed to use the service corresponding to the first REDCAP information, that is, the terminal device is allowed to use the REDCAP access technology to access the service of the first service type. If the at least one service type does not include the first service type, the terminal device is not allowed to use the service corresponding to the first REDCAP information, that is, the terminal device is not allowed to use the REDCAP access technology to access the service of the first service type.
  • the terminal device is allowed to use the REDCAP access technology to access the video surveillance service. If the first service type is video surveillance and the at least one service type is a wearable service, the terminal device is not allowed to use the REDCAP access technology to access the video surveillance service.
  • the first REDCAP information is used to indicate a first type of REDCAP access technology
  • the second REDCAP information is used to indicate at least one type of REDCAP access technology.
  • the service types corresponding to different types of REDCAP access technologies are different.
  • the terminal device is allowed to use the service corresponding to the first REDCAP information, that is, the terminal device is allowed to use the first type of REDCAP access technology Access services corresponding to the first type of REDCAP access technology. If the at least one type of REDCAP access technology does not include the first type of REDCAP access technology, the terminal device is not allowed to use the service corresponding to the first REDCAP information, that is, the terminal device is not allowed to use the first type of REDCAP The access technology accesses services corresponding to the first type of REDCAP access technology.
  • the first type of REDCAP access technology corresponds to video surveillance scenarios
  • the second type of REDCAP access technology corresponds to the industrial sensor network
  • the third type of REDCAP access technology corresponds to wearable scenarios.
  • REDCAP terminals used in video surveillance scenarios such as surveillance cameras can use the first type of REDCAP access technology
  • REDCAP terminals used in industrial sensor networks such as temperature sensors and pressure sensors, can use the second type of REDCAP access technology.
  • Wearable devices such as rings and smart watches can use the third type of REDCAP access technology.
  • the terminal device is a surveillance camera and the surveillance camera is subscribed to the first type of REDCAP access technology
  • the terminal device is allowed to use the first type of REDCAP access technology to access the video surveillance service.
  • business, business type, scenario, use case, and use case information can be replaced with each other.
  • the terminal device can report the access technology and/or service type to the first network element (access network device or core network device), and the first network element uses the subscription information of the terminal device to report to the terminal device
  • the reported access technology and/or service type is verified to determine whether the terminal device can use the reported access technology and/or service type, which is beneficial to ensure that the terminal device can only use its corresponding service.
  • the first network element may be an access network device or a core network device.
  • the first network element is taken as the access network equipment, the access and mobility management network element, the session management network element, the access network equipment in the second network in the process of switching the terminal device from the first network to the second network, Taking the access and mobility management network elements in the second network during the handover process of the terminal device from the first network to the second network as an example, the solution provided by the present application will be described in more detail.
  • FIG. 4 is a schematic flowchart of a communication method provided by the present application.
  • the method 400 is an example in which the first network element is an access network device, and the method 400 will be described below.
  • an access network device acquires first REDCAP information.
  • the access network device may acquire the first REDCAP information in various ways. An example is given below.
  • the terminal device may carry the first REDCAP information in the RRC message sent to the access network device.
  • the RRC message is an RRC connection establishment request message.
  • the terminal device may send the wireless capability information of the terminal device to the access network device, and the access network device may determine the first REDCAP information according to the wireless capability information.
  • the wireless capability information may carry the first REDCAP information.
  • the access network device may determine the first REDCAP information according to parameters in the wireless capability information, for example, the access network device may determine the terminal device according to parameters such as the access frequency point corresponding to the wireless capability information Use the REDCAP information as the first REDCAP information.
  • this method may be applied to the case where the terminal device is powered on and registered for the first time.
  • the terminal device may send the wireless capability information of the terminal device to the access network device, and the access network device may send the wireless capability information to the access and mobility management network element.
  • the access network device may request the wireless capability information from the access and mobility management network element, and the access and mobility management network element receives the connection.
  • the wireless capability information is returned to the access network device.
  • the access network device may determine the first REDCAP information according to the wireless capability information. For how the access network device determines the first REDCAP information according to the wireless capability information, reference may be made to the description in the second manner, which will not be repeated here.
  • the access and mobility management network element may put the wireless capability information of the terminal device in a container, which only saves the wireless capability information of the terminal device, but does not view the terminal device. Contents of the device's wireless capability information.
  • the terminal device may send the first REDCAP information to the access and mobility management network element through a NAS message, and the access and mobility management network element may send the received first REDCAP information to the access network device.
  • the access and mobility management network element may actively send the first REDCAP information in the NAS message to the access network device.
  • the access and mobility management network element may send the received first REDCAP information to the access network device.
  • the NAS message may be a registration request message (registration request message).
  • the access and mobility management network element may send the first REDCAP information to the access network device through an N2 message.
  • N2 is the interface between the access and mobility management network element and the access network equipment. If the name of the interface is changed, the message name will also be changed accordingly.
  • the access network device sends a first request message to the access and mobility management network element according to the first REDCAP information.
  • the access and mobility management network element receives the first request message sent by the terminal device.
  • the first request message is used to instruct the access and mobility management network element to obtain the subscription information of the terminal device from the unified data management network element, where the subscription information includes the second REDCAP information.
  • the first request message may include identification information of the terminal device, such as a subscription permanent identifier (SUPI).
  • SUPI subscription permanent identifier
  • the first request message may further include fourth indication information, where the fourth indication information is used to instruct the access and mobility management network element to obtain only the second REDCAP information from the unified data management network element, but not to obtain the information of the terminal device. Additional information for the contract.
  • the access and mobility management network element sends a second request message to the unified data management network element according to the first request message from the access network device.
  • the content in the first request message and the second request message may be the same, but this application does not limit this.
  • the first request message includes the fourth indication information
  • the second request message may not include the fourth indication information.
  • the unified data management network element sends the subscription information of the terminal device or the second REDCAP information to the access and mobility management network element.
  • the access and mobility management network element receives the subscription information of the terminal device or the second REDCAP information.
  • the unified data management network element can search for the second REDCAP information from the subscription information of the terminal device, and then send the second REDCAP information to the access and mobility management network element .
  • the unified data management network element sends the subscription information of the terminal device to the access and mobility management network element according to the request of the access and mobility management network element, where the subscription information of the terminal device includes the second REDCAP information.
  • the access and mobility management network element sends the second REDCAP information or the subscription information of the terminal device to the access network device.
  • the access network device receives the second REDCAP information or the subscription information of the terminal device.
  • the access network device determines, according to the first REDCAP information and the second REDCAP information, whether to allow the terminal device to use the service corresponding to the first REDCAP information.
  • This step is the same as S330, and reference may be made to S330.
  • the method may also include:
  • the access network device sends first indication information to the terminal device.
  • the terminal device receives the first indication information.
  • the first indication information is used to indicate that the terminal device is not allowed to use the service corresponding to the first REDCAP information, or the first indication information is used to indicate that the terminal device cannot use the service corresponding to the first REDCAP information.
  • the access network device determines that the terminal device is not allowed to use the service corresponding to the first REDCAP information, it can send first indication information to the terminal device, and indicate the terminal to the terminal device through the first indication information. The device cannot use the service corresponding to the first REDCAP information.
  • the first indication information may include a reason value, and the reason value is used to indicate the reason why the terminal device is rejected, that is, the reason value indicates the reason why the terminal device is not allowed to use the service corresponding to the first REDCAP information.
  • the cause value indicates that the terminal device is not subscribed to the REDACP access technology.
  • the cause value indicates that the terminal device is illegal/unauthorized to use the service of the first service type.
  • the first indication information or the cause value may be carried by an RRC reject or RRC release message.
  • the method may also include:
  • the terminal device sends the adjusted REDCAP information to the access network device.
  • the terminal device After receiving the first indication information, the terminal device can report the adjusted REDCAP information to the access network device, and the access network device can determine whether to allow the terminal device to use the service corresponding to the adjusted REDCAP information.
  • the adjusted REDCAP information can indicate the REDCAP access technology and the second service type
  • the access technology used by the second service type is the REDCAP access technology
  • the second REDCAP information indicates the REDCAP access technology and the second service type
  • the terminal device is allowed to use the service corresponding to the adjusted REDCAP information.
  • the method may also include:
  • the terminal device initiates a mobility update process to update the wireless capability information of the terminal device, thereby updating the first REDCAP information.
  • the terminal device sends the adjusted REDCAP information to the access network device by updating the wireless capability information of the terminal device.
  • S408a and S409a may be selected for execution.
  • the method may also include:
  • the access network device sends second indication information to the terminal device, where the second indication information is used to indicate that the terminal device is allowed to use the service corresponding to the first REDCAP information.
  • the terminal device receives the second indication information.
  • the access network device determines that the terminal device is allowed to use the service corresponding to the first REDCAP information, it may send second indication information to the terminal device.
  • the access network device determines that the terminal device is allowed to use the service corresponding to the first REDCAP information, and the access priority represented by the first service type indicated by the first REDCAP information is higher, Then the access network device can send the second indication information to the terminal device. For example, if the access network device determines that the terminal device is allowed to use the service corresponding to the first REDCAP information, and the first service type indicated by the first REDCAP information is a wearable service, the access network device can send the service to the terminal device. Send second indication information.
  • the second indication information may be carried in an RRC accept message.
  • the terminal device can report the first REDCAP information to the access network device, and the access network device obtains the subscribed REDCAP information (ie, the second REDCAP information) of the terminal device and then reports the first REDCAP information to the access network device. Verification is performed to determine whether the terminal device can use the service corresponding to the first REDCAP information, which is beneficial to ensure that the terminal device can only use the corresponding service.
  • FIG. 5 is a schematic flowchart of a communication method provided by the present application.
  • the method 500 is an example in which the first network element is an access and mobility management network element, and the method 500 will be described below.
  • an access and mobility management network element acquires first REDCAP information.
  • the access and mobility management network element can acquire the first REDCAP information in various ways. An example is given below.
  • the terminal device may send a NAS message to the access and mobility management network element, where the NAS message may carry the first REDCAP information. Therefore, the access and mobility management network element can acquire the first REDCAP information by receiving the NAS message.
  • the NAS message may be a registration request message.
  • the access network device may send the first REDCAP information to the access and mobility management network element.
  • the first REDCAP information on the access network device side may be sent by the terminal device to the access network device through an RRC message.
  • the first REDCAP information on the access network device side may be determined by the access network device according to the wireless capability information of the terminal device sent by the terminal device. For example, during the first registration process when the terminal device is powered on, the terminal device may send the wireless capability information of the terminal device to the access network device (perhaps at the request of the access network device). How the access network device determines the first REDCAP information according to the wireless capability information of the terminal device sent by the terminal device can refer to the second way in the method 400, and details are not repeated here.
  • the first REDCAP information on the access network device side may be determined by the access network device according to the wireless capability information of the terminal device obtained from the access and mobility management network element.
  • the terminal device may send the wireless capability information of the terminal device to the access network device, and the access network device may send the wireless capability information to the access and mobility management network element.
  • the access network device may request the wireless capability information from the access and mobility management network element, and the access and mobility management network element receives the access network After the request of the device, the wireless capability information is returned to the access network device.
  • the access network device may determine the first REDCAP information according to the wireless capability information, and send the first REDCAP information to the access and mobility management network element.
  • the access network device determines the first REDCAP information according to the wireless capability information reference may be made to the description in the second manner, and details are not repeated here.
  • the access and mobility management network element sends a second request message to the unified data management network element according to the first REDCAP information, so as to request the second REDCAP information or the subscription information of the terminal device.
  • the unified data management network element returns the second REDCAP information or the subscription information of the terminal device to the access and mobility management network element according to the request of the access and mobility management network element.
  • Steps S502-S503 are the same as S403-S404, and can be referred to S403-S404 and will not be repeated here.
  • the access and mobility management network element determines, according to the first REDCAP information and the second REDCAP information, whether to allow the terminal device to use the service corresponding to the first REDCAP information.
  • This step is the same as S330, and reference may be made to S330.
  • the method may also include:
  • the access and mobility management network element sends first indication information to the terminal device, where the first indication information is used to indicate that the terminal device is not allowed to use the service corresponding to the first REDCAP information.
  • the terminal device receives the first indication information.
  • the access and mobility management network element determines that the terminal device is not allowed to use the service corresponding to the first REDCAP information, the first indication information may be sent to the terminal device.
  • the first indication information may include a reason value, where the reason value is used to indicate the reason why the terminal device is rejected.
  • the cause value indicates that the terminal device is not subscribed to the REDACP access technology.
  • the cause value indicates that the terminal device is illegal/unauthorized to use the service of the first service type.
  • the first indication information or the cause value may be carried in a NAS reject (NAS reject) message.
  • NAS reject NAS reject
  • the NAS reject message may be a NAS registration reject message.
  • the method may also include:
  • the terminal device sends the adjusted REDCAP information to the access and mobility management network element.
  • the terminal device After receiving the first indication information, the terminal device can report the adjusted REDCAP information to the access network device, and then the access network device sends the adjusted REDCAP information to the access and mobility management network element, and the access and mobility management The network element can determine whether to allow the terminal device to use the service corresponding to the adjusted REDCAP information.
  • the adjusted REDCAP information may indicate the REDCAP access technology and the second service type, the access technology used by the second service type is the REDCAP access technology, and the second REDCAP information indicates the REDCAP access technology and the second service type , the terminal device is allowed to use the service corresponding to the adjusted REDCAP information.
  • the method may also include:
  • the terminal device initiates a mobility update process to update the wireless capability of the terminal device, thereby updating the first REDCAP information.
  • the terminal device sends the adjusted REDCAP information to the access network device by updating the wireless capability information of the terminal device.
  • the access network device can send the adjusted REDCAP information to the access and mobility management network element, and the access and mobility management network element can determine whether to allow the terminal device to use the service corresponding to the adjusted REDCAP information. It should be understood that one of S506a and S507a may be selected for execution.
  • the method may also include:
  • the access and mobility management network element sends second indication information to the terminal device, where the second indication information is used to indicate that the terminal device is allowed to use the service corresponding to the first REDCAP information.
  • the terminal device receives the second indication information.
  • the access and mobility management network element determines that the terminal device is allowed to use the service corresponding to the first REDCAP information, the second indication information may be sent to the terminal device.
  • the second indication information may be carried in the NAS accept message.
  • the access and mobility management network element can acquire the first REDCAP information, and after acquiring the subscribed REDCAP information (ie, the second REDCAP information) of the terminal device, the first REDCAP information Verification is performed to determine whether the terminal device can use the service corresponding to the first REDCAP information, which is beneficial to ensure that the terminal device can only use the corresponding service.
  • FIG. 6 is a schematic flowchart of a communication method provided by the present application.
  • the method 600 is an example in which the first network element is a session management network element, and the method 600 will be described below.
  • a session management network element acquires first REDCAP information.
  • the access and mobility management network element may send the first REDCAP information to the session management network element.
  • the access and mobility management network element acquires the first REDCAP information, reference may be made to the description of S501 in method 500, and details are not repeated here.
  • the session management network element sends a third request message to the unified data management network element.
  • the content of the third request message may be the same as the content of the first request message or the second request message described above.
  • steps S402 and S403 in method 400 please refer to the description of steps S402 and S403 in method 400, which will not be repeated here.
  • the unified data management network element returns the second REDCAP information or the subscription information of the terminal device to the session management network element according to the request of the terminal device.
  • the session management network element receives the second REDCAP information or the subscription information of the terminal device.
  • the subscription information of the terminal device includes second REDCAP information.
  • the session management network element determines, according to the first REDCAP information and the second REDCAP information, whether to allow the terminal device to use the service corresponding to the first REDCAP information.
  • This step is the same as S330, and reference may be made to S330.
  • the method may also include:
  • the session management network element sends first indication information to the terminal device, where the first indication information is used to indicate that the terminal device is not allowed to use the service corresponding to the first REDCAP information.
  • the terminal device receives the first indication information.
  • the session management network element determines that the terminal device is not allowed to use the service corresponding to the first REDCAP information
  • the first indication information may be sent to the access and mobility management network element.
  • the access and mobility management network element may carry the first indication information in the NAS message sent to the terminal device.
  • the first indication information may include a reason value, where the reason value is used to indicate the reason why the terminal device is rejected.
  • the cause value indicates that the terminal device is not subscribed to the REDACP access technology.
  • the cause value indicates that the terminal device is illegal/unauthorized to use the service of the first service type.
  • the first indication information or the cause value may be carried by the NAS SM reject message.
  • the NAS reject message may be a PDU session establishment reject message.
  • the method may also include:
  • the terminal device sends the adjusted REDCAP information to the access network device, and the access network device sends the adjusted REDCAP information to the session management network element through the access and mobility management network element.
  • the terminal device can report the adjusted REDCAP information to the access network device, and the access network device sends the adjusted REDCAP information to the session management network element through the access and mobility management network element.
  • the network element can determine whether to allow the terminal device to use the service corresponding to the adjusted REDCAP information.
  • the adjusted REDCAP information may indicate the REDCAP access technology and the second service type, the access technology used by the second service type is the REDCAP access technology, and the second REDCAP information indicates the REDCAP access technology and the second service type , the terminal device is allowed to use the service corresponding to the adjusted REDCAP information.
  • the method may also include:
  • the terminal device initiates a mobility update process to update the wireless capability of the terminal device, thereby updating the first REDCAP information.
  • the terminal device sends the adjusted REDCAP information to the access network device by updating the wireless capability information of the terminal device.
  • the access network device can send the adjusted REDCAP information to the session management network element through the access and mobility management network element, and the session management network element can determine whether to allow the terminal device to use the service corresponding to the adjusted REDCAP information.
  • S606a and S607a may be performed alternatively.
  • the method may also include:
  • the session management network element sends second indication information to the terminal device, where the second indication information is used to indicate that the terminal device is allowed to use the service corresponding to the first REDCAP information.
  • the terminal device receives the second indication information.
  • the session management network element determines that the terminal device is allowed to use the service corresponding to the first REDCAP information, the second indication information may be sent to the terminal device.
  • the second indication information may be carried by a PDU session establishment accept message.
  • the session management network element can acquire the first REDCAP information, and after acquiring the subscribed REDCAP information (ie, the second REDCAP information) of the terminal device, can verify the first REDCAP information, In order to clarify whether the terminal device can use the service corresponding to the first REDCAP information, it is beneficial to ensure that the terminal device can only use the corresponding service.
  • FIG. 7 is a schematic flowchart of a communication method provided by the present application.
  • the method 700 is an example in which the first network element is an access and mobility management network element in the second network during the handover process of the terminal device from the first network to the second network.
  • the first network may be a 4G or LTE network
  • the second network may be a 5G or NR network, but this application is not limited thereto.
  • the access network device in the second network is denoted as: target access network device
  • the access network device in the first network is denoted as: source access network device
  • the access and mobility management network element in the first network is recorded as: target access and mobility management network element
  • the access network equipment in the first network is recorded as: source access and mobility management network element.
  • the target access network device may be the gNB shown in the figure
  • the source access network device may be the eNB shown in the figure
  • the target access and mobility management network elements may be the AMF shown in the figure
  • the ingress and mobility management network elements may be MMEs as shown in the figure.
  • the method 700 is described below.
  • the source access network device sends a handover request message to the target access network device.
  • the target access network device receives the handover request message from the source access network device.
  • the handover request message includes wireless capability information of the terminal device.
  • the source access network device acquires the wireless capability information of the terminal device
  • the element should be an access and mobility management network element in the first network, such as an MME.
  • step S701 can refer to the prior art, for example, can refer to TS 23.502 Clause 4.111.2.2, which will not be described in detail here.
  • REDCAP indication information may be sent to the target access network device.
  • the target access network device receives the REDCAP indication information.
  • the REDCAP indication information is used to instruct the target access network device to determine the first REDCAP information according to the wireless capability information of the terminal device.
  • 702 may be performed before S701, or may be performed after S701, which is not limited in this embodiment of the present application.
  • the target access network device determines the first REDCAP information according to the wireless capability information of the terminal device.
  • the target access network device may determine the first REDCAP information from the terminal wireless capability information according to the REDCAP indication information sent by the access and mobility management network element.
  • the target access network device determines the first REDCAP information according to the wireless capability information of the terminal device.
  • the second method of step S401 for the access network device determines the first REDCAP information according to the wireless capability information of the terminal device. The related descriptions are not repeated here.
  • S702 is an optional step. That is, the target access network device may determine the first REDCAP information according to the REDCAP indication information sent by the target access and mobility management network element, or may independently determine the first REDCAP information.
  • the target access network device after determining the first REDCAP information, sends the first REDCAP information to the target access and mobility management network element. Accordingly, the target access and mobility management network element receives the first REDCAP information.
  • the target access and mobility management network element sends a second request message to the unified data management network element, and the unified data management network element sends a request to the target access and mobility management network element to the target access and mobility management network element according to the request of the target access and mobility management network element
  • the element returns the second REDCAP information or the subscription information of the terminal device.
  • the content of the second request message here may be the same as the content of the second request message described above.
  • steps S402 and S403 in the method 400 please refer to the description of steps S402 and S403 in the method 400, which will not be repeated here.
  • the target access and mobility management network element determines, according to the first REDCAP information and the second REDCAP information, whether to allow the terminal device to use the service corresponding to the first REDCAP information.
  • This step is the same as S330, and reference may be made to S330.
  • the method may also include:
  • the target access and mobility management network element sends first indication information to the source access and mobility management network element, where the first indication information is used to not allow the terminal device to use the service corresponding to the first REDCAP information.
  • the source access and mobility management network element receives the first indication information.
  • the target access and mobility management network element determines that the terminal device is not allowed to use the service corresponding to the first REDCAP information, the first indication information may be sent to the terminal device.
  • the first indication information may include a reason value, where the reason value is used to indicate the reason why the terminal device is rejected.
  • the cause value indicates that the terminal device is not subscribed to the REDACP access technology.
  • the cause value indicates that the terminal device is illegal/unauthorized to use the service of the first service type.
  • the method may also include one or more of the following steps:
  • the source access and mobility management network element sends handover failure information to the source access network device.
  • the source access network device receives the handover failure information.
  • the handover failure information is used to indicate that the handover fails.
  • the source access network device performs reselection of the target access network device according to the handover failure information or triggers the terminal device to update the wireless capability information.
  • the method may also include:
  • the target access and mobility management network element sends second indication information to the source access and mobility management network element, where the second indication information is used to indicate that the terminal device is allowed to use the service corresponding to the first REDCAP information.
  • the source access and mobility management network element receives the second indication information.
  • second indication information may be sent to the source access and mobility management network element.
  • S708a and 708b may be performed alternatively.
  • the target access and mobility management network element can acquire the first REDCAP information, and after acquiring the subscribed REDCAP information of the terminal device (ie, the second REDCAP information) Afterwards, the first REDCAP information can be verified to determine whether the terminal device can use the service corresponding to the first REDCAP information, which is beneficial to ensure that the terminal device can only use the corresponding service.
  • FIG. 8 is a schematic flowchart of a communication method provided by the present application.
  • the method 800 is an example in which the first network element is the target access network device in the second network during the handover process of the terminal device from the first network to the second network.
  • the first network may be a 4G or LTE network
  • the second network may be a 5G or NR network, but this application does not limit it.
  • the access network device in the second network is denoted as: target access network device
  • the access network device in the first network is denoted as: source access network device
  • the access and mobility management network element in the first network is recorded as: target access and mobility management network element
  • the access network equipment in the first network is recorded as: source access and mobility management network element.
  • the target access network device may be the gNB shown in the figure
  • the source access network device may be the eNB shown in the figure
  • the target access and mobility management network elements may be the AMF shown in the figure
  • the ingress and mobility management network elements may be MMEs as shown in the figure.
  • S801-S803 are the same as S801-S803, and refer to S801-S803.
  • the target access network device sends a first request message to the target access and mobility management network element.
  • the content of the first request message here may be the same as the content of the first request message described above.
  • steps S402 and S403 in the method 400 please refer to the description of steps S402 and S403 in the method 400, which will not be repeated here.
  • the target access and mobility management network element sends a second request message to the unified data management network element to request the second REDCAP information or the subscription information of the terminal device.
  • the unified data management network element returns the second REDCAP information or the subscription information of the terminal device to the target access and mobility management network element according to the request of the target access and mobility management network element.
  • the content in the first request message and the second request message may be the same, but this application does not limit this.
  • the first request message includes the fourth indication information
  • the second request message may not include the fourth indication information.
  • S804 is an optional step.
  • the target access and mobility management network element may request the unified data management network element for the second REDCAP information or the terminal device. contract information.
  • the target access and mobility management network element requests the unified data management network element for the second REDCAP information or the subscription information of the terminal device.
  • the target access and mobility management network element sends the second REDCAP information or the subscription information of the terminal device to the target access network device.
  • the target access network device receives the second REDCAP information or the subscription information of the terminal device.
  • the subscription information of the terminal device includes second REDCAP information.
  • the target access network device determines, according to the first REDCAP information and the second REDCAP information, whether to allow the terminal device to use the service corresponding to the first REDCAP information.
  • This step is the same as S330, and reference may be made to S330.
  • S805-S808 are similar to S403-S406, and reference may be made to S403-S406.
  • the method may also include:
  • the target access network device sends a handover rejection message to the source access network device.
  • the target access network device determines that the terminal device is not allowed to perform network communication with the target access network device, it may send a handover rejection message to the source access network device.
  • the method may also include:
  • the source access network device sends first indication information to the terminal device, where the first indication information is used to indicate that the terminal device is not allowed to use the service corresponding to the first REDCAP information.
  • the terminal device receives the first indication information.
  • the source access network device may send first indication information to the terminal device, and indicate to the terminal device through the first indication information that the terminal device is not allowed to use the service corresponding to the first REDCAP information.
  • the first indication information may include a reason value, where the reason value is used to indicate the reason why the terminal device is rejected.
  • the cause value indicates that the second REDCAP information indicates that the terminal device is not subscribed to the REDACP access technology.
  • the cause value indicates that the terminal device is illegal/unauthorized to use the service of the first service type.
  • the source access network device performs reselection of the target access network device according to the handover rejection message or triggers the terminal device to update the wireless capability information.
  • S810a and S811a may alternatively be executed.
  • the method may also include:
  • the target access network device sends a handover execution message to the source access network device.
  • the target access network device determines that the terminal device is allowed to perform network communication with the target access network device, it may send a handover execution message to the source access network device.
  • the source access network device sends second indication information to the terminal device.
  • the second indication information is used to indicate that the terminal device is allowed to use the service corresponding to the first REDCAP information.
  • the terminal device receives the second indication information.
  • the source access network device can learn that the target access network device allows the terminal device to use the service corresponding to the first REDCAP information, so that the second indication information can be sent to the terminal device.
  • the target access network device can acquire the first REDCAP information, and after acquiring the subscribed REDCAP information (ie, the second REDCAP information) of the terminal device, can The first REDCAP information is verified to determine whether the terminal device can use the service corresponding to the first REDCAP information, which is beneficial to ensure that the terminal device can only use the corresponding service.
  • the second REDCAP information is further used to indicate service feature information corresponding to the at least one service type.
  • the second REDCAP information indicates the REDCAP access technology and at least one service type, it may also indicate service feature information corresponding to the at least one service type.
  • the service feature information may be mobility information and/or energy saving requirements and the like.
  • the access network device may also obtain the service corresponding to the first service type according to the second REDCAP information characteristic information.
  • the access and mobility management network element may also obtain the first REDCAP information according to the second REDCAP information.
  • Service feature information corresponding to a service type, and the service feature information corresponding to the first service type can be sent to the access network device.
  • the session management network element may also obtain the service corresponding to the first service type according to the second REDCAP information feature information, and the service feature information corresponding to the first service type can be sent to the access network device.
  • the access network device can send the information to the terminal.
  • the device sends third indication information.
  • the third indication information is used to indicate one or more of the following:
  • the terminal device saves the timing advance TA value used in the current RRC connection establishment process, and uses it in the next RRC connection establishment; or,
  • the terminal device reduces the frequency at which neighbor measurements are made; or,
  • the terminal device saves the transmit power used in the current RRC connection establishment process, and uses it in the next RRC connection establishment.
  • the access network device may send third indication information.
  • the access network device may send broadcast information.
  • the broadcast information includes access technology indication information and optimization indication information of REDCAP, and the optimization information indicates whether the terminal device whose access technology is the first wireless access technology enables the optimization function according to the optimization indication information, and the optimization function includes the following: one or more of the above:
  • the access network device may send broadcast information.
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and inherent logic.
  • the various numerical numbers or serial numbers involved in the above processes are only for the convenience of description, and should not constitute any limitation on the implementation process of the embodiments of the present application.
  • the method described above mainly involves the REDCAP technology, but it should be understood that the method can also be extended to other technologies, such as extended to 6G or 6.5G technology.
  • FIG. 9 is a schematic block diagram of a communication apparatus provided by the present application.
  • the communication apparatus 2000 may include a transceiver unit 2100 and a processing unit 2200 .
  • the transceiver unit 2100 may include a sending unit and/or a receiving unit.
  • the transceiver unit 2100 may be a transceiver (including a transmitter and/or a receiver), an input/output interface (including an input and/or output interface), a pin or a circuit, and the like.
  • the transceiver unit 2100 may be configured to perform the sending and/or receiving steps in the above method embodiments.
  • the processing unit 2200 may be a processor (which may include one or more), a processing circuit with a processor function, and the like, and may be used to perform other steps in the foregoing method embodiments except for sending and receiving.
  • the communication device may further include a storage unit, which may be a memory, an internal storage unit (eg, a register, a cache, etc.), an external storage unit (eg, a read-only memory, a random access memory, etc.), etc. .
  • the storage unit is used for storing instructions, and the processing unit 2200 executes the instructions stored in the storage unit, so that the communication device executes the above method.
  • the communication apparatus 2000 may correspond to the first network element in the above method embodiments, such as the first network element in the method 300, the access network device in the method 400, and the access and mobility in the method 500.
  • the transceiver unit 2100 is configured to obtain the first REDCAP information from the terminal device and the second REDCAP information subscribed by the terminal device; the processing unit 2200 is configured to, according to the first REDCAP information and the second REDCAP information information to determine whether to allow the terminal device to use the service corresponding to the first REDCAP information.
  • the first REDCAP information is used to indicate a REDCAP access technology
  • the second REDCAP information is used to indicate whether the terminal device subscribes to the REDCAP access technology.
  • the first REDCAP information is used to indicate the REDCAP access technology and the first service type
  • the access technology used by the first service type is the REDCAP access technology
  • the second REDCAP information is used to indicate the REDCAP access technology.
  • the REDCAP access technology and at least one service type, and the access technology used by the at least one service type is the REDCAP access technology.
  • the first REDCAP information is used to indicate a first type of REDCAP access technology
  • the second REDCAP information is used to indicate at least one type of REDCAP access technology, services corresponding to different types of REDCAP access technologies different types.
  • the transceiver unit 2100 is further configured to send first indication information to the terminal device, where the first indication information is used to indicate that the terminal device cannot use the service corresponding to the first REDCAP information .
  • the first indication information includes a reason value, and the reason value is used to indicate the reason why the terminal device is rejected.
  • the apparatus 2000 is an access network device.
  • the transceiver unit 2100 is specifically configured to receive a radio resource control RRC message from the terminal device, where the RRC message includes the first REDCAP information.
  • the transceiver unit 2100 is specifically configured to receive wireless capability information from the terminal device; the processing unit 2200 is specifically configured to determine the first REDCAP information according to the wireless capability information.
  • the transceiver unit 2100 is specifically configured to receive a first message from an access and mobility management network element, where the first message includes the first REDCAP information.
  • the transceiver unit 2100 is specifically configured to receive wireless capability information of the terminal device from an access and mobility management network element; the processing unit 2200 is specifically configured to determine the wireless capability information according to the wireless capability information.
  • First REDCAP information is specifically configured to determine the wireless capability information according to the wireless capability information.
  • the apparatus 2000 is an access network device in the second network during the handover process of the terminal apparatus from the first network to the second network.
  • the transceiver unit 2100 is specifically configured to receive wireless capability information from the terminal device of an access network device in the first network; the transceiver unit 2200 is specifically configured to, according to the wireless capability information determines the first REDCAP information.
  • the transceiver unit 2100 is further configured to receive REDCAP indication information sent from an access and mobility management network element in the second network, where the REDCAP indication information is used to instruct the apparatus 2000 to The wireless capability information determines the first REDCAP information.
  • the transceiver unit is further configured to, according to the first REDCAP information, send request information to the access and mobility management network element, where the request information is used to request the access and mobility management network element from the unified
  • the data management network element obtains the second REDCAP information; and receives the second REDCAP information from the access and mobility management network element.
  • the apparatus 2000 is an access and mobility management network element.
  • the transceiver unit 2100 is specifically configured to receive a NAS message from the terminal device, where the NAS message includes the first REDCAP information; or, receive the first REDCAP information from an access network device .
  • the transceiver unit 2100 is further configured to send wireless capability information of the terminal device to the access network device, where the wireless capability information is used by the access network device to determine the first REDCAP information .
  • the apparatus 2000 is an access and mobility management network element in the second network during the handover process of the terminal apparatus from the first network to the second network.
  • the transceiver unit 2100 is specifically configured to receive the first REDCAP information from an access network device in the second network, where the first REDCAP information is an access network in the second network
  • the network device is determined according to the wireless capability information of the terminal device from the access network device in the first network.
  • the transceiver unit 2100 is further configured to send REDCAP indication information to the access network device in the second network, where the REDCAP indication information is used to instruct the access network device in the second network to The wireless capability information determines the first REDCAP information.
  • the apparatus 2000 is a session management network element.
  • the transceiver unit 2100 is specifically configured to receive the first REDCAP information from an access and mobility management network element.
  • the transceiver unit 2100 is specifically configured to, according to the first REDCAP information, send request information to a unified data management network element, where the request information is used to request the second REDCAP information;
  • the second REDCAP information of the data management network element is specifically configured to, according to the first REDCAP information, send request information to a unified data management network element, where the request information is used to request the second REDCAP information;
  • the second REDCAP information of the data management network element is specifically configured to, according to the first REDCAP information, send request information to a unified data management network element, where the request information is used to request the second REDCAP information;
  • the second REDCAP information of the data management network element is specifically configured to, according to the first REDCAP information, send request information to a unified data management network element, where the request information is used to request the second REDCAP information;
  • the second REDCAP information of the data management network element is specifically configured to, according to the first REDCAP information, send request information to a unified
  • the second REDCAP information is further used to indicate service feature information corresponding to the at least one service type.
  • the transceiver unit 2100 is further configured to send third indication information to the terminal device, where the third indication information is used to indicate one or more of the following: the terminal device saves this time The value of the timing advance TA used in the RRC connection establishment process, and used in the next RRC connection establishment; or, the terminal device reduces the frequency of neighbor cell measurement; or the terminal device saves the current RRC connection establishment The transmit power used in the process and will be used when the next RRC connection is established.
  • the transceiver unit 2100 is further configured to send broadcast information, where the broadcast information includes the REDCAP access technology indication information and optimization indication information, where the optimization information indication is used to indicate that the access technology is the REDCAP Whether the terminal device of the access technology enables the optimization function according to the optimization instruction information, and the optimization function includes one or more of the following: saving the timing advance TA value used in the current RRC connection establishment process, and It is used when the next RRC connection is established; or, the frequency of the neighbor cell measurement is reduced; or, the transmit power used during the current RRC connection establishment is saved and used when the next RRC connection is established.
  • transceiver unit 2100 and the processing unit 2200 may also perform other operations performed by the corresponding first network element in the above-mentioned corresponding methods, which will not be described in detail here.
  • the communication device 2000 may correspond to the terminal device in the foregoing method embodiments, and may perform operations performed by the terminal device.
  • the transceiver unit 2100 is configured to send first REDCAP information; and receive indication information from the first network element, where the indication information is used to indicate whether the apparatus 2000 is allowed to use the service corresponding to the first REDCAP information
  • the transceiver unit 2100 is further configured to, according to the indication information, send adjusted REDCAP information, where the adjusted REDCAP information is different from the first REDCAP information.
  • the first network element is an access network device.
  • the transceiver unit 2100 is further configured to receive third indication information from the first network element, where the third indication information is used to indicate one or more of the following: the apparatus 2000 Save the timing advance TA value used in the current RRC connection establishment process, and use it when the next RRC connection is established; or, the apparatus 2000 reduces the frequency of performing neighbor cell measurement; or, the apparatus 2000 saves this time The transmit power used during the establishment of the RRC connection, and will be used when the next RRC connection is established.
  • the transceiver unit 2100 is further configured to receive broadcast information from the first network element, where the broadcast information includes the REDCAP access technology indication information and optimization indication information, and the optimization information indicates that Whether the device 2000 indicating that the access technology is the REDCAP access technology enables the optimization function according to the optimization instruction information, and the optimization function includes one or more of the following: saving the current RRC connection establishment process used in TA value of the timing advance, and use it when the next RRC connection is established; or, reduce the frequency of neighbor cell measurement; use.
  • transceiver unit 2100 and the processing unit 2200 may also perform other operations performed by the terminal device in the foregoing method embodiments, which will not be described in detail here.
  • the communication apparatus 2000 may correspond to the unified data management network element in the above method embodiments, and may perform operations performed by the unified data management network element.
  • processing unit may be implemented by hardware or software, or may be implemented by a combination of software and hardware.
  • the transceiver unit 2100 in the communication device may correspond to the RRU 3100 in the access network device 2000 shown in FIG. 10
  • the processing unit 2200 in the communication device It may correspond to the BBU 3200 in the access network device 2000 shown in FIG. 10
  • the transceiver unit 2100 in the communication apparatus may be an input/output interface.
  • the transceiver unit 2100 in the communication device 2000 may correspond to the transceiver 4002 in the terminal device 4000 shown in FIG. 11
  • the processing unit 2200 in the communication device 2000 may Corresponds to the processor 4001 in the terminal device 4000 shown in FIG. 11 .
  • FIG. 10 is a schematic structural diagram of an access network device provided by an embodiment of the present application, which may be, for example, a schematic structural diagram of a base station.
  • the access network device 3000 may implement the functions of the access network device in the foregoing method embodiments.
  • the access network device 3000 may include one or more radio frequency units, such as a remote radio unit (RRU) 3100 and one or more baseband units (BBU) (also referred to as distributed Unit (DU)) 3200.
  • RRU remote radio unit
  • BBU baseband units
  • DU distributed Unit
  • the RRU 3100 may be called a transceiver unit or a communication unit, which corresponds to the transceiver unit 2100 in FIG. 9 .
  • the transceiver unit 3100 may also be referred to as a transceiver, a transceiver circuit, or a transceiver, etc., which may include at least one antenna 3101 and a radio frequency unit 3102 .
  • the transceiver unit 3100 may include a receiving unit and a sending unit, the receiving unit may correspond to a receiver (or called a receiver, a receiving circuit), and the sending unit may correspond to a transmitter (or called a transmitter, a sending circuit).
  • the RRU 3100 part is mainly used for the transceiver of radio frequency signals and the conversion of radio frequency signals and baseband signals.
  • the part of the BBU 3200 is mainly used to perform baseband processing, control the base station, and the like.
  • the RRU 3100 and the BBU 3200 may be physically set together, or may be physically separated, that is, a distributed base station.
  • the BBU 3200 is the control center of the base station, and can also be referred to as a processing unit, which can correspond to the processing unit 2200 in FIG. 9 , and is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spread spectrum, and the like.
  • the BBU processing unit
  • the BBU may be used to control the base station to perform the operation procedure of the access network device in the foregoing method embodiments.
  • the BBU 3200 may be composed of one or more boards, and the multiple boards may jointly support a wireless access network (such as an LTE network) of a single access standard, or may respectively support a wireless access network of different access standards.
  • Wireless access network (such as LTE network, 5G network or other network).
  • the BBU 3200 also includes a memory 3201 and a processor 3202.
  • the memory 3201 is used to store necessary instructions and data.
  • the processor 3202 is configured to control the base station to perform necessary actions, for example, to control the base station to perform the operation flow of the access network device in the foregoing method embodiments.
  • the memory 3201 and processor 3202 may serve one or more single boards. That is to say, the memory and processor can be provided separately on each single board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits may also be provided on each single board.
  • the access network device 3000 shown in FIG. 10 can implement various processes related to the access network device in the foregoing method embodiments.
  • the operations or functions of each module in the access network device 3000 are respectively to implement the corresponding processes in the foregoing method embodiments.
  • the above-mentioned BBU 3200 may be used to perform the actions performed by the access network device described in the foregoing method embodiments, and the RRU 3100 may be used to perform the actions of sending and receiving by the access network device described in the foregoing method embodiments.
  • the RRU 3100 may be used to perform the actions of sending and receiving by the access network device described in the foregoing method embodiments.
  • FIG. 11 is a schematic structural diagram of a terminal 4000 provided by an embodiment of the present application.
  • the terminal 4000 includes a processor 4001 and a transceiver 4002 .
  • the terminal 4000 may further include a memory 4003 .
  • the processor 4001, the transceiver 4002 and the memory 4003 can communicate with each other through an internal connection path to transmit control and/or data signals, the memory 4003 is used to store computer programs, and the processor 4001 is used to retrieve data from the memory 4003.
  • the computer program is invoked and executed to control the transceiver 4002 to send and receive signals.
  • the above-mentioned processor 4001 and the memory 4003 can be combined into a processing device 4004, and the processor 4001 is configured to execute the program codes stored in the memory 4003 to realize the above-mentioned functions. It should be understood that the processing device 4004 shown in the figure is only an example. During specific implementation, the memory 4003 may also be integrated in the processor 4001 or independent of the processor 4001 . This application does not limit this.
  • the above-mentioned terminal 4000 may further include an antenna 4010 for transmitting the uplink data or uplink control signaling output by the transceiver 4002 through wireless signals.
  • the terminal 4000 shown in FIG. 11 can implement the functions that can be implemented by the terminal device involved in the foregoing method embodiments.
  • the operations or functions of each module in the terminal 4000 are respectively to implement the corresponding processes in the foregoing method embodiments.
  • the above-mentioned terminal 4000 may further include a power supply 4005 for providing power to various devices or circuits in the terminal.
  • the terminal 4000 may further include one or more of an input unit 4006, a display unit 4007, an audio circuit 4008, a camera 4009, a sensor 4011, etc.
  • the audio circuit may also Including speaker 40081, microphone 40082, etc.
  • the processing device 4004 or the processor 4001 may be a chip.
  • the processing device 4004 or the processor 4001 may be a field programmable gate array (FPGA), a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (application specific integrated circuit) integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and can also be a system on chip (system on chip, SoC), It can also be a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (microcontroller).
  • CPU central processing unit
  • NP network processor
  • DSP digital signal processing circuit
  • microcontroller microcontroller
  • controller unit MCU
  • MCU memory
  • PLD programmable logic device
  • 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.
  • a memory in this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable 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 random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM enhanced synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SCRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • FIG. 12 is a schematic block diagram of a communication apparatus 5000 provided by an embodiment of the present application. Any network element involved in this application, such as an access network device, a first network element, a terminal device, etc., can be implemented by the communication device shown in FIG. 12 .
  • the communication apparatus 5000 may be a physical device, or a component of the physical device (eg, an integrated circuit, a chip, etc.), or a functional module in the physical device.
  • the communication apparatus 5000 includes: one or more processors 5001 .
  • the processor 5001 may store execution instructions for executing the methods of the embodiments of the present application.
  • the processor 5001 may call an interface to implement the receiving and sending functions.
  • the interface may be a logical interface or a physical interface, which is not limited.
  • the interface may be a transceiver circuit, or an interface circuit.
  • Transceiver circuits or interface circuits for realizing receiving and transmitting functions may be separate or integrated.
  • the above-mentioned transceiver circuit or interface circuit can be used for code/data reading and writing, or the above-mentioned transceiver circuit or interface circuit can be used for signal transmission or transmission.
  • the interface can be implemented by a transceiver.
  • the communication apparatus 5000 may further include a transceiver 5003 .
  • the transceiver 5003 may be referred to as a transceiver unit, a transceiver, a transceiver circuit or a transceiver, etc., and is used to implement a transceiver function.
  • the communication apparatus 5000 may further include a memory 5002 .
  • This embodiment of the present application does not specifically limit the specific deployment location of the memory 5002, and the memory may be integrated in the processor, or may be independent of the processor.
  • the communication device 5000 does not include the memory, the communication device 5000 only needs to have a processing function, and the memory can be deployed in other locations (eg, a cloud system).
  • the processor 5001, the memory 5002 and the transceiver 5003 communicate with each other through an internal connection path to transmit control and/or data signals.
  • the communication device 5000 may also include other devices, such as input devices, output devices, batteries, and the like.
  • the memory 5002 may store execution instructions for executing the methods of the embodiments of the present application.
  • the processor 5001 can execute the instructions stored in the memory 5002 in combination with other hardware (eg, the transceiver 5003) to complete the steps of the method shown in this document.
  • other hardware eg, the transceiver 5003
  • the methods disclosed in the embodiments of the present application may be applied to the processor 5003 or implemented by the processor 5003 .
  • the processor 5003 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the method can be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (field programmable gate array, FPGA), or other possible solutions. 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.
  • Software modules can be located in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory or electrically erasable programmable memory, registers, etc. in the storage medium.
  • the storage medium is located in the memory, and the processor reads the instructions in the memory, and completes the steps of the above method in combination with its hardware.
  • the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code runs on a computer, the computer is made to execute any of the foregoing method embodiments A method for any one of the network elements (eg, access network equipment, first network element, terminal device, or unified data management network element).
  • the network elements eg, access network equipment, first network element, terminal device, or unified data management network element.
  • the present application further provides a computer-readable medium, where program codes are stored in the computer-readable medium, and when the program codes are run on a computer, the computer is made to execute any of the foregoing method embodiments method for any network element.
  • the present application also provides a system, which includes one or more of the following: an access network device, a session management network element, an access and mobility management network element, or a unified data Manage network elements.
  • An embodiment of the present application further provides a processing apparatus, including a processor and an interface, where the processor is configured to execute the method in any of the foregoing method embodiments.
  • the above processing device may be a chip.
  • the processing device may be a field programmable gate array (FPGA), a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC) , off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, can also be system on chip (system on chip, SoC), can also be central processing It can be a central processor unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (MCU) , it can also be a programmable logic device (PLD) or other integrated chips.
  • FPGA field programmable gate array
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • FPGA field programmable gate array
  • FPGA field programmable gate array
  • FPGA field programmable gate array
  • FPGA field programmable gate
  • 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 above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state discs, SSD)) etc.
  • a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, or a computer.
  • an application running on a computing device and the computing device may be components.
  • One or more components may reside within a process or thread of execution, and a component may be localized on one computer or distributed among 2 or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • a component may, for example, pass a signal through a local system based on a signal having one or more data packets (such as data from two components interacting with another component between a local system, a distributed system, or a network, such as the Internet interacting with other systems through signals). or remote process to communicate.
  • a signal having one or more data packets (such as data from two components interacting with another component between a local system, a distributed system, or a network, such as the Internet interacting with other systems through signals). or remote process to communicate.
  • B corresponding to A indicates that B is associated with A, and B can be determined according to A.
  • determining B according to A does not mean that B is only determined according to A, and B may also be determined according to A and/or other information.
  • an item includes one or more of the following: A, B, and C
  • the item can be any of the following: A; B, unless otherwise specified. ;C;A and B;A and C;B and C;A,B and C;A and A;A,A and A;A,A and B;A,A and C,A,B and B;A , C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B and C.
  • a total of three elements of A, B and C are used as examples above to illustrate the optional items of the item.
  • 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: a U disk, a removable hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk and other media that can store program codes.

Landscapes

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

Abstract

本申请提供了一种通信方法和通信装置，可以由第一网元获取来自终端装置的第一REDCAP信息和该终端装置的签约的第二REDCAP信息，并且由第一网元根据第一REDCAP信息和第二REDCAP信息，确定是否允许该终端装置使用和第一REDCAP信息所对应的业务。其中，第一网元为接入网设备或者核心网设备。基于该方案，第一网元可以通过终端装置的签约的REDCAP信息验证第一REDCAP信息所对应的业务是否可以被使用，从而有利于保障该终端装置仅仅使用用于其对应的业务，比如，有利于保证该终端装置仅能够通过REDCAP接入技术使用第一业务类型的业务，而不能通过REDCAP接入技术使用第二业务类型的业务。

Description

通信方法和通信装置 技术领域
本申请涉及通信领域，并且更具体地，涉及一种通信方法和通信装置。
背景技术
第五代(5G)无线技术主要用于解决各种用例，这些用例分为增强型移动宽带(enhanced mobile broadband，eMBB)，超可靠和低延迟通信(ultra reliable low latency communication，URLLC)以及大规模机器类型通信(massive machine type communication，mMTC)。尽管如此，在这些主要用例之间还存在其他一些用例，例如工业传感网络，视频监控和可穿戴设备。为了有效地服务于此类用例，引入了功能较弱的NR终端，即低能力(reduced capability，REDCAP)终端。与常规NR终端相比，REDCAP终端具有较低的成本和复杂性，更小的外形尺寸和更长的电池寿命。对于REDCAP终端，如何保障该终端仅仅能够使用相应的用例或者业务，是当前面临的关键问题。
发明内容
本申请提供一种通信方法和通信装置，有利于保障对应终端装置仅仅能够使用其对应的业务。
第一方面，提供了一种通信方法，该方法包括：第一网元获取来自终端装置的第一REDCAP信息和该终端装置的签约的第二REDCAP信息，并且根据第一REDCAP信息和第二REDCAP信息，确定是否允许该终端装置使用和第一REDCAP信息所对应的业务。
可选地，第一网元为接入网设备或者核心网设备。
根据本申请提供的通信方法，第一网元可以通过终端装置签约的REDCAP信息(即，第二REDCAP信息)验证该终端装置上报的REDCAP信息(即，第一REDCAP信息)是否可以被使用，从而有利于保障该终端装置仅仅能够使用其对应的业务。
结合第一方面，在第一方面的某些实现方式中，该第一REDCAP信息用于指示REDCAP接入技术，该第二信息用于指示该终端装置是否签约了该REDCAP接入技术。
在该方案中，是否允许该终端装置使用和第一REDCAP信息所对应的业务是指是否允许该终端装置通过REDCAP接入技术与网络建立连接。基于该方案，第一网元可以确定该终端装置是否可以通过REDCAP接入技术与网络建立连接，从而能够保障该终端装置仅能够使用其签约的接入技术与网络建立连接。
结合第一方面，在第一方面的某些实现方式中，该第一REDCAP信息用于指示REDCAP接入技术和第一业务类型，该第一业务类型使用的接入技术为REDCAP接入技术，该第二REDCAP信息用于指示该REDCAP接入技术和至少一个业务类型，该至少一个业务类型使用的接入技术为该REDCAP接入技术。
在该方案中，是否允许该终端装置使用和第一REDCAP信息所对应的业务是指是否 允许该终端装置通过REDCAP接入技术使用第一业务类型的业务。基于该方案，第一网元可以确定该终端装置是否可以通过REDCAP接入技术使用第一业务类型的业务，从而能够保障该终端装置仅能够用于REDCAP接入技术下的第一业务类型的业务。
结合第一方面，在第一方面的某些实现方式中，该第一REDCAP信息用于指示第一类型的REDCAP接入技术，该第二REDCAP信息用于指示至少一个类型的REDCAP接入技术，不同类型的REDCAP接入技术对应的业务类型不同。其中，第一类型的REDCAP接入技术对应第一业务类型。
在该方案中，是否允许该终端装置使用和第一REDCAP信息所对应的业务是指是否允许该终端装置使用第一类型的REDCAP接入技术，或者是否允许该终端装置通过第一类型的REDCAP接入技术使用第一业务类型的业务，或者是否允许该终端装置使用第一业务类型的业务。基于该方案，第一网元可以确定该终端装置是否可以使用第一类型的REDCAP接入技术，从而能够保障该终端装置仅能够用于第一类型的REDCAP接入技术。
结合第一方面，在第一方面的某些实现方式中，第一网元向该终端装置发送第一指示信息，第一指示信息用于指示不允许该终端装置使用和第一REDCAP信息所对应的业务，或者用于指示该终端装置不能使用和第一REDCAP信息所对应的业务。
可选地，第一指示信息包括原因值，该原因值用于指示该终端装置被拒绝的原因。
结合第一方面，在第一方面的某些实现方式中，在第一网元为接入网设备的情况下，第一网元获取来自该终端装置的第一REDCAP信息，包括：第一网元接收来自该终端装置的无线资源控制(radio resource control，RRC)消息，该RRC消息包括该第一REDCAP信息；或者，第一网元接收来自该终端装置的无线能力信息，并根据该无线能力信息确定该第一REDCAP信息；或者，该第一网元接收来自接入和移动管理网元的第一消息，该第一消息包括该第一REDCAP信息；或者，该第一网元接收来自接入和移动管理网元的该终端装置的无线能力信息，并根据该无线能力信息确定该第一REDCAP信息。
基于上述任一种方式，第一网元可以获得该第一REDCAP信息。
示例性的，该RRC消息为RRC连接建立请求消息。
结合第一方面，在第一方面的某些实现方式中，该第一网元为该终端装置从第一网络向第二网络切换过程中的该第二网络中的接入网设备。
示例性的，第一网络可以是第四代(4th generation，4G)或长期演进(long term evolution，LTE)网络、第二网络可以是第五代(5th generation，5G)或者新无线(new radio，NR)网络。
结合第一方面，在第一方面的某些实现方式中，第一网元获取来自该终端装置的第一REDCAP信息，包括：第一网元接收来自该第一网络中的接入网设备的该终端装置的无线能力信息；第一网元根据该无线能力信息确定该第一REDCAP信息。
进一步地，在第一网元根据该无线能力信息确定该第一REDCAP信息之前，该方法还包括：第一网元接收来自该第二网络中的接入和移动管理网元发送的REDCAP指示信息，该REDCAP指示信息用于指示第一网元根据该无线能力信息确定该第一REDCAP信息。
基于该方案，第一网元可以根据第二网络中的接入和移动管理网元的指示，根据该无线能力信息确定该第一REDCAP信息。
结合第一方面，在第一方面的某些实现方式中，第一网元获取该终端装置的签约的第二REDCAP信息，包括：第一网元根据该第一REDCAP信息，向接入和移动管理网元发送请求信息，该请求信息用于请求该接入和移动管理网元从统一数据管理网元获取第二REDCAP信息；第一网元接收来自该接入和移动管理网元的第二REDCAP信息。
应理解，在第一网元为第二网络中的接入网设备的情况下，该接入和移动管理网元为第二网络中的接入和移动管理网元。
结合第一方面，在第一方面的某些实现方式中，第一网元为接入和移动管理网元。
结合第一方面，在第一方面的某些实现方式中，第一网元获取该第一REDCAP信息，包括：第一网元接收来自该终端装置的非接入层(non-access stratum，NAS)消息，该NAS消息包括该第一REDCAP信息；或者，第一网元接收来自接入网设备的该第一REDCAP信息。
结合第一方面，在第一方面的某些实现方式中，在第一网元接收来自接入网设备的该第一REDCAP信息之前，该方法还包括：第一网元向该接入网设备发送该终端装置的无线能力信息，该无线能力信息用于该接入网设备确定该第一REDCAP信息。
结合第一方面，在第一方面的某些实现方式中，第一网元为该终端装置从第一网络向第二网络切换过程中的该第二网络中的接入和移动管理网元。
结合第一方面，在第一方面的某些实现方式中，第一网元获取该第一REDCAP信息，包括：第一网元接收来自该第二网络中的接入网设备的该第一REDCAP信息，该第一REDCAP信息为该第二网络中的接入网设备根据来自该第一网络中的接入网设备的该终端装置的无线能力信息确定的。
结合第一方面，在第一方面的某些实现方式中，在第一网元接收来自该第二网络中的接入网设备的该第一REDCAP信息之前，该方法还包括：第一网元向该第二网络中的接入网设备发送REDCAP指示信息，该REDCAP指示信息用于指示该第二网络中的接入网设备根据该无线能力信息确定该第一REDCAP信息。
结合第一方面，在第一方面的某些实现方式中，第一网元为会话管理网元。
结合第一方面，在第一方面的某些实现方式中，第一网元获取该第一REDCAP信息，包括：第一网元接收来自接入和移动管理网元的该第一REDCAP信息。
结合第一方面，在第一方面的某些实现方式中，第一网元获取第二REDCAP信息，包括：第一网元根据该第一REDCAP信息，向统一数据管理网元发送请求信息，该请求信息用于请求第二REDCAP信息；第一网元接收来自该统一数据管理网元的该第二REDCAP信息。
结合第一方面，在第一方面的某些实现方式中，该第二REDCAP信息还用于指示该至少一个业务类型对应的业务特征信息。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：第一网元向该终端装置发送第三指示信息，该第三指示信息用于指示下述中的一项或多项：该终端装置保存本次RRC连接建立过程中所使用的定时提前量(timing advance，TA)值，并在下一次RRC连接建立时使用；或者，该终端装置降低进行邻区测量时的频率；或者，该终端装置保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
示例性的，在该第一业务类型对应的业务特征信息为终端装置固定位置或者终端装置 用于视频监控场景的情况下，第一网元可以发送第三指示信息，通过第三指示信息对该终端装置的随机接入、无线资源管理或功率控制等方法进行优化。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：第一网元发送广播信息，该广播信息包括该REDCAP接入技术指示信息和优化指示信息，该优化信息指示用于指示接入技术为该第一无线接入技术的终端装置是否根据该优化指示信息开启优化功能，该优化功能包括下述中的一项或多项：保存本次RRC连接建立过程中所使用的定时提前量TA值，并在下一次RRC连接建立时使用；或者，降低进行邻区测量时的频率；或者，保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
示例性的，在该第一业务类型对应的业务特征信息为终端装置固定位置或者终端装置用于视频监控场景的情况下，第一网元可以发送广播信息，通过该广播信息对该终端装置的随机接入、无线资源管理或功率控制等方法进行优化。
第二方面，提供了一种通信方法，包括：终端装置发送第一REDCAP信息；该终端装置接收来自第一网元根据第一REDCAP信息发送的指示信息，该指示信息用于指示是否允许该终端装置使用和该第一REDCAP信息所对应的业务。
。
根据本申请提供的通信方法，第一网元可以通过终端装置的签约的REDCAP信息验证该第一REDCAP信息是否可以被使用，从而利于保障该终端装置仅仅能够使用其对应的业务。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该终端装置根据该指示信息，发送调整后的REDCAP信息，该调整后的REDCAP信息与该第一REDCAP信息不同。
结合第二方面，在第二方面的某些实现方式中，该终端装置发送第一REDCAP信息，包括：该终端装置发送无线能力信息，该无线能力信息用于确定该第一REDCAP信息。
结合第二方面，在第二方面的某些实现方式中，该第一网元为接入网设备。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该终端装置接收来自该第一网元的第三指示信息，该第三指示信息用于指示下述中的一项或多项：该终端装置保存本次RRC连接建立过程中所使用的定时提前量TA值，并在下一次RRC连接建立时使用；或者，该终端装置降低进行邻区测量时的频率；或者，该终端装置保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该终端装置接收来自该第一网元的广播信息，该广播信息包括该REDCAP接入技术指示信息和优化指示信息，该优化信息指示用于指示接入技术为该REDCAP接入技术的终端装置是否根据该优化指示信息开启优化功能，该优化功能包括下述中的一项或多项：保存本次RRC连接建立过程中所使用的定时提前量TA值，并在下一次RRC连接建立时使用；或者，降低进行邻区测量时的频率；或者，保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
第三方面，提供了一种通信系统，包括：第一网元和第二网元；该第二网元向该第一网元发送终端装置的第一REDCAP信息；该第一网元根据该第一REDCAP信息，获取该 终端装置的签约的第二REDCAP信息；该第一网元根据该第一REDCAP信息和该第二REDCAP信息，确定是否允许该终端装置使用和该第一REDCAP信息所对应的业务。
根据本申请提供的通信系统，第一网元可以通过终端装置的签约的REDCAP信息验证该第一REDCAP信息是否可以被使用，从而利于保障该终端装置仅仅能够使用其对应的业务。
结合第三方面，在第三方面的某些实现方式中，该第二网元为接入和移动管理网元，且该第一网元为接入网设备；或者，该第二网元为接入网设备，且该第一网元为接入和移动管理网元；或者，该第二网元为接入和移动管理网元，且该第一网元为会话管理网元；或者，该第二网元为该终端装置从第一网络向第二网络切换过程中的该第一网络中的接入网设备，且该第一网元为该第二网络中的接入网设备。
结合第三方面，在第三方面的某些实现方式中，该系统还包括统一数据管理网元；以及，该第一网元根据该第一REDCAP信息，获取该终端装置的签约的第二REDCAP信息，包括：该第一网元根据该第一REDCAP信息，从该统一数据管理网元获取第二REDCAP信息。
第四方面，提供了一种通信装置，包括用于执行第一方面至第二方面或第一方面至第二方面中任一种可能实现方式中的方法的各个模块或单元。
第五方面，提供了一种装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以使得该装置执行上述第一方面至第二方面或第一方面至第二方面中任一种可能实现方式中的方法。可选地，该装置还包括存储器。可选地，该装置还包括接口电路，处理器与接口电路耦合。
第六方面，提供了一种处理器，包括：输入电路、输出电路和处理电路。该处理电路用于通过该输入电路接收信号，并通过该输出电路发射信号，使得该处理器执行第一方面至第二方面或第一方面至第二方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第七方面，提供了一种处理装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行第一方面至第二方面或第一方面至第二方面中任一种可能实现方式中的方法。
可选地，该处理器为一个或多个，该存储器为一个或多个。
可选地，该存储器可以与该处理器集成在一起，或者该存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
上述第七方面中的处理装置可以是一个芯片，该处理器可以通过硬件来实现也可以通 过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第八方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当该计算机程序被运行时，使得计算机执行上述第一方面二第九方面或第一方面至第二方面中任一种可能实现方式中的方法。
第九方面，提供了一种计算机可读介质，该计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面至第二方面或第一方面至第二方面中任一种可能实现方式中的方法。
附图说明
图1是本申请提供的一种通信系统的示意图；
图2是本申请提供的另一种通信系统的示意图；
图3是本申请提供的一种通信方法的示意性流程图；
图4是本申请提供的另一种通信方法的示意性流程图；
图5是本申请提供的一种通信方法的示意性流程图；
图6是本申请提供的另一种通信方法的示意性流程图；
图7是本申请提供的一种通信方法的示意性流程图；
图8是本申请提供的另一种通信方法的示意性流程图；
图9是本申请提供的一种通信装置的示意性框图；
图10是本申请提供的一种接入网设备的示意性框图；
图11是本申请提供的一种终端装置的示意性框图；
图12是本申请提供的一种通信装置的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、第五代(5th generation，5G)系统、新无线(new radio，NR)或未来可能出现的其他通信系统等。
图1示出了可以应用于本申请的系统100的架构图。如图1所示，该系统100可以包括下述中的一个或多个设备：终端装置101、接入网设备102、用户面网元103、数据网络104、接入和移动管理网元105、会话管理网元106、策略控制网元107、应用网元108、统一数据管理网元109和网络开放网元110。
终端装置101：可以是用户设备(user equipment，UE)、用户、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。例如，可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端装置、增强现实(augmented reality，AR)终端装置、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中 的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。终端装置101还可以是上述各种设备中设置的装置或者电路结构，例如，芯片或者芯片系统。
本申请中的终端装置可以是指REDCAP终端设备，或者，低能力终端设备、降低能力终端设备、REDCAP UE、Reduced Capacity UE、窄带NR(narrow-band NR，NB-NR)UE等。
可选地，本申请中的终端装置具备下述中的一项或多项特征：
1、带宽能力。带宽能力可以用基带最大带宽处理能力表示。例如，本申请中的终端装置支持的带宽不大于40MHz。
2、收发天线数。例如，本申请中的终端装置可以支持2收1发(2个接收天线和1个发送天线)，或者1收1发(1个接收天线和1个发送天线)。
3、上行最大发射功率。例如，本申请中的终端装置的上行最大发射功率可以为4分贝毫瓦(dBm)
Figure PCTCN2021080479-appb-000001
20dBm中的一个值。
4、协议版本。本申请中的终端装置可以是NR版本17(release-17,Rel-1)或者NRRel-17以后版本中的终端装置。
5、栽波聚合能力。例如，本申请中的终端装置不支持栽波聚合，或者支持栽波聚合，但是同时支持的载波聚合的最大个数小于传统能力或正常能力或高能力的终端装置(也可以称为传统(legacy)终端设备或者常规(normal)终端装置)同时支持的栽波聚合的最大个数。
6、双工能力。例如，本申请中的终端装置支持半双工频分双工(frequency division duplexing,FDD)。
7、数据的处理时间能力。例如，本申请中的终端装置接收下行数据与发送对该下行数据的反馈之间的最小时延大于传统能力或正常能力或高能力的终端装置接收下行数据与发送对该下行数据的反馈之间的最小时延；和/或，本申请中的终端装置发送上行数据与接收对该上行数据的反馈之间的最小时延大于传统能力或正常能力或高能力的终端装置发送上行数据与接收对该上行数据的反馈之间的最小时延。
8、处理能力(ability/capability)。例如，本申请中的终端装置的基带处理能力低于传统能力或正常能力或高能力的终端装置的基带处理能力。其中，基带处理能力可以包括以下至少一项：终端装置进行数据传输时支持的最大多输入多输出(multiple input multiple output，MIMO)层数，终端装置支持的混合自动重传请求(hybrid automatic repeat request,HARQ)进程数目，终端装置支持的最大传输块大小(transmission block size，TBS)。
9、上行和/或下行的传输峰值速率。传输峰值速率是指终端设备在单位时间内(例如每秒)能够达到的最大数据传输速率。本申请中的终端装置支持的上行峰值速率可以低于传统能力或正常能力或高能力的终端装置支持的上行峰值速率，和/或本申请中的终端装置支持的下行峰值速率可以低于传统能力或正常能力或高能力的终端装置支持的下行峰值速率。
10、缓存(buffer)大小。buffer可以理解为层2(Layer2,L2)缓存总大小，或者，buffer也可以理解为HARQ处理所能使用的软信道比特总数。
接入网设备102：能够管理无线资源，为终端装置提供接入服务，进而完成控制信号和用户数据在终端装置和核心网之间的转发。
接入网设备可以是传输接收点(transmission reception point，TRP)、LTE系统中的演进型基站(evolved NodeB，eNB或eNodeB)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)、云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、中继站、接入点、车载设备、可穿戴设备、5G移动通信系统中的下一代基站(next generation NodeB，gNB)、未来演进的陆上公用移动通信网(public land mobile network，PLMN)网络中的接入网设备、接入点(access point，AP)等。
用户面网元103：主要负责数据包路由和转发。
数据网络104：可以是运营商服务，互联网接入或者第三方服务，如IP多媒体业务(IP Multi-media Service，IMS)、互联网等。数据网络中可以包括应用服务器(application server，AS)，AS是一种软件框架，提供一个应用程序运行的环境，用于为应用程序提供安全、数据、事务支持、负载平衡大型分布式系统管理等服务。终端装置通过与AS通信获取应用报文。
接入和移动管理网元105：主要负责移动网络中的移动性管理，如用户位置更新、用户注册网络、用户切换等。
会话管理网元106：主要负责移动网络中的会话管理，如会话建立、修改、释放。具体功能如为用户分配IP地址、选择提供报文转发功能的用户面网元等。
策略控制网元107：负责向接入和移动管理网元、会话管理网元提供策略，如服务质量(quality of service，QoS)策略、切片选择策略等。
应用网元108：负责向3GPP网络提供业务、与策略控制网元之间交互以进行策略控制等。
统一数据管理网元109：用于存储用户数据，如签约信息、鉴权/授权信息。
网络开放网元110：提供网络能力开放相关的框架、鉴权和接口，在5G系统网络功能和其他网络功能之间传递信息。
应理解，上述各设备或网元可以是具有相应功能的装置，可以是该装置内部的软/硬件模块(如芯片)等。还应理解，本申请所涉及的任一设备或网元可以以软件形式、软硬件结合形式的方式实现。
在一个示例中，图1所示的系统100可以是图2所示的5G系统。应理解，系统100还可以是4G系统或者其他系统，本申请对此不作限定。
图2是一种5G系统架构示意图。该系统架构图中，与图1中附图标记相同的网元是图1中相应的网元在当前5G系统中的命名。参见图2，该5G系统架构可以包括下述一个或多个网元：UE 101、(无线)接入网((radio)access network，(R)AN)102、用户平面功能(user plane function，UPF)103、数据网络(data network，DN)104、接入和移动性管理功能(access and mobility management function，AMF)105、会话管理功能(session management function，SMF)106、策略控制功能(policy control function，PCF)107、应用功能(application function，AF)108、统一数据管理(unified data management，UDM)109以及网络开放功能(network exposure function)110。
应理解，图2所示的各个网元的命名仅是一个名字，名字对网元本身的功能不构成限定。在不同的网络中，上述各个网元也可以是其他的名字，本申请实施例对此不作具体限定。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能是其他命名。类似地，图2所示的网元之间的接口仅是一个示例，在5G网络以及未来其它的网络中，网元之间的接口也可以不是图中所示的接口，本申请对此不作限定。
还应理解，本申请实施例并不限于图2所示的系统架构中。例如，可以应用本申请的通信系统可以包括更多或更少的网元或设备。图2中的设备或网元可以是硬件，也可以是从功能上划分的软件或者以上二者的结合。图2中的设备或网元之间可以通过其他设备或网元通信。
5G无线技术主要用于解决各种用例，这些用例分为增强型移动宽带(eMBB)，超可靠和低延迟通信(URLLC)以及大规模机器类型通信(mMTC)。尽管如此，在这些主要用例之间还存在其他一些用例，例如工业传感网络，视频监控和可穿戴设备。为了有效地服务于此类用例，引入了功能较弱的NR终端，即低能力(reduced capability，REDCAP)终端。与常规NR终端相比，REDCAP终端具有较低的成本和复杂性，更小的外形尺寸和更长的电池寿命。对于REDCAP终端，如何保障该终端仅仅能够使用相应的用例或者业务，是当前面临的关键问题。
有鉴于此，本申请提供了一种通信方法，接入网设备或者核心网设备能够确定终端装置是否能够使用其上报的REDCAP信息(即，第一REDCAP信息)所对应的业务，从而有利于保障终端装置仅仅能够使用其对应的业务。下面对本申请提供的方案进行说明。
图3是本申请提供的一种通信方法的示意性流程图。该方法300可以包括步骤S310至S330，以下将对各步骤进行说明。
S310，第一网元获取来自终端装置的REDACP信息，即第一REDACP信息。
在本申请中，第一REDACP信息可以是其他网元主动向第一网元发送的，也可以是其他网元在接收到第一网元的请求后向第一网元发送的，还可以是第一网元自己确定的。下文中的方法400至方法800中将会进行举例说明。
S320，第一网元获取该终端装置的签约的REDCAP信息，即第二REDCAP信息。
第一网元可以从统一数据管理网元获取该终端装置的签约的信息，该终端装置的签约的信息包括第二REDCAP信息。或者，第一网元可以从统一数据管理网元获取该终端装置的签约的信息中的第二REDCAP信息。其中，第二REDCAP信息可以是终端装置签约时就已经存储在统一数据管理网元中的信息，也可以是应用网元通过能力开放接口向统一数据管理网元发送的。
S330，第一网元根据第一REDCAP信息和REDCAP第二信息，确定是否允许该终端装置使用和第一REDCAP信息所对应的业务。
第一种实现方式中，第一REDCAP信息用于指示REDCAP接入技术。相应地，第二REDCAP信息用于指示该终端装置签约的接入技术，或者，第二REDCAP信息用于指示该终端装置是否签约了REDCAP接入技术。
如果该终端装置签约的接入技术包括REDCAP接入技术，或者，该终端装置签约了REDCAP接入技术，则允许该终端装置使用和第一REDCAP信息所对应的业务，即允许该终端装置使用REDCAP接入技术与网络建立连接。如果该终端装置签约的接入技术不 包括REDCAP接入技术，或者，该终端装置没有签约REDCAP接入技术，则不允许该终端装置使用和第一REDCAP信息所对应的业务，即不允许该终端装置使用REDCAP接入技术与网络建立连接。
在第一种实现方式和下文中的第二种实现方式中，REDCAP接入是指5G NR为了适配海量物联网终端网络接入进行的“简配”版NR技术，即Reduced Capability NR，旨在满足视频监控、工业传感网络以及可穿戴设备三种场景下的物联网终端装置网络连接需求，或其它场景的类似需求。也就是说，在第一种实现方式和下文中的第二种实现方式中，可以认为不同场景或不同用例所对应的REDCAP终端都可以通过REDCAP接入技术与网络建立连接。比如，视频监控场景对应的REDCAP终端、工业传感网络对应的REDCAP终端以及可穿戴场景对应的REDCAP终端(即，可穿戴设备)都可以通过REDCAP接入技术与网络建立连接。
例如，所述终端装置为可穿戴设备，在该可穿戴设备签约了REDCAP接入技术的情况下，可以允许该可穿戴设备通过REDCAP接入技术与网络建立连接。如果该可穿戴设备签约的接入技术为窄带物联网(narrow band internet of things，NB-IoT)，则不允许该可穿戴设备通过REDCAP接入技术与网络建立连接。
第二种实现方式中，第一REDCAP信息用于指示REDCAP接入技术和第一业务类型，第一业务类型使用的接入技术为REDCAP接入技术。相应地，第二REDCAP信息用于指示REDCAP接入技术和至少一个业务类型，该至少一个业务类型使用的接入技术为REDCAP接入技术。
如果该至少一个业务类型包括第一业务类型，则允许该终端装置使用和第一REDCAP信息所对应的业务，即允许该终端装置使用REDCAP接入技术访问第一业务类型的业务。如果该至少一个业务类型不包括第一业务类型，则不允许该终端装置使用和第一REDCAP信息所对应的业务，即不允许该终端装置使用REDCAP接入技术访问第一业务类型的业务。
例如，如果第一业务类型为视频监控业务，该至少一个业务类型也包括视频监控业务，则允许该终端装置使用REDCAP接入技术访问视频监控业务。如果第一业务类型为视频监控，该至少一个业务类型为可穿戴业务，则不允许该终端装置使用REDCAP接入技术访问视频监控业务。
第三种实现方式中，第一REDCAP信息用于指示第一类型的REDCAP接入技术，相应地，第二REDCAP信息用于指示至少一个类型的REDCAP接入技术。其中，不同类型的REDCAP接入技术对应的业务类型不同。
如果该至少一个类型的REDCAP接入技术包括第一类型的REDCAP接入技术，则允许该终端装置使用和第一REDCAP信息所对应的业务，即允许该终端装置使用第一类型的REDCAP接入技术访问第一类型的REDCAP接入技术对应的业务。如果该至少一个类型的REDCAP接入技术不包括第一类型的REDCAP接入技术，则不允许该终端装置使用和第一REDCAP信息所对应的业务，即不允许该终端装置使用第一类型的REDCAP接入技术访问第一类型的REDCAP接入技术对应的业务。
在该实现方式中，可以认为不同场景或不同用例对应不同的REDCAP接入技术，或者可以认为不同的REDCAP接入技术指示了不同的场景或者用例。比如，第一类型的 REDCAP接入技术对应视频监控场景、第二类型的REDCAP接入技术对应工业传感网络第三类型的REDCAP接入技术对应可穿戴场景。监控摄像头等用于视频监控场景的REDCAP终端可以使用第一类型的REDCAP接入技术，温度传感器、压力传感器等用于工业传感网络的REDCAP终端可以使用第二类型的REDCAP接入技术，智能手环、智能手表等可穿戴设备可以使用第三类型的REDCAP接入技术。
例如，在所述终端装置为监控摄像头，并且该监控摄像头签约了第一类型的REDCAP接入技术，则允许该终端装置使用第一类型的REDCAP接入技术访问视频监控业务。
本申请中，业务、业务类型、场景、用例以及用例信息(use case)可以相互替换。
根据本申请提供的方法，终端装置可以向第一网元(接入网设备或者核心网设备)上报接入技术和/或业务类型，第一网元使用该终端装置的签约的信息对终端装置上报的接入技术和/或业务类型进行验证，以明确该终端装置是否可以使用其上报的接入技术和/或业务类型，这样，有利于保证终端装置仅仅能够使用其对应的业务。
上述方案中，第一网元可以是接入网设备也可以是核心网设备。下面分别以第一网元为接入网设备、接入和移动管理网元、会话管理网元、终端装置从第一网络向第二网络切换过程中的第二网络中的接入网设备、以及终端装置从第一网络向第二网络切换过程中的第二网络中的接入和移动管理网元为例，对本申请提供的方案进行更详细的说明。
图4是本申请提供的一种通信方法的示意性流程图。该方法400是第一网元为接入网设备的一个例子，下面对该方法400进行说明。
S401，接入网设备获取第一REDCAP信息。
该接入网设备可以通过多种方式获取该第一REDCAP信息。下面进行举例说明。
方式一
该终端装置可以在向该接入网设备发送的RRC消息中携带第一REDCAP信息。
示例性的，该RRC消息为RRC连接建立请求消息。
方式二
该终端装置可以向该接入网设备发送该终端装置的无线能力信息，该接入网设备可以根据该无线能力信息确定该第一REDCAP信息。比如，该无线能力信息可以携带该第一REDCAP信息。或者，该接入网设备可以根据该无线能力信息中的参数确定该第一REDCAP信息，比如，该接入网设备可以根据该无线能力信息中对应的接入频点等参数，确定该终端装置使用的REDCAP信息，并将其作为该第一REDCAP信息。
示例性的，该方式可以应用于该终端装置开机首次注册的情况下。
方式三
该终端装置可以向该接入网设备发送该终端装置的无线能力信息，该接入网设备可以将该无线能力信息发送给接入和移动管理网元。当该终端装置与该接入网设备之间建立RRC连接后，该接入网设备可以向该接入和移动管理网元请求该无线能力信息，该接入和移动管理网元接收到该接入网设备的请求后，向该接入网设备返回该无线能力信息。该接入网设备可以根据该无线能力信息确定该第一REDCAP信息，关于该接入网设备如何根据该无线能力信息确定该第一REDCAP信息可以参见方式二中的说明，这里不再赘述。
示例性的，本申请中，接入和移动管理网元可以将该终端装置的无线能力信息放在一个容器(contain)中，其只保存该终端装置的无线能力信息，而不会查看该终端装置的无 线能力信息中的内容。
方式四
该终端装置可以通过NAS消息向接入和移动管理网元发送第一REDCAP信息，接入和移动管理网元可以将接收到的第一REDCAP信息发送给该接入网设备。比如，接入和移动管理网元接收到NAS消息后，可以将NAS消息中的第一REDCAP信息主动发送给该接入网设备。或者，在该接入网设备请求该第一REDCAP信息时，接入和移动管理网元可以将接收到的第一REDCAP信息发送给该接入网设备。
示例性的，所述NAS消息可以是注册请求消息(registration request message)。
示例性的，接入和移动管理网元可以通过N2消息向该接入网设备发送第一REDCAP信息。N2为接入和移动管理网元和接入网设备之间的接口，如果该接口的名称改变了，则该消息名称也会相应改变。
S402，接入网设备根据该第一REDCAP信息，向接入和移动管理网元发送第一请求消息。相应地，接入和移动管理网元接收该终端装置发送的第一请求消息。
示例性的，第一请求消息用于指示接入和移动管理网元从统一数据管理网元获取该终端装置的签约的信息，其中，该签约的信息包括第二REDCAP信息。比如，第一请求消息可以包括该终端装置的身份标识信息，如用户永久标识符(subscription permanent identifier，SUPI)。
进一步地，第一请求消息还可以包括第四指示信息，该第四指示信息用于指示接入和移动管理网元从统一数据管理网元仅获取第二REDCAP信息，而不获取该终端装置的签约的其他信息。
S403，接入和移动管理网元根据来自接入网设备的第一请求消息，向统一数据管理网元发送第二请求消息。
应理解，第一请求消息和第二请求消息中的内容可以相同，但本申请对此不作限定。比如，第一请求消息包括第四指示信息时，第二请求消息可以不包括第四指示信息。
S404，统一数据管理网元向接入和移动管理网元发送该终端装置的签约的信息或者第二REDCAP信息。相应地，接入和移动管理网元接收该终端装置的签约的信息或者第二REDCAP信息。
具体地，统一数据管理网元根据接入和移动管理网元的请求，可以从该终端装置的签约的信息里查找第二REDCAP信息，然后将第二REDCAP信息发送给接入和移动管理网元。或者，统一数据管理网元根据接入和移动管理网元的请求，将该终端装置的签约的信息发送给接入和移动管理网元，该终端装置的签约的信息包括第二REDCAP信息。
S405，接入和移动管理网元向接入网设备发送第二REDCAP信息或者该终端装置的签约的信息。相应地，接入网设备接收第二REDCAP信息或者该终端装置的签约的信息。
S406，接入网设备根据第一REDCAP信息和第二REDCAP信息，确定是否允许该终端装置使用和第一REDCAP信息所对应的业务。
该步骤与S330相同，可以参考S330。
可选地，该方法还可以包括：
S407a，接入网设备向该终端装置发送第一指示信息。相应地，该终端装置接收第一指示信息。其中，第一指示信息用于指示不允许该终端装置使用和第一REDCAP信息所 对应的业务，或者第一指示信息用于指示该终端装置不能使用和第一REDCAP信息所对应的业务。
若在S406中，接入网设备确定不允许该终端装置使用和第一REDCAP信息所对应的业务，则可以向该终端装置发送第一指示信息，通过第一指示信息向该终端装置指示该终端装置不能使用和第一REDCAP信息所对应的业务。
示例性的，第一指示信息可以包括原因值，该原因值用于指示该终端装置被拒绝的原因，即该原因值指示不允许该终端装置使用和第一REDCAP信息所对应的业务的原因。比如，该原因值指示该终端装置没有签约REDACP接入技术。比如，该原因值指示该终端装置非法/无权使用第一业务类型的业务。
示例性的，第一指示信息或者该原因值可以通过RRC拒绝或者RRC释放消息携带。
可选地，该方法还可以包括：
S408a，该终端装置向接入网设备发送调整后的REDCAP信息。
该终端装置接收到第一指示信息后，可以向接入网设备上报调整后的REDCAP信息，接入网设备可以确定是否允许该终端装置使用和调整后的REDCAP信息所对应的业务。
比如，如果调整后的REDCAP信息可以指示REDCAP接入技术和第二业务类型，第二业务类型使用的接入技术为REDCAP接入技术，并且，第二REDCAP信息指示REDCAP接入技术和第二业务类型，则允许该终端装置使用和调整后的REDCAP信息所对应的业务。
可选地，该方法还可以包括：
S409a，该终端装置发起移动性更新过程，进行该终端装置的无线能力信息更新，从而更新该第一REDCAP信息。
即，该终端装置通过更新该终端装置的无线能力信息，向该接入网设备发送调整后的REDCAP信息。
应理解，S408a和S409a可以择其一执行。
可选地，该方法还可以包括：
S407b，接入网设备向该终端装置发送第二指示信息，第二指示信息用于指示允许该终端装置使用和第一REDCAP信息所对应的业务。相应地，该终端装置接收第二指示信息。
若在S406中，接入网设备确定允许该终端装置使用和第一REDCAP信息所对应的业务，则可以向该终端装置发送第二指示信息。
或者，若在S406中，接入网设备确定允许该终端装置使用和第一REDCAP信息所对应的业务，并且该第一REDCAP信息所指示的第一业务类型所代表的接入优先级较高，则接入网设备可以向该终端装置发送第二指示信息。比如，接入网设备确定允许该终端装置使用和第一REDCAP信息所对应的业务，并且该第一REDCAP信息所指示的第一业务类型为可穿戴业务，则接入网设备可以向该终端装置发送第二指示信息。示例性的，第二指示信息可以通过RRC接受消息携带。
应理解，S407a和S407b可以择其一执行。
根据本申请提供的通信方法，终端装置可以向接入网设备上报第一REDCAP信息，接入网设备获取到该终端装置的签约的REDCAP信息(即，第二REDCAP信息)后对第 一REDCAP信息进行验证，以明确该终端装置是否可以使用和第一REDCAP信息所对应的业务，这样，有利于保证终端装置仅仅能够使用其对应的业务。
图5是本申请提供的一种通信方法的示意性流程图。该方法500是第一网元为接入和移动管理网元的一个例子，下面对该方法500进行说明。
S501，接入和移动管理网元获取第一REDCAP信息。
接入和移动管理网元可以通过多种方式获取第一REDCAP信息。下面进行举例说明。
方式一
该终端装置可以向接入和移动管理网元发送NAS消息，该NAS消息可以携带该第一REDCAP信息。从而，该接入和移动管理网元可以通过接收到NAS消息获取该第一REDCAP信息。
示例性的，该NAS消息可以是注册请求消息。
方式二
接入网设备可以向该接入和移动管理网元发送该第一REDCAP信息。
示例性的，接入网设备侧的该第一REDCAP信息可以该终端装置通过RRC消息向该接入网设备发送的。
示例性的，接入网设备侧的该第一REDCAP信息可以是该接入网设备根据该终端装置发送的该终端装置的无线能力信息确定的。比如，在该终端装置开机首次注册的过程中，该终端装置可以向该接入网设备发送该终端装置的无线能力信息(可能是应接入网设备的请求)。该接入网设备如何根据该终端装置发送的该终端装置的无线能力信息确定该第一REDCAP信息可以参考方法400中的方式二，这里不再赘述。
示例性的，接入网设备侧的该第一REDCAP信息可以是该接入网设备根据从该接入和移动管理网元获取的该终端装置的无线能力信息确定的。具体地，该终端装置可以向该接入网设备发送该终端装置的无线能力信息，该接入网设备可以将该无线能力信息发送给接入和移动管理网元。当该终端装置与该接入网设备完成RRC连接后，该接入网设备可以向该接入和移动管理网元请求该无线能力信息，该接入和移动管理网元接收到该接入网设备的请求后，向该接入网设备返回该无线能力信息。该接入网设备可以根据该无线能力信息确定该第一REDCAP信息，并将该第一REDCAP信息发送给该接入和移动管理网元。关于该接入网设备如何根据该无线能力信息确定该第一REDCAP信息可以参见方式二中的说明，这里不再赘述。
S502～S503，接入和移动管理网元根据第一REDCAP信息，向统一数据管理网元发送第二请求消息，以请求第二REDCAP信息或者该终端装置的签约的信息。统一数据管理网元根据接入和移动管理网元的请求，向接入和移动管理网元返回第二REDCAP信息或者该终端装置的签约的信息。
步骤S502～S503与S403～S404相同，可以参照S403～S404这里不再赘述。
S504，接入和移动管理网元根据第一REDCAP信息和第二REDCAP信息，确定是否允许该终端装置使用和第一REDCAP信息所对应的业务。
该步骤与S330相同，可以参考S330。
可选地，该方法还可以包括：
S505a，接入和移动管理网元向该终端装置发送第一指示信息，第一指示信息用于指 示不允许该终端装置使用和第一REDCAP信息所对应的业务。相应地，该终端装置接收第一指示信息。
若在S504中，接入和移动管理网元确定不允许该终端装置使用和第一REDCAP信息所对应的业务，则可以向该终端装置发送第一指示信息。
示例性的，第一指示信息可以包括原因值，该原因值用于指示该终端装置被拒绝的原因。比如，该原因值指示该终端装置没有签约REDACP接入技术。比如，该原因值指示该终端装置非法/无权使用第一业务类型的业务。
示例性的，第一指示信息或者该原因值可以通过NAS拒绝(NAS reject)消息携带。比如，该NAS拒绝消息可以是NAS注册拒绝消息。
可选地，该方法还可以包括：
S506a，该终端装置向接入和移动管理网元发送调整后的REDCAP信息。
该终端装置接收到第一指示信息后，可以向接入网设备上报调整后的REDCAP信息，然后接入网设备将调整后的REDCAP信息发送给接入和移动管理网元，接入和移动管理网元可以确定是否允许该终端装置使用和调整后的REDCAP信息所对应的业务。
比如，调整后的REDCAP信息可以指示REDCAP接入技术和第二业务类型，第二业务类型使用的接入技术为REDCAP接入技术，并且，第二REDCAP信息指示REDCAP接入技术和第二业务类型，则允许该终端装置使用和调整后的REDCAP信息所对应的业务。
可选地，该方法还可以包括：
S507a，该终端装置发起移动性更新过程，进行该终端装置的无线能力更新，从而更新该第一REDCAP信息。
即，该终端装置通过更新该终端装置的无线能力信息，向该接入网设备发送调整后的REDCAP信息。接入网设备可以将调整后的REDCAP信息发送给接入和移动管理网元，接入和移动管理网元可以确定是否允许该终端装置使用和调整后的REDCAP信息所对应的业务。应理解，S506a和S507a可以择其一执行。
可选地，该方法还可以包括：
S505b，接入和移动管理网元向该终端装置发送第二指示信息，第二指示信息用于指示允许该终端装置使用和第一REDCAP信息所对应的业务。相应地，该终端装置接收第二指示信息。
若在S504中，接入和移动管理网元确定允许该终端装置使用和第一REDCAP信息所对应的业务，则可以向该终端装置发送第二指示信息。
示例性的，第二指示信息可以通过NAS接受消息携带。
应理解，S505a和S506b可以择其一执行。
根据本申请提供的通信方法，接入和移动管理网元可以获取第一REDCAP信息，并在获取到该终端装置的签约的REDCAP信息(即，第二REDCAP信息)后，可以对第一REDCAP信息进行验证，以明确该终端装置是否可以使用和第一REDCAP信息所对应的业务，这样，有利于保证终端装置仅仅能够使用其对应的业务。
图6是本申请提供的一种通信方法的示意性流程图。该方法600是第一网元为会话管理网元的一个例子，下面对该方法600进行说明。
S601，会话管理网元获取第一REDCAP信息。
具体地，接入和移动管理网元可以向会话管理网元发送该第一REDCAP信息。关于接入和移动管理网元如何获取到该第一REDCAP信息，可以参考方法500中对S501的说明，这里不再赘述。
S602，会话管理网元向统一数据管理网元发送第三请求消息。
示例性的，第三请求消息中的内容可以和前文描述的第一请求消息或者第二请求消息中的内容相同，具体可以参见方法400中对步骤S402和S403的说明，这里不再赘述。
S603，统一数据管理网元根据该终端装置的请求，向会话管理网元返回第二REDCAP信息或者该终端装置的签约的信息。相应地，会话管理网元接收第二REDCAP信息或者该终端装置的签约的信息。其中，终端装置的签约的信息包括第二REDCAP信息。
S604，会话管理网元根据第一REDCAP信息和第二REDCAP信息，确定是否允许该终端装置使用和第一REDCAP信息所对应的业务。
该步骤与S330相同，可以参考S330。
可选地，该方法还可以包括：
S605a，会话管理网元向该终端装置发送第一指示信息，第一指示信息用于指示不允许该终端装置使用和第一REDCAP信息所对应的业务。相应地，该终端装置接收第一指示信息。
若在S604中，会话管理网元确定不允许该终端装置使用和第一REDCAP信息所对应的业务，则可以向接入和移动管理网元发送第一指示信息。例如，接入和移动管理网元可以在发送给该终端装置的NAS消息中携带第一指示信息。
示例性的，第一指示信息可以包括原因值，该原因值用于指示该终端装置被拒绝的原因。比如，该原因值指示该终端装置没有签约REDACP接入技术。比如，该原因值指示该终端装置非法/无权使用第一业务类型的业务。示例性的，第一指示信息或者该原因值可以通过NAS SM拒绝消息携带。比如，该NAS拒绝消息可以是PDU会话建立拒绝消息。
可选地，该方法还可以包括：
S606a，该终端装置向接入网设备发送调整后的REDCAP信息，接入网设备通过接入和移动管理网元向会话管理网元发送调整后的REDCAP信息。
该终端装置接收到第一指示信息后，可以向接入网设备上报调整后的REDCAP信息，接入网设备通过接入和移动管理网元向会话管理网元发送调整后的REDCAP信息，会话管理网元可以确定是否允许该终端装置使用和调整后的REDCAP信息所对应的业务。比如，调整后的REDCAP信息可以指示REDCAP接入技术和第二业务类型，第二业务类型使用的接入技术为REDCAP接入技术，并且，第二REDCAP信息指示REDCAP接入技术和第二业务类型，则允许该终端装置使用和调整后的REDCAP信息所对应的业务。
可选地，该方法还可以包括：
S607a，该终端装置发起移动性更新过程，进行该终端装置的无线能力更新，从而更新该第一REDCAP信息。
即，该终端装置通过更新该终端装置的无线能力信息，向该接入网设备发送调整后的REDCAP信息。接入网设备可以通过接入和移动管理网元向会话管理网元发送调整后的REDCAP信息，会话管理网元可以确定是否允许该终端装置使用和调整后的REDCAP信 息所对应的业务。
应理解，S606a和S607a可以择其一执行。
可选地，该方法还可以包括：
S605b，会话管理网元向该终端装置发送第二指示信息，第二指示信息用于指示允许该终端装置使用和第一REDCAP信息所对应的业务。相应地，该终端装置接收第二指示信息。
若在S604中，会话管理网元确定允许该终端装置使用和第一REDCAP信息所对应的业务，则可以向该终端装置发送第二指示信息。
示例性的，第二指示信息可以通过PDU会话建立接受消息携带。
应理解，S605a和S606b可以择其一执行。
根据本申请提供的通信方法，会话管理网元可以获取第一REDCAP信息，并在获取到该终端装置的签约的REDCAP信息(即，第二REDCAP信息)后，可以对第一REDCAP信息进行验证，以明确该终端装置是否可以使用和第一REDCAP信息所对应的业务，这样，有利于保证终端装置仅仅能够使用其对应的业务。
图7是本申请提供的一种通信方法的示意性流程图。该方法700是第一网元为终端装置从第一网络向第二网络切换过程中的第二网络中的接入和移动管理网元的一个例子。示例性的，第一网络可以是4G或LTE网络、第二网络可以是5G或者NR网络，但本申请对此不作限定。
为便于理解和描述，以下将第二网络中的接入网设备记作：目标接入网设备，将第一网络中的接入网设备记作：源接入网设备；将第二网络中的接入和移动管理网元记作：目标接入和移动管理网元，将第一网络中的接入网设备记作：源接入和移动管理网元。例如，目标接入网设备可以是图中所示的gNB，源接入网设备可以是图中所示的eNB；目标接入和移动管理网元可以是图中所示的AMF，源目标接入和移动管理网元可以是图中所示的MME。下面对该方法700进行说明。
S701，源接入网设备向目标接入网设备发送切换请求消息。相应地，目标接入网设备接收来自源接入网设备的该切换请求消息。其中，该切换请求消息包括该终端装置的无线能力信息。
关于该源接入网设备如何获取到该终端装置的无线能力信息，可以参考步骤S401中对接入网设备获取终端装置的无线能力信息的说明，但应理解，此时接入和移动管理网元应为第一网络中的接入和移动管理网元，如MME。
应理解，异系统切换场景下，需要在步骤S701之前执行的流程可以参考现有技术，比如可以参考TS 23.502 Clause 4.111.2.2，这里不再详述。
S702，当目标接入和移动管理网元明确该终端装置从正在进行异系统切换，如明确该终端正在从LTE切往5G系统时，可以向目标接入网设备发送REDCAP指示信息。相应地，目标接入网设备接收该REDCAP指示信息。
其中，该REDCAP指示信息用于指示目标接入网设备根据该终端装置的无线能力信息确定该第一REDCAP信息。
应理解，702可以在S701之前执行，也可以在S701之后执行，本申请实施例对此不作限定。
S703，目标接入网设备根据该终端装置的无线能力信息，确定该第一REDCAP信息。
可选的，目标接入网设备可以根据接入和移动管理网元发送的REDCAP指示信息，从终端无线能力信息中确定第一REDCAP信息。
关于目标接入网设备如何根据该终端装置的无线能力信息确定该第一REDCAP信息，可以参考在步骤S401的方式二中对接入网设备根据该终端装置的无线能力信息确定该第一REDCAP信息的相关描述，这里不再赘述。
在本申请实施例中，S702为可选步骤。即，目标接入网设备可以根据目标接入和移动管理网元发送的REDCAP指示信息确定该第一REDCAP信息，也可以自主确定该第一REDCAP信息。
S704，确定该第一REDCAP信息后，目标接入网设备向目标接入和移动管理网元发送该第一REDCAP信息。相应地，目标接入和移动管理网元接收该第一REDCAP信息。
S705～S706，目标接入和移动管理网元向统一数据管理网元发送第二请求消息，统一数据管理网元根据该目标接入和移动管理网元的请求，向目标接入和移动管理网元返回第二REDCAP信息或者该终端装置的签约的信息。
示例性的，这里的第二请求消息中的内容可以和前文描述的第二请求消息中的内容相同，具体可以参见方法400中对步骤S402和S403的说明，这里不再赘述。
S707，目标接入和移动管理网元根据第一REDCAP信息和第二REDCAP信息，确定是否允许该终端装置使用和第一REDCAP信息所对应的业务。
该步骤与S330相同，可以参考S330。
可选地，该方法还可以包括：
S708a，目标接入和移动管理网元向源接入和移动管理网元发送第一指示信息，第一指示信息用于不允许该终端装置使用和第一REDCAP信息所对应的业务。相应地，该源接入和移动管理网元接收第一指示信息。
若在S707中，目标接入和移动管理网元确定不允许该终端装置使用和第一REDCAP信息所对应的业务，则可以向该终端装置发送第一指示信息。
示例性的，第一指示信息可以包括原因值，该原因值用于指示该终端装置被拒绝的原因。比如，该原因值指示该终端装置没有签约REDACP接入技术。比如，该原因值指示该终端装置非法/无权使用第一业务类型的业务。可选地，该方法还可以包括下述中的一个或多个步骤：
S709a，源接入和移动管理网元向源接入网设备发送切换失败信息。相应地，源接入网设备接收该切换失败信息。其中，该切换失败信息用于指示切换失败。
S710a，源接入网设备根据该切换失败信息进行目标接入网设备的重选或者触发该终端装置进行无线能力信息更新。
可选地，该方法还可以包括：
S708b，目标接入和移动管理网元向源接入和移动管理网元发送第二指示信息，第二指示信息用于指示允许该终端装置使用和第一REDCAP信息所对应的业务。相应地，该源接入和移动管理网元接收第二指示信息。
若在S707中，目标接入和移动管理网元确定允许该终端装置使用和第一REDCAP信息所对应的业务，则可以向该源接入和移动管理网元发送第二指示信息。
应理解，S708a和708b可以择其一执行。
根据本申请提供的通信方法，在异系统切换过程中，目标接入和移动管理网元可以获取第一REDCAP信息，并在获取到该终端装置的签约的REDCAP信息(即，第二REDCAP信息)后，可以对第一REDCAP信息进行验证，以明确该终端装置是否可以使用和第一REDCAP信息所对应的业务，这样，有利于保证终端装置仅仅能够使用其对应的业务。图8是本申请提供的一种通信方法的示意性流程图。该方法800是第一网元为终端装置从第一网络向第二网络切换过程中的第二网络中的目标接入网设备的一个例子。其中，第一网络可以是4G或LTE网络、第二网络可以是5G或者NR网络，但本申请对此不作限定。
为便于理解和描述，以下将第二网络中的接入网设备记作：目标接入网设备，将第一网络中的接入网设备记作：源接入网设备；将第二网络中的接入和移动管理网元记作：目标接入和移动管理网元，将第一网络中的接入网设备记作：源接入和移动管理网元。例如，目标接入网设备可以是图中所示的gNB，源接入网设备可以是图中所示的eNB；目标接入和移动管理网元可以是图中所示的AMF，源目标接入和移动管理网元可以是图中所示的MME。
S801～S803，与S801～S803相同，可以参考S801～S803。
S804，目标接入网设备向目标接入和移动管理网元发送第一请求消息。
示例性的，这里的第一请求消息中的内容可以和前文描述的第一请求消息中的内容相同，具体可以参见方法400中对步骤S402和S403的说明，这里不再赘述。
S805～S806，目标接入和移动管理网元向统一数据管理网元发送第二请求消息，以请求第二REDCAP信息或者该终端装置的签约的信息。统一数据管理网元根据该目标接入和移动管理网元的请求，向目标接入和移动管理网元返回第二REDCAP信息或者该终端装置的签约的信息。
应理解，第一请求消息和第二请求消息中的内容可以相同，但本申请对此不作限定。比如，第一请求消息包括第四指示信息时，第二请求消息可以不包括第四指示信息。
需要说明的是，S804为可选步骤。一种方式中，在目标接入和移动管理网元明确该终端装置从正在进行异系统切换后，目标接入和移动管理网元可以向统一数据管理网元请求第二REDCAP信息或者该终端装置的签约的信息。另一种方式中，目标接入和移动管理网元接收到目标接入网设备发送的第一请求消息后，再向统一数据管理网元请求第二REDCAP信息或者该终端装置的签约的信息。
S807，目标接入和移动管理网元向目标接入网设备发送第二REDCAP信息或者该终端装置的签约的信息。相应地，目标接入网设备接收第二REDCAP信息或者该终端装置的签约的信息。该终端装置的签约的信息包括第二REDCAP信息。
S808，目标接入网设备根据第一REDCAP信息和第二REDCAP信息，确定是否允许该终端装置使用和第一REDCAP信息所对应的业务。
该步骤与S330相同，可以参考S330。
应理解，S805～S808与S403～S406类似，可以参考S403～S406。
可选地，该方法还可以包括：
S809a，目标接入网设备向源接入网设备发送切换拒绝消息。
若在S808中，目标接入网设备确定不允许终端装置与目标接入网设备进行网络通信， 则可以向源接入网设备发送切换拒绝消息。
可选地，该方法还可以包括：
S810a，源接入网设备向该终端装置发送第一指示信息，第一指示信息用于指示不允许该终端装置使用和第一REDCAP信息所对应的业务。相应地，该终端装置接收第一指示信息。
源接入网设备接收到切换拒绝消息后，可以向该终端装置发送第一指示信息，通过第一指示信息向该终端装置指示不允许该终端装置使用和第一REDCAP信息所对应的业务。
示例性的，第一指示信息可以包括原因值，该原因值用于指示该终端装置被拒绝的原因。比如，该原因值指示第二REDCAP信息指示该终端装置没有签约REDACP接入技术。比如，该原因值指示该终端装置非法/无权使用第一业务类型的业务。S811a，源接入网设备根据该切换拒绝消息进行目标接入网设备的重选或者触发该终端装置进行无线能力信息更新。
应理解，S810a和S811a可以择其一执行。
可选地，该方法还可以包括：
S809b，目标接入网设备向源接入网设备发送切换执行消息。
若在S808中，目标接入网设备确定允许终端装置与目标接入网设备进行网络通信，则可以向源接入网设备发送切换执行消息。
S810b，源接入网设备向该终端装置发送第二指示信息。第二指示信息用于指示允许该终端装置使用和第一REDCAP信息所对应的业务。相应地，该终端装置接收第二指示信息。
源接入网设备接收到切换执行消息后，可以获知目标接入网设备允许该终端装置使用和第一REDCAP信息所对应的业务，从而可以向该终端装置发送第二指示信息。
根据本申请提供的通信方法，在异系统切换过程中，目标接入网设备可以获取第一REDCAP信息，并在获取到该终端装置的签约的REDCAP信息(即，第二REDCAP信息)后，可以对第一REDCAP信息进行验证，以明确该终端装置是否可以使用和第一REDCAP信息所对应的业务，这样，有利于保证终端装置仅仅能够使用其对应的业务。可选地，第二REDCAP信息还用于指示该至少一个业务类型对应的业务特征信息。比如，第二REDCAP信息在指示REDCAP接入技术和至少一个业务类型时，还可以指示该至少一个业务类型对应的业务特征信息。比如，业务特征信息可以是移动性信息和/或节能需求等。
在方法400中，在接入网设备确定允许该终端装置使用和第一REDCAP信息所对应的业务的场景下，该接入网设备还可以根据第二REDCAP信息，获得第一业务类型对应的业务特征信息。
在方法500中，在接入和移动管理网元确定允许该终端装置使用和第一REDCAP信息所对应的业务的场景下，该接入和移动管理网元还可以根据第二REDCAP信息，获得第一业务类型对应的业务特征信息，并且可以将该第一业务类型对应的业务特征信息发送给接入网设备。
在方法600中，在会话管理网元确定允许该终端装置使用和第一REDCAP信息所对应的业务的场景下，该会话管理网元还可以根据第二REDCAP信息，获得第一业务类型对应的业务特征信息，并且可以将该第一业务类型对应的业务特征信息发送给接入网设 备。
可选地，作为本申请一个实施例，在接入网设备获得该第一业务类型对应的业务特征信息后或者在接入网设备获知该终端装置的业务类型后，接入网设备可以向终端装置发送第三指示信息。其中，所述第三指示信息用于指示下述中的一项或多项：
终端装置保存本次RRC连接建立过程中所使用的定时提前量TA值，并在下一次RRC连接建立时使用；或者，
终端装置降低进行邻区测量时的频率；或者，
终端装置保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
示例性的，在该第一业务类型对应的业务特征信息为终端装置固定位置或者终端装置用于视频监控场景的情况下，接入网设备可以发送第三指示信息。
可选地，作为本申请一个实施例，在接入网设备获得该第一业务类型对应的业务特征信息后或业务类型后，接入网设备可以发送广播信息。其中，该广播信息包括REDCAP的接入技术指示信息和优化指示信息，优化信息指示用于指示接入技术为第一无线接入技术的终端装置是否根据优化指示信息开启优化功能，优化功能包括下述中的一项或多项：
保存本次RRC连接建立过程中所使用的定时提前量TA值，并在下一次RRC连接建立时使用；或者，
降低进行邻区测量时的频率；或者，
保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
示例性的，在该第一业务类型对应的业务特征信息为终端装置固定位置或者终端装置用于视频监控场景的情况下，接入网设备可以发送广播信息。
应理解，本申请实施例中出现的各个术语的解释或说明可以在各个实施例中互相参考或解释，对此不作限定。
还应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。上述各个过程涉及的各种数字编号或序号仅为描述方便进行的区分，而不应对本申请实施例的实施过程构成任何限定。
另外，上文描述的方法主要涉及REDCAP技术，但应理解，该方法也可以扩展到其他技术，比如扩展到6G或者6.5G技术等。
上文结合图3至图8描述了本申请提供的方法，下面对本申请提供的装置进行说明。
图9是本申请提供的通信装置的示意性框图。如图9所示，该通信装置2000可以包括收发单元2100和处理单元2200。
该收发单元2100可以包括发送单元和/或接收单元。该收发单元2100可以是收发器(包括发射器和/或接收器)、输入/输出接口(包括输入和/或输出接口)、管脚或电路等。该收发单元2100可以用于执行上述方法实施例中发送和/或接收的步骤。该处理单元2200可以是处理器(可以包括一个多个)、具有处理器功能的处理电路等，可以用于执行上述方法实施例中除发送接收外的其它步骤。
可选地，该通信装置还可以包括存储单元，该存储单元可以是存储器、内部存储单元(例如，寄存器、缓存等)、外部的存储单元(例如，只读存储器、随机存取存储器等)等。该存储单元用于存储指令，该处理单元2200执行该存储单元所存储的指令，以使该 通信装置执行上述方法。
一种设计中，该通信装置2000可以对应于上述方法实施例中的第一网元，如方法300中的第一网元、方法400中的接入网设备、方法500中的接入和移动管理网元、方法600中的会话管理网元、方法700中的目标接入和移动管理网元、或者方法800中的目标接入网设备，且可以执行第一网元所执行的操作。
具体地，收发单元2100用于，获取来自终端装置的第一REDCAP信息和所述终端装置的签约的第二REDCAP信息；处理单元2200用于，根据所述第一REDCAP信息和所述第二REDCAP信息，确定是否允许所述终端装置使用和所述第一REDCAP信息所对应的业务。
可选地，所述第一REDCAP信息用于指示REDCAP接入技术，所述第二REDCAP信息用于指示所述终端装置是否签约了所述REDCAP接入技术。
可选地，所述第一REDCAP信息用于指示REDCAP接入技术和第一业务类型，所述第一业务类型使用的接入技术为REDCAP接入技术，所述第二REDCAP信息用于指示所述REDCAP接入技术和至少一个业务类型，所述至少一个业务类型使用的接入技术为所述REDCAP接入技术。
可选地，所述第一REDCAP信息用于指示第一类型的REDCAP接入技术，所述第二REDCAP信息用于指示至少一个类型的REDCAP接入技术，不同类型的REDCAP接入技术对应的业务类型不同。
可选地，所述收发单元2100还用于，向所述终端装置发送第一指示信息，所述第一指示信息用于指示所述终端装置不能使用和所述第一REDCAP信息所对应的业务。
可选地，所述第一指示信息包括原因值，所述原因值用于指示所述终端装置被拒绝的原因。
可选地，所述装置2000为接入网设备。
可选地，所述收发单元2100具体用于，接收来自所述终端装置的无线资源控制RRC消息，所述RRC消息包括所述第一REDCAP信息。
可选地，所述收发单元2100具体用于，接收来自所述终端装置的无线能力信息；所述处理单元2200具体用于，根据所述无线能力信息确定所述第一REDCAP信息。
可选地，所述收发单元2100具体用于，接收来自接入和移动管理网元的第一消息，所述第一消息包括所述第一REDCAP信息。
可选地，所述收发单元2100具体用于，接收来自接入和移动管理网元的所述终端装置的无线能力信息；所述处理单元2200具体用于，根据所述无线能力信息确定所述第一REDCAP信息。
可选地，所述装置2000为所述终端装置从第一网络向第二网络切换过程中的所述第二网络中的接入网设备。
可选地，所述收发单元2100具体用于，接收来自所述第一网络中的接入网设备的所述终端装置的无线能力信息；所述收发单元2200具体用于，根据所述无线能力信息确定所述第一REDCAP信息。
可选地，所述收发单元2100还用于，接收来自所述第二网络中的接入和移动管理网元发送的REDCAP指示信息，所述REDCAP指示信息用于指示所述装置2000根据所述 无线能力信息确定所述第一REDCAP信息。
可选地，所述收发单元还用于，根据所述第一REDCAP信息，向接入和移动管理网元发送请求信息，所述请求信息用于请求所述接入和移动管理网元从统一数据管理网元获取所述第二REDCAP信息；接收来自所述接入和移动管理网元的所述第二REDCAP信息。
可选地，所述装置2000为接入和移动管理网元。
可选地，所述收发单元2100具体用于，接收来自所述终端装置的NAS消息，所述NAS消息包括所述第一REDCAP信息；或者，接收来自接入网设备的所述第一REDCAP信息。
可选地，所述收发单元2100还用于，向所述接入网设备发送所述终端装置的无线能力信息，所述无线能力信息用于所述接入网设备确定所述第一REDCAP信息。
可选地，所述装置2000为所述终端装置从第一网络向第二网络切换过程中的所述第二网络中的接入和移动管理网元。
可选地，所述收发单元2100具体用于，接收来自所述第二网络中的接入网设备的所述第一REDCAP信息，所述第一REDCAP信息为所述第二网络中的接入网设备根据来自所述第一网络中的接入网设备的所述终端装置的无线能力信息确定的。
可选地，所述收发单元2100还用于，向所述第二网络中的接入网设备发送REDCAP指示信息，所述REDCAP指示信息用于指示所述第二网络中的接入网设备根据所述无线能力信息确定所述第一REDCAP信息。
可选地，所述装置2000为会话管理网元。
可选地，所述收发单元2100具体用于，接收来自接入和移动管理网元的所述第一REDCAP信息。
可选地，所述收发单元2100具体用于，根据所述第一REDCAP信息，向统一数据管理网元发送请求信息，所述请求信息用于请求所述第二REDCAP信息；接收来自所述统一数据管理网元的所述第二REDCAP信息。
可选地，所述第二REDCAP信息还用于指示所述至少一个业务类型对应的业务特征信息。
可选地，所述收发单元2100还用于，向所述终端装置发送第三指示信息，所述第三指示信息用于指示下述中的一项或多项：所述终端装置保存本次RRC连接建立过程中所使用的定时提前量TA值，并在下一次RRC连接建立时使用；或者，所述终端装置降低进行邻区测量时的频率；或者，所述终端装置保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
可选地，所述收发单元2100还用于，发送广播信息，所述广播信息包括所述REDCAP接入技术指示信息和优化指示信息，所述优化信息指示用于指示接入技术为所述REDCAP接入技术的终端装置是否根据所述优化指示信息开启优化功能，所述优化功能包括下述中的一项或多项：保存本次RRC连接建立过程中所使用的定时提前量TA值，并在下一次RRC连接建立时使用；或者，降低进行邻区测量时的频率；或者，保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
应理解，收发单元2100以及处理单元2200还可以执行上述相应方法中由相应的第一网元所执行的其他操作，这里不再一一详述。
另一种设计中，该通信装置2000可以对应于上述方法实施例中的终端装置，且可以执行终端装置所执行的操作。
具体地，收发单元2100用于，发送第一REDCAP信息；接收来自第一网元的指示信息，所述示信息用于指示是否允许所述装置2000使用和所述第一REDCAP信息所对应的业务可选地，所述收发单元2100还用于，根据所述指示信息，发送调整后的REDCAP信息，所述调整后的REDCAP信息与所述第一REDCAP信息不同。
可选地，所述第一网元为接入网设备。
可选地，所述收发单元2100还用于，接收来自所述第一网元的第三指示信息，所述第三指示信息用于指示下述中的一项或多项：所述装置2000保存本次RRC连接建立过程中所使用的定时提前量TA值，并在下一次RRC连接建立时使用；或者，所述装置2000降低进行邻区测量时的频率；或者，所述装置2000保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
可选地，所述收发单元2100还用于，接收来自所述第一网元的广播信息，所述广播信息包括所述REDCAP接入技术指示信息和优化指示信息，所述优化信息指示用于指示接入技术为所述REDCAP接入技术的装置2000是否根据所述优化指示信息开启优化功能，所述优化功能包括下述中的一项或多项：保存本次RRC连接建立过程中所使用的定时提前量TA值，并在下一次RRC连接建立时使用；或者，降低进行邻区测量时的频率；或者，保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
应理解，收发单元2100以及处理单元2200还可以执行上述方法实施例由终端装置所执行的其他操作，这里不再一一详述。
又一种设计中，该通信装置2000可以对应于上述方法实施例中的统一数据管理网元，且可以执行统一数据管理网元所执行的操作。
应理解，上述各个单元的划分仅仅是功能上的划分，实际实现时可能会有其它的划分方法。
还应理解，上述处理单元可以通过硬件来实现也可以通过软件来实现，或者可以通过软硬结合的方式实现。
还应理解，该通信装置2000为接入网设备时，该通信装置中的收发单元2100可对应于图10中示出的接入网设备2000中的RRU 3100，该通信装置中的处理单元2200可对应于图10中示出的接入网设备2000中的BBU 3200。通信装置2000为配置于接入网设备中的芯片时，该通信装置中的收发单元2100可以为输入/输出接口。
还应理解，该通信装置2000为终端装置时，该通信装置2000中的收发单元2100可对应于图11中示出的终端装置4000中的收发器4002，该通信装置2000中的处理单元2200可对应于图11中示出的终端装置4000中的处理器4001。
图10是本申请实施例提供的接入网设备的结构示意图，例如可以为基站的结构示意图。该接入网设备3000可实现上述方法实施例中接入网设备的功能。
如图所示，该接入网设备3000可以包括一个或多个射频单元，如远端射频单元(remote radio unit，RRU)3100和一个或多个基带单元(BBU)(也可称为分布式单元(DU))3200。所述RRU 3100可以称为收发单元或通信单元，与图9中的收发单元2100对应。
可选地，该收发单元3100还可以称为收发机、收发电路、或者收发器等等，其可以包括至少一个天线3101和射频单元3102。可选地，收发单元3100可以包括接收单元和发送单元，接收单元可以对应于接收器(或称接收机、接收电路)，发送单元可以对应于发射器(或称发射机、发射电路)。所述RRU 3100部分主要用于射频信号的收发以及射频信号与基带信号的转换。所述BBU 3200部分主要用于进行基带处理，对基站进行控制等。所述RRU 3100与BBU 3200可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。
所述BBU 3200为基站的控制中心，也可以称为处理单元，可以与图9中的处理单元2200对应，主要用于完成基带处理功能，如信道编码，复用，调制，扩频等等。例如所述BBU(处理单元)可以用于控制基站执行上述方法实施例中关于接入网设备的操作流程。
在一个示例中，所述BBU 3200可以由一个或多个单板构成，多个单板可以共同支持单一接入制式的无线接入网(如LTE网)，也可以分别支持不同接入制式的无线接入网(如LTE网，5G网或其他网)。所述BBU 3200还包括存储器3201和处理器3202。所述存储器3201用以存储必要的指令和数据。所述处理器3202用于控制基站进行必要的动作，例如用于控制基站执行上述方法实施例中关于接入网设备的操作流程。所述存储器3201和处理器3202可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
应理解，图10所示的接入网设备3000能够实现前述方法实施例中涉及接入网设备的各个过程。接入网设备3000中的各个模块的操作或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详细描述。
上述BBU 3200可以用于执行前面方法实施例中描述的由接入网设备内部实现的动作，而RRU 3100可以用于执行前面方法实施例中描述的接入网设备发送接收的动作。具体请见前面方法实施例中的描述，此处不再赘述。
图11是本申请实施例提供的终端4000的结构示意图。如图所示，该终端4000包括处理器4001和收发器4002。可选地，该终端4000还可以包括存储器4003。其中，处理器4001、收发器4002和存储器4003之间可以通过内部连接通路互相通信，传递控制和/或数据信号，该存储器4003用于存储计算机程序，该处理器4001用于从该存储器4003中调用并运行该计算机程序，以控制该收发器4002收发信号。
上述处理器4001和存储器4003可以合成一个处理装置4004，处理器4001用于执行存储器4003中存储的程序代码来实现上述功能。应理解，图中所示的处理装置4004仅为示例。在具体实现时，该存储器4003也可以集成在处理器4001中，或者独立于处理器4001。本申请对此不做限定。
上述终端4000还可以包括天线4010，用于将收发器4002输出的上行数据或上行控制信令通过无线信号发送出去。
应理解，图11所示的终端4000能够实现前述方法实施例中涉及终端装置所能实现的功能。终端4000中的各个模块的操作或功能，分别为了实现上述方法实施例中的相应流 程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详细描述。
可选地，上述终端4000还可以包括电源4005，用于向终端中的各种器件或电路提供电源。
除此之外，为了使得终端的功能更加完善，该终端4000还可以包括输入单元4006、显示单元4007、音频电路4008、摄像头4009和传感器4011等中的一个或多个，所述音频电路还可以包括扬声器40081、麦克风40082等。
应理解，所述处理装置4004或处理器4001可以是一个芯片。例如，该处理装置4004或处理器4001可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
本申请中的存储器(如存储器4003)可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(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)。
图12是本申请实施例提供的一种通信装置5000的示意性框图。本申请中所涉及的任一网元，如接入网设备、第一网元、终端装置等都可以由图12所示的通信装置来实现。
应理解，通信装置5000可以是实体设备，也可以是实体设备的部件(例如，集成电路，芯片等等)，还可以是实体设备中的功能模块。
如图12所示，该通信装置5000包括：一个或多个处理器5001。处理器5001可以存储用于执行本申请实施例的方法的执行指令。可选地，处理器5001中可以调用接口实现接收和发送功能。所述接口可以是逻辑接口或物理接口，对此不作限定。例如，接口可以是收发电路，或是接口电路。用于实现接收和发送功能的收发电路、或接口电路可以是分 开的，也可以集成在一起。上述收发电路或接口电路可以用于代码/数据的读写，或者，上述收发电路或接口电路可以用于信号的传输或传递。
可选地，接口可以通过收发器实现。可选地，该通信装置5000还可以包括收发器5003。所述收发器5003可以称为收发单元、收发机、收发电路或者收发器等，用于实现收发功能。
可选地，该通信装置5000还可以包括存储器5002。本申请实施例对存储器5002的具体部署位置不作具体限定，该存储器可以集成于处理器中，也可以是独立于处理器之外。对于该通信装置5000不包括存储器的情形，该通信装置5000具备处理功能即可，存储器可以部署在其他位置(如，云系统)。
处理器5001、存储器5002和收发器5003之间通过内部连接通路互相通信，传递控制和/或数据信号。
可以理解的是，尽管并未示出，通信装置5000还可以包括其他装置，例如输入装置、输出装置、电池等。
可选的，在一些实施例中，存储器5002可以存储用于执行本申请实施例的方法的执行指令。处理器5001可以执行存储器5002中存储的指令结合其他硬件(例如收发器5003)完成本文所示方法执行的步骤，具体工作过程和有益效果可以参见本文中方法实施例中的描述。
本申请实施例揭示的方法可以应用于处理器5003中，或者由处理器5003实现。处理器5003可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存取存储器(random access memory，RAM)、闪存、只读存储器(read-only memory，ROM)、可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的指令，结合其硬件完成上述方法的步骤。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行前述任一方法实施例中任一网元(如，接入网设备、第一网元、终端装置、或者统一数据管理网元)的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行前述任一方法实施例中任一网元的方法。
根据本申请实施例提供的方法，本申请还提供一种系统，其包括下述中的一项或多项：接入网设备、会话管理网元、接入和移动管理网元、或者统一数据管理网元。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器用于执行上述任一方法实施例中的方法。
应理解，上述处理装置可以是一个芯片。例如，该处理装置可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程或执行线程中，部件可位于一个计算机上或分布在2个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地或远程进程来通信。
应理解，说明书通篇中提到的“实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各个实施例未必一定指相同的 实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
应理解，在本申请实施例中，编号“第一”、“第二”…仅仅为了区分不同的对象，比如为了区分不同的网络设备，并不对本申请实施例的范围构成限制，本申请实施例并不限于此。
还应理解，在本申请中，“当…时”、“若”以及“如果”均指在某种客观情况下网元会做出相应的处理，并非是限定时间，且也不要求网元实现时一定要有判断的动作，也不意味着存在其它限定。
还应理解，在本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。
还应理解，在本申请各实施例中，“A对应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
还应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
本申请中出现的类似于“项目包括如下中的一项或多项：A，B，以及C”表述的含义，如无特别说明，通常是指该项目可以为如下中任一个：A；B；C；A和B；A和C；B和C；A，B和C；A和A；A，A和A；A，A和B；A，A和C，A，B和B；A，C和C；B和B，B，B和B，B，B和C，C和C；C，C和C，以及其他A，B和C的组合。以上是以A，B和C共3个元素进行举例来说明该项目的可选用条目，当表达为“项目包括如下中至少一种：A，B，……，以及X”时，即表达中具有更多元素时，那么该项目可以适用的条目也可以按照前述规则获得。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各 个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (36)

  1. 一种通信方法，其特征在于，包括：
    第一网元获取来自终端装置的第一低能力REDCAP信息；
    所述第一网元获取所述终端装置的签约的第二REDCAP信息；
    所述第一网元根据所述第一REDCAP信息和所述第二REDCAP信息，确定是否允许所述终端装置使用和所述第一REDCAP信息所对应的业务。
  2. 如权利要求1所述的方法，其特征在于，所述第一REDCAP信息用于指示REDCAP接入技术和第一业务类型，所述第一业务类型使用的接入技术为REDCAP接入技术，所述第二REDCAP信息用于指示所述REDCAP接入技术和至少一个业务类型，所述至少一个业务类型使用的接入技术为所述REDCAP接入技术。
  3. 如权利要求1所述的方法，其特征在于，所述第一REDCAP信息用于指示第一类型的REDCAP接入技术，所述第二REDCAP信息用于指示至少一个类型的REDCAP接入技术，不同类型的REDCAP接入技术对应的业务类型不同。
  4. 如权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网元向所述终端装置发送第一指示信息，所述第一指示信息用于指示不允许所述终端装置使用和所述第一REDCAP信息所对应的业务。
  5. 如权利要求4所述的方法，其特征在于，所述第一指示信息包括原因值，所述原因值用于指示所述终端装置被拒绝的原因。
  6. 如权利要求1至5中任一项所述的方法，其特征在于，所述第一网元为接入网设备。
  7. 如权利要求6所述的方法，其特征在于，所述第一网元获取来自终端装置的第一REDCAP信息，包括：
    所述第一网元接收来自所述终端装置的无线资源控制RRC消息，所述RRC消息包括所述第一REDCAP信息；或者，
    所述第一网元接收来自所述终端装置的无线能力信息，并根据所述无线能力信息确定所述第一REDCAP信息；或者，
    所述第一网元接收来自接入和移动管理网元的第一消息，所述第一消息包括所述第一REDCAP信息；或者，
    所述第一网元接收来自接入和移动管理网元的所述终端装置的无线能力信息，并根据所述无线能力信息确定所述第一REDCAP信息。
  8. 如权利要求1至5中任一项所述的方法，其特征在于，所述第一网元为所述终端装置从第一网络向第二网络切换过程中的所述第二网络中的接入网设备。
  9. 如权利要求8所述的方法，其特征在于，所述第一网元获取来自终端装置的第一REDCAP信息，包括：
    所述第一网元接收来自所述第一网络中的接入网设备的所述终端装置的无线能力信息；
    所述第一网元根据所述无线能力信息确定所述第一REDCAP信息。
  10. 如权利要求9所述的方法，其特征在于，在所述第一网元根据所述无线能力信息确定所述第一信息之前，所述还包括：
    所述第一网元接收来自所述第二网络中的接入和移动管理网元发送的REDCAP指示信息，所述REDCAP指示信息用于指示所述第一网元根据所述无线能力信息确定所述第一REDCAP信息。
  11. 如权利要求6至10中任一项所述的方法，其特征在于，所述第一网元获取所述终端装置的签约的第二REDCAP信息，包括：
    所述第一网元根据所述第一REDCAP信息，向接入和移动管理网元发送请求信息，所述请求信息用于请求所述接入和移动管理网元从统一数据管理网元获取所述第二REDCAP信息；
    所述第一网元接收来自所述接入和移动管理网元的所述第二REDCAP信息。
  12. 如权利要求1至5中任一项所述的方法，其特征在于，所述第一网元为接入和移动管理网元。
  13. 如权利要求12所述的方法，其特征在于，所述第一网元获取来自终端装置的第一REDCAP信息，包括：
    所述第一网元接收来自所述终端装置的NAS消息，所述NAS消息包括所述第一REDCAP信息；或者，
    所述第一网元接收来自接入网设备的所述第一REDCAP信息。
  14. 如权利要求13所述的方法，其特征在于，在所述第一网元接收来自接入网设备的所述第一REDCAP信息之前，所述方法还包括：
    所述第一网元向所述接入网设备发送所述终端装置的无线能力信息，所述无线能力信息用于所述接入网设备确定所述第一REDCAP信息。
  15. 如权利要求1至5中任一项所述的方法，其特征在于，所述第一网元为所述终端装置从第一网络向第二网络切换过程中的所述第二网络中的接入和移动管理网元。
  16. 如权利要求15所述的方法，其特征在于，所述第一网元获取来自终端装置的第一REDCAP信息，包括：
    所述第一网元接收来自所述第二网络中的接入网设备的所述第一REDCAP信息，所述第一REDCAP信息为所述第二网络中的接入网设备根据来自所述第一网络中的接入网设备的所述终端装置的无线能力信息确定的。
  17. 如权利要求16所述的方法，其特征在于，在所述第一网元接收来自所述第二网络中的接入网设备的所述第一REDCAP信息之前，所述方法还包括：
    所述第一网元向所述第二网络中的接入网设备发送REDCAP指示信息，所述REDCAP指示信息用于指示所述第二网络中的接入网设备根据所述无线能力信息确定所述第一REDCAP信息。
  18. 如权利要求1至5中任一项所述的方法，其特征在于，所述第一网元为会话管理网元。
  19. 如权利要求18所述的方法，其特征在于，所述第一网元获取来自终端装置的第一REDCAP信息，包括：
    所述第一网元接收来自接入和移动管理网元的所述第一REDCAP信息。
  20. 如权利要求12至19中任一项所述的方法，其特征在于，所述第一网元获取终端装置的签约的第二REDCAP信息，包括：
    所述第一网元根据所述第一REDCAP信息，向统一数据管理网元发送请求信息，所述请求信息用于请求所述第二REDCAP信息；
    所述第一网元接收来自所述统一数据管理网元的所述第二REDCAP信息。
  21. 如权利要求2所述的方法，其特征在于，所述第二REDCAP信息还用于指示所述至少一个业务类型对应的业务特征信息。
  22. 如权利要求6所述的方法，其特征在于，所述方法还包括：
    所述第一网元向所述终端装置发送第三指示信息，所述第三指示信息用于指示下述中的一项或多项：
    所述终端装置保存本次无线资源控制RRC连接建立过程中所使用的定时提前量TA值，并在下一次RRC连接建立时使用；或者，
    所述终端装置降低进行邻区测量时的频率；或者，
    所述终端装置保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
  23. 如权利要求6所述的方法，其特征在于，所述方法还包括：
    所述第一网元发送广播信息，所述广播信息包括所述REDCAP接入技术指示信息和优化指示信息，所述优化信息指示用于指示接入技术为所述REDCAP接入技术的终端装置是否根据所述优化指示信息开启优化功能，所述优化功能包括下述中的一项或多项：
    保存本次无线资源控制RRC连接建立过程中所使用的定时提前量TA值，并在下一次RRC连接建立时使用；或者，
    降低进行邻区测量时的频率；或者，
    保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
  24. 一种通信方法，其特征在于，包括：
    终端装置发送第一低能力REDCAP信息；
    所述终端装置接收来自第一网元根据所述第一REDCAP信息发送的指示信息，所述指示信息用于指示是否允许所述终端装置使用和所述第一REDCAP信息所对应的业务。
  25. 如权利要求22所述的方法，其特征在于，所述方法还包括：
    所述终端装置根据所述指示信息，发送调整后的REDCAP信息，所述调整后的REDCAP信息与所述第一REDCAP信息不同。
  26. 如权利要求24或25所述的方法，其特征在于，所述第一网元为接入网设备。
  27. 如权利要求26所述的方法，其特征在于，所述方法还包括：
    所述终端装置接收来自所述第一网元的第三指示信息，所述第三指示信息用于指示下述中的一项或多项：
    所述终端装置保存本次无线资源控制RRC连接建立过程中所使用的定时提前量TA值，并在下一次RRC连接建立时使用；或者，
    所述终端装置降低进行邻区测量时的频率；或者，
    所述终端装置保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
  28. 如权利要求26所述的方法，其特征在于，所述方法还包括：
    所述终端装置接收来自所述第一网元的广播信息，所述广播信息包括所述REDCAP接入技术指示信息和优化指示信息，所述优化信息指示用于指示接入技术为所述REDCAP接入技术的终端装置是否根据所述优化指示信息开启优化功能，所述优化功能包括下述中的一项或多项：
    保存本次无线资源控制RRC连接建立过程中所使用的定时提前量TA值，并在下一次RRC连接建立时使用；或者，
    降低进行邻区测量时的频率；或者，
    保存本次RRC连接建立过程中所使用的发射功率，并在下一次RRC连接建立时使用。
  29. 一种通信系统，其特征在于，包括：第一网元和第二网元；
    所述第二网元向所述第一网元发送终端装置的第一低能力REDCAP信息；
    所述第一网元根据所述第一REDCAP信息，获取所述终端装置的签约的第二REDCAP信息；
    所述第一网元根据所述第一REDCAP信息和所述第二REDCAP信息，确定是否允许所述终端装置使用和所述第一REDCAP信息所对应的业务。
  30. 如权利要求29所述的系统，其特征在于，所述第二网元为接入和移动管理网元，且所述第一网元为接入网设备；或者，
    所述第二网元为接入网设备，且所述第一网元为接入和移动管理网元；或者，
    所述第二网元为接入和移动管理网元，且所述第一网元为会话管理网元；或者，
    所述第二网元为所述终端装置从第一网络向第二网络切换过程中的所述第一网络中的接入网设备，且所述第一网元为所述第二网络中的接入网设备。
  31. 如权利要求29或30所述的系统，其特征在于，所述系统还包括统一数据管理网元；
    以及，所述第一网元根据所述第一REDCAP信息，获取所述第二REDCAP信息，包括：
    所述第一网元根据所述第一REDCAP信息，从所述统一数据管理网元获取所述第二REDCAP信息。
  32. 一种通信装置，其特征在于，包括用于实现如权利要求1至23中任一项所述的方法的单元。
  33. 一种通信装置，其特征在于，包括用于实现如权利要求24至28中任一项所述的方法的单元。
  34. 一种通信装置，其特征在于，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得所述装置执行如权利要求1至23中任一项所述的方法，或24至28中任一项所述的方法。
  35. 一种可读存储介质，其上存储有计算机程序或指令，其特征在于，所述计算机程序或指令被执行时使得计算机执行如权利要求1至23中任一项所述的方法，或24至28中任一项所述的方法。
  36. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行：如权利要求1至23中任一项所述的方法，或24至28中任一项所述的方 法。
PCT/CN2021/080479 2021-03-12 2021-03-12 通信方法和通信装置 WO2022188156A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2021/080479 WO2022188156A1 (zh) 2021-03-12 2021-03-12 通信方法和通信装置
CN202180081172.4A CN116569571A (zh) 2021-03-12 2021-03-12 通信方法和通信装置
EP21929630.8A EP4294059A4 (en) 2021-03-12 2021-03-12 COMMUNICATION METHOD AND COMMUNICATION APPARATUS
US18/461,905 US20230413039A1 (en) 2021-03-12 2023-09-06 Communication method and communication apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/080479 WO2022188156A1 (zh) 2021-03-12 2021-03-12 通信方法和通信装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/461,905 Continuation US20230413039A1 (en) 2021-03-12 2023-09-06 Communication method and communication apparatus

Publications (1)

Publication Number Publication Date
WO2022188156A1 true WO2022188156A1 (zh) 2022-09-15

Family

ID=83226219

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/080479 WO2022188156A1 (zh) 2021-03-12 2021-03-12 通信方法和通信装置

Country Status (4)

Country Link
US (1) US20230413039A1 (zh)
EP (1) EP4294059A4 (zh)
CN (1) CN116569571A (zh)
WO (1) WO2022188156A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018126823A1 (zh) * 2017-01-06 2018-07-12 中兴通讯股份有限公司 信息发送、资源配置方法及装置、控制节点、网元、存储介质
WO2020190484A1 (en) * 2019-03-18 2020-09-24 Qualcomm Incorporated Priority handling for a random access message that includes a preamble and a payload

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018126823A1 (zh) * 2017-01-06 2018-07-12 中兴通讯股份有限公司 信息发送、资源配置方法及装置、控制节点、网元、存储介质
WO2020190484A1 (en) * 2019-03-18 2020-09-24 Qualcomm Incorporated Priority handling for a random access message that includes a preamble and a payload

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CMCC: "Discussion on design principles and definition for RedCap device type", 3GPP DRAFT; R1-2008019, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20201026 - 20201113, 16 October 2020 (2020-10-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051939435 *
LG ELECTRONICS INC.: "Discussion on intended use cases for RedCap UEs", 3GPP DRAFT; R2-2100770, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic meeting; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051973877 *
See also references of EP4294059A4 *
XIAOMI COMMUNICATIONS: "Discussion on Identification and UE access restrictions for Redcap devices", 3GPP DRAFT; R2-2008947, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20201102 - 20201113, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051941997 *

Also Published As

Publication number Publication date
EP4294059A4 (en) 2024-07-10
US20230413039A1 (en) 2023-12-21
CN116569571A (zh) 2023-08-08
EP4294059A1 (en) 2023-12-20

Similar Documents

Publication Publication Date Title
US20220217611A1 (en) Service Configuration Method, Communication Apparatus, and Communication System
WO2019196643A1 (zh) 通信的方法和通信装置
US12058745B2 (en) System and method for RRC connection using a relay terminal
WO2021136211A1 (zh) 授权结果的确定方法及装置
US11818652B2 (en) Method and apparatus for selecting network slices in wireless communication system
WO2020135850A1 (zh) 通信方法和装置
US20230029714A1 (en) Authorization method, policy control function device, and access and mobility management function device
US11729599B2 (en) Communication system
WO2022022347A1 (zh) 接入网络的方法、通信系统和通信装置
US20230254922A1 (en) Multipath transmission method and communication apparatus
US11259362B2 (en) Method for repeatedly transmitting data and device
US20240172084A1 (en) Data transmission method and apparatus
WO2023160199A1 (zh) 一种接入通信网络的方法和装置
WO2022199451A1 (zh) 会话切换的方法和装置
WO2022170798A1 (zh) 确定策略的方法和通信装置
WO2020024865A1 (zh) 一种会话对应关系的管理方法和终端设备
WO2021163894A1 (zh) 一种基于中继的通信方法及装置
US20230136984A1 (en) Method and apparatus for verifying compliance with ue route selection policy
WO2023020481A1 (zh) 用于传输数据的方法和装置
WO2023273880A1 (zh) 传输方式切换的方法和相关装置
WO2024000412A1 (zh) 通信方法和通信装置
JP7053878B2 (ja) セルアクセスプロシージャの改善
US20220360969A1 (en) Communication method and apparatus
KR20240060670A (ko) 통신 방법 및 장치
US20230071815A1 (en) Path section between uu and pc5

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180081172.4

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2021929630

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021929630

Country of ref document: EP

Effective date: 20230914

NENP Non-entry into the national phase

Ref country code: DE