[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

CN113453343B - Service request method and device - Google Patents

Service request method and device Download PDF

Info

Publication number
CN113453343B
CN113453343B CN202010218594.9A CN202010218594A CN113453343B CN 113453343 B CN113453343 B CN 113453343B CN 202010218594 A CN202010218594 A CN 202010218594A CN 113453343 B CN113453343 B CN 113453343B
Authority
CN
China
Prior art keywords
message
service request
random access
service
terminal device
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.)
Active
Application number
CN202010218594.9A
Other languages
Chinese (zh)
Other versions
CN113453343A (en
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.)
Spreadtrum Communications Shanghai Co Ltd
Original Assignee
Spreadtrum Communications Shanghai 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 Spreadtrum Communications Shanghai Co Ltd filed Critical Spreadtrum Communications Shanghai Co Ltd
Priority to CN202010218594.9A priority Critical patent/CN113453343B/en
Priority to PCT/CN2021/079313 priority patent/WO2021190278A1/en
Publication of CN113453343A publication Critical patent/CN113453343A/en
Application granted granted Critical
Publication of CN113453343B publication Critical patent/CN113453343B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/52Allocation or scheduling criteria for wireless resources based on load
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/08Non-scheduled access, e.g. ALOHA
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/08Non-scheduled access, e.g. ALOHA
    • H04W74/0833Random access procedures, e.g. with 4-step access
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/27Transitions between radio resource control [RRC] states
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Landscapes

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

Abstract

The embodiment of the application discloses a service request method and a device, wherein the method comprises the following steps: the method comprises the steps that terminal equipment sends a first message to network equipment, the first message carries or indicates service request information, the service request information is used for sending service data to the network equipment, and the first message is used for a random access process. The terminal equipment can carry or indicate the service request information in the message of the random access process, so that the network equipment can consider the service requirements of the terminal equipment in the RRC idle state and the RRC non-activated state, thereby meeting the service requirements of the terminal equipment in different RRC states and saving the wireless resources of the network equipment.

Description

