WO2025007249A1 - 通信方法和设备 - Google Patents

通信方法和设备 Download PDF

Info

Publication number
WO2025007249A1
WO2025007249A1 PCT/CN2023/105564 CN2023105564W WO2025007249A1 WO 2025007249 A1 WO2025007249 A1 WO 2025007249A1 CN 2023105564 W CN2023105564 W CN 2023105564W WO 2025007249 A1 WO2025007249 A1 WO 2025007249A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
network element
sor
message
information
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2023/105564
Other languages
English (en)
French (fr)
Inventor
杨皓睿
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
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 Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to CN202380099898.XA priority Critical patent/CN121488570A/zh
Priority to PCT/CN2023/105564 priority patent/WO2025007249A1/zh
Publication of WO2025007249A1 publication Critical patent/WO2025007249A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • the present application relates to the field of communications, and more particularly, to a communication method and device.
  • the terminal equipment is required to support the Steering of Roaming (SOR) technology.
  • SOR is a technology that allows the terminal equipment's Home Public Land Mobile Network (HPLMN) to switch the terminal equipment to another Visited Public Land Mobile Network (VPLMN).
  • HPLMN Home Public Land Mobile Network
  • VPLMN Visited Public Land Mobile Network
  • the network side sends the SOR information to the terminal equipment, which includes the priority list of VPLMN and access technology, the timer corresponding to the service, and other contents; after receiving the SOR information, the user equipment (UE) enters the idle state after the timer expires, and then uses the priority list of VPLMN and access technology to perform network selection.
  • Zero-power terminals do not require internal batteries and are simple-designed terminal equipment.
  • the overall design of the SOR technology is too complicated for zero-power devices. Therefore, how to reduce the adverse effects of the SOR mechanism on zero-power devices is a technical problem that needs to be solved.
  • the embodiments of the present application provide a communication method and device, which can reduce the adverse effects of the SOR mechanism on zero-power devices.
  • the present application provides a communication method, including:
  • the terminal device sends a registration request message to the first network element, where the registration request message carries identification information of the terminal device.
  • the terminal device receives a registration acceptance message from the first network element.
  • the present application provides a communication method, including:
  • the first network element receives a second message from the second network element, where the second message carries identification information of the terminal device;
  • the first network element sends a registration acceptance message to the terminal device.
  • the present application provides a communication method, including:
  • the second network element sends a second message to the first network element, where the second message carries identification information of the terminal device.
  • the present application provides a communication method, including:
  • the third network element receives from the second network element identification information of the terminal device, the location of the terminal device, a frequency band supported by the terminal device, and at least one of a first indication; wherein the first indication is used to indicate whether the terminal device is a zero-power consumption terminal.
  • the third network element determines the SOR information of the terminal device.
  • the present application provides a communication method, including:
  • the access device receives a registration request message from a terminal device, where the registration request message carries identification information of the terminal device.
  • the access device forwards the registration request message to the first network element.
  • the present application provides a terminal device, including:
  • the first sending unit is used to send a registration request message to the first network element, where the registration request message carries identification information of the terminal device.
  • the first receiving unit is configured to receive a registration acceptance message from a first network element.
  • An embodiment of the present application provides a first network element, including:
  • a third receiving unit configured to receive a second message from a second network element, where the second message carries identification information of the terminal device
  • the second sending unit is used to send a registration acceptance message to the terminal device.
  • An embodiment of the present application provides a second network element, including:
  • the fifth sending unit is used to send a second message to the first network element, where the second message carries identification information of the terminal device.
  • the embodiment of the present application provides a third network element, including:
  • the seventh receiving unit is used to receive from the second network element the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device and at least one of the first indications; wherein the first indication is used to indicate whether the terminal device is a zero-power consumption terminal.
  • the fourth determining unit is used to determine the SOR information of the terminal device.
  • the present application provides an access device, including:
  • An eighth receiving unit is configured to receive a registration request message from a terminal device, where the registration request message carries identification information of the terminal device.
  • An eighth sending unit is used to forward the registration request message to the first network element.
  • the embodiment of the present application provides a terminal device, including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the above communication method.
  • An embodiment of the present application provides a chip for implementing the above-mentioned communication method.
  • the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned communication method.
  • An embodiment of the present application provides a computer-readable storage medium for storing a computer program.
  • the computer program When the computer program is executed by a device, the device executes the above-mentioned communication method.
  • An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above-mentioned communication method.
  • An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above-mentioned communication method.
  • the terminal device sends a registration request message to the first network element, the first network element receives a second message from the second network element according to the registration request message, and sends a registration acceptance message to the terminal device; the terminal device receives the registration acceptance message.
  • the first network element can determine the information carried in the registration acceptance message according to whether the terminal device is a zero-power device, so as to reduce the adverse effects of the SOR mechanism on zero-power devices.
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a zero-power consumption terminal.
  • FIG3 is a schematic diagram of a 5G system architecture.
  • FIG. 4 is a schematic flow chart of a communication method 400 according to an embodiment of the present application.
  • FIG5 is a schematic flow chart of a communication method 500 according to an embodiment of the present application.
  • FIG6A is a schematic flowchart of a communication method 600 according to an embodiment of the present application.
  • FIG6B is another schematic flowchart of a communication method 600 according to an embodiment of the present application.
  • FIG. 7A is a schematic flowchart of a communication method 700 according to an embodiment of the present application.
  • FIG. 7B is another schematic flowchart of a communication method 700 according to an embodiment of the present application.
  • FIG8 is a schematic flow chart of a communication method 800 according to an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a communication method 900 according to an embodiment of the present application.
  • FIG. 10 is an implementation flow chart of the first embodiment of the present application.
  • FIG11 is an implementation flow chart of the second embodiment of the present application.
  • FIG12 is an implementation flow chart of the third embodiment of the present application.
  • FIG. 13 is a schematic diagram of the structure of a terminal device 1300 according to an embodiment of the present application.
  • FIG. 14 is a schematic diagram of the structure of a terminal device 1400 according to an embodiment of the present application.
  • FIG. 15 is a schematic diagram of the structure of a first network element 1500 according to an embodiment of the present application.
  • FIG. 16 is a schematic diagram of the structure of a first network element 1600 according to an embodiment of the present application.
  • FIG. 17 is a schematic diagram of the structure of a second network element 1700 according to an embodiment of the present application.
  • FIG18 is a schematic diagram of the structure of a second network element 1800 according to an embodiment of the present application.
  • FIG19 is a schematic diagram of the structure of a third network element 1900 according to an embodiment of the present application.
  • FIG. 20 is a schematic diagram of the structure of a third network element 2000 according to an embodiment of the present application.
  • FIG. 21 is a schematic diagram of the structure of an access device 2100 according to an embodiment of the present application.
  • FIG. 22 is a schematic diagram of the structure of an access device 2200 according to an embodiment of the present application.
  • FIG. 23 is a schematic diagram of the structure of a communication device 2300 according to an embodiment of the present application.
  • FIG. 24 is a schematic structural diagram of a chip 2400 according to an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced long term evolution
  • NR New Radio
  • LTE-based access to unlicensed spectrum (LTE-U) systems LTE-based access to unlicensed spectrum (LTE-U) systems
  • NR-based access to unlicensed spectrum (NR-U) systems NTN-based access to unlicensed spectrum (NR-U) systems
  • NTN non-terrestrial communication networks
  • UMTS universal mobile telecommunication systems
  • WLAN wireless local area networks
  • WiFi wireless fidelity
  • 5G fifth-generation communication
  • D2D device to device
  • M2M machine to machine
  • MTC machine type communication
  • V2V vehicle to vehicle
  • V2X vehicle to everything
  • the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.
  • CA carrier aggregation
  • DC dual connectivity
  • SA standalone
  • the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.
  • the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.
  • UE user equipment
  • the terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in the next generation communication system such as the NR network, or a terminal device in the future evolved Public Land Mobile Network (PLMN) network, etc.
  • STAION, ST in a WLAN
  • a cellular phone a cordless phone
  • Session Initiation Protocol (SIP) phone Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).
  • the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.
  • VR virtual reality
  • AR augmented reality
  • the terminal device may also be a wearable device.
  • Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.
  • the network device may be a device for communicating with a mobile device.
  • the network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.
  • the network device may have a mobile feature, for example, the network device may be a mobile device.
  • the network device may be a satellite or a balloon station.
  • the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc.
  • the network device may also be a base station set up in a location such as land or water.
  • a network device may provide services for a cell, and a terminal device communicates with the network device through transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell.
  • the cell may be a cell corresponding to a network device (e.g., a base station).
  • the cell may belong to a macro base station or a base station corresponding to a small cell.
  • the small cells here may include: a metro cell, a micro cell, a pico cell, a femto cell, and a femto cell. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • Fig. 1 exemplarily shows a communication system 100.
  • the communication system includes a network device 110 and two terminal devices 120.
  • the communication system 100 may include multiple network devices 110, and each network device 110 may include other number of terminal devices 120 within its coverage area, which is not limited in the embodiment of the present application.
  • the communication system 100 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), but this is not limited to the embodiments of the present application.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment.
  • the access network equipment may be an evolutionary base station (evolutional node B, referred to as eNB or e-NodeB) macro base station, micro base station (also called “small base station”), pico base station, access point (AP), transmission point (TP) or new generation Node B (gNodeB) in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.
  • eNB evolutionary base station
  • AP access point
  • TP transmission point
  • gNodeB new generation Node B
  • LTE long-term evolution
  • NR next-generation
  • LAA-LTE authorized auxiliary access long-term evolution
  • the device with communication function in the network/system in the embodiment of the present application can be called a communication device.
  • the communication device may include a network device and a terminal device with communication function, and the network device and the terminal device may be specific devices in the embodiment of the present application, which will not be repeated here; the communication device may also include other devices in the communication system, such as a network controller, a mobile management entity and other network entities, which are not limited in the embodiment of the present application.
  • the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship.
  • a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.
  • corresponding may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.
  • Zero-power communication network is a wireless communication technology suitable for short distance and low rate.
  • Zero-power devices mainly combine RF energy harvesting technology, backscattering technology, and low-power computing technology to achieve the advantage of device nodes not carrying power supply.
  • Figure 2 is a schematic diagram of a zero-power terminal.
  • the core of RF energy collection is to convert RF energy into direct current.
  • the energy can be stored in batteries or capacitors, or it can be directly used to drive logic circuits, digital chips or sensor devices after collection, to complete the modulation and transmission of backscattered signals, the collection and processing of sensor information and other functions and applications.
  • Zero-power communication systems can be used in scenarios such as wireless industrial sensing networks, smart agriculture, smart warehousing and logistics, and smart homes.
  • zero-power terminals Based on the energy source and usage of zero-power terminals, zero-power terminals can be divided into the following types:
  • Zero-power terminals do not need internal batteries. When they are close to network devices (such as readers of RFID systems), they are in the near field formed by the radiation of the network device antenna. Therefore, the antenna of the zero-power terminal generates an induced current through electromagnetic induction, and the induced current drives the low-power chip circuit of the zero-power terminal. This realizes the demodulation of the forward link signal and the modulation of the backward link signal. For the backscatter link, the zero-power terminal uses the backscatter implementation method to transmit the signal.
  • the passive zero-power terminal does not require a built-in battery to drive either the forward link or the reverse link, and is a truly zero-power terminal.
  • Passive zero-power terminals do not require batteries, and the RF circuit and baseband circuit are very simple. For example, they do not require LNA (low noise amplifier), PA (power amplifier), crystal oscillator, ADC and other devices. Therefore, they have many advantages such as small size, light weight, very cheap price and long service life.
  • LNA low noise amplifier
  • PA power amplifier
  • ADC analog to digital converter
  • the characteristics of this terminal device can also be: 1) no battery; 2) obtain energy from the surrounding environment (such as radio waves, solar energy, wind energy, mechanical kinetic energy, etc.); 3) no USIM card. It can also store energy to a certain extent through the surrounding environment, but the energy is very small, so the functional logic supported is much less than that of ordinary mobile phone terminals.
  • the semi-passive zero-power terminal itself does not have a conventional battery installed, but can use an RF energy harvesting module to harvest radio wave energy and store the harvested energy in an energy storage unit (such as a capacitor). After the energy storage unit obtains energy, it can drive the low-power chip circuit of the zero-power terminal. It can realize the demodulation of the forward link signal and the modulation of the backward link signal. For the backscatter link, the zero-power terminal uses the backscatter implementation method to transmit the signal.
  • the semi-passive zero-power terminal does not require a built-in battery to drive either the forward link or the reverse link. Although energy stored in capacitors is used in operation, the energy comes from the radio energy collected by the energy harvesting module. Therefore, it is also a true zero-power terminal.
  • Semi-passive zero-power consumption terminals inherit many advantages of passive zero-power consumption terminals, so they have many advantages such as small size, light weight, very cheap price and long service life.
  • the zero-power terminals used in some scenarios can also be active zero-power terminals, which can have built-in batteries.
  • the battery is used to drive the low-power chip circuit of the zero-power terminal. It can realize the demodulation of the forward link signal and the modulation of the backward link signal.
  • the zero-power terminal uses the backscatter implementation method to transmit the signal. Therefore, the zero power consumption of this type of terminal is mainly reflected in the fact that the signal transmission of the reverse link does not require the terminal's own power, but uses the backscatter method.
  • Active zero-power terminals have built-in batteries to power RFID chips to increase the read and write distance of tags and improve communication reliability. Therefore, they are used in some scenarios with relatively high requirements for communication distance and reading delay.
  • Zero-power terminals can be connected to the base station directly, or through a relay device.
  • the former is called direct mode, and the latter is called indirect mode.
  • zero-power IoT can also be called AIoT (Ambient power enabled IoT) devices, referred to as ambient IoT (Ambient IoT), and in some technical literature it is also called passive IoT.
  • AIoT device refers to an IoT device that uses various environmental energies, such as wireless radio frequency energy, light energy, solar energy, thermal energy, mechanical energy, and other environmental energies to drive itself. This type of device may have no energy storage capacity or may have very limited energy storage capacity (such as using capacitors with a capacity of tens of uF).
  • Ambient IoT devices have many advantages such as no conventional battery, no maintenance, small size, low complexity, low cost, and long life cycle.
  • Figure 3 is a schematic diagram of a 5G system architecture.
  • SOR roaming control
  • HPLMN Home Public Land Mobile Network
  • VPLMN Visited Public Land Mobile Network
  • HPLMN sends the priority list of VPLMNs and access technologies specified by HPLMN to the UE through Non-Access Stratum (NAS) signaling. After receiving the list, the UE immediately enters the idle state and uses the list to select a new VPLMN.
  • NAS Non-Access Stratum
  • SOR-CMCI contains timers corresponding to each service. After the timer corresponding to the service (which may include multiple services) expires, the UE enters the idle state to perform network selection.
  • the SOR information sent by the network device to the terminal device may be carried in a SOR transparent container (SOR transparent container) information element (IE, Information Element).
  • SOR transparent container SOR transparent container
  • IE Information Element
  • Table 1 is an example of a format of a SOR transparent container IE.
  • the network side For zero-power devices, the overall design of SOR is too complicated compared to zero-power devices because of their very simple design. However, since the relevant technology stipulates that supporting SOR is a mandatory feature of terminal devices, the network side expects zero-power terminals to report information related to SOR; however, if the zero-power terminal unilaterally does not support SOR, the network side cannot receive information related to SOR; at this time, the network side will think that the terminal side protocol design is wrong because the expectation does not match the actual situation, and then refuse the terminal to access the network, affecting the terminal business.
  • the embodiments of the present application propose several communication methods, which involve at least one of a terminal device, an access device, a first network element, a second network element, and a third network element.
  • the terminal device may include a zero-power terminal, such as an AIoT terminal; or, the terminal device may include other types of terminals besides a zero-power terminal.
  • the access device may include a base station.
  • the first network element may include core network devices such as AMF.
  • the second network element may include devices such as UDM and UDR.
  • the third network element may include an application function network element related to SOR, such as a SOR application function (SOR-AF, SOR-Application Function), etc.
  • Figure 4 is a schematic flow chart of a communication method 400 according to an embodiment of the present application, which involves the aforementioned multiple devices. The method includes at least part of the following contents.
  • the terminal device sends a registration request message to the first network element, and the registration request message carries the identification information of the terminal device.
  • the registration request message may also carry a first indication and/or a frequency band supported by the terminal device, wherein the first indication may be used to indicate whether the terminal device is a zero-power consumption terminal.
  • the terminal device sends an RRC message including the registration request message to the first network element.
  • the registration request message may be forwarded to the first network element through the access device.
  • the access device may also identify the access technology used by the terminal device, and send the access technology used by the terminal device and/or the location of the terminal device to the first network element.
  • the location of the terminal device may include the tracking area identifier (TAI, Tracking Area Identity) where the terminal device is located. If the terminal device is a zero-power terminal, and the access technology used by the terminal device is an access technology specific to zero-power terminals, the access device may indicate to the first network element that the terminal device uses an access technology specific to zero-power terminals.
  • TAI Tracking Area Identity
  • the first network element can determine whether the terminal device is a zero-power terminal according to the first indication carried in the registration request message and/or according to the access technology used by the terminal device. If the terminal device is a zero-power terminal, the first network element can send a third message to the second network element, and the third message carries at least one of the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device, and the first indication.
  • the first indication can be obtained from the registration request message received by the terminal device, or it can be generated by the first network element according to the access technology used by the terminal device to determine whether the terminal device is a zero-power terminal and the judgment result.
  • the third message may include a user data management acquisition (Nudm_SubscriberDataManagement_Get) message or a user equipment context management update (Nudm_UEContextManagement_Update) message.
  • the second network element determines the SOR information of the terminal device according to the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device, and at least one of the first indication. If the second network element cannot determine the SOR information of the terminal device, the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device, and at least one of the first indication may be sent to the third network element, and the third network element determines the SOR information of the terminal device according to the information, and feeds back the SOR information of the terminal device to the second network element. If the terminal device is a zero-power terminal, the second network element or the third network element may determine simplified SOR information for the zero-power terminal.
  • the methods of simplifying SOR information may include one or more of the following:
  • the SOR information does not include access technology.
  • the zero-power terminal uses a specific access technology, it is not necessary to include the access technology in the PLMN ID and access technology list field of the SOR transparent container. This field may only contain a list of PLMNs.
  • the SOR information includes a network identifier and an access technology list, which is determined based on the location of the terminal device and/or the frequency band supported by the terminal device.
  • the contents in the network identification and access technology list include: the network identification and access technology of the operator corresponding to the location of the terminal device; and/or the network identification and access technology of the operator corresponding to the frequency band supported by the terminal device.
  • the network ID and access technology of the operator of the country or region where the terminal device is currently located can be configured according to the location of the terminal device, rather than the entire set of the PLMN ID and access technology list;
  • only the network ID and access technology of the operator corresponding to the frequency band supported by the terminal device may be configured, instead of the entire set of the PLMN ID and access technology list;
  • the network IDs and access technologies that correspond to the operator of the country or region where the terminal device is currently located and the frequency bands supported by the terminal device can be configured based on the location of the terminal device and the supported frequency bands, rather than the entire set of the PLMN ID and access technology list.
  • the SOR-CMCI indicator in the SOR transparent container may be set to 0, indicating that there is no SOR-CMCI in the SOR information.
  • the length of the SSCMI in the SOR transparent container IE is set to 1 bit, and when the SSCMI value is 0, it indicates that there is no SOR-CMCI in the SOR information; when the SSCMI value is 1, it indicates that there is SOR-CMCI in the SOR information.
  • the SSCMI value is 1, it indicates that there is no SOR-CMCI in the SOR information; when the SSCMI value is 0, it indicates that there is SOR-CMCI in the SOR information.
  • the SOR message includes a first timer.
  • the first timer can be used to control the time for the terminal device to reselect a network after receiving the SOR message. For example, after receiving the SOR message, the terminal device enters an idle state when the first timer times out and performs network selection.
  • the terminal device does not need to feed back an acknowledgment (ACK) message of the SOR information to the network side.
  • ACK acknowledgment
  • the second network element sends a second message to the first network element, and the second message carries the identification information of the terminal device.
  • the second message may also carry SOR information; the SOR information may be determined by the second network element or the third network element. If the terminal device is a zero-power terminal, the SOR information may be the aforementioned simplified SOR information; or, if the terminal device is a zero-power terminal, the second message sent by the second network element to the first network element may not carry SOR information.
  • the second message may include a response message to the third message, etc.
  • the first network element sends a registration acceptance message to the terminal device.
  • the registration acceptance message may be forwarded to the terminal device via the access device.
  • the registration acceptance message may carry SOR information.
  • the registration acceptance message may carry the simplified SOR information received in step S450.
  • the registration request message may carry a SOR transparent container, which carries the SOR information.
  • the registration acceptance message may not carry the SOR information.
  • the registration acceptance message may not carry the SOR information.
  • the receive message may not carry SOR information.
  • the first network element may also send other messages to the terminal device, such as sending a first message (not shown in the figure), in which the SOR information is carried.
  • the first message carries a SOR transparent container, and the SOR transparent container carries the SOR information.
  • the first message may be forwarded to the terminal device via the access device.
  • the terminal device can perform subsequent communication processes based on the received information.
  • the terminal device may carry SOR information, and the SOR information is a simplified SOR information.
  • the terminal device may not feed back an acknowledgment (ACK) message of the SOR information to the network side.
  • ACK acknowledgment
  • the terminal device can enter an idle state and perform network selection after the first timer expires, and during the network selection process, the terminal device can use an access technology unique to zero-power terminals, or use the network identifier and access technology of the operator corresponding to the location of the terminal device and/or the supported frequency band contained in the network identifier and access technology list (PLMN ID and access technology list), thereby reducing the complexity of the SOR process.
  • PLMN ID and access technology list network identifier and access technology list
  • the terminal device will not receive the SOR information, that is, the registration acceptance message received by the terminal device does not carry the SOR information.
  • the terminal device can directly skip the SOR process, which can also achieve the effect of reducing complexity.
  • Fig. 5 is a schematic flow chart of a communication method 500 according to an embodiment of the present application, which can be applied to the systems shown in Figs. 1-3, but is not limited thereto.
  • the method includes at least part of the following contents.
  • the terminal device sends a registration request message to the first network element.
  • the registration request message carries identification information of the terminal device.
  • the terminal device receives a registration acceptance message from the first network element.
  • the terminal device may include a zero-power consumption terminal, such as an AIoT terminal; or, the terminal device may include other types of terminals except the zero-power consumption terminal.
  • a zero-power consumption terminal such as an AIoT terminal
  • the terminal device may include other types of terminals except the zero-power consumption terminal.
  • the terminal device may send an RRC message including a registration request message to the first network element; the registration request message may also carry a first indication and/or a frequency band supported by the terminal device, the first indication being used to indicate whether the terminal device is a zero-power consumption terminal.
  • the registration request message may be forwarded to the first network element via an access device, and the access device may send other relevant information (such as the access technology used by the terminal device and/or the location of the terminal device) to the first network element.
  • the first network element queries the second network element for relevant information of the terminal device based on the received registration request message and other relevant information; the second network element sends a second message to the first network element, the second message carrying identification information of the terminal device and may also carry SOR information.
  • the first network element sends a registration acceptance message to the terminal device, and the registration acceptance message may carry SOR information.
  • the first network element sends a registration acceptance message to the terminal device, and for example, the registration acceptance message may be forwarded to the terminal device through the access device.
  • the registration acceptance message may carry a SOR transparent container, and the SOR transparent container carries the SOR information.
  • the terminal device also receives a first message carrying SOR information.
  • the first message carries a SOR transparent container
  • the SOR transparent container carries SOR information.
  • the first network element sends a first message to the terminal device, for example, the first message may be forwarded to the terminal device through an access device.
  • the first message may include a downlink NAS transport message.
  • the registration acceptance message or the first message received by the terminal device may carry SOR information, and the SOR information may be simplified SOR information; or, the registration acceptance message received by the terminal device may not carry SOR information.
  • the SOR information does not include access technology.
  • the SOR information includes a network identifier and an access technology list, which is determined based on the location of the terminal device and/or the frequency band supported by the terminal device.
  • the contents of the network identifier and access technology list include: the network identifier and access technology of the operator corresponding to the location of the terminal device; and/or, the network identifier and access technology of the operator corresponding to the frequency band supported by the terminal device.
  • the SOR information does not include the SOR-CMCI.
  • the SOR message includes a first timer.
  • the terminal device may not feed back an acknowledgment (ACK) message of the SOR information to the network side.
  • ACK acknowledgment
  • the terminal device can directly skip the SOR process, which can also achieve the effect of reducing complexity.
  • FIG6A is a schematic flow chart of a communication method 600 according to an embodiment of the present application, which can be applied to the systems shown in FIG1-3 , but is not limited thereto.
  • the method includes at least part of the following contents.
  • the first network element receives a second message from the second network element, where the second message carries identification information of the terminal device.
  • the first network element sends a registration acceptance message to the terminal device.
  • the first network element may include devices such as AMF, and the second network element may include devices such as UDM or UDR.
  • the second message includes a response message of a Nudm_SubscriberDataManagement_Get message or a Nudm_UEContextManagement_Update message, etc.
  • the registration acceptance message can be forwarded to the terminal device via the access device.
  • FIG. 6B is another schematic flow chart of a communication method 600 according to an embodiment of the present application. As shown in FIG. 6B , before step S610, the method may further include:
  • a first network element receives at least one of a registration request message, a location of a terminal device, and a second indication.
  • the first network element may receive at least one of a registration request message, a location of a terminal device, and a second indication from a terminal device.
  • the registration request message may be forwarded to the first network element via an access device.
  • the registration request message may carry at least one of the identification information of the terminal device, the frequency band supported by the terminal device, and a first indication; wherein the first indication may be used to indicate whether the terminal device is a zero-power consumption terminal.
  • the location of the terminal device may include the TAI where the terminal device is located.
  • the second indication is used to indicate that the terminal device uses the first access technology.
  • the first network element may receive at least one of a registration request message, the location of the terminal device, and a second indication; wherein the registration request message may be forwarded by the access device to the first network element, and the location of the terminal device and the second indication may be determined by the access device and sent to the first network element.
  • the first access technology may include an access technology used by a zero-power terminal.
  • the first network element may determine whether the terminal device is a zero-power terminal based on the second indication.
  • the first network element may determine that the terminal device is a zero-power terminal.
  • the first network element can determine whether the terminal device is a zero-power consumption terminal based on the first indication carried in the registration request message; it can also obtain the access technology used by the terminal device based on the second indication sent by the access device, thereby determining whether the terminal device is a zero-power consumption terminal.
  • the first network element sends a third message to the second network element, where the third message carries at least one of the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device, and the first indication.
  • the third message may include a user data management acquisition (Nudm_SubscriberDataManagement_Get) message or a user equipment context management update (Nudm_UEContextManagement_Update) message.
  • the information carried in the third message can be used for the second network element or other network elements to determine the SOR information and to feed back the SOR information to the first network element; or, the information carried in the third message is used for the second network element to decide not to feed back the SOR information when it determines that the terminal device is a zero-power consumption terminal.
  • Method 1 The second network element feeds back SOR information to the first network element:
  • the first network element receives a second message from the second network element, where the second message also carries SOR information.
  • the registration acceptance message sent by the first network element may carry the SOR information.
  • the registration acceptance message carries the SOR transparent container, and the SOR transparent container carries the SOR information.
  • the first network element may also send a first message, the first message carrying the SOR information.
  • the first message carries a SOR transparent container, and the SOR transparent container carries the SOR information.
  • the first network element sends the first message to the first network element, and the first message may be forwarded to the terminal device through the access device.
  • the first message may include a downlink NAS transport message.
  • the second message received by the first network element may carry SOR information, and the SOR information may be simplified SOR information. Specifically:
  • the SOR information does not include access technology.
  • the SOR information includes a network identifier and an access technology list, which is determined based on the location of the terminal device and/or the frequency band supported by the terminal device.
  • the contents of the network identifier and access technology list include: the network identifier and access technology of the operator corresponding to the location of the terminal device; and/or, the network identifier and access technology of the operator corresponding to the frequency band supported by the terminal device.
  • the SOR information does not include the SOR-CMCI.
  • the SOR message includes a first timer.
  • the SOR information can be sent to the terminal device via the first network element.
  • the terminal device can enter the idle state and perform network selection after the first timer expires, and in the network selection process, it can use the access technology unique to the zero-power terminal, or use the network identifier and access technology of the operator corresponding to the location of the terminal device and/or the supported frequency band included in the network identifier and access technology list, thereby reducing the complexity of the SOR process.
  • the second network element does not feed back SOR information to the first network element:
  • the first network element receives a second message from the second network element, where the second message does not carry SOR information.
  • the registration acceptance message sent by the first network element does not carry the SOR information.
  • the terminal device does not perform the SOR process after receiving the registration acceptance message.
  • the registration acceptance message fed back by the first network element to the terminal device does not carry the SOR information, so the terminal device can directly skip the SOR process, which can also achieve the effect of reducing complexity.
  • FIG7A is a schematic flow chart of a communication method 700 according to an embodiment of the present application, which can be applied to the systems shown in FIG1-3 , but is not limited thereto.
  • the method includes at least part of the following contents.
  • the second network element sends a second message to the first network element, where the second message carries identification information of the terminal device.
  • the first network element may include devices such as AMF, and the second network element may include devices such as UDM or UDR.
  • the second message includes a response message of a Nudm_SubscriberDataManagement_Get message or a Nudm_UEContextManagement_Update message, etc.
  • FIG. 7B is another schematic flow chart of a communication method 700 according to an embodiment of the present application. As shown in FIG. 7B , before step S710, the method may further include:
  • the second network element receives a third message from the first network element, the third message carrying at least one of identification information of a terminal device, a location of the terminal device, a frequency band supported by the terminal device, and a first indication; wherein the first indication may be used to indicate whether the terminal device is a zero-power terminal.
  • the location of the terminal device may include the TAI where the terminal device is located.
  • the third message may include a user data management acquisition (Nudm_SubscriberDataManagement_Get) message or a user equipment context management update (Nudm_UEContextManagement_Update) message.
  • the second network element determines SOR information according to at least one of the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device, and the first indication. Then, the process proceeds to step S710.
  • the second network element sends at least one of the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device, and the first indication to the third network element; the second network element receives SOR information from the third network element.
  • the third network element may include SOR-AF, and the SOR information is determined by the third network element according to the received information. Then, step S710 is continued.
  • the second network element can determine that the second message does not carry the SOR information, and directly execute step S710, that is, send the second message to the first network element, and the second message does not carry the SOR information.
  • step S710 that is, send the second message to the first network element, and the second message does not carry the SOR information.
  • the registration acceptance message fed back by the first network element to the terminal device does not carry the SOR information, and the terminal device can directly skip the SOR process, which can also achieve the effect of reducing complexity.
  • the second network element determines or receives the SOR information in step S702
  • the second message sent by the second network element to the first network element also carries the SOR information.
  • the registration acceptance message sent by the first network element to the terminal device carries the SOR information.
  • the SOR information may be simplified SOR information, specifically:
  • the SOR information does not include access technology.
  • the SOR information is determined based on the location of the terminal device and/or the frequency bands supported by the terminal device.
  • the SOR information includes a network identifier and an access technology list, which is determined based on the location of the terminal device and/or the frequency bands supported by the terminal device.
  • the contents of the network identifier and access technology list include: the network identifier and access technology of the operator corresponding to the location of the terminal device; and/or, the network identifier and access technology of the operator corresponding to the frequency bands supported by the terminal device.
  • the SOR information does not include the SOR-CMCI.
  • the SOR message includes a first timer.
  • the terminal device can enter the idle state and perform network selection after the first timer expires.
  • the terminal device can adopt the access technology unique to zero-power terminals, or adopt the network identifier and access technology of the operator corresponding to the terminal device's location and/or supported frequency band included in the network identifier and access technology list, thereby reducing the complexity of the SOR process.
  • the third message may not carry the location of the terminal device and the supported frequency bands (because this information is used to determine the SOR information), but only carry the identification information and the first indication of the terminal device, and the subsequent series of related information may not carry the location of the terminal device and the supported frequency bands.
  • FIG8 is a schematic flow chart of a communication method 800 according to an embodiment of the present application, which can be applied to the systems shown in FIG1-3 , but is not limited thereto.
  • the method includes at least part of the following contents.
  • the third network element receives from the second network element at least one of the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device, and a first indication; wherein the first indication can be used to indicate whether the terminal device is a zero-power consumption terminal.
  • the third network element determines the SOR information of the terminal device.
  • the third network element may include a network element such as SOR-AF, etc.
  • the second network element may include a network element such as UDM or UDR, etc.
  • the third network element may also send the SOR information of the terminal device to the second network element.
  • the SOR information determined and sent by the third network element may be simplified SOR information, specifically:
  • the SOR information does not include access technology.
  • the SOR information is determined based on the location of the terminal device and/or the frequency bands supported by the terminal device.
  • the SOR information includes a network identifier and an access technology list, which is determined based on the location of the terminal device and/or the frequency bands supported by the terminal device.
  • the contents of the network identifier and access technology list include: the network identifier and access technology of the operator corresponding to the location of the terminal device; and/or, the network identifier and access technology of the operator corresponding to the frequency bands supported by the terminal device.
  • the SOR information does not include the SOR-CMCI.
  • the SOR message includes a first timer.
  • the SOR information determined by the third network element is sent to the terminal device via the second network element and the first network element.
  • the terminal device can enter the idle state and perform network selection after the first timer times out, and in the network selection process, the terminal device can use the access technology unique to the zero-power terminal, or use the network identifier and access technology of the operator corresponding to the location of the terminal device and/or the supported frequency band included in the network identifier and access technology list, thereby reducing the complexity of the SOR process.
  • FIG9 is a schematic flow chart of a communication method 900 according to an embodiment of the present application, which can be applied to the systems shown in FIG1-3 , but is not limited thereto.
  • the method includes at least part of the following contents.
  • the access device receives a registration request message from a terminal device.
  • the registration request message carries identification information of the terminal device.
  • the access device forwards the registration request message to the first network element.
  • the access device may include a base station, etc.
  • the first network element may include network elements such as an AMF.
  • the access device receives an RRC message including a registration request message from the terminal device.
  • the registration request message carries a first indication and/or a frequency band supported by the terminal device, and the first indication is used to indicate whether the terminal device is a zero-power consumption terminal.
  • the access device also sends the access technology used by the terminal device and/or the location of the terminal device to the first network element.
  • the information sent by the access device to the first network element includes relevant information for determining whether to generate SOR information for the terminal device and the specific content of the SOR information, so that the terminal device can perform a simplified SOR process based on the SOR information, or directly skip the SOR process, thereby reducing the complexity of the terminal device.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the access device includes a base station
  • the first network element includes an AMF
  • the second network element includes a UDM/UDR
  • the third network element includes a SOR-AF
  • FIG10 is a flowchart of an implementation of Embodiment 1 of the present application, including:
  • the terminal device sends an RRC message including a registration request message to the AMF, where the registration request message carries the identification information of the terminal device.
  • the registration request message may also carry the frequency band supported by the terminal device, and/or indication information indicating whether the terminal device is a zero-power consumption terminal.
  • the terminal device may carry the AIoT capability in the registration request message, and the AIoT capability may be used as indication information for indicating whether the terminal device is a zero-power consumption terminal.
  • the AIoT capability value when the AIoT capability value is 1, it means that the terminal device has the AIoT capability and the terminal device is a zero-power terminal; when the AIoT capability value is 0, it means that the terminal device does not have the AIoT capability and the terminal device is not a zero-power terminal. In other examples, when the AIoT capability value is 1, it means that the terminal device does not have the AIoT capability and the terminal device is not a zero-power terminal; when the AIoT capability value is 0, it means that the terminal device has the AIoT capability and the terminal device is a zero-power terminal.
  • the registration request message may be forwarded to the AMF by a base station in the RAN. For example, after the base station receives an RRC message containing a registration request message, if the registration request message carries indication information indicating whether the terminal device is a zero-power terminal, the registration request message may be forwarded to the AMF and the location of the terminal device may be sent at the same time.
  • the location of the terminal device may be the TAI where the terminal device is located.
  • the base station can forward the registration request message to the AMF and send the location of the terminal device and the access technology used by the terminal device. For example, if the base station indicates to the AMF that the access technology used by the terminal device is a technology unique to zero-power devices, the AMF can determine that the terminal device is a zero-power terminal based on the indication.
  • AMF requests the UDM/UDR for the contract information of the terminal device, and AMF sends a Nudm_SubscriberDataManagement_Get message or a Nudm_UEContextManagement_Update message to the UDM/UDR, which carries the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device, and the AIOT indication (AIoT indication).
  • the AIoT indication is used to indicate whether the terminal device is a zero-power terminal. In some examples, when the AIoT indication value is 1, it indicates that the terminal device is a zero-power terminal; when the AIoT indication value is 0, it indicates that the terminal device is not a zero-power terminal.
  • AIoT indication value when the AIoT indication value is 1, it indicates that the terminal device is not a zero-power terminal; when the AIoT indication value is 0, it indicates that the terminal device is a zero-power terminal.
  • AIoT indication is an optional parameter. For example, if the UDM/UDR can find out whether the terminal device is a zero-power terminal from the contract information of the terminal device through the identification information of the terminal device, it is not necessary to carry the AIoT indication. For example, when applying for network access permission for a terminal device, the operator can record in the UDM/UDR information such as whether the terminal device is a zero-power terminal and the frequency bands supported by the terminal device.
  • the UDM/UDR may request the SOR information of the terminal device from the SOR-AF. For example, the UDM/UDR sends at least one of the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device, and the AIoT indication to the SOR-AF.
  • SOR-AF determines whether the terminal device is a zero-power terminal based on the AIoT indication. If the terminal device is a zero-power terminal, SOR-AF determines simplified SOR information for the terminal device and returns a response message to UDM/UDR. The response message may carry the identification information of the terminal device and the SOR information.
  • Simplified methods include one or more of the following:
  • the zero-power terminal uses a specific access technology, it is not necessary to include the access technology in the PLMN ID and access technology list. Only the PLMN list is sent.
  • a timer can be configured
  • the network does not require the UE to reply with an ACK message.
  • UDM/UDR replies to AMF with a response message of Nudm_SubscriberDataManagement_Get message or Nudm_UEContextManagement_Update message, which includes the identification information (UE ID) and SOR information of the terminal device.
  • AMF sends a Registration Accept message to the terminal device.
  • the Registration Accept message may be forwarded to the terminal device via the base station, wherein the Registration Accept message includes a SOR transparent container, and the SOR transparent container includes SOR information.
  • AMF may also send SOR information after the registration process.
  • AMF sends a first message to the terminal device, and the first message includes a SOR transparent container, and the SOR transparent container includes SOR information.
  • the first message may include a Downlink NAS transport message.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the access device includes a base station
  • the first network element includes an AMF
  • the second network element includes a UDM/UDR
  • FIG11 is a flowchart of an implementation of Embodiment 2 of the present application, including:
  • the terminal device sends an RRC message including a registration request message (Registration Request) to the AMF, where the registration request message carries the identification information of the terminal device.
  • the registration request message may also carry the frequency band supported by the terminal device, and/or indication information indicating whether the terminal device is a zero-power consumption terminal.
  • the terminal device may carry the AIoT capability in the registration request message, and the AIoT capability may be used as indication information for indicating whether the terminal device is a zero-power consumption terminal.
  • the AIoT capability value when the AIoT capability value is 1, it means that the terminal device has the AIoT capability and the terminal device is a zero-power terminal; when the AIoT capability value is 0, it means that the terminal device does not have the AIoT capability and the terminal device is not a zero-power terminal. In other examples, when the AIoT capability value is 1, it means that the terminal device does not have the AIoT capability and the terminal device is not a zero-power terminal; when the AIoT capability value is 0, it means that the terminal device has the AIoT capability and the terminal device is a zero-power terminal.
  • the registration request message may be forwarded to the AMF via a base station in the RAN. For example, after receiving an RRC message containing a registration request message, if the registration request message carries indication information indicating whether the terminal device is a zero-power terminal, the registration request message may be forwarded to the AMF and the location of the terminal device may be sent at the same time.
  • the location of the terminal device may be the TAI where the terminal device is located.
  • the base station can forward the registration request message to the AMF and send the location of the terminal device and the access technology used by the terminal device. For example, if the base station indicates to the AMF that the access technology used by the terminal device is a technology unique to zero-power devices, the AMF can determine that the terminal device is a zero-power terminal based on the indication.
  • AMF requests the UDM/UDR for the contract information of the terminal device, and AMF sends a Nudm_SubscriberDataManagement_Get message or a Nudm_UEContextManagement_Update message to the UDM/UDR; the message carries the identification information of the terminal device, the location of the terminal device, the frequency bands supported by the terminal device, and the AIOT indication (AIoT indication).
  • the AIoT indication is used to indicate whether the terminal device is a zero-power terminal. In some examples, when the AIoT indication value is 1, it indicates that the terminal device is a zero-power terminal; when the AIoT indication value is 0, it indicates that the terminal device is not a zero-power terminal.
  • AIoT indication value when the AIoT indication value is 1, it indicates that the terminal device is not a zero-power terminal; when the AIoT indication value is 0, it indicates that the terminal device is a zero-power terminal.
  • AIoT indication is an optional parameter. For example, if the UDM/UDR can Through the identification information of the terminal device, it can be found from the contract information of the terminal device whether the terminal device is a zero-power terminal, and there is no need to carry AIoT indication. For example, when the terminal device is licensed for network access, the operator can record in the UDM/UDR whether the terminal device is a zero-power terminal, the frequency band supported by the terminal device, and other information.
  • the UDM/UDR determines whether the terminal device is a zero-power terminal according to the AIoT indication. If the terminal device is a zero-power terminal, the UDM/UDR determines simplified SOR information for the terminal device.
  • the simplified methods include one or more of the following:
  • the zero-power terminal uses a specific access technology, it is not necessary to include the access technology in the PLMN ID and access technology list. Only the PLMN list is sent.
  • a timer can be configured
  • the network does not require the UE to reply with an ACK message.
  • UDM/UDR replies to AMF with a response message of Nudm_SubscriberDataManagement_Get message or Nudm_UEContextManagement_Update message, which contains the terminal device identification information (UE ID) and SOR information.
  • AMF sends a Registration Accept message to the terminal device.
  • the Registration Accept message may be forwarded to the terminal device via a base station, wherein the Registration Accept message includes a SOR transparent container, and the SOR transparent container includes SOR information.
  • AMF may also send SOR information after the registration process.
  • AMF sends a first message to the terminal device, and the first message includes a SOR transparent container, and the SOR transparent container includes SOR information.
  • the first message may include a Downlink NAS transport message.
  • the access device includes a base station
  • the first network element includes an AMF
  • the second network element includes a UDM/UDR
  • FIG. 12 is a flowchart of the implementation of the third embodiment of the present application, including:
  • the terminal device sends an RRC message including a registration request message (Registration Request) to the terminal device, and the registration request message carries identification information of the terminal device.
  • the registration request message may also carry a frequency band supported by the terminal device, and/or indication information for indicating whether the terminal device is a zero-power consumption terminal.
  • the terminal device may carry the AIoT capability in the registration request message, and the AIoT capability may be used as indication information for indicating whether the terminal device is a zero-power consumption terminal.
  • the AIoT capability value when the AIoT capability value is 1, it means that the terminal device has the AIoT capability and the terminal device is a zero-power terminal; when the AIoT capability value is 0, it means that the terminal device does not have the AIoT capability and the terminal device is not a zero-power terminal. In other examples, when the AIoT capability value is 1, it means that the terminal device does not have the AIoT capability and the terminal device is not a zero-power terminal; when the AIoT capability value is 0, it means that the terminal device has the AIoT capability and the terminal device is a zero-power terminal.
  • the registration request message may be forwarded to the AMF by a base station in the RAN. For example, after the base station receives an RRC message containing a registration request message, if the registration request message carries indication information indicating whether the terminal device is a zero-power consumption terminal, the registration request message may be forwarded to the AMF.
  • the base station can forward the registration request message to the AMF and send the access technology used by the terminal device at the same time. For example, the base station indicates to the AMF that the access technology used by the terminal device is a technology unique to zero-power devices, and the AMF can determine that the terminal device is a zero-power terminal based on the indication.
  • AMF requests the UDM/UDR for the contract information of the terminal device, and AMF sends a Nudm_SubscriberDataManagement_Get message or a Nudm_UEContextManagement_Update message to the UDM/UDR, which carries the identification information of the terminal device and the AIoT indication.
  • the AIoT indication is used to indicate whether the terminal device is a zero-power terminal. In some examples, when the AIoT indication value is 1, it indicates that the terminal device is a zero-power terminal; when the AIoT indication value is 0, it indicates that the terminal device is not a zero-power terminal.
  • AIoT indication value when the AIoT indication value is 1, it indicates that the terminal device is not a zero-power terminal; when the AIoT indication value is 0, it indicates that the terminal device is a zero-power terminal.
  • AIoT indication is an optional parameter. For example, if the UDM/UDR can find out whether the terminal device is a zero-power terminal from the contract information of the terminal device through the identification information of the terminal device, it is not necessary to carry the AIoT indication. For example, when applying for network access permission for a terminal device, the operator can record in the UDM/UDR information such as whether the terminal device is a zero-power terminal and the frequency bands supported by the terminal device.
  • UDM/UDR determines that the terminal device is a zero-power terminal based on the AIoT indication, and then UDM/UDR decides not to send SOR information to the terminal side, thereby avoiding the terminal device from performing the SOR process.
  • UDM/UDR sends a response message of Nudm_SubscriberDataManagement_Get message or Nudm_UEContextManagement_Update message to AMF, which does not carry SOR information.
  • AMF sends a Registration Accept message to the terminal device.
  • the Registration Accept message can be forwarded to the terminal device via the base station, wherein the Registration Accept message does not carry SOR information.
  • FIG. 13 is a schematic diagram of the structure of a terminal device 1300 according to the embodiment of the present application, including:
  • the first sending unit 1301 is used to send a registration request message to the first network element, where the registration request message carries identification information of the terminal device.
  • the first receiving unit 1302 is configured to receive a registration acceptance message from a first network element.
  • the registration accept message SOR information.
  • the registration acceptance message may carry a SOR transparent container, and the SOR transparent container carries SOR information.
  • FIG. 14 is a schematic diagram of the structure of a terminal device 1400 according to an embodiment of the present application. As shown in FIG. 14 , the terminal device further includes:
  • the second receiving unit 1403 is configured to receive a first message, where the first message carries SOR information.
  • the first message may carry a SOR transparent container, and the SOR transparent container carries SOR information.
  • the first message includes a downlink NAS transmission message.
  • the registration request message also carries a first indication and/or a frequency band supported by the terminal device, wherein the first indication is used to indicate whether the terminal device is a zero-power consumption terminal.
  • the registration acceptance message carries SOR information.
  • the SOR information does not include access technology.
  • the SOR information includes a network identifier and an access technology list, and the network identifier and the access technology list are determined according to the location of the terminal device and/or the frequency band supported by the terminal device.
  • the contents of the network identification and access technology list include: the network identification and access technology of the operator corresponding to the location of the terminal device; and/or the network identification and access technology of the operator corresponding to the frequency band supported by the terminal device.
  • the SOR information does not include the SOR-CMCI.
  • the SOR message includes a first timer.
  • the registration acceptance message does not carry SOR information.
  • the terminal device comprises a zero-power consumption terminal.
  • FIG. 15 is a schematic structural diagram of a first network element 1500 according to the embodiment of the present application, including:
  • the third receiving unit 1501 is configured to receive a second message from a second network element, where the second message carries identification information of a terminal device;
  • the second sending unit 1502 is used to send a registration acceptance message.
  • the second message also carries roaming control SOR information.
  • the registration accept message carries the SOR information.
  • the registration acceptance message may carry a SOR transparent container, and the SOR transparent container carries the SOR information.
  • FIG. 16 is a schematic diagram of the structure of a first network element 1600 according to an embodiment of the present application. As shown in FIG. 16 , the first network element may further include:
  • the third sending unit 1603 is configured to send a first message, where the first message carries the SOR information.
  • the first message may carry a SOR transparent container, and the SOR transparent container carries the SOR information.
  • the first message includes a downlink NAS transmission message.
  • the first network element may further include:
  • the fourth sending unit 1604 is configured to send a third message to the second network element, where the third message carries at least one of the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device, and the first indication; wherein,
  • the first indication is used to indicate whether the terminal device is a zero-power consumption terminal.
  • the first network element may further include:
  • the fourth receiving unit 1605 is configured to receive at least one of a registration request message, a location of the terminal device, and a second indication; wherein:
  • the second indication is used to instruct the terminal device to use the first access technology.
  • the first access technology includes an access technology used by a zero-power terminal.
  • the first network element may further include:
  • the first determining unit 1606 is used to determine whether the terminal device is a zero-power consumption terminal according to the second indication.
  • the registration request message carries at least one of identification information of the terminal device, a frequency band supported by the terminal device, and the first indication.
  • the third message includes a user data management acquisition message or a user equipment context management update message.
  • the second message when the terminal device is a zero-power consumption terminal, the second message carries SOR information, and the SOR information is determined according to the location of the terminal device and/or a frequency band supported by the terminal device.
  • the SOR information does not include access technology.
  • the SOR information includes a network identifier and an access technology list, and the network identifier and the access technology list are determined according to the location of the terminal device and/or the frequency band supported by the terminal device.
  • the contents of the network identification and access technology list include: the network identification and access technology of the operator corresponding to the location of the terminal device; and/or the network identification and access technology of the operator corresponding to the frequency band supported by the terminal device.
  • the SOR information does not include the SOR-CMCI.
  • the SOR message includes a first timer.
  • the second message when the terminal device is a zero-power consumption terminal, the second message does not carry SOR information.
  • the first network element includes an AMF.
  • the second network element includes a UDM or a UDR.
  • the second message includes a response message.
  • FIG. 17 is a schematic diagram of the structure of a second network element 1700 according to the embodiment of the present application, including:
  • the fifth sending unit 1701 is used to send a second message to the first network element, where the second message carries identification information of the terminal device.
  • the second message also carries SOR information.
  • FIG. 18 is a schematic diagram of the structure of a second network element 1800 according to an embodiment of the present application. As shown in FIG. 18 , the second network element may further include:
  • the fifth receiving unit 1802 is configured to receive a third message from the first network element, where the third message carries at least one of the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device, and the first indication; wherein,
  • the first indication is used to indicate whether the terminal device is a zero-power consumption terminal.
  • the second network element may further include:
  • the sixth sending unit 1803 is configured to send at least one of the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device, and the first indication to the third network element;
  • the sixth receiving unit 1804 is configured to receive the SOR information from the third network element.
  • the second network element may further include:
  • the second determining unit 1805 is used to determine the SOR information according to at least one of the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device and the first indication.
  • the third message includes a user data management acquisition message or a user equipment context management update message.
  • the SOR information when the terminal device is a zero-power consumption terminal, the SOR information does not include access technology.
  • the SOR information is determined according to a location of the terminal device and/or a frequency band supported by the terminal device.
  • the SOR information includes a network identifier and an access technology list, and the network identifier and the access technology list are determined according to the location of the terminal device and/or the frequency band supported by the terminal device.
  • the content of the network identifier and access technology list includes: the network identifier and access technology of the operator corresponding to the location of the terminal device; and/or the network identifier and access technology of the operator corresponding to the frequency band supported by the terminal device.
  • the SOR information does not include the SOR-CMCI.
  • the SOR message includes a first timer.
  • the second network element may further include:
  • the third determination unit 1806 is used for, when the terminal device is a zero-power consumption terminal, the second network element to determine that the second message does not carry the SOR information.
  • the second network element includes a UDM or a UDR.
  • the first network element includes an AMF.
  • the third network element comprises a SOR-AF.
  • the second message includes a response message.
  • FIG. 19 is a schematic diagram of the structure of a third network element 1900 according to the embodiment of the present application, including:
  • the seventh receiving unit 1901 is used to receive at least one of the identification information of the terminal device, the location of the terminal device, the frequency band supported by the terminal device and the first indication from the second network element; wherein the first indication is used to indicate whether the terminal device is a zero-power consumption terminal.
  • the fourth determining unit 1902 is configured to determine the SOR information of the terminal device.
  • FIG. 20 is a schematic diagram of the structure of a third network element 2000 according to an embodiment of the present application. As shown in FIG. 20 , the third network element may further include:
  • the seventh sending unit 2003 is used to send the SOR information of the terminal device to the second network element.
  • the SOR information when the terminal device is a zero-power consumption terminal, the SOR information does not include access technology.
  • the third network element determines the SOR information according to the location of the terminal device and/or the frequency band supported by the terminal device.
  • the SOR information includes a network identifier and an access technology list; the third network element determines the network identifier and the access technology list based on the location of the terminal device and/or the frequency band supported by the terminal device.
  • the contents of the network identification and access technology list include: the network identification and access technology of the operator corresponding to the location of the terminal device; and/or the network identification and access technology of the operator corresponding to the frequency band supported by the terminal device.
  • the SOR information does not include the SOR-CMCI.
  • the SOR message includes a first timer.
  • the third network element comprises a SOR-AF.
  • the second network element includes a UDM or a UDR.
  • FIG. 21 is a schematic diagram of the structure of an access device 2100 according to the embodiment of the present application, including:
  • the eighth receiving unit 2101 is configured to receive a registration request message from a terminal device, where the registration request message carries identification information of the terminal device.
  • the eighth sending unit 2102 is configured to forward the registration request message to the first network element.
  • the registration request message carries a first indication and/or a frequency band supported by the terminal device, and the first indication is used to indicate whether the terminal device is a zero-power consumption terminal.
  • FIG. 22 is a schematic diagram of the structure of an access device 2200 according to an embodiment of the present application. As shown in FIG. 22 , the access device may further include:
  • the ninth sending unit 2203 is used to send the access technology used by the terminal device and/or the location of the terminal device to the first network element.
  • the first network element includes an AMF.
  • the functions described in the various modules (submodules, units or components, etc.) in the communication device of the embodiment of the present application can be implemented by different modules (submodules, units or components, etc.) or by the same module (submodules, units or components, etc.).
  • the first receiving module and the second receiving module can be different modules or the same module, and both can implement their corresponding functions in the embodiment of the present application.
  • the sending module and the receiving module in the embodiment of the present application can be implemented by the transceiver of the device, and some or all of the remaining modules can be implemented by the processor of the device.
  • Fig. 23 is a schematic structural diagram of a communication device 2300 according to an embodiment of the present application.
  • the communication device 2300 shown in Fig. 23 includes a processor 2310, and the processor 2310 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 2300 may further include a memory 2320.
  • the processor 2310 may call and run a computer program from the memory 2320 to implement the communication device in the embodiment of the present application.
  • the memory 2320 may be a separate device independent of the processor 2310 , or may be integrated into the processor 2310 .
  • the communication device 2300 may further include a transceiver 2330 , and the processor 2310 may control the transceiver 2330 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.
  • the transceiver 2330 may include a transmitter and a receiver.
  • the transceiver 2330 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 2300 may be the communication device of the embodiment of the present application, and the communication device 2300 may implement the corresponding processes implemented by the communication device in each method of the embodiment of the present application, which will not be described again for the sake of brevity.
  • Fig. 24 is a schematic structural diagram of a chip 2400 according to an embodiment of the present application.
  • the chip 2400 shown in Fig. 24 includes a processor 2410, and the processor 2410 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the chip 2400 may further include a memory 2420.
  • the processor 2410 may call and run a computer program from the memory 2420 to implement the method in the embodiment of the present application.
  • the memory 2420 may be a separate device independent of the processor 2410 , or may be integrated into the processor 2410 .
  • the chip 2400 may further include an input interface 2430.
  • the processor 2410 may control the input interface 2430 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
  • the chip 2400 may further include an output interface 2440.
  • the processor 2410 may control the output interface 2440 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
  • the chip can be applied to the communication device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
  • the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
  • the processors mentioned above can be general-purpose processors, digital signal processors (DSPs), Field programmable gate array (FPGA), application specific integrated circuit (ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc.
  • DSPs digital signal processors
  • FPGA Field programmable gate array
  • ASIC application specific integrated circuit
  • the general processor mentioned above can be a microprocessor or any conventional processor, etc.
  • the memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories.
  • the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM) or a flash memory.
  • the volatile memory may be a random access memory (RAM).
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)), etc.
  • the size of the serial numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Landscapes

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

