[go: up one dir, main page]

WO2025020206A1 - Procédé d'enregistrement de dispositif, premier dispositif, second dispositif et dispositif de réseau - Google Patents

Procédé d'enregistrement de dispositif, premier dispositif, second dispositif et dispositif de réseau Download PDF

Info

Publication number
WO2025020206A1
WO2025020206A1 PCT/CN2023/109695 CN2023109695W WO2025020206A1 WO 2025020206 A1 WO2025020206 A1 WO 2025020206A1 CN 2023109695 W CN2023109695 W CN 2023109695W WO 2025020206 A1 WO2025020206 A1 WO 2025020206A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
network
message
registration
capability
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.)
Pending
Application number
PCT/CN2023/109695
Other languages
English (en)
Chinese (zh)
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.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co 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 Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to PCT/CN2023/109695 priority Critical patent/WO2025020206A1/fr
Priority to CN202380010320.2A priority patent/CN117223350A/zh
Publication of WO2025020206A1 publication Critical patent/WO2025020206A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/14—Mobility data transfer between corresponding nodes

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a device registration method, a first device, a second device, and a network device.
  • the Internet of Things is an extended and expanded network based on the Internet. It combines various information sensing devices with the Internet to form a huge network, realizing the interconnection of people, machines and things at any time and any place.
  • the existing registration process supports the first request initiated by the IoT device, where the IoT device directly sends the first request to the network device.
  • the embodiments of the present disclosure provide a device registration method, a first device, a second device, and a network device.
  • a device registration method is proposed, which is performed by a first device, the first device includes a relay node or an auxiliary node, and the method includes:
  • the first request is sent to the network device.
  • a first device determines a first request, and the first request is used to request registration of a second device in the network.
  • the second device communicates with a network device through the first device, the first device assists the second device in performing a registration process, thereby improving the convenience of registration and effectively dealing with registration problems under complex topology structures.
  • a device registration method is provided, which is executed by a second device.
  • the method includes:
  • the second request instructs the first device to send a first request to the network device, where the first request is used to request to register the second device in the network;
  • the first device comprises a relay node or an assisting node.
  • the second device sends a second request to the first device, and the second request instructs the first device to send a first request to the network device.
  • the first request is used to request to register the second device in the network.
  • the second device communicates with the network device through the first device, the first device assists the second device in the registration process, thereby improving the convenience of registration and effectively dealing with registration problems under complex topology structures.
  • a device registration method is proposed, which is executed by a network device.
  • the method includes:
  • the first device includes a relay node or an auxiliary node.
  • a network device receives a first request sent by a first device, and the first request is used to request registration of a second device in the network.
  • This implements a new registration process in which the network device directly receives the first request of the second device.
  • the first device assists the second device in performing the registration process, thereby improving the convenience of registration and being able to effectively deal with registration problems under complex topology structures.
  • a device registration method is proposed, which is applied to a communication system.
  • the method includes:
  • the second device sends a second request to the first device
  • the first device sends a first request to the network device according to the second request
  • the network device obtains the first request
  • the first device includes a relay node device or an auxiliary node device
  • the first request is used to request to register the second device in the network
  • the second request is used for the first device to send the first request to the network device
  • a first device includes a relay node or an auxiliary node, and the first device includes:
  • a processing module configured to determine a first request, wherein the first request is used to register a second device in a network
  • a transceiver module is used to send the first request to the network device.
  • a second device including:
  • a transceiver module configured to send a second request to the first device
  • the second request instructs the first device to send a first request to the network device, where the first request is used to request to register the second device in the network;
  • the first device comprises a relay node or an assisting node.
  • a network device including:
  • a transceiver module configured to receive a first request sent by a first device, wherein the first request is used to request registration of a second device in a network;
  • the first device includes a relay node or an auxiliary node.
  • a communication system including a first device, a second device and a network device, the first device is configured to implement the device registration method described in the first aspect, the second device is configured to implement the device registration method described in the second aspect, and the network device is configured to implement the device registration method described in the third aspect.
  • a storage medium is proposed.
  • the communication device executes the device registration method as described in the first, second or third aspect.
  • FIG1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure
  • FIG1B is a schematic diagram of a topological structure provided according to an embodiment of the present disclosure.
  • FIG1C is a schematic diagram of another topological structure provided according to an embodiment of the present disclosure.
  • FIG1D is a schematic diagram of a registration management process of a user equipment UE according to the related art
  • FIG2 is an interactive schematic diagram of a device registration method according to an embodiment of the present disclosure
  • FIG3A is a flow chart of a device registration method according to an embodiment of the present disclosure.
  • FIG3B is a flow chart of a device registration method according to an embodiment of the present disclosure.
  • FIG3C is a flow chart of a device registration method according to an embodiment of the present disclosure.
  • FIG3D is a schematic diagram of a flow chart of a device registration method according to an embodiment of the present disclosure.
  • FIG4A is a schematic diagram of a flow chart of a device registration method according to an embodiment of the present disclosure
  • FIG4B is a flow chart of a device registration method according to an embodiment of the present disclosure.
  • FIG4C is a schematic diagram of a flow chart of a device registration method according to an embodiment of the present disclosure.
  • FIG5A is a flow chart of a device registration method according to an embodiment of the present disclosure.
  • FIG5B is a schematic diagram of a flow chart of a device registration method according to an embodiment of the present disclosure.
  • FIG6 is an interactive schematic diagram of a device registration method according to an embodiment of the present disclosure.
  • FIG7A is a schematic diagram of the structure of a first device proposed in an embodiment of the present disclosure.
  • FIG7B is a schematic diagram of the structure of a second device provided in an embodiment of the present disclosure.
  • FIG7C is a schematic diagram of the structure of a network device proposed in an embodiment of the present disclosure.
  • FIG8A is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure.
  • FIG8B is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure.
  • the embodiments of the present disclosure provide a device registration method, a first device, a second device, and a network device.
  • an embodiment of the present disclosure provides a device registration method, which is performed by a first device, wherein the first device includes a relay node or an auxiliary node, and the method includes:
  • the first request is sent to the network device.
  • the first request is determined by the first device, and the first request is used to request registration of the second device in the network.
  • the second device communicates with the network device through the first device, the first device assists the second device in the registration process, thereby improving the convenience of registration and effectively dealing with registration problems under complex topology structures.
  • the first request includes at least one of the following parameters:
  • 5GS mobile identity the fifth generation mobile communication technology system
  • the 5GS mobile identity can indicate the unique identity of the second device in the network.
  • the role of the 5GS registration type is to enable the network device to provide targeted registration procedures based on the registration type.
  • the capability of the second device included in the first request can help the first device determine a method to assist the second device in registering. It is also beneficial to determine the transmission method with the second device and improve transmission stability.
  • the capability of the second device includes at least one of the following:
  • Energy storage capability signal generation capability, data processing capability, type of second device, supported protocol stack, supported topology type, supported signal type, fifth generation mobile communication technology mobility management 5GMM capability, network capability of S1 interface, security capability and unique identification ID of radio capability.
  • each capability is helpful to determine a feasible topology structure and a suitable transmission mode of the second device, thereby improving transmission stability.
  • the method before sending the first request to the network device, the method further includes:
  • a second request sent by the second device is received, where the second request instructs the first device to send the first request to a network device.
  • the first device before sending the first request, the first device also receives a second request sent by the second device, and the second request at least causes the first device to send the first request to the network device, so that the first device responds to the second request and triggers the process of sending the first request.
  • the second request includes at least one of the following:
  • 5GS mobile identity the fifth generation mobile communication technology system
  • the parameters in the second request include the parameters in the first request, so that the first device can generate the first request according to the second request when needed, and can also include an auxiliary method, so that the first device can assist the second device to register according to the auxiliary method in the second request.
  • determining the first request includes:
  • the assistance mode is a mode in which the network device assists the second device to register in the network.
  • the first request is determined by at least one of the second request and the auxiliary manner, which improves the flexibility of determining the first request.
  • determining the first request according to at least one of the second request and the auxiliary manner includes:
  • the second request includes the first request, and the first request is obtained from the second request;
  • the second request does not include the first request, and the first request is generated according to the second request;
  • the auxiliary method is the first method, obtaining the first request from the second request;
  • the auxiliary mode is the second mode, generating the first request according to the second request;
  • the first mode is: the second request includes the first request, and the first device sends the first request in the second request to the network device;
  • the second manner is: the second request does not include the first request, and the first device generates and sends the first request on behalf of the second device.
  • the first request can be determined by whether the second request includes the first request, or by whether the auxiliary mode is the first mode or the second mode, which reflects the multi-selectivity of determining the first request of the present disclosure.
  • the assistance mode is determined by the following method:
  • the second request indicates an auxiliary mode
  • the method is determined according to a capability of at least one of the first device and the second device.
  • three methods for determining the auxiliary mode are provided, for example, it can be pre-configured, it can be indicated by the second device in the second request, or it can be determined according to the capabilities of the first device and the second device.
  • the embodiments of the present disclosure do not limit whether the auxiliary mode is determined by the first device or the second device, reflecting the multi-selectivity of the present disclosure in determining the auxiliary mode.
  • the assistance mode is determined according to capabilities of the first device and the second device, and the determining of the first request also includes:
  • the first device determines the capabilities of each other with the second device, so that the first device can determine at least one of the auxiliary mode and the topology type, and the second device can also determine at least one of the auxiliary mode and/or the topology type, which lays a foundation for the subsequent determination of the auxiliary mode.
  • sending the first request to the network device further includes:
  • a first message sent by the network device is received, where the first message is used to indicate that the network accepts registration of a second device.
  • the first device receives a first message sent by a network device, where the first message indicates that the network accepts the registration of the second device, so that the first device knows the registration progress.
  • receiving a first message sent by a network device further includes:
  • a second message is generated according to the first message, and the second message is sent to the second device, where the second message indicates that the network accepts registration of the second device.
  • the first device may directly send the first message to the second device, or modify the first message to generate a second message, such as adding or deleting some parameters, and send the second message to the second device so that the second device can perform related operations of device registration, which reflects the diversity of registration methods.
  • the sending of the first request to the network device further includes:
  • a third message is sent to the network device, where the third message indicates that the second device has completed registration in the network.
  • the third message is sent to the network device so that the network device knows that the second device has completed the device registration, thereby ending the registration process.
  • the method before sending the third message to the network device, the method further includes:
  • the fourth message indicates that the second device has completed registration in the network.
  • the first device after the first device receives the first message, it can directly generate a third message to return to the network device, without the need for the second device to instruct the second device to complete registration in the network, which can improve registration efficiency.
  • the first device can also receive the third message sent by the second device and forward the third message directly to the network device, or generate a third message based on the received fourth message, such as adding or deleting parameters in the fourth message.
  • the embodiment of the present application realizes the diversity of instructing the second device to complete registration in the network.
  • an embodiment of the present disclosure provides a device registration method, which is performed by a second device and includes:
  • the second request instructs the first device to send a first request to a network device, where the first request is used to register the second device in the network;
  • the first device includes at least one of a relay node and an assist node.
  • the second device sends a second request to the first device, and the second request instructs the first device to send a first request to the network device.
  • the first request is used to request to register the second device in the network.
  • the second device communicates with the network device through the first device, the first device assists the second device in the registration process, thereby improving the convenience of registration and effectively dealing with registration problems under complex topology structures.
  • sending the second request to the first device also includes:
  • a second request corresponding to the auxiliary mode is generated.
  • the second device determines the auxiliary mode and generates a second request corresponding to the auxiliary mode, thereby laying a foundation for the first device to determine the first request in a consistent auxiliary mode.
  • the assistance mode is determined by the following method:
  • the method is determined according to a capability of at least one of the first device and the second device.
  • the capability of the second device includes at least one of the following:
  • Energy storage capability Energy storage capability, signal generation capability, data processing capability, type of second device, supported protocol stack, supported topology type, supported signal type, 5GMM capability, network capability of S1 interface, security capability and radio capability ID.
  • the assistance mode is determined according to capabilities of the first device and the second device, and the determining of the assistance mode also includes:
  • the auxiliary mode is a first mode, and the second request corresponding to the first mode includes the first request;
  • the auxiliary mode is a second mode, and a second request corresponding to the second mode includes parameters used to generate the first request;
  • the first mode is: the second request includes the first request, and the first device sends the first request included in the second request to the network device;
  • the second manner is: the second request does not include the first request, and the first device generates and sends the first request on behalf of the second device.
  • sending a second request to the first device further includes:
  • the third message and the fourth message both indicate that the second device has completed registration in the network, and the fourth message is used to generate the third message.
  • sending the third message or the fourth message also includes:
  • the first message and the second message both indicate that the network accepts the registration of the second device, and the second message is generated by the first device according to the first message.
  • sending the second request to the first device includes:
  • the third device includes at least one of the first device, a network device, and a third-party device.
  • the present disclosure provides a device registration method, which is performed by a network device and includes:
  • the first device includes at least one of a relay node and an auxiliary node.
  • receiving a first request sent by a first device further includes:
  • a first message is sent to at least one of the first device and the second device, where the first message is used to indicate that the network accepts registration of the second device.
  • sending a first message to at least one of the first device and the second device further includes:
  • the third message indicates that the second device has completed registration in the network.
  • an embodiment of the present disclosure proposes a device registration method, which is applied to a communication system.
  • the method includes:
  • the second device sends a second request to the first device
  • the first device sends a first request to the network device according to the second request
  • the network device obtains the first request
  • the first device comprises at least one of a relay node and an auxiliary node
  • the first request is used to request registration of the second device in the network
  • the second request is used by the first device to send the first request to the network device.
  • an embodiment of the present disclosure provides a first device, the first device includes at least one of a relay node and an auxiliary node, and the first device includes:
  • a processing module configured to determine a first request, wherein the first request is configured to request registration of a second device in a network
  • a transceiver module is used to send the first request to the network device.
  • the present disclosure provides a second device, including:
  • a transceiver module configured to send a second request to the first device
  • the second request instructs the first device to send a first request to the network device, wherein the first request is used to request Registering a second device in the network;
  • the first device includes at least one of a relay node and an assist node.
  • an embodiment of the present disclosure provides a network device, including:
  • a transceiver module configured to receive a first request sent by a first device, wherein the first request is used to request registration of a second device in a network;
  • the first device includes at least one of a relay node and an auxiliary node.
  • an embodiment of the present disclosure proposes a communication system, which includes: a first device, a second device and a network device; wherein the first device is configured to execute the method described in the optional implementation manner of the first aspect, the second device is configured to execute the method described in the optional implementation manner of the second aspect, and the network device is configured to execute the method described in the optional implementation manner of the third aspect.
  • an embodiment of the present disclosure proposes a storage medium, wherein the storage medium stores instructions.
  • the instructions When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation manner of the first aspect, the second aspect or the third aspect.
  • an embodiment of the present disclosure proposes a program product.
  • the communication device executes the method described in the optional implementation manner of the first aspect, the second aspect or the third aspect.
  • an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first aspect, the second aspect, or the third aspect.
  • an embodiment of the present disclosure provides a chip or a chip system.
  • the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first aspect, the second aspect, or the third aspect.
  • the first device, the second device, the network device, the communication system, the storage medium, the program product, the computer program, the chip or the chip system are all used to execute the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method, which will not be repeated here.
  • the embodiments of the present disclosure provide a device registration method, a first device, a second device, and a network device.
  • the terms device registration method, information processing method, communication method, etc. can be replaced with each other
  • the terms device registration device, information processing device, communication device, etc. can be replaced with each other
  • the terms information processing system, communication system, etc. can be replaced with each other.
  • each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined.
  • a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged.
  • the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined, for example, some or all of the steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
  • elements expressed in the singular form such as “a”, “an”, “the”, “above”, “said”, “aforementioned”, “this”, etc., may mean “one and only one", or “one or more”, “at least one”, etc.
  • the noun after the article may be understood as a singular expression or a plural expression.
  • plurality refers to two or more.
  • the terms "at least one of”, “one or more”, “a plurality of”, “multiple”, etc. can be used interchangeably.
  • "at least one of A and B", “A and/or B", “A in one case, B in another case”, “in response to one case A, in response to another case B”, etc. may include the following technical solutions according to the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). When there are more branches such as A, B, C, etc., the above is also similar.
  • the recording method of "A or B” may include the following technical solutions according to the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed).
  • A A is executed independently of B
  • B B is executed independently of A
  • execution is selected from A and B (A and B are selectively executed).
  • the ordinal number before the "level” in “first level” and “second level” does not limit the priority between the "levels”.
  • the number of description objects is not limited by ordinal numbers and can be one or more. Take “first device” as an example, where the number of "devices" can be one or more.
  • the objects modified by different prefixes can be the same or different.
  • the description object is "device”
  • the “first device” and the “second device” can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information”, the “first information” and the “second information” can be the same information or different information, and their contents can be the same or different.
  • “including A”, “comprising A”, “used to indicate A”, and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
  • time/frequency refers to the time domain and/or the frequency domain.
  • terms such as “greater than”, “greater than or equal to”, “not less than”, “more than”, “more than or equal to”, “not less than”, “higher than”, “higher than or equal to”, “not lower than”, and “above” can be replaced with each other, and terms such as “less than”, “less than or equal to”, “not greater than”, “less than”, “less than or equal to”, “no more than”, “lower than”, “lower than or equal to”, “not higher than”, and “below” can be replaced with each other.
  • devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments.
  • Terms such as “device”, “equipment”, “device”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.
  • network may be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).
  • terminal In some embodiments, the terms "terminal”, “terminal device”, “user equipment (UE)”, “user terminal” “mobile station (MS)”, “mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client and the like can be used interchangeably.
  • the access network device, the core network device, or the network device can be replaced by a terminal.
  • the various embodiments of the present disclosure can also be applied to a structure in which the access network device, the core network device, or the network device and the communication between the terminals is replaced by the communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.).
  • D2D device-to-device
  • V2X vehicle-to-everything
  • it can also be set as a structure in which the terminal has all or part of the functions of the access network device.
  • terms such as "uplink” and "downlink” can also be replaced by terms corresponding to communication between terminals (for example, "side”).
  • uplink channels, downlink channels, etc. can be replaced by side channels
  • uplinks, downlinks, etc. can be replaced by side links.
  • the terminal may be replaced by an access network device, a core network device, or a network device.
  • the access network device, the core network device, or the network device may also be configured to have a structure that has all or part of the functions of the terminal.
  • acquisition of data, information, etc. may comply with the laws and regulations of the country where the data is obtained.
  • data, information, etc. may be obtained with the user's consent.
  • each element, each row, or each column in the table of the embodiments of the present disclosure may be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns may also be implemented as an independent embodiment.
  • FIG1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.
  • a communication system 100 includes a second device 101 , a first device 102 , and a network device 103 .
  • the second device may be an Internet of Things device.
  • the second device may be an ambient IoT device.
  • An ambient IoT device refers to an IoT device that supports ambient power, is powered by energy harvesting, and is either battery-free or has limited energy storage capacity (e.g., using capacitors), providing a promising solution to meet the above unmet needs. It can communicate without a traditional power source, and/or avoid human intervention for charging or replacement. It has the characteristics of low power consumption and low complexity, very small size, and longer life cycle. Ambient IoT devices can be maintenance-free (e.g., no human intervention required) and have a long service life (e.g., more than 10 years).
  • the ambient IoT device uses energy harvested from wireless radio waves or any other form of energy that can be harvested in a particular use case.
  • the ambient IoT device can harvest energy from radio waves, where the radio waves may come from a 5G NR network entity or a user device.
  • the ambient IoT device can harvest energy from energy from solar energy, light, motion/vibration, heat, pressure, or any other power source.
  • the first device 102 may be an auxiliary node or a relay node.
  • the auxiliary node or the relay node may be one or more base stations, terminals, relays, integrated access backhaul (IAB), etc.
  • the network device 103 may include an access network device and a core network device.
  • the access network device is, for example, a node or device that accesses a terminal to a wireless network.
  • the access network device may include an evolved Node B (eNB), a next generation evolved Node B (ng-eNB), a next generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.
  • eNB evolved Node B
  • ng-eNB next generation evolved Node B
  • gNB next generation Node B
  • NB node
  • the technical solution of the present disclosure may be applicable to the Open RAN architecture.
  • the interfaces between access network devices or within access network devices involved in the embodiments of the present disclosure may become internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces may be implemented through software or programs.
  • the access network device may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU), wherein the CU may also be called a control unit (control unit).
  • the CU-DU structure may be used to split the protocol layer of the access network device, with some functions of the protocol layer being centrally controlled by the CU, and the remaining part or all of the functions of the protocol layer being distributed in the DU, and the DU being centrally controlled by the CU, but not limited to this.
  • the core network device may be one device, or may be multiple devices or a group of devices.
  • the core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).
  • EPC Evolved Packet Core
  • 5GCN 5G Core Network
  • NGC Next Generation Core
  • the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure.
  • a person of ordinary skill in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.
  • the following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG. 1A or part of the subject, but are not limited thereto.
  • the subjects shown in FIG. 1A are examples, and the communication system may include all or part of the subjects in FIG. 1A, or may include other subjects other than FIG. 1A, and the number and form of the subjects are arbitrary, and the subjects may be physical or virtual, and the connection relationship between the subjects is an example, and the subjects may be connected or disconnected, and the connection may be in any manner, and may be a direct connection or an indirect connection, and may be a wired connection or a wireless connection.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • SUPER 3G IMT-Advanced
  • 4th generation mobile communication system 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • 5G new radio NR
  • future radio access FX
  • new radio access technology RAT
  • new radio NR
  • new radio access NX
  • future generation radio access FX
  • GSM Global System for Mobile communications
  • GSM registered trademark
  • CDMA2000 Code Division Multiple Access
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi (registered trademark)
  • IEEE 802.16 WiMAX (registered trademark)
  • IEEE 802.20 Ultra-WideBand (UWB), Bluetooth (registered trademark)
  • Public Land Mobile Network PLMN) network
  • D2D Device-to-Device
  • M2M Machine-to-Machine
  • IoT Vehicle-to-Everything
  • connection topologies of the second device In all these topologies, carriers from other nodes inside or outside the topology can be provided to the second device.
  • the links in each topology can be bidirectional or unidirectional.
  • BS, IoT devices, auxiliary nodes or relay nodes can be multiple BS or IoT devices respectively.
  • Such mixed indoor and outdoor deployment of nodes is considered as a choice for network implementation.
  • the potential impact on device or node complexity needs to be considered. In the connection topology, this does not mean that there are multi-hop auxiliary nodes or relay nodes.
  • FIG. 1B exemplarily shows a topology structure provided by an embodiment of the present disclosure.
  • the relay node can be a relay that can realize the Internet of Things, an IAB node, a UE, a repeater, etc.
  • the relay node transmits information between the BS and the second device.
  • FIG. 1C exemplarily shows another topology structure provided by an embodiment of the present disclosure.
  • the second device sends data/signaling to the base station and receives data/signaling from the auxiliary node; or the second device receives data/signaling from the base station and sends data/signaling to the auxiliary node.
  • the auxiliary node can be a relay, IAB, UE, repeater, etc. that can realize the Internet of Things.
  • FIG. 1D exemplarily shows a schematic diagram of a registration management process of a UE in the related art. As shown in the figure, the following steps are included:
  • AMF Access and Mobility Management Function
  • the new AMF network element initiates the UE context transfer service operation Namf_Communication_UE ContextTranfer to the old AMF network element;
  • the old AMF network element sends the UE context transfer service operation response Namf_Communication_UE ContextTranfer response to the new AMF network element;
  • the new AMF network element sends an identity request Identity Request to the UE;
  • the UE sends an Identity Response to the new AMF network element
  • the new AMF network element selects the Authentication Server Function (AUSF) network element
  • the new AMF network element performs security identity authentication
  • the new AMF network element initiates the registration status update operation Namf_Communication_RegistrationStatusUpdate to the old AMF network element;
  • the new AMF network element initiates an identity request or identity response Identity Request/Response to the UE;
  • the new AMF network element initiates identity check N5g-eir EquipmentOdemtityCheck_Get;
  • the new AMF network element calls the Nudm_UECM_Registration service of the UDM network element to register;
  • the new AMF network element calls the Nudm_SDM_Ge service of the UDM network element to retrieve the access and mobile subscription data in the SMF network element data;
  • the new AMF NE After the new AMF NE receives a successful response, it subscribes to the notification using Nudm_SDM_Subscribe when the requested data is modified.
  • the UDM NE can subscribe to the UDR NE using Nudr_DM_Subscribe.
  • the UDM network element initiates the Nudm_UECM_DeregistrationNotification service to the old AMF network element;
  • the old AMF network element will call the Nudm_SDM_unsubscribe service to the UDM network element to cancel the subscription;
  • the new AMF network element selects the PCF network element
  • the new AMF network element executes AM Policy Association Establishment/Modification and will ignore the emergency registration;
  • the new AMF network element calls the Nsmf_PDUSession_UpdateSMContext service/Nsmf_PDUSession_ReleaseSMContext service of the SMF network element;
  • the new AMF network element sends a UE Context modification Request to the N3IWF/TNGF/W-AGF network element;
  • N3IWF/TNGF/W-AGF network element sends UE Context modification Response to the new AMF network element
  • the UDM network element initiates Nudm_UECM_DeregistrationNotify to the old AMF network element, and the old AMF network element removes the non-3GPP UE context;
  • the old AMF network element uses the Nudm_SDM_Unsubscribe service to cancel the subscription
  • the new AMF network element sends a Registration Accept message to the UE;
  • the new AMF network element executes the UE Policy Association Establishment process
  • the UE sends a Registration Complete message to the new AMF network element
  • the AMF network element confirms the UDM network element to the UE using Nudm_SDM_Info;
  • the new AMF network element sends a "same type support for IMS voice over PS session" indication to the UDM network element using Nudm_UECM_Update;
  • FIG2 is an interactive schematic diagram of a device registration method according to an embodiment of the present disclosure. As shown in FIG2 , an embodiment of the present disclosure relates to a device registration method, and the method includes:
  • step S2101 the second device 101 and the first device 102 discover and determine each other's capabilities.
  • signaling between the second device 101 and the first device 102 may be transmitted based on PC5, simplified PC5, or other new interfaces.
  • the capabilities of the second device 101 include at least one of the following:
  • Energy storage capacity that is, the ability to store energy.
  • the second device may or may not have energy storage capacity. When it has energy storage capacity, it may further include the maximum degree of energy storage, power consumption, etc.;
  • Signal generation capability that is, the ability to generate a signal.
  • the signal generation capability may include at least one of the following:
  • Data processing capability that is, the ability to process data, such as the ability to collect environmental data, the ability to generate signals, etc.
  • Type of the second device includes at least one of the following:
  • Type A no energy storage, no independent signal generation/amplification, i.e. backscatter transmission;
  • Type B with energy storage, without independent signal generation, i.e. backscatter transmission, the use of stored energy may include amplification of the reflected signal;
  • Type C with energy storage and independent signal generation, i.e. active RF components for transmission;
  • Supported signal types such as amplitude-shift keying (ASK), on-off keying (OOK), orthogonal frequency division multiplexing (OFDM), etc.
  • 5GS mobility management, 5GMM Fifth generation mobile communication technology mobility management
  • the capabilities of the first device 102 may include auxiliary capabilities (downlink, uplink, or both), supported topologies (such as FIG. 1B or FIG. 1C ), and supported auxiliary modes.
  • the assistance capabilities are determined based on the topology type.
  • the assistance mode refers to a mode in which the first device assists the second device to register in the network.
  • the assistance method refers to a method in which the first device assists the second device in performing a registration management process in the network.
  • the types of auxiliary methods include a first method, in which the first device only transparently forwards (also referred to as transparent transmission) the first request of the second device (without modifying the information contained in the request), and other parameters may also be added, such as the first The type and ID of the device are forwarded to the network device 103.
  • the first mode is: the second request includes the first request, and the first device forwards the first request in the second request to the network device.
  • the type of auxiliary mode includes a second mode, in which the first device generates and sends the first request on behalf of the second device. That is, in the second mode, part or all of the capabilities of the first device itself are combined with the capabilities of the second device as a whole and sent to the network device.
  • the second mode is: the second request does not include the first request, and the first device generates and sends the first request on behalf of the IoT device.
  • the first device 102 or the second device 101 determines a topology type and/or an assistance method.
  • the second device 101 or the first device 102 determines the topology type and/or the assistance method according to the capability of at least one of the first device 102 and the second device 101 .
  • the second device 101 or the first device 102 determines the topology type and/or the assistance method according to common capabilities of the first device 102 and the second device 101 .
  • the second device 101 After the second device 101 determines the topology type and/or the assistance mode, it notifies the first device 102 .
  • the first device 102 After the first device 102 determines the topology type and/or the assistance mode, it sends a message to the surrounding second devices 101 to notify the topology type and/or the assistance mode.
  • step S2101 may be skipped.
  • the names of information, etc. are not limited to the names recorded in the embodiments, and terms such as “information”, “message”, “signal”, “signaling”, “report”, “configuration”, “indication”, “instruction”, “command”, “channel”, “parameter”, “domain”, “field”, “symbol”, “symbol”, “code element”, “codebook”, “codeword”, “codepoint”, “bit”, “data”, “program”, and “chip” can be used interchangeably.
  • Step S2102 the second device 101 sends a second request to the first device 102 .
  • the first device 102 receives the second request.
  • the second request is used to request the first device 102 to assist the second device 101 in performing a registration process in the network.
  • the second request is used to instruct the first device 102 to send the first request to the network device 103 .
  • the name of the second request is not limited, and it may be, for example, a "registration assistance request".
  • the parameters in the second request include at least one of a 5GS mobile identity, a 5GS registration type, a 5GMM capability, a network capability of an S1 interface, a security capability, a radio capability ID, a preferred network behavior, and an auxiliary mode.
  • the 5GS mobile identity provides at least one of a subscription concealed identifier (SUCI) of the second device, a 5G-globally unique temporary UE identity (GUTI), an international mobile equipment identity (IMEI), an IMEI software version (IMEI Software Version, IMEISV), a 5G S-Temporary Mobile Subscription Identifier, 5G-S-TMSI, a media access control address (MAC) address, or a 64-bit extended unique identifier (EUI-64).
  • SUCI subscription concealed identifier
  • GUI 5G-globally unique temporary UE identity
  • IMEI international mobile equipment identity
  • IMEI software version IMEI Software Version
  • MAC media access control address
  • EUI-64 64-bit extended unique identifier
  • the second request may or may not include the first request.
  • the second device sends a second request including the first request according to the auxiliary mode being the first mode, and does not send the first request according to the auxiliary mode being the second mode.
  • the parameters in the first request include at least one of a 5GS mobile identity, a 5GS registration type, a 5GMM capability, a network capability of an S1 interface, a security capability, a radio capability ID, and a preferred network behavior.
  • the second device 101 before the second device 101 sends the second request, it may be triggered by a third device.
  • the third device may be the first device, a network device, a third-party device, or the like.
  • the triggering means that the second device receives a signal sent by the third device, thereby sending the second request according to the energy of the signal.
  • Step S2103 the first device 102 determines the first request.
  • the first device receives the second request.
  • the first device determines the first request based on at least one of the auxiliary manner and the second request.
  • the first device obtains the first request from the second request based on the first request being included in the second request.
  • the first device generates the first request according to the parameters in the second request based on the fact that the first request is not included in the second request.
  • the parameters included in the second request include at least one of the 5GS mobile identity, 5GS registration type, 5GMM capability, network capability of the S1 interface, security capability, radio capability ID, preferred network behavior, and auxiliary mode, and the 5GS At least one of the mobile identity, 5GS registration type, 5GMM capability, network capability of the S1 interface, security capability, radio capability ID, and preferred network behavior is encapsulated to generate a first request.
  • the first device obtains the first request from the second request in a first manner according to the auxiliary manner.
  • the first device generates the first request according to the second request in a second manner according to the auxiliary manner.
  • the auxiliary mode of the embodiment of the present disclosure is synchronized with the first device and the second device. Therefore, when the first device determines that the auxiliary mode is the first mode, the second device will include the first request in the second request, so that the first device can directly obtain the first request from the second request. When the first device determines that the auxiliary mode is the second mode, the second request sent by the second device includes parameters for generating the first request, so that the first device generates the first request according to the parameters for generating the first request in the second request.
  • the assistance mode is determined by any of the following methods:
  • the auxiliary mode may be configured on the first device and the second device before step S2102;
  • the first device can determine the assistance mode according to the capabilities of each other and inform the second device after determining the assistance mode, or the second device can determine the assistance mode according to the capabilities of each other and inform the first device of the assistance mode.
  • Step S2104 the first device 102 sends a first request to the network device 103 .
  • the first device 102 sends a first request to an access network device in the network device 103 .
  • the first device 102 sends a fifth message to the network device 103 .
  • the fifth message includes the first request.
  • the fifth message includes access network parameters and the first request.
  • Step S2105 the network device 103 registers the second device in the network.
  • the registration process of the second device 101 may be performed with reference to steps 2-19 in FIG. 1D .
  • the second device 101 is registered in the network.
  • Step S2106 the network device 103 sends a first message.
  • the first message is sent by a core network device.
  • the first message is used to indicate that the network accepts registration of the second device.
  • the parameters in the first message are applicable to the second device.
  • the name of the first message is not limited, and it may be, for example, a "registration acceptance message".
  • the network device 103 sends a first message to the first device 102 .
  • the first device 102 receives the first message and sends the first message to the second device 101 .
  • the first device 102 receives the first message, generates a second message based on the first message, and sends the second message to the second device, where the second message indicates that the network accepts registration of the second device.
  • the name of the second message is not limited, and it is, for example, "Registration Assistance Response”.
  • the second message includes at least one of a registration result, a 5G-GUTI, and a registration area.
  • the first device 102 stores information of the second device 101 .
  • the network device 103 sends a first message to the second device 101 .
  • Step S2107 the first device 102 sends a third message.
  • the third message is used to indicate that the second device has completed registration in the network.
  • the name of the third message is not limited, for example, it can be a "registration completion message".
  • the first device 102 receives the first message, generates a third message, and sends the third message to the network device 103 .
  • the second device 101 receives the first message or the second message, generates a third message, sends the third message to the first device 102, and the first device 102 sends the third message to the network device.
  • the second device 101 receives the first message or the second message, generates a fourth message, sends the fourth message to the first device 102, the first device 102 generates a third message based on the fourth message, and the first device 102 sends the third message to the network device.
  • the fourth message is used to indicate that the second device has completed registration in the network.
  • the fourth message is used to indicate the assistance is complete.
  • the name of the fourth message is not limited, for example, it can be a "registration assistance completion message".
  • the second device 101 receives the first message or the second message, generates a third message, and the second device 101 sends the third message to the network device 103 .
  • the registration process of the second device 101 can be performed with reference to steps 23-25 in FIG. 1D .
  • the second device 101 may be registered in the network with reference to steps 23-25 of FIG. 1D.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S2101 to S2107.
  • step S2101 may be implemented as an independent embodiment
  • step S2102 may be implemented as an independent embodiment
  • steps S2103 to S2105 may be implemented as independent embodiments
  • steps S2106 to S2107 may be implemented as independent embodiments.
  • steps S2101, S2102, and S2106-S2107 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • FIG3A is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to a first device, and the method includes:
  • Step S3101 determine the capability of the second device.
  • step S3101 can refer to the optional implementation of step S2101 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • the first device 102 receives a message sent by the second device 101, in which the capabilities of the second device are indicated, but not limited thereto, and the capabilities of the second device sent by other entities may also be received.
  • the first device 102 obtains the capabilities of the second device as specified by the protocol.
  • the first device 102 obtains the capability of the second device from an upper layer(s).
  • the upper layer(s) may include an application layer.
  • the first device 102 performs processing to determine the capabilities of the second device.
  • step S3101 is omitted, and the first device 102 autonomously determines the capabilities of the second device.
  • Step S3102 receiving a second request.
  • step S3102 can refer to the optional implementation of step S2102 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • the second device 101 sends a second request to the first device 102 .
  • the second request is used to request the first device 102 to assist the second device 101 in performing a registration process.
  • the second request is used to instruct the first device 102 to send the first request to the network device 103 .
  • Step S3103 determine the first request.
  • step S3103 can refer to the optional implementation of step S2103 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • the second request includes the first request, and the first device obtains the first request from the second request.
  • the second request does not include the first request
  • the first device generates the first request according to the parameters in the second request.
  • Step S3104 sending a first request.
  • step S3104 can refer to the optional implementation of step S2104 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • the first device 102 sends a first request to the network device 103 .
  • the first device 102 sends a fifth message to the network device 103.
  • the fifth message includes the first request and access network parameters.
  • Step S3105 receiving the first message.
  • step S3105 can refer to the optional implementation of step S2106 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • the first device 102 receives a first message from the network device 103 .
  • the first device 102 sends a first message to the second device 101 .
  • Step S3106 Send at least one of the second message and the third message.
  • step S3106 can refer to the optional implementation of steps S2106 and S2107 in Figure 2, and other related parts in the embodiment involved in Figure 2, which will not be repeated here.
  • the first device 102 obtains the third message from the second device 101 and sends the third message to the network device 103 .
  • the first device 102 generates a third message based on receiving the first message, and sends the third message to the network device 103 .
  • the first device 102 receives the fourth message obtained by the second device 101, generates a third message according to the fourth message, The third message is sent to the network device 103. In some embodiments, the first device 102 further sends a second message to the second device 101, and the second device can determine that the registration is completed according to the receipt of the second message.
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S3101 to S3106.
  • step S3102 may be implemented as an independent embodiment
  • S3103 may be implemented as an independent embodiment
  • steps S3102+S3103+S3104 may be implemented as independent embodiments, but are not limited thereto.
  • steps S3101, S3105, and S3106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • steps S3101-S3103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • FIG3B is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a first device, and the method includes:
  • Step S3201 receiving a second request.
  • step S3201 can refer to the optional implementation of step S2102 in Figure 2, step S3102 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.
  • Step S3202 determine the first request.
  • step S3202 can refer to the optional implementation of step S2103 in Figure 2, step S3103 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.
  • Step S3203 sending the first request.
  • step S3203 can refer to the optional implementation of step S2104 in Figure 2, step S3104 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.
  • Step S3204 determine the third message.
  • step S3204 can refer to the optional implementation of step S2107 in Figure 2, the optional implementation of step S3106 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.
  • the first device 102 receives a third message sent by the second device 101 .
  • the first device 102 receives a fourth message sent by the second device 101, and generates a third message according to the fourth message.
  • the network device after the first device 102 sends the first request to the network device 103, the network device sends a first message to the second device 101, and the second device 101 sends a third message or a fourth message to the first device 102 based on the first message.
  • Step S3205 sending the third message.
  • the first device 102 sends a third message to the network device 103 .
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S3201 to S3205.
  • step S3203 may be implemented as an independent embodiment
  • S3201 may be implemented as an independent embodiment
  • steps S3201+S3202+S3203 may be implemented as independent embodiments, but are not limited thereto.
  • S3204 is optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • steps S3201-S3204 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • step S3201 may be combined with step S3102 of FIG. 3a
  • step S3202 may be combined with step S3104 of FIG. 3a
  • step S3203 may be combined with step S3105 of FIG. 3a .
  • FIG3C is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG3C , the present disclosure embodiment relates to a device registration method, and the method includes:
  • Step S3301 assist the second device to register in the network.
  • step S3301 includes: sending a first request to the network device 103.
  • the optional implementation method of sending the first request to the network device 103 can be seen in step S2103 and step S2104 of Figure 2, step S3103 and step S3104 of Figure 3A, the optional implementation method of step S3201 and step S3203 of Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.
  • step S3301 also includes: forwarding the first message to the second device.
  • the optional implementation method of forwarding the first message to the second device can be seen in step S2106, step S2104 of Figure 2, step S3105 of Figure 3A, and other related parts of the embodiments involved in Figures 2 and 3A, which will not be repeated here.
  • step S3301 further includes: sending a third message to the network device.
  • step S3301 further includes: sending a third message to the network device.
  • the device registration method involved in the embodiment of the present disclosure may include step S3301.
  • step S3301 may be combined with step S3101 of FIG. 3A .
  • FIG3D is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG3D , the embodiment of the present disclosure relates to a device registration method, and the method includes:
  • Step S3401 Determine a first request, where the first request is used to request registration of a second device in a network;
  • Step S3402 Send the first request to the network device.
  • the first request includes at least one of the following:
  • 5GS mobile identity the fifth generation mobile communication technology system
  • the capability of the second device includes at least one of the following:
  • Energy storage capability Energy storage capability, signal generation capability, data processing capability, type of second device, supported protocol stack, supported topology type, supported signal type, 5GMM capability, network capability of S1 interface, security capability and radio capability unique identification ID.
  • the step before sending the first request to the network device, the step further includes:
  • a second request sent by the second device is received, where the second request instructs the first device to send the first request to a network device.
  • the second request includes at least one of the following:
  • 5GS mobile identity the fifth generation mobile communication technology system
  • determining the first request includes:
  • the first request is determined according to at least one of the second request and an auxiliary manner.
  • determining the first request according to at least one of the second request and the auxiliary manner includes:
  • the second request includes the first request, and the first request is obtained from the second request;
  • the second request does not include the first request, and the first request is generated according to the second request;
  • the auxiliary method is the first method, obtaining the first request from the second request;
  • the auxiliary mode is the second mode, generating the first request according to the second request;
  • the first mode is: the second request includes the first request, and the first device sends the first request in the second request to the network device;
  • the second manner is: the second request does not include the first request, and the first device generates and sends the first request on behalf of the second device.
  • the auxiliary mode is determined by the following method:
  • the second request indicates an auxiliary mode
  • the method is determined according to the capabilities of the first device and the second device.
  • the assistance mode is determined according to capabilities of the first device and the second device, and before determining the first request, the method further includes:
  • the sending the first request to the network device further includes:
  • a first message sent by the network device is received, where the first message indicates that the network accepts registration of a second device.
  • the receiving a first message sent by the network device further includes:
  • a second message is generated according to the first message, and the second message is sent to the second device, where the second message indicates that the network accepts registration of the second device.
  • the sending the first request to the network device further includes:
  • a third message is sent to the network device, where the third message indicates that the second device has completed registration in the network.
  • the method before sending the third message to the network device, the method further includes:
  • the fourth message indicates that the second device has completed registration in the network.
  • FIG4A is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG4A , the present disclosure embodiment relates to a second device, and the method includes:
  • Step S4101 determining the capability of the first device 102.
  • step S4101 can refer to the optional implementation of step S2101 in Figure 2, step S3101 in Figure 3A, step S3201 in Figure 3B and other related parts in the embodiments involved in Figures 2, 3A and 3B, which will not be repeated here.
  • the capability of the first device is used by the second device to determine the topology type and/or the auxiliary mode.
  • the optional implementation method thereof can refer to the optional implementation method of step S2102 of FIG. 2 and other related parts of the embodiment involved in FIG. 2, which will not be repeated here.
  • Step S4102 sending a second request.
  • step S4102 can refer to the optional implementation of step S2102 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • the second device 101 sends a second request to the first device 102 .
  • the second request is used to request the first device 102 to assist the second device 101 in registering in the network.
  • the second request is used to instruct the first device 102 to send the first request to the network device 103 .
  • the second request includes the first request.
  • the second request includes parameters used to generate the first request.
  • the second request includes at least one of a 5GS mobile identity, a 5GS registration type, capabilities of the second device, a preferred network behavior, and an assistance method.
  • whether the second request includes the first request is determined by the second device according to the determined assistance mode and/or topology type.
  • Step S4103 obtain the first message.
  • step S4103 can refer to the optional implementation of step S2106 in Figure 2, step S3105 in Figure 3A, and other related parts of the embodiments involved in Figure 2 and Figure 3A, which will not be repeated here.
  • the second device receives the first message sent by the first device.
  • the second device receives a first message sent by the network device.
  • Step S4104 sending the third message or the fourth message.
  • step S4104 can refer to the optional implementation of step S2106 in Figure 2, step S3106 in Figure 3A, and other related parts of the embodiments involved in Figure 2 and Figure 3A, which will not be repeated here.
  • the second device 101 sends a third message to the first device 102 , and the first device 102 forwards the third message to the network device 103 .
  • the second device 101 sends a third message to the network device 103 .
  • the second device 101 sends a fourth message to the first device 102 , the first device 102 generates a third message based on the fourth message, and sends the third message to the network device 103 .
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S4101 to S4104.
  • step S4103 may be implemented as an independent embodiment
  • S4105 may be implemented as an independent embodiment
  • steps S4101+S4102+S4103 may be implemented as independent embodiments, but are not limited thereto.
  • steps S4101 and S4102 may be executed in an interchangeable order or simultaneously.
  • steps S4101, S4102, and S4105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • steps S4101-S4104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • FIG4B is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to a second device, and the method includes:
  • Step S4201 sending a second request.
  • step S4201 can refer to the optional implementation of step S2103 in Figure 2, step S4102 in Figure 4A and other related parts in the embodiments involved in Figures 2, 3A, 3B and 4A, which will not be repeated here.
  • the second device 101 sends a second request to the first device 102 .
  • Step S4202 receiving the second message.
  • step S4202 can refer to the optional implementation of step S2106 in Figure 2, step S3106 in Figure 3A and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.
  • the second device 101 receives the second message sent by the first device 102 .
  • step S4201 may be implemented as an independent embodiment
  • step S4202 may be implemented as an independent embodiment, but is not limited thereto.
  • steps S4201 and S4202 may be performed in an interchangeable order or simultaneously.
  • FIG4C is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG4C , the embodiment of the present disclosure relates to a second device, and the method includes:
  • Step S4301 Send a second request to the first device.
  • the second request instructs the first device to send a first request to a network device, where the first request is used to request to register the second device in the network.
  • the first device includes at least one of a relay node and an assist node.
  • sending the second request to the first device also includes:
  • a second request corresponding to the auxiliary mode is generated.
  • the auxiliary mode is determined by the following method:
  • the method is determined according to the capabilities of the first device and the second device.
  • the capability of the second device includes at least one of the following:
  • Energy storage capability Energy storage capability, signal generation capability, data processing capability, type of second device, supported protocol stack, supported topology type, supported signal type, 5GMM capability, network capability of S1 interface, security capability and radio capability ID.
  • the auxiliary mode is determined according to the capabilities of the first device and the second device, and before determining the auxiliary mode, the auxiliary mode also includes:
  • the auxiliary mode is the first mode, and the second request corresponding to the first mode includes the first request;
  • the auxiliary mode is a second mode, and a second request corresponding to the second mode includes parameters used to generate the first request;
  • the first mode is: the second request includes the first request, and the first device sends the first request included in the second request to the network device;
  • the second manner is: the second request does not include the first request, and the first device generates and sends the first request on behalf of the second device.
  • the sending the second request to the first device further includes:
  • the third message and the fourth message both indicate that the second device has completed registration in the network, and the fourth message is used to generate the third message.
  • sending the third message or the fourth message also includes:
  • the first message and the second message both indicate that the network accepts the registration of the second device, and the second message is generated by the first device according to the first message.
  • sending the second request to the first device includes:
  • the third device includes at least one of the first device, a network device, and a third-party device.
  • FIG5A is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG5A , the present disclosure embodiment relates to a network device 103, and the method includes:
  • Step S5101 obtain the first request.
  • step S5101 can refer to the optional implementation of step S2104 in Figure 2, step S3104 in Figure 3A, step S3203 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.
  • the network device 103 receives a first request sent by the first device 102 .
  • Step S5102 registering the second device in the network.
  • step S5102 can refer to the optional implementation of step S2105 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • Step S5103 sending the first message.
  • step S5103 can refer to the optional implementation of step S2106 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
  • the network device 103 sends a first message to the second device 101 .
  • the network device 103 sends a first message to the first device 102 , and the first device 102 forwards the first message to the second device 101 .
  • the network device 103 sends a first message to the first device 102 , and the first device 102 generates a second message based on the first message and sends the second message to the first device 102 .
  • Step S5104 obtain the third message.
  • step S5104 can refer to the optional implementation of step S2106 in Figure 2, step S3106 in Figure 3A, step S3204 in Figure 3B and other related parts in the embodiments involved in Figures 2, 3A and 3B, which will not be repeated here.
  • the network device 103 receives a third message sent by the second device 101 .
  • the network device 103 receives the third message sent by the first device 102 .
  • the communication method involved in the embodiment of the present disclosure may include at least one of steps S5101 to S5104.
  • step S5101 may be implemented as an independent embodiment
  • S5102 may be implemented as an independent embodiment
  • steps S5103+S5104 may be implemented as independent embodiments, but are not limited thereto.
  • steps S5103 and S5104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
  • FIG5B is a flow chart of a device registration method according to an embodiment of the present disclosure. As shown in FIG5B , the present disclosure embodiment relates to a network device 103, and the method includes:
  • Step S5201 Receive a first request sent by a first device, where the first request is used to request registration of a second device in a network;
  • the first device includes at least one of a relay node and an auxiliary node.
  • receiving a first request sent by a first device and then further comprising:
  • a first message is sent to at least one of the first device and the second device, where the first message is used to indicate that the network accepts registration of the second device.
  • the sending a first message to at least one of the first device and the second device further includes:
  • the third message indicates that the second device has completed registration in the network.
  • FIG6 is an interactive schematic diagram of a device registration method according to an embodiment of the present disclosure. As shown in FIG6 , an embodiment of the present disclosure relates to a device registration method, and the method includes:
  • Step S6101 The first device and the second device discover and determine each other's capabilities.
  • step S6101 can refer to the optional implementation method of step S2101 in Figure 2, step S3101 in Figure 3A, step S3201 in Figure 3B, step S4101 in Figure 4A, step S4201 in Figure 4B, and other related parts in the embodiments involved in Figures 2, 3A, 3B, 4A, and 4B, which will not be repeated here.
  • step S6101 can be skipped.
  • the capabilities of the first device may include assistance capabilities (downlink, uplink, or both), supported topology types, and supported assistance methods.
  • the capabilities of the second device include energy storage capability, signal generation capability, data processing capability, environmental second device type, supported protocol stack, supported topology type, supported signal type, 5GMM capability, S1UE network capability, UE security capability, UE radio ID, etc.
  • the assistance method is used to indicate how the first device assists the second device in performing the registration process.
  • the first device transparently forwards the second request received from the IoT device (without modifying the information contained in the request), and may add other parameters and pack them into the message and forward it to the (R)AN.
  • the first device In the second mode, the first device generates the first request on behalf of the second device. If the second request is received from the IoT device, some or all of the capabilities of the first node may be combined with the capabilities of the IoT device and can be considered as a whole and sent to the (R)AN.
  • Step S6102 The first device or the second device determines a topology type and/or an assistance mode according to capabilities of the first device and the second device.
  • step S6102 can refer to the optional implementation method of step S2102 in Figure 2, step S3102 in Figure 3A, step S3202 in Figure 3B, step S4102 in Figure 4A, step S4202 in Figure 4B, and other related parts in the embodiments involved in Figures 2, 3A, 3B, 4A, and 4B, which will not be repeated here.
  • the first device or the second device may determine the topology type and/or the assistance method according to the capabilities of the first device and the second device.
  • the first device sends a message to the surrounding second devices to notify the determined topology type and assistance method.
  • step S6102 can be skipped.
  • Step S6103 The second device sends a second request to the first device.
  • step S6103 can refer to the optional implementation methods of step S2102 in Figure 2, step S3102 in Figure 3A, step S3201 in Figure 3B, step S4102 in Figure 4A, step S4201 in Figure 4B, and other related parts in the embodiments involved in Figures 2, 3A, 3B, 4A, and 4B, which will not be repeated here.
  • the second request includes at least one of a 5GS mobile identity, a 5GS registration type, a 5GMM capability, an S1UE network capability, a UE security capability, a UE radio capability ID, a preferred network behavior, and an auxiliary method.
  • the second device before the second device sends the second request, it may be triggered by the second device, such as the first device, the access network device, etc.
  • the second request includes the first request
  • the first request includes at least one of a 5GS mobile identity, a 5GS registration type, a 5GMM capability, an S1UE network capability, a UE security capability, and a UE radio capability ID.
  • the second request does not include the first request.
  • the 5GS Mobile Identity provides the SUCI, 5G-GUTI, IMEI, IMEISV, 5G-S-TMSI, MAC address, or EUI-64 of the second device.
  • the 5GS Registration Type indicates the type of registration requested.
  • the auxiliary mode is an auxiliary mode requested by the second device. If determined in step S6102, the second request may not include the auxiliary mode.
  • Step S6104 The first device sends a first request to the network device.
  • step S6104 can refer to steps S2103 and S2104 in Figure 2, steps S3103 and S3104 in Figure 3A, steps S3202 and S3204 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.
  • the second device sends an access network message to the network device, wherein the access network message includes the first request and the access network parameter.
  • the first device directly sends the first request to the network device.
  • the first device if the second request does not include the first request, or the auxiliary mode is the second mode, the first device generates the first request according to the parameters in the second request.
  • Step S6105 the network device registers the second device 101 in the network.
  • step S6105 can refer to step S2106 in FIG. 2 , step S5102 in FIG. 5A , and other related parts in the embodiments involved in FIG. 2 and FIG. 5A , which will not be described in detail here.
  • steps 2-19 of the registration process are performed, for example based on Figure 1d.
  • Step S6106a1 The network device sends a first message to the first device.
  • step S6106a1 can refer to step S2106 in Figure 2, step S3102 in Figure 3A, step S3102 in Figure 3B, and step S5102 in Figure 5A and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 5A, which will not be repeated here.
  • the core network device sends a first message to a first device defined in step 21 of clause 4.2.2.2.2-1 of 3GPP TS 23.502.
  • Step S6106a2 The first device sends a second message to the second device.
  • step S6106a2 can refer to step S2106 in Figure 2, step S3105 in Figure 3A, step S3102 in Figure 3B, and step S5102 in Figure 5A and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 5A, which will not be repeated here.
  • the second message includes at least one of a registration result, a 5G-GUTI, and a registration area.
  • Step S6106b The network device sends a first message to the second device.
  • step S6106b can refer to step S2106 in Figure 2, step S4103 in Figure 4A, step S5102 in Figure 5A and other related parts in the embodiments involved in Figures 2, 4A and 5A, which will not be repeated here.
  • Step S6106c The network device sends a first message to the first device.
  • step S6105c can refer to step S2106 in Figure 2, step S3105 in Figure 3A, step S5102 in Figure 5A and other related parts in the embodiments involved in Figures 2, 3A and 5A, which will not be repeated here.
  • the core network sends a first message to a first device defined in step 21 of clause 4.2.2.2.2-1 of 3GPP TS 23.502. Parameters included in the first message are applicable to the second device.
  • the first device stores the information of the second device without sending the first message to the second device.
  • Step S6107a1 the second device sends a fourth message to the first device.
  • step S6107a1 may refer to step S2106 in FIG. 2 , step S3105 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.
  • Step S6107a2 The first device sends a third message to the network device.
  • step S6107a2 may refer to step S2106 in FIG. 2 , step S3106 in FIG. 3A , S5103 in FIG. 5A , and other related parts in the embodiments involved in FIG. 2 , FIG. 3A , and FIG. 5A , which will not be described in detail here.
  • Step S6107b The second device sends a third message to the network device.
  • step S6107b may refer to step S2106 in FIG. 2 , step S4104 in FIG. 4A , step S5103 in FIG. 5A and other related parts in the embodiments involved in FIG. 2 , FIG. 4A and FIG. 5A , which will not be described in detail here.
  • Step S6107c the first device sends a third message to the network device
  • step S6107c may refer to step S2106 in FIG. 2 , step S3106 in FIG. 3A , step S5103 in FIG. 5A , and other related parts in the embodiments involved in FIG. 2 , FIG. 3A , FIG. 3B , and FIG. 5A , which will not be described in detail here.
  • Step S6108 registering the second device in the network, referring to steps 23-25 in FIG. 1D;
  • Step S6109 after executing step S6106c or S6107c, the first device sends a second message to the second device.
  • step S6109 may refer to step S2106 of FIG. 2 , step S3106 of FIG. 3A , and other related parts of the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.
  • step S6106a the second device may execute step S6107a or S6107b, and if step S6106b is executed, the second device may execute step S6107a or S6107b. If step S6106c is executed, the first device may execute step S6107c and step S6109.
  • the embodiments of the present disclosure also propose a device for implementing any of the above methods, for example, a device is proposed, the above device includes a unit or module for implementing each step performed by the terminal in any of the above methods.
  • a device is also proposed, including a unit or module for implementing each step performed by a network device (such as an access network device, a core network function node, a core network device, etc.) in any of the above methods.
  • a network device such as an access network device, a core network function node, a core network device, etc.
  • the division of the units or modules in the above device is only a division of logical functions, and in actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated.
  • the units or modules in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory.
  • the processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory inside the device or a memory outside the device.
  • CPU central processing unit
  • microprocessor a microprocessor
  • the units or modules in the device may be implemented in the form of hardware circuits, and the functions of some or all of the units or modules may be realized by designing the hardware circuits.
  • the hardware circuits may be understood as one or more processors.
  • the hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units or modules are realized by designing the logical relationship of the components within the circuit.
  • the hardware circuit may be implemented by a programmable logic device (PLD).
  • PLD programmable logic device
  • FPGA field programmable gate array
  • it may include a large number of logic gate circuits, and the connection relationship between the logic gate circuits may be configured by a configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices may be implemented entirely by the processor calling software, or entirely by hardware circuits, or partially by The processor calls the software, and the rest is implemented in the form of hardware circuits.
  • the processor is a circuit with signal processing capability.
  • the processor may be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which may be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the above hardware circuit may be fixed or reconfigurable, such as a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the process of the processor loading a configuration document to implement the hardware circuit configuration may be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules.
  • it can also be a hardware circuit designed for artificial intelligence, which can be understood as ASIC, such as Neural Network Processing Unit (NPU), Tensor Processing Unit (TPU), Deep Learning Processing Unit (DPU), etc.
  • ASIC Neural Network Processing Unit
  • NPU Neural Network Processing Unit
  • TPU Tensor Processing Unit
  • DPU Deep Learning Processing Unit
  • the first device 7100 is a schematic diagram of the structure of the first device proposed in an embodiment of the present disclosure.
  • the first device includes a relay node or an auxiliary node.
  • the first device 7100 may include: at least one of a processing module 7101, a transceiver module 7102, etc.
  • the processing module is used to determine a first request, and the first request is used to request registration of a second device in a network; the transceiver module is used to send the first request to the network device.
  • the transceiver module is used to execute the communication steps such as sending and/or receiving performed by the first device 102 in any of the above methods, such as step S2101 and step S2105, which are not repeated here.
  • the processing module is used to execute other steps performed by the first device 102 in any of the above methods, such as at least one of step S2104, which are not repeated here.
  • FIG7B is a schematic diagram of the structure of the second device proposed in the embodiment of the present disclosure.
  • the second device 7200 may include: a transceiver module 7201.
  • the transceiver module is used to send a second request to the first device; the second request instructs the first device to send a first request to the network device, and the first request is used to request to register the second device in the network; the first device includes a relay node or an auxiliary node.
  • the above-mentioned transceiver module is used to execute the communication steps such as sending and/or receiving performed by the second device 101 in any of the above methods, such as step S2101 and step S2103, which will not be repeated here.
  • FIG. 7C is a structural diagram of the network device proposed in an embodiment of the present disclosure.
  • the network device 7300 may include a transceiver module 7301.
  • the transceiver module receives a first request sent by a first device, and the first request is used to register a second device in the network; optionally, the above-mentioned transceiver module is used to execute the communication steps such as sending and/or receiving performed by the network device 103 in any of the above methods, such as step S2107 and step S2108, which are not repeated here.
  • the transceiver module may include a transceiver module and/or a transceiver module, and the transceiver module and the transceiver module may be separate or integrated.
  • the transceiver module may be interchangeable with the transceiver.
  • the processing module can be a module or include multiple submodules.
  • the multiple submodules respectively execute all or part of the steps required to be executed by the processing module.
  • the processing module can be replaced with the processor.
  • FIG8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure.
  • the communication device 8100 may be a network device (e.g., an access network device, a core network device, etc.), or a second device, or a first device, or a chip, a chip system, or a processor that supports the network device to implement any of the above methods, or a chip, a chip system, or a processor that supports the second device to implement any of the above methods.
  • the communication device 8100 may be used to implement the method described in the above method embodiment, and the details may refer to the description in the above method embodiment.
  • the communication device 8100 includes one or more processors 8101.
  • the processor 8101 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit.
  • the baseband processor may be used to process the communication protocol and the communication data
  • the central processing unit may be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute the program, and process the data of the program.
  • the communication device 8100 is used to execute any of the above methods.
  • one or more processors 8101 are used to call instructions so that the communication device 8100 executes any of the above methods.
  • the communication device 8100 further includes one or more transceivers 8102.
  • the transceiver 8102 performs at least one of the communication steps such as sending and/or receiving in the above method (for example, step S2101, step S2103, step S2105, step S2107, step S2108, but not limited thereto), and the processor 8101 performs at least one of the other steps (for example, step S2102, step S2104, step S2106, but not limited thereto).
  • the transceiver may include a receiver and/or a transmitter, and the receiver and the transmitter may be separated or integrated together.
  • transceiver transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc.
  • transmitter transmitting unit, transmitter, transmitting circuit, etc.
  • receiver receiving unit, receiver, receiving circuit, etc.
  • the communication device 8100 also includes one or more memories 8103 for storing data.
  • the memory 8103 or part of the memory 8103 may also be outside the communication device 8100.
  • the communication device 8100 may include one or more interface circuits 8104.
  • the interface circuit 8104 is connected to the memory 8102, and the interface circuit 8104 may be used to receive data from the memory 8102 or other devices, and may be used to send data to the memory 8102 or other devices.
  • the interface circuit 8104 may read the data stored in the memory 8102 and send the data to the processor 8101.
  • the communication device 8100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8A.
  • the communication device may be an independent device or may be part of a larger device.
  • the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.
  • FIG. 8B is a schematic diagram of the structure of a chip 8200 provided in an embodiment of the present disclosure.
  • the communication device 8100 may be a chip or a chip system
  • the chip 8200 includes one or more processors 8201.
  • the chip 8200 is configured to execute any of the above methods.
  • the chip 8200 further includes one or more interface circuits 8202.
  • the terms interface circuit, interface, transceiver pin, etc. can be interchangeable.
  • the chip 8200 further includes one or more memories 8203 for storing data.
  • all or part of the memory 8203 can be outside the chip 8200.
  • the interface circuit 8202 is connected to the memory 8203, and the interface circuit 8202 can be used to receive data from the memory 8203 or other devices, and the interface circuit 8202 can be used to send data to the memory 8203 or other devices.
  • the interface circuit 8202 can read the data stored in the memory 8203 and send the data to the processor 8201.
  • the interface circuit 8202 performs at least one of the communication steps such as sending and/or receiving in the above method (for example, step S2101, step S2103, step S2105, step S2107, step S2108, but not limited thereto).
  • the interface circuit 8202 performs the communication steps such as sending and/or receiving in the above method, for example, means that the interface circuit 8202 performs data interaction between the processor 8201, the chip 8200, the memory 8203, or the transceiver device.
  • the processor 8201 performs at least one of the other steps (for example, step S2102, step S2104, step S2106, but not limited thereto).
  • the present disclosure also proposes a storage medium, on which instructions are stored, and when the instructions are executed on the communication device 8100, the communication device 8100 executes any of the above methods.
  • the storage medium is an electronic storage medium.
  • the storage medium is a computer-readable storage medium, but is not limited to this, and it can also be a storage medium readable by other devices.
  • the storage medium can be a non-transitory storage medium, but is not limited to this, and it can also be a temporary storage medium.
  • the present disclosure also proposes a program product, which, when executed by the communication device 8100, enables the communication device 8100 to execute any of the above methods.
  • the program product is a computer program product.
  • the present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to execute any one of the above methods.