Service request method and device
Technical Field
The present application relates to the field of mobile communications technologies, and in particular, to a service request method and apparatus.
Background
In a 5th Generation cellular mobile communication system (5G, hereinafter referred to as "5G", also referred to as "New Radio over the air interface", or simply as "NR"), in order to satisfy New service characteristics and save power consumption of a User Equipment (UE), a New Radio Resource Control (RRC) state is defined, so that there are three RRC states in the 5G system, namely, an RRC Idle state, an RRC Inactive state, and an RRC Connected state.
In practical applications, in order to initiate a corresponding service, a User Equipment (UE) needs to first send a corresponding access request (such as a radio resource control connection request) to a base station corresponding to a camped cell. After receiving a random access request sent by the UE, the base station establishes Radio Resource Control (RRC) connection with the UE through a corresponding signaling interaction process, and then the UE accesses a network where a cell resides, thereby completing a corresponding service through the accessed network. However, in the above process, only the service requirements of the UE in the RRC connected state are considered, and the service requirements of the UE in the RRC idle state and the UE in the RRC inactive state are not considered.
Content of application
The embodiment of the application provides a service request method and a service request device, which can meet service requirements of terminal equipment in different RRC states and save wireless resources of network equipment.
In a first aspect, an embodiment of the present application provides a service request method, where the method includes:
the method comprises the steps that terminal equipment sends a first message to network equipment, the first message carries or indicates service request information, the service request information is used for requesting the network equipment to send service data, and the first message is used for a random access process.
In a second aspect, an embodiment of the present application provides a service request method, where the method includes:
the method comprises the steps that network equipment receives a first message from terminal equipment, wherein the first message carries service request information, the service request information is used for requesting the network equipment to send service data, and the first message is used for a random access process.
In a third aspect, an embodiment of the present application provides a service request apparatus, where the apparatus includes:
a sending unit, configured to send a first message to a network device by a terminal device, where the first message carries or indicates service request information, the service request information is used to request the network device to send service data, and the first message is used in a random access process.
In a fourth aspect, an embodiment of the present application provides a service request apparatus, where the apparatus includes:
a receiving unit, configured to receive, by a network device, a first message from a terminal device, where the first message carries or indicates service request information, the service request information is used to request the network device to send service data, and the first message is used in a random access process.
In a fifth aspect, embodiments of the present application provide a terminal device, which includes a processor, a memory, a communication interface, and one or more programs, stored in the memory and configured to be executed by the processor, the programs including instructions for performing some or all of the steps described in the method of the first aspect.
In a sixth aspect, embodiments of the present application provide a network device, which includes a processor, a memory, a communication interface, and one or more programs, which are stored in the memory and configured to be executed by the processor, the programs including instructions for performing some or all of the steps described in the method of the second aspect.
In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program for electronic data exchange, where the computer program makes a computer perform some or all of the steps described in the method of the first aspect.
In an eighth aspect, the present application provides a computer-readable storage medium storing a computer program for electronic data exchange, where the computer program makes a computer perform part or all of the steps described in the method of the second aspect.
In a ninth aspect, embodiments of the present application provide a computer program product, where the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to perform some or all of the steps described in the method according to the first aspect of the embodiments of the present application. The computer program product may be a software installation package.
In a tenth aspect, embodiments of the present application provide a computer program product, where the computer program product includes a non-transitory computer-readable storage medium storing a computer program, where the computer program is operable to cause a computer to perform some or all of the steps described in the method according to the second aspect of the embodiments of the present application. The computer program product may be a software installation package.
It can be seen that, in the embodiment of the present application, a terminal device sends a first message to a network device, where the first message carries or indicates service request information, the service request information is used to request the network device to send service data, and the first message is used in a random access process. The terminal equipment can carry or indicate the service request information in the message of the random access process, so that the network equipment can consider the service requirements of the terminal equipment in the RRC idle state and the RRC non-activated state, thereby meeting the service requirements of the terminal equipment in different RRC states and saving the wireless resources of the network equipment.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
Fig. 1 is a schematic architecture diagram of a communication system according to an embodiment of the present application;
fig. 2 is a flowchart illustrating a service request method according to an embodiment of the present application;
fig. 3A is a schematic diagram illustrating a four-step contention random access procedure according to an embodiment of the present application;
fig. 3B is a schematic diagram illustrating a flow of a two-step contention random access according to an embodiment of the present application;
fig. 3C is a schematic diagram illustrating a four-step non-contention random access procedure according to an embodiment of the present application;
fig. 3D is a flow chart illustrating a two-step non-contention random access according to an embodiment of the present application;
fig. 4 is a schematic flowchart of a four-step contention random access provided in the embodiment of the present application;
fig. 5 is a schematic flowchart of a service request initiated by msg1 according to an embodiment of the present application;
fig. 6A is a schematic flowchart of another msg1 service request initiation process provided in the embodiment of the present application;
fig. 6B is a schematic flowchart of a service request initiated by msg3 according to an embodiment of the present application;
fig. 6C is a schematic flowchart of a service request initiated by msgA according to an embodiment of the present application;
fig. 7 is a block diagram of functional units of a service request device according to an embodiment of the present application;
fig. 8 is a block diagram of functional units of a request apparatus for another service provided in an embodiment of the present application;
fig. 9A is a schematic structural diagram of a network device according to an embodiment of the present application;
fig. 9B is a schematic structural diagram of a terminal device according to an embodiment of the present application.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
It should be understood that the technical solution of the embodiment of the present application may be applied to a Global System for Mobile Communication (CSM), a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a Worldwide Interoperability for Microwave Access (Wi-MAX) System, a Long Term Evolution (Long Term Evolution, LTE) System, a 5G Communication System (e.g., new Radio, NR)), a Communication System in which Multiple Communication technologies are merged (e.g., a Communication System in which an LTE technology and an NR technology are merged), or various future Communication systems, e.g., a 6G Communication System, a 7G Communication System, and the like, and the embodiment of the present application is not limited thereto. The technical solution of the embodiment of the present application is also applicable to different network architectures, including but not limited to a relay network architecture, a dual link architecture, a Vehicle-to-any-object communication (Vehicle-to-event) architecture, and the like.
The embodiment of the application relates to terminal equipment. The terminal equipment comprises equipment with wireless communication function, can be deployed on land and comprises indoor or outdoor equipment, a handheld device, a wearable device or a vehicle-mounted device; can also be deployed on the water surface (such as a ship and the like); and may also be deployed in the air (e.g., airplanes, balloons, satellites, etc.). The terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in smart home (smart home), and the like. The terminal device may also be a handheld device with wireless communication function, a vehicle-mounted device, a wearable device, a computer device or other processing device connected to a wireless modem, a terminal device in a future 5G Network, or a terminal device in a Public Land Mobile Network (PLMN) for future evolution, and the like. The terminal devices in different networks may be called different names, for example: a user equipment, an access terminal, a subscriber unit, a subscriber Station, a Mobile Station (MS), a remote Station, a remote terminal, a Mobile device, a user terminal, a Wireless communication device, a user agent or a user equipment, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) Station, a Personal Digital Assistant (PDA), a terminal device in a 5G network or a future evolution network, etc., which are not limited in this embodiment.
The embodiment of the application relates to a network device. The Network device may be a device for communicating with the terminal device, and includes a device of a Radio Access Network (RAN), a base station controller of the RAN, and a device on a core Network side. For example, the network device may be a base station of a RAN on the access network side in a cellular network, including but not limited to: evolved Node B (eNB), radio Network Controller (RNC), node B (NB), base Station Controller (BSC), base Transceiver Station (BTS), home Base Station (e.g., home evolved Node B, or Home Node B, HNB), base Band Unit (BBU), management Entity (Mobility Management Entity, MME); for another example, the Network device may also be a node device in a Wireless Local Area Network (WLAN), such as an Access Controller (AC), a gateway, or a WIFI Access Point (AP); for another example, the network device may also be an Access network device (e.g., a gNB, a CU, a DU) in an NR system, and a node B (ng-eNB) that continues to evolve, where the gNB and the terminal device communicate using an NR technology, the ng-eNB and the terminal device communicate using an E-UTRA (Evolved Universal Radio Access) technology, and both the gNB and the ng-eNB may be connected to a 5G core network. The network device in the embodiment of the present application also includes a device that provides a base station function in a future new communication system, and the like.
The Core Network related in the embodiment of the present application may be an Evolved Packet Core (EPC), a 5G Core Network (5G Core Network), or may be a new Core Network in a future communication system. The 5G core network is composed of a set of devices, and implements Access and Mobility Management functions (AMF) for Mobility Management and other functions, user Plane Function (UPF) for providing packet routing and forwarding and QoS (Quality of Service) Management functions, session Management Function (SMF) for providing Session Management, IP address allocation and Management functions, and the like. The EPC may be composed of a Mobility Management Entity (MME) providing Mobility Management, gateway selection, and the like, a Serving Gateway (S-GW) providing packet forwarding, and the like, and a PDN Gateway (P-GW) providing terminal address allocation, rate control, and the like. For Multicast Broadcast Service (MBS), the core network may include several new network elements to implement functions such as packet forwarding, MBS conference management, qoS management, and transmission mode switching (switching between unicast and Multicast/broadcast transmission modes). Alternatively, the functions may be implemented by a network element in an existing core network.
In the embodiment of the application, a unidirectional communication link from an access network to a terminal device is defined as a downlink, data transmitted on the downlink is downlink data, and the transmission direction of the downlink data is called as a downlink direction; the unidirectional communication link from the terminal device to the access network is an uplink, the data transmitted on the uplink is uplink data, and the transmission direction of the uplink data is referred to as an uplink direction.
The term "connection" in the embodiment of the present application refers to various connection manners such as direct connection or indirect connection, so as to implement communication between devices, which is not limited in this embodiment of the present application.
It is to be understood that reference to "at least one" in the embodiments of the present application means one or more, and "a plurality" means two or more. "and/or" describes the association relationship of the associated object, indicating that there may be three relationships, for example, a and/or B, which may indicate: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple.
And, unless stated to the contrary, the embodiments of the present application refer to the ordinal numbers "first", "second", etc., for distinguishing a plurality of objects, and do not limit the sequence, timing, priority, or importance of the plurality of objects. For example, the first information and the second information are different information only for distinguishing them from each other, and do not indicate a difference in the contents, priority, transmission order, importance, or the like of the two kinds of information.
Hereinafter, some terms in the embodiments of the present application are explained so as to be easily understood by those skilled in the art.
Random Access (RA) procedure: the Random Access procedure is also referred to as a Random Access Channel (RACH) procedure. The Random Access procedure is divided into a Contention Based Random Access (CBRA) and a non-Contention Random Access (CFRA). In the competitive random access, the network equipment does not allocate a special lead code to the terminal equipment, but the terminal equipment randomly selects the lead code in a lead code pool to initiate random access, so that the risk of resource collision exists; the network equipment distributes the special lead code for the terminal equipment in the non-competitive random access, and the terminal equipment uses the special lead code to initiate the random access without the risk of resource collision.
In the 5G system, in order to satisfy new service characteristics and save power consumption of the terminal device, a new RRC state, RRC inactive state, is defined. In practical applications, the suspension or transmission of the traffic is determined by the network elements of the core network. The core network may decide the transmission mode in which to send the traffic based on the number of UEs interested in the traffic and the radio resources in the RAN. However, in this case, the network device only considers the requirements of the UE in the RRC connected state, and does not consider the requirements of the UE in the RRC idle state and the UE in the RRC inactive state.
In order to solve the above problems, the present application provides a service request method, in which service request information is carried or indicated in a message of a random access process by a terminal device, and service requirements of the terminal device in an RRC idle state and an RRC inactive state are considered, so that the service requirements of the terminal device in different RRC states are met, and radio resources of a network device are saved.
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a schematic diagram of a communication system according to an embodiment of the present disclosure. As shown in fig. 1, the communication system includes a network device 110 and a terminal device 120, and b =3 is taken as an example for explanation here. When the wireless communication network includes a core network, the network device 110 may also be connected to the core network. Network device 110 may also communicate with an Internet Protocol (IP) network, such as the internet (internet), a private IP network, or other data network. Network devices 110 may provide wireless access services to terminal devices 120, with each network device 110 corresponding to a service coverage area into which terminal devices 120 entering the area may communicate with the network device 110 via wireless signals. In addition, network devices 110 may also communicate with each other.
Based on the system architecture shown in fig. 1, the terminal device 120 sends a first message to the network device 110, where the first message carries or indicates service request information, the service request information is used to request the network device to send service data, and the first message is used in a random access process, and may specifically include msg1, msg3, or msgA; the network device 110 sends a third message to the terminal device 120 in response to receiving the first message, where the third message carries transmission mode information, the transmission mode information is used to indicate a transmission mode of the service data, the transmission mode includes unicast, multicast, or broadcast, the third message specifically includes msg2, msg4, or msgB, and in this process, the RRC state of the terminal device 120 includes: the RRC idle state, the RRC inactive state, or the RRC connected state take into account the service requirements of the terminal device in the RRC idle state and in the RRC inactive state. Therefore, by carrying or indicating the service request information in the message in the random access process, the network device 110 may perform data transmission of a unicast or multicast or broadcast service according to the service requirements of the terminal device 120 in different RRC states, thereby not only satisfying the service requirements of the terminal device 120, but also saving the wireless resources of the network device 110. It should be noted that the form and number of the network device 110 and the terminal device 120 shown in fig. 1 are only for example and do not constitute a limitation to the embodiment of the present application.
Referring to fig. 2, fig. 2 is a schematic flow chart of a service request method according to an embodiment of the present application, and as shown in fig. 2, the service request method includes the following steps:
s210, the terminal device sends a first message to the network device.
The first message carries or indicates service request information, the service request information is used for requesting the network device to send service data, and the first message is used for a random access process.
In practical application, when a terminal device initiates a service request, it needs to initiate a random access process first to establish an RRC connection, and in this application, in order to consider the service requirements of the terminal device in an RRC idle state and an RRC inactive state, the terminal device may carry or indicate a service request message in a message in the random access process to request a network device to send service data.
In the embodiment of the present application, the types of random access include four-step random access (4-step RA) and two-step random access (2-step RA). Since the random access procedure is classified into a contention random access and a non-contention random access, the 4-step RA includes a 4-step CBRA and a 4-step CFRA, and the 2-step RA includes a 2-step CBRA and a 2-step CFRA.
As shown in FIG. 3A, the 4-step CBRA is divided into four steps, msg1: the terminal equipment selects a Random Access Preamble (Random Access Preamble) and a Physical Random Access Channel (PRACH) resource and utilizes the PRACH resource to send the selected Preamble to the network equipment; msg2: the network equipment receives the lead code, calculates Timing Advance (TA), and sends a Random Access Response (Random Access Response) to the terminal equipment, wherein the Random Access Response comprises TA information, uplink scheduling grant (UL grant) aiming at msg3 and temporary C-RNTI (or T-CRNTI) distributed by the network equipment; msg3: scheduling transmission (scheduled transmission) information, wherein terminal equipment sends uplink transmission on a UL grant specified by msg2, and the uplink transmission contents of msg3 are different due to different random access reasons; msg4: a contention resolution (contention resolution) message, and the terminal device may determine whether the random access is successful according to msg 4. As shown in fig. 3B, the 2-step CBRA is divided into two steps, namely msgA and msgB, where the msgA includes a preamble in a random access procedure and a payload (payload) of a Physical Uplink Shared Channel (PUSCH), that is, the msgA may include contents in msg1 and msg3; msgB: the response to the msgA may include a contention resolution message, a backoff indication, and a backoff indication, that is, the msgB may include the contents of msg2 and msg 4.
As shown in FIG. 3C, the 4-step CFRA is divided into three steps, msg0: the network equipment allocates a special lead code for CFRA and PRACH resources used by random access to the terminal equipment; msg1: the terminal equipment sends a specified special lead code to the network equipment on a specified PRACH resource according to the indication of the msg 0; msg2: and the network equipment sends a random access response to the terminal equipment, wherein the random access response comprises TA information and subsequent uplink transmission resource allocation (UL grant). As shown in fig. 3D, the 2-step CFRA is divided into three steps, msg0, msgA and msgB, wherein msgA includes a dedicated preamble specified by msg0 and a payload of PUSCH, and msgB includes a random access response.
Optionally, the first message may include: msg1, msg3, or msgA.
Wherein the msg1 can belong to 4-step CBRA or 4-step CFRA; the msgA may be a 2-step CBRA or a 2-step CFRA, and the msg3 may be a 4-step CBRA. Specifically, when the terminal device adopts 4-step CBRA, the first message may be msg1 or msg3; when the terminal device adopts 4-step CFRA, the first message may be msg1; the first message may be msgA when the terminal device employs a 2-step CBRA or a 2-step CFRA.
The first message may include a control part (e.g., a preamble in msg 1) and a data part (e.g., a radio resource control message), and may carry service request information to initiate a service request, which may be carried in the data part.
In a possible embodiment of the present application, the first message may indicate service request information, and the terminal device may indicate different service request information through msg1, msg3, and msgA, or the terminal device may indicate the service request information through a mapping relationship between a resource of the first message and a service identifier. For example, assuming that a terminal device initiates a service a request to a network device, the terminal device may send a preamble a on a PRACH RO resource 1 corresponding to the service a through a mapping relationship between the service a and the preamble a and/or the PRACH RO resource 1 to instruct the terminal device to request the service a from the network device.
Optionally, in a case that the first message is the msg3 or the msgA, the first message includes one or more pieces of the service request information.
The msg3 and the msgA may be configured to transmit uplink data, and a size of a data portion of the msg3 and the msgA may carry a plurality of service request information, so that the msg3 and the msgA may include at least one service request information.
In this embodiment, the terminal device selects the first message according to the type of the random access and/or the number of the service request messages.
Optionally, the selecting, by the terminal device, the first message according to the type of the random access and/or the number of the service request messages includes:
when the type of the random access is the 4-step RA and/or the number of the service request messages is one, the first message is the msg1 or the msg3; when the type of the random access is the 4-step RA and the number of the service request messages is multiple, the first message is the msg3; and in the case that the type of the random access is the 2-step RA and/or the number of the service request messages is one or more, the first message is the msgA.
Specifically, in the case that the number of the service request information is one, the first message may be msg1, msg3, or msgA; under the condition that the number of the service request information is one and the type of the random access is the 4-step RA, the first message may be msg1 or msg3; in case that the number of the service request information is one and the type of the random access is the 2-step RA, the first message may be msgA. When the number of the service request messages is multiple, the first message may be msg3 or msgA; in the case that the number of the service request messages is multiple and the type of the random access is the 4-step RA, the first message may be msg3; in case that the number of the service request information is plural and the type of the random access is the 2-step RA, the first message may be msgA.
When the terminal device fails to initiate a service request through msg1, the terminal device may select msg3 or msgA to initiate a corresponding service request again according to the random access type, for example, when the next modification period (next modification period) does not yet detect the requested service, the terminal device selects msg3 to initiate a corresponding service request under the condition that the type of the random access is 4-step RA.
In an embodiment of the present application, the service request information includes at least one of the following: service identification, time information for receiving the service data and geographical position information for receiving the service data.
The service identifier is a unique identifier of the type of service requested by the terminal device, and may be one or more. The service identifier indicates that the information sent by the terminal device is information requesting the network device to send a service, but not information for other purposes. The time information for receiving the service data may include at least one of a start time for receiving the service data, a time period for receiving the service data, and a time duration for receiving the service data. The geographical location information for receiving the service data may include at least one of a cell list (cell list), a TA list, a beam (beam) list in a current serving cell and/or a neighboring cell, and a distance between the terminal device and the current serving cell.
Further, the service request information may further include a terminal device identifier, which may be identification information indicating an identity of the terminal device, for example, the terminal device identifier may be a user ID, S-TMSI, C-RNTI, temp-C-RNTI, or a random number.
In this embodiment of the present application, when the first message is the msg1 or the msgA, the terminal device determines the resource of the first message according to a mapping relationship between the resource of the first message and the service identifier.
For 4-step RA, the network device may give the terminal device available preamble and PRACH Transmission time (RO) resources, and the terminal device may select the preamble and PRACH RO resources used by this RA according to a certain rule. For 2-step RA, the network device configures the terminal device with a preamble and PUSCH resources for transmitting a payload in msgA, where the position of the PUSCH resource may have a certain mapping relationship with the preamble and/or the PRACH RO resource.
For example, it is assumed that a terminal device requests a multicast or broadcast service by sending msg1, where the terminal device may request a service corresponding to a resource used by msg1 through a preamble and/or PRACH RO resource used in an RA procedure. In particular, assuming that the end device wishes to receive service a from the network device, the end device may initiate a multicast or broadcast service request to the network device. As shown in fig. 4, a terminal requests a multicast/broadcast service by sending msg1, and if there is a mapping relationship between service a and preamble a, a terminal device selects preamble a to send when sending msg1, that is, the terminal device sends msg1 through preamble a to indicate a network device that the terminal device wants to receive service a, and PRACH RO resources in the process may be selected according to other rules. If the service a has a mapping relationship with the PRACH RO resource 1, the terminal device selects the PRACH RO resource 1 to transmit a preamble in the msg1 transmitting process, that is, the network device is indicated by transmitting the preamble through the location of the PRACH RO resource 1 that the terminal device wants to receive the service a, and the preamble transmitted in the process may be selected according to other rules. If the service a has a mapping relationship with both the preamble a and the PRACH RO resource 1, the terminal device selects to transmit the preamble a at the location of the PRACH RO resource 1 during the msg1 transmission process, that is, the network device is instructed that the terminal device wants to receive the service a by transmitting the preamble a at the location of the PRACH RO resource 1.
Further, the network device may determine the resource of the beam (beam) according to the resource of the terminal device that transmits the first message in the RA procedure, so that the network device may transmit the service data according to the beam direction requested by the terminal device, thereby saving the wireless resource.
Optionally, the method further includes: and the terminal equipment receives a second message from the network equipment, wherein the second message is used for indicating the mapping relation.
Wherein, the mapping relationship between the service identity and the preamble and/or the PRACH RO resource may be configured by the network device. The terminal device may receive information of a mapping relationship between the service identity and the preamble and/or the PRACH RO resources through the second message.
Further, the second message may include a system message, an RRC message, a Multimedia Access Control (MAC) Control Element (CE), or a MAC Service Data Unit (SDU), when the second message is an RRC message, the network device may not need to complete connection establishment of a Non-Access Stratum (NAS) layer for the terminal device, and the network device may configure a mapping relationship between the Service identifier and a preamble and/or a PRACH RO resource by carrying the mapping relationship information in an existing RRC message in an RA procedure of this time, or may carry the mapping relationship in an RRC message class in another RA procedure.
Further, the service type may be represented by a unique service identifier, and the unique service identifier may be at least one of a service ID (Identity), a Public Land Mobile Network (PLMN) ID, and a session ID.
In a possible embodiment of the present application, a mapping relationship between the resource of the first message and the service identifier may also be defined by a protocol, and the terminal device may select the resource of the first message according to the requested service according to the mapping relationship defined in the protocol.
In this embodiment of the present application, the RRC state of the terminal device includes: RRC idle state, RRC inactive state, or RRC connected state.
In order to consider the requirements of terminal devices in an RRC idle state and an RRC inactive state, so that a network device can perform data transmission of a multicast or broadcast service according to service requirements of the terminal devices in different RRC states, in the service request method provided by the present application, the terminal device may be in an idle state, an inactive state, or a connected state when initiating a service request.
In this embodiment, the terminal device sends the first message in a current serving cell or a neighboring serving cell, where the neighboring serving cell includes one or more cells.
When the terminal device is located in the coverage of multiple serving cells, the terminal device in different RRC states may send a first message to initiate a service request in any one of the multiple serving cells, where the multiple serving cells include a current serving cell and/or a neighboring serving cell.
For example, when a terminal device in an idle state or an inactive state resides in a serving cell 1, the terminal device may read a system message, an RRC message, an MAC CE, or an MAC SDU of the serving cell 1 to obtain a mapping relationship between a service a and an RA resource (for example, a preamble index and/or a PRACH RO resource carrying a service request message) in the serving cell 1, initiate an RA procedure on the RA resource corresponding to the requested service, and request the service in the serving cell 1; the terminal device may also read the message of the serving cell 2 to obtain the mapping relationship between the service a and the RA resource in the serving cell 2, and initiate an RA procedure on the RA resource of the serving cell 2 corresponding to the requested service to request the service, where the serving cells 1 and 2 are any serving cells in the coverage area of the multiple serving cells in which the terminal device is located. For a terminal device UE in a connected state residing in a serving cell 1, the terminal device may read a message of the serving cell 1 to obtain a mapping relationship between a service a and an RA resource in the serving cell 1, and initiate an RA process on the RA resource of the serving cell 1 corresponding to a requested service to request the service; the terminal device may also read the message of the neighboring cell 2 to obtain the mapping relationship between the service a and the RA resource in the neighboring serving cell 2, and initiate an RA process on the RA resource of the neighboring serving cell 2 corresponding to the requested service to request the service. Wherein, the serving Cell 1 may be a Master Cell Group (MCG) of the terminal device; the neighboring serving Cell 2 may be a Secondary Cell Group (SCG) of the terminal device, or may not be the SCG of the terminal device.
S220, the network equipment receives the first message from the terminal equipment.
In this embodiment, after receiving the first message, the network device may indicate whether to accept the service request in an RA procedure. The network device may send a third message to the terminal device, where the third message is used to indicate whether the network device accepts the service request, and the third message may include msg2, msg4, or msgB.
Specifically, when the terminal device sends service request information through msg1, the network device may indicate, by sending msg2, whether the network device accepts the service request, that is, the network device sends service data in a unicast, multicast or broadcast manner; when the terminal device sends the service request information through msg3, the network device may indicate whether the network device accepts the service request by sending msg 4; when the terminal device sends the service request information through msgA, the network device may be whether the network device accepts the service request by sending msgB.
Another possible implementation manner is that after receiving the first message, the network device does not send a third message to the terminal device, and the terminal device determines whether the network device receives the service request by checking whether the network device sends the requested service.
In another possible embodiment of the present application, after receiving the service request information, the network device may send a third message to the terminal device to indicate a transmission mode of the service data requested by the terminal device when the network device accepts the service request sent by the terminal device. The third message may carry transmission mode information, where the transmission mode information is used to indicate a transmission mode of the service data, the transmission mode includes unicast, broadcast, and multicast, and the third message may include msg2, msg4, or msgB.
Specifically, when the terminal device sends the service request information through msg1, the network device may indicate the transmission mode by sending msg2, that is, the network device sends service data in a unicast or multicast or broadcast manner; when the terminal device sends the service request information through msg3, the network device may indicate the transmission mode by sending msg 4; when the terminal device sends the service request information through msgA, the network device may indicate the transmission mode by sending msgB.
In another implementation manner of the embodiment of the present application, in an RA process, after receiving the service request information, a network device may indicate, by sending a third message to a terminal device, a transmission mode of service data requested by the terminal device, where the third message may include msg4 or msgB, and when the terminal device sends the service request information by msg1 or msg3, the network device may indicate the transmission mode by sending msg 4; when the terminal device sends the service request information through msgA, the network device may indicate the transmission mode by sending msgB. The network device may indicate the transmission mode of the service request according to an RRC message carried in msg4 or msgB.
Optionally, when the propagation mode is the unicast and the terminal device is in the RRC idle state or the RRC inactive state, the terminal device establishes an RRC connection with the network device.
It can be seen that, in the service request method described in this embodiment of the application, the terminal device sends a first message to the network device, where the first message carries or indicates service request information, the service request information is used to request the network device to send service data, and the first message is used in a random access process. The terminal equipment carries or indicates the service request information in the message of the random access process, so that the network equipment can consider the service requirements of the terminal equipment in the RRC idle state and the RRC non-activated state, thereby meeting the service requirements of the terminal equipment in different RRC states and saving the wireless resources of the network equipment.
Referring to fig. 5, fig. 5 is a schematic flow chart of another service request method according to an embodiment of the present application, and as shown in fig. 5, the service request method includes the following steps:
s510, the terminal device sends a first message to the network device.
The above detailed description of S510 may refer to the specific implementation described in S210 in fig. 2, and is not repeated herein.
S520, the network equipment receives the first message from the terminal equipment.
S530, the network equipment sends a third message to the terminal equipment.
In the RA procedure, after receiving the service request information, the network device may indicate a transmission mode of service data requested by the terminal device by sending a third message to the terminal device. The third message may carry transmission mode information, where the transmission mode information is used to indicate a transmission mode of the service data, the transmission mode includes unicast, broadcast, and multicast, and the third message may include msg2, msg4, or msgB.
Specifically, when the terminal device sends the service request information through msg1, the network device may indicate the transmission mode by sending msg2, that is, the network device sends service data in a unicast or multicast or broadcast manner, as shown in fig. 6A. When the terminal device sends the service request information through msg3, the network device may indicate the transmission mode by sending msg4, as shown in fig. 6B. When the terminal device sends the service request information through msgA, the network device may indicate the transmission mode by sending msgB, as shown in fig. 6C.
Wherein, the third message may include a control part (e.g., random access response in msg 2) and a data part (e.g., radio resource control message), the transmission mode information may be carried in the data part, and the network device may indicate a transmission mode corresponding to a service request by using a bit code word. When the first message carries a service request message, in order to respond to the service request, the third message carries a transmission mode message for indicating the data transmission mode of the requested service; when the first message carries multiple service request information, for example, msg3 carries multiple service request information, in order to respond to each service request, the third message may carry multiple transmission mode information, and there is a corresponding relationship between the transmission mode information and the service request information.
Further, the transmission mode information may be represented by M bit code words, where the M bit code words correspond to the number of service requests in a one-to-one manner, and an ith bit code word in the M bit code words may be used to indicate a transmission mode of an ith service request, where a bit code word length of the transmission mode information, that is, M, may be predefined by a protocol and represents that the transmission mode of the M service requests may be indicated at most once. For example, M may be 1, 2, 4, or other integer values. Illustratively, assuming that M is 4, the four codewords correspond to service request1, service request 2, service request 3 and service request 4 in turn, assuming that 1 indicates that the transmission mode is unicast and 0 indicates that the transmission mode is multicast or broadcast. When the transmission mode information is 1000, the service request1 is transmitted in a unicast mode, and the service request 2, the service request 3 and the service request 4 are transmitted in a multicast or broadcast mode; when the transmission mode information is 0110, it indicates that the service request 2 and the service request 3 are both transmitted in a unicast mode, and the service request1 and the service request 4 are both transmitted in a multicast or broadcast mode; when the transmission mode information is 1111, it indicates that the service request1, the service request 2, the service request 3, and the service request 4 are all transmitted by a unicast method.
In another possible embodiment, the transmission mode information may be represented using K bit code words,
Figure BDA0002425276860000142
Figure BDA0002425276860000141
represents rounding up; wherein N is the number of service requests. For example, when N is 3 or 4, K is 2, when N is 5 to 8, K is 3, when N is 9 to 16, K is 4, and so on. It should be noted that K bit code words are identification information of the service request, and therefore, when the transmission mode information can be represented by K bit code words, the network device only needs to represent the transmission mode information at the same timeThe transmission mode of a service request may be indicated. Exemplarily, assuming that N is 4, representing service request1, service request 2, service request 3, and service request 4, K takes 2, i.e. the transmission mode information may be represented by a 2-bit codeword. When the 2 bit code words are 00, the unicast transmission mode adopted by the service request1 is represented; when the 2 bit code words are 01, the unicast transmission mode adopted by the service request 2 is represented; when the 2 bit code words are 10, the unicast transmission mode adopted by the service request 3 is represented; when the 2-bit code word is 11, this indicates that the service request 4 adopts a unicast transmission mode.
In another possible embodiment of the present application, the method further includes: and the terminal equipment receives a third message from the network equipment, wherein the third message is used for indicating the transmission mode of the service data, and the third message comprises the msg4 or the msgB.
In the RA procedure, after receiving the service request information, the network device may indicate a transmission mode of service data requested by the terminal device by sending a third message to the terminal device, where the third message may include msg4 or msgB, and when the terminal device sends the service request information by msg1 or msg3, the network device may indicate the transmission mode by sending msg4, as shown in fig. 7. When the terminal device sends the service request information through msgA, the network device may indicate the transmission mode by sending msgB, as shown in fig. 8.
The network device may indicate the transmission mode of the service request according to an RRC message carried in msg4 or msgB. The RRC message may include, but is not limited to, any one of an RRC setup message, an RRC resume message, an RRC Release message, an RRC reject message, an RRC connection reconfiguration message, an RRC connection reestablishment message, an RRC connection setup message, an RRC connection resume message, or other RRC messages. For example, when the terminal device is in an idle state, the network device may indicate that the requested service is transmitted in a unicast manner by carrying an RRC setup message in msg4 or msgB; when the terminal device is in an inactive state, the network device may indicate that the requested service is transmitted in a unicast manner by carrying an RRC resume message in msg4 or msgB; when the terminal device is in a connected state, the network device may trigger the terminal device to stay in an idle state by using an RRC release message carried in msg4 or msgB to indicate that the requested service is transmitted in a multicast or broadcast manner.
In the embodiment of the application, the terminal device may initiate a service request by msg1, msg3, or msgA, and the network device may instruct, according to the service requirements of the terminal device in different RRC states, the transmission mode of the service request by msg2, msg4, or msgB to transmit service data, thereby satisfying the service requirements of the terminal device in different RRC states and saving the wireless resources of the network device.
Optionally, when the propagation mode is the unicast mode and the terminal device is in the RRC idle state or the RRC inactive state, the terminal device establishes an RRC connection with the network device.
When the terminal equipment initiates a service request through the first message, the network equipment determines to provide service data for the terminal equipment in a unicast mode. When the terminal device receives the unicast transmission instruction carried in the third message, if the terminal device is currently in an idle state or an inactive state, the terminal device needs to initiate establishment of an RRC connection, and then unicast transmission can be performed with the network device. When the terminal device is in an idle state, after receiving the third message, the terminal device may initiate establishment of an RRC connection by sending an RRC setup Request message in the RA process; when the terminal device is in the inactive state, after receiving the third message, the terminal device may initiate establishment of an RRC connection by sending an RRC Resume Request message or an RRC Resume Request1 message in the RA process, where scenarios used by the RRC Resume Request message or the RRC Resume Request1 message are different. In another example of the embodiment of the present application, when the terminal device is in an idle state, after receiving the third message, the terminal device may initiate establishment of an RRC connection by sending an RRC setup Request message in another RA procedure; when the terminal device is in the inactive state, after receiving the third message, the terminal device may initiate establishment of an RRC connection by sending an RRC Resume Request message or an RRC Resume Request1 message in another RA procedure.
For example, as shown in fig. 6A, a terminal device in an idle state initiates a service request through msg1, and a network device indicates, in msg2, the terminal device that the service request sends service data through a unicast transmission mode. After receiving msg2, the terminal device may initiate establishment of RRC connection by carrying an RRC setup Request message in msg3 or other messages in the current RA procedure, or initiate establishment of RRC connection by carrying an RRC setup Request message in msg3 or other messages in another RA procedure (not shown in the figure).
In this embodiment of the application, the network device may indicate the transmission mode of the request service through the third message, and when the transmission mode is unicast and the terminal device is in an RRC idle state or an RRC inactive state, the terminal device establishes an RRC connection with the network device in an RA process, so as to reduce a time delay of establishing the RRC connection and improve service performance of the terminal device.
It should be noted that, when the propagation mode indicated by the third message is multicast or broadcast, and the terminal device is in the RRC idle state or the RRC inactive state, the terminal device may send the service data without establishing an RRC connection with the network device. For example, for a terminal device in an RRC idle state and adopting a 2-type CFRA, it may initiate a service request through msg1, obtain a transmission mode of the service request as multicast by receiving msg2, and then may receive the requested service data on a downlink physical shared channel.
And S540, the terminal equipment receives a third message from the network equipment.
It can be seen that, in this embodiment of the present application, a terminal device sends a first message to a network device, where the first message carries or indicates service request information, the service request information is used to request the network device to send service data, the first message is used in a random access process, the network device receives the first message and sends a third message to the terminal device, and the third message is used to carry or indicate a transmission mode of the service data. The terminal equipment can carry or indicate service request information in the message of the random access process, and the network equipment considers the service requirements of the terminal equipment in different RRC states and indicates the transmission mode of the service request to send service data by sending a third message, so that the service requirements of the terminal equipment in different RRC states are met, and the wireless resources of the network equipment are saved.
The above description has introduced the solution of the embodiment of the present application mainly from the perspective of the method-side implementation process. It is understood that the electronic device comprises corresponding hardware structures and/or software modules for performing the respective functions in order to realize the functions. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments provided herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiment of the present application, the electronic device may be divided into the functional units according to the method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
Referring to fig. 7, fig. 7 is a block diagram of functional units of a service request apparatus 700 according to an embodiment of the present application, where the service request apparatus 700 is applied to a terminal device, and the apparatus 700 includes: a sending unit 710 for sending, among other things,
a sending unit 710, configured to send a first message to a network device by a terminal device, where the first message carries or indicates service request information, the service request information is used to request the network device to send service data, and the first message is used in a random access process.
In a possible embodiment of the present application, the first message includes msg1, msg3, or msgA.
In a possible embodiment of the present application, in a case that the first message is the msg3 or the msgA, the first message includes one or more pieces of the service request information.
In a possible embodiment of the present application, the apparatus 700 further includes a selecting unit 720, where the selecting unit 720 is configured to: and the terminal equipment selects the first message according to the type of the random access and/or the quantity of the service request information, wherein the type of the random access comprises four-step random access 4-step RA and two-step random access 2-step RA.
In a possible embodiment of the present application, the selecting unit 720 is specifically configured to: when the type of the random access is the 4-step RA and/or the number of the service request messages is one, the first message is the msg1 or the msg3; when the type of the random access is the 4-step RA and the number of the service request messages is multiple, the first message is the msg3; and in the case that the type of the random access is the 2-step RA and/or the number of the service request messages is one or more, the first message is the msgA.
In a possible embodiment of the present application, the service request information includes at least one of the following: service identification, time information for receiving the service data and geographical position information for receiving the service data.
In a possible embodiment of the present application, the apparatus 700 further includes a determining unit 730, where the determining unit 730 is configured to: and under the condition that the first message is the msg1 or the msgA, the terminal equipment determines the resource of the first message according to the mapping relation between the resource of the first message and the service identifier.
In a possible embodiment of the present application, the apparatus 700 further includes a receiving unit 740, where the receiving unit 740 is configured to: and the terminal equipment receives a second message from the network equipment, wherein the second message is used for indicating the mapping relation.
In a possible embodiment of the present application, the receiving unit 740 is further configured to: the terminal device receives a third message from the network device, where the third message carries transmission mode information, the transmission mode information is used to indicate a transmission mode of the service data, the transmission mode includes unicast, multicast and broadcast, and the third message includes msg2, msg4 or msgB.
In another possible embodiment of the present application, the receiving unit 740 is further configured to: the terminal device receives a third message from the network device, where the third message is used to indicate a transmission mode of the service data, and the third message includes the msg4 or the msgB.
In a possible embodiment of the present application, the RRC state of the terminal device includes: RRC idle state, RRC inactive state, or RRC connected state.
In a possible embodiment of the present application, when the propagation mode is the unicast mode and the terminal device is in the RRC idle state or the RRC inactive state, the terminal device and the network device perform RRC connection establishment.
In a possible embodiment of the present application, the terminal device sends the first message in a current serving cell or a neighboring serving cell, where the neighboring serving cell includes one or more neighbor serving cells.
It can be seen that the service request apparatus described in this embodiment of the present application is applied to a terminal device, where the terminal device sends a first message to a network device, where the first message carries or indicates service request information, the service request information is used to request the network device to send service data, and the first message is used in a random access process. The terminal equipment can carry or indicate the service request information in the message of the random access process, so that the network equipment can consider the service requirements of the terminal equipment in an RRC idle state and an RRC non-activated state, thereby meeting the service requirements of the terminal equipment in different RRC states and saving the wireless resources of the network equipment.
Referring to fig. 8, fig. 8 is a block diagram illustrating functional units of a service request apparatus 800 according to an embodiment of the present application, where the service request apparatus 800 is applied to a network device, and the apparatus 800 includes: a receiving unit 810 for receiving, among other things,
a receiving unit 810, configured to receive, by a network device, a first message from a terminal device, where the first message carries or indicates service request information, the service request information is used to request the network device to send service data, and the first message is used in a random access process.
In a possible embodiment of the present application, the first message includes msg1, msg3, or msgA.
In a possible embodiment of the present application, in a case that the first message is the msg3 or the msgA, the first message includes one or more pieces of the service request information.
In a possible embodiment of the present application, the service request information includes at least one of the following: service identification, time information for receiving the service data and geographical position information for receiving the service data.
In a possible embodiment of the present application, the apparatus 800 further includes a sending unit 820, where the sending unit 820 is configured to: and the network equipment sends a second message to the terminal equipment, wherein the second message is used for indicating the mapping relation between the resource of the first message and the service identifier.
In a possible embodiment of the present application, the sending unit 820 is further configured to: the network device sends a third message to the terminal device, where the third message carries transmission mode information, the transmission mode information is used to indicate a transmission mode of the service data, the transmission mode includes unicast, multicast and broadcast, and the third message includes msg2, msg4 or msgB.
In another possible embodiment of the present application, the sending unit 820 is further configured to: and the network equipment sends a third message to the terminal equipment, wherein the third message is used for indicating the transmission mode of the service data, and the third message comprises the msg4 and the msgB.
It can be seen that the service request apparatus described in this embodiment of the present application is applied to a network device, where the network device receives a first message from a terminal device, where the first message carries or indicates service request information, the service request information is used to request the network device to send service data, and the first message is used in a random access process. The network device sends the service data by receiving the service request initiated by the terminal device in different RRC states, so that the service requirements of the terminal device in different RRC states can be met, and the wireless resources of the network device are saved.
It can be understood that the functions of each program module of the service request device in the embodiment of the present application may be specifically implemented according to the method in the foregoing method embodiment, and the specific implementation process may refer to the relevant description of the foregoing method embodiment, which is not described herein again.
Referring to fig. 9A, fig. 9A is a terminal device according to an embodiment of the present application, where the terminal device includes: one or more processors, one or more memories, one or more communication interfaces, and one or more programs;
the one or more programs are stored in the memory and configured to be executed by the one or more processors;
the program includes instructions for performing the steps of:
the method comprises the steps that terminal equipment sends a first message to network equipment, the first message carries or indicates service request information, the service request information is used for sending service data to the network equipment, and the first message is used for a random access process.
In a possible embodiment of the application, the program comprises instructions for further performing the steps of: setting the first message to msg1, msg3 or msgA.
In a possible embodiment of the present application, in terms that the first message is the msg3 or the msgA, the program includes instructions further for performing the following steps: and carrying one or more service request messages by the first message.
In a possible embodiment of the application, the program comprises instructions for further performing the steps of: and the terminal equipment selects the first message according to the type of the random access and/or the quantity of the service request information, wherein the type of the random access comprises four-step random access 4-step RA and two-step random access 2-step RA.
In a possible embodiment of the application, the program comprises instructions for further performing the steps of: in a case that the type of the random access is the 4-step RA and/or the number of the service request messages is one, the first message is the msg1 or the msg3; when the type of the random access is the 4-step RA and the number of the service request messages is multiple, the first message is the msg3; and in the case that the type of the random access is the 2-step RA and/or the number of the service request messages is one or more, the first message is the msgA.
In a possible embodiment of the application, the program comprises instructions for further performing the steps of: and carrying at least one item of service identification, time information for receiving the service data and geographical location information for receiving the service data in the service request information.
In a possible embodiment of the present application, in terms that the first message is the msg1 or the msgA, the program includes instructions further for performing the following steps: and the terminal equipment determines the resource of the first message according to the mapping relation between the resource of the first message and the service identifier.
In a possible embodiment of the application, the program comprises instructions for further performing the steps of: and the terminal equipment receives a second message from the network equipment, wherein the second message is used for indicating the mapping relation.
In a possible embodiment of the application, the program comprises instructions for further performing the steps of: the terminal device receives a third message from the network device, where the third message carries transmission mode information, the transmission mode information is used to indicate a transmission mode of the service data, the transmission mode includes unicast, multicast and broadcast, and the third message includes msg2, msg4 or msgB.
In another possible embodiment of the present application, the program includes instructions for performing the further steps of: the terminal device receives a third message from the network device, where the third message is used to indicate a transmission mode of the service data, and the third message includes the msg4 or the msgB.
In a possible embodiment of the application, the program comprises instructions for further performing the steps of: and setting the Radio Resource Control (RRC) state of the terminal equipment to be an RRC idle state, an RRC inactive state or an RRC connected state.
In a possible embodiment of the present application, in an aspect that the propagation mode is the unicast and the terminal device is in the RRC idle state or the RRC inactive state, the program includes instructions further configured to: and establishing RRC connection between the terminal equipment and the network equipment.
In a possible embodiment of the application, the program comprises instructions for further performing the steps of: and the terminal equipment sends the first message in a current serving cell or adjacent serving cells, wherein the adjacent serving cells comprise one or more than one.
It should be noted that, for a specific implementation process in the embodiment of the present application, reference may be made to the specific implementation process described in the foregoing method embodiment, and details are not described herein again.
Referring to fig. 9B, fig. 9B is a network device according to an embodiment of the present application, where the network device includes: one or more processors, one or more memories, one or more communication interfaces, and one or more programs;
the one or more programs are stored in the memory and configured to be executed by the one or more processors;
the program includes instructions for performing the steps of:
the method comprises the steps that network equipment receives a first message from terminal equipment, the first message carries or indicates service request information, the service request information is used for requesting the network equipment to send service data, and the first message is used for a random access process.
In a possible embodiment of the application, the program comprises instructions for further performing the steps of: indicating that the first message is set to msg1, msg3, or msgA.
In a possible embodiment of the present application, in terms that the first message is the msg3 or the msgA, the program includes instructions further for performing the following steps: and indicating that the first message carries one or more service request messages.
In a possible embodiment of the present application, the program includes instructions for performing the following steps: indicating that the service request information is configured as at least one of: service identification, time information for receiving the service data and geographical position information for receiving the service data.
In a possible embodiment of the present application, the program includes instructions for performing the following steps: and the network equipment sends a second message to the terminal equipment, wherein the second message is used for indicating the mapping relation between the resource of the first message and the service identifier.
In a possible embodiment of the application, the program comprises instructions for further performing the steps of: the network device sends a third message to the terminal device, where the third message carries transmission mode information, the transmission mode information is used to indicate a transmission mode of the service data, the transmission mode includes unicast, multicast and broadcast, and the third message includes msg2, msg4 or msgB.
In a possible embodiment of the application, the program comprises instructions for further performing the steps of: and the network equipment sends a third message to the terminal equipment, wherein the third message is used for indicating the transmission mode of the service data, and the third message comprises the msg4 and the msgB.
It should be noted that, for a specific implementation process in the embodiment of the present application, reference may be made to the specific implementation process described in the foregoing method embodiment, and details are not described herein again.
Embodiments of the present application further provide a computer storage medium, where the computer storage medium stores a computer program for electronic data exchange, and the computer program makes a computer execute part or all of the steps of any one of the methods as described in the above method embodiments.
Embodiments of the present application also provide a computer program product comprising a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any of the methods as described in the above method embodiments. The computer program product may be a software installation package.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to the related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the above-described division of the units is only one type of division of logical functions, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed coupling or direct coupling or communication connection between each other may be through some interfaces, indirect coupling or communication connection between devices or units, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiments of the present application.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.
The integrated unit may be stored in a computer readable memory if it is implemented in the form of a software functional unit and sold or used as a stand-alone product. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a memory, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method of the embodiments of the present application. And the aforementioned memory comprises: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable memory, which may include: flash disk, ROM, RAM, magnetic or optical disk, and the like.
The foregoing detailed description of the embodiments of the present application has been presented to illustrate the principles and implementations of the present application, and the above description of the embodiments is only provided to help understand the method and the core concept of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, the specific implementation manner and the application scope may be changed, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims (23)