Abstract

本申请实施例提出通信方法和设备，其中通信方法包括，终端设备向第一网元发送注册请求消息，该注册请求消息携带终端设备的标识信息；终端设备从第一网元接收注册接受消息。本申请实施例能够降低SOR机制对零功耗设备所造成的不利影响。

Description

通信方法和设备 技术领域
本申请涉及通信领域，并且更具体地，涉及通信方法和设备。
背景技术
相关技术中，要求终端设备支持漫游控制(SOR，Steering of Roaming)技术，SOR技术是一种终端设备的本地公共陆地移动网络(HPLMN，Home Public Land Mobile Network)将终端设备转换到别的陆上公用移动通信网(VPLMN，Visited Public Land Mobile Network)的技术。网络侧将SOR信息发送至终端设备，该SOR信息中包含VPLMN和接入技术的优先级列表、业务对应的定时器等内容；接收到SOR信息之后，用户设备(User Equipment，UE)在定时器到期之后进入空闲态，再利用该VPLMN和接入技术的优先级列表执行选网。零功耗终端不需要内装电池，是一种设计简单的终端设备，SOR技术的整体设计对于零功耗设备而言过于复杂，因此，如何降低SOR机制对零功耗设备所造成的不利影响，是需要解决的技术问题。
发明内容
本申请实施例提供通信方法和设备，可以降低SOR机制对零功耗设备所造成的不利影响。
本申请实施例提供一种通信方法，包括：
终端设备向第一网元发送注册请求消息，该注册请求消息携带该终端设备的标识信息。
终端设备从第一网元接收注册接受消息。
本申请实施例提供一种通信方法，包括：
第一网元从第二网元接收第二消息，该第二消息携带终端设备的标识信息；
该第一网元向终端设备发送注册接受消息。
本申请实施例提供一种通信方法，包括：
第二网元向第一网元发送第二消息，该第二消息携带终端设备的标识信息。
本申请实施例提供一种通信方法，包括：
第三网元从第二网元接收终端设备的标识信息、该终端设备的位置、该终端设备支持的频段和第一指示中的至少之一；其中，该第一指示用于指示该终端设备是否为零功耗终端。
该第三网元确定该终端设备的SOR信息。
本申请实施例提供一种通信方法，包括：
接入设备从终端设备接收注册请求消息，该注册请求消息携带该终端设备的标识信息。
该接入设备向第一网元转发该注册请求消息。
本申请实施例提供一种终端设备，包括：
第一发送单元，用于向第一网元发送注册请求消息，该注册请求消息携带该终端设备的标识信息。
第一接收单元，用于从第一网元接收注册接受消息。
本申请实施例提供一种第一网元，包括：
第三接收单元，用于从第二网元接收第二消息，该第二消息携带终端设备的标识信息；
第二发送单元，用于向终端设备发送注册接受消息。
本申请实施例提供一种第二网元，包括：
第五发送单元，用于向第一网元发送第二消息，该第二消息携带终端设备的标识信息。
本申请实施例提供一种第三网元，包括：
第七接收单元，用于从第二网元接收终端设备的标识信息、该终端设备的位置、该终端设备支持的频段和第一指示中的至少之一；其中，该第一指示用于指示该终端设备是否为零功耗终端。
第四确定单元，用于确定该终端设备的SOR信息。
本申请实施例提供一种接入设备，包括：
第八接收单元，用于从终端设备接收注册请求消息，该注册请求消息携带该终端设备的标识信息。
第八发送单元，用于向第一网元转发该注册请求消息。
本申请实施例提供一种终端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，以使该终端设备执行上述的通信方法。
本申请实施例提供一种芯片，用于实现上述的通信方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行上述的通信方法。
本申请实施例提供一种计算机可读存储介质，用于存储计算机程序，当该计算机程序被设备运行时使得该设备执行上述的通信方法。
本申请实施例提供一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述的通信方法。
本申请实施例提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述的通信方法。
本申请实施例中，终端设备向第一网元发送注册请求消息，第一网元根据该注册请求消息从第二网元接收第二消息，并向终端设备发送注册接受消息；终端设备接收该注册接受消息。这样，第一网元可以根据终端设备是否为零功耗设备，决定注册接受消息中携带的信息，以降低SOR机制对零功耗设备所造成的不利影响。
附图说明
图1是本申请实施例的应用场景的示意图。
图2是一种零功耗终端的示意图。
图3是一种5G系统架构示意图。
图4是根据本申请实施例的一种通信方法400的示意性流程图。
图5是根据本申请实施例的一种通信方法500的示意性流程图。
图6A是根据本申请实施例的一种通信方法600的一种示意性流程图。
图6B是根据本申请实施例的一种通信方法600的另一种示意性流程图。
图7A是根据本申请实施例的一种通信方法700的一种示意性流程图。
图7B是根据本申请实施例的一种通信方法700的另一种示意性流程图。
图8是根据本申请实施例的一种通信方法800的示意性流程图。
图9是根据本申请实施例的一种通信方法900的示意性流程图。
图10是本申请实施例一的实现流程图。
图11是本申请实施例二的实现流程图。
图12是本申请实施例三的实现流程图。
图13是根据本申请实施例的终端设备1300结构示意图。
图14是根据本申请实施例的终端设备1400结构示意图。
图15是根据本申请实施例的第一网元1500结构示意图。
图16是根据本申请实施例的第一网元1600结构示意图。
图17是根据本申请实施例的第二网元1700结构示意图。
图18是根据本申请实施例的第二网元1800结构示意图。
图19是根据本申请实施例的第三网元1900结构示意图。
图20是根据本申请实施例的第三网元2000结构示意图。
图21是根据本申请实施例的接入设备2100结构示意图。
图22是根据本申请实施例的接入设备2200结构示意图。
图23是根据本申请实施例的通信设备2300结构示意图。
图24是根据本申请实施例的芯片2400的示意性结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
需要说明的是，本申请实施例的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。同时描述的“第一”、“第二”描述的对象可以相同，也可以不同。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、非授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、非授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)系统、非地面通信网络(Non-Terrestrial Networks，NTN)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、第五代通信(5th-Generation，5G)系统或其它通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，车辆间(Vehicle to Vehicle，V2V)通信，或车联网(Vehicle to everything，V2X)通信等，本申请实施例也可以应用于这些通信系统。
在一种实施方式中，本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
在一种实施方式中，本申请实施例中的通信系统可以应用于非授权频谱，其中，非授权频谱也可以认为是共享频谱；或者，本申请实施例中的通信系统也可以应用于授权频谱，其中，授权频谱也可以认为是非共享频谱。
本申请实施例结合网络设备和终端设备描述了各个实施例，其中，终端设备也可以称为用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是WLAN中的站点(STAION，ST)，可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、下一代通信系统例如NR网络中的终端设备，或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的终端设备等。
在本申请实施例中，终端设备可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。
在本申请实施例中，终端设备可以是手机(Mobile Phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(selfdriving)中的无线终端设备、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备或智慧家庭(smart home)中的无线终端设备等。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
在本申请实施例中，网络设备可以是用于与移动设备通信的设备，网络设备可以是WLAN中的接入点(Access Point，AP)，GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB，NB)，还可以是LTE中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及NR网络中的网络设备(gNB)或者未来演进的PLMN网络中的网络设备或者NTN网络中的网络设备等。
作为示例而非限定，在本申请实施例中，网络设备可以具有移动特性，例如网络设备可以为移动的设备。可选地，网络设备可以为卫星、气球站。例如，卫星可以为低地球轨道(low earth orbit，LEO)卫星、中地球轨道(medium earth orbit，MEO)卫星、地球同步轨道(geostationary earth orbit，GEO)卫星、高椭圆轨道(High Elliptical Orbit，HEO)卫星等。可选地，网络设备还可以为设置在陆地、水域等位置的基站。
在本申请实施例中，网络设备可以为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto  cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
图1示例性地示出了一种通信系统100。该通信系统包括一个网络设备110和两个终端设备120。在一种实施方式中，该通信系统100可以包括多个网络设备110，并且每个网络设备110的覆盖范围内可以包括其它数量的终端设备120，本申请实施例对此不做限定。
在一种实施方式中，该通信系统100还可以包括移动性管理实体(Mobility Management Entity，MME)、接入与移动性管理功能(Access and Mobility Management Function，AMF)等其它网络实体，本申请实施例对此不作限定。
其中，网络设备又可以包括接入网设备和核心网设备。即无线通信系统还包括用于与接入网设备进行通信的多个核心网。接入网设备可以是长期演进(long-term evolution，LTE)系统、下一代(移动通信系统)(next radio，NR)系统或者授权辅助接入长期演进(authorized auxiliary access long-term evolution，LAA-LTE)系统中的演进型基站(evolutional node B，简称可以为eNB或e-NodeB)宏基站、微基站(也称为“小基站”)、微微基站、接入站点(access point，AP)、传输站点(transmission point，TP)或新一代基站(new generation Node B，gNodeB)等。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统为例，通信设备可包括具有通信功能的网络设备和终端设备，网络设备和终端设备可以为本申请实施例中的具体设备，此处不再赘述；通信设备还可包括通信系统中的其它设备，例如网络控制器、移动管理实体等其它网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例的描述中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
为便于理解本申请实施例的技术方案，以下对本申请实施例的相关技术进行说明，以下相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合，其均属于本申请实施例的保护范围。
零功耗通讯网络是一种适用于短距离，低速率的无线通讯技术。零功耗设备主要结合射频能量采集技术，反向散射技术，低功耗运算技术，以实现设备节点不携带供电电源的优势。图2是一种零功耗终端的示意图。
射频能量收集的核心是将射频能量转化为直流，能量可以存储在电池或者电容里，也可以收集后直接用于驱动逻辑电路、数字芯片或传感器件等，完成对反向散射信号的调制和发射，传感信息的采集与处理等功能及应用。
随着5G系统的发展，出现了5G系统支持零功耗终端接入网络的需求。主要针对的场景有以下特点：
-环境极端，不适合普通终端工作；
-使用非常低的功耗和成本的终端；
-无电池终端。
零功耗通信系统可以使用在无线工业感应网络、智能农业、智能仓储与物流、智能家居等场景下。
基于零功耗终端的能量来源以及使用方式可以将零功耗终端分为如下类型：
1)无源零功耗终端
零功耗终端不需要内装电池，零功耗终端接近网络设备(如RFID系统的读写器)时，零功耗终端处于网络设备天线辐射形成的近场范围内。因此，零功耗终端天线通过电磁感应产生感应电流，感应电流驱动零功耗终端的低功耗芯片电路。实现对前向链路信号的解调，以及后向链路的信号调制等工作。对于反向散射链路，零功耗终端使用反向散射实现方式进行信号的传输。
可以看出，无源零功耗终端无论是前向链路还是反向链路都不需要内置电池来驱动，是一种真正意义的零功耗终端。
无源零功耗终端不需要电池，射频电路以及基带电路都非常简单，例如不需要LNA(低噪放)，PA(功放)，晶振，ADC等器件，因此具有体积小、重量轻、价格非常便宜、使用寿命长等诸多优点。
这种终端设备的特征还可以是：1)无电池；2)从周边环境中获得能量(如无线电波、太阳能、风能、机械动能等)；3)无USIM卡。还可以通过周边环境做一定的储能，但是能量很少，因此支持的功能逻辑较普通手机类终端少很多。
2)半无源零功耗终端
半无源零功耗终端自身也不安装常规电池，但可使用RF能量采集模块采集无线电波能量，同时将采集的能量存储于一个储能单元(如电容)中。储能单元获得能量后，可以驱动零功耗终端的低功耗芯片电路。实现对前向链路信号的解调，以及后向链路的信号调制等工作。对于反向散射链路，零功耗终端使用反向散射实现方式进行信号的传输。
可以看出，半无源零功耗终端无论是前向链路还是反向链路都不需要内置电池来驱动，虽然工作中使用了电容储存的能量，但能量来源于能量采集模块采集的无线电能量，因此也是一种真正意义的零功耗终端。
半无源零功耗终端继承了无源零功耗终端的诸多优点，因此具有体积小、重量轻、价格非常便宜、使用寿命长等诸多优点。
3)有源零功耗终端
有些场景下使用的零功耗终端也可以为有源零功耗终端，该类终端可以内置电池。电池用于驱动零功耗终端的低功耗芯片电路。实现对前向链路信号的解调，以及后向链路的信号调制等工作。但对于反向散射链路，零功耗终端使用反向散射实现方式进行信号的传输。因此，这类终端的零功耗主要体现于反向链路的信号传输不需要终端自身功率，而是使用反向散射的方式。
有源零功耗终端，内置电池向RFID芯片供电，以增加标签的读写距离，提高通信的可靠性。因此在一些对通信距离，读取时延等方面要求相对较高的场景得以应用。
零功耗终端可以直接接入基站，或者，通过一个中继设备接入到基站中。前者称为直接模式(direct mode)，后者称为间接模式(indirect mode)。
在标准化讨论过程中，零功耗物联网也可以称之为(AIoT，Ambient power enabled IoT)设备，简称环境能物联网(Ambient IoT)，在一些技术文献中也有称之为无源物联网(passive IoT)。所谓AIoT设备意指使用各种环境能量，如无线射频能、光能、太阳能、热能、机械能等各种环境能驱动自身的IoT设备。这种设备可以没有能量储备能力、也可以具备非常有限的能量储存能力(如使用几十uF容量的电容)。相比现有的IoT装置，Ambient IoT设备具备免常规电池、免维护、体积尺寸小、低复杂度低成本、长寿命周期等诸多优势。图3是一种5G系统架构示意图。
相关技术中，UE需要支持漫游控制(SOR，Steering ofRoaming)。SOR是一种UE的本地公共陆地移动网络(HPLMN，Home Public Land Mobile Network)把UE转换到别的陆上公用移动通信网(VPLMN，Visited Public LandMobile Network)的技术。HPLMN通过非接入层(NAS，Non-Access Stratum)信令，把HPLMN规定的VPLMN和接入技术的优先级列表发给UE，UE收到后立即进入空闲态、并使用该列表选择新的VPLMN。
随着技术的发展，相关技术中，UE需要支持SOR和SOR-连接模式控制信息(CMCI，connected mode control information)。SOR-CMCI中包含各个业务分别对应的定时器，UE在使用业务(可能包括多个业务)对应的定时器到期后再进入空闲态执行选网。
网络设备向终端设备发送的SOR信息可以承载于SOR透明容器(SOR transparent container)信息元素(IE，Information Element)中，下表1是一种SOR透明容器IE的一种格式示例。
表1
对于零功耗设备，由于其设计十分简单，SOR的整体设计相对于零功耗设备来说过于复杂。但是，由于相关技术中规定支持SOR是终端设备的必选特性，网络侧会期待零功耗终端上报与SOR相关的信息；然而，如果零功耗终端单方面不支持SOR，则网络侧无法收到与SOR相关的信息；此时网络侧会由于期待与实际情况不符，认为终端侧协议设计出错，进而拒绝终端接入网络，影响终端业务。
因此，如何使零功耗终端避免复杂的SOR机制是需要解决的技术问题。
本申请实施例提出几种通信方法，该方法涉及终端设备、接入设备、第一网元、第二网元、第三网元中的至少之一。其中，终端设备可以包括零功耗终端，例如AIoT终端；或者，该终端设备可以包括除零功耗终端以外的其他类型的终端。接入设备可以包括基站。第一网元可以包括AMF等核心网设备。第二网元可以包括UDM、UDR等设备。第三网元可以包括与SOR相关的应用功能网元，如SOR应用功能(SOR-AF，SOR-Application Function)等。图4是根据本申请实施例的一种通信方法400的示意性流程图，该通信方法涉及前述多个设备。该方法包括以下内容的至少部分内容。
S410、终端设备向第一网元发送注册请求消息，该注册请求消息携带该终端设备的标识信息。该注册请求消息还可以携带第一指示和/或该终端设备支持的频段，其中，第一指示可以用于指示该终端设备是否为零功耗终端。例如，终端设备向第一网元发送包含注册请求消息的RRC消息。
其中，注册请求消息可以通过接入设备转发至第一网元。在一些实施方式中，接入设备还可以识别该终端设备使用的接入技术，并将该终端设备使用的接入技术和/或该终端设备的位置发送至第一网元。其中，终端设备的位置可以包括终端设备所在的跟踪区标识(TAI，Tracking Area Identity)。如果该终端设备是零功耗终端，并且该终端设备使用的接入技术是零功耗终端特有的接入技术，则接入设备可以向第一网元指示该终端设备使用零功耗终端特有的接入技术。
S430、第一网元根据注册请求消息中携带的第一指示，和/或，根据终端设备使用的接入技术，能够确定该终端设备是否为零功耗终端。如果该终端设备是零功耗终端，第一网元可以向第二网元发送第三消息，该第三消息携带终端设备的标识信息、终端设备的位置、终端设备支持的频段和第一指示中的至少之一。其中，该第一指示可以从终端设备接收的注册请求消息中得到的，也可以是由第一网元根据终端设备使用的接入技术判断终端设备是否为零功耗终端、并根据判断结果生成的。在一些示例中，第三消息可以包括用户数据管理获取(Nudm_SubscriberDataManagement_Get)消息或者用户设备上下文管理更新(Nudm_UEContextManagement_Update)消息。
S440、第二网元根据终端设备的标识信息、终端设备的位置、终端设备支持的频段和第一指示中的至少之一，确定该终端设备的SOR信息。如果第二网元无法确定终端设备的SOR信息，则可以将该终端设备的标识信息、终端设备的位置、终端设备支持的频段和第一指示中的至少之一发送至第三网元，由第三网元根据这些信息确定终端设备的SOR信息，并向第二网元反馈终端设备的SOR信息。如果该终端设备是零功耗终端，第二网元或第三网元可以为该零功耗终端确定简化的SOR信息。
具体地，简化SOR信息的方式可以包括以下一种或多种：
(1)SOR信息中不包含接入技术。
例如，如果零功耗终端使用特定的接入技术，则不需要在SOR透明容器(SOR transparent container)的网络标识和接入技术列表(PLMN ID and access technology list)字段中包含接入技术， 该字段中可以只包含PLMN列表。
(2)SOR信息中包含网络标识和接入技术列表，该网络标识和接入技术列表根据终端设备的位置和/或终端设备支持的频段确定。
例如，网络标识和接入技术列表中的内容包括：终端设备的位置对应的运营商的网络标识和接入技术；和/或，终端设备支持的频段对应的运营商的网络标识和接入技术。
在一些示例中，SOR透明容器的网络标识和接入技术列表(PLMN ID and access technology list)字段中，可以根据终端设备的位置，只配置终端设备当前所在的国家或地区的运营商的网络标识和接入技术，而不是网络标识和接入技术(PLMN ID and access technology list)列表的全集；
在一些示例中，SOR透明容器的网络标识和接入技术列表(PLMN ID and access technology list)字段中，可以根据终端设备支持的频段，只配置该频段对应的运营商的网络标识和接入技术，而不是网络标识和接入技术(PLMN ID and access technology list)列表的全集；
在一些示例中，SOR透明容器的网络标识和接入技术列表(PLMN ID and access technology list)字段中，可以根据终端设备的位置和支持的频段，只配置既与终端设备当前所在的国家或地区的运营商对应、又与终端设备支持的频段对应的网络标识和接入技术，而不是网络标识和接入技术(PLMN ID and access technology list)列表的全集。
(3)SOR信息中不包含SOR-CMCI。
由于零功耗终端一般都是传输测量、位置参数等小数据，对业务的连续传输的需求不大，可以在收到SOR信息后直接进入空闲态，因此可以不配置针对各个业务的SOR-CMCI。
例如，可以将SOR透明容器中的SOR-CMCI指示(SOR-CMCI indicator)设置为0，表示SOR信息中没有SOR-CMCI。例如，将SOR透明容器(SOR transparent container)IE中的SSCMI的长度设置为1比特，SSCMI取值为0时，表示SOR信息中没有SOR-CMCI；SSCMI取值为1时，表示SOR信息中有SOR-CMCI。或者，SSCMI取值为1时，表示SOR信息中没有SOR-CMCI；SSCMI取值为0时，表示SOR信息中有SOR-CMCI。
(4)SOR信息中包含第一定时器。
该第一定时器可以用于控制终端设备在接收到SOR信息后重新选网的时间。例如，终端设备接收到SOR信息后，在第一定时器超时的情况下进入空闲态，并执行选网。
(5)终端设备不需要向网络侧反馈该SOR信息的确认(ACK)消息。
S450、第二网元向第一网元发送第二消息，该第二消息携带终端设备的标识信息。该第二消息中还可以携带SOR信息；该SOR信息可以是由第二网元或第三网元确定的。如果终端设备是零功耗终端，该SOR信息可以是前述简化的SOR信息；或者，如果终端设备是零功耗终端，第二网元向第一网元发送的第二消息中，可以不携带SOR信息。其中，该第二消息可以包括第三消息的响应消息等。
S460、第一网元向终端设备发送注册接受消息。
其中，该注册接受消息可以通过接入设备转发至终端设备。
该注册接受消息可以携带SOR信息，例如，如果终端设备是零功耗终端，该注册接受消息中可以携带步骤S450中接收到的简化的SOR信息。具体地，注册请求消息可以携带SOR透明容器，该SOR透明容器携带SOR信息。
或者，该注册接受消息可以不携带SOR信息，例如，如果终端设备是零功耗终端，该注册接 受消息中可以不携带SOR信息。
或者，第一网元也可以向终端设备发送其他消息，如发送第一消息(图中未示出)，在该第一消息中携带SOR信息。例如，第一消息携带SOR透明容器，SOR透明容器携带SOR信息。在一些实施方式中，该第一消息可以通过接入设备转发至终端设备。
之后，终端设备可以根据接收的信息进行后续通信过程。
例如，如果该终端设备是零功耗终端，该终端设备接收的注册接受消息或第一消息中可能携带SOR信息，该SOR信息是简化的SOR信息。终端设备可以不向网络侧反馈该SOR信息的确认(ACK)消息。利用该简化的SOR信息，终端设备可以在第一定时器超时后进入空闲态并执行选网，并且在选网过程中，终端设备可以采用零功耗终端特有的接入技术，或者采用网络标识和接入技术列表(PLMN ID and access technology list)中包含的终端设备的位置和/或支持的频段对应的运营商的网络标识和接入技术，从而降低SOR过程的复杂度。
或者，如果该终端设备是零功耗终端，在一些实施方式中，该终端设备不会接收到SOR信息，即终端设备接收的注册接受消息中不携带SOR信息。这种情况下，终端设备可以直接跳过SOR过程，也能够达到降低复杂度的效果。
图5是根据本申请实施例的一种通信方法500的示意性流程图，该方法可以应用于图1-3所示的系统，但并不仅限于此。该方法包括以下内容的至少部分内容。
S510、终端设备向第一网元发送注册请求消息，该注册请求消息携带该终端设备的标识信息。
S520、终端设备从该第一网元接收注册接受消息。
其中，终端设备可以包括零功耗终端，例如AIoT终端；或者，该终端设备可以包括除零功耗终端以外的其他类型的终端。
在一些实施方式中，终端设备可以向第一网元发送包含注册请求消息的RRC消息；注册请求消息还可以携带第一指示和/或终端设备支持的频段，第一指示用于指示终端设备是否为零功耗终端。在一些示例中，该注册请求消息可以通过接入设备转发至第一网元，并且，接入设备可以向第一网元发送其他相关信息(如该终端设备使用的接入技术和/或该终端设备的位置)。第一网元根据收到的注册请求消息及其他相关信息，从第二网元查询该终端设备的相关信息；第二网元向第一网元发送第二消息，该第二消息中携带终端设备的标识信息，还可以携带SOR信息。
第一网元向终端设备发送注册接受消息，该注册接受消息可以携带SOR信息。示例性地，第一网元向终端设备发送注册接受消息，例如，该注册接受消息可以通过接入设备转发给终端设备。在一些示例中，注册接受消息可以携带SOR透明容器，SOR透明容器携带SOR信息。
在一些示例中，还包括，终端设备接收第一消息，第一消息携带SOR信息。
例如，该第一消息携带SOR透明容器，SOR透明容器携带SOR信息。
示例性地，第一网元向终端设备发送第一消息，例如，该第一消息可以通过接入设备转发至终端设备。其中，该第一消息可以包括下行NAS传输(Downlink NAS transport)消息。
在终端设备是零功耗终端的情况下，终端设备接收的注册接受消息或第一消息可以携带SOR信息，该SOR信息可以是简化的SOR信息；或者，终端设备接收的注册接受消息可以不携带SOR信息。
针对注册接受消息携带SOR信息的情况：
在一些示例中，SOR信息中不包含接入技术。
在一些示例中，SOR信息中包含网络标识和接入技术列表，该网络标识和接入技术列表根据终端设备的位置和/或终端设备支持的频段确定。例如，网络标识和接入技术列表中的内容包括：终端设备的位置对应的运营商的网络标识和接入技术；和/或，终端设备支持的频段对应的运营商的网络标识和接入技术。
在一些实施方式中，SOR信息中不包含SOR-CMCI。
在一些实施方式中，SOR信息中包含第一定时器。
并且，终端设备可以不向网络侧反馈该SOR信息的确认(ACK)消息。
如果该终端设备是零功耗终端，并且终端设备接收的注册接受消息不携带SOR信息，则终端设备可以直接跳过SOR过程，也能够达到降低复杂度的效果。
图6A是根据本申请实施例的一种通信方法600的一种示意性流程图，该方法可以应用于图1-3所示的系统，但并不仅限于此。该方法包括以下内容的至少部分内容。
S610、第一网元从第二网元接收第二消息，该第二消息携带终端设备的标识信息；
S620、第一网元向终端设备发送注册接受消息。
在一些实施方式中，第一网元可以包括AMF等设备，第二网元可以包括UDM或UDR等设备。
在一些示例中，第二消息包括Nudm_SubscriberDataManagement_Get消息或者Nudm_UEContextManagement_Update消息的响应消息等。
如步骤S620，在一些示例中，该注册接受消息可以通过接入设备转发至终端设备。
图6B是根据本申请实施例的一种通信方法600的另一种示意性流程图，如图6B所示，在步骤S610之前，还可以包括，
S601、第一网元接收注册请求消息、终端设备的位置和第二指示中的至少之一。在一些示例中，第一网元可以从终端设备接收注册请求消息、终端设备的位置和第二指示中的至少之一。例如，注册请求消息可以通过接入设备转发至第一网元。其中：
(1)注册请求消息可以携带终端设备的标识信息、终端设备支持的频段和第一指示中的至少之一；其中第一指示可以用于指示终端设备是否为零功耗终端。
(2)终端设备的位置可以包括终端设备所在的TAI。
(3)第二指示用于指示终端设备使用第一接入技术。例如，第一网元可以接收注册请求消息、终端设备的位置和第二指示中的至少之一；其中，注册请求消息可以由接入设备转发至第一网元，终端设备的位置和第二指示可以由接入设备确定并发送至第一网元。第一接入技术可以包括零功耗终端使用的接入技术。第一网元根据该第二指示，可以确定终端设备是否为零功耗终端。例如，如果第一网元接收到第二指示，由于该第二指示用于指示终端设备使用零功耗终端特有的接入技术(即第一接入技术)，则第一网元可以确定出该终端设备是零功耗终端。
可见，第一网元可以根据注册请求消息中携带的第一指示确定出终端设备是否为零功耗终端；也可以根据接入设备发送的第二指示，获知终端设备所使用的接入技术，从而确定出终端设备是否为零功耗终端。
S602、第一网元向第二网元发送第三消息，该第三消息携带终端设备的标识信息、终端设备的位置、终端设备支持的频段和第一指示中的至少之一。第三消息可以包括用户数据管理获取(Nudm_SubscriberDataManagement_Get)消息或用户设备上下文管理更新(Nudm_UEContextManagement_Update)消息。
第三消息中携带的信息，可以用于供第二网元或其他网元确定SOR信息，并向第一网元反馈SOR信息；或者，第三消息中携带的信息，用于供第二网元在确定终端设备是零功耗终端的情况下，决定不反馈SOR信息。
以下分别介绍上述两种方式：
方式一，第二网元向第一网元反馈SOR信息：
第一网元从第二网元接收第二消息，该第二消息还携带SOR信息。
相应地，第一网元发送的注册接受消息中，可以携带该SOR信息。例如，注册接受消息携带SOR透明容器，SOR透明容器携带SOR信息。
或者，第一网元还可以发送第一消息，该第一消息携带SOR信息。例如，第一消息携带SOR透明容器，SOR透明容器携带该SOR信息。在一些示例中，第一网元向第一网元发送第一消息，该第一消息可以通过接入设备转发至终端设备。
在一些示例中，第一消息可以包括下行NAS传输消息。
在一些实施方式中，在终端设备是零功耗终端的情况下，第一网元接收的该第二消息可以携带SOR信息，该SOR信息可以是简化的SOR信息。具体地：
在一些示例中，SOR信息中不包含接入技术。
在一些示例中，SOR信息中包含网络标识和接入技术列表，该网络标识和接入技术列表根据终端设备的位置和/或终端设备支持的频段确定。例如，网络标识和接入技术列表中的内容包括：终端设备的位置对应的运营商的网络标识和接入技术；和/或，终端设备支持的频段对应的运营商的网络标识和接入技术。
在一些实施方式中，SOR信息中不包含SOR-CMCI。
在一些实施方式中，SOR信息中包含第一定时器。
通过这种方式，该SOR信息可以经由第一网元发送至终端设备。利用该SOR信息，终端设备可以在第一定时器超时后进入空闲态并执行选网，并且在选网过程中，可以采用零功耗终端特有的接入技术，或者采用网络标识和接入技术列表中包含的终端设备的位置和/或支持的频段对应的运营商的网络标识和接入技术，从而降低SOR过程的复杂度。
方式二：
第二网元不向第一网元反馈SOR信息：
第一网元从第二网元接收第二消息，该第二消息不携带SOR信息。
相应地，第一网元发送的注册接受消息中，也不携带SOR信息。这样，终端设备在接收到注册接受消息后，不执行SOR过程。
通过这种方式，第一网元向终端设备反馈的注册接受消息中不携带SOR信息，则终端设备可以直接跳过SOR过程，也能够达到降低复杂度的效果。
图7A是根据本申请实施例的一种通信方法700的一种示意性流程图，该方法可以应用于图1-3所示的系统，但并不仅限于此。该方法包括以下内容的至少部分内容。
S710、第二网元向第一网元发送第二消息，第二消息携带终端设备的标识信息。
在一些实施方式中，第一网元可以包括AMF等设备，第二网元可以包括UDM或UDR等设备。
在一些示例中，第二消息包括Nudm_SubscriberDataManagement_Get消息或者Nudm_UEContextManagement_Update消息的响应消息等。
图7B是根据本申请实施例的一种通信方法700的另一种示意性流程图，如图7B所示，在步骤S710之前，还可以包括，
S701、第二网元从第一网元接收第三消息，该第三消息携带终端设备的标识信息、终端设备的位置、终端设备支持的频段和第一指示中的至少之一；其中，第一指示可以用于指示终端设备是否为零功耗终端。终端设备的位置可以包括终端设备所在的TAI。在一些示例中，第三消息可以包括用户数据管理获取(Nudm_SubscriberDataManagement_Get)消息或用户设备上下文管理更新(Nudm_UEContextManagement_Update)消息。
S702、第二网元根据终端设备的标识信息、该终端设备的位置、该终端设备支持的频段和第一指示中的至少之一，确定SOR信息。之后，继续执行步骤S710。
或者，第二网元向第三网元发送终端设备的标识信息、终端设备的位置、终端设备支持的频段和第一指示中的至少之一；第二网元从第三网元接收SOR信息。其中，第三网元可以包括SOR-AF，该SOR信息由第三网元根据接收的信息确定。之后，继续执行步骤S710。
或者，如果第二网元根据第一指示，获知终端设备是零功耗终端，则第二网元可以确定第二消息不携带SOR信息，直接执行步骤S710，即，向第一网元发送第二消息，该第二消息中不携带SOR信息。通过这种方式，第一网元向终端设备反馈的注册接受消息中不携带SOR信息，则终端设备可以直接跳过SOR过程，也能够达到降低复杂度的效果。
如果终端设备是零功耗终端，并且步骤S702中第二网元确定或接收到SOR信息，则步骤S710中，第二网元向第一网元发送的第二消息还携带SOR信息。相应地，第一网元向终端设备发送的注册接受消息中携带SOR信息。该SOR信息可以是简化的SOR信息，具体地：
在一些示例中，SOR信息中不包含接入技术。
在一些示例中，SOR信息根据终端设备的位置和/或终端设备支持的频段确定。例如，SOR信息中包含网络标识和接入技术列表，该网络标识和接入技术列表根据终端设备的位置和/或终端设备支持的频段确定。例如，网络标识和接入技术列表中的内容包括：终端设备的位置对应的运营商的网络标识和接入技术；和/或，终端设备支持的频段对应的运营商的网络标识和接入技术。
在一些实施方式中，SOR信息中不包含SOR-CMCI。
在一些实施方式中，SOR信息中包含第一定时器。
利用该SOR信息，终端设备可以在第一定时器超时后进入空闲态并执行选网，并且在选网过程中，终端设备可以采用零功耗终端特有的接入技术，或者采用网络标识和接入技术列表中包含的终端设备的位置和/或支持的频段对应的运营商的网络标识和接入技术，从而降低SOR过程的复杂度。
需要说明的是，如果采用无需确定SOR信息的方式，则第三消息中可以不携带终端设备的位置和支持的频段(因为这些信息是用于确定SOR信息的)，而只携带终端设备的标识信息和第一指示，后续一系列相关信息中也可以不携带终端设备的位置和支持的频段。
图8是根据本申请实施例的一种通信方法800的示意性流程图，该方法可以应用于图1-3所示的系统，但并不仅限于此。该方法包括以下内容的至少部分内容。
S810、第三网元从第二网元接收终端设备的标识信息、终端设备的位置、终端设备支持的频段和第一指示中的至少之一；其中，第一指示可以用于指示终端设备是否为零功耗终端。
S820、第三网元确定终端设备的SOR信息。
其中，第三网元可以包括SOR-AF等网元。第二网元可以包括UDM或UDR等网元。
在一些实施方式中，还可以包括，第三网元将终端设备的SOR信息发送至第二网元。
如果终端设备是零功耗终端，则第三网元确定并发送的SOR信息可以是简化的SOR信息，具体地：
在一些示例中，SOR信息中不包含接入技术。
在一些示例中，SOR信息根据终端设备的位置和/或终端设备支持的频段确定。例如，SOR信息中包含网络标识和接入技术列表，该网络标识和接入技术列表根据终端设备的位置和/或终端设备支持的频段确定。例如，网络标识和接入技术列表中的内容包括：终端设备的位置对应的运营商的网络标识和接入技术；和/或，终端设备支持的频段对应的运营商的网络标识和接入技术。
在一些实施方式中，SOR信息中不包含SOR-CMCI。
在一些实施方式中，SOR信息中包含第一定时器。
第三网元确定的SOR信息经由第二网元、第一网元发送至终端设备。这样，终端设备可以在第一定时器超时后进入空闲态并执行选网，并且在选网过程中，终端设备可以采用零功耗终端特有的接入技术，或者采用网络标识和接入技术列表中包含的终端设备的位置和/或支持的频段对应的运营商的网络标识和接入技术，从而降低SOR过程的复杂度。
图9是根据本申请实施例的一种通信方法900的示意性流程图，该方法可以应用于图1-3所示的系统，但并不仅限于此。该方法包括以下内容的至少部分内容。
S910、接入设备从终端设备接收注册请求消息，该注册请求消息携带终端设备的标识信息。
S920、接入设备向第一网元转发该注册请求消息。
其中，接入设备可以包括基站等。第一网元可以包括AMF等网元。
例如，接入设备从终端设备接收包含注册请求消息的RRC消息。
在一些实施方式中，注册请求消息携带第一指示和/或终端设备支持的频段，第一指示用于指示终端设备是否为零功耗终端。
在一些实施方式中，还包括，接入设备向第一网元发送终端设备使用的接入技术和/或终端设备的位置。
接入设备向第一网元发送的信息中，包含用于确定是否生成终端设备的SOR信息、以及SOR信息的具体内容的相关信息，从而使终端设备可以根据该SOR信息进行简化的SOR流程、或者直接跳过SOR流程，从而降低终端设备的复杂度。
以下参照附图，举具体的实施例详解介绍本申请。
实施例一：
在本实施例中，以接入设备包括基站、第一网元包括AMF、第二网元包括UDM/UDR、第三网元包括SOR-AF为例进行介绍，但该示例并不作为对本申请的限制。
图10是本申请实施例一的实现流程图，包括：
S1010、终端设备向AMF发送包含注册请求(Registration Request)消息的RRC消息，该注册请求消息中携带终端设备的标识信息。该注册请求消息还可以携带终端设备支持的频段，和/或，用于指示该终端设备是否为零功耗终端的指示信息。
例如，终端设备可以在注册请求消息中携带AIoT能力，该AIoT能力可以作为用于指示终端设备是否为零功耗终端的指示信息。
在一些示例中，AIoT能力取值为1时，表示终端设备具备AIoT能力，该终端设备是零功耗终端；AIoT能力取值为0时，表示终端设备不具备AIoT能力，该终端设备不是零功耗终端。在另一些示例中，AIoT能力取值为1时，表示终端设备不具备AIoT能力，该终端设备不是零功耗终端；AIoT能力取值为0时，表示终端设备具备AIoT能力，该终端设备是零功耗终端。
在一些示例中，该注册请求消息可以通过RAN中的基站转发至AMF。例如，基站接收到包含注册请求消息的RRC消息之后，如果该注册请求消息中携带用于指示该终端设备是否为零功耗终端的指示信息，则可以将注册请求消息转发至AMF，同时发送终端设备的位置。终端设备的位置可以为终端设备所在的TAI。
如果该注册请求消息中不携带用于指示该终端设备是否为零功耗终端的指示信息，则基站可以将注册请求消息转发至AMF，同时发送终端设备的位置和终端设备使用的接入技术。例如，基站向AMF指示终端设备使用的接入技术是零功耗设备特有的技术，则AMF可以根据该指示确定出终端设备是零功耗终端。
S1030、AMF向UDM/UDR请求终端设备的签约信息，AMF向UDM/UDR发送Nudm_SubscriberDataManagement_Get消息或者Nudm_UEContextManagement_Update消息；其中携带终端设备的标识信息，终端设备的位置，终端设备支持的频段，AIOT指示(AIoT indication)。AIoT indication用于指示终端设备是否为零功耗终端。在一些示例中，AIoT indication取值为1时，表示终端设备是零功耗终端；AIoT indication取值为0时，表示终端设备不是零功耗终端。在另一些示例中，AIoT indication取值为1时，表示终端设备不是零功耗终端；AIoT indication取值为0时，表示终端设备是零功耗终端。其中，AIoT indication是可选参数。例如，如果UDM/UDR能够通过终端设备的标识信息，从终端设备的签约信息查找到该终端设备是否为零功耗终端，则不需要携带AIoT indication。例如，运营商可以在终端设备入网许可时，在UDM/UDR中记录该终端设备是否为零功耗终端、终端设备支持的频段等信息。
S1040、如果UDM/UDR无法本地获取终端设备的SOR信息，则UDM/UDR可以向SOR-AF请求终端设备的SOR信息，例如，UDM/UDR向SOR-AF发送终端设备的标识信息、终端设备的位置、终端设备支持的频段、AIoT indication中的至少之一。
S1050、SOR-AF根据AIoT indication确定终端设备是否为零功耗终端，如果终端设备是零功耗终端，则SOR-AF为该终端设备确定简化的SOR信息，并向UDM/UDR返回响应消息，该响应消息中可以携带终端设备的标识信息和该SOR信息。
简化的方式包括以下一种或多种：
(1)如果零功耗终端使用特定的接入技术，则不需要在PLMN ID and access technology list中包含接入技术，只发PLMN list；
(2)根据终端设备的位置，只配置终端设备当前所在的国家或地区的运营商的PLMN ID and access technology list，而不是全集；
(3)根据终端设备支持的频段，只配置该频段对应的运营商的PLMN ID and access technology list，而不是全集；
(4)不配置SOR-CMCI；因为AIoT设备一般都是传输测量、位置参数等小数据，对业务的连续传输的需求不大，可以在收到SOR信息后直接进入空闲态，因此可以不配置SOR-CMCI。其中，将SOR-CMCI indicator设置为0，代表没有SOR-CMCI；
(5)如果HPLMN想要控制UE重新选网的时间，可以配置一个定时器；
(6)网络不需要UE回复确认(ACK)消息。
S1060、UDM/UDR向AMF回复Nudm_SubscriberDataManagement_Get消息或者Nudm_UEContextManagement_Update消息的响应消息，其中包含终端设备的标识信息(UE ID)和SOR信息。
S1070、AMF向终端设备发送注册接受(Registration Accept)消息，例如，该注册接受消息可以通过基站转发给终端设备，其中，注册接受消息中包含SOR透明容器(SOR transparent container)，SOR透明容器中包含SOR信息。或者，AMF也可以在注册流程之后发送SOR信息，例如，在注册流程之后，AMF向终端设备发送第一消息，该第一消息中包含SOR透明容器，SOR透明容器中包含SOR信息。该第一消息可以包括下行NAS传输(Downlink NAS transport)消息。
实施例二：
在本实施例中，以接入设备包括基站、第一网元包括AMF、第二网元包括UDM/UDR为例进行介绍，但该示例并不作为对本申请的限制。
图11是本申请实施例二的实现流程图，包括：
S1110、终端设备向AMF发送包含注册请求消息(Registration Request)的RRC消息，该注册请求消息中携带终端设备的标识信息。该注册请求消息还可以携带终端设备支持的频段，和/或，用于指示该终端设备是否为零功耗终端的指示信息。
例如，终端设备可以在注册请求消息中携带AIoT能力，该AIoT能力可以作为用于指示终端设备是否为零功耗终端的指示信息。
在一些示例中，AIoT能力取值为1时，表示终端设备具备AIoT能力，该终端设备是零功耗终端；AIoT能力取值为0时，表示终端设备不具备AIoT能力，该终端设备不是零功耗终端。在另一些示例中，AIoT能力取值为1时，表示终端设备不具备AIoT能力，该终端设备不是零功耗终端；AIoT能力取值为0时，表示终端设备具备AIoT能力，该终端设备是零功耗终端。
在一些示例中，该注册请求消息可以通过RAN中的基站转发至AMF。例如，接收到包含注册请求消息的RRC消息之后，如果该注册请求消息中携带用于指示该终端设备是否为零功耗终端的指示信息，则可以将注册请求消息转发至AMF，同时发送终端设备的位置。终端设备的位置可以为终端设备所在的TAI。
如果该注册请求消息中不携带用于指示该终端设备是否为零功耗终端的指示信息，则基站可以将注册请求消息转发至AMF，同时发送终端设备的位置和终端设备使用的接入技术。例如，基站向AMF指示终端设备使用的接入技术是零功耗设备特有的技术，则AMF可以根据该指示确定出终端设备是零功耗终端。
S1130、AMF向UDM/UDR请求终端设备的签约信息，AMF向UDM/UDR发送Nudm_SubscriberDataManagement_Get消息或者Nudm_UEContextManagement_Update消息；其中携带终端设备的标识信息，终端设备的位置，终端设备支持的频段，AIOT指示(AIoT indication)。AIoT indication用于指示终端设备是否为零功耗终端。在一些示例中，AIoT indication取值为1时，表示终端设备是零功耗终端；AIoT indication取值为0时，表示终端设备不是零功耗终端。在另一些示例中，AIoT indication取值为1时，表示终端设备不是零功耗终端；AIoT indication取值为0时，表示终端设备是零功耗终端。其中，AIoT indication是可选参数。例如，如果UDM/UDR能够 通过终端设备的标识信息，从终端设备的签约信息查找到该终端设备是否为零功耗终端，则不需要携带AIoT indication。例如，运营商可以在终端设备入网许可时，在UDM/UDR中记录该终端设备是否为零功耗终端、终端设备支持的频段等信息。
S1140、如果UDM/UDR能够本地获取终端设备的SOR信息，UDM/UDR根据AIoT indication确定终端设备是否为零功耗终端，如果终端设备是零功耗终端，则UDM/UDR为该终端设备确定简化的SOR信息，简化的方式包括以下一种或多种：
(1)如果零功耗终端使用特定的接入技术，则不需要在PLMN ID and access technology list中包含接入技术，只发PLMN list；
(2)根据终端设备的位置，只配置终端设备当前所在的国家或地区的运营商的PLMN ID and access technology list，而不是全集；
(3)根据终端设备支持的频段，只配置该频段对应的运营商的PLMN ID and access technology list，而不是全集；
(4)不配置SOR-CMCI；因为AIoT设备一般都是传输测量、位置参数等小数据，对业务的连续传输的需求不大，可以在收到SOR信息后直接进入空闲态，因此可以不配置SOR-CMCI。其中，将SOR-CMCI indicator设置为0，代表没有SOR-CMCI；
(5)如果HPLMN想要控制UE重新选网的时间，可以配置一个定时器；
(6)网络不需要UE回复确认(ACK)消息。
UDM/UDR向AMF回复Nudm_SubscriberDataManagement_Get消息或者Nudm_UEContextManagement_Update消息的响应消息，其中包含终端设备的标识信息(UE ID)和SOR信息。
S1150、AMF向终端设备发送注册接受(Registration Accept)消息，例如，该注册接受消息可以通过基站转发给终端设备，其中，注册接受消息中包含SOR透明容器(SOR transparent container)，SOR透明容器中包含SOR信息。或者，AMF也可以在注册流程之后发送SOR信息，例如，在注册流程之后，AMF向终端设备发送第一消息，该第一消息中包含SOR透明容器，SOR透明容器中包含SOR信息。该第一消息可以包括下行NAS传输(Downlink NAS transport)消息。
实施例三：
在本实施例中，以接入设备包括基站、第一网元包括AMF、第二网元包括UDM/UDR为例进行介绍，但该示例并不作为对本申请的限制。
图12是本申请实施例三的实现流程图，包括：
S1210、终端设备向终端设备发送包含注册请求消息(Registration Request)的RRC消息，该注册请求消息中携带终端设备的标识信息。该注册请求消息还可以携带终端设备支持的频段，和/或，用于指示该终端设备是否为零功耗终端的指示信息。
例如，终端设备可以在注册请求消息中携带AIoT能力，该AIoT能力可以作为用于指示终端设备是否为零功耗终端的指示信息。
在一些示例中，AIoT能力取值为1时，表示终端设备具备AIoT能力，该终端设备是零功耗终端；AIoT能力取值为0时，表示终端设备不具备AIoT能力，该终端设备不是零功耗终端。在另一些示例中，AIoT能力取值为1时，表示终端设备不具备AIoT能力，该终端设备不是零功耗终端；AIoT能力取值为0时，表示终端设备具备AIoT能力，该终端设备是零功耗终端。
在一些示例中，该注册请求消息可以通过RAN中的基站转发至AMF。例如，基站接收到包含注册请求消息的RRC消息之后，如果该注册请求消息中携带用于指示该终端设备是否为零功耗终端的指示信息，则可以将注册请求消息转发至AMF。
如果该注册请求消息中不携带用于指示该终端设备是否为零功耗终端的指示信息，则基站可以将注册请求消息转发至AMF，同时发送终端设备使用的接入技术。例如，基站向AMF指示终端设备使用的接入技术是零功耗设备特有的技术，则AMF可以根据该指示确定出终端设备是零功耗终端。
S1230、AMF向UDM/UDR请求终端设备的签约信息，AMF向UDM/UDR发送用户数据管理获取(Nudm_SubscriberDataManagement_Get)消息或用户设备上下文管理更新(Nudm_UEContextManagement_Update)消息；其中携带终端设备的标识信息和AIOT指示(AIoT indication)。AIoT indication用于指示终端设备是否为零功耗终端。在一些示例中，AIoT indication取值为1时，表示终端设备是零功耗终端；AIoT indication取值为0时，表示终端设备不是零功耗终端。在另一些示例中，AIoT indication取值为1时，表示终端设备不是零功耗终端；AIoT indication取值为0时，表示终端设备是零功耗终端。其中，AIoT indication是可选参数。例如，如果UDM/UDR能够通过终端设备的标识信息，从终端设备的签约信息查找到该终端设备是否为零功耗终端，则不需要携带AIoT indication。例如，运营商可以在终端设备入网许可时，在UDM/UDR中记录该终端设备是否为零功耗终端、终端设备支持的频段等信息。
S1240、UDM/UDR根据AIoT indication确定终端设备是零功耗终端，则UDM/UDR决定不向终端侧发送SOR信息，从而避免终端设备执行SOR过程。UDM/UDR向AMF发送Nudm_SubscriberDataManagement_Get消息或者Nudm_UEContextManagement_Update消息的响应消息，其中不携带SOR信息。
S1250、AMF向终端设备发送注册接受(Registration Accept)消息，例如，该注册接受消息可以通过基站转发给终端设备，其中，注册接受消息中不携带SOR信息。
本申请实施例还提出一种终端设备，图13是根据本申请实施例的终端设备1300结构示意图，包括：
第一发送单元1301，用于向第一网元发送注册请求消息，该注册请求消息携带该终端设备的标识信息。
第一接收单元1302，用于从第一网元接收注册接受消息。
在一些实施方式中，注册接受消息SOR信息。
其中，注册接受消息可以携带SOR透明容器，SOR透明容器携带SOR信息。
图14是根据本申请实施例的终端设备1400结构示意图，如图14所示，该终端设备还包括：
第二接收单元1403，用于接收第一消息，第一消息携带SOR信息。
其中，第一消息可以携带SOR透明容器，SOR透明容器携带SOR信息。
在一些实施方式中，第一消息包括下行NAS传输消息。
在一些实施方式中，注册请求消息还携带第一指示和/或所述终端设备支持的频段，所述第一指示用于指示所述终端设备是否为零功耗终端。
在一些实施方式中，在终端设备是零功耗终端的情况下，所述注册接受消息携带SOR信息。
在一些实施方式中，SOR信息中不包含接入技术。
在一些实施方式中，SOR信息中包含网络标识和接入技术列表，所述网络标识和接入技术列表根据所述终端设备的位置和/或所述终端设备支持的频段确定。
在一些实施方式中，网络标识和接入技术列表中的内容包括：所述终端设备的位置对应的运营商的网络标识和接入技术；和/或，所述终端设备支持的频段对应的运营商的网络标识和接入技术。
在一些实施方式中，SOR信息中不包含SOR-CMCI。
在一些实施方式中，SOR信息中包含第一定时器。
在一些实施方式中，在终端设备是零功耗终端的情况下，所述注册接受消息不携带SOR信息。
在一些实施方式中，终端设备包括零功耗终端。
应理解，根据本申请实施例的终端设备中的单元的上述及其他操作和/或功能分别为了实现图4和图5的方法的终端设备的相应流程，为了简洁，在此不再赘述。
本申请实施例还提出一种第一网元，图15是根据本申请实施例的第一网元1500的结构示意图，包括：
第三接收单元1501，用于从第二网元接收第二消息，该第二消息携带终端设备的标识信息；
第二发送单元1502，用于发送注册接受消息。
在一些实施方式中，第二消息还携带漫游控制SOR信息。
在一些实施方式中，注册接受消息携带所述SOR信息。
其中，注册接受消息可以携带SOR透明容器，SOR透明容器携带所述SOR信息。
图16是根据本申请实施例的第一网元1600的结构示意图，如图16所示，第一网元还可以包括：
第三发送单元1603，用于发送第一消息，所述第一消息携带所述SOR信息。
其中，第一消息可以携带SOR透明容器，SOR透明容器携带所述SOR信息。
在一些实施方式中，第一消息包括下行NAS传输消息。
如图16所示，第一网元还可以包括：
第四发送单元1604，用于向所述第二网元发送第三消息，所述第三消息携带所述终端设备的标识信息、所述终端设备的位置、所述终端设备支持的频段和第一指示中的至少之一；其中，
所述第一指示用于指示所述终端设备是否为零功耗终端。
如图16所示，第一网元还可以包括：
第四接收单元1605，用于接收注册请求消息、所述终端设备的位置和第二指示中的至少之一；其中，
所述第二指示用于指示所述终端设备使用第一接入技术。
在一些实施方式中，第一接入技术包括零功耗终端使用的接入技术。
如图16所示，第一网元还可以包括：
第一确定单元1606，用于根据所述第二指示，确定所述终端设备是否为零功耗终端。
在一些实施方式中，注册请求消息携带所述终端设备的标识信息、所述终端设备支持的频段和所述第一指示中的至少之一。
在一些实施方式中，第三消息包括用户数据管理获取消息或用户设备上下文管理更新消息。
在一些实施方式中，在终端设备是零功耗终端的情况下，所述第二消息携带SOR信息，并且所述SOR信息根据所述终端设备的位置和/或所述终端设备支持的频段确定。
在一些实施方式中，SOR信息中不包含接入技术。
在一些实施方式中，SOR信息中包含网络标识和接入技术列表，所述网络标识和接入技术列表根据所述终端设备的位置和/或所述终端设备支持的频段确定。
在一些实施方式中，网络标识和接入技术列表中的内容包括：所述终端设备的位置对应的运营商的网络标识和接入技术；和/或，所述终端设备支持的频段对应的运营商的网络标识和接入技术。
在一些实施方式中，SOR信息中不包含SOR-CMCI。
在一些实施方式中，SOR信息中包含第一定时器。
在一些实施方式中，在所述终端设备是零功耗终端的情况下，所述第二消息不携带SOR信息。
在一些实施方式中，第一网元包括AMF。
在一些实施方式中，第二网元包括UDM或UDR。
在一些实施方式中，第二消息包括响应消息。
应理解，根据本申请实施例的第一网元中的单元的上述及其他操作和/或功能分别为了实现图4、图6A和图6B的方法中的第一网元的相应流程，为了简洁，在此不再赘述。
本申请实施例还提出一种第二网元，图17是根据本申请实施例的第二网元1700结构示意图，包括：
第五发送单元1701，用于向第一网元发送第二消息，该第二消息携带终端设备的标识信息。
在一些实施方式中，第二消息还携带SOR信息。
图18是根据本申请实施例的第二网元1800的结构示意图，如图18所示，第二网元还可以包括：
第五接收单元1802，用于从所述第一网元接收第三消息，所述第三消息携带所述终端设备的标识信息、所述终端设备的位置、所述终端设备支持的频段和第一指示中的至少之一；其中，
所述第一指示用于指示所述终端设备是否为零功耗终端。
如图18所示，第二网元还可以包括：
第六发送单元1803，用于向第三网元发送所述终端设备的标识信息、所述终端设备的位置、所述终端设备支持的频段和第一指示中的至少之一；
第六接收单元1804，用于从所述第三网元接收所述SOR信息。
如图18所示，第二网元还可以包括：
第二确定单元1805，用于根据所述终端设备的标识信息、所述终端设备的位置、所述终端设备支持的频段和第一指示中的至少之一，确定所述SOR信息。
在一些实施方式中，第三消息包括用户数据管理获取消息或用户设备上下文管理更新消息。
在一些实施方式中，在所述终端设备是零功耗终端的情况下，所述SOR信息中不包含接入技术。
在一些实施方式中，在所述终端设备是零功耗终端的情况下，所述SOR信息根据所述终端设备的位置和/或所述终端设备支持的频段确定。
在一些实施方式中，所述SOR信息中包含网络标识和接入技术列表，所述网络标识和接入技术列表根据所述终端设备的位置和/或所述终端设备支持的频段确定。
在一些实施方式中，所述网络标识和接入技术列表中的内容包括：所述终端设备的位置对应的运营商的网络标识和接入技术；和/或，所述终端设备支持的频段对应的运营商的网络标识和接入技术。
在一些实施方式中，SOR信息中不包含SOR-CMCI。
在一些实施方式中，SOR信息中包含第一定时器。
如图18所示，第二网元还可以包括：
第三确定单元1806，用于在所述终端设备是零功耗终端的情况下，所述第二网元确定第二消息不携带所述SOR信息。
在一些实施方式中，第二网元包括UDM或UDR。
在一些实施方式中，第一网元包括AMF。
在一些实施方式中，第三网元包括SOR-AF。
在一些实施方式中，第二消息包括响应消息。
应理解，根据本申请实施例的第二网元中的单元的上述及其他操作和/或功能分别为了实现图4、图7A、图7B的方法中的第二网元的相应流程，为了简洁，在此不再赘述。
本申请实施例还提出一种第三网元，图19是根据本申请实施例的第三网元1900结构示意图，包括：
第七接收单元1901，用于从第二网元接收终端设备的标识信息、该终端设备的位置、该终端设备支持的频段和第一指示中的至少之一；其中，该第一指示用于指示该终端设备是否为零功耗终端。
第四确定单元1902，用于确定该终端设备的SOR信息。
图20是根据本申请实施例的第三网元2000的结构示意图，如图20所示，第三网元还可以包括：
第七发送单元2003，用于将所述终端设备的SOR信息发送至所述第二网元。
在一些实施方式中，所述终端设备是零功耗终端的情况下，所述SOR信息中不包含接入技术。
在一些实施方式中，所述终端设备是零功耗终端的情况下，所述第三网元根据所述终端设备的位置和/或所述终端设备支持的频段确定所述SOR信息。
在一些实施方式中，SOR信息中包含网络标识和接入技术列表；所述第三网元根据所述终端设备的位置和/或所述终端设备支持的频段，确定所述网络标识和接入技术列表。
在一些实施方式中，网络标识和接入技术列表中的内容包括：所述终端设备的位置对应的运营商的网络标识和接入技术；和/或，所述终端设备支持的频段对应的运营商的网络标识和接入技术。
在一些实施方式中，SOR信息中不包含SOR-CMCI。
在一些实施方式中，SOR信息中包含第一定时器。
在一些实施方式中，第三网元包括SOR-AF。
在一些实施方式中，第二网元包括UDM或UDR。
应理解，根据本申请实施例的第三网元中的单元的上述及其他操作和/或功能分别为了实现图4、图8的方法中的第三网元的相应流程，为了简洁，在此不再赘述。
本申请实施例还提出一种接入设备，图21是根据本申请实施例的接入设备2100结构示意图，包括：
第八接收单元2101，用于从终端设备接收注册请求消息，该注册请求消息携带该终端设备的标识信息。
第八发送单元2102，用于向第一网元转发该注册请求消息。
在一些实施方式中，注册请求消息携带第一指示和/或所述终端设备支持的频段，第一指示用于指示所述终端设备是否为零功耗终端。
图22是根据本申请实施例的接入设备2200的结构示意图，如图22所示，接入设备还可以包括：
第九发送单元2203，用于向第一网元发送所述终端设备使用的接入技术和/或所述终端设备的位置。
在一些实施方式中，第一网元包括AMF。
应理解，根据本申请实施例的接入设备中的单元的上述及其他操作和/或功能分别为了实现图4、图9方法中的接入设备的相应流程，为了简洁，在此不再赘述。
需要说明，关于本申请实施例的通信设备中的各个模块(子模块、单元或组件等)所描述的功能，可以由不同的模块(子模块、单元或组件等)实现，也可以由同一个模块(子模块、单元或组件等)实现，举例来说，第一接收模块与第二接收模块可以是不同的模块，也可以是同一个模块，均能够实现其在本申请实施例中的相应功能。此外，本申请实施例中的发送模块和接收模块，可通过设备的收发机实现，其余各模块中的部分或全部可通过设备的处理器实现。
图23是根据本申请实施例的通信设备2300示意性结构图。图23所示的通信设备2300包括处理器2310，处理器2310可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
在一些实施方式中，如图23所示，通信设备2300还可以包括存储器2320。其中，处理器2310可以从存储器2320中调用并运行计算机程序，以实现本申请实施例中的通信设备。
其中，存储器2320可以是独立于处理器2310的一个单独的器件，也可以集成在处理器2310中。
在一些实施方式中，如图23所示，通信设备2300还可以包括收发器2330，处理器2310可以控制该收发器2330与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器2330可以包括发射机和接收机。收发器2330还可以进一步包括天线，天线的数量可以为一个或多个。
在一些实施方式中，该通信设备2300可为本申请实施例的通信设备，并且该通信设备2300可以实现本申请实施例的各个方法中由通信设备实现的相应流程，为了简洁，在此不再赘述。
图24是根据本申请实施例的芯片2400的示意性结构图。图24所示的芯片2400包括处理器2410，处理器2410可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
在一些实施方式中，如图24所示，芯片2400还可以包括存储器2420。其中，处理器2410可以从存储器2420中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器2420可以是独立于处理器2410的一个单独的器件，也可以集成在处理器2410中。
在一些实施方式中，该芯片2400还可以包括输入接口2430。其中，处理器2410可以控制该输入接口2430与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
在一些实施方式中，该芯片2400还可以包括输出接口2440。其中，处理器2410可以控制该输出接口2440与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
在一些实施方式中，该芯片可应用于本申请实施例中的通信设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
上述提及的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、现成可 编程门阵列(field programmable gate array，FPGA)、专用集成电路(application specific integrated circuit，ASIC)或者其他可编程逻辑器件、晶体管逻辑器件、分立硬件组件等。其中，上述提到的通用处理器可以是微处理器或者也可以是任何常规的处理器等。
上述提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行该计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。该计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，该计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以该权利要求的保护范围为准。