Landscapes

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

Abstract

La présente divulgation se rapporte à un procédé d'enregistrement de dispositif, à un second dispositif, à un premier dispositif et à un dispositif de réseau. Le procédé d'enregistrement de dispositif est exécuté par un premier dispositif, le premier dispositif comprend un nœud de relais ou un nœud auxiliaire, et le procédé consiste : à déterminer une première demande, la première demande étant utilisée pour demander à un dispositif de réseau d'effectuer un processus d'enregistrement d'un second dispositif ; et à envoyer la première demande au dispositif de réseau. La présente divulgation améliore la commodité d'enregistrement et peut résoudre efficacement des problèmes d'enregistrement sous une structure topologique complexe.
PCT/CN2023/109695 2023-07-27 2023-07-27 Procédé d'enregistrement de dispositif, premier dispositif, second dispositif et dispositif de réseau Pending WO2025020206A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2023/109695 WO2025020206A1 (fr) 2023-07-27 2023-07-27 Procédé d'enregistrement de dispositif, premier dispositif, second dispositif et dispositif de réseau
CN202380010320.2A CN117223350A (zh) 2023-07-27 2023-07-27 设备注册方法、第一设备、第二设备及网络设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/109695 WO2025020206A1 (fr) 2023-07-27 2023-07-27 Procédé d'enregistrement de dispositif, premier dispositif, second dispositif et dispositif de réseau