1. A service request method is applied to a terminal device, and comprises the following steps:
sending a first message, where the first message carries or indicates service request information, where the service request information is used to request a network device to send service data, and the service request information includes at least one of the following: the first message is used for a random access process, the first message is selected according to the type of random access and/or the quantity of the service request information, and the type of the random access comprises four-step random access 4-step RA and two-step random access 2-step RA.
2. The method of claim 1, wherein the first message comprises msg1, msg3, or msgA.
3. The method of claim 1, wherein in a case that the first message is msg3 or msgA, the first message includes one or more pieces of the service request information.
4. The method of claim 1, wherein the first message is selected according to a type of random access and/or a quantity of the service request information, and comprises:
when the type of the random access is the 4-step RA and/or the number of the service request messages is one, the first message is msg1 or msg3;
when the type of the random access is the 4-step RA and/or the number of the service request messages is multiple, the first message is msg3;
and in the case that the type of the random access is the 2-step RA and/or the number of the service request messages is one or more, the first message is msgA.
5. The method of claim 1, wherein in a case that the first message is msg1 or msgA, the resource of the first message is determined according to a mapping relationship between the resource of the first message and the service identifier.
6. The method of claim 5, further comprising:
and receiving a second message, wherein the second message is used for indicating the mapping relation.
7. The method of claim 1, further comprising:
receiving a third message, where the third message carries transmission mode information, where the transmission mode information is used to indicate a transmission mode of the service data, the transmission mode includes unicast, multicast, and broadcast, and the third message includes msg2, msg4, or msgB.
8. The method of claim 1, further comprising:
receiving a third message, where the third message is used to indicate a transmission mode of the service data, and the third message includes msg4 or msgB.
9. The method according to claim 7 or 8, wherein the radio resource control, RRC, state of the terminal device comprises: RRC idle state, RRC inactive state, or RRC connected state.
10. The method of claim 7, wherein the terminal device performs RRC connection establishment with the network device when the transmission mode is the unicast mode and the terminal device is in an RRC idle state or an RRC inactive state.
11. The method of claim 1, wherein the terminal device sends the first message on a current serving cell or on neighboring serving cells, and wherein the neighboring serving cells comprise one or more cells.
12. A service request method is applied to a network device, and the method comprises the following steps:
receiving a first message, where the first message carries or indicates service request information, the service request information is used to request a network device to send service data, and the service request information includes at least one of the following: the first message is used for a random access process, the first message is selected according to the type of random access and/or the quantity of the service request information, and the type of the random access comprises four-step random access 4-step RA and two-step random access 2-step RA.
13. The method of claim 12, wherein the first message comprises msg1, msg3, or msgA.
14. The method of claim 12, wherein in a case that the first message is msg3 or msgA, the first message includes one or more pieces of the service request information.
15. The method of claim 12, further comprising:
and sending a second message, wherein the second message is used for indicating the mapping relation between the resource of the first message and the service identifier.
16. The method of claim 12, further comprising:
and sending a third message, wherein the third message carries transmission mode information, the transmission mode information is used for indicating a transmission mode of the service data, the transmission mode comprises unicast, multicast and broadcast, and the third message comprises msg2, msg4 or msgB.
17. The method according to any one of claims 12-16, further comprising:
and sending a third message, wherein the third message is used for indicating the transmission mode of the service data, and the third message comprises msg4 and msgB.
18. An apparatus for requesting a service, the apparatus comprising:
a sending unit, configured to send a first message, where the first message carries or indicates service request information, the service request information is used to request a network device to send service data, and the service request information includes at least one of the following information: the first message is used for a random access process, the first message is selected according to the type of random access and/or the quantity of the service request information, and the type of the random access comprises four-step random access 4-step RA and two-step random access 2-step RA.
19. An apparatus for requesting a service, the apparatus comprising:
a receiving unit, configured to receive a first message, where the first message carries or indicates service request information, the service request information is used to request a network device to send service data, and the service request information includes at least one of the following: the first message is used for a random access process, the first message is selected according to the type of random access and/or the quantity of the service request information, and the type of the random access comprises four-step random access 4-step RA and two-step random access 2-step RA.
20. A terminal device, characterized in that the terminal device comprises a processor, a memory, a communication interface, and one or more programs stored in the memory and configured to be executed by the processor, the programs comprising instructions for carrying out the steps in the method according to any one of claims 1-11.
21. A network device comprising a processor, a memory, a communication interface, and one or more programs stored in the memory and configured to be executed by the processor, the programs comprising instructions for performing the steps in the method of any of claims 12-17.
22. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program causes a computer to perform the method according to any one of claims 1-11.
23. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for electronic data exchange, wherein the computer program causes a computer to perform the method according to any one of claims 12-17.
CN202010218594.9A 2020-03-25 2020-03-25 Service request method and device Active CN113453343B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010218594.9A CN113453343B (en) 2020-03-25 2020-03-25 Service request method and device
PCT/CN2021/079313 WO2021190278A1 (en) 2020-03-25 2021-03-05 Service request method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010218594.9A CN113453343B (en) 2020-03-25 2020-03-25 Service request method and device