Claims (79)

  1. 一种通信方法，包括：
    终端设备向第一网元发送注册请求消息，所述注册请求消息携带所述终端设备的标识信息；
    终端设备从所述第一网元接收注册接受消息。
  2. 根据权利要求1所述的方法，其中，所述注册接受消息携带漫游控制SOR信息。
  3. 根据权利要求2所述的方法，其中，所述注册接受消息携带SOR信息，包括：
    所述注册接受消息携带SOR透明容器，所述SOR透明容器携带所述SOR信息。
  4. 根据权利要求1所述的方法，还包括，所述终端设备从所述第一网元接收第一消息，所述第一消息携带SOR信息。
  5. 根据权利要求4所述的方法，其中，所述第一消息携带SOR信息，包括：
    所述第一消息携带SOR透明容器，所述SOR透明容器携带所述SOR信息。
  6. 根据权利要求4或5所述的方法，其中，所述第一消息包括下行非接入层NAS传输消息。
  7. 根据权利要求1-6中任一所述的方法，其中，注册请求消息还携带第一指示和/或所述终端设备支持的频段，所述第一指示用于指示所述终端设备是否为零功耗终端。
  8. 根据权利要求1-7中任一所述的方法，其中，在所述终端设备是零功耗终端的情况下，所述注册接受消息携带SOR信息。
  9. 根据权利要求8所述的方法，其中，所述SOR信息中不包含接入技术。
  10. 根据权利要求8或9所述的方法，其中，所述SOR信息中包含网络标识和接入技术列表，所述网络标识和接入技术列表根据所述终端设备的位置和/或所述终端设备支持的频段确定。
  11. 根据权利要求10所述的方法，其中，所述网络标识和接入技术列表中的内容包括：所述终端设备的位置对应的运营商的网络标识和接入技术；和/或，所述终端设备支持的频段对应的运营商的网络标识和接入技术。
  12. 根据权利要求7-11中任一所述的方法，其中，所述SOR信息中不包含SOR-连接模式控制信息CMCI。
  13. 根据权利要求7-12中任一所述的方法，其中，所述SOR信息中包含第一定时器。
  14. 根据权利要求1-7中任一所述的方法，其中，在所述终端设备是零功耗终端的情况下，所述注册接受消息不携带SOR信息。
  15. 根据权利要求1-14中任一所述的方法，其中，所述终端设备包括零功耗终端。
  16. 一种通信方法，包括：
    第一网元从第二网元接收第二消息，所述第二消息携带终端设备的标识信息；
    所述第一网元向终端设备发送注册接受消息。
  17. 根据权利要求16所述的方法，其中，所述第二消息还携带漫游控制SOR信息。
  18. 根据权利要求17所述的方法，其中，所述注册接受消息携带所述SOR信息。
  19. 根据权利要求18所述的方法，其中，所述注册接受消息携带所述SOR信息，包括：
    所述注册接受消息携带SOR透明容器，所述SOR透明容器携带所述SOR信息。
  20. 根据权利要求17所述的方法，还包括，所述第一网元向所述终端设备发送第一消息，所述第一消息携带所述SOR信息。
  21. 根据权利要求20所述的方法，其中，所述第一消息携带所述SOR信息，包括：
    所述第一消息携带SOR透明容器，所述SOR透明容器携带所述SOR信息。
  22. 根据权利要求20或21所述的方法，其中，所述第一消息包括下行NAS传输消息。
  23. 根据权利要求16-22中任一所述的方法，所述第一网元从第二网元接收第二消息之前，还包括：
    所述第一网元向所述第二网元发送第三消息，所述第三消息携带所述终端设备的标识信息、所述终端设备的位置、所述终端设备支持的频段和第一指示中的至少之一；其中，
    所述第一指示用于指示所述终端设备是否为零功耗终端。
  24. 根据权利要求23所述的方法，所述第一网元向所述第二网元发送第三消息之前，还包括：
    所述第一网元接收注册请求消息、所述终端设备的位置和第二指示中的至少之一；其中，
    所述第二指示用于指示所述终端设备使用第一接入技术。
  25. 根据权利要求24所述的方法，其中，所述第一接入技术包括零功耗终端使用的接入技术。
  26. 根据权利要求24或25所述的方法，还包括，所述第一网元根据所述第二指示，确定所述终端设备是否为零功耗终端。
  27. 根据权利要求26所述的方法，其中，所述注册请求消息携带所述终端设备的标识信息、所述终端设备支持的频段和所述第一指示中的至少之一。
  28. 根据权利要求23-27中任一所述的方法，其中，所述第三消息包括用户数据管理获取消息或用户设备上下文管理更新消息。
  29. 根据权利要求16-28中任一所述的方法，其中，在所述终端设备是零功耗终端的情况下，所述第二消息携带SOR信息，并且所述SOR信息根据所述终端设备的位置和/或所述终端设备支持的频段确定。
  30. 根据权利要求29所述的方法，其中，所述SOR信息中不包含接入技术。
  31. 根据权利要求29或30所述的方法，其中，所述SOR信息中包含网络标识和接入技术列表，所述网络标识和接入技术列表根据所述终端设备的位置和/或所述终端设备支持的频段确定。
  32. 根据权利要求31所述的方法，其中，所述网络标识和接入技术列表中的内容包括：所述终端设备的位置对应的运营商的网络标识和接入技术；和/或，所述终端设备支持的频段对应的运营商的网络标识和接入技术。
  33. 根据权利要求29-32中任一所述的方法，其中，所述SOR信息中不包含SOR-CMCI。
  34. 根据权利要求29-33中任一所述的方法，其中，所述SOR信息中包含第一定时器。
  35. 根据权利要求16-28中任一所述的方法，其中，在所述终端设备是零功耗终端的情况下，所述第二消息不携带SOR信息。
  36. 根据权利要求16-35中任一所述的方法，其中，所述第一网元包括AMF。
  37. 根据权利要求16-36中任一所述的方法，其中，所述第二网元包括UDM或UDR。
  38. 根据权利要求16-37中任一所述的方法，其中，所述第二消息包括响应消息。
  39. 一种通信方法，包括：
    第二网元向第一网元发送第二消息，所述第二消息携带终端设备的标识信息。
  40. 根据权利要求39所述的方法，其中，所述第二消息还携带SOR信息。
  41. 根据权利要求39或40所述的方法，所述第二网元向第一网元发送第二消息之前，还包括：
    所述第二网元从所述第一网元接收第三消息，所述第三消息携带所述终端设备的标识信息、所述终端设备的位置、所述终端设备支持的频段和第一指示中的至少之一；其中，
    所述第一指示用于指示所述终端设备是否为零功耗终端。
  42. 根据权利要求41所述的方法，还包括，
    所述第二网元向第三网元发送所述终端设备的标识信息、所述终端设备的位置、所述终端设备支持的频段和第一指示中的至少之一；
    所述第二网元从所述第三网元接收所述SOR信息。
  43. 根据权利要求41所述的方法，还包括，
    所述第二网元根据所述终端设备的标识信息、所述终端设备的位置、所述终端设备支持的频段和第一指示中的至少之一，确定所述SOR信息。
  44. 根据权利要求41-43中任一所述的方法，其中，所述第三消息包括用户数据管理获取消息或用户设备上下文管理更新消息。
  45. 根据权利要求40、42-44中任一所述的方法，其中，在所述终端设备是零功耗终端的情况下，所述SOR信息中不包含接入技术。
  46. 根据权利要求40、42-45中任一所述的方法，其中，在所述终端设备是零功耗终端的情况下，所述SOR信息根据所述终端设备的位置和/或所述终端设备支持的频段确定。
  47. 根据权利要求40、42-46中任一所述的方法，其中，所述SOR信息中包含网络标识和接入技术列表，所述网络标识和接入技术列表根据所述终端设备的位置和/或所述终端设备支持的频段确定。
  48. 根据权利要求47所述的方法，其中，所述网络标识和接入技术列表中的内容包括：所述终端设备的位置对应的运营商的网络标识和接入技术；和/或，所述终端设备支持的频段对应的运营商的网络标识和接入技术。
  49. 根据权利要求40、42-48中任一所述的方法，其中，所述SOR信息中不包含SOR-CMCI。
  50. 根据权利要求40、42-49中任一所述的方法，其中，所述SOR信息中包含第一定时器。
  51. 根据权利要求41所述的方法，还包括，
    在所述终端设备是零功耗终端的情况下，所述第二网元确定第二消息不携带所述SOR信息。
  52. 根据权利要求39-51中任一所述的方法，其中，所述第二网元包括UDM或UDR。
  53. 根据权利要求39-52中任一所述的方法，其中，所述第一网元包括AMF。
  54. 根据权利要求42所述的方法，其中，所述第三网元包括SOR-AF。
  55. 根据权利要求39-54中任一所述的方法，其中，所述第二消息包括响应消息。
  56. 一种通信方法，包括：
    第三网元从第二网元接收终端设备的标识信息、所述终端设备的位置、所述终端设备支持的频段和第一指示中的至少之一；其中，所述第一指示用于指示所述终端设备是否为零功耗终端；
    所述第三网元确定所述终端设备的SOR信息。
  57. 根据权利要求56所述的方法，还包括，
    所述第三网元将所述终端设备的SOR信息发送至所述第二网元。
  58. 根据权利要求56或57所述的方法，其中，在所述终端设备是零功耗终端的情况下，所述SOR信息中不包含接入技术。
  59. 根据权利要求56-58中任一所述的方法，其中，在所述终端设备是零功耗终端的情况下，所述第三网元根据所述终端设备的位置和/或所述终端设备支持的频段确定所述SOR信息。
  60. 根据权利要求56-59中任一所述的方法，其中，所述SOR信息中包含网络标识和接入技术列表；所述第三网元根据所述终端设备的位置和/或所述终端设备支持的频段，确定所述网络标识和接入技术列表。
  61. 根据权利要求60所述的方法，其中，所述网络标识和接入技术列表中的内容包括：所述终端设备的位置对应的运营商的网络标识和接入技术；和/或，所述终端设备支持的频段对应的运营商的网络标识和接入技术。
  62. 根据权利要求56-61中任一所述的方法，其中，所述SOR信息中不包含SOR-CMCI。
  63. 根据权利要求56-62任一所述的方法，其中，所述SOR信息中包含第一定时器。
  64. 根据权利要求56-63中任一所述的方法，其中，所述第三网元包括SOR-AF。
  65. 根据权利要求56-64中任一所述的方法，其中，所述第二网元包括UDM或UDR。
  66. 一种通信方法，包括：
    接入设备从终端设备接收注册请求消息，所述注册请求消息携带所述终端设备的标识信息；
    所述接入设备向第一网元转发所述注册请求消息。
  67. 根据权利要求66所述的方法，其中，所述注册请求消息携带第一指示和/或所述终端设备支持的频段，所述第一指示用于指示所述终端设备是否为零功耗终端。
  68. 根据权利要求66或67所述的方法，还包括，所述接入设备向所述第一网元发送所述终端设备使用的接入技术和/或所述终端设备的位置。
  69. 根据权利要求66-68中任一所述的方法，其中，所述第一网元包括AMF。
  70. 一种终端设备，包括：
    第一发送单元，用于向第一网元发送注册请求消息，所述注册请求消息携带所述终端设备的标识信息；
    第一接收单元，用于从所述第一网元接收注册接受消息。
  71. 一种第一网元，包括：
    第三接收单元，用于从第二网元接收第二消息，所述第二消息携带终端设备的标识信息；
    第二发送单元，用于向终端设备发送注册接受消息。
  72. 一种第二网元，包括：
    第五发送单元，用于向第一网元发送第二消息，所述第二消息携带终端设备的标识信息。
  73. 一种第三网元，包括：
    第七接收单元，用于从第二网元接收终端设备的标识信息、所述终端设备的位置、所述终端设备支持的频段和第一指示中的至少之一；其中，所述第一指示用于指示所述终端设备是否为零功耗终端；
    第四确定单元，用于确定所述终端设备的SOR信息。
  74. 一种接入设备，包括：
    第八接收单元，用于从终端设备接收注册请求消息，所述注册请求消息携带所述终端设备的标识信息；
    第八发送单元，用于向第一网元转发所述注册请求消息。
  75. 一种通信设备，包括：处理器、存储器和收发器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，并控制所述收发器，执行如权利要求1-15、16-38、39-55、56-65、或66-69中任一项所述的方法。
  76. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1-15、16-38、39-55、56-65、或66-69中任一项所述的方法。
  77. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1-15、16-38、39-55、56-65、或66-69中任一项所述的方法。
  78. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1-15、16-38、39-55、56-65、或66-69中任一项所述的方法。
  79. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1-15、16-38、39-55、56-65、或66-69中任一项所述的方法。