Publications (1)

Publication Number Publication Date
WO2025020206A1 true WO2025020206A1 (fr) 2025-01-30

Family

ID=89044867

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/109695 Pending WO2025020206A1 (fr) 2023-07-27 2023-07-27 Procédé d'enregistrement de dispositif, premier dispositif, second dispositif et dispositif de réseau

Country Status (2)

Country Link
CN (1) CN117223350A (fr)
WO (1) WO2025020206A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN120677672A (zh) * 2024-01-19 2025-09-19 北京小米移动软件有限公司 通信方法及装置、通信设备、通信系统、存储介质
CN120786730A (zh) * 2024-04-03 2025-10-14 维沃移动通信有限公司 行为执行方法、装置、通信设备及可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111480353A (zh) * 2017-12-18 2020-07-31 皇家Kpn公司 用于经由具有中继能力的用户设备（ue）在远程ue与电信网络之间建立信令连接的方法和设备
CN112911583A (zh) * 2017-07-11 2021-06-04 华为技术有限公司 设备接入方法、设备及系统
CN114143871A (zh) * 2020-09-04 2022-03-04 华为技术有限公司 网络连接方法、网络去连接方法及通信装置
WO2023078258A1 (fr) * 2021-11-03 2023-05-11 维沃移动通信有限公司 Procédé, appareil et dispositif de commande d'état de connexion, et support de stockage informatique

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112911583A (zh) * 2017-07-11 2021-06-04 华为技术有限公司 设备接入方法、设备及系统
CN111480353A (zh) * 2017-12-18 2020-07-31 皇家Kpn公司 用于经由具有中继能力的用户设备（ue）在远程ue与电信网络之间建立信令连接的方法和设备
CN114143871A (zh) * 2020-09-04 2022-03-04 华为技术有限公司 网络连接方法、网络去连接方法及通信装置
WO2023078258A1 (fr) * 2021-11-03 2023-05-11 维沃移动通信有限公司 Procédé, appareil et dispositif de commande d'état de connexion, et support de stockage informatique

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHINA TELECOM: "Correction of NSSAI in the Registration procedure and Service Request procedure", 3GPP DRAFT; S2-2006492, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Elbonia; 20200819 - 20200901, 2 September 2020 (2020-09-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051928879 *

Also Published As

Publication number Publication date
CN117223350A (zh) 2023-12-12

Similar Documents

Publication Publication Date Title
WO2025010574A1 (fr) Procédés de traitement d'informations, élément de réseau, terminal, système de communication et support de stockage
WO2025000401A1 (fr) Procédé et appareil de communication à relais, et dispositif de communication, système de communication et support de stockage
WO2025000129A1 (fr) Procédé et appareil de transmission d'informations, dispositif de communication, système de communication et support de stockage
WO2025007281A1 (fr) Procédés et dispositifs d'activation de dispositif
CN116889009A (zh) 通信方法及装置、通信设备、通信系统
CN117136627A (zh) 用户面连接建立方法及装置
WO2025020206A1 (fr) Procédé d'enregistrement de dispositif, premier dispositif, second dispositif et dispositif de réseau
WO2025091310A1 (fr) Procédé de découverte de relais, dispositif de communication, système de communication et support de stockage
WO2025025123A1 (fr) Procédé et appareil de réception de message
WO2025015612A1 (fr) Procédé et appareil de configuration de ressources et support de stockage
CN117561780A (zh) 通信处理方法、第一网元、第二网元、核心网设备
WO2025065642A1 (fr) Procédés de communication de relais, dispositifs de relais, terminaux, système de communication et support de stockage
WO2025030332A1 (fr) Procédé et appareil de positionnement
WO2025179499A1 (fr) Procédés de communication, premier dispositif, fonctions de réseau, système de communication et support de stockage
WO2025137950A1 (fr) Procédé d'indication d'informations, terminal, dispositif de réseau d'accès, système de communication, et support de stockage
WO2025065718A1 (fr) Procédés de traitement de communication, premier élément de réseau, seconds éléments de réseau et dispositifs de réseau central
WO2025137897A1 (fr) Procédé de communication, dispositif et support de stockage
WO2025189403A1 (fr) Procédés et dispositifs de traitement d'informations, et support de stockage
WO2025091309A1 (fr) Procédé de communication, dispositif de réseau, terminal, système de communication et support de stockage
WO2025137898A1 (fr) Procédé de communication, dispositif et support de stockage
WO2025137899A1 (fr) Procédé de communication, terminal, système de communication et support de stockage
WO2025123340A1 (fr) Procédé et appareil de connexion, et support de stockage
WO2025166554A1 (fr) Terminal, procédé d'envoi d'informations et support de stockage
WO2025161036A1 (fr) Procédé et appareil de traitement d'informations, et support de stockage
WO2025065292A1 (fr) Procédé d'établissement de connexion, premier dispositif, première entité et seconde entité

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

Country of ref document: EP

Kind code of ref document: A1