Publications (2)

Publication Number Publication Date
CN113453343A CN113453343A (en) 2021-09-28
CN113453343B true CN113453343B (en) 2023-04-18

Family

ID=77806738

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010218594.9A Active CN113453343B (en) 2020-03-25 2020-03-25 Service request method and device

Country Status (2)

Country Link
CN (1) CN113453343B (en)
WO (1) WO2021190278A1 (en)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114615751A (en) * 2020-12-04 2022-06-10 维沃移动通信有限公司 Random access method, device and equipment
CN116939505A (en) * 2022-03-29 2023-10-24 华为技术有限公司 Communication method and device
CN116939506A (en) * 2022-04-02 2023-10-24 展讯通信(上海)有限公司 Multicast session/service transmission method, device, chip and module equipment
CN116980836A (en) * 2022-04-22 2023-10-31 大唐移动通信设备有限公司 Service processing method, device, terminal equipment and network equipment
CN117479342A (en) * 2022-07-22 2024-01-30 大唐移动通信设备有限公司 Uplink processing method, downlink processing method, paging processing method and communication equipment
CN118235440A (en) * 2022-10-21 2024-06-21 北京小米移动软件有限公司 Multicast service receiving, configuring and transmitting method and device
CN118785105A (en) * 2023-04-04 2024-10-15 荣耀终端有限公司 Method and device for transmitting multicast service

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101115292B (en) * 2006-07-27 2011-06-08 华为技术有限公司 Method for paging and connecting terminal and terminal and system for fast activating data transmission
US9445446B2 (en) * 2012-07-09 2016-09-13 Industrial Technology Research Institute Method and apparatus for device to device communication
WO2018080229A1 (en) * 2016-10-31 2018-05-03 엘지전자 주식회사 Method for performing random access by terminal, and device supporting same
US11134422B2 (en) * 2017-02-28 2021-09-28 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Random access method, terminal device and network device
WO2018201483A1 (en) * 2017-05-05 2018-11-08 华为技术有限公司 Data transmission method, terminal device and access network device
CN108496341A (en) * 2017-06-30 2018-09-04 北京小米移动软件有限公司 Method, apparatus, equipment and the base station of edge calculations are realized in cellular network
CN109587769B (en) * 2017-09-28 2022-02-22 中兴通讯股份有限公司 Data transmission method and device and search space optimization method and device
CN114222295A (en) * 2017-11-06 2022-03-22 华为技术有限公司 Communication method and device
CN108521890B (en) * 2018-04-17 2022-05-13 北京小米移动软件有限公司 Random access method and device
US11190989B2 (en) * 2018-05-22 2021-11-30 Apple Inc. Mobility management for inter-gNB (next generation node-b) handover in new radio (NR) systems
WO2020024611A1 (en) * 2018-08-03 2020-02-06 Oppo广东移动通信有限公司 Information transmission method and device, and computer storage medium