PCT/CN2023/105564 2023-07-03 2023-07-03 通信方法和设备 Ceased WO2025007249A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202380099898.XA CN121488570A (zh) 2023-07-03 2023-07-03 通信方法和设备
PCT/CN2023/105564 WO2025007249A1 (zh) 2023-07-03 2023-07-03 通信方法和设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/105564 WO2025007249A1 (zh) 2023-07-03 2023-07-03 通信方法和设备

Publications (1)

Publication Number Publication Date
WO2025007249A1 true WO2025007249A1 (zh) 2025-01-09

Family

ID=94171081

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/105564 Ceased WO2025007249A1 (zh) 2023-07-03 2023-07-03 通信方法和设备

Country Status (2)

Country Link
CN (1) CN121488570A (zh)
WO (1) WO2025007249A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022177294A1 (en) * 2021-02-17 2022-08-25 Samsung Electronics Co., Ltd. Apparatus and method for handling sor-cmci configuration in wireless network
CN114980063A (zh) * 2021-02-18 2022-08-30 大唐移动通信设备有限公司 漫游引导sor信息处理方法、装置及处理器可读存储介质
US20220312360A1 (en) * 2020-08-12 2022-09-29 Apple Inc. Steering of roaming check during mobility registration

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220312360A1 (en) * 2020-08-12 2022-09-29 Apple Inc. Steering of roaming check during mobility registration
WO2022177294A1 (en) * 2021-02-17 2022-08-25 Samsung Electronics Co., Ltd. Apparatus and method for handling sor-cmci configuration in wireless network
CN114980063A (zh) * 2021-02-18 2022-08-30 大唐移动通信设备有限公司 漫游引导sor信息处理方法、装置及处理器可读存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Editor's note on de-registration or NAS signalling connection release", 3GPP DRAFT; C1-206329, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Electronic meeting; 20201015 - 20201023, 8 October 2020 (2020-10-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051951268 *
NTT DOCOMO, ERICSSON: "Introducing new requirements for CP-SOR in connected mode", 3GPP DRAFT; C1-206529, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Electronic meeting; 20201015 - 20201023, 21 October 2020 (2020-10-21), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051940816 *

Also Published As

Publication number Publication date
CN121488570A (zh) 2026-02-06

Similar Documents

Publication Publication Date Title
US20250071674A1 (en) Communication method, network device and terminal device
US20250267732A1 (en) Communication method, and device
EP4607869A1 (en) Communication methods, and devices
US20230093178A1 (en) Method for service identification and terminal device
US20250071663A1 (en) Method for accessing a network, terminal device and network device
US20250089108A1 (en) Communication method, and devices
US20250280282A1 (en) Terminal device and network device
US20240235257A1 (en) Wireless communication method, and terminal device
WO2025007249A1 (zh) 通信方法和设备
WO2024145847A1 (zh) 通信方法和设备
EP4626080A1 (en) Communication method, and device
US20260006593A1 (en) Method for wireless communication, zero-power device, and communication device
EP4697766A1 (en) Communication method and device
US20250365713A1 (en) Channel preemption methods and apparatuses, and communication device
EP4668877A1 (en) Information indication method and apparatus, and communication device
WO2026011392A1 (zh) 业务控制方法、终端设备和网络设备
US20260019783A1 (en) Communication method and device
WO2025184889A1 (zh) 通信方法和设备
WO2025184886A1 (zh) 通信方法和设备
WO2025112059A1 (zh) 通信方法和设备
WO2024159522A1 (zh) 无线通信的方法和设备

Legal Events

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

Ref document number: 23943983

Country of ref document: EP

Kind code of ref document: A1

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112025029253

Country of ref document: BR

WWE Wipo information: entry into national phase

Ref document number: 2023943983

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2023943983

Country of ref document: EP

Effective date: 20260203