Also Published As

Publication number Publication date
CN113453343A (en) 2021-09-28
WO2021190278A1 (en) 2021-09-30

Similar Documents

Publication Publication Date Title
CN113453343B (en) Service request method and device
KR102478372B1 (en) Random access method and apparatus
US9084263B2 (en) Network connection method and system
CN116325900A (en) Communication method and device
US9794972B2 (en) Base station, user equipment and methods for random access
CN113498022A (en) Configuration information updating method and device
CN105101454A (en) Method and device for random access of MTC UE (Machine Type Communication User Equipment)
US11516852B2 (en) Random access method of communications apparatus, apparatus, and storage medium
WO2019223792A1 (en) Data transmission method, device, base station, terminal, and readable storage medium
WO2018024027A1 (en) Resource allocation and request initiating method and device for non-contention based random access
WO2022017118A1 (en) Method for random access and communication device
EP4247061A1 (en) Communication method, apparatus, and system
CN116546573A (en) Network slice information processing method, terminal equipment and network equipment
CN113518466B (en) Feedback method and device of multicast broadcast service
WO2018028436A1 (en) Random access method, network-side device and terminal
WO2022126667A1 (en) Method for processing random access response, and network device and terminal device
WO2021195994A1 (en) Data transmission method and device applied to access network
EP4373200A1 (en) Random access method and apparatus
WO2021207902A1 (en) Data transmission method and apparatus
WO2022067614A1 (en) Wireless communication method, terminal device, and network device
CN111757549B (en) Method for establishing connection and communication device
CN111757537A (en) Random access method and device
WO2024230561A1 (en) Communication method and apparatus
WO2023169362A1 (en) Paging method and apparatus thereof
WO2023169580A1 (en) Data transmission method, apparatus, storage medium, terminal device, and network device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant